Section_J_Atch_17-Sec_L_Instructions_to_Offerors.pdf

Solicitation FA8617-17-6219 Section J - Attachment 17

Section L - Instructions, Conditions, and Notices to Offerors

- 1 -

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

1 PROGRAM STRUCTURE AND OBJECTIVES

The efforts anticipated under this contract are for the development, production, and limited sustainment of the Advanced Pilot Training (APT) System.

For consideration in developing a proposal, the following information is provided:

• Customer: Air Education and Training Command

• Award Type: Competitive

• Contract Type: Indefinite Delivery/Indefinite Quantity (IDIQ) – Fixed Price Incentive

Firm, Firm Fixed Price, and Time and Materials

• Fifteen-year (15) IDIQ ordering period (Engineering and Manufacturing Development (EMD) / Low Rate Initial Production (LRIP), Production, Limited Sustainment)

• Pre-priced variable quantity pricing tables

NOTE: Offerors are advised that the costs of any response to, or other costs incurred as a result of responding to, this solicitation are at the offeror’s own risk. Any costs incurred in preparing a response to this solicitation may be attributable to bid and proposal (B&P) overhead costs but may not be directly charged to any resulting awarded contract. B&P costs for this solicitation are costs covered by Cost Accounting Standards 420, 48 CFR 9904.420 Accounting for Independent Research and Development Costs and Bid and Proposal Costs and Federal Acquisition Regulation (FAR) 31.205-18, Independent Research and Development and Bid and Proposal Costs.

2 GENERAL INSTRUCTIONS

2.1 OVERVIEW

This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror’s proposal must include all data and information requested and must be submitted in accordance with (IAW) these instructions.

The offeror’s proposal shall be compliant with Section L and shall meet requirements as stated in the APT Program Statement of Work (SOW), APT Aircraft and GBTS System Specifications (SS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with these instructions provided may result in the proposal being deemed non-responsive.

The proposal should be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or

- 2 -restate the Government's requirements but rather should provide convincing rationale to address how the offeror intends to meet these requirements. Offerors should assume that the Government has no prior knowledge of its facilities and experience. The Government will base its evaluation only on the information presented in the offeror’s proposal.

Only unclassified information should be included in the proposals, no classified information should be included.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

The proposal acceptance period is specified in Section A of the Model Contract. The offeror shall make a clear statement in Section A of its Proposal Documentation volume that its proposal is valid for 18 months from the date proposals are due to the Government.

In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain one copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful proposals.

2.1.1 Points of Contact/Communications

The Procuring Contracting Officer (PCO) is the only point of contact for this acquisition.

Address any concerns you may have to the PCO. Concerns may be sent to the PCO at the address located in Section A, Block 8 (Standard Form (SF) 33) of the Model Contract/Solicitation or by e-mail. Government responses may be posted to the Federal Business Opportunities (FedBizOpps) website at http://www.fbo.gov and/or issued via an amendment to the Government’s Request for Proposal (RFP). In the event of any conflict between the Government responses to offeror’s queries and the RFP, the RFP (including any amendments) shall take precedence. Exchanges of source selection information between Government and offerors will be controlled by the PCO. E-mail may be used to transmit such information to offerors only if the e-mail can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the subject line.

2.1.2 Use of Non-Government Advisors

1) Offerors are advised that technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors for review and analysis. The non-government advisor support will be provided by the following:

COLSA CORPORATION

6728 ODYSSEY DR

HUNTSVILLE, AL 35806-3302

INFOSCITEX CORP

4027 COLONEL GLENN HWY SUITE 210

DAYTON, OH 45431-0000

- 3 -

2) Any objection to the aforementioned disclosure shall:

a) Be submitted in writing to the contracting officer within 10 days of RFP issuance;

and

b) Include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the offeror objects to disclosure to listed non-government advisors.

3) In the event no objection (pursuant to part 2 above) is received by the contracting officer, submission of a certified offer IAW paragraph 7.1.1 hereof, shall be construed as consent to the release of any proprietary, confidential, or privileged commercial or financial data provided in response to this solicitation, to non-government advisors for review and analysis.

2.2 DEBRIEFINGS

The PCO will promptly notify offerors of any decision to exclude them from the competitive range. IAW FAR 15.505, Pre-award Debriefing of Offerors, offerors excluded from the competitive range may request a pre-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each submitted proposal.

Once the final source selection decision has been made, the PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506, Post-award Debriefing of Offerors. Upon such notification, unsuccessful offerors may request and receive a debriefing IAW FAR 15.506.

2.3 DISCREPANCIES

If an offeror believes that the requirements in these instructions contain either errors or omissions, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with its supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to that possible omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. This reservation includes matters of additional or substitute pages to the proposal.

2.4 ELECTRONIC REFERENCE DOCUMENTS

Referenced documents for this solicitation may be available on the FedBizOpps website (http://www.fbo.gov). Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 ORGANIZATION

The offeror shall prepare its proposal as set forth in the “Proposal Organization Table” shown in Section L, Table 1. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Section L, Table 1. Each volume identified in the table shall be separately bound in a three-

- 4 -ring, loose-leaf binder. If the offeror’s electronic proposal does not match the original signed paper-copy proposal, the original signed paper-copy version shall take precedence.

2.5.1 Page Limitations

Page limitations shall be treated as maximums. If maximums are exceeded, excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) those excess pages will be returned to the offeror as soon as practicable. Each page shall be counted except the following: cover page, table of contents, and glossaries. Specifically requested plans (e.g., Integrated Master Plan (IMP)) shall be included as attachments to the proposal (reference Section L, paragraph 8) and will not be included in the page limitations.

If Evaluation Notices (EN) are necessary, the PCO’s Cover Letter accompanying the EN(s) will specify the page limits that apply to the offeror’s EN responses.

Table 1: Proposal Organization

Volume Paragraph Number Volume Title Copies

(Paper/Elec.) Page Limit Submission date Para. 2.9.1

Executive Summary

3.0 Executive

Summary

4/2 20 (excludes attachments) 30 March 2017

I(a) 4.0 Technical Proposal

4/2 250 (excludes attachments) 30 March 2017

I(b) 4.0 Technical Proposal - Aircraft Performance

4/2 50 (excludes attachments) 28 June 2017

II RESERVED

III 6.0 Price Proposal 4/2 100 (excludes attachments) 30 March 2017

IV 7.0 Contract Documentation

4/2 SF-33 w/ Model Contract and attachments

30 March 2017

2.5.2 Formatting

2.5.2.1 Page Size and Format

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced and typed except for the reproduced sections of the solicitation document. The text size shall be no less than 12 point and use Times New Roman font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. At least 1-inch margins on the top and bottom and 1-inch side margins shall be used. Pages shall

- 5 -be numbered sequentially by volume. If ENs are submitted, then these page format restrictions shall also apply to the responses.

2.5.2.2 Tables, Charts, and Graphs

Any tables, charts, graphs, and figures to depict organizations, systems and layout, implementation schedules, plans, etc., used by the offeror shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size, and the text shall be at least 10 points. Foldout pages shall fold entirely within the volume and may only be used for large tables, charts, graphs, diagrams, and schematics; not for pages of text. Any tables, charts, figures, or graphs exceeding the size limitations or other restrictions herein will be treated as excess pages (reference paragraph 2.5.1 above).

2.5.2.3 Pricing Information

All pricing information shall be addressed ONLY in the Price Proposal and Contract Documentation volumes. Pricing information included in any other proposal section will not be evaluated.

2.6 REFERENCES & SUPPORTING MATERIALS

2.6.1 Proposal Cross Referencing

2.6.1.1 Cross Reference Matrix

The offeror will provide a proposal cross reference matrix (CRM) (Section L, Attachment

2) that assures all solicitation requirements are addressed and that the applicable information is easily accessible to the evaluators. The proposal CRM should provide a single integrated index for the entire proposal. Deliver the proposal CRM in tabular and Microsoft (MS) Excel 2010 format.

2.6.1.2 Cross Referencing Between Volumes

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

2.6.2 Indexing

Each volume will contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing will be used to identify sections.

2.6.3 Glossary of Abbreviations and Acronyms

Each volume will contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

- 6 -

2.7 BINDING AND LABELING

Each volume of the proposal should be separately bound in a three-ring loose leaf binder that shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, book number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. All document binders shall have a color other than red, or other applicable security designation colors. Unless otherwise restricted in these instructions, be sure to apply any and all appropriate markings including those prescribed IAW FAR 52.215- 1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.8 ELECTRONIC OFFERS – MEDIA AND LABELING REQUIREMENTS

Do not submit proposals on a flash drive or rewritable compact disc (CD-RW) media. Do not provide any password protected files as part of the proposal. For electronic copies, indicate on each compact disc the volume number and title. Within each volume use separate files to permit rapid location of all portions, including exhibits, annexes, and attachments, if any.

Each volume shall be in a different directory on a compact disc-recordable (CD-R) or digital video disc-recordable (DVD-R). If files are compressed, the necessary decompression program must be included. Two electronic copies of the proposal shall be submitted in a format readable by MS Word 2010, MS Excel 2010, MS Project 2010, MS Power Point 2010, and Adobe Acrobat Portable Document Format (PDF), as applicable. One copy must be unlocked in order to enable the Government to export the winning offeror’s information into Government contract writing systems.

In addition to other instructions for submitting electronic versions of proposals, offerors shall follow these instructions:

1) Electronic storage media shall be submitted in the following formats: CD-R or DVD- R. (No CD-RWs)

2) Documents submitted using MS Office shall be saved in the default format of MS Office 2010.

3) Submit any MS Project files in MS Project 2010. There are no special “save” functions required for later versions of MS Project.

4) Submit PDF documents using only Adobe Acrobat 9.0. Do NOT submit any documents in PDF format that are copied as “images.” When creating PDF files always create to enable textual search and copy functions.

- 7 -

2.9 PROPOSAL SUBMISSION AND DISTRIBUTION

Offerors must submit paper copies of their proposals IAW Section L, Table 1. One of the paper copies shall be the original signed copy and must be marked accordingly. The original shall have two holes punched in the top, centered and spaced 2 ¾ inches apart. Proposals shall be addressed to the PCO and delivered to:

Air Force Life Cycle Management Center/Acquisition Center of Excellence

(AFLCMC/AQH)

Building 570 1755 11th St WPAFB, Ohio 45433-7404

2.9.1 Timeframe for Proposal Submission

Proposal Executive Summary and Volumes I(a), III, IV shall be submitted at AFLCMC/AQH, Building 570, NLT Thursday, 30 March 2017 at 1200 Eastern Standard Time.

Proposal Volume I(b) shall be submitted at AFLCMC/AQH, Building 570, NLT Wednesday, 28 June 2017 at 1200 Eastern Standard Time.

Proposal Executive Summary and Volumes I(a), III, IV received at AFLCMC/AQH, Building 570, after Thursday, 30 March 2017 at 1200 Eastern Standard Time will not be considered for evaluation.

Any Volume I(b) received at AFLCMC/AQH, Building 570, after Wednesday, 28 June 2017 at 1200 Eastern Standard Time will not be considered for evaluation.

2.9.2 Instructions for Technical Volume I(b)

Submission of Volume I(b) is limited to only Section L, Attachment 14a and 14b and up to an additional 50 pages to the technical volume, specific to Subfactor 1.6, Aircraft Performance.

Submission of Volume I(b) is not an opportunity for updates to previously submitted proposal volumes/content. Any attempts to submit updates to other areas of the proposal with the submission of Volume I(b) will not be accepted or evaluated. Evaluation of Volume I(b) will occur prior to establishment of the competitive range, and the commencement of discussions, if the Government so chooses.

3 EXECUTIVE SUMMARY

3.1 GENERAL

This section helps evaluators understand the offeror's overall technical approach and the offeror’s rationale for selecting that approach. While the Technical Proposal volume focuses on those aspects of the offeror's approach that relate to the Technical Subfactors, evaluators also need to grasp the “big picture” in order to render an accurate assessment. In its Executive Summary, the offeror shall provide the following information:

- 8 -

3.1.1 Narrative Summary

This section shall include a concise narrative summary of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding price. The unique features should correspond with Section M evaluation factors and subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.1.2 Table of Contents

Offerors shall submit a master table of contents for the entire proposal.

3.1.3 Other Required Information

3.1.3.1 Authorized Offeror Personnel

On a separate memorandum provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can contractually obligate your company. Also, identify those individuals authorized to negotiate with the Government.

3.1.3.2 Government Offices

On a separate memorandum provide the mailing address, telephone number, e-mail address, and facility codes for the cognizant Contract Administration Office, Defense Contract Audit Agency, and Government Paying Office.

4 VOLUME I – TECHNICAL PROPOSAL

4.1 GENERAL

The Technical Proposal Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical Subfactors defined in Section M. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these Subfactors. All the requirements specified in the solicitation are mandatory to include the offeror selected specifications in Section L, Attachment 9, Aircraft System Specification, Appendix D, and Section L, Attachment 10, GBTS System Specification, Appendix G. By your proposal submission, you are representing that your firm will perform all the requirements specified and proposed in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

- 9 -

4.2 ORGANIZATION

The Technical Proposal shall contain two parts, Volume I(a) and Volume I(b). The Technical Proposal volume shall be organized according to the following general outline:

Volume I(a)

1) Table of Contents

2) List of Tables and Drawings

3) Glossary

4) Technical Performance and Risk Narratives (Section L, Subfactors 1.1 – 1.5)

5) Small Business Participation (Section L, Subfactor 1.7)

6) Attachments

Volume I(b)

7) Aircraft Performance (Section L, Subfactor 1.6)

8) Attachments

4.2.1 Technical Performance and Risk Narratives

The offeror shall provide a narrative description and explanation of the technical approach to meet the APT Program’s requirements for each of the subfactors below. A thorough explanation is critical to enable the Government to determine an offeror’s ability to manage the risks in delivering the capabilities required in the Aircraft SS and GBTS SS in addition to performing the work required in the SOW. The 250-page limit listed in Section L, Table 1 is specifically for, and should only be applied to, the technical performance and risk narratives in Volume I(a). The 50-page limit listed in Section L, Table 1 is specifically for, and should only be applied to, the Aircraft Performance in Volume I(b).

4.2.1.1 Subfactor 1.1 – Systems Integration

1) Aerial Refueling

The offeror shall provide preliminary design information for meeting the Aircraft SS Aerial Refueling (AR) requirement, and identify and propose mitigation of risks associated with the offeror's proposed solution.

- 10 -

Preliminary design information shall include, as a minimum:

a) A comprehensive description of the offeror’s approach to meet the required AR capability, to include:

i) Identification of Group A and Group B hardware to be included as part of the proposed APT production configuration

ii) Identification of physical space allocations, and additional weight, electrical/hydraulic power, and cooling for installation

b) The offeror’s AR receptacle installation location and how the location was chosen to account for: potential impacts to safe handling qualities of the tanker boom/APT Aircraft, structural integrity, and hazards due to fuel spray during AR process (See Joint Service Specification Guide-2009A w/Amendment 1, Air Vehicle Subsystems, Appendix F, paragraph F.3.4.6.2.2.2 for specific guidance on the location and design of aerial refueling receptacles.)

c) Identification of any re-certifications associated with the installation and operation of the receptacle system and the conduct of AR operations, including but not limited to:

i) Relocation or modification of existing equipment/hardware

ii) Re-classification of existing Fire Zones

iii) Re-design of existing structure and control surfaces to be compatible with flying in the wake of each targeted tanker

iv) Flight control system re-design for AR operations

v) External lighting changes or additions

vi) Changes in proof/ultimate pressure capability of existing fuel/hydraulic system

vii) Changes in fuel system performance (including single failures) due to AR capability, to include:

(1) refuel rates/fill sequences

(2) fuel management

(3) tank pressures

d) Illustrations showing:

i) The presumed boom path to achieve a contact with the receptacle

ii) The associated clearances between the boom system and the APT Aircraft fuselage, canopy, and any other structure/external items when the boom follows this presumed boom path

iii) The associated clearances between the boom system and the APT Aircraft fuselage, canopy, and any other structure/external items, when the boom nozzle is connected to the receptacle and the APT Aircraft is positioned at the

- 11 -boundaries of the contact envelope and disconnect envelope of each targeted tanker’s boom system

e) Illustrations of each pilot's line-of-sight to each targeted tanker’s director lights when:

i) The APT Aircraft is at the pre-contact/contact positions associated with each targeted tanker’s boom system

ii) The APT Aircraft is positioned at the boundaries of the disconnect envelope of each targeted tanker’s boom system with the boom nozzle engaged within the receptacle

f) Locations of displays/controls in the cockpit for the aerial refueling system functions.

g) Weight impacts (segregated into Group A and Group B, if appropriate) to include the following:

i) Receptacle

ii) Strike plates around receptacle installation

iii) Cockpit displays/controls of AR system functions

iv) Added electrical wiring, as well as hydraulic and fuel tubing/support brackets

v) Additions/reinforcement of aircraft structure to be compatible with:

(1) loads associated with boom contacts/disconnects

(2) loads associated with flying behind the wake of each targeted tanker

h) Identification of major components associated with providing the AR capability that will require new development.

i) Analysis of electrical and hydraulic power requirements and margins required for the operation of receptacle system.

j) Predicted maximum refuel rate and refuel time from 15% fuel capacity to the APT Aircraft’s maximum in-flight gross weight or maximum fuel capacity (whichever is least).

2) Anthropometrics

The offeror shall provide their approach to meet Aircrew Accommodation requirements, to include the following:

a) The offeror shall provide an Anthropometric Computer Aided Design (CAD) drawing package (Submitted as Section L, Attachment 22) for both aircrew positions. The proposed ejection seats shall be represented in the CAD drawing package, including seat pan lid, seat back, and travel dimensions for the adjustment range. The range of any change in relative distance between seat pan lid with center of head rest and inertial reel strap restraint/mounting point as a result of seat adjustment shall also be reported. If there is no CAD representation

- 12 -of the seat cushions, a complete dimensional description of them, as well as photographs, shall be reported. The CAD drawing package shall contain the 3- Dimensional CAD geometry using Initial Graphics Exchange Specification (IGES) file format for both aircrew positions. IGES file formats shall be compatible with Innovmetric’s Polyworks 2015 (build 2840, 64-bit, April 2015).

The CAD drawing package shall include the following:

i) All visible surfaces contained in the cockpit, such as instrument panels and center and side consoles, detailing all controls and displays.

ii) Primary flight controls (control stick, rudders, throttle) at their extreme positions in their range of movement, and applicable adjustability.

iii) Transparencies (in open and closed positions).

iv) Ejection seat range of motion (adjustability) in all axes.

v) Dimensions of escape path clearance for the ejection seat in the following 4 positions: the most forward (upper and lower) and most aft (upper and lower) positions.

vi) An ejection seat model as a separate CAD model that can be positioned throughout the range of motion and can be examined independently.

vii) Bulkheads, and all other operator interfaces.

viii) The aircraft attitude, in degrees from horizontal (referenced to the aircraft waterline) for 1) level flight, 2) full-flap approach, and 3) no-flap approach configurations, represented as a vector or plane. The angle of the aircraft canopy sill referenced to the aircraft waterline shall also be shown.

ix) A geometric representation of the location of the aircraft Design Eye Point (DEP), as well as the associated design eye plane for required over-the-nose vision. For aircraft utilizing a fixed Head-Up Display (HUD) the CAD drawing package shall include the Eye Reference Point, if different than the aircraft DEP, and the spatial location in the aircraft coordinate system of the outer boundary describing the volume in which all HUD symbology is visible (100% of symbology is visible without moving head). The CAD drawing package shall also include the location of any other defined, display feature volumes (e.g., HUD eye box/head motion box). For aircraft utilizing a Helmet Mounted Display, the CAD drawing package shall show the head motion box, if applicable. (Note: If digital HUD related CAD data is not available, the appropriate non-digital drawings/data shall be provided.) The CAD drawing package shall provide a graphical depiction of the lines of sight from the DEP of both cockpits. The depiction shall include a side and rear view for a 60 degree vision cone parallel to level flight and a 60 degree vision cone parallel to the final approach pitch, for full-flap and no-flap configurations. The rear cockpit depictions shall show the position of the forward aircrew helmet given a representative crewmember of the tallest sitting height.

- 13 -

b) The offeror shall provide an Aircrew Anthropometric Test (AAT) Report (submitted as Section L, Attachment 23) that describes in detail the testing methods and analysis that were employed to evaluate their production representative cockpit design and its determination of accommodation for Aircraft SS 3.5.5 per the instructions in Section L, Attachment 21. The AAT Report shall not exceed 200 pages. The offeror shall also provide all digital data (i.e. subject data and mockup scanned polygonal mesh) collected during the AAT with notation defining required performance data by subject. The digital data collected as part of the AAT shall be submitted in one of the following formats: .ply, .obj, or .stl, for 3D scanned data. These mockup and subject data files shall be aligned, and in the same coordinate space, as the 3D CAD geometry of the cockpit, and shall be provided as attached digital media to the AAT Report.

c) In the written proposal submission, the offeror shall identify and describe the mitigation of risks associated with their proposed approach, to meet the required anthropometric accommodation for the weight and size range required in the Aircraft SS, paragraph 3.5.5.

d) The offeror shall provide the following, related to the escape system design for the required population, as defined in the Aircraft SS:

i) Detailed information on the production ejection seat design and operation, aircraft and seat interfaces, seat modes, interseat sequencing modes, aircrew and seat interfaces (all seat controls, personal leads, emergency oxygen, restraint system, survival kits, etc.), and escape path clearance system (i.e., canopy removal or fracturing and penetration systems; both primary and backup).

ii) The offeror shall discuss all testing planned or completed to meet the Aircraft SS requirements for canopies, seats, interseat sequencing system and related escape system equipment to include: seat subsystem testing (recovery parachute, drogue/stabilization, CAD/PAD, etc.) compatibility testing, sled test data (if available), and sled test plans to qualify the escape system for the required population in the proposed aircraft. If previous testing is to be leveraged for qualification, the offeror shall provide details on any changes made/differences between the as tested system and the proposed production system.

- 14 -

3) Software Development, Assurance, and Architecture

a) The offeror shall describe, for both the aircraft and GBTS, its detailed approach, identifying and providing mitigation of risks associated with the following:

i) Overall software development, test, and integration efforts. The offeror shall list all Operational Flight Programs/Software Items with a description of each’s capabilities.

ii) Software assurance practices specifically pertaining to the development environment, development process, and operational system.

b) The offeror shall provide the following:

i) For each GBTS and aircraft Operational Flight Program/Software Item (OFP/SI) provide software metrics, to include: total Source Lines of Code (SLOC) count (including auto-generated code), percent of new code, percent of reused code, and percent of modified code.

ii) For each new or modified OFP/SI, provide the respective incremental (if applicable) software delivery plan and resource-loaded schedule (that includes planned software development activities showing key software development events) for the first planned delivery to the Systems Integration Lab through the final planned delivery that is intended to support System Verification Review.

c) The offeror shall identify and describe the technical approach to meet the Open Systems Architecture (OSA) requirement in the Aircraft SS. In addition, identify "key components and interfaces," as defined in the Aircraft SS. Identify any proprietary interfaces and explain how these interfaces meet the OSA requirement.

4) Design Maturity

The offeror shall describe its technical approach, and identify and provide mitigation of risks associated with the following:

a) The offeror shall provide a configuration description of the aircraft used to collect flight test data for this proposal. The offeror shall describe configuration differences between the aircraft used to collect data and the final production aircraft that will meet all Aircraft SS requirements. As a minimum, the configuration differences described shall include the following systems/subsystems:

i) Airframe/Structures

ii) Propulsion System/Propulsion Controls

iii) Flight Control System

iv) Avionics and Displays

v) Electrical System

- 15 -

vi) Fuel System (other than aerial refueling)

vii) Environmental Control System

viii) Oxygen System/On-Board Oxygen Generation Systems

ix) Escape System For planned modifications in items (i) through (ix) above, the offeror shall discuss the rationale for the selected approach, the integration design details, and any test, certification, or qualification data and verification plans required to reach the final production configuration. The offeror shall also include details of any modifications made to interfaces that affect the systems/subsystems and identify if the interface is based on a specific standard.

For planned modifications in items (i) through (ix) above, the offeror shall describe the space, weight, power, and cooling impacts, and the expected impact to flight performance, space, and cooling margins.

b) For each aircraft component that contains an OFP/SI (as defined in the Aircraft SS), the offeror shall submit a gap analysis to meeting the MIL-STD-810G requirements in Aircraft SS 3.9.1.1 and 3.9.2.2. This analysis should take into consideration (with respect to retesting) any modifications required to be made to the previously "as tested" component in order to meet APT requirements. For each component identify:

i) Component name, specified environmental conditions, test document used (e.g., DO-160, MIL-STD-810G), laboratory test method and, percent complete. If previously tested, specify any differences between the "tested-to" value(s) and MIL-STD-810G requirement, and whether retesting is needed to meet the MIL-STD-810G requirement. If a component was in production configuration and successfully completed testing (per APT requirements) do not provide all the above information for each environmental condition, but list the component as 100% complete. If the data is unknown or unavailable, the offeror is to assume 100% retest will be required.

- 16 -

Example Table for Completion of Subparagraph i)

Component Name

Environmental Condition

Test Document

Used

Laboratory Test

Method

Percent Complete

Difference(s) between

“tested-to” Value(s) and

MIL-STD-

810G Requirement

Retest Required?

(Y/N)

A

Altitude (Low Pressure)

High Temperature

Low Temperature

Solar Radiation (Sunshine)

Humidity Explosive Atmosphere

Acceleration Vibration Acoustic Noise Shock

B … … … … … … C … … … … … … D … … … … … …

ii) For each component’s production-representative configuration, that does not meet Aircraft SS 3.9.1.1 and 3.9.2.2, provide the plan for completing all remaining qualification testing broken out by environmental condition.

Note: The number of pages that are used to complete 4 b) above shall be submitted as Section L, Attachment 4, Design Maturity Environmental Qualification Status.

c) The offeror shall provide the anticipated/planned total number and the completion percentage for all drawings necessary for manufacture of the production aircraft that will meet the Aircraft SS. In addition, the offeror shall provide the anticipated/planned total number and the completion percentage for drawings of critical components (e.g., critical safety items and critical application items) for the production aircraft that will meet the Aircraft SS. If the drawings are not 100% complete, describe the plan/schedule for achieving 100% completed drawings.

- 17 -

d) The offeror shall provide a detailed status of the full-scale durability and damage tolerance tests of a production-representative airframe to meet Aircraft SS, paragraph 4.1.3.1. Describe current status and plan/schedule for completion to include percent complete, projected completion dates, use of previous durability test data, and number/configuration of test articles.

5) Datalink and Network Connectivity

a) Datalink and Network Connectivity threshold requirements (Aircraft SS, paragraphs 3.2.4 through 3.2.4.4). The offeror shall provide its detailed approach for meeting the threshold requirements, identify and provide mitigation of risks, and provide evidence (of the highest fidelity available) that the proposed solution has performed or will perform the following:

i) Spectrum certification

ii) Sufficient link margin and antenna coverage to maintain aircraft-to-aircraft connectivity over the required local flying area while flying all syllabus maneuvers

iii) Sufficient data rate (throughput) to support the required minimum number of aircraft operating concurrently in the local flying area

iv) The conduct of multiple independent (mutually exclusive) missions operating concurrently within the local flying area

b) Ground Based Training Systems (GBTS) Connectivity. For proposals that include this objective requirement (Aircraft SS, paragraphs 3.2.4.5 and 3.2.4.5.1 and GBTS SS, paragraphs 3.2.1.1.8, 3.3.1.3.1, 3.3.1.12.3, 3.3.5.6.7 and 3.4.6.4) in addition to the proposal requirements identified in paragraph 4.2.1.1 (5)(a) the offeror shall also provide its detailed approach for meeting the objective requirement, identify and provide mitigation of risks, and provide evidence (of the highest fidelity available) that the proposed solution has performed or will perform without any degradation to both aircraft and GBTS network operations.

c) Ground Support Station Connectivity. For proposals that include this objective requirement (Aircraft SS, paragraphs 3.2.4.6 and 3.2.4.6.1 and 3.2.4.6.2), in addition to the proposal requirements identified in paragraph 4.2.1.1 (5)(a), the offeror shall also provide its detailed approach for meeting the objective requirement, identify and provide mitigation of risks, and provide evidence (of the highest fidelity available) that the proposed solution has performed or will perform without any degradation to aircraft-to-aircraft network operations.

6) Embedded Training (ET)

For the ET threshold requirements and, if offered, the Targeting Pod System Simulation objective requirements - The offeror shall provide the following:

a) Provide a top level system description of the ET capabilities to include all hardware and software components required.

- 18 -

b) For each GBTS and aircraft Operational Flight Program/Software Item (OFP/SI) containing any Embedded Training capabilities, provide the software metrics, to include: total SLOC count (including auto-generated code), percent of new code, percent of reused code, and percent of modified code.

c) For each of the above OFP/SI that are new or modified, provide the respective incremental (if applicable) software delivery plan and resource-loaded schedule (that includes planned software development activities showing key software development events), for the first planned delivery to the Systems Integration Lab through the final planned delivery that is intended to support System Verification Review. The offeror shall also identify and provide mitigation of risks associated with the above discrete software development activities.

7) Terrain Warning and Avoidance

a) The offeror shall describe its approach for provisions (i.e., Group A, other hardware components, and interfaces) associated with integration of the Auto- Ground Collision Avoidance System (Auto-GCAS) capability (for aircraft with digital flight controls) for meeting the threshold requirement (Aircraft SS, paragraph 3.2.3.5.1).

b) For proposals that include this objective requirement (Aircraft SS, paragraph 3.2.3.5.2), the offeror shall provide its detailed approach for meeting the objective requirements, identify and provide mitigation of risks, and provide evidence (of the highest fidelity available) that the proposed solution has or will provide an integrated Auto-GCAS capability, to include:

i) Flight control system architecture, components and interfaces (e.g., flight control computer(s), mission computer, auto-pilot, auto-throttle)

ii) Identification of the origin of the Auto-GCAS algorithms

iii) Method for processing terrain elevation data from data transfer/storage equipment and interfaces

iv) Implementation approach for system wide integrity management

v) Description of key Auto GCAS system functionality

4.2.1.2 Subfactor 1.2 – Systems Engineering/Program Management

The offeror shall explain its approach for the following:

1) Schedule

a) Integrated Master Plan (IMP). The offeror shall provide an IMP (provided by the Government as Section L, Attachment 15a, to be tailored by the offeror and resubmitted) including, glossary, and tables, which shall not exceed 150 pages.

Details of the offeror’s integrated processes shall be addressed in the IMP to include all necessary activities performed by all functional disciplines to produce the product required by this RFP. The offeror shall use version 0.9 of the

- 19 -

Department of Defense (DoD) IMP and IMS Preparation and Use Guide, 21 October 2005, as guidance. The IMP shall be event based, containing the events, significant accomplishments, and accomplishment criteria needed to successfully complete the program, including the mandatory events, accomplishments, and criteria identified in the Government provided IMP (Section L, Attachment 15a).

Other events, accomplishments, and criteria may be included as necessary at the discretion of the offeror. The IMP shall demonstrate that the APT Program is structured to provide a balanced approach to minimize and control risk. The IMP shall contain the following in contractor format:

i) Events: Logical points to assess the program’s processes.

ii) Significant Accomplishments: Two or more for each event, defining the desired results prior to or at the completion of each event.

iii) Criteria: Two or more for each significant accomplishment, defined as measureable information that provides definitive evidence that a specific accomplishment is being completed. Completion of these criteria constitutes completion of the accomplishment.

iv) Required Assets Available (RAA): The offeror shall provide a qualitative assessment to identify risks to achieving the required capabilities by the Required Assets Available (RAA) date (1 June 2024) and describe its approach to managing and mitigating these risks, including identification of the responsible parties and any training required.

b) Integrated Master Schedule (IMS). The offeror shall provide an electronic and hardcopy IMS, as Section L, Attachment 15b IAW Integrated Program Management Report Data Item Description Management (DID DI-MGMT- 81861A). The offeror’s IMS shall be submitted on a Windows-compatible CD-R in MS Project 2010 format. The offeror’s IMS shall be limited to no more than 1,000 discrete tasks/activities for proposal evaluation purposes only and include both the aircraft system and the GBTS as clearly identifiable, segregated subsets.

Events, accomplishments, and criteria in the Government-directed IMP, Section L, Attachment 15a, are not counted against the 1,000 task limit but shall be included and appropriately linked in the offeror’s schedule. Summary tasks and Milestones, either Government directed or offeror determined, are not counted against the 1,000 task limit. The offeror’s proposal shall include no more than one IMS that covers the period from Contract Start Date through the RAA date.

2) Manufacturing and Quality

a) Manufacturing Readiness Level (MRL) Evaluation. The offeror shall clearly identify its current MRL for the aircraft. The offeror shall also clearly identify the current MRLs for major subsystems. At a minimum these subsystems shall include the following:

i) Propulsion

- 20 -

ii) Ejection Seat

iii) Canopy

iv) Landing Gear

v) Large Area Display

vi) All Major Structural Assemblies The offeror shall evaluate the MRLs using the criteria and process identified in the Interactive MRL Users Guide [Version 12.6 October, 2015] (see http://www.dodmrl.com). The offeror shall provide a description of its approach and processes used to assess and determine its MRLs. If the Aircraft or any subsystem has an MRL of less than 6, the offeror shall summarize its Manufacturing Maturation Plans (MMPs). Each MMP shall describe the approach to achieve MRL 8 by Milestone C. The offeror shall provide this information as Section L, Attachment 6.

b) Manufacturing Management. The offeror shall describe its overall approach to manufacturing management that ensures compliance with the requirements of SAE International Aerospace Standards (SAE AS) 6500, Manufacturing Management Program.

The offeror shall describe its approach for production and delivery of the APT Aircraft that aligns with the proposed IMS. This approach shall describe the major assembly sequence, manufacturing process flow, key supplier deliveries, and facility layouts.

c) Quality. The offeror shall describe its approach for ensuring acceptable manufacturing product quality IAW SAE AS9100C, Quality Management Systems

- Requirements for Aviation, Space and Defense Organizations, for the APT Aircraft. This proposed approach shall address defect prevention, root cause analysis, corrective action implementation, supplier quality, and key characteristic control.

3) Airworthiness

The offeror shall provide an APT Airworthiness Plan (Section L, Attachment 17a) and APT Tailored Airworthiness Certification Criteria (TACC), to include the APT Certification Compliance Report (Section L, Attachment 18).

a) Airworthiness Plan. Provide an Airworthiness Plan using the Government’s Airworthiness Plan for the Advanced Pilot Training Program (Attachment 17b);

Air Worthiness Bulletin (AWB)-002A, Airworthiness Planning; and the SOW as guidance. The plan shall include a detailed description of the offeror’s airworthiness program that addresses:

i) USAF certification tasks, products, and schedule that includes planned flight activities showing key airworthiness events and their relationship to program events.

- 21 -

ii) Processes and decision points for handling non-compliances and non-compliance risks.

iii) Offeror’s plan for airworthiness data access, including how access to all data will be provided to Government personnel when and where it is required.

iv) Offeror’s understanding of and approaches to supporting the platform throughout its active time in the USAF inventory, and continued airworthiness during any contractor-provided logistics support.

b) APT Certification Basis. Provide a tailored APT Certification Basis using the USAF Technical Airworthiness Authority (TAA)-approved TACC (Attachment 18); AWB-004A, Development of an Airworthiness Certification Basis; and AWB-005, Tailored Airworthiness Certification Criteria/Modification Airworthiness Certification Criteria (TACC/MACC) Document Construction and Format as guidance. Starting with the USAF TAA-approved TACC, the offeror shall:

i) Provide a detailed system description of the offeror’s aircraft design.

ii) Designate criterion applicability and correctly identify non-applicable criteria, and include clear and complete rationale for offeror-identified, non-applicable criteria.

iii) Include redline markups of tailored Standards and Methods of Compliance for easy identification of proposed changes, following correct tailoring conventions IAW AWB-004A and AWB-005 and including clear and complete rationale for the tailoring.

iv) Describe how a level of safety equivalent to that in the USAF TAA-approved TACC is maintained.

c) APT Compliance Certification Report. Provide an APT Compliance Certification Report using the offeror’s tailored APT Certification Basis (Attachment 18 tailored); and AWB-013A, Risk Identification and Acceptance for Airworthiness Determinations as guidance. The APT Compliance Certification Report shall:

i) Identify Substantiating Data References for each applicable airworthiness criteria using columns on the above-described APT Certification Basis included by the Government for that purpose.

ii) Include document titles and numbers for existing data references and those that exist but will be modified as part of the APT Program effort.

iii) Include working or proposed titles for data references that will be developed as part of this effort.

iv) Show the correspondence between the offeror-identified Substantiating Data References and the Methods of Compliance.

- 22 -

4.2.1.3 Subfactor 1.3 – Training

1) Aircrew Training Device (ATD) Fidelity (GBTS SS, paragraphs 3.2, 3.3, and 3.4)

a) Flight Dynamics Simulation Fidelity

i) The offeror shall provide its approach for Flight Dynamics Simulation Development.

ii) The offeror shall provide details, and identify risks and mitigation strategies for the following:

(1) Ownship model development

(2) Implementation of flight test data

(3) Making aircraft hardware simulation vs. stimulation decisions

iii) The offeror shall identify, describe, define, and fully explain its flight dynamics modeling of ownship models in the Weapons System Trainer (WST), to include the following:

(1) Parameter identification techniques

(2) General parameters

(3) Frequency of flight dynamics computations

(4) Aerodynamic coefficients

(5) Installed propulsive effects

(6) Mass and inertia computations

(7) Refueling flowfield effects

(8) Assumptions and any unique techniques

iv) The offeror shall identify and describe how the technical data and information sources used are applicable for flowfield model characteristics, including a description of your Computational Fluid Dynamics analysis approach and/or Wind Tunnel testing.

b) Weapons System Trainer Visualization System Fidelity. The offeror shall describe its proposed WST Visual System Design, to include the following:

i) Specific projector technologies and specifications, layout of projectors, screen types, edge blending and smear reduction methodologies, static and dynamic resolutions, physical dimensions, simulator software and visualization database(s). Provide analyses that illustrate how each solution meets field of view, system resolutions, visual acuity, and the certification standards as required in the GBTS SS.

ii) The offeror shall provide the history, current phase of development or production of its proposed WST Visual System (including: the Image Generator, the Visual Databases, and the Projection System layout with

- 23 -details on the screen type and material), and whether it has been implemented in an existing simulator.

iii) The offeror shall describe and substantiate any remaining development, integration, and manufacturing efforts needed to meet WST Visual System…