Skip to main content

5-5 Concept & Requirements Definition

HF Input to Preliminary Program Requirements Document. During CRD, the Preliminary FAA HFC will interact with the FAA Systems Engineering Management Team to create the preliminary Program Requirements Document (PRD). This includes providing HF Critical Operational Issues (HFCOIs) for this document. The human-system integration requirements indicated in the preliminary PRD need to be reviewed to supply human-system integration requirements to the FAA Systems Engineering Management Team. The human-system integration requirements provided in FAA Human Factors Design Standard (HF-STD-001B), can be considered.

crdguidelines.pdf (faa.gov) indicates:

  • “Principal contributors to the pPRD include the Solution ConOps, Shortfall Analysis Report (SAR), Functional Analysis Document (FAD) (derived from the ConOps) and the Enterprise Architecture (EA) Artifacts. Functions contained in the functional analysis are transformed into functional requirements and inserted into the preliminary Program Requirements Document (pPRD).” 
  • “The pPRD does not dictate a solution; it is considered the starting point for identifying the essential characteristics of a solution and estimating basic costs that will provide the desired OCs and service outcomes. The sponsoring service organization typically forms a team of experienced technical, user, and program personnel (e.g., operations, human factors, and safety disciplines, etc.) to develop and analyze preliminary program requirements.” 
  • “Research or prototyping may be necessary to define an acceptable range of requirements. The pPRD establishes the basis for determining alternative solutions and estimating costs.” 

During the generation and refinement of concepts, depending on the nature and size of the project, the Preliminary FAA HFC or responsible HF support person needs to participate in meetings discussing alternative concepts, use cases, scenarios, documenting potential human performance risk areas to be evaluated during concept demonstration/validation exercises or needs to manage completion of these activities by a contractor.

There are a variety of sources of information that can provide preliminary requirements for the system under review. Examples include:

  • Review of Operational and Maintenance CONOPS for the acquisition
  • Review of predecessor system information (e.g., procedures, work-arounds, trouble reports, lessons learned)
  • Review of research and analysis relevant to the future system
    • Contact WJHTC HF Division, CAMI, ANG-C1 and AJM-131 for listing of research, studies, and analyses they may have available for review
    • Request contact information for known subject matter experts from WJHTC HF Division, CAMI, ANG-C1 and AJM-131
    • Collaborate with the Systems Engineering Management Team for this acquisition and contact Subject Matter Experts to request inputs
  • Attend meetings with Integrated Requirements Team (IRT)
  • Review products from the Research for Service Analysis transfer package 
Back to top