Table of Contents 2
Definition of Terms 3
Standards 4-17

AREA A TECHNICAL DESIGN

Factor Descriptions

A.1 Integrated ABL 4

A.2 Beam Control/Fire Control 5

A.2.1 Integrated Beam Control/Fire Control 5

A.2.2 Precision Tracking and Pointing 6

A.2.3 Wavefront Correction 6

A.2.4 Optical Systems 7

A.2.5 Fire Control 7

A.3 Laser 7

A.4 BMC4I 9

A.5 Aircraft 10

A.6 Ground Facility 11

AREA B: SYSTEM MANAGEMENT APPROACH

Factor Evaluations

B.1 System Management 12

B.1.1 Program Management 12

B.1.2 Technical Management 13

B.1.3 Beam Control/Fire Control 15

B.1.4 Laser 15

B.1.5 BMC4I 15

B.1.6 Aircraft 15

B.1.7 Ground Facility 16

B.2 System Test and Evaluation 16

Specialty Engineering includes the following:
1) Integrated Logistics Support (ILS)
2) Reliability and Maintainability
3) Environmental, Safety, and Health (ESH)
4) Electromagnetic Interference and Compatibility (EMI/EMC)
5) Human Engineering
6) Quality
7) Packaging, Handling, Storage, and Transportation
8) Producibility/Manufacturing
9) Training
10) System Security
11) Survivability/Vulnerability
12) Intelligence Support

Systems Engineering includes the following:
1) Requirements Analysis
2) Functional Analysis/Allocation
3) Design Synthesis
4) System Analysis and Control
5) System Integration
6) Affordability, e.g., design-to-weight, design-to-cost, and Life Cycle Cost
7) Interface Definition and Control
8) Configuration and Data Management
9) Risk Assessment and Management
10) Technical Performance Evaluation and Tracking
11) Threat Analysis and Survivability

System Design includes hardware, computer hardware, and software.

Traceability means all key technologies necessary to achieve the operational capability must be demonstrated (e.g., Lasers, adaptive optics, sensors, illuminator, etc.). The functions, methods, and design approach utilized on the PDRR ABL must be directly transferable to the proposed EMD design in a fashion that resolves critical technical and integration issues. The ABL program uses traceability to mean the existence of an obvious set of successive development stages that link laboratory experiments, PDRR ABL engineering and performance, and predicted EMD capability. In a practical sense this implies that any technology, unique engineering, or manufacturing required to meet EMD requirements, must not only be shown in the PDRR ABL, but also needs to be directly coupled to a comprehensive risk reduction effort. This is not to preclude incorporation of breakthrough technologies at any time in the development process.

Scalability means that the appropriate engineering parameters that measure system performance, size, and rates are in the correct ratio with respect to actual ABL system requirements. Scalability is an essential quality for traceable experiments whose hardware does not match the "dimensions" or specification performance of the EMD ABL system.

AREA A TECHNICAL DESIGN

These standards will be used to evaluate the technical design of the proposed PDRR system, subsystems, and components. The most relevant documents for evaluating this area are the CoDR1 data package, with any updates to be provided at CoDR2. The most relevant documents are the Technical Baseline Measures (TBMs), Rationale Document, the Offeror's Proposal, Government System Simulations, and System Specifications Based on PDRR TRD Requirements. EACH STANDARD IN AREA A WILL BE USED TO EVALUATE THE PDRR DESIGN. SCALABILITY AND TRACEABILITY TO THE EMD SYSTEM DESIGN AND REQUIREMENTS CAPTURED IN THE ABL EMD TRD WILL ALSO BE EVALUATED. WHERE PDRR SUBSYSTEMS OR COMPONENTS ARE NOT IDENTICAL TO THE PLANNED EMD CONFIGURATION, JUSTIFICATION OF THE DIFFERENCES WILL BE EVALUATED.

FACTOR A.1 INTEGRATED ABL

STANDARD (A.1.1.1) REQUIREMENTS DEVELOPMENT. The standard is met when the offeror adequately defines:

• Complete system performance requirements, functional requirements, and constraints derived from the top level government requirements defined in the TRD, captured in the ABL specifications, and the constraints imposed by specialty engineering
• PDRR requirements that are scalable and traceable to the EMD requirements
• Allocation of lower level performance and functional requirements (hardware and software) to subsystems and key critical components
• System and subsystem interfaces and the resulting constraints on system, subsystem, and critical component design

• The offeror defines all system level TBMs with a logical construction, which includes all factors/functions required to determine top level system performance values
• The source of all TBM entries is clearly identified
• The entries are credible and their underlying assumptions, limitations, and uncertainties are adequately explained or justified in the supporting rationale

• PDRR system design which provides the required performance for the ABL Weapon System
• A PDRR design which provides an acceptable residual operational capability (ROC)
• A robust system design developed with adequate sensitivity analyses to account for uncertainties in the assumptions and appropriately balances risk and performance margin
• A balanced, flexible, and testable PDRR system fully incorporating the specialty engineering and computer system disciplines while providing maximum operational utility, and supportability, with minimum impact on the environment, for the ABL's entire life cycle
• A system design that has been developed and refined using appropriate models, simulations, assumptions, and input parameters that are benchmarked against actual data or higher fidelity subsystem and/or phenomenology models, with an emphasis on affordability
• System design with inherent flexibility and provisions to incorporate adjunct mission requirements or technology improvements
• System design that uses the minimum acceptable amount of government furnished equipment or information, e.g., avionics equipment, software, and new or unique intelligence support
• Computer systems (hardware and software) constraints and performance requirements that are consistent with functional requirements; interfaces and integration necessary for computer systems to meet weapon system functional requirements; and use of open systems standards that ensure interoperability, portability, scalability, traceability and flexibility to easily accommodate design changes and system improvements throughout the PDRR and EMD efforts

FACTOR A.2 BEAM CONTROL / FIRE CONTROL (BC/FC)

SUBFACTOR A.2.1 INTEGRATED BEAM CONTROL/FIRE CONTROL

STANDARD (A.2.1.1) BC/FC TBMs. This standard is met when

• All BC/FC TBMs are logically constructed and include all factors/functions required to determine top level, ABL weapon performance values
• The design is based on appropriate trade studies, models, and simulations
• All TBM entries are credible, have adequate margin, and their source, underlying assumptions, limitations, and uncertainties are adequately explained or justified in the supporting rationale
• All discrepancies between budgeted and predicted TBM entries are fully explained
• All TBM entries are clearly traceable to segments, subsystems, or components in the PDRR or EMD ABL designs, and are consistent with other TBMs

STANDARD (A.2.1.3) MODELS AND SIMULATIONS. This standard is met when the offeror adequately describes the BC/FC models and simulations used to derive the PDRR design and the extent to which they are anchored to experimental data.

STANDARD (A.2.1.4) BC/FC INTEGRATION & INTERFACE ISSUES. This standard is met when the proposed design demonstrates an adequate understanding of integration and interface issues required to install/integrate, operate, and maintain all parts of the BC/FC within the overall weapons system.

STANDARD (A.2.1.5) BC/FC COMPUTER HARDWARE/SOFTWARE. This standard is met when the BC/FC computer hardware/software architecture is complete and consistent with the overall ABL PDRR system hardware/software architecture. The BC/FC computer hardware/software architecture design has adequate margin. The BC/FC computer hardware is fully identified or valid rationale is given for leaving such equipment undefined.

STANDARD (A.2.1.6) SPECIALTY ENGINEERING. The standard is met when the offeror defines a balanced BC/FC design that incorporates specialty engineering requirements.

STANDARD (A.2.1.7) BC/FC MANUFACTURABILITY: This standard is met when the proposal identifies production sources capable of cost-effectively manufacturing, in the numbers and sizes required, all optical coatings on the requisite substrates, all optical and other sensors, and all non-coating, non-sensor optical hardware in the appropriate materials, including electronics, isolators, etc.

SUBFACTOR A.2.2 PRECISION TRACKING & POINTING:

STANDARD (A.2.2.1) ILLUMINATOR LASERS. This standard is met when the offeror defines a credible design for illuminator lasers that meets the derived energy/pulse, pulse repetition rate, coherence, and beam quality requirements. The estimates for the number, weight, volume, electrical power consumption, and thermal dissipation characteristics of these lasers are realistic and include all auxiliary equipment.

STANDARD (A.2.2.2) FINE TRACKING. This standard is met when the proposed PDRR passive or active fine tracking subsystem, including hardware and algorithms, possesses sufficient field-of-view, resolution, sensitivity, bandwidth, and accuracy whose performance supports the PDRR system requirements.

STANDARD (A.2.2.3) VIBRATION ISOLATION/LINE-0F-SIGHT (LOS) MAINTENANCE. This standard is met when the offeror describes a complete and integrated vibration isolation and LOS maintenance architecture. The vibration and acoustic power spectral densities (PSDs) present at BC/FC hardware locations are the same as those predicted by the aircraft subsystem. The isolation rejection performances of each layer of BC/FC isolation/LOS maintenance is clearly described and meets derived requirements. The inertial reference unit is technically mature and its performance in an aircraft environment meets its derived requirements.

STANDARD (A.2.2.4) BEAM STABILIZATION. This standard is met when the offeror describes a credible method of maintaining a stable beam on target in the presence of atmospheric scintillation. The issue of illuminator beam to track sensor jitter coupling for active fine tracking systems is thoroughly addressed. The proposed method(s) of maintaining the selected aimpoint on target, regardless of target range or acceleration, is clearly described and feasible.

SUBFACTOR A.2.3 WAVEFRONT CORRECTION

STANDARD (A.2.3.1) WAVEFRONT CORRECTION. This standard is met when the offeror's wavefront correction subsystems, including hardware and algorithms, has adequate field-of-view, resolution, sensitivity, bandwidth, and corrective performance to support the PDRR system requirements. The subsystem has adequate margin to anisoplanatically point the HEL when required for aimpoint selection. The proposed wavefront correction techniques are credible and meet derived requirements in the presence of HEL heating, deformation of the optical train, beam path conditioning, and effects of air flow around the ABL aircraft. The placement of any deformable mirrors in optics' space, and the effect of that placement on wavefront correction performance, is thoroughly analyzed and described.

SUBFACTOR A.2.4 OPTICAL SYSTEMS

STANDARD (A.2.4.1) BC/FC AUTOALIGNMENT. This standard is met when the proposed BC/FC autoalignment system is technically realistic and meets derived requirements. The autoalignment system restores system alignment after replacement of optical components.

STANDARD (A.2.4.2) OPTICAL COATINGS. This standard is met when the offeror defines a credible design for optical coatings which meet the derived requirements for reflectivity, transmission, absorption, scattering, stress levels, and polarization for all proposed BC/FC optical components. The coatings must be durable, i.e., long-lived in the presence of HEL exposure and temperature & humidity cycles, and resistant to performance degradation due to contamination.

STANDARD (A.2.4.3) OPTICAL SENSORS. This standard is met when the offeror defines credible, realistic, and reliable sensors that meet derived sensing requirements.

STANDARD (A.2.4.4) BEAM PATH CONDITIONING. This standard is met when the offeror defines a credible, realistic, and adequate system for beam path conditioning.

SUBFACTOR A.2.5 FIRE CONTROL

STANDARD (A.2.5.1) HARDBODY HANDOVER. This standard is met when the proposed method of accomplishing target hardbody handover is technically realistic, is robust relative to target plume temporal dynamics, and has minimum dependence on a priori knowledge of the target type, missile length, or other characteristics.

STANDARD (A.2.5.2) AIMPOINT SELECTION. This standard is met when the proposed method of selecting aimpoints on targets is technically realistic, and has minimum dependence on a priori knowledge of the target type or other characteristics. The proposed method must be flexible and robust, using target type information to improve system effectiveness.

STANDARD (A.2.5.3) KILL ASSESSMENT. This standard is met when the proposed method of doing target kill assessment is technically realistic, and has minimum dependence on a priori knowledge of the target type or other characteristics.

FACTOR A.3 LASER

STANDARD: (A.3.1.1) Laser TBMs. This standard is met when:

• All Laser System TBMs are logically constructed, and include all factors/functions required to determine top level system performance values
• The design is based on appropriate trade studies, models, and simulations
• All TBM entries are credible, have adequate margin, and their source, underlying assumptions, limitations, and uncertainties are adequately explained or justified in the supporting rationale
• All discrepancies between budgeted and predicted TBM entries are fully explained
• All TBM entries are clearly traceable to segments, subsystems, or components in the PDRR or EMD ABL designs, and are consistent with other TBMs

STANDARD (A.3.1.3) MODELS AND SIMULATIONS. This standard is met when the offeror adequately describes the Laser models and simulations used to derive the PDRR design and the extent to which they are anchored to experimental data.

STANDARD (A.3.1.4) OXYGEN GENERATOR. This standard is met when oxygen generator performance and associated performance parameters are clearly defined, fully justified, and meet all design performance parameters. The oxygen generator design minimizes carryover and adverse start/stop transient effects. The thermal management design provides the generator a robust and dynamic performance range. Experiments and modeling results justify the predicted performance over the entire design range of BHP molarity. Experiments are conducted using the offeror's baseline chemicals at expected fluid flows and power, and with appropriate diagnostics.

STANDARD (A.3.1.5) NOZZLES/CAVITY. This standard is met when nozzle and cavity performance and associated performance parameters are clearly defined, fully justified, and meet all design performance parameters. The iodine dissociation profile, effects of the iodine injection scheme on the flow characteristics and densities in the optical cavity, and the basis for modeling the dissociation profile are adequately described. The modeling and experimental results justify the predicted small signal gain and medium quality.

STANDARD (A.3.1.6) OPTICAL RESONATOR. This standard is met when optical resonator and cavity performance and associated performance parameters are clearly defined, justified, and meet design performance parameters for Flight-weight Laser Module (FLM), PDRR, and EMD. Mode length in the cavity, the basis for the geometry of the optical extraction, gain saturation, models, and relevant experiments support performance predictions. The allocated budgets for medium and beam quality, the models supporting the budgets, and any measurements and experiments supporting the models are realistic. The optical surface loadings, the performance margin for the coatings and substrates, alignment characteristics, and wavefront predictions are realistic. The design has adequate margin to account for hot spots in the beam. The resonator alignment method is robust and accounts for the operational environment and optical component maintenance.

STANDARD (A.3.1.7) PRESSURE RECOVERY SYSTEM (PRS). This standard is met when pressure recovery system performance and associated performance parameters are based on clearly defined trade studies, meet all performance design parameters, and adequately describe the complete pressure history within the diffuser. The design is robust to deal with the effects of transients and partial or complete ejector failure.

STANDARD (A.3.1.8) LASER INTEGRATION & INTERFACE ISSUES. This standard is met when the proposed design demonstrates an adequate understanding of integration and interface issues required to install/integrate, operate, and maintain all parts of the laser within the overall weapon system, the overall thermal management of the laser system, and appropriate diagnostics for laser operation.

STANDARD (A.3.1.9) SPECIALTY ENGINEERING. The standard is met when the offeror defines a balanced Laser design that incorporates specialty engineering requirements.

STANDARD (A.3.1.10) LASER COMPUTER HARDWARE/SOFTWARE. This standard is met when the Laser computer hardware/software architecture is complete and consistent with the overall ABL PDRR system hardware/software architecture. The Laser computer hardware/software architecture design has adequate margin. The Laser computer hardware is fully identified or valid rationale is given for leaving such equipment undefined.

STANDARD (A.3.1.11) LASER MANUFACTURABILITY: This standard is met when the proposal identifies production sources capable of cost-effectively manufacturing key laser component hardware in the numbers, sizes, and materials required.

FACTOR A.4 BATTLE MANAGEMENT, COMMAND, CONTROL, COMPUTERS,
COMMUNICATIONS, AND INTELLIGENCE (BMC4I)

STANDARD: (A.4.1.1) BMC4I TBMs. This standard is met when:

• All BMC4I System TBMs are logically constructed, and include all factors/functions required to determine top level system performance values
• The design is based on appropriate trade studies, models, and simulations
• All TBM entries are credible, have adequate margin, and their source, underlying assumptions, limitations, and uncertainties are adequately explained or justified in the supporting rationale
• All discrepancies between budgeted and predicted TBM entries are fully explained
• All TBM entries are clearly traceable to segments, subsystems, or components in the PDRR or EMD ABL designs, and are consistent with other TBMs

STANDARD (A.4.1.3) SURVEILLANCE SENSOR. The standard is met when the offeror describes a sound and integrated surveillance system design which demonstrates a clear understanding of the critical surveillance issues and adequately meets the defined performance/design requirements specified in the TRD, including the potential for future growth performance improvements.

STANDARD (A.4.1.4) MISSION SYSTEMS. The standard is met when the offeror describes a solid integrated mission systems design which addresses all performance/design requirements as specified in the TRD, including the potential for future growth capability, adequate man-machine interfaces, situational decision aids, theater integration, mission planning aids, threat discrimination, prioritization, predictive avoidance, as well as kill assessment and reporting to theater, and appropriate diagnostics.

STANDARD (A.4.1.5) COMMUNICATION SYSTEMS. The standard is met when the offeror provides a sound communication system design with the potential for future growth that meets all design and performance requirements for theater operations.

STANDARD (A.4.1.6) SPECIALTY ENGINEERING. The standard is met when the offeror defines a balanced BMC4I design that incorporates specialty engineering requirements.

STANDARD (A.4.1.7) BMC4I COMPUTER HARDWARE/SOFTWARE. This standard is met when the BMC4I computer hardware/software architecture is complete and consistent with the overall PDRR system hardware/software architecture. The BMC4I computer hardware/software architecture design has adequate design margin. The BMC4I computer hardware is fully identified or valid rationale is given for leaving such equipment undefined.

FACTOR A.5 AIRCRAFT

STANDARD (A.5.1.1) AIRCRAFT TBMs. This standard is met when:

• All Aircraft System TBMs are logically constructed, and include all factors/functions required to determine top level system performance values
• The design is based on appropriate trade studies (which include consideration of affordability), models, and simulations
• All TBM entries are credible, have adequate margin, and their source, underlying assumptions, limitations, and uncertainties are adequately explained or justified in the supporting rationale
• All discrepancies between budgeted and predicted TBM entries are fully explained
• All TBM entries are clearly traceable to segments, subsystems, or components in the PDRR or EMD ABL designs, and are consistent with other TBMs

STANDARD (A.5.1.3) AIRCRAFT INTEGRATION. The standard is met when all modifications to the aircraft and interfaces between the aircraft subsystem, other subsystems, and the operating environment have been defined and developed, to sufficient detail to demonstrate adequate understanding of system design, including diagnostics, interface constraints. The impact of the other subsystems on the aircraft and its operational limits is adequately described.

STANDARD (A.5.1.4) SPECIALTY ENGINEERING. The standard is met when the offeror defines a balanced Aircraft design that incorporates specialty engineering requirements.

FACTOR A.6 GROUND FACILITY

STANDARD (A.6.1.1) GROUND FACILITY TBMs. This standard is met when:

• All Ground Facility System TBMs are logically constructed, and include all factors/functions required to determine top level system performance values
• The design is based on appropriate trade studies, models, and simulations
• All TBM entries are credible, have adequate margin, and their source, underlying assumptions, limitations, and uncertainties are adequately explained or justified in the supporting rationale
• All discrepancies between budgeted and predicted TBM entries are fully explained
• All PDRR TBM entries are clearly traceable to the EMD design

• Facilities and facility modifications accommodating all requirements for the PDRR ABL program, i.e. hardware and software integration, testing, and training
• The PDRR system integration facility including provisions for software and hardware maintenance, hardware emulation, data reduction, mission planning, and other capabilities required of an integration environment, as well as how this facility may migrate to the ABL SIL for EMD
• The requirements for major modifications to government-owned facilities and construction of new facilities taking into account the unique budgeting and schedule constraints
• Specific utility requirements, essential for conducting the PDRR ABL program, including weight, cooling, cabling, power, space, communication and networking to other labs, safety, facility security, computer security, and appropriate diagnostics
• Relocatable ground support equipment, including the ground-based Pressure Recovery System and laboratories
• Facilities for storing, handling, and disposing of fuels, chemicals, and hazardous materials

These standards will be used to evaluate the system management approach to the development of the Airborne Laser, including the approach for demonstrating design performance of the proposed PDRR system, subsystem, and components; providing residual operational capability; and the PDRR Phase II preparations for EMD. The most relevant documents for evaluating this area are the Integrated Task and Management Plan (ITAMP), System/Segment Specification, any available B-Specifications, Work Breakdown Structure (WBS), Software Development Plan (SDP), Software Development Capability Evaluation, the initial Integrated Master Schedule (IMS), Key Processes, Risk Assessment, Target Option, and available test planning documentation. IN EACH AREA B STANDARD, THE PROPOSED TASKS, EVENTS, OR SIGNIFICANT ACCOMPLISHMENTS MUST ENSURE SCALABILITY AND TRACEABILITY OF THE PDRR SYSTEM TO THE EMD SYSTEM. WHERE PDRR SUBSYSTEMS OR COMPONENTS ARE NOT IDENTICAL TO THE PLANNED EMD CONFIGURATION, EXPLANATIONS OF DIFFERENCES, PLANS FOR TRANSITION TO EMD, AND RISK MITIGATION, ACCOMPLISHED DURING PDRR PHASE II, TO ENSURE A SMOOTH TRANSITION TO EMD WILL BE EVALUATED.

FACTOR B.1 SYSTEM MANAGEMENT

SUBFACTOR B.1.1 PROGRAM MANAGEMENT

STANDARD (B.1.1.1) ITAMP/IMS DEVELOPMENT. The standard is met when the offeror adequately defines:

• ITAMP, IMS, and WBS that are logical, complete, and consistent. A PDRR program that is broken down into finite events, tasks, significant accomplishments, accomplishment criteria, and narratives that are logical, clearly related and support completion of program objectives -- accomplishment criteria are objective and measurable -- events are appropriately spaced
• ITAMP, IMS, and WBS that detail how the offeror will balance resources, integrate multiple IPTs and specialty engineering disciplines for the PDRR program, and provide an efficient transition from PDRR into EMD that addresses all configuration differences through analysis, demonstration, or test to increase confidence in EMD
• Key processes that are sound and adequate to ensure program objectives are met
• An adequate approach to program control, administrative security, contracting, and subcontract management

SUBFACTOR B.1.2 TECHNICAL MANAGEMENT

STANDARD (B.1.2.1) SYSTEMS ENGINEERING. The standard is met when the offeror defines an adequate approach implemented at the IPT level for:

• Using systems engineering tools and processes to efficiently apply a systems engineering process to develop, integrate, and test ABL system and subsystems that satisfy performance and specialty engineering requirements, and system constraints
• Developing, tracking, and documenting an integrated set of hardware, software, and system metrics; appropriate TBMs/Technical Performance Measures (TPMs); error and loss budgets; trade study results; design decision rationale; and lessons learned
• Providing an effective means to ensure each IPT supports a consistent and clearly defined process, that is implemented in the ITAMP/IMS, to define and evolve both the PDRR and EMD system baselines
• Conducting studies and analyses (threat, survivability, countermeasures, etc.) conducted to support continued development of the EMD operational concept and design
• Providing an effective method of managing system interfaces

STANDARD (B.1.2.3) SYSTEM INTEGRATION. The standard is met when the offeror clearly defines an adequate process or plan to incrementally integrate PDRR system components in a manner that maximizes probability of success. The evaluation of this standard includes a cohesive systems engineering process that integrates hardware and software design and development.

STANDARD (B.1.2.4) COMPUTER SYSTEMS DEVELOPMENT. The standard is met when the offeror adequately defines the approach for implementing at all IPT levels:

• The requirements analysis, requirements identification, development, design, plans and processes to be employed for the computer hardware and software (computer systems) for the program
• A systematic computer systems integration approach and plan to include incremental phasing of builds, incremental benchmarking, integration across subsystems, use of open systems and common tools, and the connectivity and coordination between geographically separated development facilities
• Computer systems testing with adequate schedule; allocation of human and fiscal resources; regression testing planned for builds, where necessary; and software growth control and management
• Credible parameters, emulations and inputs used to support computer systems trade studies
• All processes used to develop the object code and to perform the first-level testing. The criteria to be followed for turning code over to unit test and to integration are defined, including provisions for code changes. Code generation and autotest generation tools that will be used on the program to produce code, reduce complexity, and test software end items are defined, as well as descriptions of the use of these tools for retest of changed software units/end items.
• Critical software components and the plan to monitor the software quality within their own organizations and across organizations

STANDARD (B.1.2.5) AFFORDABILITY. The standard is met when the proposal defines a satisfactory approach for affordability that includes the following:

• The ITAMP incorporates necessary tasks to define and use Affordability thresholds, objectives, and metrics as system design parameters during the PDRR phase.
• Affordability tools and criteria are used by the IPTs to effectively trade cost and requirements. All trade studies incorporate cost as an independent variable.
• The ITAMP incorporates necessary tasks to define affordability thresholds and objectives for the EMD ABL to be incorporated in the EMD System Specification.

• A clear Integrated Logistics Support/Logistics Supportability Analysis (ILS/LSA) strategy integrated into the system and IPT activities with an emphasis in maximizing operational utility, and supportability
• Implementation of a system reliability, maintainability, and supportability program that actively influences the hardware and software design development process
• Provisions to verify the capability of the PDRR ABL to meet the EMD availability and logistics requirements
• Pollution prevention measures and environmental impacts which are considered in all applicable design trade studies
• Environmental compliance for the facility design approach, training, reporting, and personnel compliance as well as tasks to address future compliance changes and environmental impacts
• Tasks required to develop a Hazardous Material Management Program that will identify and minimize or replace hazardous material/waste, EPA 17 chemicals, and Class I and II Ozone Depleting Substances
• Implementation of a system safety program that integrates system, hardware, and software safety considerations into the PDRR development process to ensure the program adequately addresses safety and complies with appropriate safety regulations and requirements
• Implementation of an Electromagnetic Environmental Effects (EEE) assessment and control program to identify and mitigate EEE impacts to PDRR and EMD ABLs
• Implementation of an adequate human factors program to develop the human/machine interface for maximum operator efficiency and effectiveness in accomplishing the ABL test program and operational mission
• Implementation of a quality assurance/quality control program that incorporates quality into the IPTs to influence the design, development, manufacture, and test processes to achieve a better product at a lower cost
• Implementation of a manufacturing/producibility program to influence design development; support development of EMD Build-To packages; recommend and implement innovative manufacturing methods; and actively manage manufacturing risks and critical processes
• Implementation of a system security management program that influences design development to ensure operational, communication, and computer security requirements are accomplished correctly
• Integration of intelligence support considerations into the design process

STANDARD (B.1.3.1) BC/FC ITAMP. This standard is met when the proposed BC/FC portions of the ITAMP & IMS clearly show the logical flow, completeness, and consistency of the BC/FC events, tasks, significant accomplishments, accomplishment criteria, and narratives, including preparation for EMD in PDRR Phase II.

STANDARD (B.1.3.2) MODELS AND SIMULATIONS. This standard is met when the offeror defines an approach for integrating models and simulations into the engineering design process, including wave optics and fast running system performance (i.e., scaling law) codes, tracking and pointing, and wavefront correction architecture models, etc. which are mature, detailed, and complete, and have been anchored to experimental data.

SUBFACTOR B.1.4 LASER

STANDARD (B.1.4.1) LASER ITAMP. This standard is met when the proposed Laser portions of the ITAMP & IMS clearly show the logical flow, completeness, and consistency of the Laser events, tasks, significant accomplishments, accomplishment criteria, and narratives, including preparation for EMD in PDRR Phase II.

STANDARD (B.1.4.2) MODELS AND SIMULATIONS: This standard is met when the offeror's approach for models and simulations for laser component development, scaling, and integration is mature, detailed, complete, and will be anchored to relevant experimental data.

STANDARD (B.1.4.3) LASER DIAGNOSTICS. The standard is met when the offeror adequately describes the approach to defining the diagnostics that will be incorporated into the PDRR and EMD designs.

SUBFACTOR B.1.5 BMC4I

STANDARD (B.1.5.1) BMC4I ITAMP. This standard is met when the proposed BMC4I portions of the ITAMP & IMS clearly show the logical flow, completeness, and consistency of the BMC4I events, tasks, significant accomplishments, accomplishment criteria, and narratives, including preparation for EMD in PDRR Phase II.

STANDARD (B.1.5.2) MODELS AND SIMULATIONS. This standard is met when the offeror's BMC4I modeling and simulation approach provides for the adequate development of the BMC4I subsystem.

SUBFACTOR B.1.6 AIRCRAFT

STANDARD (B.1.6.1) AIRCRAFT ITAMP. This standard is met when the proposed aircraft portions of the ITAMP & IMS clearly show the logical flow, completeness, and consistency of the Aircraft events, tasks, significant accomplishments, accomplishment criteria, and narratives, including preparation for EMD in PDRR Phase II.

STANDARD (B.1.6.2) AIRCRAFT DESIGN APPROACH. The standard is met when the offeror adequately describes:

• The approach to designing components, fabricating them, modifying the aircraft, and checking out the modifications
• The approach to demonstrating airworthiness and flying qualities to obtain an FAA Experimental Certificate to conduct the PDRR program and to provide useful residual operational capability. Airworthiness will include, but is not limited to flight mechanics, structure, design and construction, powerplant, equipment, and operating limits.
• The approach to certifying the EMD and production aircraft. Also included is the approach to ensuring that eventual conversion of the PDRR aircraft to the production configuration can be made in a cost-effective manner

STANDARD (B.1.7.1) GROUND FACILITY ITAMP. This standard is met when the proposed ground facility portions of the ITAMP & IMS clearly show the logical flow, completeness, and consistency of the ground facility events, tasks, significant accomplishments, accomplishment criteria, and narratives, including preparation for EMD in PDRR Phase II.

STANDARD (B.1.7.2) GROUND FACILITY DEVELOPMENT. The standard is met when the offeror adequately:

• Provides planning and executing construction contracts as well as completing and validating the facilities that meet the PDRR ABL system requirements
• Defines the tasks leading to a Beneficial Occupancy Date and turn-over/transfer processes
• Defines a test and evaluation plan for the ground facility subsystems and components that is complete, detailed, logical, and incrementally and systematically increases confidence in the ground facility performance versus derived requirements

• The incorporation and consideration of supportability in the PDRR and EMD ground facility including Design-to-Cost, and Design-to-Weight objectives and metrics are clearly defined and used as PDRR design parameters
• An appropriate environmental disposal and demilitarization approach

STANDARD (B.2.1.1) REQUIREMENTS VERIFICATION. The standard is met when the offeror's Requirements Verification Matrix adequately addresses all TRD requirements and when the proposed System Specification, is logical, and reflects appropriate balance.

STANDARD (B.2.1.2) TEST APPROACH. The standard is met when the offeror's detailed test objectives define and reflect a logical flow down from program objectives, top-level test objectives, and requirements verification. The test approach is adequately reflected in test processes, tasks, scenarios, and support activities, and flows down from the detailed test objectives. The incremental test approach supports all major program activities (including Authority to Proceed (ATP) decisions and milestone activities). The approach includes using models and simulations in test planning and requirements verification. The approach addresses hardware as well as software test requirements, and closely integrates with the overall approaches to product development and requirements verification. The approach is closely integrated with other activities in PDRR Phase II and ensures a smooth transition from PDRR to EMD. The test program schedule is realistic.

STANDARD (B.2.1.3) TEST RESOURCES. The standard is met when all resources and facilities required to conduct the test program are clearly defined and planned for, including instrumentation, target vehicles, range and ground facilities, other test tools, etc. The proposed source for those resources is identified (i.e., CFE or GFE). The proposed manning and test organization for test conduct are clearly defined, reflect the proposed test approach, and are realistic.

STANDARD (B.2.1.4) BC/FC TEST & EVALUATION. This standard is met when the proposed test & evaluation plan for the BC/FC components and subsystems is complete, detailed, logical, and incrementally and systematically increases confidence in the BC/FC's performance versus derived requirements, including the approach to accomplishing the applicable ATP exit criteria. The test approach allows portions of the BC/FC subsystem to be isolated for functional checkout and minimizes the need to operate the high power laser to checkout the operation of the BC/FC subsystem.

STANDARD (B.2.1.5) LASER TEST & EVALUATION. This standard is met when the proposed test & evaluation plan for the Laser components and subsystems is complete, detailed, logical, and incrementally and systematically increases confidence in the Laser's performance versus derived requirements, including the approach to accomplishing the applicable ATP exit criteria.