Chapter-4
4.1 MANPRINT Management
The Department of Defense (DoD) recognizes the critical importance of management control. Rigorous internal management control systems are integral to effective and accountable program management. The objective is to perform acquisition functions efficiently and effectively while maximizing the utilization and protection of resources. Previously, a System MANPRINT Management Plan (SMMP) was required for all systems. It was developed by a MANPRINT Joint Working Group (MJWG) early in the systems acquisition process (prior to Milestone I) and maintained as a living MANPRINT management tool throughout the system’s life-cycle. It was initially primarily the responsibility of the Combat Developer or Functional Proponent and was turned over to the Program Manager when appointed. The SMMP is still highly desirable as a MANPRINT management control system. ARL-HRED, as the focal point for the MANPRINT effort on all systems, has the responsibility for developing guidance on coordination and communication between ARL-HRED and the MANPRINT team. Department of Defense Regulation Number 5000.2R requires that a comprehensive management and technical strategy for human systems integration be initiated early in the acquisition process. It should be noted that the Defense Acquisition Deskbook recommends that the PM develop a Human Systems Integration Plan (HSIP) when the system has complex human-systems interfaces; significant manpower or training costs; personnel concerns; or safety, health hazard, or survivability issues. The SMMP equates to a HSIP. The SMMP, if developed, can and should be tailored to fit the system.
4.2 System MANPRINT Management Plan (SMMP)
A recommended SMMP format that with minimum essential information contains:
System Information: This might include a brief system description and acquisition strategy.
Target Audience: As a minimum, identify the operators, maintainers, and supporters of the system. Highlight any significant changes from the predecessor system. If there is no predecessor system that will be replaced, identify the billpayers for the system.
Issues: The ICT Report will contain MANPRINT Common Data Elements (CDEs). This is a start point for continuous identification and resolution of issues. The CDE format is:
Each MANPRINT issue or opportunity
The impact of that issue or opportunity
What has been done
Potential solution(s) that have not been attempted
Proponent Agency
As issues are resolved, data on MANPRINT costs (analyses, support) and benefit (cost savings and cost avoidance) should be captured.
Coordination: Capture POCs for the system and MANPRINT POCs supporting the system.
4.3 MANPRINT Crosswalks
In TRADOC Pamphlet 71-9, there is a specific process to crosswalk requirements in the Operational Requirements Document (ORD) to the Request for Proposal (RFP) and the process must be documented (see Figure 4-1). The requirements of the ORD should also provide the basis for testing issues in the Test and Evaluation Master Plan (TEMP). MANPRINT AOs must ensure this process is used to manage MANPRINT requirements, objectives, and thresholds. When a specific MANPRINT requirement, objective, or threshold is not addressed, it should be brought to the attention of the combat developer and materiel developer. MANPRINT requirements should also be crosswalked to the Supportability Strategy.
Figure 4.1— ORD to RFP Crosswalk
|
|
Copyright © 1998,
1999 U.S. Army. |
