When reviewing support activities, the PM and PSM should work with manpower and functional representatives to identify process improvements, design options or other initiatives to reduce manpower requirements, improve the efficiency or effectiveness of support services or enhance the cross-functional integration of support activities. The cumulative effects of systems-of-systems, families-of-systems and related systems integration should be considered when developing manpower requirements. Tasks and workload for individual systems, systems-of-systems and families-of-systems should be reviewed together to identify commonalities, merge operations and avoid duplication. Additionally, manpower requirements should be calculated in conjunction with personnel capabilities, training and human factors engineering trade-offs. Manpower requirements should be based on task analyses, which consider all factors, including fatigue cognitive, physical and sensory overload, and environmental conditions (e.g., heat/cold) and reduced visibility. Based on a top-down functional analysis, an assessment should be conducted to determine which functions should be automated, eliminated, consolidated or simplified to keep the manpower numbers within constraints.
#PHONE NUMBER TO MANPOWER SOFTWARE#
These tasks can sometimes be eliminated during engineering design by increasing equipment or software performance.
Moreover, these high-driver tasks might result from hardware design or hardware/software interface design problems. When assessing manpower, system designers should examine labor-intensive, “high-driver” tasks. If sufficient end strength is not available, a request for an increase in authorizations should be submitted and approved as part of the trade-off process. These manpower determinations should be based on current workforce mix instruction found in DoDI 1100.22, Policy and Procedures for Determining Workforce Mix. Critical manpower constraints should be identified in the Departments' capability documents to ensure that manpower requirements remain within DoD Component end-strength constraints. This assessment shall determine whether the new system requires a higher, lower or equal number of personnel than the predecessor system, and whether the distribution of ranks/grades will change. The PM/PSM should evaluate the manpower required and/or available to support a new system, and consider manpower constraints when establishing contract specifications to ensure that the human resource demands of the system do not exceed the projected supply. If appropriate, manpower goals and parameters shall be established to ensure programs do not exceed what the Component is able to invest for operating, maintaining, and supporting the system."
Mobilization planning shall include all activities necessary to enable time-phased, scenario-specific mobilization. "A formal validated process shall be used to determine mobilization, contingency, and wartime manpower requirements.Changes in manpower shall be preceded by changes to the programs, missions, and functions that require manpower resources." "Manpower requirements are driven by workload and shall be established at the minimum levels necessary to accomplish mission and performance objectives.DoD Instruction (DoDI) 5000.91, Product Support Management for the Adaptive Acquistion Framework (AAF), requires the PM, with the support of the Product Support Manager (PSM), to "work with the cross-functional team to conduct a thorough analysis using analytical tools and modeling techniques to facilitate informed decisions on supply support, manpower, training, maintenance and maintenance planning, and other IPS elements." (Note: bold text added for emphasis.)Īdditional advice is provided in DoDI 1100.4, Guidance for Manpower Management, which states that:
0 kommentar(er)
