3._T-6A_ADS_B_Out_Section_L_Final_1_Jul_16.doc

T-6A ADS-B (OUT)

Section L

Instructions, Conditions, and Notices to Offerors or Respondents

1 Program Information

1.1 Program Structure and Objectives

The overall objective of this program is to satisfy Air Education and Training Command’s (AETC), Chief of Naval Air Training’s (CNATRA), and Naval Air System Command’s (NAVAIRSYSCOM) requirement to have Automatic Dependent Surveillance-Broadcast (ADS-B) (Out) in all T-6A aircraft and aircrew training devices (ATDs). This requirement is based on the FAA mandate that indicates all aircraft operating in class A, B, C, and certain E airspace after 1 January 2020, shall have a transponder operating with ADS-B (Out) capability. This program will design, develop, integrate, test, certify, and install the ADS–B (Out) capability into 487 T-6A aircraft and 88 T-6A ATDs.

2 General Instructions The offeror's proposal must include all data and information requested by this Information to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), System Requirements Document (SRD), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall 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 restate the Government's requirements but, rather, shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the offeror's proposal.

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

The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

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 within 60 days of contract award.

2.1 Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation. The source selection for this effort will be conducted at the Wright-Patterson AFB Acquisition Center of Excellence, Area B, Building 570.

2.2 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range whereupon they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the 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 discussion.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOps) website at https://www.fbo.gov/. Potential offerors are encouraged to subscribe to real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Oral Presentation

Oral presentations will not be utilized.

2.6 Communications

Exchanges of source selection information between Government and offerors will be controlled by the CO. E-mail (encrypted when possible or password protected documents) may be used to transmit such information to offerors and shall include “Source Selection Information -- See FAR 2.101 & 3.104” in the subject line. Additionally, source selection information may be transmitted via U.S. Postal (or like service) delivery and/or oral with telephonic or face-to-face meetings.

2.7 Amendments to Solicitation

If this Request for Proposal (RFP) is amended, all terms and conditions (which are not amended) will remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the offeror’s proposal.

2.8 Submission, Modification, Revision, and Withdrawal of Proposals Proposals and modifications to proposals shall be submitted in sealed envelopes or packages in paper media and electronic media (either CD or DVD) addressed to the CO at the address shown in Section A of the model contract/solicitation and show the time and date specified for receipt, the solicitation number, and the name and address of the offeror.

2.9 System for Award Management (SAM)

Offerors will not be eligible to receive a contract award from a DoD activity unless they are registered in SAM. Offerors must be registered in the SAM Database prior to award of any contract. Firms must register on a one-time basis and annually confirm accuracy and completeness of registration information. Online registration and instructions can be accessed at https://www.sam.gov/index.html.

2.10 Data Universal Numbering System (DUNS) Number

A DUNS Number is required for offers exceeding $25,000. The offeror shall enter the annotation “DUNS” followed by the DUNS number identifying the offeror’s name and address in the block with its name and address on the cover page of its offer. If the offeror does not have a DUNS number, contact Dun and Bradstreet at http://www.dnb.com/.

2.11 Technical Data or Computer Software Previously Delivered In accordance with DFARS 252.227-7028, the offeror shall attach to its offer an identification of all documents or other media incorporating technical data or computer software, which the offeror intends to deliver under this contract with other than unlimited or government purpose data rights, that are identical or substantially similar to documents or other media that the offeror has produced for, delivered to, or is obligated to deliver to the Government under any contract or subcontract. See the RFP document for additional related clauses, including, but not limited to, DFARS 252.227-7013, 252.227-7014, and 252.227-7017.

3 Proposal Preparation Instructions

3.1 Organization/Number of Copies/Page Limits

The title page of each volume must show solicitation number, name, address, and telephone and facsimile numbers of the offeror and e-mail address, if available. A title page is required for each volume. A team list of the offeror’s primary Points of Contact (POC) shall be submitted in each volume.

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1). This table specifies the titles and contents of the volumes, required page limits, number of copies to provide, and the format for those copies. The attachments identified in the table shall be bound separately in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in Table 1.

TABLE 1—PROPOSAL ORGANIZATION

Number

Title Page

Table of Contents

List of Table and Drawings

Glossary of Abbreviations and Acronyms

Subfactor 1: Systems Engineering

Subfactor 2: FAA Airworthiness Approval

Subfactor 3: Military Airworthiness

Subfactor 4: Aircraft Integration

Subfactor 5: ATD Integration

Risk Matrix

Appendix (Limited to Integrated Master Schedule (IMS), Systems Engineering Management Plan (SEMP), FAA certification plan, an airworthiness plan, and Cross Reference Matrix)

Unlimited

Title Page

Table of Contents

Unlimited

Business Relationships

1 Page Per Relationship

Past Performance Information (PPI) Recent and Relevant Contracts Narratives / Specific Content

6 Pages Per Contract

Corresponding Official Statement of Work

Unlimited

Consent/Authorization Letters

Unlimited

Organization Structure Change History

Unlimited

3.1.1 Names

Offerors shall submit volumes with the following folder names: Volume 1 - Executive Summary, Volume II - Technical, Volume III - PastPerf, Volume IV - Pricing Matrix, and Volume V - Contract Documentation. Within those folders, documents should be named according to title. For example, the Volume I folder should contain a document titled NarrativeSummary.docx.

3.1.2 Page Limitations

Each page shall be included in the total page count except the following: blank pages, title pages, tables of contents, tabs, indexes, glossaries, and those noted in the Proposed Organization Chart as unlimited. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

3.1.3 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. Except for the reproduced sections of the solicitation document, the font shall be Times New Roman and the text size shall be no less than 12 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics not for pages of text. For tables, charts, graphs, and figures, the text shall be no smaller than 8 point. These limitations shall apply to both electronic and hard copy proposals.

3.2 Cost or Pricing Related Data

All cost or pricing information shall be addressed only in the Price Proposal and Contract Documentation volumes.

3.3 Cross-Referencing

Each volume shall be written on a stand-alone basis. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. The offeror shall provide a Solicitation Cross-Reference Matrix indicating by ITO, SOW, and/or specification paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item.

3.4 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Include an indexed list of tables and figures.

3.5 Glossary of Abbreviations and Acronyms

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

3.6 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose-leaf binder permitting 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, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

3.7 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD/DVD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit volumes 1 through 5 in electronic format, using recordable CDs/DVDs. Each volume shall be in a different directory on a CD/DVD. In the event hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation. The electronic copies of the proposal shall be submitted in accordance with the following:

a. Electronic storage media shall be submitted in one of the following formats:

CD or DVD.

b. Submitting documents using Microsoft Office 2010 or newer:

· Word documents: Set "Save as type" to "Word Document (*.docx)"

· Excel spreadsheets: Set "Save as type" to "Excel Workbook (*.xlsx)."

· PowerPoint presentations: Set "Save as type" to "PowerPoint Presentation (*.pptx)."

c. Submit Microsoft Project files in Microsoft Project 2007 or newer. There are no special “save” functions required for later versions of Project.

d. Submit PDF documents using only Adobe Acrobat. 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.

Do NOT submit documents using file compression software (such as .zip format).

3.8 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand-carried to:

ATTN:

T-6A ADS-B (Out), POC: Erin Bevan

AFLCMC/AZA

BLDG 570, ROOM 113

1755 ELEVENTH STREET

WRIGHT-PATTERSON AFB, OH 45433-7404

4 Proposal Organization

4.1 Volume I ‑ Executive Summary

In the Executive Summary volume, the offeror shall provide the following information:

4.1.1 Narrative Summary

The Narrative Summary of the entire proposal should be concise and address the significant risks, highlighting any key or unique features, excluding price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

4.1.2 Table of Contents

Include a master table of contents for the entire proposal.

4.2 Volume II - Technical Volume

4.2.1 General

The Technical 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, Evaluation Factors for Award. 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. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2.2 Technical and Technical Risk

In the Technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor. Address Technical Risk associated with those aspects of your proposed Aircraft Integration (Subfactor 4) technical approach and Aircrew Training Devices Integration (Subfactor 5) technical approach you consider to have the potential for disruption of schedule, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance.

Provide the rationale for each risk and its rating, including quantitative estimates of the impact on schedule and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOW or specification requirements), and whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigator for identified risks that will eliminate or reduce risk to an acceptable level. An acceptable level of risk is demonstrated when proposed work-arounds and mitigation steps lead to the completion of the development, procurement and retrofit by the 1 January 2020 deadline. Identify and classify any new risks introduced by such risk mitigation.

4.2.3 Volume Organization

The Technical volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Tables and Drawings

(3) Glossary of Abbreviations and Acronyms

(4) Cross Reference Matrix

(5) Subfactor 1: Systems Engineering

(6) Subfactor 2: FAA Airworthiness Approval

(7) Subfactor 3: Military Airworthiness

(8) Subfactor 4: Aircraft Integration

(9) Subfactor 5: ATD Integration

(10) Risk Matrix

(11) Appendix

4.2.4 Cross Reference Matrix

The offeror shall submit a cross reference matrix using the format shown in Attachment L-5. The offeror is responsible for populating the proposal column.

4.2.5 Subfactor One: Systems Engineering

The offeror shall provide their methodology with timelines and descriptions of procedures, processes, and plans for the T-6A ADS-B (Out) development, production, and retrofit program. At a minimum, the methodology shall provide the following essential elements:

· A System Engineering Management Plan (SEMP) to ensure technical requirements, design criteria, design data, and supportability requirements are developed to provide direction and control of the design, development, test, and integration evaluation of the system. At a minimum, this plan shall include:

a. A flow-down of requirements from the T-6A ADS-B (Out) Capability System Requirements Document to the ADS-B (Out) Interface Control Document (ICD) as well as lower level ADS-B (Out) Subsystem Performance Specifications and ICDs.

b. A Specification Requirements Verification Matrix that ensures all ADS-B (Out) performance specification requirements are met by the offeror’s design and development documentation IAW SOW paragraph 3.2.1.

4.2.6 Subfactor Two: FAA Airworthiness Approval

The offeror shall provide their methodology with timelines and descriptions of procedures, processes, and plans for obtaining a FAA Airworthiness certification for the completed T-6A ADS-B (Out) modification. At a minimum, the methodology shall provide the following essential elements:

· Detailed draft certification plan IAW SOW paragraph 3.8.1 to obtain an FAA Supplemental Type Certificate (STC) per FAA Order 8110.101A for the T-6A ADS-B (Out) modification. At a minimum, this plan shall:

a. Provide details on how to obtain, sustain, and retain ownership of the STC for the ADS-B (Out) modification IAW SOW paragraph 3.2.2.1.

4.2.7 Subfactor Three: Military Airworthiness

The offeror shall provide their methodology with timelines and descriptions of procedures, processes, and plans for a military airworthiness certification for the completed T-6A ADS-B (Out) modification. At a minimum, the methodology shall provide the following essential elements:

· An Airworthiness Plan to comply with USAF policy on airworthiness certification and the T-6A ADS-B (Out) certification basis. At a minimum, this plan shall:

a. Provide details on how to update and maintain the Government-provided Certification Basis IAW SOW paragraph 3.2.2.2.

4.2.8 Subfactor Four: Aircraft Integration

The offeror shall provide their methodology with timelines and descriptions of procedures, processes, and plans for designing, developing, testing, and building production-ready T-6A ADS-B (Out) modification kits to execute developmental and operational test and evaluation, and installation of these kits on all Air Force and Navy T-6A aircraft by 1 January 2020. Please note: due to USG constraints, at each of the six retrofit bases, no more than two aircraft can be in retrofit at any given time, with the exception of NAS Pensacola where two aircraft can be in retrofit with Air Force Combat Systems Operator (CSO) and two aircraft can be in retrofit with NAS Pensacola Naval Flight Officer (NFO) at any given time. At a minimum, the methodology shall provide the following essential elements:

a. A description of the proposed avionics architecture to include components, installation locations inside aircraft, block diagrams, and interface definitions on the T-6A that will be used to satisfy the aircraft ADS-B (Out) requirement.

b. A description of the projected aircraft modifications required for installation of the proposed avionics architecture IAW SOW paragraph 3.4.3, and the number and composition of qualified team members required to complete the retrofit IAW SOW paragraph 3.7.

c. An integrated master schedule which includes activities for Research, Development, Test, Evaluation, material procurement, FAA certification, Military Airworthiness certification, modification kit build, and retrofit execution IAW SOW paragraph 3.3.2.1.

4.2.9 Subfactor Five: ATD Integration

The offeror shall provide their methodology with timelines and descriptions of procedures, processes, and plans for designing, developing, testing, and building production-ready ATD ADS-B (Out) modification kits. The offeror shall execute a program to retrofit a minimum of one ATD suite (one UTD, one IFT, and one OFT) per base at least one month prior to the first aircraft retrofit at each base. The exception to this base requirement is NAS Pensacola, where both Air Force CSO and Navy NFO are located. In the case of NAS Pensacola, Air Force CSO will need one suite of ATDs retrofit one month prior to the first Air Force CSO aircraft retrofit. Navy NFO will need one suite of ATDs retrofit one month prior to the first Navy NFO aircraft retrofit.. At each location, only one type of ATD suite (UTD, IFT, and OFT) can be worked on at a time. All Air Force and Navy T-6A ATDs will be retrofitted prior to the completion of the air vehicle retrofit; all ATD retrofits will be completed by 1 January 2020.

At a minimum, the approach shall provide the following essential elements:

a. A description of the proposed avionics architecture to include components, installation locations in the ATD, block diagrams, and interface definitions on the ATD that will be used to satisfy the ADS-B (Out) requirement.

b. A description of the projected ATD modifications required for installation of the proposed avionics architecture IAW SOW paragraph 3.13.3, and the number and composition of qualified team members required to complete the retrofit IAW SOW paragraph 3.13.

c. An integrated master schedule which includes activities for Research, Development, Test, Evaluation, material procurement, modification kit build, and retrofit execution IAW SOW paragraph 3.3.2.1.

4.3 Volume III - Past Performance

4.3.1 Past Performance Information (PPI) Tool

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment L-1, which contains instructions for use of the PPI Tool. This information is required for the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 10% percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

4.3.2 Recent and Relevant Contracts

Submit information IAW Attachment L-1, Past Performance Information for Offerors, on up to five (5) recent contracts you consider most relevant in demonstrating your ability to perform the proposed effort. Recency is defined as an ongoing effort or an effort completed within the last five (5) years of the date of the issuance of this solicitation. Relevance is defined as an effort that is similar in scope, magnitude, and complexity. Include rationale supporting your assertion of relevance. Also, include information on recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Please note five (5) (maximum) recent contracts for the prime contractor and up to three (3) recent contracts total for all teaming partners/subcontractors shall be submitted. Offerors shall also submit the corresponding official statement of work (SOW) for each contract submitted. The SOW will be used to verify the assertions made in the contract narrative. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, provision M002 - Evaluation Factors, paragraph M002c - Past Performance Factor.

4.3.3 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating since the problems encountered may have been on a more complex program or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. Categorize the relevant information into the specific Technical subfactors used to evaluate the proposal.

4.3.4 Consent/Authorization Letters

Along with the information required in this paragraph, the offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. A sample consent letter is included as Attachment L-3. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the offeror's performance. A sample authorization letter is included as Attachment L-4.

4.3.5 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources, as well as that provided by the offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

4.3.6 Early Proposal Information

Each offeror is requested to submit Volume III Past Performance for each relevant contract fifteen (15) calendar days prior to the solicitation closing date. Offerors must use the PPI Tool provided in the solicitation in order to electronically submit the PPI portion of the Past Performance Volume in accordance with the RFP. Failure to submit early proposal information will not result in offeror disqualification.

As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Information Questionnaire (PPIQ) (Attachment L-2). Offerors then shall distribute the PPIQ to all POCs the offeror has identified in the PPI Tool as directed in the Past Performance Information for Offerors (Attachment L-1). POCs will then complete the questionnaires and mail them directly to the Past Performance Evaluation Team (PPET) (ATTN: Erin Bevan) at the address provided on the questionnaire or email erin.bevan@us.af.mil. POCs should be advised by the offeror that they shall not, under any circumstances, send the completed questionnaire back to the offeror.

4.4 Volume IV –Price

4.4.1 General Instructions

4.4.1.1 Price Reasonableness, Balance, and Completeness This section is designed to assist you in submitting data that is required to evaluate the reasonableness, balance, and completeness of your proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Additionally, unbalanced pricing may pose an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers shall include a completed Pricing Matrix (Attachment 5 to the solicitation) and be sufficiently detailed to demonstrate its reasonableness, balance, and completeness. The burden of proof for credibility of proposed prices rests with the offeror.

4.4.1.2 Total Evaluated Price

The TEP will be calculated on the Pricing Matrix spreadsheet as a summation of the offeror’s proposed prices for each line item in the CLIN Pricing Matrix.

4.4.1.3 Price Information Information beyond that required by this instruction shall not be submitted. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

Proposals shall be in “Then Year” (TY) United States currency dollars unless stated specifically otherwise. TY dollars are dollars that have been escalated into the time period of performance of the contract. They are sometimes referred to as “escalated dollars” or “inflated dollars.” All dollars shall be displayed in the same units (millions, thousands, and so on). Spreadsheets and supporting documents will identify the type of dollar in TY$M, TY$K, etc.

4.4.1.4 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

4.4.1.5 Rounding

All dollar amounts provided shall be rounded to the nearest dollar.

4.4.2 Volume Organization

The Price volume shall consist of the following sections:

SECTION 1 - Table of Contents.

SECTION 2 - Completed Pricing Matrix.

SECTION 3 - Data other than certified cost or pricing data, to include estimating methodology.

Summary: The offeror shall provide a narrative of the basic pricing approach and methodology utilized to generate matrix prices.

SECTION 4 - Other information such as Government Furnished Property (GFP), base support, development/production schedule, inflation rate summary and explanation, and special tooling/test equipment.

4.4.3 Pricing Matrix Instructions

Submission of an incomplete Pricing Matrix, see solicitation Attachment 5 - Pricing Matrix, will cause the offeror’s proposal to be non-compliant with the terms and conditions of the RFP and may render the proposal ineligible for award. Offerors shall complete the matrix IAW the instructions contained within the Pricing Matrix workbook.

4.4.4 Accounting System

Indicate whether you have Government approval of your accounting system, and if so, provide evidence of such approval.

4.5 Volume V - Contract Documentation

4.5.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract and Sections A through K.

4.5.1.1 Section A - Solicitation/Contract Form

Completion of blocks 12-16 and signature and date for blocks 17 and 18 of the SF 33. Signature by the offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes. Offeror shall also supply Government with an electronic copy of the offer.

4.5.1.2 Section B - Supplies or Services and Prices

Complete pricing information in Section B of the model contract, as well as the pricing matrix.

4.5.1.3 Section F - Deliveries or Performance

Attachment 12 to the solicitation is the notional execution schedule that includes the non-negotiable completion date of 1 January 2020. The offeror may propose an alternate execution schedule by completing the blanks in Section F of the model contract and providing a corresponding execution schedule. The Government reserves the right to award under either the required execution schedule in Attachment 12 to the solicitation or the proposed schedule when an offeror proposes an earlier completion date than the one stipulated in the notional execution schedule. If the offeror proposes no other execution schedule, the notional execution schedule in Attachment 12 of the solicitation will apply.

4.5.1.4 Section I - Contract Clauses

The offeror shall provide necessary information to complete clauses as required.

4.5.1.5 Section J – Attachments Exhibit A:

Contract Data Requirements List (CDRLs) Package Attachment 1:

JPATS NAC ADS-B (Out) Statement of Work (SOW) Attachment 2:

JPATS NAC ADS-B (Out) System Requirements Document for the T-6A Attachment 3:

JPATS NAC ADS-B (Out) Section L Instruction, Conditions, and Notices to Offerors or Respondents

· Attachment L-1: Past Performance Information (PPI) for Offerors

· Attachment L-2: Past Performance Information Questionnaire

· Attachment L-3: Subcontractor/Teaming Partner Consent Letter for the Release of Past and Present Performance Information to the Prime

Contractor

· Attachment L-4: Client Authorization Letter

· Attachment L-5: Cross Reference Matrix

Attachment 4:

JPATS NAC ADS-B (Out) Section M - Tradeoff Evaluation Factors for Award Attachment 5:

JPATS NAC ADS-B (Out) Pricing Matrix Attachment 6:

JPATS NAC ADS-B (Out) Program Work Breakdown Structure for the T-6A Attachment 7:

JPATS NAC ADS-B (Out) Program Work Breakdown Structure Dictionary for the T-6A Aircraft & Aircrew Training Devices Attachment 8: JPATS NAC ADS-B (Out) Schedule of Government Furnished Property

Attachment 9:

JPATS NAC ADS-B (Out) Base Support Agreement Attachment 10:

JPATS NAC ADS-B (Out) Packaging Requirements, AFMC Form 158 Attachment 11:

JPATS NAC ADS-B (Out) Transportation Data for Solicitations, AFMC Form 1653

Attachment 12: JPATS NAC ADS-B (Out) Notional Execution Schedule

Attachment 13: JPATS NAC ADS-B (Out) Test and Evaluation Master Plan (TEMP)

Attachment 14: JPATS NAC ADS-B (Out) Certification Basis

Attachment 15: JPATS NAC ADS-B (Out) Quality Assurance Surveillance Plan

4.5.1.6 Section K - Representations, Certifications, and other Statements of Offerors

The offeror shall provide complete representations, certifications, acknowledgments, and statements. Offerors are reminded to read each representation and certification carefully before answering or completing. The offeror certifies by submission of this offer the assurances in Section K are accurate and true to the best of their knowledge.

4.5.2 Use Of Non-Government Advisors

Offerors are advised that technical and 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: COLSA Corporation.

Offerors shall provide written objection to disclosure as indicated below if the offeror objects to disclosure of a portion of the proposal.

Any objection to disclosure shall be provided in writing to the contracting officer within 10 days of RFP issuance and shall 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 being disclosed to non-Government advisors.

By submitting a proposal in response to this solicitation, the offeror understands and acknowledges that technical and price data submitted to the Government in response to this solicitation may be released to non-Government advisors and is consenting to release of any (unless objection is provided as stated above) proprietary, confidential, or privileged commercial or financial data provided by the offeror in response to this solicitation to non-Government advisors for review and analysis.

4.5.3 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2.

TABLE 2 –SOLICITATION EXCEPTIONS

Solicitation Document Page/ Paragraph Requirement/ Portion Rationale

4.5.4 Other Information Required

4.5.4.1 Authorized Offeror Personnel

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 obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. In addition, provide the name and telephone number of the CEO, Division President, and/or Vice President, as the SSA may require such information for the purpose of notifying successful and unsuccessful offerors of the award decision.

4.5.4.2 Government Offices

Provide the mailing address, telephone and fax numbers, and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

4.5.4.3 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code, CAGE code, DUNS code, TIN, size of business (large or small), and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

4.5.4.4 Attachments to the Model Contract

The offeror shall provide the following as attachments in section J of the model contract:

4.5.4.5 GFP and/or Base Support Requirements

The Government plans to provide the items listed in Attachment 8 to the solicitation as GFP and Base Support as indicated in Attachment 9 to the solicitation. If the offeror requires the use of Government furnished items other than those specified, the offeror shall provide a listing IAW Table 3 below to include quantity, federal stock number, nomenclature, date needed, duration of availability, rental value per FAR 45.1 and 45.2, reason for need, and cross reference to price volume paragraphs which pertain to GFP and/or base support. The offeror shall also provide the written authorization from the cognizant ACO, as applicable. The offeror shall supply this information in the format shown in Table 3. The Government is the ultimate approval authority for the use of GFP not identified in Attachment 8.

TABLE 3—REQUIRED INFORMATION FOR USING GFP/BASE SUPPORT

Stock #

of Need Rental

Value Reason for Need Cross Ref. to Prop

4.5.4.6 Associate Contractor Agreements

Include Associate Contractor Agreements (or Letters of Intent). The Contractor shall use its best efforts to establish agreements with:

a) Beechcraft Defense Company, LLC (Aircraft Original Equipment Manufacturer)

b) FlightSafety Services Corporation (ATD Original Equipment Manufacturer)

c) DynCorp International (Contractor Logistics Support Contractor)

d) COMBS III provider (TBD in CY 18)

4.5.5 Required Attachments

4.5.5.1 Integrated Master Schedule (IMS) The intent of this section is to obtain a functionally integrated understanding of the proposal with clear tracks between the technical, price, schedule, management, etc., in a way that provides the Government confidence that the program is structured to be executable for the resources indicated. The IMS is a detailed task and timing of the work effort and is used as the primary tracking tool for technical and schedule status.

The IMS is an integrated and networked, multi-layered schedule of program/project tasks. The IMS identifies all events, accomplishments, and criteria and the expected dates of each. These dates are based on the calendar dates provided as the starting point and the logical flow of dates provided by calculating the addition of duration of all tasks using typical schedule networking tools. The IMS tasks will be directly traceable to the WBS, SOW, and CLINs.

The offeror shall provide a detailed IMS at the work package and planning package level as part of the proposal submittal. The IMS is intended as a tool for day-to-day tracking of the program/project that rolls up to increasingly higher summary levels. All tasks/activities in the IMS should be logically linked together showing predecessor/successor relationships. The activities and tasks will be sufficient to account for the entire program under contract. Key elements of the IMS include:

a. Milestone/Event A specific definable accomplishment in the program/project network, recognizable at a particular point in time. Milestones and events that shall be included are Contract Award, Post Award Conference, System Requirement Review, System Functional Review, Program Management Reviews, Preliminary Design Review, Critical Design Review, Cockpit Evauation Team, Technology Readiness Review, Technical Interchange Meetings, Contractor Developmental Testing start/complete, First Flight Readiness Review, Material Readiness Assessments, Government Developmental testing start/complete, Government Operational testing start/complete, FAA Certification Completion, Military Airworthiness Completion, Functional Configuration Audit start/complete, Physical Configuration Audit start/complete, Aircraft/ATD Material procurement start/complete, Aircraft/ATD retrofit start/complete, Support Equipment Ugrade start/complete, Aircraft/ATD training Material available, and Aircraft/ATD training events.

b. Activity or Task

A time consuming element, e.g. work in progress between interdependent events, represented in an activity box. Activities are numbered and are contained within an activity box. The left side represents the beginning of the activity and the right side is the completion of the activity.

c. Duration

The length of time estimated to accomplish an activity (disregarding the “calendar impact"). Rationale should also be provided supporting the derivation of the durations including ground rules and assumptions (e.g. historical data, experience on similar efforts, vendor schedules, number of work days per week, number of shifts, company holidays). In addition, the offeror shall provide a supporting narrative for the network diagram that explains the basis for the estimated durations of those activities on the critical path(s) and for activities designated as high risk. Any unusual aspects of their proposed approach to the program shall also be described.

d. Relationships/Dependencies Identifies how predecessor and successor tasks/activities and milestones are logically linked.

· Finish-to-Start (FS) - An activity must finish before another can start. The offeror shall provide a brief narrative for all activities that do not have FS relationships and how the respective relationship was determined and the lead or lag estimated.

· Start-to-Start (SS) - An activity depends on the start of another activity

· Finish-to-Finish (FF) - One activity cannot finish until another activity finishes.

· Start-to- Finish (SF) - An activity cannot finish until another activity starts.

· Percent Complete or Lead Lag.

e. Total Slack or Float

Extra time available on an activity before it will impact another activity on the critical path.

f. Free Slack or Float

Extra time available on an activity before it will impact an activity on another successor activity.

g. Lead

The amount of time of the overlap between where a successor task begins and a predecessor task completes.

h. Lag

The amount of time between the end of a predecessor task and the beginning of a successor task.

i. Critical Path

A sequence of activities in the network that has the longest total duration through the program/project. Activities along the critical path have zero or negative slack/float. It should be easily distinguished on the report formats.

j. Target Start (TS)

Date when an activity should start.

k. Target Complete (TC)

Date when an activity should finish.

l. Actual Start (AS)

Actual start date of an activity.

m. Actual Finish (AF)

Actual finish date of an activity.

n. Early Start (ES)

The earliest date an activity can start.

o. Early Finish (EF)

The earliest date an activity can end.

p. Late Start (LS)

The latest date an activity can start without delaying the program/project target completion date.

q. Late Finish (LF)

The latest finish date an activity can have without affecting the program/project target completion date.

r. Gantt Chart

A graphical display of program activities and key milestones that depict work activities in an integrated fashion. Represent activities by bars showing the length of time for each activity.

s.

Constraints

Limits applied to start and finish dates (e.g. “Finish No Later Than,” “Finish On or Before”).

The offeror shall also provide a resource-loaded Gantt chart for all high-risk areas in the program, including separate charts for critical subcontract efforts. High-risk WBS elements may be explicitly identified by the Government. For each of these high-risk areas, the offeror shall provide minimum and maximum durations for the summary-level activity/WBS. In addition, the offeror shall provide resource-loaded schedules for other risk (low to moderate) areas that are unique to their proposal based on offeror’s analysis. The resource loading shall be represented by functional hours for labor and by material content. These hours shall be time phased by quarter with a recurring/non-recurring breakout for each quarter using the attached resource loaded Gantt chart.

Section L Attachment 1 (L-1) Past Performance Information (PPI) for Offerors

Offerors must use the PPI Tool provided in the solicitation in order to electronically submit…