SMR4 Section L - Instructions to Offerors Final.pdf

SIR 693KA7-25-R-00001

Surface Movement Radar, Model 4 (SMR4)

Section L

L - 1

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

Table of Contents

L.1 POINTS OF CONTACT

L.2 AMS 3.1-1 CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE (JULY 2019) .. 2

L.3 CLAUSES AND PROVISIONS INCORPORATED IN FULL TEXT

L.4 GENERAL INSTRUCTIONS

L.5 PROPOSAL SUBMISSION AND DELIVERY INSTRUCTIONS

L.6 PROPOSAL PREPARATION

L.7 VOLUME I - TECHNICAL PROPOSAL

L.8 VOLUME II - MANAGEMENT PROPOSAL

L.9 VOLUME III - PAST PERFORMANCE

L.10 VOLUME IV- COST PRICE PROPOSAL

L.11 VOLUME V – SMALL BUSINESS SUBCONTRACTING PLAN, OFFER AND OTHER

DOCUMENTATION

L - 2

L.1 POINTS OF CONTACT

The FAA Contracting Officers (CO) are the points of contact for this acquisition. All questions or concerns must be addressed to the contracting points of contact, listed below:

Patrick Weare, Contracting Officer, AAQ-210 Federal Aviation Administration 600 Independence Ave., SW Washington DC 20591 202-267-5483 Patrick.Weare@faa.gov

Aleksandra Skoric, Contracting Officer, AAQ-210 Federal Aviation Administration 600 Independence Ave., SW Washington DC 20591 202-267-0774 Aleksandra.Skoric@faa.gov

All Offerors must send communications through the FAA Contracting Officers.

L.2 AMS 3.1-1 CLAUSES AND PROVISIONS INCORPORATED BY REFERENCE

(JULY 2019)

This screening information request (SIR) or contract, 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 will make the full text available, or offerors and contractors may obtain the full text via Internet at: https://fast.faa.gov/contractclauses.cfm.

(End of clause)

AMS

CLAUSE

TITLE DATE

3.2.2.3-1 False Statements in Offers April 2024 3.2.2.3-6 Submittals in the English Language September 2020 3.2.2.3-7 Submittals in U.S. Currency September 2020 3.2.2.3-12 Amendments to Screening Information Requests July 2024 3.2.2.3-13 Submission of Information/Documentation/Offers April 2024 3.2.2.3-14 Late Submissions, Modifications, and Withdrawals of Submittals April 2024 3.2.2.3-17 Preparing Offers April 2024 3.2.2.3-18 Prospective Offerors Requests for Explanations April 2024 3.2.2.3-19 Contract Award July 2004 3.2.2.3-31 Facilities Capital Cost of Money July 2004 3.3.1-29 Notice of Availability of Progress Payments Exclusively for Small

Business Concerns November 1997

3.6.2-7 Pre-award On-Site Equal Opportunity Compliance Review July 2023 mailto:Patrick.Weare@faa.gov mailto:Aleksandra.Skoric@faa.gov https://fast.faa.gov/contractclauses.cfm

L - 3

L.3 CLAUSES AND PROVISIONS INCORPORATED IN FULL TEXT

L.3.1 AMS 3.2.2.3-15 Authorized Negotiators (April 2024)

The offeror states that the following persons are authorized to negotiate on the offeror’s behalf with the FAA in connection with this offer:

Name:______________________________________________ Title:_______________________________________________ Phone number:_______________________________________ Email:______________________________________________

(End of provision)

L.3.2 AMS 3.2.2.3-16 Restricting, Disclosing and Using Data (April 2024)

If the offeror includes data in the offer that the offeror does not want to be disclosed to the public or for the FAA to use except for evaluation purposes-

(a) Mark the title page with the following legend: “This offer includes data that must not be (1) disclosed outside the FAA and (2) duplicated, used, or disclosed -in whole or in part- for any purpose other than to evaluate this offer.”

(b) Contracts awarded as a result of this SIR are subject to the disclosure requirements specified in this SIR. This restriction does not limit the FAA’s right to use information from another source that may be contained in the offer.

(c) Use the following space to identify the pages containing the restricted data:

Numbers or other identification of pages:

(d) Mark each page the offeror wants to restrict with the following legend: “Using or disclosing data contained on this page is subject to the restriction on the title page of this offer.”

L.3.3 AMS 3.2.2.3-20 Offers (January 2018)

(a) The offeror (you) must submit responses to this SIR by uploading files to the website specified in Section L.5.2.

(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.

L - 4

(d) Send your offer by uploading files to the website specified in Section L.5.2.

(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".

L.3.4 AMS 3.2.2.3-22 Period of 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.

L.3.5 AMS 3.2.2.3-38 Alternate II Requirements for Certified Cost or Pricing Data or Data Other Than Certified Cost or Pricing Data (January 2022)

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

(b) The offeror must provide the following data:

1. See Section L.10 (Volume IV Cost Price Proposal).

(End of clause)

L.3.6 AMS 3.2.4-1 Type of Contract (April 1996)

The FAA contemplates a single award of a hybrid Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF), Cost Reimbursement (CR), Time and Materials (T&M) and Indefinite Delivery/ Indefinite Quantity (IDIQ) Task or Delivery Orders type contract resulting from this SIR.

L.3.7 AMS 3.6.1-17 North American Industry Classification System (NAICS) Code (October 2022)

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

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

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

For NAICS codes based on SBA’s calculation of annual receipts, the annual average receipts cannot exceed N/A.

For NAICS codes based on the number of employees, the average number of employees over the last 24-month period cannot exceed 1,350.

L - 5

L.3.8 AMS 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.

L.4 GENERAL INSTRUCTIONS

L.4.1 Offeror Point of Contact

Each Offeror must provide their primary and alternate points of contact, telephone number, and email address for purposes of initiating all communications.

L.4.2 Eligibility for Proposal Consideration

The FAA will perform a verification to identify proposals that will continue through to the evaluation. To be considered for this procurement, the Offeror must demonstrate that its proposed Surface Movement Radar (SMR) system is currently operational and in use by an Air Navigation Service Provider (ANSP) to provide surface surveillance in support of air traffic services, or it is derived from the operational production baseline by:

1) Identifying the ANSP utilizing your SMR system,

2) Providing the location of your operational SMR system, and;

3) Providing a point of contact, email address, and telephone number within the ANSP for the

FAA to validate the information above.

The Offeror must provide their Eligibility for Consideration information submission as part of its proposal.

L.4.3 Compliance with Instructions

Offerors must comply with all instructions in Section L. Failure to comply with the instructions may result in a determination that the Offeror’s proposal is non-compliant. This determination will be made at the sole discretion of the Government. Proposals must conform to all incorporated AMS clauses and provisions in accordance with this Section L. To aid in the evaluations, proposals must be clearly and

L - 6 concisely written, as well as, neat, indexed (cross indexed, as appropriate), and logically assembled. All material submitted should be directly pertinent to the requirements of this SIR.

The FAA reserves the right to award a contract based on initial submittals received. Therefore, the Proposal should contain the Offeror’s best terms from a price and technical standpoint. Offerors are cautioned to consult the CO before submitting any offer that takes exception to any term or condition of the SIR. Any objection to any of the terms and conditions will constitute a deficiency, which may make the offer unacceptable. However, the FAA also reserves the right to conduct Offeror-specific discussions or to conduct discussions and permit Offerors to revise their proposals, if the CO deems appropriate and is in the best interest of the FAA. The FAA reserves the right to reject any exception for any reason.

Contractors must make an offer to this solicitation on all requirements, and in accordance to all the specified SIR terms, or the entire offer will be rejected as non-responsive.

L.4.4 Expenses Related to Offeror’s Submissions

Offerors are warned that 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 proposal under this SIR. This includes costs associated with any aspect of the proposal activity and any research, site surveys, studies, or designs carried out for the purpose of incorporation into any part of the proposal. It also includes any costs to acquire or subcontract for any services or products relating to the offer under this SIR. No pre-contract costs will be allowed on this contract. Pre-contract costs are defined as any costs incurred at the Offeror’s risk in anticipation that any such costs may later be charged to any resulting contract, and to the extent that they would have been allowable if incurred after the date of the contract and to the extent authorized by the Contracting Officer.

L.4.5 SIR Questions

The FAA Contracting Officers (COs) are the sole points of contact for this acquisition. All questions or requests for clarification regarding any section of the SIR must be prepared in writing and submitted as part of Attachment L-4, to the Contracting Officers via electronic mail at the address identified in Section L.1 Point of Contact, in an editable Microsoft Word table or Microsoft Excel format.

Questions/Clarifications must make reference to the applicable SIR section or document, page and/or paragraph.

All questions will be answered provided to all Offerors and the public on the System for Award Management website (sam.gov). The FAA will not attribute the questions to the submitting Offerors, but the text of the questions and answers will be made available to the general public.

All questions and clarifications relating to this SIR must be received by the Contracting Officers in accordance with the due date specified in L.5.1. The Offeror is responsible for ensuring that the FAA Contracting Officers has received the questions or clarifications.

The Contracting Officer will respond to questions with the Government’s answers or clarifications in accordance with L.5.1.

Questions or requests for clarification, and resultant resolution, may require an amendment to this SIR.

The amendment will be published at sam.gov. The CO will establish a common deadline for receipt by the Government of Offeror revisions to its proposal made necessary by the amendment.

L - 7

If an Offeror believes that these instructions contain an error, omission, or are otherwise unsound, the Offeror must immediately notify the Contracting Officers in writing with supporting rationale but no later than Offeror Proposals Due Date listed in L.5.1. Discrepancies not brought to the attention of the Contracting Officers prior to proposal submission, are waived.

Any question(s) submitted should not contain any restrictive legends (i.e. proprietary information). As all answers must be shared with all Offerors, if an Offeror submits a question that is marked with restricted legends, the question will not be considered or answered by the Government.

L.4.6 Alternate Proposals

Alternate proposals are not authorized and will not be accepted. If Offerors are using partner companies, only a single proposal from the Prime offeror must be submitted.

L.4.7 Communication with Offerors

Any information concerning the SIR given to any Offeror will be promptly furnished to all other Offerors.

FAA Communications and Clarifications with Offerors:

All communications will be conducted through the FAA Contracting Officer, per L.1.

The Government reserves the right to communicate with one, all, or none of the Offerors. However, Offerors are advised that a selection may be made without communication or any contact concerning the proposal received. Therefore, Offerors are instructed to submit proposals on the most favorable terms possible. Offerors should not assume that they will be contacted or afforded an opportunity to clarify, discuss, or revise their proposals. Any information obtained during communications may be used to clarify, substantiate, and validate information provided in Offeror proposals.

The following conditions apply to Offeror communications:

1. Communications with one Offeror does not require communications with any other Offeror;

2. Government communications may occur orally or in writing;

3. The Government reserves the right to conduct communications with any Offeror as the situation warrants;

4. Content of the communications may vary between Offerors; and,

5. Any information provided in response to a Government issued communication may be used in the evaluation of proposals.

The FAA may, at any time and within its sole discretion, communicate orally or in writing with Offerors on an individual basis to clarify particular aspects of their proposal, to negotiate the terms and conditions of the proposed contract, or to seek clarification or additional information regarding Offerors’ submissions. Communication with potential Offerors may take place throughout the source selection process. The purpose of communications is to ensure mutual understandings between the FAA and the Offerors on all aspects of the procurement, including the Offerors’ proposals. Any information obtained during communications may be used, at the FAA’s sole discretion, to clarify, substantiate, or validate information provided in an Offeror’s proposal. Responses to communication requests may be treated the same as information submitted with the written proposals and information disclosed as a result of oral or written communication with an Offeror may be considered by the FAA in the evaluation of an Offeror’s proposal. The FAA also reserves the right to allow Offerors to revise their proposals, within the FAA’s

L - 8 sole discretion. The FAA is not required, however, to request any clarifications or accept any offeror revisions.

L.4.8 Proposal Modifications

The FAA reserves the right to make a selection and contract award based on initial proposal submissions.

However, if requested by the FAA, an Offeror’s response to the request must be limited to those modifications required to address FAA communications or specific changes depicted in a SIR amendment.

Offerors are instructed to limit modifications to their proposals to the pertinent subject of the communications. If change pages are required, the Offeror must not exceed the total page count listed for the original proposal, as set forth herein.

If an amendment to the SIR affects the total number of pages allowed in a proposal, the FAA, will issue instructions specifically modifying the page number limitations to the designated sections of an Offeror’s proposal.

The FAA, at its discretion, may make administrative changes to information contained in a proposal, such as mathematical errors or inaccurate cross-references. The FAA will notify the Offeror of any administrative change.

L.4.9 Notification of Intent to Withdraw Proposal

An Offeror may withdraw its proposal from competition by sending written notice, signed by an authorized representative, to the Contracting Officer, at any time prior to Contract Award. Prior to such action, the Offeror must notify the Contracting Officer in writing of representatives authorized to withdraw the proposal. Proposals may not be withdrawn by facsimile or electronic mail.

L.4.10 Non-Government Personnel Participation

Offerors are hereby notified that the Government may utilize support contractors to assist during the administrative, clerical, and evaluation process of proposals. All non-Government personnel and their companies have signed, or will sign, before the evaluation process begins, Non-Disclosure and Conflict of Interest statements.

Individuals from the following companies may serve as evaluators and/or advisors in the process:

1. DTIS, LLC

2. INCATECH LLC

3. MCR Federal, LLC/ Systems Planning and Analysis, Inc.

4. Noblis, Inc.

5. Regulus Group, LLC

6. Science Applications International Corporation (SAIC)

7. Cobec Consulting, Inc.

8. Aurora Innovations, LLC

If the Government decides to use support contractors other than, or in addition to those listed above, the CO will notify Offerors in writing of this decision. The company name(s) of these replacements and the FAA SIR number will be provided.

L - 9

The responsibility for source selection will remain with the FAA.

L.4.11 Organizational Conflict of Interest

Pursuant to AMS Procurement Guidance T.3.1.7, an organizational conflict of interest means that because of an existing or planned activities, (1) an offeror or contractor is unable or potentially unable to render impartial assistance to the agency, or (2) has an unfair competitive advantage, or (3) the offeror or contractor’s objectivity is or might be impaired.

For example, companies which are providing, will provide, or have provided, program management support to the Government related to the planning for a competitive procurement or oversight of the awarded contract, may be considered to have an unacceptable conflict of interest risk and would be ineligible to provide products or services to implement requirements under this contract.

Companies that have provided support to the Government in development of concepts and system requirements for work within the scope of future acquisitions may be considered to have an unfair competitive advantage and thus may be considered ineligible to provide products or services to implement the requirements under this contract unless the Contracting Officer has approved a mitigation plan.

In accordance with FAA AMS Clause 3.1.7-2, FAA has OCI concerns with the following companies and their subcontractors are prohibited from bidding in any role:

1. DTIS, LLC

2. INCATECH LLC

3. MCR Federal, LLC/ Systems Planning and Analysis, Inc.

4. Noblis, Inc.

5. Regulus Group, LLC

6. Science Applications International Corporation (SAIC)

7. Constellation Aerospace Solutions, LLC (CAS)

8. Cobec Consulting, Inc.

9. AK Government Solutions

10. ASRC Federal

11. LS Technologies

12. Systems Ingenuity

13. Veracity Engineering

14. Aurora Innovations, LLC

15. Aneon Federal Solutions, LLC

16. Booz Allen Hamilton

This section will be updated, as necessary, to list companies that have OCI and are prohibited from bidding in any role on this procurement.

L.4.12 Notification of Award and Debriefing of Unsuccessful Offerors

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

Successful or unsuccessful Offerors may request a debriefing by providing written request to the Contracting Officer within three (3) business days of receiving notice of contract award. The debriefing must be conducted only after source selection activities have been completed and the contract awarded.

L - 10

Debriefings are conducted with the goal of identifying, to unsuccessful offerors, areas where changes can be made to improve future source selection participation. To that end, source selection debriefing will be conducted with only one offeror at a time. The debriefing will be confined to discussion of the offeror’s proposal only. A point-by-point comparison with other offerors proposals will not be made. The debriefing will neither discuss nor reveal the relative merits, nor will it reveal the evaluation.

During and after completion of debrief, time will be provided for the offeror to ask oral or written questions. Every effort will be made to answer all questions at the debriefing or as soon as feasible.

L.5 PROPOSAL SUBMISSION AND DELIVERY INSTRUCTIONS

L.5.1 Volume Submission and Projected Procurement Milestones

The following acquisition milestones are provided for informational purposes only and are subject to change. The projected milestone dates for this procurement are shown in the table below:

Milestone Estimated Dates Final SIR Release 10/28/2024 Final SIR Offeror Q&A Submission Deadline 11/26/2024 (21 business days after Final

SIR Release) RunAcquisition Access User Request for Vendor Proposal Submission Platform

11/18/2024 (15 business days after Final SIR Release)

Contracting Officer Response to Questions 12/11/2024 Offeror Proposals Due 1/24/2025 Contract Award 12/16/2025

Table 1 -Projected Procurement Milestones Schedule

L.5.2 Proposal Delivery Instructions

1) TIME AND DATE: Proposals must be received by the Contracting Officer at the location identified below no later than 12:00 p.m. EST on the due date identified in L.5.1.

2) DELIVERY LOCATION: RunAcquisition proposal submission platform at https://submit.acquisitions.run

3) ACCESS REQUEST: Attachment L-5 FAA SMR-4 RunAcquisition Vendor User Form must be submitted within 15 business days after the SIR release date to access the proposal submission delivery platform location. Upon gaining access to the proposal submission platform, User Guide instructions entitled “FAA SMR4_RunAcquisistions Vendor Portal User Guide” will be made available to Users.

4) Proposals must be valid for a period of 365 days after receipt of offer unless extended by the

Offeror.

Any proposal or portion of any proposal delivered to any other location will not be accepted.

Delivery after the appointed time will not be accepted.

https://submit.acquisitions.run/

L - 11

The FAA may reject incomplete proposals, or those proposals not submitted in accordance with the delivery instructions previously stipulated.

The Offeror must allow subcontractors to submit their Subcontractor Proprietary Data for this SIR by email to the Contracting Officer at the email address in L.1.

L.5.3 Submit Legally Binding Documentation

The Offeror’s submission constitutes a formal document for which an award may be made without communications. Proposal must be signed by an individual authorized to commit the Offeror. Offerors are instructed to comply with all terms and conditions contained in preparation of their proposals.

L.6 PROPOSAL PREPARATION

This section provides general guidance for preparing proposals and instructions on format and content of the proposal. In addressing the requirements of Section L, Offerors are instructed to ensure that all aspects of the factors in Section M are addressed. Also, unless explicitly instructed otherwise, for each section Offerors should address the entire period of performance of the contract. Replies to the SIR must follow the outlines and instructions concerning format given in Section L.

L.6.1 General Preparation Instructions

The Offeror must include a cover submittal letter with the proposal. The submittal letter must include the Offeror’s acknowledgement of any and all SIR amendments.

Proposals must include supporting rationale, substantiation of all claims, and factual information to facilitate the FAA’s evaluation. Proposals should be specific enough to provide the FAA evaluators with enough information to be able to judge the technical and financial ability of the Offeror to conduct this contract and meet all requirements. The proposal must not merely offer to perform work in accordance with the SOW but must detail the actual work proposed as specifically as practical. Proposals that repeat the information contained in the SOW without sufficient elaboration, or that merely paraphrase Section C of the SIR, or that use non-specific phrases such as “in accordance with standard procedures” or “in accordance with well-known techniques” may result in weaknesses, risks, and lower evaluation scores.

Offerors should assume that the FAA has no prior knowledge of its proposed solution, capability, and experience and that the FAA will base its evaluation on the information presented by the Offeror.

Proposals must contain enough detail to enable the FAA evaluators to determine the ability of the Offeror and the proposed solution to meet the SIR requirements. Lack of detail in a proposal may be deemed a weakness or risk by evaluators. Offerors must not assume that they will be contacted or afforded an opportunity to clarify, discuss, or revise their proposal if FAA evaluators identify omissions or lack of detail.

The Offeror need not repeat information within the same volume if that information is required in response to two or more proposal requirements. Such information should be presented in detail in the one area of the volume where it contributes most critically to the discussion of the SIR requirement. In other areas where discussion of the same information is necessary, the Offeror may refer to the initial discussion and identify its location within the proposed volume.

If the Offeror determines that the same or similar information is required in separate volumes, that information must be addressed in full text in each volume.

L - 12

All proposals will be screened initially for timeliness and adherence to Section L instructions. Offeror proposals that do not meet initial screening criteria may not be evaluated further. Any data that may contain trade secrets, copyright data, and financial information which the Offeror or proposed subcontractors do not want disclosed for any purpose other than the evaluation of the proposal must be marked in accordance with L.3.1 AMS 3.2.2.3-16, “Restricting, Disclosing and Using Data (April 2024).”

Offerors are instructed to assemble and identify volumes in accordance with the Table 2 – Proposal Organization below.

Offerors are instructed to ensure that all volume titles and associated content must be compiled and delivered within the page limitations shown in Table 2 – Proposal Organization.

L.6.2 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.

L.6.2.1 Format and Structure

Proposals must comply with the following guidelines:

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

2) Margins: 1” inch

3) Spacing: Single-spaced

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

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

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

7) 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.

8) 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.

9) 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.

10) Print Ready. Electronic copies of the proposal must be print ready in accordance with the instructions above.

L - 13

11) All pages of each part must be appropriately numbered, and identified with the name of the Prime Offeror, the date, and the solicitation number to the extent practicable.

L.6.2.2 Electronic Copies of Proposals

Your offer must arrive at the place and by the time specified in the SIR. File names must be consistent with the structure of the proposal. Offerors must submit an electronic file for all Volumes. Volume IV is the only volume that must be in a separate file. 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:

1) Microsoft Office 365 (e.g., Excel, Word, PowerPoint)

2) Microsoft Project 2016

3) Adobe Acrobat Reader 11.0

The Offerors must submit any Microsoft Office Excel spreadsheets in a format that allows formulas within the spreadsheets to be reviewed and manipulated.

L.6.3 Price Data

Applicable hours, skill levels, and materials must be provided without price data for evaluation of non-price volumes, i.e., Technical, Management, and Past Performance. Care should be exercised to ensure that no price data of any kind is included in any proposal volume other than Volume IV. Applicable hours and skill mix as necessary must be provided without price data.

L.6.4 Proposal Organization

Offerors are instructed to assemble and identify volumes in accordance with the Table 2 below. Offerors are instructed to ensure that all volume titles and associated content must be compiled and delivered within the page limitations shown in Table 2.

The Offeror’s proposal submission must consist of Volume I – Technical Proposal, Volume II – Management Proposal, Volume III – Past Performance, Volume IV – Cost Price Proposal, and Volume V –Small Business Subcontracting Plan, Offer, and Other Documentation.

Pricing information must only be included in Volume IV and must not be included within any other volume. If pricing information is included within other volumes, the FAA reserves the right to exclude the proposal from the evaluation.

The volumes must be organized as follows:

Table 2 – Proposal Organization

L - 14

VOLUME # DESCRIPTION Page Limit

I TECHNICAL PROPOSAL

Executive Summary

1. System Design and Performance

2. System Engineering

3. System Test and Evaluation

4. Transfer and Data Rights

5. Implementation

6. Integrated Logistics Support

Appendices 1. System Requirements Document (SRD)

2. Offeror’s SMR4 System Specification Crosswalk

No page limit

II MANAGEMENT PROPOSAL

Executive Summary

1. Program Management

2. Integrated Master Schedule (IMS) Management

3. Risks, Issues, and Opportunities Management

Appendices 1. Draft Integrated Master Schedule (IMS)

2. Risks, Issues, and Opportunities

2.a. Productivity Efficiencies for Increased Production System Quantities

3. Key Personnel Resumes (2 pages /resume) and/or Letter(s) of Intent if required (no page limit for Letter(s) of Intent)

No page limit, unless specified

III PAST PERFORMANCE Page limit

1. Past Performance Descriptions (Page count does not include Attachment L-2)

Attachments 1. Attachment L-1 – Past Performance List

2. Attachment L-2 – Past Performance Survey Form

(Section A only)

No page limit

IV COST/ PRICE PROPOSAL Page limit

- Executive Summary No page limit PART A - Cost Price Workbook (CPW) Model –

Attachment L-6 Total Contract Cost and Price Summary

L - 15

VOLUME # DESCRIPTION Page Limit PART B – Detailed Narrative and Supporting Documentation

1. Adequacy of Offeror Accounting Systems Verification, SF-1408, and/or Explanation Submission(s)

2. Direct Labor Rates and Hours

3. Indirect Costs

4. Other Direct Costs/ Subcontractors/

Interdivisional Transfer Materials

5. Fee – CPFF CLINS

6. T&M Labor Category CLINs Detailed Narrative

7. Detailed Narrative and Supporting

Documentation – Firm Fixed Price CLINs

8. Provision of the Volume Discounts by the

Offeror PART C – Cost / Price Exceptions, Deviations or Assumptions

Estimating Methodology and Supporting Cost Price Documentation

1. General (AMS T.3.2.3 Appendix 1)

2. Basis of Estimate

Mandated Assumptions for Offeror Pricing

1. Contractor Start Date

2. Estimated Material and ODCs

V SMALL BUSINESS SUBCONTRACTING PLAN,

OFFER AND OTHER DOCUMENTATION

Page limit

L.11.1 SMALL BUSINESS SUBCONTRACTING PLAN

(LARGE BUSINESSES ONLY)

No page limit

L.11.2 OFFER AND OTHER DOCUMENTATION

L.11.2.1 Completed Solicitation, Offer, and Award (OMB Form

SF-33) and Model Contract No page limit

L.11.2.2 Section K, Representations, Certifications and Other Statements of Offerors

No page limit

L.11.2.3 Organizational Conflicts (OCI) of Interest Plan 50 L.11.2.4 Business Declaration Form (Attachment L-3) 2 L.11.2.5 Required Data for Eligibility for Proposal Consideration No page limit L.11.2.6 Required Data for Determination of Responsibility

Requirements No page limit

L.11.2.7 Subcontractor Agreement(s) and Letter(s) of Intent No page limit L.11.2.8 Proposal Compliance Matrix 15

L - 16

L.7 VOLUME I - TECHNICAL PROPOSAL

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 complete, valid, and achievable. The Offerors proposal must demonstrate an understanding of all contract requirements and address all Technical Proposal requirements outlined below.

The Technical Proposal must consist of the Offeror’s proposed approach for addressing the technical and support aspects of the acquisition. The proposal must provide a straightforward explanation of what the Offeror will do to satisfy all requirements of the SIR. The Offeror must discuss risk, issues, risk mitigation strategies, and opportunities.

The filename must be “Vol I-XXX_MM-DD-YY.pdf”. (XXX is the acronym for company name and MM- DD-YY is the date). All Attachments mentioned in Volume I will be included as part of this file, or as otherwise indicated below.

L.7.1 Executive Summary

Each offeror must provide an Executive Summary that summarizes the contents of its Technical Proposal, including:

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

2) Opportunities and approach for accomplishment.

3) Risks and mitigation strategies.

L.7.2 System Design and Performance

The Offeror must provide the following:

1) A description of the Offeror’s proposed system including the function of major elements.

2) A description of how the Offeror’s proposed SMR4 satisfies the functional and performance requirements specified in SMR4 System Specification Document (SSD), FAA-E-37024 (Attachment J-03) and SMR4 Interface Requirements Document (IRD), NAS-IR-nnnnnnn (Attachment J-04), including:

a. Completion of the SMR4 Technical Requirements Matrix (Attachment J-07). See Section L.7.8.2.

b. A description of the development required for their proposed system to meet all FAA-E- 37024 (Attachment J-03) requirements and identification of any requirement that cannot be met as currently specified. Where performance requirements (FAA-E-37024 Section 3.2) cannot be met, include the actual performance that the proposed system can achieve.

c. A description of the development required for the proposed system to meet NAS-IR-nnnnnnn (Attachment J-04) requirements as they pertain to the SMR4.

3) A detailed description of the following characteristics of the proposed system:

a. Transceiver capabilities including (but not limited to) pulse shaping, modulation techniques, transmit frequencies, transmit power, sensitivity time control, and pulse

L - 17 repetition frequency.

b. Features to eliminate false targets due to clutter, weather, radio frequency interference, and multipath.

c. Capabilities to mitigate interference with other SMRs operating within the same frequency band.

d. Capabilities to mitigate multiple time around clutter and time sidelobes. If the proposed system is not susceptible to these phenomena, explain how system design eliminates these concerns (e.g., pulse compression is not used).

e. Plot extraction function and adaptability. Include the plot extractor impact on target resolution, how large plot integrity is maintained, and the ability to distinguish smaller targets in proximity to other targets (e.g., vehicle and aircraft).

f. Tracker performance with closely spaced targets, including merge and unmerge distances, minimum track initiation distances, and adaptability.

g. System redundancy features, including the ability to service an offline channel without taking the system out of service.

h. Anti-icing capabilities of the antenna array, including standard and optional heated array, and any system differences when installed with a heated array vs standard array.

i. Impact temperature extremes have on antenna beam squint, the impact to azimuth accuracy, and any mitigation features included in the design.

j. Methods or features of the antenna subsystem designed to mitigate bird strikes.

k. Supportability of the proposed Operating System (end of life) and current security features.

L.7.3 Systems Engineering

The Offeror must provide a description of the engineering approach they will utilize to ensure all contract requirements are met, including:

1) Systems Engineering Process, which defines the approach for planning, controlling, and conducting a fully integrated engineering effort to meet the requirements of the SMR4 System Specification, FAA-E-37024 (Attachment J-03) and the SMR4 to Surface Surveillance System Interface Requirements Document, NAS-IR-nnnnnnn (Attachment J-04).

2) Software Engineering and Development Process, which defines:

a. The Offeror’s approach for producing certifiable software compliant with RTCA/DO- 278A Assurance Level 4 (AL4).

b. All aspects of the Offeror’s software lifecycle processes to include planning, development, verification, configuration management, and quality assurance.

c. The software design of the proposed system, including identification of the major computer software configuration items (CSCI), the software language used in each major CSCI, and the lines of code for each major CSCI.

3) The Offeror’s approach to developing an interface with the existing Airport Surface Detection Equipment – Model X (ASDE-X) and Airport Surface Surveillance Capability (ASSC) systems.

L - 18

4) The Offeror’s approach to developing and implementing a security program to address information/data for the security requirements in the SMR4 System Specification, FAA-E-37024 (Attachment J-03) and the SOW.

5) The strategies that will be employed during the design, development, integration, and test phases to reduce risk and to meet cost, performance, and scheduling milestones.

L.7.4 System Test and Evaluation

The Offeror must provide a detailed description of their system test and evaluation approach, including:

1) Major components, processes, and procedures of the proposed test program and the tests necessary to validate that the SMR4 system design meets the functional and performance requirements as delineated in the SMR4 System Specification 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. This description must identify and discuss, in detail, any test tool development required to meet test program needs.

4) A description of the test facilities that will be used for In-Plant Development Test. This discussion must include all limitations with respect to requirements verification (e.g., maximum range).

5) Specific test methodologies to be employed (demonstration, test, analysis, inspection, test with data, and design review) to verify that all SMR4 System Specification requirements are met.

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

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

L.7.5 Transfer and Data Rights

The Government requires the Offeror to transfer the systems and data rights to support Government, contractor and competitively procured third party contractor operation, maintenance, and modification of the SMR4 systems, processes, and the software.

L.7.5.1 Systems Transfer The Offeror must describe its proposed approach for transferring the SMR4 systems to the FAA, and the proposed data rights for hardware, software, and data. The Offeror must include:

1) The activities required to fully transfer SMR4 to the FAA for operations, including component and system warranties.

2) The activities required to fully transfer SMR4 to the FAA for maintenance and further development.

3) The description of obstacles and constraints on the transfer of SMR4 to the FAA.

L.7.5.2 Data Rights

L - 19

The Offeror must submit Attachment J-18 Disclosure of Data Assertion and Identification List (“Assertions List”) that comprises a comprehensive data accounting that define the rights and data:

1) Afforded to the Government.

2) Not afforded to the Government.

The Offeror must provide the basis for assertion for all data rights.

The Government will incorporate all data rights offered in Attachment J-18 Assertions List into the successful Offeror’s contract upon award.

L.7.6 Implementation

The Offeror must describe in detail how they will perform implementation activities for the installation of the SMR4 into the NAS, including:

1) Plans, processes, and schedule (including assumptions) for site preparation, installation, optimization, site acceptance testing, and contractor acceptance inspection. The plans must include a description for providing site and personnel security and safety.

2) Plans and processes to address Generic Site Implementation Plan (GSIP) (Attachment J-06) implementation requirements.

3) Approach to efficiently install and optimize the SMR4 that minimizes the impact to Air Traffic and local airport operations during SMR4 implementation.

4) Identify all tools, equipment, and materials required to perform installation, optimization, test, and inspection activities.

L.7.7 Integrated Logistics Support

The Offeror must describe in detail how they will implement and sustain Integrated Logistics Support to include the following:

1) Maintenance and support planning and demonstrated ability to support fielded systems.

2) Training and documentation for technical personnel for SMR4 maintenance, restoration, and system certification.

3) Training and documentation for Second Level Engineers including but is not limited to the generation, maintenance, testing, analysis, and debugging of all the functional hardware and software at a Government Second Level Support facility.

4) Interim Contractor Depot Level Support (ICDLS) and the transition of depot functions to the FAA Logistics Center.

L.7.8 Technical Proposal – Appendices

L.7.8.1 System Requirements Document (Appendix 1) The Offeror must provide the requirements documentation that was used to develop their proposed system, from this point referred to as “System Requirements Document (SRD)”. Contractor format of the SRD acceptable. The Offeror must include requirements within their SRD that fully define all capabilities of the proposed system, including those capabilities that exceed the requirements in SMR4 System Specification Document, (SSD) FAA-E-37024 (Attachment J-03).

L - 20

L.7.8.2 Offeror System Specification Crosswalk (Appendix 2)

The Offeror must provide a completed crosswalk between the requirements in the SMR4 SSD, FAA-E- 37024 (Attachment J-03), the SMR4 Interface Requirements Document (IRD) in NAS-IR-nnnnnnn (Attachment J-04), and the requirements in the Offeror’s SRD. The crosswalk must identify which SMR4 requirements are currently met by the Offeror’s proposed system and which ones require product modification or development. The Offeror must utilize the SMR4 Technical Requirements Matrix (Attachment J-07) for completing the crosswalk. The spreadsheet must be completed in accordance with the Instruction tab in the spreadsheet.

The filename must be “Vol I-XXX_J-07-MM-DD-YY.xlsx”. (XXX is the acronym for company name and MM-DD-YY is the date).

L.8 VOLUME II - MANAGEMENT PROPOSAL

Offerors must fully substantiate their management approach that is complete, valid, and achievable. The Management Proposal must address the management and support requirements to satisfy accomplishment of the objectives of the SIR.

The filename must be “Vol II-XXX_MM-DD-YY.pdf”. (XXX is the acronym for company name and MM- DD-YY is the date). All Appendices mentioned in Volume II will be included as part of this file unless otherwise specified.

L.8.1 Executive Summary

This section must provide a summary of the following information:

1) Key elements, unique features, and benefits (excluding price) of the Offeror’s proposed management approach

2) Comprehensive descriptions of risks and mitigations, and opportunities and the realization of benefits

3) Major milestones

4) Key personnel and qualification highlights (in accordance with SIR Section H.2.3 of this SIR) for both prime and subcontract organizations

5) Reporting processes

L.8.2 Program Management

The Program Management Volume must demonstrate the approach and processes which will be applied in performing the work, including specific examples of successful application to similar projects. The Volume must demonstrate how the Offeror will successfully accomplish the work, to include the following:

1) Organizational structure, lines of communication, and responsibility and authority

2) Processes for program management, conducting program reviews and technical interchanges, issue escalation, and effective tracking and reporting of results.

3) Processes for quality management, configuration management and data management.

L - 21

4) Approach for managing and integrating subcontractors, to include a description of roles, responsibilities, lines of communication, and reporting mechanisms.

5) Processes for estimation and control of resources, time, and expenditures to successfully accomplish the work.

6) Development, implementation, and monitoring of technical performance and Earned Value Management metrics that depict program cost, cost control, schedule, and performance attainment.

7) Key personnel and resources to implement a successful program.

The Offeror must discuss opportunities, risks, and risk mitigation strategies throughout the Management Proposal. The Offeror must identify risks and opportunities at the point where they are discussed.

The Offeror must also identify key personnel (in accordance with SIR Section H.2.3 of this SIR) who have demonstrated experience and competency to provide leadership and direction in support of the SMR4 Program. The Offeror must describe the approach for staffing the program across all team and subcontract members.

L.8.3 Integrated Master Schedule (IMS) Management

The Offeror must provide the approach for developing, using, and maintaining the IMS. The Offeror must detail the processes for managing and using the IMS over the contract life cycle, including changes driven by the Contractor or FAA, and reporting associated technical and cost impacts.

L.8.4 Risks, Issues, and Opportunities Management

The Offeror must describe their risk management approach. The Offeror’s approach must include proactive risk and opportunity identification and resolution, including escalation of risks and issues. The Offeror must address risk, issue, and opportunity reporting for integration with the FAA RIO Process (Attachment J-11 – Surface Surveillance Program, Standard Operating Procedure (SOP), Programmatic Risks, Issues and Opportunities (RIO) Management and Attachment J-12 – RIO Identification Worksheet.)

L.8.5 Management Proposal – Appendices

L.8.5.1 Draft Integrated Master Schedule (IMS) (Appendix 1)

The Offeror must address the following in the proposed draft IMS, submitted as part of the proposal, with a detailed supporting narrative that clearly shows how the schedule will meet the program requirements:

1) Contractor schedule and milestones to meet contract schedule requirements, including the activities, critical path and internal dependencies for procurement, systems engineering, software development, systems integration, logistics, test, implementation, checkout and acceptance, production and training;

2) Traceability to the CWBS and identification of external interdependencies (e.g., FAA and suppliers); and

3) Activities for meeting first article and…