MSBRS SIR Section L - Amendment 0002.docx

TABLE OF CONTENTS

Contract Number: XXXX Section L: Instructions, Conditions, and Notices to Offerors

CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (AMS 3.1-1)

This Screening Information Request (SIR) or solicitation, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make the full text available or Offerors and contractors may also obtain the full text via the Internet at http://conwrite.faa.gov. On this web page, select "Download All” and then “Download”.

CLAUSES AND PROVISIONS INCORPORATED BY FULL TEXT

3.2.2.3-20 Offers (January 2018)

(a) The offeror (you) must submit responses to this SIR in accordance with Section L.4.

(b) Such offers must refer to this SIR and include, as applicable, the item or sub-items, quantities, unit prices, time and place of delivery, all representations and other information required and a statement specifying the extent of your agreement with all the FAA's (we) terms, conditions, and provisions.

(c) We may decline to consider offers that do not include required information, or that reject any of the terms, conditions and provisions of the SIR.

(d) Send your offer to the address(es) specified in Section L.4.

(e) We will not be responsible for any failure attributable to transmitting or receiving the offer, unless it falls under section (a) of AMS provision 3.2.2.3-14 "Late Submissions, Modifications, and Withdrawals of Submittals".

3.2.2.3-22 Period for Acceptance of Offer (October 2014)

The offeror (you) agrees if this offer is accepted within 365 calendar days from the date the SIR specifies for receiving offers, to provide all items for which you offer prices at the price set opposite each item, delivered at the designated point(s), within the time specified in the Schedule.

3.2.2.3-38 Requirements for Certified Cost or Pricing Data or Other Information (July 2010)

Offerors (you) may submit certificates of current cost or pricing data (CCCPD) or you may request an exception to this requirement. Depending on the option you use, you must submit either the CCCPD shown in paragraph (e) of clause 3.2.2.3-39, "Requirements for Certified Cost or Pricing Data or Information - Modifications" (the clause) or request an exception consistent with the information in the clause. Any information in the clause regarding the CCCPD or the exception that is relevant to an offer is incorporated into this provision.

3.2.2.3-38 Alternate I Requirements for Certified Cost or Pricing Data or Other Information (July 2010)

(c) Submit the cost proposal electronically by e-mail to HYPERLINK "mailto:craig.mayo@faa.gov" craig.mayo@faa.gov.

3.2.2.3-38 Alternate II Requirements for Certified Cost or Pricing Data or Other Information (July 2010)

(a) The FAA does not require certified cost or pricing data.

(b) The offeror must provide the following information: Please refer to L.22 for details.

3.2.4-1 Type of Contract (April 1996)

The FAA contemplates award of a IDIQ contract with Cost Plus Fixed Fee (CPFF), Firm Fixed Price (FFP), Time and Materials (T&M), and Cost Reimbursement (CR) Task Orders resulting from this Screening Information Request.

3.6.1-17 North American Industry Classification System (NAICS) Code (January 2016)

The North American Industry Classification System (NAICS) code for this procurement is:

334511 - Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing.

The small business size standard as defined by the Small Business Administration is the following:

For NAICS codes based on annual receipts, the annual average receipts for the last three fiscal years cannot exceed ___N/A____.

For NAICS codes based on the number of employees, the average number of employees over the last twelve-month period cannot exceed ___1,250__.

3.9.1-3 Protest (October 2011)

AS A CONDITION OF SUBMITTING AN OFFER OR RESPONSE TO THIS SIR (OR OTHER SOLICITATION, IF APPROPRIATE), THE OFFEROR OR POTENTIAL OFFEROR AGREES TO BE BOUND BY THE FOLLOWING PROVISIONS RELATING TO PROTESTS:

(a) Protests concerning Federal Aviation Administration Screening Information Requests (SIRs) or awards of contracts shall be resolved through the Federal Aviation Administration (FAA) dispute resolution system at the Office of Dispute Resolution for Acquisition (ODRA) and shall be governed by the procedures set forth in 14 C.F.R. Parts 14 and 17, which are hereby incorporated by reference. Judicial review, where available, will be in accordance with 49 U.S.C. 46110 and shall apply only to final agency decisions. A protestor may seek review of a final FAA decision only after its administrative remedies have been exhausted.

(b) Offerors initially should attempt to resolve any issues concerning potential protests with the Contracting Officer. The Contracting Officer should make reasonable efforts to answer questions promptly and completely, and, where possible, to resolve concerns or controversies. The protest time limitations, however, will not be extended by attempts to resolve a potential protest with the Contracting Officer.

(c) The filing of a protest with the ODRA may be accomplished by mail, overnight delivery, hand delivery, or by facsimile or if permitted by order of the ODRA, by electronic filing. A protest is considered to be filed on the date it is received by the ODRA during normal business hours. The ODRA's normal business hours are from 8:30 am to 5:00 pm Eastern Time (ET).

(d) Only an interested party may file a protest. An interested party is one whose direct economic interest has been or would be affected by the award or failure to award an FAA contract. Proposed subcontractors are not "interested parties" within this definition.

(e) A written protest must be filed with the ODRA within the times set forth below, or the protest shall be dismissed as untimely:

(1) Protests based upon alleged improprieties in a solicitation or a SIR that are apparent prior to bid opening or the time set for receipt of initial proposals shall be filed prior to bid opening or the time set for the receipt of initial proposals.

(2) In procurements where proposals are requested, alleged improprieties that do not exist in the initial solicitation, but which are subsequently incorporated into the solicitation, must be protested not later than the next closing time for receipt of proposals following the incorporation.

(3) For protests other than those related to alleged solicitation improprieties, the protest must be filed on the later of the following two dates:

(i) Not later than seven (7) business days after the date the protester knew or should have known of the grounds for the protest; or

(ii) If the protester has requested a post-award debriefing from the FAA Product Team, not later than five (5) business days after the date on which the Product Team holds that debriefing.

(f) Protests shall be filed at:

(1) Office of Dispute Resolution for Acquisition Federal Aviation Administration 800 Independence Ave., S.W.

Room 323 Washington, DC 20591

Telephone: (202) 267-3290 Facsimile: (202) 267-3720; or

(2) Other address as specified in 14 CFR Part 17.

(g) At the same time as filing the protest with the ODRA, the protester shall serve a copy of the protest on the Contracting Officer and any other official designated in the SIR for receipt of protests by means reasonably calculated to be received by the Contracting Officer on the same day as it is to be received by the ODRA. The protest shall include a signed statement from the protester, certifying to the ODRA the manner of service, date, and time when a copy of the protest was served on the Contracting Officer and other designated official(s).

(h) Additional information and guidance about the ODRA dispute resolution process for protests can be found on the ODRA Website at http://www.faa.gov.

3.14-8 Non-FAA Information Systems (July 2017)

(a) For all non-FAA Information systems (including those from cloud services providers) to be used under this contract, offerors must disclose with their proposal all countries where FAA data and information is to be stored, processed, backed up to, or if the data and information is transmitted through an international processing hub or exchange.

(b) Offerors must disclose to the FAA with their proposal, the country of ownership (if more than 50% foreign-owned) for all subcontractors and third parties that will process, store, or backup the data and information.

(c) If an international processing hub or exchange is involved or there are foreign-owned subcontractors or third parties, offerors must provide to the FAA with their proposal, the details of the security measures for how the contractor, subcontractor, and third party processing facilities will protect the FAA data and information at the subcontractor or third party processing facility.

PROJECTED MILESTONE SCHEDULE

The following represents the anticipated procurement milestone as of the SIR release date. This schedule is for planning purposes only and is subject to change:

TIME, DATE, PLACE, AND SUBMISSION OF PROPOSALS

The following information applies for the time, date, place and submission of proposals:

· TIME AND DATE: Proposals must be received by the Contracting Officer at the mailing/delivery address identified below no later than 4 p.m. ET on October 19, 2018.

· MAILING/DELIVERY ADDRESS: Proposals must be hand-carried, mailed, or delivered by courier or Express Mail to the Contracting Officer at the following address:

Federal Aviation Administration ATTN: Craig Mayo, Contracting Officer 600 Independence Ave SW Wilbur Wright Building (10B) Suite 4W42HS Washington, DC 20591

(202) 267-0773

· PROPOSAL VALIDITY PERIOD: Proposals are valid for a period of 365 days after receipt of offer.

· ELECTRONIC COPIES: An electronic file must be provided on a flash drive for each proposal volume and included within the original of each volume.

· QUESTIONS: Any questions or requests for clarifications concerning any aspect of the SIR must be prepared in writing, utilizing the attached Comment/Question Matrix, and submitted to the Contracting Officer via email to craig.mayo@faa.gov and Contract Specialist, krystalyn.stuhr@faa.gov no later than 4 p.m. ET on August 14, 2018. Verbal communication will not be entertained. Questions must make reference to the applicable page number, section, and paragraph of the SIR. Offerors’ questions and the responses by the Federal Aviation Administration (FAA) may form the basis of an amendment to the SIR.

· SIGNED ORIGINALS: One copy of the proposal must contain the signed original of all documents requiring signature by the Offeror. Use of reproductions of signed originals is authorized for all other copies of the proposal. The proposal must be signed by an Offeror’s duly authorized representative with the authority to obligate the company to this proposal.

· PROPOSAL SUBMISSION: Offerors assume full responsibility for ensuring that proposals are received at the place and by the date and time specified above.

EXPENSES RELATED TO OFFEROR SUBMISSIONS

The FAA is not responsible for, and will not pay or reimburse, any costs incurred by the Offerors in the development or submission of any aspect of their proposals under this SIR. This includes any costs associated with the following:

· Any aspect of the proposal activity.

· Research, studies, or designs conducted for the purpose of incorporation into any part of the proposal.

· Acquiring or contracting for any services or products relating to the offer under this SIR.

· Any costs related to Eligibility for Consideration as described in Section L.7.

· Operational capability demonstration activities described in Sections L.9.

AWARD SELECTION

The FAA intends to select one Offeror for contract award.

ELIGIBILITY FOR CONSIDERATION

The FAA will perform an initial screening to identify proposals that will continue through the evaluation. To be considered for this procurement, the Offeror must:

· Demonstrate that its proposed monopulse Mode S system is currently operational and in use by an Air Navigation Service Provider (ANSP) to provide civilian Air Traffic services and separation of aircraft, or is derived from that operational production baseline. See Attachment J-20 for a list of applicable ANSPs.

· Provide the locations of their operational system(s), identify the ANSP(s) utilizing the system, and a point of contact within the ANSP for the FAA to validate this information.

Each Offeror must submit one proposal containing only one technical solution.

DETERMINATION OF RESPONSIBILITY

To be eligible for award, an Offeror must be determined by the Contracting Officer to be a responsible contractor in accordance with the FAA Acquisition Management System (AMS), Section T.3.2.2.7 – Contractor Qualifications. The FAA will consider the elements identified below to determine a potential contractor’s responsibility. Offerors must provide substantiating information to support their assertions as described in Section L.23.6. Failure to provide the requested information with the proposal submission will eliminate the Offeror from consideration for award.

In accordance with AMS Section T.3.2.2.7, a responsible contractor:

(1) Has or can obtain adequate financial resources to perform a contract;

(2) Has the ability to meet any required or proposed delivery schedules;

(3) Has a satisfactory performance history;

(4) Has a record of integrity and proper business ethics;

(5) Has appropriate accounting and operational controls that may include, but are not limited to:

(a) Production control;

(b) Property control systems;

(c) Quality assurance programs;

(d) Appropriate safety programs; and

(6) Is qualified and eligible to receive an award under applicable laws or regulations.

To demonstrate its responsibility to perform the MSBRS contract, an Offeror must provide documentation to substantiate it has:

· Experience as an operating business entity for a minimum of five (5) years.

· Contractor Purchasing System that describes company processes utilized in its procurement of goods and services. If the system has been reviewed and approved by the cognizant Defense Contract Management Agency (DCMA) Administrative Contracting Officer, the Offeror must provide a copy of their letter of system adequacy.

· The contractor’s accounting system must be adequate for determining costs applicable to the contract. Offerors must submit verification from the Defense Contract Audit Agency (DCAA), the Defense Contract Management Agency (DCMA), any federal civilian audit third-party Certified Public Accounting (CPA) firm of an accounting system that has been audited and determined acceptable for the award of a prospective cost-reimbursement contract. In the event the verification is from a third-party CPA firm, the verification letter shall be on the letter head of the third-party CPA firm, and certified by a certified public accountant. The FAA reserves the right to perform an audit of an Offeror’s accounting system prior to potential award.

· Signed agreement(s) or letter(s) of intent with all proposed major subcontractors, binding the subcontractor(s) for the performance of the proposed work.

· Financial statements or publicly available annual reports for the last three (3) fiscal years of business for the corporation, and for any affiliate, subsidiary, or division proposed to perform work delineated in Section C for which separate financial records are maintained. Financial statements should include the following: balance sheet, profit and loss statements, statement of cash flow, and statement of retained earnings.

In the event an Offeror is deemed non-responsible, that Offeror will be notified and removed from participation in this procurement.

Operational Capability Demonstration (OCD) The Government will conduct OCDs at the FAA William J. Hughes Technical Center’s (WJHTC) Elwood Experimental En Route Facility, located in Elwood, NJ. A separate OCD will be conducted for each Offeror meeting the “Eligibility for Consideration” criteria defined in Section L.7. Participation in the OCD is mandatory. Offerors refusing or unavailable to participate in an OCD will be removed from further consideration. Eligible Offerors will be contacted by the Government to schedule a mutually acceptable date for conduct of their OCD. It is the Government’s intent to schedule each OCD no earlier than 30 days after initially contacting the Offeror. OCDs will be conducted no earlier than 45 days after the SIR response due date. A maximum of three weeks will be allocated for each OCD. During this period, Offerors must install their system, perform any necessary optimization, support conduct of the OCD, and remove their system from the FAA facility. OCD conduct is expected to take no more than five business days.

As part of the OCD, Offerors must install, optimize, and demonstrate their system at the WJHTC (see Attachment J-34 OCD Plan for further details). The Government will supply the Aircraft Capacity and Environment Simulator (ACES) tool and antenna sub-system for conduct of the OCD. The Government will provide power, grounding, facilities and local resources for Offeror access. In support of the OCD, the Offeror must:

· Provide a fully configured, production representative system meeting the requirements contained in the current System/Subsystem Specification (SSS) submitted as part of their proposal.

· Provide qualified personnel to install, optimize, and operate the system in support of OCD conduct in accordance with the OCD Plan (Attachment J-34).

· Remove their system at the conclusion of the OCD.

· Cover all costs they incur as a result of participation in the OCD.

· Provide any equipment required to convert the Government supplied ACP/ARP signals to a format that is compatible with their system.

· Provide all cabling and adapters required to interface their system with the Government provided equipment in accordance with the OCD Plan (Attachment J-34).

· Provide all tools necessary to generate and parse the system data recordings captured during conduct of the OCD.

· Provide electronic copies of all raw and fully parsed system data recordings generated during conduct of the OCD in the same format as the sample data provided as part of their proposal (see Section L.19.2.6.5).

Recordings and observations generated during the OCD will be analyzed and documented by the Government to assess maturity of the system in meeting the performance parameters defined in the OCD Plan.

If invited to participate in an OCD, the Government will contact Offerors to schedule the OCD. When contacted by the Government, the Offeror must provide any additional information in support of the OCD which includes, but is not limited to, names/information of Contractor participants and any other system specific information needed by the Government. Vendors participate at their own risk and the FAA assumes no liability for any damages or losses the vendors may incur as a result of their participation.

COMMUNICATIONS WITH OFFERORS AFTER CLOSING DATE OF SIR

Communications with potential Offerors may take place throughout the evaluation process. Any information obtained during communications may be used to clarify, substantiate, or validate information provided in an Offeror’s proposal. Offerors should not assume that they will be contacted or afforded an opportunity to clarify or discuss their proposals. Therefore, Offerors are instructed to submit proposals with the most favorable terms possible regarding all evaluation factors.

Certain topics of communication may necessitate amendments to the SIR. If this is the case, all competing Offerors will be advised of the changes via amendments to the SIR, and the Contracting Officer will establish common cut-off dates for any and all resulting Offeror revisions should any be requested. Any communications with one Offeror that could pertain to other Offerors, or which could provide information useful to all, will be communicated to all Offerors.

The FAA may hold one-on-one meetings with individual Offerors and one-on-one communications may continue throughout the process, as required, at the FAA’s discretion. Communications with one Offeror does not necessitate communications with other Offerors.

NON-GOVERNMENT PERSONNEL PARTICIPATION

Offerors are notified that the FAA may have any written proposals or other written information provided in response to this acquisition reviewed by personnel from various support contractors who may serve as advisors, Subject Matter Experts (SME) or as evaluators for the FAA during the evaluation phase of this acquisition. All non-Government personnel will have signed non-disclosure and no conflict-of-interest statements before the evaluation process begins. The exclusive responsibility for source selection will remain with the FAA.

The following companies may be utilized as participants in this process:

· A3 Technology

· Arctic Slope Regional Corporation (ASRC)

· Aurora Sciences LLC

· Booz Allen Hamilton

· BVTI, Inc.

· Constellation Aviation Solutions LLC

· CSRA, Inc.

· DTIS-Corp LLC

· Enterprise Technology Solutions

· ETEK

· Evans Incorporated

· Grant Thornton LLP

· Human Solutions Inc.

· IncaTech, Inc.

· JEP3 Consulting Group

· MCR LLC

· Regulus Group LLC

· S & K Global LLC

· Strieyder LLC

· Wein and Associates

EVALUATION PROCESS

During the evaluation process, the FAA will evaluate each Offeror’s proposal. The FAA will evaluate each Offeror’s capability to perform the effort required by this SIR, as provided by the Offeror in the following proposal volumes:

1. Technical Proposal (Volume I)

2. Past Performance (Volume II)

3. Management Proposal (Volume III)

4. Price Proposal (Volume IV)

5. Other Documentation (Volume V)

INITIAL COMPLIANCE REVIEW

Offerors must comply with all instructions in Section L when developing proposals. Failure to comply with the instructions may result in a determination that the Offeror’s proposal is noncompliant. This determination will be made at the sole discretion of the Government.

INFORMATION OF AWARD

Written notice to unsuccessful Offerors and contract award information will be promptly provided upon contract award.

GENERAL SIR INSTRUCTIONS

Replies to this SIR must follow the outlines and instructions provided throughout Section L. In addressing the requirements of Section L, Offerors are instructed to ensure that all aspects of the evaluation factors in Section M are addressed.

Proposals should be specific enough to provide the FAA with all required information to evaluate the technical and financial ability of the Offeror to perform the SIR requirements. The proposal must not merely offer to perform work in accordance with the SOW, but must provide a detailed response of the actual approach and solution proposed. Proposals that repeat the information contained in the SOW without sufficient details or that use nonspecific phrases such as “in accordance with standard procedures” or “in accordance with well-known techniques” may be deemed unacceptable.

Omission of information may be considered grounds for eliminating a proposal from further consideration.

PROPOSAL ORGANIZATION

The Offeror’s proposal submission must consist of Volume I – Technical Proposal, Volume II – Past Performance, Volume III – Management Proposal, Volume IV – Price Proposal and Volume V – Other Documentation. Each hard copy submittal must be labeled as an original or copy. The volumes must be organized as follows:

Subfactor 1 - System Engineering Design and Development Subfactor 2 - System Maturity[footnoteRef:2] [2: Please see Section L.9 – Operational Capability Demonstration, Section L.19.2.6.5 – System Maturity Support Information, and Section L.18.2 – Electronic Copies of Proposals for System Maturity instructions. ]

Subfactor 3 - System Test and Evaluation Subfactor 4 - Implementation and Activation Subfactor 5 - Lifecycle Support

2. Systems Engineering Management Plan

3. System/Subsystem Specification

4. Proposal Compliance Matrix

5. System Maturity Support Information[footnoteRef:3] [3: System Maturity Support Information must be submitted only in electronic format via a flash drive as specified in Section L.18.2. Hard copies are not permitted]

6. Frequency Transmit Authorization

N/A

Subfactor 1 - Program Management Subfactor 2 - Draft Integrated Master Schedule (IMS)[footnoteRef:4] [4: Please see Section L.21.2.5.1– Draft Integrated Master Schedule for draft IMS instructions]

Subfactor 3 - Offeror’s Risk, Issue, and Opportunity (RIO) Subfactor 4 - Earned Value Management (EVM) System

2. Resumes

N/A

2. Labor Category Crosswalk

3. Section B.5 Pricing Tables

4. Forward Pricing Rates

5. CAS Disclosure Statement

** Volume IV - Section I and Appendices to be submitted in soft copy electronic file only.

COST/PRICE DATA

Volume IV must be submitted separately from all other volumes in a sealed package marked “Volume IV – Cost/Price Proposal.” Subcontractor information of a proprietary nature may be provided within the Prime’s proposal submission in sealed packages appropriately marked. If subcontractor sealed packages require the use of passwords to open, the passwords must be submitted directly to the Contracting Officer.

Pricing data must not be included within any other volume and, if included within other volumes, that data will be discarded and excluded from the evaluation. Data beyond that required by this instruction shall not be submitted, unless it is considered essential to document or support the cost/price position.

PROPOSAL PREPARATION INSTRUCTIONS

Replies to this SIR must follow the outlines and instructions concerning the format given in this section, as well as other sections of Section L. Paper and electronic copies of proposals will not be returned to Offerors.

Format and Structure Proposals must comply with the following guidelines:

· Paper Size: 8.5” x 11” paper – each side of a sheet of paper must constitute one (1) page

· Margins: 1” inch

· Spacing: Single-spaced

· Font: Times New Roman, 12 point. Text embedded within graphic, diagrams, or tables must not be smaller than 10 point.

· Packaging: Offerors are instructed to package each volume into a three-ring binder and label with a title. Section L.16 defines the number of hard copies required per volume. All originals and copies must be numbered (e.g., Volume I – Original, Volume I – Copy 1 of N.)

· Cover Letter: Offerors must provide a cover letter signed by an authorized company official for all volumes.

· Table of Contents & Tabs: Offerors must include a table of contents with each volume and tab indexing to identify proposal sections within each volume.

· Foldouts: Foldouts are permitted for Volumes I, III, and IV, which will not count against the page limit. Only five foldouts are permitted per volume (including appendices), they must fold entirely within the volume, and must not exceed 11” x 17” in size. Offerors are instructed not to use foldout pages for text.

· Glossary: Offerors must include a glossary of acronyms and abbreviations in each volume, with an explanation for each. The glossary must not be used to define techniques and approaches and will not be evaluated.

· Page Count: The table of contents, volume covers, cover letters, tabs, title pages, assigned appendices and glossary of acronyms or abbreviations will not count toward the page limit.

Electronic Copies of Proposals Offerors must submit an electronic file for Volumes I, II, III, and V on a flash drive in addition to the paper copies specified in Section L.16. Volume IV is the only volume that must be on a separate flash drive. The Offeror must include all flash drives with the “original” paper copy of each volume as identified in the SIR. Offerors are instructed to ensure that the files submitted are “virus-free” prior to submission. Offerors’ electronic submittals must be compatible with the following equipment and software products:

· Microsoft Office 2016 (e.g., Excel, Word, PowerPoint)

· Microsoft Project 2016

· Adobe Acrobat Reader 11.0 Offerors are instructed to ensure that the electronic copy of the proposal is an exact duplicate of the original paper proposal. The Offerors must submit any MS Excel spreadsheets in a format that allows formulas within the spreadsheets to be reviewed and manipulated. If there are discrepancies between the electronic proposal and the original paper proposal, the paper original will be deemed the correct version.

Label Information with Restricted Disclosure Offerors who include information in their proposal that they do not want to disclose to the public or be used by the FAA, except for evaluation purposes, must mark the title page with the following footer:

This proposal includes information that must not be disclosed outside the FAA and its representatives and must not be duplicated, used, or disclosed in whole or in part for any purpose other than to evaluate this proposal.

Offerors must mark each sheet of restricted data with reference to the title page. However, Offerors are warned that this restriction does not limit the FAA’s right to use the information if it is obtained from another source without restriction.

VOLUME I TECHNICAL PROPOSAL – Not to Exceed (NTE) 200 Pages Offerors are instructed to provide information for each of the sections described below in the Technical Proposal. Offerors must fully substantiate an approach that is sound, complete, valid and achievable; demonstrate an understanding of the requirements, and address all requirements of the Technical Proposal.

The Technical Proposal must consist of the Offeror’s proposed approach for addressing the technical and support aspects of the acquisition. It should indicate the Offeror’s capabilities and the means to be used to satisfy the requirements of the SIR in its entirety. It will be evaluated in accordance with Section M and it should be specific and complete in detail. The proposal must provide a straightforward explanation of what it is the Offeror will do to satisfy all requirements of the SIR.

Executive Summary This section must provide a summary of the following information:

· Key elements, unique features, and benefits (excluding price) of the Offeror’s proposed approach and plans to fulfill the requirements in the SIR.

· Potential risks and mitigation strategies.

· Major milestones.

Technical Proposal (Volume I, Section I) The Technical Proposal must clearly address the evaluation criteria in Section M and the requirements of the SIR. It must be presented in as much detail as practical and include principles and techniques which may be applied in performing the work, and an explanation of the various methods considered and substantiation of those selected. The Offeror must discuss risk, issues, opportunities, and any associated mitigation strategies throughout the Technical Proposal.

Systems Engineering Design and Development – Subfactor 1 The Offeror must provide a detailed description of their systems engineering design and development approach, including:

1) How the proposed MSBRS architecture satisfies the functional and performance requirements specified in FAA-E-7716 (Attachment J-5). The Offeror must complete the System Specification Technical Requirements Crosswalk (Attachment J-23) to trace FAA-E-7716 requirements to the Offeror’s System/Subsystem Specification requirements to identify the extent of architecture, hardware, and software modifications required.

The Offeror must provide an overview of any enhanced capabilities associated with their system and identified in the Offeror System Specification Technical Requirements Crosswalk (See Section L.19.2.6.1). Enhanced capabilities are defined as capabilities that exist within the Offeror’s core system and are not defined in FAA-E-7716 that would pose potential benefits to the NAS. Enhanced capabilities pertaining to Mode-5 or datalink levels 3/4/5 will not be evaluated or assessed by the FAA. The FAA reserves the right to identify additional enhanced capabilities that will not be evaluated or assessed during the SIR evaluation. Enhanced capabilities may be identified as opportunities, but will not count towards the technical subfactor score.

2) Engineering Process, which defines:

a. An approach for planning, controlling, and conducting a fully integrated engineering effort to meet the MSBRS System Specification.

b. Systems engineering processes to ensure the integrity of the MSBRS interface design, information security, and human engineering aspects.

c. System safety risks and mitigation strategies.

3) Software Engineering and Development Process, which defines:

a. Approach for allocation of requirements to COTS, newly developed code, prototype software, and/or modified existing code, and all aspects of software life cycle processes to include planning, development, verification, configuration management, and quality assurance, including RTCA/DO-278A AL5.

b. How the proposed software design elements will ensure effective delivery of the MSBRS, lead to certifiable software delivery, and address all aspects of the software life cycle process; and describe its software development organization and its methodology for project tracking, quality control and oversight.

c. Approach to interface with existing NAS systems, including CARSR, ASR-9, STARS, ERAM and RMMS/RMLS, that is achievable and ensures data and performance integrity.

4) Plans and process to develop and implement a security program to address information/data security needs and considerations for the security requirements in the MSBRS System Specification.

5) Human Factors Engineering and Development Process, which details:

a. The Human Factor design standards and approaches that were utilized in the development of the proposed Maintenance and Air Traffic Terminals.

b. An assessment of the development/redesign required for the Offeror’s proposed Maintenance and Air Traffic Terminals to comply with the FAA Human Engineering requirements defined in FAA HF-STD-001 and HF-STD-003F.

6) The Offeror must address each of the following Technical Scenarios:

a. Describe capabilities within your system for reducing transponder occupancy and controlling FRUIT.

b. Describe what features your system has for minimizing false targets and avoiding interference with other sensors.

c. Describe how your system utilizes ADS-B information to reduce 1030/1090 MHz congestion.

System Maturity – Subfactor 2 Please see Section L.9 – Operational Capability Demonstration and Section L.19.2.6.5 – System Maturity Support Information, and Section L.18.2 – Electronic Copies of Proposals for System Maturity instructions.

System Test and Evaluation – Subfactor 3 The Offeror must provide a detailed description of their system test and evaluation approach, including:

1) Proposed test program, including major components, processes, procedures, and the tests necessary to validate that the MSBRS meets the system design and performance requirements as delineated in FAA-E-7716 and the test program defined in the SOW. This includes resource allocation, test staffing, facilities, equipment, and test tools to ensure achievement of test planning and conduct in accordance with required schedules.

2) Planned sequence of test activities by phase (e.g., development (in-plant and on-site), production acceptance and site acceptance test), including test events, test locations, durations, interdependencies, and integration of subsystems.

3) A description of all test tools, both hardware and software, required to complete the proposed test program, including a detailed discussion of the capabilities of the RF target/FRUIT simulator that will be provided by the Offeror. This description must identify and discuss, in detail, any test tool development required to meet test program needs. The Offeror must provide an assessment of the effort associated with any required test tool development and validation.

4) Specific test methodologies to be employed (demonstration, test, analysis, inspection, test with data, and design review) to verify that all FAA-E-7716 requirements are met.

5) Quality assurance and configuration management processes to be used for testing throughout the contract.

6) Regression testing processes to effectively address system deficiencies, anomalies, and test failures.

Implementation and Activation – Subfactor 4 The Offeror must describe in detail how they will deliver implementation and activation support, including:

1) Plans, processes, and schedule (including assumptions) for site preparation, installation, integration, optimization, site testing, and acceptance for implementation of the MSBRS system at all operational site configurations. This includes plans for integrating and prioritizing Government airport and contractor activities to meet or exceed planned schedules.

2) Plans and processes to address implementation requirements based on the MSBRS implementation process flow (see Attachment J-24).

3) Integration of the MSBRS into an operational environment while minimizing impacts to Air Traffic and local airport operations (e.g., radar downtime or no radar coverage) in support of MSBRS implementation.

Lifecycle Support – Subfactor 5 The Offeror must describe in detail how they will implement and sustain lifecycle support by addressing the following:

1) Plans for developing a component-level training program that ensures personnel responsible for maintenance and certification on equipment used in the NAS are proficient in performing their assigned duties.

2) Process for providing second level engineering support in accordance with the MSBRS maintenance concept, and to organize those functions in a manner that can be sustained for the system lifecycle.

3) Plans for managing and providing required supply support functions (e.g., stocking, storing, issuing, and shipping expendable and repairable items, and a process for diagnosis, repair, inspection and certification of failed LRUs), including Interim Contractor Depot Level Support (ICDLS).

4) Plans and process to transition Interim Contractor Depot Level Support and second level engineering functions, along with associated data, to the FAA.

Appendices – No Page Limit VRTM and Offeror System Specification Technical Requirements Crosswalk (Volume I, Appendix 1) The Offeror must provide a crosswalk between the MSBRS Verification Requirements Traceability Matrix (VRTM) and the Offeror’s current System/Subsystem Specification (SSS). The crosswalk must identify which MSBRS requirements are currently met by the Offeror’s proposed system and which ones require development. The Offeror must identify any current SSS requirements that specify enhanced system capabilities associated with their system. The Offeror must utilize the L-2 Technical Requirements Crosswalk (Attachment J-23) for completing the crosswalk. The spreadsheet must be completed in accordance with the Instruction tab in the spreadsheet.

Systems Engineering Management Plan (Volume I, Appendix 2) The Offeror must provide the Systems Engineering Management Plan (SEMP) that was developed in support of their proposed system, as part of their proposal.

System/Subsystem Specification (Volume I, Appendix 3) The Offeror must provide their current SSS that was developed in support of their proposed system, as part of their proposal. Contractor format is acceptable.

The Offeror must include requirements within their current SSS that fully define all capabilities of the proposed system, including those capabilities that exceed the requirements in FAA-E-7716 (Attachment J-5). The Offeror’s price proposal must separately address the additional price associated with full verification of the requirements associated with each individual enhanced system capability. At the post-award conference, the Government will identify which, if any, enhanced capabilities and requirements from the Offeror’s current SSS that the Offeror must fully verify as part of the formal test and evaluation program.

Proposal Compliance Matrix (Volume I, Appendix 4) Offerors must develop a matrix which shows the traceability between sections of the SIR and all volumes of their proposal. The matrix should clearly identify where requirements are addressed in their proposal, including all volumes of the Offeror’s proposal, CLINs, and SIR Sections C, L, and M. The traceability matrix must be included in the appendix of the Technical Proposal. Include page numbers and the applicable section in the matrix.

System Maturity Support Information (Volume I, Appendix 5) Inn support of the OCD, the Offeror must submit sample system data recordings collected on their proposed system while operating in either a live or simulated environment over a minimum of 30 contiguous minutes. Simulated targets must continuously perform maneuvers that imitate airborne fixed-wing aircraft, no stationary targets are allowed. Submitted recordings must contain simultaneously captured internal plot output, interrogation, and reply data as well as disseminated plot data recorded at the surveillance user output. A minimum of 100 targets in a mix that includes Mode S (both RTCA/DO-181E and RTCA/DO-260B compliant) and ATCRBS must be present in the recordings. Interrogation and reply data must include all roll-call, all-call Mode 2, Mode 3/A, and Mode C interrogations generated by the system as well as all received replies. Recordings must include at least one ATCRBS and one Mode S target replying to Mode 2 interrogations over a minimum of 50 contiguous scans; this requirement does not have to be met simultaneously for the two targets. All recordings must be provided in the format generated by the system and in fully parsed Comma Separated Value (.csv) format. The Offeror must provide documentation that defines the contents of each column in all .csv files.

The Offeror must submit all documentation necessary for the FAA to parse and interpret all messages and fields within the recordings. The format of all messages in the submitted sample recordings must identically match those that will appear in recordings generated during conduct of the OCD.

The Offeror must also submit documentation identifying the physical space, grounding, and power requirements of their proposed system. This information will be utilized to prepare the OCD facility for installation of the system.

All electronic files and documentation specified in the paragraphs above must be submitted to the FAA via a flash drive as specified in Section L.18.2. There must be a file on the flash drive titled “TOC.doc” describing the contents of each file. Hard copies are not permitted for System Maturity Support Information. These recordings will be utilized by the FAA to develop test tools to support analysis of data collected during the OCD.

Frequency Transmit Authorization Information (Volume I, Appendix 6) The Offeror must complete and submit the Frequency Transmit Authorization Questionnaire (Attachment J-44) as part of their proposal.

VOLUME II PAST PERFORMANCE – No Page Limit Past Performance Descriptions The Offeror must submit three (3) past performance descriptions, ongoing or completed within the past five (5) years, for contracts of similar scope and complexity as the MSBRS Program requirements, including implementation and support requirements. Past Performance descriptions for major subcontractors may be provided in lieu of a Prime Offeror reference for the subject matter for which the subcontractor is being proposed. No more than one reference can be for a subcontractor.

In the absence of relevant past performance as defined above, the Prime Offeror may submit three (3) recent past performance descriptions closest to the MSBRS Program requirements, as defined in this SIR.

It is incumbent upon the Offeror to explain the relevance of the past performance information provided. It is not the responsibility of the FAA to search for information to correct problems in the past performance descriptions. The burden of providing thorough and complete past performance information remains with the Offeror.

Past Performance Description Format The Offeror must submit the information defined in Sections I and II below for each past performance description. The information provided must also be listed in Attachment J-25, Past Performance List, providing contract and contact information, so that the FAA may review and discuss this with the customers for each contract.

I. Product or Program Description, Points of Contact and Key Personnel:

· Company Name

· Company Role: Prime or Subcontractor

· Program Title

· Name of Customer

· Customer Address

· Reference: Telephone and Email of Contracting Officer and Program Manager that can be traced to the past performance survey

· Contract Number

· Contract Type(s)

· Period of Performance

· Contract Dollar Value

· Number of Systems (as applicable)

· Key Personnel: Name key personnel proposed for the MSBRS Program who were also involved in this contractual effort. Describe their roles and responsibilities.

· Description of Effort: Describe the characteristics of the program that make it relevant for comparison with the MSBRS SIR requirements, including products and services. Describe the scope, complexity and type of development, production and implementation efforts, number of installations, etc. Be specific as to your company’s role and/or the role of Subcontractors. Describe other operational and technical aspects of this contractual effort considered unique or especially noteworthy, especially where these may be applicable to MSBRS. Describe accomplishments and benefits/value delivered to the Customer.

II. Contract Performance:

A. Quality

1. Describe operational or technical requirements, which were exceeded or not met, and the role these requirements played in the overall product or service

2. Of requirements satisfied, were they as originally specified or as subsequently changed?

3. Describe actions taken to exceed requirements or to remedy unmet requirements

4. Identify any engineering methods, tools and activities related to the above performance that will be used on the MSBRS

5. Steps taken to correct and prevent performance problems B. Timeliness

1. Original Completion Dates for Major Contract Milestones

2. (Current) Scheduled Completion Dates for Major Contract Milestones

3. Estimated or Actual Completion Dates for Major Contract Milestones

4. Number of Times Each Major Milestone changed and reason(s) for change(s)

5. Steps taken to correct and prevent delivery schedule problems C. Cost Control

1. Initial Contract Value

2. For Ongoing Contracts: Current value and estimate at completion

3. For Completed Contracts: Final value.