4.4 HSI in the System Development and Demonstration Phase
Overview
The purpose of the Production and Deployment phase is to achieve an operational capability that satisfies mission needs. Once maturity has been proven, the system or block is baselined, and a methodical and synchronized deployment plan is implemented to all applicable locations. A system must be demonstrated before the DoD will commit to production (or procurement) and deployment. For DOT&E Oversight programs, a system can not be produced at full-rate until a Beyond Low-Rate Initial Production Report has been completed and sent to Congress, the Secretary of Defense, and the USD(AT&L). The MDA shall make the commitment decision at Milestone C. Milestone C can be reached directly from pre-systems acquisition (e.g., a commercial product) or from System Development and Demonstration phase.
Regardless of the entry point, approval at Milestone C is dependent on the following criteria being met:
Milestone C. The purpose of this milestone is to authorize entry into low-rate initial production (for MDAPs and major systems), into production or procurement (for non-major systems that do not require low-rate production) or into limited deployment for MAIS or software-intensive systems with no production components.
Evolutionary Acquisition. According to DoD 5000.1, in order to ensure that the Defense Acquisition System provides useful military capability to the operational user as rapidly as possible, evolutionary acquisition strategies shall be the preferred approach to satisfying operational needs. Evolutionary acquisition strategies define, develop, and produce/deploy an initial, militarily useful capability ("Block I") based on proven technology, time-phased requirements, projected threat assessments, and demonstrated manufacturing capabilities, and plan for subsequent development and production/deployment of increments beyond the initial capability over time (Blocks II, III, and beyond). The scope, performance capabilities, and timing of subsequent increments shall be based on continuous communications among the requirements, acquisition, intelligence, and budget communities. In planning evolutionary acquisition strategies, program managers shall strike an appropriate balance among key factors, including the urgency of the operational requirement; the maturity of critical technologies; and the interoperability, supportability, and affordability of alternative acquisition solutions. To facilitate evolutionary acquisition, program managers shall use appropriate enabling tools, including a modular open systems approach to ensure access to the latest technologies and products, and facilitate affordable and supportable modernization of fielded assets. Sustainment strategies must evolve and be refined throughout the life cycle, particularly during development of subsequent blocks in an evolutionary strategy.
Overview of Production and Deployment Phase HSI Activities
The HSI process for Production and Deployment is depicted above. The steps associated with this process are described in the following sections.
Substeps/Activities/Guidelines
Step 16. Prepare Equipment Installation Criteria
Overview:
Installation criteria will be developed based on operator and maintainer access requirements, safety considerations, and task analysis results. Mockups and scale models of equipment installations will be developed to verify accessibility, operability and maintainability. Lessons learned from predecessor systems will be examined to identify problems with equipment installation.
Relationship to SHAP:
The engineering process for military systems of the future must include a commitment to total quality in the installation of the system into its intended environment. Quality is a characteristic of a system which demands that the development process be efficient, that the system products be affordable, reliable, durable and usable, and that the system meets appropriate quality standards. A commitment to quality involves a dedication to ensuring that systems will be able to meet the challenges of warfare in the 21st century. Systems will meet quality standards to the extent that they are usable, durable, effective, affordable, and safe. The HSI aspects of these systems is important to the extent that successful system operation depends on human performance, and that its quality depends on ease and safety of its use.
DoD 5900.2 includes policies and procedures which establish the basis for quality management activities which will result in the delivery of operational systems that satisfy the user's requirements under all anticipated deployment and operating conditions.In these systems quality shall be integrated throughout all elements and activities of a program. Quality efforts in the system engineering process must focus on three interconnected sub-efforts: a) Quality of Design - The effectiveness of the design process in capturing the operational requirements and translating them into detailed design requirements that can be manufactured (or coded) in a consistent manner; b) Quality of Conformance - The effectiveness of the design and manufacturing functions in executing the product manufacturing requirements and process specifications while meeting tolerances, process control limits, and target yields for a give product group c) Fitness for Use - The effectiveness of the design, manufacturing, and support processes in delivering a system that meets the operational requirements under all anticipated operational conditions.
The quality effort will be integrated into the system engineering effort by establishing design control processess to ensure that the engineering process properly captures all of the operational requirements, and efficiently translates them into detailed design requirements. Critical design options should be identified by the end of Phase I, Demonstration and Validation. Quality engineering tools will be applied to these critical options to maximize the system design's capability of meeting design objectives. During development of the system, subsystem critical functions will be identified. Special quality emphasis will be applied to these items, especially to those functions crucial to personnel safety or flight safety, environmental protection, and prevention of system loss or damage. During development of the system, manufacturing critical processess will be identified. The quality emphasis during Phase II, Contract Design, and Phase III, Detail Design, will be on preventing product deficiencies, rather than detecting and correcting defects. For products planned for rate production, an effective manufacturing in-process control system will be established and used. All DoD Components are to establish a product deficiency reporting and correction system to provide feedback to the system developer to track and record the status of the operational quality condition of the system.
Inputs: Installation requirements and constraints
Outputs: Assessments of installations based on HSI criteria
16.1 Identify equipment installation requirements
16.1.1 Identify Location Requirements
16.1.1.1 Identify space layout for equipment installation
16.1.1.2 Identify location constraints
16.1.1.3 Identify alternate locations
16.1.2 Identify equipment configuration requirements
16.1.2.1 Identify spatial configuration of the equipment in the space
16.1.2.2 Identify the range of configurations
16.1.2.3 Identify requirements for configuration changes
16.1.2.4 Identify dimensions associated with each configuration
16.1.3 Identify operation & maintenance requirements
16.1.3.1 Identify operations tasks to be conducted in the space
16.1.3.2 Identify requirements associated with operations tasks to be conducted in the space with the equipment
16.1.3.3 Identify requirements associated with operations tasks to be conducted in the space in proximity to the equipment
16.1.3.4 Identify operational modes
16.1.3.5 Identify free volume requirements associated with operations tasks
16.1.3.6 Identify time constraints associated with operations tasks
16.1.3.7 Identify operations conditions to include the following:
16.1.3.8 Identify maintenance tasks to be conducted in the space
16.1.3.9 Identify requirements associated with maintenance tasks to be conducted in the space with the equipment
16.1.3.10 Identify requirements associated with maintenance tasks to be conducted in the space in proximity to the equipment
16.1.3.11 Identify maintenance modes
16.1.3.12 Identify free volume requirements associated with maintenance tasks
16.1.3.13 Identify time constraints associated with maintenance tasks
16.1.3.14 Identify maintenance conditions to include the following:
16.1.4 Identify access/egress requirements - The objective of this effort is to identify access/egress design requirements based on requirements and human engineering criteria.
16.1.4.1 Identify access/egress design specifications - This activity is concerned with identifying criteria and design specifications already in place governing requirements for access/egress use and design. Primary sources of data will include human engineering criteria from standards such as MIL- STD 1382D and design specifications and criteria for access/egress from other sources. Data will be of two types: those governing the design dimensions and characteristics of access/egress provisions; and those governing the use and operation of these provisions.
16.1.4.2 Acquire data on existing and planned access/egress provisions - Data on existing and planned access/egress provisions will be acquired from three classes of sources: (a) design agents, (b) test and evaluation data bases, and (c) operational data sources. Design data to be collected will include design waivers and deviations as they pertain to access/egress provisions. Design data will also include dimensions and design characteristics of access/egress provisions as installed in existing facilities. Test and evaluation data will include reports on the adequacy of access/egress provisions from human engineering and safety evaluations of existing provisions. Operational data will be acquired from:
16.1.4.3 Prepare lessons learned for existing access/egress provisions - Data acquired on access/egress provisions in existing and planned facilities will be analyzed to identify access/egress lessons learned. Lessons learned data are of three types: 1) problems in the design and/or use of access/egress provisions; 2) positive aspects of provisions; and 3) deficiencies in existing standards and specifications, and in the extent to existing standards and specifications are met. Lessons learned data will be further analyzed to identify the causes for problems, deficiencies in design standards, and situations of non-compliance with standards. Problems and shortcomings will be prioritized in terms of impact on crew safety and survivability.
16.1.5 Identify facility/installation design requirements - The single most important determiner of the design of a manned facility should be the requirements of the facility users, including personnel who will inhabit the facility and who will perform operations, maintenance and support functions within the facility. The end result is often a constructed facility which fails to meet important user requirements and needs but which cannot be modified without considerable additional costs. The ideal situation is to address user requirements and needs early in the design process where human factors engineering considerations can influence facility design at a nominal cost. The steps to be pursued in the identification of facility requirements are as follows:
16.1.5.1 Identification of users - The initial step is to identify facility users by user role. Specific roles include those of inhabiter, operator, maintainer, security guard, clerical worker, computer specialist, supervisor, and material handler. Requirements for performance of jobs will be identified including an identification of duties associated with each job. An estimate will also be made of the percentage of time that specific users, by role and/or job title, are housed within the facility.
16.1.5.2 Identification of facility uses and use conditions - For each user and user role/job, facility uses will be identified. Uses of the facility include duties performed within specific areas of the facility. In addition, use conditions will be identified which will include those situations which will have an impact on the performance of assigned duties, such as emergency conditions, contingency conditions, conditions of high workload, tight time constrained situations, and conditions of minimum manning levels.
16.1.5.3 Identification of user functions by use - User functions will be identified for each duty, facility use and use condition.
16.1.5.4 Identify requirements by function - Requirements associated with specific functions by use conditions will be identified. Requirements will include:
16.1.5.5 Conduct user task analyses - For each user function for each use and under each use condition, user tasks will be identified and analyzed. The task analysis will address such task characteristics as frequency and expected duration of tasks, information needed to perform the task and characteristics of the information, performance requirements associated with the task, decisions required in task performance, and factors associated with the facility design and environment which are expected to impact the safe and effective performance of the task. The task analysis will also identify specific user-equipment and user-facility interfaces associated with the performance of each task.
16.1.5.6 Identify architectural/engineering (AE)constraints - including situations where the design of the user-machine and user-facility interfaces is constrained by structural, engineering or cost factors and where the human factors engineering effort will have to comply with the constraints. These AE constraints will require approval of customer personnel.
16.1.6 Identify safety & health requirements - associated with the proposed installation and the resultant facility design. The process for identifying requirements will address:
16.1.7 Identify environmental requirements for each operations and maintenance task conducted with the installed equipment, to include:
16.1.8 Identify signs/labels/marking requirements . The expected results to be attained from attending to sign, labeling & marking requirements include:
The benefits associated with these results include improved performance, reduced errors and accidents, reduced training time, reduced system acquisition costs (due to standardization of labels), and reduced system life cycle costs (due to reduced training, accidents, and system failures caused by human errors).
The steps to be followed in the identification of signs/label/marking requirements are described in the following sections.
16.1.8.1 Classify signs/labels/marking applications and use conditions. To identify the range of environmental and operational conditions under which the sign/label/marking is to be seen, read and understood.
16.1.8.2 Identify human engineering sign/labeling/marking issues. Sign, labeling and marking issues include the factors associated with the sign, label and marking itself, the message, the environment, and the reader, which have an impact on reader performance. Specific classes of issues include the following:
16.1.8.3 Identify human engineering problems for signs/labeling/marking on existing systems Problems associated with signs, labeling and marking in existing facilities will be identified and analyzed. Sources of data on problems will include interviews with users, review of accident data, and human engineering assessment of samples of existing sign/labeling/marking. The activities associated with this step are listed below.
16.2 Identify Potential Problems with Installation
16.2.1 Identify need to determine potential problems with installations
16.2.2 Identify Lessons Learned from Baseline Systems (see IDEA Step 59.0)
16.2.3 Identify problems from drawings (see IDEA Step 56.0)
16.2.4 Identify problems from mockup walkthroughs - Mockup/model walkthroughs will be used to identify design problems and operational difficulties. The mockups will be full scale representations of the essential attributes of an installation design approach and will be constructed from foam-cor or plywood for ease of construction and modification. Models will be scaled down representations of larger areas depicting the installation concepts in existing arrangements.
16.2.5 Identify problems by comparing installation requirements and facility concepts
16.3 Identify Alternate Solutions to Problems
16.3.1 Conduct Studies to Identify Installation Concepts
16.3.1.1 Develop human factors engineering design requirements and concepts
Design concepts will be developed for user-machine and user-facility interfaces. Concepts will be developed on the basis of human factors requirements and AE constraints as well as on the results of a human factors assessment of a baseline predecessor system . The baseline system will comprise an existing facility in which users perform functions and tasks similar to those proposed for the new Facility, and for which human factors problem areas can be readily identified through user interviews. Concepts will be developed through the conduct of human factors engineering studies of five types:
The human factors engineering concepts to be developed will address the major user-machine and user-facility interface issues. Human factors engineering concepts will either be developed or will reflect an assessment of architectural/engineering design concepts from a human factors engineering point of view. Specific concepts will include the following:
16.3.1.2 Conduct tradeoffs and select optimum concepts - Tradeoffs of human factors engineering concepts will be conducted jointly with AE representatives to select the optimum user-machine and user-facility interface concepts. Tradeoff criteria will include user requirements as well as AE constraints. Tradeoff criteria will be weighted in terms of relative importance for achieving the objectives of the facility, as well as for occupant safety and productivity considerations.
16.3.1.3 Develop human factors engineering design criteria - Design criteria will be developed for each selected user-machine and user-facility interface concept. These design criteria will be derived from human factors engineering studies and from Government and Industry standards.
16.3.1.4 Develop alternate approaches to resolving problems - Alternate solutions to sign, labeling and marking problems include design solutions, training solutions and environmental solutions.
16.3.2 Identify design/redesign solutions - Design solutions include: redesign, relocation, or recoding. Design solutions also involve modifying the sign/label/marking media and/or the message.
16.3.2.1 Select human engineering sign, labeling and marking concepts by application
This step begins with an effort to develop labeling and marking human engineering design concepts by application. Concepts will be based on alternative approaches to resolving identified problems. General approaches and special case approaches will be developed to labeling and marking by application and system. Concepts will be compared through the use of tradeoffs which will assess the adequacy of alternative design concepts in terms of selected tradeoff criteria. On the basis of the tradeoffs, optimal design, training and environmental approaches will be identified for each sign/label/marking application.
16.3.2.2 Develop human engineering design criteria and guidelines for the selected sign/ labeling and marking concepts
Design guidelines and criteria will include design requirements to implement the selected solutions by applications area. These design requirements will be derived from existing standards and handbooks. Where data are not available to support development of design guidelines and criteria, a requirement for additional research and technology development will be identified.
16.3.2.3 Generate cost/benefit ratios for updating existing sign/label/marking schemes to the recommended concepts. Cost/benefit ratios will be developed to support the decisions to proceed with sign/labeling/marking changes. Sign/label/marking improvements having the highest payoffs at lowest cost will be recommended for initial implementation.
16.3.3 Identify Training solutions including alternative approaches to initial, schoolhouse training, as well as on-board training, tutoring, prompting, cueing, or otherwise helping.
16.3.4 Identify environmental solutions which involve modifying the facility environment and the installation of components to support environmental control.
16.3.5 Develop installation concepts
16.3.5.1 Objectives
16.3.5.2 Scope of the effort
16.3.5.3 Expected results
16.3.5.4 Activities
16.4 Identify Evaluation Requirements
16.4.1 Prepare evaluation plan - A plan will be prepared for conducting experimental evaluations of proposed access/egress provision improvements. The experiments will entail acquiring data on the performance of representative crew members in using existing access/egress provisions. Modifications will be made to the existing provisions as dictated by the provision improvement concept under investigation, and data will be collected on crew performance using the improved provisions. The evaluation plan will address improvement concepts to be evaluated, techniques for inexpensively implementing the concept on-board selected ships, and evaluation data to be collected and analyzed.
16.4.2 Identify design evaluation requirements
16.4.2.1 Identify requirements for an HSI design evaluations - Where the HSI program is not concerned with developing user-machine and user-facility interface concepts, the effort will be directed to evaluating the design approaches proposed by the architect/engineer element. The specific substeps involved in the conduct of human factors engineering design evaluations are as follows:
16.4.2.2 Identify System and Facility Representations - In this step system and facility representations will be identified for evaluation. These representations include the products of the system engineering process which are available for evaluation at each stage of development. Specific representations are as follows:
16.4.3 Identify evaluation methods - The principal types of evaluation methods are: analytic methods, empirical methods, comparative measurement methods, observational/walkthrough methods, and subjective methods.
16.4.3.1 Analytic methods include evaluation techniques where the evaluation data are derived through analysis of the compliance of system design features with standards. Analytic methods are most applicable in the early stages of system development, where a physical representation of the system does not yet exist, and the only system representation is in the form of drawings and conceptual analyses. They are also applicable to later stages of system development where application of other evaluation methods is not feasible. An example is the application of error likelihood analysis to qualitatively estimate error potential in system operation where measurement or observation of error occurrence is not possible.
16.4.3.2 Empirical Methods include evaluation techniques which employ applications of experimental methods. These methods can include simulations or controlled studies of specified features of system design. The distinguishing feature of these evaluations is that they involve an experimental setting.
16.4.3.3 Comparative measurement methods involve those evaluation procedures that require measurement of some physical, functional or performance attribute of the system or system personnel and comparison of the data to standards or criteria. Typical methods include environmental effects evaluation, application of design checklists, individual/team performance measurement, and workload assessment.
16.4.3.4 Observational/walkthrough methods include situations where the evaluation requires observation of ongoing activities, or a controlled walkthrough of operational sequences by selected test participants or by the test conductor himself, using mockups of facility areas and workspaces or the actual facility.
16.4.3.5 Subjective methods include evaluation procedures wherein data are obtained from subject matter experts and/or actual facility users by means of interviews, surveys or questionnaires.
16.4.3.6 Alternative methods will be identified, along with guidelines for selecting specific methods as a function of the purpose of the evaluation, specific data requirements, and the applicable phase of the materiel acquisition process.
16.4.4 Identify evaluation conditions
Evaluation conditions are required for some evaluation methods to control the experimental setting and to ensure a high degree of fidelity between the test and the actual situation. Applicable evaluations will select evaluation conditions to be representative or worst-case. Specific types of conditions to be addressed include:
16.4.5 Identify evaluation criteria
Evaluation criteria are the effectiveness factors against which the evaluation data are compared. These criteria can be derived from:
The measurement of human factors engineering effectiveness can only be accomplished in terms of effectiveness criteria. Human factors engineering effectiveness criteria should be explicitly derived from specific objectives of each human factors application.
Criteria are of four basic types:
16.4.6 Identify evaluation measures - Human factors engineering evaluation measures are a direct function of the selected evaluation methods and the evaluation data requirements. Representative measures include:
16.4.7 Identify Data Acquisition and Recording Techniques
Designation of techniques for data acquisition and recording will depend on the data to be acquired, the evaluation criteria, the types of measures, and the characteristics of data quantity, quality, reliability, validity and affordability. Techniques to acquire and record data on measures will be developed for the human factors evaluation conducted for the baseline system.
16.4.8 Prepare Evaluation Materials including software to support the application of human factors engineering measures. These materials can include simulation exercises and software, mockups, evaluation media, test software, and special documentation such as checklists and questionnaires. Evaluation procedures to be developed include:
16.5 Assemble/Prepare Installation Criteria
16.5.1 Review results of evaluations of installation concepts
16.5.2 Assemble Candidate Installation criteria
16.5.3 Select Installation Criteria
Step 17 Provide HSI Inputs to Engineering Change Proposals (ECPs)
Overview
This step will address development of engineering change proposals, specifically solutions to eliminate or attenuate adverse effects of problems including redesign of hardware, software solutions, changes to manning, training, tutoring, aiding, labeling and marking changes, instructions, procedures, or guards.
Relationship to the System Acquisition Process
This step is concerned with HSI ECPs as well as HSI aspects of system-level ECPs.
Inputs
Requirements for ECPs
Outputs
HSI ECPs and HSI aspects of system ECPs
Activities
17.1 Acquire and analyze human engineering lessons learned for the system or item
17.1.1 Acquire and analyze human engineering lessons learned for use procedures
17.1.2 Acquire and analyze human engineering lessons learned for human errors
17.1.3 Acquire and analyze human engineering lessons learned for human performance problems or difficulties
17.1.4 Acquire and analyze human engineering lessons learned for decision aiding
17.1.5 Acquire and analyze human engineering lessons learned for workloads and workload distributions
17.1.6 Acquire and analyze human engineering lessons learned for safety hazards
17.1.7 Acquire and analyze human engineering lessons learned for problems with the use environment
17.1.8 Acquire and analyze human engineering lessons learned for problems with information handling
17.1.9 Acquire and analyze human engineering lessons learned for problems with communications
17.1.10 Acquire and analyze human engineering lessons learned for problems with maintenance
17.1.11 Acquire and analyze human engineering lessons learned for problems with control systems
17.1.12 Acquire and analyze human engineering lessons learned for problems with logistic support including documentation
17.1.13 Acquire and analyze human engineering lessons learned for problems with life support
17.2 Identify human functions and tasks performed with the system or item
17.2.1 Review results of function analysis
17.2.2 Review baseline system function descriptions
17.2.3 Identify relevant human functions
17.2.3.1 identify operator functions
17.2.3.2 identify maintainer functions
17.2.3.3 identify user functions
17.2.4 Identify critical tasks per function as defined in MIL-H-17820B
17.3 Identify human-machine interfaces and requirements for critical tasks
17.3.1 Identify and describe human-hardware interfaces
17.3.2 Identify and describe human-computer interfaces
17.3.3 Identify and describe human-environment interfaces
17.3.4 Identify and describe human-information interfaces
17.3.5 Identify and describe human-human interfaces
17.3.6 Identify and analyze task requirements
17.4 Acquire T&E data
17.4.1 Identify and describe Develop human engineering test and evaluation measures
17.4.2 Conduct human engineering test and evaluation to identify problems and/or validate lessons learned data
17.4.2.1 evaluate the roles of the human vs automation
17.4.2.2 evaluate workloads
17.4.2.3 evaluate human-hardware interfaces
17.4.2.4 evaluate human-computer interfaces
17.4.2.5 evaluate human-environment interfaces
17.4.2.6 evaluate human-information interfaces
17.4.2.7 evaluate human-human interfaces - communications
17.4.2.8 evaluate procedures
17.4.2.9 evaluate effects of use environments
17.4.2.10 evaluate quality of life
17.4.2.11 Integrate design problem T&E data with lessons learned data
17.5 Process HSI issues
17.5.1 Identify HSI issues
17.5.2 Classify HSI issues in terms of causal factors and contributing conditions
17.5.3 Prioritize HSI issues
17.5.4 Identify solutions to eliminate or attenuate adverse effects of issues
17.5.4.1 requirements for redesign of hardware
17.5.4.2 requirements for software solutions
17.5.4.3 requirements for changes to manning
17.5.4.4 requirements for training, tutoring, aiding
17.5.4.5 requirements for labeling and marking changes
17.5.4.6 requirements for instructions
17.5.4.7 requirements for procedures
17.5.4.8 requirements for guards
17.5.5 Identify constraints on solutions
17.5.6 Tradeoff alternative solutions
17.6 Prepare ECPs/inputs to ECPs
Step 18.0 Approve engineering drawings depicting interfaces between system personnel and other system elements
Overview: Drawing reviews from a HSI standpoint will focus on assessments of arrangements, human-machine interfaces and safety provisions depicted in the drawings.
Relationship to the system acquisition process: According to DoDI 5000.2, human factors engineering shall be an integral part of planning and conceptual efforts, development projects, and acquisition programs to include modifications. Management responsibility for human factors engineering will transfer along with the system in inter-command transition agreements. Furthermore, human factors design requirements shall be established to develop effective human-machine interfaces and preclude system characteristics that: (1) Require extensive cognitive, physical, or sensory skills; (2) Require complex manpower or training intensive tasks; or (3) Result in frequent or critical errors. MIL-STD-1472 and DoD-HDBK-763 should be used as the basis for human factors engineering design. Additional guidance is found in MIL-STD-1801. Manpower, personnel, training, health-hazard, and safety concerns will be translated into human-machine interface design issues to be addressed during systems engineering. This includes efforts to:
In keeping with total system acquisition, test and evaluation will:
Inputs: Drawings to be evaluated
Outputs: Evaluated drawings
Activities:
18.1 Identify features to be evaluated in drawings
18.2 Define criteria to be used in the evaluations
18.2.1 Identify criteria to evaluate human-machine Interfaces depicted in the drawings
18.2.2 Identify criteria to evaluate facility arrangements depicted in the drawings
18.2.3 Identify criteria to evaluate maintenance workspace depicted in the drawings
18.3 Prepare checklists
18.4 Conduct evaluations
18.5 Identify potential problems
Step 19 Perform Detailed Safety and Health Assessment
Overview: The system safety program attempts to insure that:
Relationship to SHAP: As described in DoD 5000.2
Input:
Output:
Activities
19.1 Prepare/Update Documentation
19.1.1 Prepare/Update System Safety Program Plan
19.1.1.1 Describe Program Scope and Objectives
19.1.1.2 Describe the System Safety Organization
19.1.1.3 Describe System Safety Program Milestones
19.1.1.4 Describe General System Safety Requirements and Criteria
19.1.1.5 Describe Hazard Analyses
19.1.1.6 Describe System Safety Data
19.1.1.7 Describe Safety Verification
19.1.1.8 Describe Safety Audit Program
19.1.1.9 Describe Safety Training
19.1.1.10 Describe Mishap and Hazardous Malfunction Analysis and Reporting
19.1.1.11 Describe System Safety Interfaces
19.1.2 Prepare Safety Requirements in Specifications/Design Documents
19.1.2.1 Prepare Prime Item Development Specification (Type B1)
19.1.2.2 Critical Item Development Specification (Type B2)
19.2 Review Documentation
19.2.1 Review Preliminary Engineering Designs to Insure Safety Design Requirements are Incorporated
19.2.2 Review Engineering Documentation to Ensure Safety Considerations are Incorporated
19.2.3 Review Logistic Support Documentation
19.3 Identify and Evaluate Safety Issues
19.3.1 Perform/Update Preliminary Hazard Analysis
19.3.1.1 Review Pertinent Historical Safety Experience
19.3.1.2 Categorize and List Basic Energy Sources
19.3.1.3 Investigate Provisions for Control of Energy Sources
19.3.1.4 Identify and Evaluate Safety Related Interface Considerations Among Subsystems
19.3.1.5 Identify and Evaluate Environmental Constraints
19.3.1.6 Identify and Evaluate Procedures
19.3.1.7 Identify Safety Requirements and Other Regulations With Which System Will Have to Comply
19.3.1.8 Recommend Corrective Actions
19.3.2 Perform/Update Subsystem Hazard Analysis
19.3.2.1 Identify Hazards Associated with Each Subsystem
19.3.2.2 Identify Necessary Actions to Determine How to Eliminate/Control Hazard
19.3.3 Perform/Update System Hazard Analysis
19.3.3.1 Examine Subsystem Interfaces for Compliance with Required Safety Criteria
19.3.3.2 Determine Possible Combinations of Failures That Can Create Hazards
19.3.3.3 Investigate Effects of Control and Safety Device Failures
19.3.3.4 Investigate Degradation in Subsystem/System Safety From Normal Operation of Another Subsystem
19.3.3.5 Investigate Effects of Reasonable Human Errors
19.3.3.6 Identify Necessary Actions to Determine How to Eliminate/Control Hazard
19.3.4 Perform/Update Operating and Support Hazard Analysis
19.3.4.1 Identify Activities Which Occur Under Hazardous Conditions
19.3.4.2 Identify Changes Needed in Functional/Design Requirements to Eliminate/Control Hazards
19.3.4.3 Determine Requirements for Safety Devices and Equipment
19.3.4.4 Determine Required Warnings and Cautions
19.3.4.5 Determine Required Special Emergency Procedures
19.3.4.6 Determine Requirements for Hazardous Materials
19.3.4.7 Determine Requirements for Personnel Certification
19.3.4.8 Determine Requirements for Safety Training
19.3.5 Perform Occupational Health Hazard Assessment
19.3.5.1 Identify Sources of Health Hazards
19.3.5.2 Determine Routine or Planned Uses and Releases of Sources
19.3.5.3 Determine Toxicity, Quantity, and Physical State of Materials
19.3.5.4 Determine Accidental Exposure Potential
19.3.5.5 Identify Hazardous Waste Generated
19.3.5.6 Determine Personnel-Hazardous Material Interface Requirements
19.3.5.7 Determine Protective Clothing/Equipment Needs
19.3.5.8 Determine Detection and Measurement Devices Required to Quantify Exposure
19.3.5.9 Determine Number of Personnel Potentially at Risk
19.3.5.10 Determine Engineering Controls That Could Be Used to Reduce Exposure/ Exposure Potential
19.3.6 Perform/Update Software Hazard Analysis
19.3.6.1 Review System/Subsytem Specifications to ID/Verify HW-SW, SW-SW, User-SW Interfaces
19.3.6.2 Analyze Program Documentation to Insure Specification and Safety Requirement Are Met
19.3.6.3 Examine SW To Determine Independence/Dependence and Inter-dependence of Modules, Tables, etc.
19.3.6.4 Examine SW Elements Which Directly Or Indirectly Influence Safety Critical SW
19.3.6.5 Examine Safety Critical Algorithms, Modules, Routines, and Calculations
19.3.6.6 Examine Programs, Routines, Modules, Functions for Design or Coding Errors
19.3.6.7 Examine Safety Critical SW for Compliance with Criteria Called Out in CPCI Specifications
19.4 Participate in Test Activities
19.4.1 System Safety Testing
19.4.1.1 Establish Analysis, Inspection, and Test Requirements
19.4.1.2 Review Test Plans and Procedures
19.4.1.3 Identify Need for Special Tests
19.4.1.4 Perform Safety Verification
19.4.2 Health Hazard Testing
19.4.2.1 Plan, Conduct, and Evaluate DT/OT II
19.4.2.2 Provide Input to Test and Evaluation Plans (IEP, TDP, OTP, CTP)
19.4.2.3 Identify Potential Health Risks
19.4.2.4 Identify Issues Regarding Use of Human Subjects
19.4.2.5 Identify Requirements for Medical Data Collection an Evaluation
19.4.2.6 Identify Requirements for Direct Test Support
19.4.2.7 Identify Requirements for Special Test Training
19.4.3 Ensure Health Hazard Evaluation Requirements Are:
19.4.3.1 Monitor Test Conduct
19.4.3.2 Forward DT/OT II Data to TSG-Appointed Medical Evaluator
19.4.3.3 Prepare Draft Health Hazard Assessment Report (Evaluator)
19.4.3.4 TSG Approval of Draft HHAR
19.4.4 Ensure HHAR Incorporated into Safety Assessment Report or HFE Analysis
19.5 Evaluate Test Results and Recommend Corrective Actions
19.5.1 Evaluate Safety Testing Results
19.5.1.1 Verify Safety Devices
19.5.1.2 Verify Warning Devices
19.5.1.3 Procedures and Training Requirements Verified
19.5.1.4 Evaluate Other System Testing
19.5.1.5 Evaluate Failure Analyses
19.5.1.6 Mishap Investigations
19.5.2 Recommend Corrective Actions
19.5.2.1 Redesign to Eliminate Hazard
19.5.2.2 Redesign to Reduce Associated Risk
19.5.2.3 Incorporate Safety Devices
19.5.2.4 Provide Warning Devices
19.5.2.5 Develop Procedures and Training
19.6 Participate in Technical and Program Reviews
19.6.1 Participate in Technical Design Meetings
19.6.2 Participate in Program Reviews
19.6.2.1 Present Safety Program Status
19.6.2.2 Present Results of Design or Operations Risk Assessments
19.6.2.3 Summarize Hazard Analyses
19.6.2.4 Present Results of Analyses of R&D Mishaps
19.6.2.5 Present Results of Analyses of Hazardous Malfunctions
19.6.2.6 Respond to Assigned Action Items
19.6.3 Participate in Integrated Logistics Support Team (ILST) Reviews
19.6.3.1 Participate in Design Reviews
19.6.3.2 Participate in In-Process Reviews
19.6.3.3 Participate in Army Systems Acquisition Review Council Review
19.7 Tailor System Safety Program Requirements
19.7.1 Tailor Generally Applicable Requirements
19.7.1.1 Tailor System Safety Program Plan
19.7.1.2 Tailor SSG/SSWG Support
19.7.1.3 Tailor Hazard Tracking and Risk Resolution
19.7.1.4 Tailor Test and Evaluation Safety
19.7.1.5 Tailor System Safety Progress Summary
19.7.1.6 Tailor Safety Review of ECPs and Waivers
19.7.1.7 Tailor GFE/GFP System Safety Analysis
19.7.2 Tailor Selectively Applicable Requirements
19.7.2.1 Tailor Integration/Management of Associate Contractors, Subcontractors, and AE Firms
19.7.2.2 Tailor System Safety Program Reviews
19.7.2.3 Tailor Qualifications of Key System Safety Personnel
19.7.2.4 Tailor Safety Verification
19.7.2.5 Tailor Training
19.7.2.6 Tailor Safety Assessment
19.7.2.7 Tailor Safety Compliance Assessment
19.7.3 Tailor Requirements Generally Applicable to Design Changes Only
19.7.3.1 Tailor Preliminary Hazard Analysis
19.7.3.2 Tailor Subsystem Hazard Analysis
19.7.3.3 Tailor System Hazard Analysis
19.7.3.4 Tailor Operating and Support Hazard Analysis
19.7.3.5 Tailor Occupational Health Hazard Assessment
19.7.3.6 Tailor Software Hazard Analysis
19.8 Provide System Safety Surveillance
19.8.1 Identify Safety Critical Elements
19.8.2 Ensure Adequate Safety Provisions are Included In the Planning and Layout of Production Line
19.8.3 Ensure Adequate Safety Provisions are Included in Inspection, Tests, Procedures, and Checklists for Quality Control of Production
19.8.4 Ensure Production/Manufacturing Control Data Contain Required Warnings, Cautions, and Special Safety Procedures
19.8.5 Ensure Test and Evaluation are Performed on Early Production Hardware
19.8.6 Ensure Minimum Risk is Involved in Accepting/Using New Designs, Materials, or Production/Test Techniques
19.9 Prepare Summary Report
19.9.1 Introduction
19.9.2 System Description
19.9.3 System Operations
19.9.4 System Safety Engineering
19.9.4.1 Summarize/Reference Safety Criteria/Methodology Used to Classify and Rank Hazards
19.9.4.2 Identify Hazards
19.9.4.3 List All Hazards Identified
19.9.4.4 Discuss Hazard
19.9.4.5 Discuss Actions Taken to Eliminate/Control Hazard
19.9.4.6 Discuss Effects of Actions Taken of Probability/Severity Levels of Hazard
19.9.4.7 Discuss/Reference Results of Tests Conducted to Validate Safety Criteria Requirements
19.9.5 Conclusions and Recommendations
19.9.5.1 Assess Results of Safety Program Efforts
19.9.5.2 List Significant Hazards and Associated Specific Safety Actions
19.9.5.3 Hazardous Materials Statement
19.9.5.4 System Does Not Contain or Generate Hazardous Materials
19.9.5.5 System Does Contain or Generate Hazardous Materials
19.10 Review system safety design
19.10.1 Identify, evaluate, and provide safety considerations or tradeoff studies.
19.10.1.1 Define concepts for guarding the hazard
19.10.1.2 Define concepts for labeling the hazard
19.10.1.3 Define concepts for alarming the hazard
19.10.1.4 Define concepts for training/procedures
19.10.1.5 Develop safety & health design criteria
19.10.2 Review appropriate engineering documentation (drawings, specifications, etc.) to make sure safety considerations have been incorporated.
19.10.3 Review logistic support publications for adequate safety considerations, and ensure the inclusion of applicable DOT, EPA, and OSHA requirements.
19.10.4 Verify the adequacy of safety and warning devices, life support equipment, and personal protective equipment.
19.10.5 Identify the need for safety training and provide safety inputs to training courses.
19.11 Ensure that procedures developed for system test, maintenance, operation, and servicing provide for safe disposal of expendable hazardous materials.
19.11.1 Identify any material or manufactured component when access to hazardous material will be required by personnel during planned servicing, teardown, or maintenance activities.
19.11.2 Identify hazards from safety data developed in SSHAs, SHAs, and O&SHAs, and summarized in safety assignment reports for systems which are demilitarized and subject to disposal.
19.12 Prepare reports
19.12.1 Prepare a summary report of the results of the system safety tasks to support the decision-making process.
19.12.2 Tailor system safety program requirements for the production and deployment phase.
Step 20 Define MPTS Concepts and Criteria
Overview: Manpower, Personnel, Training, and Safety (MPTS) concepts and criteria describe the human dimensions and constraints involving a system throughout the system's life cycle. This includes, but is not limited to, descriptions and categorizations of occupations, aptitudes, individual skills and demographics, training system characteristics and components, potential system hazards, and other issues affecting the performance and welfare of operators, maintainers, and personnel that support existing, modified, or new sytems.
Relationship to the System Acquisition Process: During Production and Deployment, consideration is directed toward MPTS contributions to system operational effectiveness and suitability. Efforts are expended to validate the meeting of established thresholds for authorized or required manning levels, training times, quality requirements, and safety goals. The human performance results gathered during testing and evaluation are assessed.
Input:
Output:
Activities
20.1 Conduct MPT Analyses
20.1.1 Conduct Comparative Analyses
20.1.2 Conduct Top-Down Analysis of Total Force To Determine Resources Available
20.1.3 Conduct Organizational and Equipment Modeling to Determine Probable MPT Requirements
20.2 Describe Quantity of Military/Civilian Personnel Required
20.2.1 Describe Programmed Manpower Structure
20.2.2 Describe Programmed Manning
20.2.3 Describe Operators
20.2.4 Describe Maintainers
20.2.5 Describe Supporters
20.2.6 Describe Trainers
20.2.7 Describe Civilian Personnel
20.3 Describe Quality of Military/Civilian Personnel Required
20.3.1 Describe Required Distributions of Skills
20.3.2 Describe Required Distributions of Grade
20.3.3 Describe Required Distributions of Aptitute
20.3.4 Describe Required Distributions of Anthropometric &/or Physical Attributes
20.3.5 Describe Required Distributions of Educational Background
20.3.6 Describe Required Distributions of Training Background
20.4 Describe Training System Components
20.4.1 Describe Tasks Trained
20.4.2 Describe Training Courses
20.4.3 Describe Training Methodologies
20.4.4 Describe Training Time
20.4.5 Describe Training Rates
20.4.6 Describe Simulators and Other Training Devices
20.4.7 Describe Training Facilities
20.4.8 Describe Military Construction Costs
20.4.9 Describe Location of Training Equipments
20.4.10 Describe Instructor-Student Ratios
20.4.11 Describe MOS/Paygrade for Trainees
20.4.12 Describe MOS/Paygrade for Instructors
20.4.13 Review Adequacy of Funding Profiles for Simulators/Devices
20.4.14 Address Impacts of Funding Shortfalls
20.5 Describe Status of System Safety
20.5.1 Describe Potential Safety and Health Hazards
20.5.2 Estimate Probability of Occurance, Severity, and Effects
20.5.3 Recommend Alternatives/Corrective Actions
Step 21.0 Acquire HSI Lessons Learned
Overview: The HSI Program will review existing elements (systems, equipment, software, facilities, and services) to identify lessons learned to include existing capabilities, requirements for additional capability, and deficiencies with existing or projected capability. Lessons learned will include problems to be resolved and positive features of the design which should be continued
Relationship to the System Acquisition Process: Acquisition of lessons learned will be accomplished for Low Rate Production items as well as Full Rate Production.
Inputs: Design descriptions
Outputs: Descriptions of lessons learned
Activities:
21.1 Identify Lessons Learned/Solutions For High Driver missions, conditions, functions and tasks
21.1.1 Identify lessons learned
21.1.1.1 Acquire lessons learned data
21.1.1.2 Collect Lessons Learned data
21.1.1.3 Identify lessons learned
21.1.2 Classify lessons learned in terms of causal factors or HF domain
21.1.3 Validate lessons learned
21.1.4 Prioritize lessons learned
21.1.5 Use lessons learned to eliminate problems with conditions, scenarios, etc.
21.2 Integrate high driver/ lessons learned data
21.2.1 Identify problems which are human factors problems
21.2.2 Identify possible causes for problems
21.2.3 Identify positive aspects of the BCS
21.2.4 Identify positive aspects of the element design which should be retained
21.3 Identify potential solutions to human factors problems
21.3.1 Identify design solutions
21.3.2 Identify NDI solutions
21.3.3 Identify product improvements
21.3.4 Identify manning solutions
21.3.5 Identify selection/training solutions
21.3.6 Identify policy/ procedural change solutions
21.3.7 Integrate problem solutions
Step 22.0 Assess HSI at the End of Production and Deployment
Overview: Assess the status of the system at the end of Production and Deployment
Relationship to Systems Acquisition Process: Applies to :Loww Rate Production as well as to Full Rate Production
Inputs: The system representation at the end of Production and Deployment
Outputs: completion of assessments
Activities:
22.1 Assess installations
1) have equipment location requirements been identified?
2) has space layout for equipment installation been identified?
3) have equipment configuration requirements been identified?
4) have operation & maintenance requirements been identified?
5) have access/egress requirements - based on requirements and HF criteria, been identified?
6) have facility/installation design requirements been identified?
7) have facility users been identified by user role?
8) have facility uses and use conditions been identified?
9) have user functions by use been identified?
10) has a user task analyses been conducted?
11) have architectural/engineering (AE) constraints been identified?
12) have safety & health requirements been identified?
13) have environmental requirements been identified?
14) have signs/labels/marking requirements been identified?
15) have potential problems with installation been identified?
16) have studies been conducted to identify installation concepts?
17) have design/redesign solutions been identified?
18) have training solutions been identified?
19) have environmental solutions been identified?
20) have installation concepts been developed?
21) has an HSI design evaluation been conducted?
22.2 Assess Engineering Change Proposals
1) have HSI lessons learned been identified for the element?
2) have relevant human functions been identified?
3) have operator functions been identified?
4) have maintainer functions been identified?
5) have user functions been identified?
6) have critical tasks per function been identified?
7) have human-hardware interfaces been identified?
8) have human-computer interfaces been identified?
9) have human-environment interfaces been identified?
10) have human-information interfaces been identified?
11) have human-human interfaces been identified?
12) have task requirements been identified and analyzed?
13) have HSI test and evaluation measures been identified?
14) has HSI test and evaluation been conducted to identify problems and/or validate lessons learned data?
15) has the role of human vs automation been evaluated?
16) have workloads been evaluated?
17) have human-hardware interfaces been evaluated?
18) have human-computer interfaces been evaluated?
19) have human-environment interfaces been evaluated?
20) have human-information interfaces been evaluated?
21) have human-human interfaces - communications been evaluated?
22) have procedures been evaluated?
23) has user documentation been evaluated?
24) have effects of use environments been evaluated?
25) have features to be evaluated in drawings been identified?
26) have criteria to be used in the evaluations been identified?
27) are man-machine interface design approaches in compliance with the standards?
28) are design techniques employed within accepted human engineering practice?
29) do design approaches depicted in the drawings exhibit potential problems for human performance and safety?
30) are design approaches depicted in the drawings such that conduct of required activities will require special skills?
31) are identification coding practices depicted in the drawings and are they consistent across equipment and systems?
32) are facility arrangements expected to impede information flow, traffic patterns or interpersonal communications?
33) are provisions for access and egress adequate to accomodate emergency use?
34) are consoles and workstations designed to accommodate operators of all expected body sizes and representative skill levels?
35) do workplace designs take into account expected extremes of environments to be encountered at the workplace?
36) do equipment and facility designs take into account the potential donning, doffing, wearing and storage of individual protective ensembles, and other protective garments?
37) are stowage locations identified as such, are they readily accessible, and are they expected to provide adequate storage?
38) are maintenance workstations identified as such and do they provide sufficient space for safe and easy access to components for maintenance?
39) are items of equipment to be maintained by system personnel designed to enhance maintenance?
40) are maintenance workstations designed to accommodate operators of all expected body sizes and representative skill levels?
41) do maintenance workplace designs take into account expected extremes of environments to be encountered at the workplace?
42) are maintenance stowage locations identified as such, are they readily accessible, and are they expected to provide adequate storage?
43) have HSI issues been identified and classified in terms of causal factors and contributing conditions?
44) have HSI issues been prioritized?
45) have requirements for redesign of hardware been identified?
46) have requirements for software solutions been identified?
47) have requirements for changes to staffing been identified?
48) have requirements for training, tutoring, aiding been identified?
49) have requirements for labeling and marking changes been identified?
50) have requirements for instructions been identified?
51) have requirements for guards been identified?
52) have constraints on solutions been identified?
53) have HSI inputs to ECPs been prepared?
22.3 Assess HSI inputs to ILSP
1) Do HSI inputs to the ILSP address determination of the role of the human maintainer vs automation in maintenance planning?
2) Do HSI inputs to the ILSP address determination of maintenance requirements in maintenance planning?
3) Do HSI inputs to the ILSP address review of maintenance design approaches in maintenance planning?
4) Do HSI inputs to the ILSP address reiterate the specific HSI objectives in design for maintenance in maintenance planning?
5) Do HSI inputs to the ILSP include reducion of the need for maintenance through reduction of human error?
6) Do HSI inputs to the ILSP include the need to reduce the time to repair?
7) Do HSI inputs to the ILSP include the need to reduce maintainer workload and staffing levels required?
8) Do HSI inputs to the ILSP include the need to reduce maintainer skill requirements and training burden?
9) Do HSI inputs to the ILSP include the need to improve the design for maintenance access?
10) Do HSI inputs to the ILSP include the need to improve maintenance procedures?
11) Do HSI inputs to the ILSP include the need to enhance maintainer safety and health?
12) Do HSI inputs to the ILSP include the need to increase maintainer productivity?
13) Do HSI inputs to the ILSP include the need to improve system affordability requirements and reduce life cycle costs?
14) Do HSI inputs to the ILSP include staffing requirements and constraints?
15) Do HSI inputs to the ILSP include staffing and staffing concepts?
16) Do HSI inputs to the ILSP include results of workload simulations?
17) Do HSI inputs to the ILSP supply support include HSI requirements in inventory control
18) Do HSI inputs to the ILSP supply support include HSI requirements in spares management
19) Do HSI inputs to the ILSP support equipment include discussions of requirements for equipment design for usability
20) Do HSI inputs to the ILSP support equipment include discussions of requirements for equipment design for operability
21) Do HSI inputs to the ILSP support equipment include discussions of requirements for equipment design for maintainability
22) Do HSI inputs to technical data and technica