
| L: Explanation of Function | |
| 01. Strategy and Planning | This function is outside of the scope of an availability contract but is included because it has a key interface with it. This function determines the asset (platform) capability changes that will be necessary to achieve medium to long term defence plans. |
| 02. Mission / Operation | This area presents the planning and control of operations/missions in accordance with operational objectives/directives and the execution of these operations/missions via the operating of allocated assets. |
| 02.1 Ops Planning and Control | This function plans operations/missions in accordance with operational objectives/directives and tasks accordingly based on allocated assets. Control of the mission/operation is performed based on feedback from operators and operating assets. |
| 02.2 Operate Asset | This activity operates the allocated asset to perform the operational/mission task and feedbacks fault and usage data. |
| 03. Fleet and Asset | Management of asset to extract optimum life (required life vs cost) and fleet management to optimise the utilisation of that life. |
| 03.1 Structure Fleet | Determining the composition (type and quantity per location) of assets from a fleet perspective in order to support the stated capability requirements. |
| 03.1.1 Define Fleet Composition | Define Fleet Composition - This function compares the requirements on the fleet (based on the operational profiles and the actual planned deployments) with the actual fleet assets to identify :
1) the optimum fleet composition (with budget to implement & sustain it) 2) the required asset characteristics (with budget to implement it) |
| 03.1.2 Define Fleet Support Structures | This function defines all the necessary support structures to sustain the desiged fleet through life |
| 03.1.2.1 Determine Requirements and Context | This function determines the requirements for support structures and documents the context in which those requirements are valid. |
| 03.1.2.2 Plan Development of Structures and Resources | This functions plans how the support structures are to be developed including resource needs across appropriate lines of development |
| 03.1.2.3 Evaluate Deployment Options | This functions evaluates options for the deployment of support structures together with the appropriate resource implications. |
| 03.1.3 Plan Upgrades | This function provides the high level plan for the physical embodiment of approved upgrades (changed/ improved capability) to assets - based on fleet perspective |
| 03.2 Establish fleet | The actvities required to assemble assets in the required condition and their placement to deliver the required fleet composition |
| 03.2.1 Initiate Fleet Composition Change | This function identifies, schedules and initiates all tasks required to realise the planned fleet composition |
| 03.2.2 Monitor and Control Fleet Composition Change | This function interprets the feedback from all domains to track the status of the identified composition change task and initiate corrective actions for deviations |
| 03.2.3 Audit Fleet Capability | This function compares the actual state of the fleet with the planned and identifies the actual capability it can deliver in this state and special conditions/ limitations that should apply. |
| 03.3 Establish Fleet Support Structure | The actvities required to assemble the support structure in the required condition and its placement to deliver the required support capability. |
| 03.3.1 Initiate Support Structure Change | This function plans and initiates the tasks necessary to establish the changed support structures |
| 03.3.1.1 Identify Support Structure Change Needs | This function determines the changess that are necessary to support structures across the lines of development |
| 03.3.1.2 Plan Acquisition and Deployment | This function plans the acquisition and deployment of support structures |
| 03.3.1.3 Acquire and Deploy Structure and Resources | This function acquires support structures and supporting resource capability across lines of development and deploys them. |
| 03.3.2 Monitor and Control Fleet Support Structure Change | This function monitors the progress of the support structure change tasks and initiates corrective actions |
| 03.3.3 Audit Fleet Support | This function provides an audited view of the status of the current support structures against requirements. |
| 03.4 Sustain Assets | Management of asset to extract optimum life (required life vs cost) |
| 03.4.1 Identify Sustainment Tasks | This function identies all tasks required to optimise the life of a specific asset within the budget constraints |
| 03.4.2 Plan and Initiate Sustainment Tasks | This function plans and initiate the sustainment tasks on the various domains based on current and planned allocation of an asset |
| 03.4.3 Execute Other Sustainment Tasks | This function initiates sustainment tasks that are not part of maintenance or supply chain support |
| 03.4.4 Monitor and Control Sustainment Tasks | This function interprets the feedback from all domains to track the status of the identified sustainment tasks and initiate corrective actions for deviations |
| 03.4.5 Audit asset | This function compares the actual state of the asset with the planned and identifies the actual useable life it can sustain in this state and special conditions/ limitations that should apply. |
| 03.5 Allocate Assets to Task | These functions identifies operational requirements, matches and allocates the most suited asset to a given task based on task priority and asset status. |
| 03.5.1 Identify Task Requirements | This function identifies the type(s) of asset suitable to execute the given task. |
| 03.5.2 Match Assets to Op Task | This function identifies the assets (serial numbers) suitable and available to execute the task. |
| 03.5.3 Allocate Asset to Task | This function links the most suited asset to a given task based on task priority and asset status. |
| 06. Configuration | This function provides visibility into, and control over a product's performance, functional and physical attributes for the product life cycle. |
| 06.1 Manage Configuration Baseline | Action to establish which members of the Product breakdown structure are to be changed, including new production and existing products. |
| 06.1.1 Manage Configuration Plans | The activities necessary neccessary to provide the context and environment in which to manage the configuration of the product |
| 06.1.2 Specify Configuration | Specify Configuration is the CM interrelated process that is the basis from which, the configuration of products is defined and verified, products and records are labelled, and accountability is maintained.
Specify Configuration, (Configuration Identification), is a set of processes, which occur throughout the product life cycle and is the basis of all subsequent configuration management of a product and its constituent elements. Specify Configuration includes: ·selecting Configuration Items (CIs) (if required) at appropriate levels of the product structure to facilitate the recording, management and support of the items and their information; ·determining the types of product definition information required for each CI to define its performance, functional and physical attributes, and internal and external interfaces. Product definition information provides the basis to develop and procure products, fabricate and assemble items, inspect and test items, and maintain systems; ·determining the configuration management authority for each configuration record; ·issuing identifiers for the CIs, all lower level items and the product configuration information; ·assigning serial and lot numbers as necessary; ·maintaining the configuration identification of CIs to facilitate logistic support of products in service; ·releasing product configuration information; ·establishing configuration baselines for the configuration management of CIs. Specify Configuration begins during the concept stage of the product life cycle with the definition of the product and its product definition information. As the product evolves through its life cycle, configuration identification activities will support the configuration management interrelated processes of configuration change management, configuration status accounting and configuration audit and verification. |
| 06.1.2.1 Specify generic structure | This process identifies the generic structure (product breakdown structure) that you wish to use for a project.
A product breakdown structure is a means for representing the composition of a product in a hierarchical fashion from the top-level product down to the lowest level item . It is an output of the system design process iterated through the various tiers of system decomposition. Each level references product definition information such as user requirements and system specifications, models, drawings, bills of material, software requirements and design records, process specifications and operating procedures. The PBS, which evolves through the life of the programme, shows the interrelationships of the various items that constitute the product and the quantity of each and is only complete when all items and product configuration information is approved and baselined. |
| 06.1.2.2 Define configuration structure | The process "define configuration structure" is where individual configuration items are selected. It is the establishment of a hierarchical Product Breakdown Structure (PBS) as an outcome of the user requirements and system design activity. This PBS is linked to each item's identifier and product definition information
Configuration Items [CI] are the basic unit from which the configuration of a product can be managed. A CI can be an item of hardware or software (or a combination of both), and its product configuration information is designated for Configuration management. Initial CI selection should reflect an optimum management level during the concept and development phase and will typically be the deliverable and separately installable items of the system. During the production and subsequent support phases, individual items required for logistic support and designated for separate procurement may also be designated as CIs. The view of what is designated a CI may depend on where in the contracting tree the view originates |
| 06.1.2.3 Define configuration identifiers | This process addresses the identification of any items and associated records that have been created so that they may be referred to precisely and retrieved when necessary. This activity includes the re-identification of records and items whose identity has changed as a result of update or the application of a change.
Clearly identified information and items are essential for effective CM throughout the product life cycle, particularly during the in-service support phase when the item identifier is key to installing a correct replacement item and satisfying the relevant operation and maintenance instructions. A record identifier, a revision identifier and a date clearly identifies a specific issue of a record. A record can have many representations in many media, all of which must be under configuration management. Product Definition Information is formatted and identified in accordance with the programme CMP.<br><br>A record is a wider definition that covers documents and documentation in any recording media |
| 06.1.3 Manage Baseline | Implement and verify a change to ensure consistancy with its released Product Configuration Information and the changed product. |
| 06.1.3.1 Establish / Update baseline | This process establishes a baseline for the product configuration.
A baseline identifies an agreed description of the attributes of a product at a point in time and provides a known configuration to which changes are addressed. The concept of defining and applying baselines to a product as a means of exercising management is not unique. For example, for a programme to be managed an understanding of the planned cost and schedule ; a baseline plan ; is required to form the reference for subsequent achievement monitoring. Similarly, in order to define and implement a development or a modification to a product, a reference product definition against which that development can proceed, or modification can be defined, is required. A Configuration baseline is a snapshot of an item's configuration at a point in time. More specifically, it is a fixed reference configuration established by defining and recording the approved Product Configuration Information (PCI) describing the object of interest at a point in time. While it is theoretically possible to establish a baseline for a component at any level of a PBS, it is rare, and indeed in the CM sense there is seldom any value, in establishing a formal configuration baseline for an object below the level of CI.In a system development, configuration baselines may be established hierarchically as the Product Breakdown Structure [PBS] evolves. For example, the Allocated Base Line [ABL] at the highest system level may be interpreted as a series of Functional Base Lines [FBL] for each constituent system-level CI; some or more of these CIs will, in turn have an individual ABL which may define a series of FBLs for next-tier CI products. The CMP must be continually reviewed to reflect the evolving PBS over the life cycle of a product. The above baselines represent an example of reference points that will provide a known configuration to which changes are addressed; once established, they remain under configuration management throughout the product life cycle. Within the development phase of the product life cycle a series of ;Design; reviews are undertaken. Each of these design reviews creates a baseline of approved product definition information. These baselines are referred to as ;Development; Baselines (DBL) and remain relevant and under configuration management for only so long as the reason for their establishment remain. |
| 06.1.3.2 Release baseline | This process authoirses draft baselines and relaeses them.
Configuration Baselines released during the product life cycle, the products comprising them and the product configuration information describing them shall be recorded in accordance with the programme CMP. |
| 06.1.4 Perform Configuration Verification | Audit Configuration is the CM Interrelated process that establishs that the performance and functional requirements defined in the product configuration information have been achieved by the design and that the design has been accurately recorded in the product configuration information.
The process: .ensures that the product design provides the recorded performance capabilities; ·verifies the consistency between a product and its product configuration information; ·determines that an adequate process is in place to provide continuing management of the configuration. Successful completion of verification and audit activities results in verified CIs and a product configuration information set that may be confidently considered a Product Baseline. It also results in a validated process to maintain the continuing consistency of product with its product configuration information. Verification is a continuous activity embedded in quality control, development, testing, manufacturing, modification and maintenance processes. Audit represents an explicit event: it is a final, comprehensive check of a design including examination of recorded outputs from the verification process. The more confidence the customer has in the contractor's configuration verification process, the easier the audit process becomes. |
| 06.1.4.1 Scope configuration Verification | This process verifies that a product&aposs attributes have been met and the product design meeting those attributes has been accurately recorded, in order to baseline the product configuration information.
Configuration Verification establishes that the performance and functional requirements defined in the product configuration information have been achieved by the design and that the design has been accurately recorded in the product configuration information). The process: ensures that the product design provides the recorded performance capabilities; verifies the consistency between a product and its Product Configuration Information; determines that an adequate process is in place to provide continuing management of the configuration. |
| 06.1.4.2 Plan configuration Verification | Action to develop a plan for the tasks required to validate, verify or audit a change.
Such plans should be based on the decision taken concerning the introduction point and effectivity of the change. It will cover both production embodiment and retrospective embodiment, before or after the delivery of the product as appropriate. An approved change is planned and scheduled for implementation in all documents, facilities, hardware and software impacted change. The implementation is carried out in accordance with the plan. Implementation of a change involves the release of new or revised configuration documentation including requirements and design information. The implementation may involve changes to operation and maintenance information, build and test information, and sales information (such as catalogues, marketing literature). The new or revised information is identified and released as PCI. The release process should correlate the document revisions to the change or changes incorporated. A common method of disseminating document change is by means of document change notices, which establish a permanent record of specific changes and facilitates distribution. |
| 06.1.4.3 Execute configuration Verification | This process executes the verification activities specified by the verification plan in accordance with programme procedures detailed in the CMP NOTE - Once the initial configuration of a CI or system has been verified, changes to that configuration must be authorised through the configuration change management process.If the change is being introduced to a production line and all future products will have the change incorporated via the production process, it is sufficient to ensure that: manufacturing instructions contain the change and are released for use; the first articles produced are inspected for compliance (First Article Verification ; FAV). If support processes are impacted or the change requires retrofit,implementation and verification of the change can be a lengthy process. Implementation planning will define the extent to which the change to each item and support process is to be verified and recorded |
| 06.1.4.4 Evaluate configuration Verification | This process consists of evaluating an verification and creating an verification report from the findings |
| 06.1.5 Perform Configuration Audit | This process defines the execution of an audit - the act of undertaking the audit activity |
| 06.1.5.1 Scope configuration audit | This activity establishes the scope of the information set that is to be audited.
Configuration audits provide the framework for verifying that the development effort has achieved the requirements specified in the configuration baselines. It is the auditing activity that has the responsibility to ensure that all action items are identified, addressed and resolved before the design activity can be deemed to have fulfilled the requirements. |
| 06.1.5.2 Plan configuration audit | This process establishes the schedule, agenda, facilities, and the rules for audit conduct and identifies the participants for the audit Action to develop a plan for the tasks required to validate, verify or audit a change.
Such plans should be based on the decision taken concerning the introduction point and effectivity of the change. It will cover both production embodiment and retrospective embodiment, before or after the delivery of the product as appropriate. An approved change is planned and scheduled for implementation in all documents, facilities, hardware and software impacted change. The implementation is carried out in accordance with the plan. Implementation of a change involves the release of new or revised configuration documentation including requirements and design information. The implementation may involve changes to operation and maintenance information, build and test information, and sales information (such as catalogues, marketing literature). The new or revised information is identified and released as PCI. The release process should correlate the document revisions to the change or changes incorporated. A common method of disseminating document change is by means of document change notices, which establish a permanent record of specific changes and facilitates distribution. |
| 06.1.5.3 Execute configuration audit | This process defines the execution of an audit - the act of undertaking the audit activity NOTE - The audit team record discrepancies or anomalies and recommend courses of action. The Chairperson reviews audit findings and determines appropriate actions. Affected parties agree to action items and the plan for effecting their closure. Audit minutes provide a record of auditfindings, conclusions and recommendations and action items. Follow-up occurs until all action items are complete. |
| 06.1.5.4 Evaluate configuration audit | This process consists of evaluating an audit and creating an audit report from the findongs.
It establishes the courses of actions required to follow-up and close down the audit actions. NOTE - Once an audit has been performed and follow-up actions have been agreed it is necessary to evaluate the audit results. The audit team will report on the execution of the audit and provide where necessary a "lessons learned" report for the benefit of future audits. audit feedback -A post audit process in which systematic follow-up of the audit action items takes place. NOTE - establishes the courses of actions required to follow-up and close down the audit actions. |
| 06.2 Manage Configuration Change | Manage change is the CM interrelated process that addresses the systematic proposal, justification, evaluation, co-ordination and disposition of proposed changes, and the implementation and verification of all authorised changes into the applicable configurations of a product and associated product configuration information.
The purpose and benefits of the Configuration Change Management process are to: ·enable change decisions to be based on knowledge of complete change impact; ·limit changes to those that are necessary or offer significant benefit; ·facilitate evaluation of cost, savings and trade-offs; ·ensure customer interests are considered; |
| 06.2.1 Administer Change | This process organizes the product configuration information and makes it available, as required, to support all programme activities such as systems engineering, manufacturing, hardware and software development and production, logistic support, modification, and disposal |
| 06.2.2 Evaluate Change | The review of the preliminary impact assessment, determination of the required change effectiveness, the cost / price assessment and the approval, rejection or deferral for more research of the change, together with reasons for the decision. |
| 06.2.2.1 Perform preliminary assessment | Carry out a preliminary assessment of the impact of the change.
The sponsor of the change is the person who has the authority to initiate the assessement of the proposed changes. This is usually the individual with responsibility for the affected product(s) and may be the originator. In consultation with the originator, the sponsor analyses the issue for merit on the basis of its nature and likely impact. This can be a fairly informal and intuitive process, but it often requires careful weighing of alternatives and cost benefit trade-offs. If the issue appears to be unwarranted, it can be closed, with a brief description of the reason for rejection recorded. |
| 06.2.2.2 Perform impact assessment | Action to determine those configuration items that will be affected by the possible solutions. |
| 06.2.3 Authorise Change | Action to establish the business case for change, select a preferred solution and authorize the change by approval of appropriate change orders to enable the change to be implemented and verified |
| 06.2.3.1 Assess solution option risks | Action to assess the risks associated with a quantified solution to a valid need for change |
| 06.2.3.2 Cost solution option | Action to evaluate the cost of a change by subjecting the most beneficial solution to a commercial pricing exercise, creating a price that meets the implementation and effectivity requirements |
| 06.2.3.3 Compile business justification | Action to review the total change package and complete a justification for the implementation requirements with a recommended classification and priority. |
| 06.2.3.4 Authorise change to be designed | Action to establish the business case for design change, selection of a preferred solution (if appropriate) and authorisation the design to be changed and verified. |
| 06.2.3.5 Authorise change to be implemented | Authorization, rejection or deferrment of a recommended change based on the associated justification.
If the change is authorized a change order will be issued for implementation. If the change is rejected a further review can be initiated. |
| 07. Event | Any occurence outside predetermined parameters, or requirement to update the parameters. Use of 'event' in this model also covers 'Exceptions' |
| 07.1 Event Management | Manages events to resolution and provides a customer help desk interface. |
| 08. Training | The updating of human resource skill sets, by the identification, planning, delivering and monitoring of courses to enable the operation and support solution activities related to a specific product. |
| 08.1 Identify Training | To conduct a training needs analysis in order to define the requirement |
| 08.2 Plan Training | Schedules the training in accordance with resource availability and operational priorities. |
| 08.3 Monitor Training | Analysing the performance of the courses, identifying any improvements required and feeding back Lessons identified. |
| 08.4 Deliver training | The running of the training courses. |
| 08.5 Create training capability | The creation of new training capability. This will include some or all the aspects of training capablity from course materials, course design up to the creation of a training facility. |
| 09. Engineering | The analysis and redesign of an asset and support solution based on performance and event feedback to maintain the desired capability. |
| 09.1 Design Product | The production, integration, testing, certification and acceptance of the design or redesign of a physical product. |
| 09.1.1 Design Physical Product | The production of the design and / or re-design of physical products. |
| 09.1.2 Integrate & Test Product | This function covers the physical and functional integration of the design. Also manages the tests and trials required to prove the design. |
| 09.1.3 Qualification & Certification | This function is responsible for managing the qualification & certification of a design |
| 09.1.4 Acceptance | The function of proving that the design is fit for purpose by involving the end user in acceptance trials. |
| 09.2 Design Support Solution | Analyse the supportability of the design and / or re-design and influences the design. Once the design is finalised the optimised Support Solution will be derived looking at all elements required e.g. Training, Tech Pubs, Maintenance, facilities, tools etc |
| 09.3 Design Intent | Activity to ensure that the design objectives are reached / maintained efficiently by the asset. Including analysis (DRACAS), performance and authorisation of all events (Concession, limitations, faults, obsolescence etc) that impacts conformance to the design. |
| 09.4 Manage Safety | This function manages the safety of a product by analysis of design, the support (including training and current material state (technical integrity) of the product |
| 09.5 Manage Environment | This function manages the environmental aspects of a product by analysis of design, the support (including training and current material state (technical integrity) of the product |
| 10 Supply | |
| 10.1 Plan Supply Capability | This function is responsible for planning supply capability in its entirety. It plans how the supply solution will support all items in or planned to be in service. |
| 10.1.1 Develop long term supply plan | This function takes a longer term view of business objectives and support solutions and determines the supply capability will support those plans though life. |
| 10.1.2 Plan core supply capability | This function takes the through life plans and plans the resources required to carry out supply operations. |
| 10.1.3 Plan supply operations | This function plans the operation of supply capability. |
| 10.2 Manage Inventory | This function manages the various groups of items. It carries out a number of key functions including: forecasting, provisioning and disposal. It also manages the static data in the catalogue. |
| 10.2.1 Develop inventory policy | This function sets the rules on ownership and management of inventory items to ensure optimum levels are achieved within constraints. |
| 10.2.2 Forecast demand | This function forecasts the future requirements for and/or predicted consumption of items. |
| 10.2.3 Control Inventory | This function continually manages the quantity and quality of the inventory. |
| 10.2.3.1 Manage Initial Provision | This function identifies the initial requirement for items to be distributed into the support structure to support an equipment in service before regular replenishment can occur. |
| 10.2.3.2 Manage Replenishment | This function addresses the immediate and planned requirement to satisfy materiel needs. It decides the balance between making new, repairing or moving items in order to optimise costs whilst meeting required service levels. The function monitors progress within a replenishment activity. |
| 10.2.3.3 Manage Disposal | This function plans the disposal of items confirmed as being no longer required in the inventory. |
| 10.2.3.4 Manage Obsolescence | This function manages the replacement of one item with another when any of the fit, form or function attributes is to change. Obsolescence may be caused through changes in function required, new technology, legislation etc. |
| 10.2.3.5 Manage Supersession | This function manages the replacement of one item with another with the same fit, form and function. |
| 10.2.3.6 Manage bans, constraints and concessions | This function details actions pertaining to restrictions on the issue of items and their specific use. |
| 10.2.5 Define inventory | This function decides the items and quantities of item in the inventory. It encompasses an optiization activity. |
| 10.2.5.1 Range Inventory | This function considers policy, plans, product details and derives the range of items for the inventory. |
| 10.2.5.2 Scale Inventory | This function considers policy, plans, targets, product details, distribution and derives the scale of items for the inventory. |
| 10.2.5.3 Plan distribution | This function plans the positioning of inventory. It sets stock targets at defined locations in conjunction with expected service levels. This function covers the military activities associated with scaling and entitlement. |
| 10.2.5.4 Review Inventory | This function monitors inventory needs, solutions and management performance and makes recommendation for change. |
| 10.2.5.5 Maintain item catalogue | This function maintains the list of items in the inventory together with item attributes. |
| 10.3 Manage demands and returns | This functions validates and finds solutions for all demand and return requirements. |
| 10.3.1 Find Stock Solution | This function searches for stocks to determine availability, quantity and locations to identify most appropriate solution to meet a valid demand. |
| 10.3.2 Manage Issue | This function confirms items for issue, initiates that issue with an issue order and manages its execution. |
| 10.3.3 Manage Returns | This function confirms items for return, initiates issue order and manages its execution. |
| 10.3.4 Manage Earmarks | The function makes reservations for known future requirements. |
| 10.4 Move items | This function plans, instructs, executes and monitors movements of consignments. |
| 10.4.1 Plan movement | This function takes movement requirements and produces the necessary movement tasks. |
| 10.4.2 Schedule movement | This function schedules consignments to execute the movement plan. |
| 10.4.3 Execute movement | This function takes the schedules and directs the build, despatch, transportation and breakdown of consignments for delivery to the correct destination through various supply nodes. |
| 10.4.4 Track consignments | This function tracks consignments in transit to the point of final delivery. |
| 10.5 Manage Stock Holding Point Activity | This function is concerned with the storage, control and accounting of stock |
| 10.5.1 Receive Items | This function performs the acceptance and receipt of items, checking against inbound consignments, informing the stock system and sending items to storage. |
| 10.5.2 Issue / Transfer Items | This function perfroms the actions required to to issue items held in stock for movement to other locations in performing issue, transfer, and disposal instructions. |
| 10.5.3 Store Items | This function perfroms the action of locating items in the correct stowage. |
| 10.5.4 Dispose of items | This function disposes of items no longer required in accordance with a disposal plan or instruction. |
| 10.5.5 Account for items | This function ensures that the stock system accurately records and reports the physical items held and ensures that accounting practice and policy are adhered to. |
| 10.5.6 Undertake Stocktaking and Census | This function performs a review to compare physical stockholdings with stock records, and carrying out account reconcilliation. |
| 10.5.7 Manage Storage Hierarchy / Floorplan | This function performs the detail planning of storage solutions at particular sites and will include issues of capacity, access, floor planning and methods. |
| 10.6 Manage Stored Items | This function manages the location, storage conditions, configuration, lifing and stock maintenance requirements of items in the store. |
| 10.6.1 Manage Packs and Assemblies | This function ensures that requirements to configure and maintain items grouped as packs or as assemblies, and then held in store as such, are met. |
| 10.6.2 Manage Items with Shelf Life | This function manages items that have shelf life. |
| 10.6.3 Manage Reconditioning / Repair Interface | This function manages items that require reconditioning / overhaul. |
| 10.6.4 Develop Storage Policy | This function develops the the policy for the physical storage and handling of items and ensures that regulations are met. |
| 10.7 Manage Supply Performance | This function takes target and actual supply performance data to inform management on overall supply performance to inform planning activites. |
| 10.7.1 Monitor Performance | This function collects required supply management data |
| 10.7.2 Report Performance | This function reports supply performance, in whole or in part, to the enterprise. |
| 10.7.3 Maintain Performance Data | This function is responsible for maintaining performance data content and quality. |
| 11. Maintenance | Maintenance is the inspection, overhaul, repair , rectification, modification, preservation and parts replacement, to ensure that the equipment is kept in a serviceable condition.
It covers all scheduled and non-scheduled events, preventative and non-preventative activities, including repair, servicing, overhaul, upgrade to an item in accordance with direction. |
| 11.1 Plan Maintenance | To plan all maintenance identifiable at that date: Looking at the resource and asset availability and grouping the maintenance logically. Then scheduling the tasks in accordance with operational and maintenance cycle and resource availability. |
| 11.1.1 Scope Maintenance | This function determines all maintenance activities to be performed for a selected scope of assets and planning horizon. Preventative maintenance will be driven by either calender or where it is utilisation based by the reported usage. Other maintenance will included planned modification embodiments, work identified and not completed during previous maintenance periods and corrective maintenance deferred for planning. |
| 11.1.2 Structure Maintenance | This function considers priorities and the logical progression of maintenance tasks and adds a potential sequence to their delivery. |
| 11.1.3 Schedule Maintenance | This function produces the maintenance plan by considering the prioritised task list adds a sequence and date to all tasks allocated to a specific maintenance opportunity, related tasks(incl. triggers), location, materiel availability, resource requirements and resource balancing considerations. |
| 11.2 Execute Maintenance | This function produces short term / resourced work schedules based on the long term maintenance plan, factors in unplanned maintenance requirements and priorities, and controls the production and issue and closure of Maintenance Work Orders. |
| 11.2.1 Allocate Maintenance Task | This function allocates specific assets to particular manitenance activities, applying the requirements of the Maintenance Plan and particular human & infrastructure resources. |
| 11.2.2 Perform Maintenance Task | This function carries out the actual maintenance activity in accordance with a work order and the policies & documentation laid out in the Support Solution. |
| 11.2.3 Close Maintenance Task | This function closes out the maintenance task and provides post maintenance feedback on the asset and the resources comsumed. |
| 11.3 Monitor & Control Maintenance | This function manages the maintenance function performance, reviewing performance against schedules and providing feedback in terms of revised targets. It also initiates corrective action to achieve maintenance targets. |
| 11.3.1 Task Assurance | This activity monitors the quality of tasks executed against quality standards and contractual specifications. |
| 11.3.2 Maintenance Exception Handling | This activity monitors all tasks and actions all delays, defers, non-conformances and emergent work, by re-scheduling where appropriate and obtaining approvals (incl concessions) where required. |
| 11.3.3 Report Maintenance | This activity collate all feedback against tasks, assets and resources/material for a given selection (maintenance opportunity/ asset/ time) and presents the information in a prescribed format. |
| 12. Commercial | This function manages the commercial and contractual negoiations with suppliers and customers including all pre-servicing activity and through life managment of contracts. |
| 12.1 Prepare Commercial Activity | |
| 12.1.1 Review Commercial Requirements | |
| 12.1.2 Aggregate Requirements | Collate and investigate similar requirements to ensure the best VFM approach to market. |
| 12.1.3 Establish Cost Drivers | Conduct cost and price analysis |
| 12.1.4 Develop Specification | |
| 12.2 Conduct Sourcing | |
| 12.2.01 Review extant arrangements | Establish whether the requirement can be met by existing arrangements |
| 12.2.02 Analyse Markets | |
| 12.2.03 Analyse Suppliers | |
| 12.2.04 Develop Sourcing Strategy | Establish which suppliers to involve for global requirements, type of arrangements, etc. |
| 12.2.05 Select Sourcing Option and Suppliers | Conduct and investment appraisal, risk analysis, etc |
| 12.2.06 Execute approval | Approval for PS to proceed |
| 12.2.07 Advertise requirement | |
| 12.2.08 Complete acquisition strategy | Determine the type of contracting arrangement and likely suppliers for specific requirements within sourcing strategy and determine payment method. |
| 12.2.09 Process expressions of interest | |
| 12.2.10 Process ITT/ITN | Process Invitations to tender/negotiate. |
| 12.2.11 Receive and Assess responses | Prepare for assessment and conduct assessment including any clarifcation questions. |
| 12.2.12 Award Contract | |
| 12.2.13 Debrief Supplier | |
| 12.2.14 Notify and Conduct Internal Debrief | |
| 12.3 Manage Contract and Evaluate | |
| 12.3.1 Compile and agree contract | Establish T&Cs etc, negotiate, award contract and sign final notification. |
| 12.3.2 Distribute and register contract details | e.g. D57, DBA |
| 12.3.3 Review contract performance | |
| 12.3.4 Manage compliance and remedies | |
| 12.3.5 Amend or terminate contract | |
| 12.4 Close Contract | |
| 12.4.1 Manage contract closure | |
| 12.4.2 Archive contract information | |
| 12.4.3 Conduct post-project costing | |
| 12.4.4 Conduct post project evaluation | |
| 12.5 Manage Contract Information | |
| 12.5.1 Assemble intelligence about MOD customer and performance | |
| 12.5.2 Assemble intelligence about supplier and performance | |
| 12.5.3 Derive purchasing trends | |
| 12.5.4 Manage queries | |
| 12.5.5 Predict future requirements | Using historical purchasing, invoice and MS data, predict future requirements. |
| 13. Resources | The collection of functions that manage the human and infrastructure resource. (eg people, tools, buildings and IT etc) |
| 13.1 Human Resource Management | This function is responsible for the management of human resources including recruitment, dismissal, pay, placement, career and skills development. |
| 13.2 Infrastructure Resource Management | This function is responsible for ensuring that the infrastructure e.g. facilities and IT is sufficient, both in quantity and state, to meet planned requirements |
| 14. Corporate Policy and Procedures | This function manages the corporate impact of legislation and other policy impacts |
| 14.1 Corporate Governance | This function manages the impact of corporate governance and environmental policy and legislation |
| 14.2 Security | This function controls the corporate and technical secuirty policy |
| 14.3 Health, Safety and Environment | This function carries out corpoate and techincal regulation activites in connection with Health and safety legislation and policy |
| 14.4 Quality Management | This function provides the quality management |
| 14.5 Information Management | This function governs the overall approach to information management including legislative requirement under FOI etc |
| 15. Manufacture / Source | This function is responsible for the initial manufacture or sourcing of items (including complete platforms and modification kits) |
| 16. Performance and Risk | The sets of activities that conducts performance monitoring against a defined set of metrics, models and analyses business performance and manages risk |
| 16.1 Metric Identification | The function of transforming objectives to define specific measurable criteria that are used to indicate progress or achievement against a given target. |
| 16.2 Performance Monitoring | The function of monitoring the performance of the system and risks to the system. Provides data on which business modelling and analysis can be carried out. |
| 16.3 Business Modelling and Analysis | The function of modelling and analysing the business data to identify and report on trends, risks, mitigation and change recommendations. |
| 16.4 Risk Management | |
| 17. Finance | This function manages the internal and external financial transactions of the business including budget, STPs, accruals, commitments etc. |
| 17.1 Planning budgeting and forecasting | |
| 17.2 Manage budgets in-year | |
| 17.3 Conduct financial approval | |
| 17.4 Financial Accounting | |
| 17.5 Execute Payment | |
| 18. Strategy and Planning | The source of higher level governance, policy and guidance to ensure a desired outcome. |
| 18.1 Business Strategy | This function determines the strategic direction that the business will take, including operational and mission intent, determining the Objectives, Key Performance Indicators and Critical Success Factors that will ensure success. |
| 18.2 Business Planning | This function determines the business plans based upon the strategic direction of the business. |
| 18.3 Stakeholder Management | This function manages communications with the business stakeholders, including customers. |
| 19. Purchasing | The set of activities that takes a valid request to buy through approvals and order to the authorisation of an invoice payment. |
| 19.1 Request to Buy | A request to buy off a contract or without a contract; includes tasking of existing contracts and RFQ off existing arrangements. |
| 19.1.1 Validate Purchasing Need | |
| 19.1.2 Consolidate Purchasing Needs | |
| 19.1.3 Check for Suitable Existing Contract / Quote | |
| 19.2 Approval to Purchase | Includes already provided, financial approval, scrutiny, technical and commercial approval |
| 19.2.1 Determine Approval Levels | |
| 19.2.2 Grant / Deny Approval to Purchase | |
| 19.3 Order | Create and issue the order to the supplier |
| 19.3.1 Compile Order | |
| 19.3.2 Send Order | |
| 19.3.3 Progress Order | |
| 19.4 Invoice Approval | |
| 19.4.1 Validate Invoice | |
| BUSINESS SUPPORT | |
| CONFIGURE | |
| DELIVER LOGISTIC SUPPORT | |
| ENGINEER | |
| ENTERPRISE | |
| EVENT | |
| FLEET AND ASSET | |
| MAINTAIN | |
| MISSION / OPERATE | |
| SUPPLY | |
| TRAINING |
LCIA
AAC990BDC6A14E59B80636B2BE28B9EC
738A662ECAD145519E79B128C1B28D29
Inputs
-
Accept Movement Schedule
-
Acceptance against Contract
-
Accounting Policy
-
Acquisition Instruction
-
Acquisition Strategy
-
Actual Maintenance Costs
-
Actual Performance Data
-
Advance Notice to Supplier of Item for Repair
-
Advance shipment notice
-
Agreement to Proceed
-
Analysed Efficiency and Effectiveness Data
-
Approval level details
-
Approval to Develop a Design Change
-
Approval to Release Design
-
Approved purchase request notice
-
Assembly Details
-
Asset Assignment Details
-
Asset Capability Upgrades Required
-
Asset Change Embodiment Schedule
-
Asset Condition
-
Asset Conditions of Use
-
Asset Current Configuration
-
Asset Current Location
-
Asset Details
-
Asset Disposal Plan
-
Asset First Use Date
-
Asset Fitment Details
-
Asset historical availability
-
Asset Identifier(s)
-
Asset Limitations
-
Asset Mod State
-
Asset Permissable Configuration
-
Asset Release
-
Asset Remaining Life
-
Asset Status
-
Asset Suitable
-
Asset Support Policy
-
Asset Sustainment Operation Request
-
Asset Training Operation Request
-
Asset Transfer Requirement
-
Asset Type Required
-
Asset Upgrade Plan
-
Asset Usage Data
-
Asset Utilisation
-
Assets available for assignment
-
Audit Evaluation
-
Audit Result
-
Audit Scope
-
Authority to Commit Funds
-
Authority to develop a support solution design change
-
Authority to Implement Change
-
Authority to Implement Design
-
Authority to Order
-
Authority to Pay
-
Authority to Use Asset
-
Authority to Use Design
-
Availability of Qualified Personnel
-
Bans and constraints
-
Baseline Disposal Confirmation
-
Batch Detail
-
Budget
-
Budget Forecast
-
Business Improvement Recommendations
-
Business Objectives
-
Business Rules
-
Cannibalisation Instruction
-
Cannot approve invoice notice
-
Cannot approve purchase request notice
-
Cannot Purchase Item Notice