FARACP_Appendix_Deliverables.docx

DRAFT // PREDECISIONAL Page 1 of 16

FUTURE ATTACK RECONNAISSANCE AIRCRAFT (FARA) COMPETITIVE PROTOTYPE (CP) DELIVERABLES DESCRIPTIONS

18 June 2018

Introduction 3

1. Baseline Data

2. Program Management Plan,

3. Bi-monthly Technical Status Reports,

4. Monthly Financial Status Updates / Bi-Monthly Financial Status Reports,

5. Long Lead Item Procurement Plan

6. Airworthiness Substantiation Data,

7. Test, Data Collection and Analysis Plan

8. Initial Design and Risk Report (includes System Spec) and Program Cost & Plan Update

9. Final Design and Risk Report (includes System Spec),

10. Initial FARA Increment 1 PDR Data Package

11. Test Plans and Reports

12. Meeting Presentations and Briefing Material,

13. Final Report.

Introduction: Data deliverables are not yet fully defined because all potential data cannot be anticipated due to the variability in possible approaches. The intent will be to fill data and reporting needs for the project management team to track cost, performance and schedule and to document progress and significant findings; for the technical team to calibrate tools and predictions, and make technology assessments; for the airworthiness community to conduct flight risk assessments; to begin assembling qualification data to be applied to the follow-on program of record; and for the Government team as a whole to manage risk, make decisions about allocation of resources and plan for entry into a follow-on Program of Record. Deliverable descriptions are provided as guidance as to the kind of data is desired.

1.0 Baseline Data: Following proposal evaluations and negotiations, for tracking purposes, submit baseline design (including SWAP-C allocations, weight and performance), fly-away price, life cycle cost, and IMS, critical path and top risk items.

2.0 Program Management Plan should document management approach in proposal with additional fidelity and detail as identified in negotiations. The plan shall include, at a minimum,

· Baseline cost and schedule data from which to track program performance/earned value,

· Key personnel and contact information

· Operating structure and plan to integrate Government personnel into operating rhythm

· Sections from proposal that address

· Detailed Technical Approach

· Statement of Research Effort and Statement of Work (SOW), Schedule, and Milestones

· Deliverables

· Management Plan

· Facilities

· Government-Furnished Resources

· Security Requirements

· Cyber security

The Recipient shall submit a draft plan within thirty (30) days of the effective date of the agreement. The Government will review the draft plan within fifteen (15) days and return an annotated copy to the Recipient. The Recipient shall submit a final version of the plan to the Government within fifteen (15) days of receiving the copy.

Submission format shall be negotiated.

3.0 Quarterly Technical Status Reports

The purpose of quarterly technical reports is to periodically document program status and anticipated progress; highlight significant issues and accomplishments; and provide, over time, a comprehensive history of the effort. The quarterly technical reports are not the primary means of communicating risks and issues to the Government project team. Reports should include:

Summary of work over last reporting period and progress against tasks and milestones to include percentage of work complete.

Performance against project metrics based on best available knowledge.

Major accomplishments and risks, issues and opportunities that effect cost, performance or schedule.

Recommended action plan for new risks and issues, and help needed.

Progress against previously reported risks, issues and opportunities.

Status of vendor and subcontractor agreements.

90 day look ahead.

Submission shall be furnished electronically in MS Word or PDF format.

The Recipient shall submit its first report 135 days after the effective date of the agreement. Subsequent reports shall be submitted every 3 months thereafter.

Submission shall be furnished electronically in MS Word or PDF format.

4.0 Monthly Financial Status Updates / Quarterly Financial Status Reports

Monthly and quarterly reports shall provide summarized details, in table or graph format, of the resource status of the Agreement, including the status of the contributions by the participants, and an accounting of current and cumulative expenditures and labor hours, by task, by month, by Government and recipient funding source, including a comparison with planned expenditures and labor hours.

Quarterly analysis shall include earned value management data including budgeting cost of work performed (BCWP), budgeted cost of work scheduled (BCWS), actual cost of work performed (ACWP), cost and schedule variances and estimate at completion (EAC). State whether remaining funds are sufficient to complete each task.

Any deviations of more than 10% from the Program Management Plan in schedule, resources, technical approach, or labor hours shall be explained along with discussions of the adjustment actions proposed.

Voucher submittal history.

Anticipated or realized rate changes.

The Recipient shall submit its first report 135 days after the effective date of the agreement. Subsequent reports shall be submitted every 3 months thereafter.

Submission shall be furnished electronically in MS Word or PDF format.

5.0 Long Lead Item Procurement Plan

If long lead item procurement or start of fabrication is required (to meet overall schedule) prior to the Initial Design and Risk Review (ID&RR), present the plan to procure or fabricate. Also submit analysis, risk assessment and other information that generates confidence in the early procurement decision. Timing of submission shall provide the Government team the opportunity to conduct analysis prior to rendering decisions.

6.0 Airworthiness Substantiation Data

The Recipient shall submit airworthiness substantiation data and documention (to support flight testing) in recipient format in a sufficiently timely manner to allow for thorough review. This does not preclude early and frequent interaction between the Recipient and the Government airworthiness team prior to delivery of documentation. The airworthiness substantiation documentation will contain all pertinent data, information, and documentation (or specific reference to existing documentation) needed to meet applicable flight safety requirements established by the government airworthiness authority.

7.0 Test, Data Collection and Analysis Plan is an overarching plan that attains FARA CP desired results. The plan describes subsystem and system test objectives; defines success; identifies metrics with threshold and objective goals; defines testing methodologies; identifies test facilities, test rigs and other resources needed; assesses risk to successful demonstrations; provides schedules, POCs and other coordinating information.

The plan should include a matrix that shows how ground and flight testing, simulations, SIL testing, and analysis contribute to each demonstrating each metric.

A preliminary plan shall be delivered with the Initial Design and Risk Review Report. The second iteration shall be delivered with the Final Design and Risk Review Report. The final iteration shall be delivered at least 30 calendar days prior to the Test Readiness Review. Within 15 days after receipt, the Government will provide review comments. This does not preclude collaboration between the Recipient and Government in generating the test plan.

Submission shall be furnished in negotiated format.

8.0 Initial Design and Risk Report

The following deliverable description for the Initial Design and Risk Report should be used as a guide for the minimum information anticipated. Reductions from the full set of data described by the referenced documents shall be negotiated prior to delivery.

The focus of the initial design and risk report is the FARA CP. The intent of this deliverable is to document design progress along with the technical, schedule and cost risk associated with meeting project metrics. This information will be used to make decisions on the allocation of resources within the project and program.

Critical technology elements and features will be identified along with aircraft efficiencies and performance metrics. Conversion modes shall be addressed. The preliminary design information for the aircraft will provide data to assess the sufficiency regarding the demonstration of those critical items and capabilities. Design for sustainment and survivability approaches should be clearly identified.

Performance against metrics and technical uncertainty will be addressed to focus resources and provide a clear path to successful project completion. Technical risks and issues shall be assessed and presented with respect to loads and design criteria, meeting component or aircraft performance metrics, uncertainty in behavior of technologies, uncertainty in analysis results or any other factors impacting technical performance. An approach shall be presented to mitigate risks and resolve issues.

Cost and schedule risks and issues shall be addressed and presented with respect to effects of technical risks; staffing, facility and other resource availability; and any other factors impacting cost and schedule.

Describe the proposed manufacturing approach, methods, tools, test equipment, materials including long lead items, processes, quality assurance, minimum and maximum throughput, and manpower required to produce the system.

Describe the overarching system safety methodology tailored from a recognized industry or military standard (MIL-STD-882E is a suggested source) based on the FARA CP design. Describe how the safety hazard management effort will be integrated into the Systems Engineering process, the procedure for tracking hazards and their controls, and identify mitigation measures in the FARA CP design including software, airframe subsystems, and human interfaces.

Describe an initial Product Support Strategy (PSS) that addresses integrated product support (IPS) elements and DOTmLPF-P challenge, barrier and opportunity analysis results. Emphasis should be placed on to the unique aspects of the configuration as they relate to sustainment, as well as sensitivities to the sustainment capabilities and technical objectives.

Describe FARA technologies or approaches that can enhance the Army maintenance concept and increase the likelihood of meeting the reliability, availability, and maintainability goals of future operational requirements and warfighting strategies. Emphasis should be placed on the uncertainties associated with a complex weapon system and sustainment paradigm shift.

The following documents shall be used as guidance for dscription of the FARA CP. Drawings, dimensions and tabulated data shall be provided at the appropriate level of detail. Specific areas where ADS-10D-SP format is unsuitable to accurately describe a unique configuration should be noted and information provided in an alternate format.

Reference Documents:

ADS-10D-SP Air Vehicle Technical Description

ADS-40A-SP Air Vehicle Flight Performance Description

SAWE RP8A Weight and Balance Data Reporting Forms for Aircraft (including Rotorcraft)

(Copies of ADS documents are available from: http://www.redstone.army.mil/amrdec/rdmr-se/tdmd/StandardAero.htm or AMSAM-RA-IM-IS-IL Bldg 5300, Sparkman Center, Redstone Arsenal, AL 35898-5000)

(Copies of SAWE document are available from www.sawe.org or SAWE, P.O. Box 60024, Terminal Annex, Los Angeles, California 90060)

Submission shall be furnished in negotiated format, however, it is desired that data tables used in creation of documentation including curves on charts shall be provided in digital spreadsheet format. Aircraft drawing geometry shall be provided in electronic International Graphics Exchange Standard (IGES) format.

9.0 Final Design and Risk Report

The following deliverable description for the Final Design and Risk Report should be used as a guide for the minimum information anticipated. Reductions from the full set of data described by the referenced documents shall be negotiated prior to delivery.

The final design and risk report will include information about the FARA CP and other major system test articles. The intent of this deliverable is document design progress along with the technical, schedule and cost risk associated with meeting project metrics. This information will be used to make decisions on the allocation of resources within the project and program. Technical risks and issues shall be assessed and presented with respect to loads and design criteria, meeting component or aircraft performance metrics, uncertainty in behavior of technologies, uncertainty in analysis results or any other factors impacting technical performance. An approach shall be presented to mitigate risks and resolve issues. Indicate contingency options for these risks and the corresponding sensitivity of the demonstrator vehicle or component to these contingency plans. Cost and schedule risks and issues shall be addressed and presented with respect to effects of technical risks; staffing, facility and other resource availability; and any other factors impacting cost and schedule.

The detailed design information for the demonstrator aircraft and additional demonstration articles will provide data to assess the sufficiency regarding the demonstration of those critical items and capabilities.

Performance against metrics and technical uncertainty will be addressed to focus resources and provide a clear path to successful project completion.

Cost and schedule risks and issues shall be addressed and presented with respect to effects of technical risks; staffing, facility and other resource availability; and any other factors impacting cost and schedule.

Describe the proposed manufacturing approach, methods, tools, test equipment, materials including long lead items, processes, quality assurance, minimum and maximum throughput, and manpower required to produce the system throughout EMD, LRIP, and FRP that contains a risk assessment and mitigation plan for any techniques, methods, materials, or processes identified as critical to the manufacturing process.

Update the overarching system safety methodology tailored from a recognized industry or military standard (MIL-STD-882E is a suggested source) based on the FARA CP design. Describe how the safety hazard management effort will be integrated into the Systems Engineering process, the procedure for tracking hazards and their controls, and identify mitigation measures in the FARA CP design including software, airframe subsystems, and human interfaces.

Update the Product Support Strategy (PSS) that addresses integrated product support (IPS) elements and DOTmLPF-P challenge, barrier and opportunity analysis results. Emphasis should be placed on to the unique aspects of the configuration as they relate to sustainment, as well as sensitivities to the sustainment capabilities and technical objectives.

Update the description of FARA technologies or approaches that can enhance the Army maintenance concept and increase the likelihood of meeting the reliability, availability, and maintainability goals of future operational requirements and warfighting strategies. Emphasis should be placed on the uncertainties associated with a complex weapon system and sustainment paradigm shift.

The following documents shall be used as guidance for dscription of the FARA CP. Drawings, dimensions and tabulated data shall be provided at the level of detail consistent with Level III data described in ADS-10D-SP and ADS-40A-SP. Specific areas where ADS-10D-SP format is unsuitable to accurately describe a unique configuration should be noted and information provided in an alternate format

Reference Documents:

ADS-10D-SP Air Vehicle Technical Description

ADS-40A-SP Air Vehicle Flight Performance Description

SAWE RP8A Weight and Balance Data Reporting Forms for Aircraft (including Rotorcraft)

(Copies of ADS documents are available from: http://www.redstone.army.mil/amrdec/rdmr-se/tdmd/StandardAero.htm or AMSAM-RA-IM-IS-IL Bldg 5300, Sparkman Center, Redstone Arsenal, AL 35898-5000)

(Copies of SAWE document are available from www.sawe.org or SAWE, P.O. Box 60024, Terminal Annex, Los Angeles, California 90060)

Submission shall be furnished in negotiated format, however, it is desired that data tables used in creation of documentation including curves on charts shall be provided in digital spreadsheet format. Aircraft drawing geometry shall be provided in electronic International Graphics Exchange Standard (IGES) format.

10.0 Initial FARA Increment 1 PDR

· Draft Product Support Strategy (PSS): Draft PSS and DOTmLPF-P challenge, barrier and opportunity analysis results. Emphasis should be placed on to the unique aspects of the configuration as they relate to sustainment, as well as sensitivities to the sustainment capabilities and technical objectives.

· Maintenance Concept that meets the reliability, availability, and maintainability goals of future operational requirements and warfighting strategies. Emphasis should be placed on the uncertainties associated with a complex weapon system and sustainment paradigm shift.

· Training Analysis / Plan that addresses critical technologies, proposed approach to training and methods to maximize concurrency

· Technical Data Rights Analysis and Risk Report that details the cost of GPR to support the transition to an organic sustainment base or alternative product support solution

· Logistics Product Data, Summaries, and IPS Element Analysis that are sufficient to support a transition to organic sustainment

· Level of Repair Analysis Report that is sufficient to support the proposed maintenance concept

· Engineering Data for Provisioning (EDFP) that is sufficient to allow provisioning for the proposed product support strategy

· Interface Control Document that addresses sustainment needs for both manned and autonomous operations. Emphasis should be placed on the implementation and integration of enhanced diagnostics, data reporting and management, health state awareness, prognostics and the integration of the logistics information systems and user interfaces.

· Program management plan: Provide a program management plan that describes the approach from FD&RR for the FARA Competitive Prototype through a successful MS C for a FARA Increment 1 in FY28. Describe the management resources necessary to execute the program including a listing of small businesses and non-traditional defense contractors participating in the effort. Describe the approach to managing program risks including prior risk reduction activities, known and potential risk areas, and the process for continuous risk control, handling, and reduction. The program management plan should also include an integrated master schedule that defines required resources, to include the required number of component and system test articles, to meet the proposed schedule. Monthly technical status reports are also required that track status to the program management plan throughout the FARA Competitive Prototype effort.

· Manufacturing Plan: Describe the proposed manufacturing approach, methods, tools, test equipment, materials including long lead items, processes, quality assurance, minimum and maximum throughput, and manpower required to produce the system throughout EMD, LRIP, and FRP that contains a risk assessment and mitigation plan for any techniques, methods, materials, or processes identified as critical to the manufacturing process. The FARA Increment 1 quantities for manufacturing throughput should be based on aircraft quantities defined in Appendix A.

· System Safety Plan: Prepare an overarching system safety report tailored from a recognized industry or military standard (MIL-STD-882E is a suggested source) based on the FARA Increment 1 design. Describe how the safety hazard management effort will be integrated into the Systems Engineering process, the procedure for tracking hazards and their controls, and identify mitigation measures in the FARA Increment 1 design including software, airframe subsystems, and human interfaces.

· Cost Management Plan:

· Include in the cost management plan the proposed programmatic approach to cost, schedule, and risk management. Although formal Earned-Value Management (EVM) is not required for the program, the proposer is expected to meet the intent and describe how they will provide ongoing assessment of technical and programmatic progress against the program plan, critical path, schedule and cost. Define the content of technical and financial progress reports to enable efficient program monitoring, tracking, and reporting. Describe how the program, if selected for contract award at EMD, will transition to a formal EVM process. Program management tools should be the same tools used internally to manage the program.

· The plan should include supporting cost and pricing information in sufficient detail to substantiate the summary cost estimates and should include a description of the method used to estimate costs and supporting documentation. The Government strongly encourages that tables included in the cost proposal also be provided in an editable (e.g., MS Excel) format with calculation formulas intact to allow traceability of the cost proposal numbers across the prime and subcontractors.

11.0 Technical Reports

The Government may desire data/information developed during FARA CP, not currently identified as a deliverable, to be formally delivered. This may include test reports, special studies into technical issues or any other company recipient generated reports. This deliverable will provide a formal means to request and provide such reports.

Submission shall be furnished in negotiated format.

12.0 Meeting Presentations and Briefing Material

All meeting presentation materials and/or briefing charts that are used shall be submitted to the Government with appropriate markings and Distribution Statements.

Submission shall be furnished electronically.

15.0 Final Report

The final report shall summarize all tasks and results at the conclusion of the CP effort. The report shall be written in clear, concise language and in sufficient detail to give valid support to the conclusions drawn. The Recipient shall submit a final report which shall provide a detailed discussion of all technical work accomplished and information gained in performance of the Agreement, pertinent observations, nature of problems, and positive as well as negative results as applicable. The details of all technical work included shall be sufficient to permit full understanding of the techniques and procedures used in evolving the technology or processes developed, conclusions reached, and recommendations made.

The Final Report includes in a single or multiple volumes:

System and Critical Technology Design Validation that describes methods, results and conclusions from demonstrations

Demonstration Aircraft Characteristics and Performance (tailored ADS-10D-SP, ADS-40D-SP data)

Analytical Tool Assessment describes how well were tools validated and where is additional development needed

Technology Development Strategy based on a residual risk assessment that describes what technology/feature/system level uncertainties remain and how those should be addressed.

MPS Aircraft Design Update based on demonstrated data and includes assessments of survivability, O&S and other –ilities

Lessons learned and recommendations

The Recipient shall submit the final report within 45 calendar days of completion of technical effort or termination of the Agreement. Within 45 calendar days, the Government will provide any recommended changes/revisions. The Recipient shall incorporate revisions and submit to the Agreement Administrator within 30 calendar days one electronic copy (on CD and via SAFE) in word processing software acceptable to the Technical Agent, and four paper copies. Additionally, one paper copy and one electronic of each version of the final report copy shall be submitted to the Defense Technical Information Center (DTIC) addressed to 8725 John J. Kingman Road, Fort Belvoir, VA 22060-6218. The final report shall include a SF 298. The Grants/Agreements Officer, at the completion of the technical effort, will provide the report number and completion instructions.

DRAFT // PREDECISIONAL