Previous PageTable Of ContentsNext Page


G2.0  FROM DEFENSE SYSTEM TO THE ARMED FORCE


G2.1  Requirement
For changes to facilities (Request)
For additional Training e.g., new common skill requirements (Request)
Change request for other DS (Request)


G2.2  Design
Proposed change to AF design constraints or standards (Request)
Common parts used in this system * (not yet covered by TLBM. Needs a two way flow)
Identify Alternate Parts - is this in use elsewhere with different id.* (Being explored with AC135. The set of info needed to perform form, fit, and function comparison)


G2.3  Interface Details for Other Systems (DS Data)


G2.4  Support Design
Proposed changes to AF maintenance policy- harmonization of approach. (Request, plus DS Data).
Potential new common tools and equipment* (DS data).

Note: Provisioning of some parts may not be managed through life by the DS Life-cycle Owner (LCO). If parts management is an AF activity, the following interactions will occur with AF stock management agency.
Provisioning recommendations including re-procurement details.* (DS data)
Packaging Handling Storage and Transportation requirements * (DS data)


G2.5  Support
If maintenance is provided primarily on a single DS basis, support activities are assumed to lie within the TLBM, under LCO control, and using the DS program SDE. If maintenance activities have to be integrated across several DS, beyond LCO control, either for reasons of work planning (e.g., a Brigade workshop, NAMSA) or access and availability reasons (e.g., ships, aircraft) then the following interactions occur:

DS Support and Maintenance Instructions/ Plans*
Ad hoc work requirements *.
System changes required/permitted.* (Selected Configuration)
Details of resources to be provided by PM (Not covered)
System Ready for use (DS ready for use)

Operate
Operating instructions* (DS data - where from?)
Operational support requirements - interfaces, services needed* (DS Data from Obtain)

 

Previous PageTop Of PageNext Page