| Template for the Requirements Document Revised: 02/2000 Using This Template This template provides guidance for preparing the Requirements Document (RD). It
supplements information found in Appendix B of the FAA Acquisition Management System
(AMS). Text of the template that is italicized is intended to guide preparation of the RD.
Non-italicized text defines the format and structure of the document (title page, table of
contents, section head and numbers, tables and titles). Not all sections of the RD
template apply to every mission need, particularly requirements that will be satisfied by
human resource services. Simply state "not applicable" for those sections which
do not apply to the acquisition program or candidate solution. About the Requirements Document At the beginning of investment analysis, the initial Requirements Document does not
contain any requirement that would unduly restrict the search for solutions to mission
need. As investment analysis proceeds, the initial Requirements Document evolves to a set
of tailored draft RDs, each containing the requirements intended to be satisfied by a
candidate solution to mission need. Typically, these draft RDs have a very high degree of
commonality, with some parameters tailored to the specific capability to be provided.
Sponsor requirements not intended to be satisfied by a candidate solution are compiled in
an attachment to each draft RD. At the Investment Decision, the Requirements Document of
the candidate solution selected for implementation becomes the performance baseline of the
acquisition program The attachment containing any unsatisfied requirements is returned to
the sponsoring line of business for deposition. Specifications, standards, executive orders, and mandates are referenced in the
appropriate section or subsection of the Requirements Document. Tailor them carefully so
only applicable sections are applied. Use industry and international standards to the
greatest possible extent. Appendix I is a Requirements Correlation Matrix that specifies a threshold value and an
objective value for each requirement in the Requirements Document, where practical. The
threshold value is the minimum performance required for acceptable operational suitability
and effectiveness. The objective value represents a measurable increase in capability that
has practical operational benefit to the FAA and its customers. Appendix II is a Mission Need Correlation Matrix that traces where each need statement
in the Mission Need Statement is addressed in the Requirements Document. JRC-Controlled Parameters Certain key parameters in the Requirements Document are designated for control by
the Joint Resources Council. They are highlighted with bold, underlined text in the RD.
The JRC controls only those requirements that are critical to (1) achieving operational
effectiveness and suitability, (2) meeting the needs of dependent elements of the NAS, (3)
and accruing benefits ascribed to the candidate solution or acquisition program. As a rule
of thumb, the JRC controls no more than 10 - 20 requirements across all sections of the
Requirements Document. Mandatory JRC controls are the total number of units for system
production, the number of facilities and/or sites to be constructed, or the total level of
services to be provided, as appropriate to the acquisition program. Change Control The Requirements Document is intended to be a firm and stable foundation for program
implementation. As the performance baseline of the Acquisition Program Baseline, it is
subject to the change procedures of the Acquisition Program Baseline. Cost The resource estimate in the Mission Need Statement addressed by this Requirements
Document is a placeholder in agency's long-range planning in the NAS Architecture. It sets
a rough boundary on the acceptable cost of solutions to the mission need. Schedule The timeframe in the Mission Need Statement when the new capability must be operational
defines the time available to develop and deploy a solution that meets the requirements in
this Requirements Document. Benefits Benefit requirements at the beginning of Investment Analysis are the benefits defined
in the Mission Need Statement. Requirements Document for [enter name of acquisition program] Change (#) Approved by: Signature Date:
Submitted By: Signature Date:
Focal Point Name Code Phone Number FAX Number Federal Aviation Administration 800
Independence Avenue SW Washington, DC 20591 Requirements Document Table of Contents 1. BACKGROUND 2. OPERATIONAL CONCEPT 2.1. Operations 3. TECHNICAL PERFORMANCE 3.1. Operational and Functional Requirements 4. PHYSICAL INTEGRATION 4.1. Real Estate 5. FUNCTIONAL INTEGRATION 5.1. Integration With Other NAS (and non-NAS) Elements 6. HUMAN INTEGRATION 6.1. Human-Product Interface 7. SECURITY 7.1. Physical Security 8. SYSTEM SAFETY MANAGEMENT (Added 02/2000) 8.1 Hazard Identification Process 9. IN-SERVICE SUPPORT 9.1. Staffing 10. TEST AND EVALUATION 10.1. Critical Operational Issues 11. IMPLEMENTATION AND TRANSITION 12. QUALITY ASSURANCE 13. CONFIGURATION MANAGEMENT 14. IN-SERVICE MANAGEMENT Appendix I. Requirements Correlation Matrix Appendix II. Mission Need Correlation Matrix Appendix III. Definitions Appendix IV. Acronyms Attachment - Residual Technical Requirements 1. BACKGROUND Identify the Mission Need Statement addressed by this Requirements Document and summarize the mission need. Describe briefly the deficiency in capability or technological opportunity, and how the proposed capability will satisfy the mission need. Identify National Airspace System (NAS) assets this capability is intended to replace. Briefly summarize any substantive changes to the Requirements Document since the Investment Decision, and explain why the changes were needed. 2. OPERATIONAL CONCEPT Briefly describe the operational concept and intended service life for the required
capability. This is based largely on agency long-range operational concepts and the NAS
Architecture. Explain how the capability will be used in the operational environment, and
how it will affect major users (e.g., controllers, pilots, flow control). To the extent
known, explain how this operational concept interacts, modifies, and folds into
preexisting NAS operations. Assess the impact of this new capability on existing
operational rules and procedures. Use block diagrams and flowcharts to illustrate this
discussion. For requirements likely to be satisfied through a manpower services program, describe how the services will resolve an existing or emerging operational or other capability shortfall. 2.2. Maintenance Describe the intended life of the capability from contractor acceptance inspection
through disposition, including sustainment engineering, pre-planned product improvement,
and other inservice management activities such as condition assessment and routine
operations and maintenance. Define the intended End of Service Life for this product or
service. For requirements likely to be satisfied through a manpower services program, describe the support concept that will be applied to any facility or equipment needed to support the services program. 2.2.1. Hardware Maintenance Define hardware maintenance requirements (e.g., in-house FAA maintenance or contractor maintenance; preventive, preemptive, corrective, first and second level depot repair, lowest level of repair). Indicate any restrictions on who or how maintenance will be done (e.g., FAA or contractor). Define any timephasing requirements for all levels of maintenance (e.g., preventive maintenance not to exceed "x" times per year, depot repair within 30 days, corrective maintenance within 24 hours). Define requirements concerning the degree of on-site and centralized maintenance. Identify whether new equipment will be monitored by RMMS/NIMS. 2.2.2. Software Maintenance Define requirements for software maintenance (e.g., in-house FAA or contractor). Define requirements concerning the degree of on-site and centralized maintenance. Indicate any restrictions on who or how maintenance will be done (e.g., FAA or contractor). Define any requirements related to release of new software into operational use. 2.3. Quantities and Location Identify the total number of units or scope of services that will be needed to meet the mission need. Provide as much location information as possible (e.g., initially the number of units per region, evolving to specific locations during Investment Analysis). Include Congressional mandates. Congressional mandates imposed on a program after baselining at the Investment Decision may require a baseline change. 2.4. Schedule Constraints Identify the date by which products or services must achieve full operational capability at the first site. Identify the date by which all sites must achieve operational capability. Identify schedule constraints associated with any predecessor and successor interfacing or interdependent NAS elements required to achieve full operational capability. Include Congressional mandates. Congressional mandates imposed on a program after baselining at the investment decision may require a baseline change. 3. TECHNICAL PERFORMANCE 3.1. Operational and Functional Requirements Define operational and functional requirements the new capability must provide to
satisfy mission need (e.g., detect, identify, and track aircraft in the en route
airspace). [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need.] The subsection titles in the following table are representative. Select and/or
develop appropriate subtitles to describe operational and functional requirements for the
candidate solution or acquisition program. Representative 3.1 Subsection Titles
3.2. Product Characteristics and Performance Requirements Define product characteristics and performance requirements. Performance
requirements must be achievable, measurable, and specified in operational terms whenever
practical. [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need.] The following subsection titles are representative. Select and/or develop titles
appropriate to the candidate solution or acquisition program. Representative 3.2 Subsections
. 4. PHYSICAL INTEGRATION [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need.] Physical integration concerns the integration of a solution into the physical environment. Initially, these requirements will be general, perhaps defined in terms of "not to exceed" values based on existing capabilities. Derived requirements are defined for each candidate solution during Investment Analysis. Many physical integration requirements do not apply to requirements for services, unless equipment or facilities will be acquired to support the services. 4.1. Real Estate Define requirements for real estate acquisition including appropriate Environmental Due Diligence Audit requirements. 4.2. Space Define physical space requirements to accommodate system/software products and auxiliary equipment both for endstate operations and during transition to the new capability. For services, define space requirements to house the workforce that will provide the services. 4.3. Environmental Define requirements to achieve compliance with the National Environmental Policy Act and other environmental regulations and standards. 4.4. Energy Conservation Define requirements to achieve compliance with energy and water conservation mandates of the National Energy Conservation Policy Act. 4.5. Heating, Ventilation, Air Conditioning Define heating, ventilation, and air conditioning requirements both during transition and for end-state operations. For services, define requirements for the workforce that will provide the services. 4.6. Grounding, Bonding, Shielding, and Lightning Protection Define grounding, bonding, shielding, and lightning protection requirements both during transition to the new capability and for end-state operations. See FAAG2100 and associated standards directives. 4.7. Cables Define cable, cable routing, and raisedfloor requirements both during transition to the new capability and for end-state operations. 4.8. Hazardous Materials Define requirements for the handling, eventual removal, cleanup, and recycling of hazardous materials. 4.9. Power Systems and Commercial Power Define power system requirements and commercial power requirements both during transition to the new capability and for end-state operations. Identify harmonic requirements for all contractorprovided equipment, as well as any deviations from current FAA standards. 4.10. Telecommunications Define telecommunications requirements both during transition to the new capability and for end-state operations. 4.11. Special Considerations Define unique requirements relating to such factors as fiber optics, water and sewer, roadway, and access both during transition to the new capability and for end-state operations. 5. FUNCTIONAL INTEGRATION [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need.] Define functional integration requirements associated with integrating the new
capability into the operational environment. This involves integration with the
approximately 14,000 primary air traffic control and air navigation systems of the
National Airspace System. It also includes functional integration with non-NAS elements. Functional integration requirements typically do not apply to requirements for services. 5.1. Integration With Other NAS (and Non-NAS) Elements Identify all other systems, subsystems, networks, facilities, and organizations, including all states and modes of operation (e.g., primary and back-up) that will interface with this capability, and for which Interface Requirements Documents and Interface Control Documents must be developed. Include remote maintenance monitoring and operational command and control integration requirements. 5.2. Software Integration Identify procedural and technical software interface requirements, as well as specifications, protocols, and standards to ensure compatibility and interoperability with other fielded systems. Identify computer resource constraints (e.g., language, computer, database, architecture, or interoperability constraints). Identify any unique user interface requirements, demonstration needs, and special software certification. 5.3. Spectrum Management Define requirements for spectrum management, including certification of radio spectrum availability. Ensure spectrum compatibility with the rest of the National Airspace System. 5.4. Standardization Define requirements to use standard products already in use in the National Airspace
System. Define any other standardization requirement to facilitate functional and physical
integration. Identify any ICAO, ISO, space management, or other standard to ensure ease of
training, logistics, workforce mobility, architecture and engineering, or compliance with
international, national, state and local codes and laws. 6. HUMAN INTEGRATION Address the following subsections when appropriate to the candidate solution or
acquisition program. Add additional subsections as needed. [No requirement should be entered into this section of the initial Requirements Document that is solution-specific or would unduly restrict the search for solutions to mission need. 6.1. Human/Product Interface Define human/product interface requirements intended to achieve optimum performance from a total product perspective. Typically, human factors requirements are intended to ensure products are designed and appropriate for the human workforce that will operate, maintain, and support them. 6.2. Employee Safety and Health Define requirements related to compliance with Occupational Safety and Health Administration mandates and other safety and health regulations and standards (e.g., adequate workspace for maintenance, access to serviceable components, environmentally friendly fuels and oils, proper handling of exhaust, waste disposal, and fall protection). Define health and safety requirements related to optimizing performance and avoiding conditions that degrade performance. Define operating environment requirements related to such factors as lighting, means of egress, temperature, noise, fire protection, stairs, and ladders. Define requirements for sensing or detecting and automatic shut-down for malfunctions that may cause a serious safety or health risk to employees or the public (e.g., microwave radiation exposure due to a radar malfunction). 6.3. Specialized Skills and Capabilities Define appropriate cognitive, physical, sensory, and performance requirements for operators, maintainers, or support personnel. Define manpower and human performance thresholds and criteria (e.g., the number of operators per equipment, capability or proficiency of operators/maintainers) that influence or shape the operational environment. Define constraints, limitations, and unique or specialized requirements related to training, staffing levels, and personnel skills. Human factors requirements must be consistent with the nature, size, and complexity of the product(s) or services that will be acquired. 7. SECURITY 7.1. Physical Security Define requirements related to the physical plant and contractorunique security both for endstate operations and during transition to the new capability. 7.2. NAS Information Security Define requirements related to the storage, processing, or transfer of information related to air traffic control or other sensitive information, both for endstate operations and during transition to the new capability. 7.3. Personnel Security Define any security requirements related to personnel, security clearances, security training, and access control methods 8. SYSTEM SAFETY MANAGEMENT (Added 02/2000) [No requirement should be entered into this section of the initial Requirements Document that is solution-specific or would unduly restrict the search for solutions to the mission need.]8.1. Hazard Identification Process Define high-level safety requirements, which meet the safety goals determined by the hazard identification process.8.2. Standards Include requirements which may not relate to specific hazards such as those from standards.8.3. Laws Include requirements which may not relate to specific hazards such as those from laws.8.4. Regulations Include requirements which may not relate to specific hazards such as those from regulations.8.5. Lessons Learned Include requirements which may not relate to specific hazards such as those from lessons learned from similar systems.9. IN-SERVICE SUPPORT [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
the mission need.] In-service support requirements typically do not apply to requirements for service
unless equipment or facilities will be acquired to support the human resources who will
provide the services. Define maintenance and support requirements for the following categories, as appropriate. 9.1. Staffing Direct person work-hours required to perform operations and maintenance actions. 9.2. Supply Support Requirements related to obtaining, cataloging, receiving, storing, and issuing items of supply. 9.3. Support Equipment Tools and equipment required to install and support the operation and maintenance of a facility, system, or equipment. Support facility requirements should be identified in the physical facility element of this document. 9.4. Technical Data Requirements related to recorded information such as manuals, specifications, drawings, and operational testing procedures to operate a product over its intended lifecycle. 9.5. Training and Training Support Requirements related to the processes, procedures, course material, and skills necessary to train personnel to install, operate, and maintain a facility, system, or equipment. 9.6. First and Second Level Repair Requirements related to processes and procedures for on-site and second-level engineering support for both hardware and software. 9.7. Packaging, Handling, Storage, and Transportation Requirements related to resources and methods to ensure that systems, equipment, and support items are preserved, packaged, handled, and transported safely. 10. TEST AND EVALUATION 10.1. Critical Operational Issues [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need.] Define the critical operational issues to be used by Independent Operational Test
and Evaluation when determining whether a new capability is operationally acceptable.
Critical operation issues typically relate to operational effectiveness which measures the
degree to which a product satisfies mission requirements when used by representative
personnel in the planned operational environment, and to operational suitability which
measures the degree to which a product meets its availability, operability,
maintainability, safety, human factors, and support requirements. Critical operational issues do not apply to requirements that will be satisfied with services provided by human resources. 10.2. Test and Evaluation Requirements [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
the mission need.] Define test and evaluation requirements. Include mandatory evaluations of safety,
environmental, and energy conservation issues prior to joint acceptance and inspection.
Specify whether independent operational test and evaluation is required. State whether
operational testing will be required at the FAA Technical Center before testing at an
operational site. Test and evaluation requirements typically do not apply to services requirements
unless equipment or facilities will be acquired to support the services. The following table contains representative test and evaluation subsection titles
that should be addressed when applicable to the candidate solution or acquisition program. Representative Test and Evaluation Subsection Titles
11. IMPLEMENTATION AND TRANSITION [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need] Define requirements related to transition from the current capability to the new capability so as to not disrupt services. Implementation requirements typically encompass implementation planning, pre-installation checkout, installation and checkout, site integration, system shakedown, dual operations, and the removal/disposal of replaced systems, equipment, land, facilities, and other items. For services programs where there will be transitions from an existing services provider to a different services provider, implementation requirements may include training, setting up contacts, office automation, support systems, databases, and operational procedures. The InService Readiness Checklist (see FAST) identifies implementation concerns. Define any rulemaking changes related to commissioning into the National Airspace System. 12. QUALITY ASSURANCE [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
mission need.] Define quality assurance requirements. Examples include contractor status reporting,
metrics, an in-plant QRO, independent verification and validation, vendor quality
assurance plans, or a documented process for software development. Specify whether a
Capability Maturity Model assessment of the software development processes of potential
suppliers is required. Identify whether and what ISO or FAA quality standards are invoked. Quality assurance requirements for services requirements typically relate to ensuring the quality of the services to be provided. 13. CONFIGURATION MANAGEMENT [No requirement should be entered into this section of the initial Requirements
Document that is solution-specific or would unduly restrict the search for solutions to
the mission need.] Define configuration management requirements for hardware, software, data,
documentation, interfaces, and tools. These requirements should be appropriate to the
nature (e.g., commercial, nondevelopmental, developmental) and complexity of the
product(s) that will be needed to satisfy mission need. Allow flexibility in the
management of commercial products. Configuration management requirements typically do not apply to requirements for
services unless equipment or facilities will be acquired to support the services. The following table contains representative configuration management subsection
titles that should be included when applicable to the candidate solution or acquisition
program. Representative Configuration Management Subsection Titles
14. IN-SERVICE MANAGEMENT Define requirements for monitoring, assessing, and optimizing the performance of
this capability during the inservice management phase of the acquisition lifecycle. The
objective is to determine whether the new capability is working as intended in the
operational environment, and whether operational and dollar benefits in the Acquisition
Program Baseline are being achieved. These requirements also relate to determining the
capacity of deployed assets to meet emerging demand for services so that replacement or
upgraded capability can be obtained and in place when needed. Appendix I. Requirements Correlation Matrix Where applicable, specify in the following table a threshold value and an objective
value for each requirement in the Requirements Document. The threshold value is the
minimum performance required for acceptable operational suitability and effectiveness. The
objective value represents a measurable increase in capability that has practical
operational benefit to the FAA and its customers.
Appendix II. Mission Need Correlation Matrix Develop a correlation matrix that maps by section number and need statement where
every need in the Mission Need Statement is addressed in the Requirements Document. Use
table format.
Appendix III. Definitions Appendix IV. Acronyms Attachment Residual Technical Requirements Specify those final sponsor requirements that are not intended to be satisfied by
the approved acquisition program. Resolution of these deferred requirements via other
Mission Need Statements or product upgrades is the responsibility of the sponsoring line
of business. |