Amendment 3 SAI SIR Section L 2.15.24.docx

TABLE OF CONTENTS

- Instructions, Conditions, and Notices to Offerors 3.1-1 Clauses and Provisions Incorporated by REFERENCE

3.2.2.3-1 FALSE STATEMENTS IN OFFERS (JUL 2004)

3.2.2.3-6 SUBMITTALS IN THE ENGLISH LANGUAGE (JUL 2004)

3.2.2.3-7 SUBMITTALS IN U.S. CURRENCY (JUL 2004)

3.2.2.3-9 NOTICE OF POSSIBLE STANDARDIZATION (JUL 2004)

3.2.2.3-11 UNNECESSARILY ELABORATE SUBMITTALS (JUL 2004)

3.2.2.3-12 AMENDMENTS TO SCREENING INFORMATION REQUESTS (JUL 2004)

3.2.2.3-13 SUBMISSION OF INFORMATION/DOCUMENTATION/OFFERS (JUL 2004)

3.2.2.3-14 LATE SUBMISSIONS, MODIFICATIONS, AND WITHDRAWALS OF SUBMITTALS (APR 2018)

3.2.2.3-15 AUTHORIZED NEGOTIATORS (JUL 2004)

3.2.2.3-16 RESTRICTING, DISCLOSING AND USING DATA (JUL 2004)

3.2.2.3-17 PREPARING OFFERS (JUL 2004)

3.2.2.3-18 PROSPECTIVE OFFEROR'S REQUESTS FOR EXPLANATIONS (MAR 2009)

3.2.2.3-19 CONTRACT AWARD (JUL 2004)

3.2.2.3-31 FACILITIES CAPITAL COST OF MONEY (JUL 2004)

3.2.2.3-72 ANNOUNCING COMPETING OFFERORS (JUL 2004)

3.2.4-25 SINGLE OR MULTIPLE AWARDS (APR 1996)

3.2.4-26 MULTIPLE AWARDS FOR ADVISORY AND ASSISTANCE SERVICES (APR 1996)

3.3.1-28 NOTICE OF PROGRESS PAYMENTS (NOV 1997)

3.3.1-29 NOTICE OF AVAILABILITY OF PROGRESS PAYMENTS EXCLUSIVELY FOR SMALL

BUSINESS CONCERNS (NOV 1997)

3.6.2-7 PREAWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE REVIEW (JUL 2011)

3.6.4-1 WAIVER OF BUY AMERICAN ACT FOR CIVIL AIRCRAFT AND RELATED ARTICLES (JAN

2011)

3.11-45 F.O.B. ORIGIN AND/OR F.O.B. DESTINATION EVALUATION (APR 1999)

3.11-46 SHIPPING POINT(S) USED IN EVALUATION OF F.O.B. ORIGIN OFFERS (APR 1999)

Clauses and Provisions Incorporated in Full Text

3.2.1.3-1 NOTICE OF COMPETITIVE SOURCING (OCT 2003)

(a) This screening information request (SIR) is part of a Government competitive sourcing process to determine whether accomplishing the specified work under contract or by a Government organization provides the best value to the Government. If Government performance is determined to be more economical, then a Letter of Obligation will be issued to the competing Government organization and a contract will not be awarded.

(b) Cost estimates for performance by the Government of the services identified in the Performance Work Statement (PWS) in this SIR will be calculated in accordance with OMB Circular No. A-76 (Revised) and submitted by designated agency personnel to the Contracting Officer in a sealed envelope not later than the time set for receipt of cost submittals from all offerors.

(End of Provision) 3.2.2.3-4 Samples (October 2018)

(a) 'Samples' are item samples the offeror (you) must provide to show characteristics of your products that cannot be described adequately (for example, balance, ease of use, or pattern).

(b) You must provide samples required elsewhere in this SIR as part of your offer by the time specified for receiving offers. The FAA may reject offers that do not provide samples on time (see provision 3.2.2.3-14 - "Late Submissions, Modifications, and Withdrawals of Offers").

(c) The Contracting Officer (CO) will evaluate samples to determine if they comply with all the characteristics listed in this SIR. The CO may reject offers if they do not provide samples meeting the requirements.

(d) Unless otherwise specified in the SIR, you must:

(1) Provide samples at no expense to the FAA, and

(2) Pay for the samples to be returned if you want them back.

(e) The CO may waive the requirement to provide samples; if

(1) You provided the same product to us ________ [the CO should designate the FAA contracting office or an alternate activity or office that previously received this product] on a previous acquisition,

(2) The CO determines that your product was accepted or tested and found to be technically acceptable, conforming in every material respect with those of this SIR, and

(3) You will produce the product offered under this SIR at the same plant where you produced the previously acquired or tested product.

(End of provision) Alternate I - AMS clause 3.2.2.3-4 "Samples" (October 2018)

If the SIR requires Information Technology (IT) devices, media, or software as samples, the Contracting Officer must insert the following additional paragraphs in the basic clause:

(f) All sample Information Technology (IT) equipment, devices, media, software, etc. must first be tested and evaluated in an isolated environment that does not connect to the FAA production network.

(g) (1) Contractor IT equipment, devices, media, software, applications, etc. that require connection to the FAA network or system to demonstrate features and functionality, must have the FAA Chief Information Officer (CIO) and Chief Information Security Officer (CISO) approval before connection to the FAA network or system.

3.2.2.3-5 DESCRIPTIVE LITERATURE (JUL 2004)

(a) "Descriptive literature" means information (for example cuts, illustrations, drawings, and brochures) submitted as part of an offer. The FAA (we) may need descriptive literature to evaluate details of the product. These details may be about:

(1) Design;

(2) Materials;

(3) Components;

(4) Performance characteristics; or

(5) Methods of manufacture, assembly, construction, or operation.

(b) Descriptive literature includes only information the FAA needs to determine that the offeror (you) will provide technically-acceptable products.

(c) The offeror (you) must mark or highlight the items you are submitting as descriptive literature so we can readily find them in your offer.

(d) The Contracting Officer (CO) may reject offers that fail to submit descriptive literature on time (see the "Late Submissions, Modifications, and Withdrawals of Offers" provision of this SIR) or in which the descriptive literature does not show that the product offered conforms to the SIR requirements.

(e) The CO may waive the SIR requirement for descriptive literature if you indicate in subparagraph (e)(1) below that you supplied a comparable product under an earlier FAA contract and the CO determines that the product meets this SIR's requirements.

(1) You represent that you [ ] have, [ ] have not (check applicable box) supplied a product to us [ ] (the CO should designate the contracting office or an alternate activity or office) under an earlier FAA contract that is the same as the product offered under this SIR.

(2) If you checked 'have' in paragraph (e)(1), and seek a waiver of the requirement for descriptive literature, submit the following information as part of your offer:

Earlier contract number _____________________________________ Date of earlier contract ______________________________________ Contract line item number of product supplied ___________________ Name and address of government activity to which you delivered the product Date of final delivery of product _______________________

(f) You must submit offers on the basis of required descriptive literature or on the basis of a product you supplied previously under paragraph (e). Once you submit an offer on one of these two bases and the deadline for us to receive offers has passed, you may not elect to have your offer considered on the alternative basis. The Government will disregard your request for a waiver under paragraph (e) above if you have submitted the descriptive literature this SIR requires.

(End of provision) 3.2.2.3-20 Offers (January 2018)

(a) The offeror (you) must submit responses to this SIR by the following electronic means: CD, DVD, or USB disk (USB preferable)email; Two (2) copies. Your offer must arrive at the place and by the time specified in the SIR.

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

and

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

(End of provision)

3.2.2.3-22 PERIOD FOR ACCEPTANCE OF OFFER (OCT 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.

(End of provision)

3.2.4-1 TYPE OF CONTRACT (APR 1996)

The FAA contemplates award of a hybrid contract including Cost Plus Fixed Fee, Cost Plus Incentive fee, Cost Plus Award Fee, Firm Fixed Price, Time and Materials, and Fixed Price Level of Effort resulting from this Screening Information Request.

(End of provision)

3.6.1-17 NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM (NAICS) CODE (JAN 2017)

The North American Industry Classification System (NAICS) code for this procurement is 518210 Data Processing, Hosting and Related Services.

The small business size standard as defined by the Small Business Administration is $25,000,000.00 for average annual gross receipts for the company including its affiliates.

(End of provision) 3.9.1-3 Protest (January 2020)

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.

(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) For filing by hand delivery, courier or other form of in-person delivery:

Office of Dispute Resolution for Acquisition Federal Aviation Administration 600 Independence Avenue SW., Room 2W100 Washington, DC 20591; or

For filing by U.S. Mail:

Office of Dispute Resolution for Acquisition Federal Aviation Administration 800 Independence Avenue SW Washington, DC 20591 [Attention: AGC-70, Wilbur Wright Bldg. Room 2W100]; or

Telephone: (202) 267-3290 Facsimile: (202) 267-3720 Alternate Facsimile: (202) 267-1293; 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.

(End of provision)

3.9.1-3 PROTEST (OCT 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.

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

(End of provision)

3.14-8 NON-FAA INFORMATION SYSTEMS (JAN 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.

(End of provision) General Information Required to Prepare Offers Contractors Providing SAI Program Support During the course of this procurement the FAA may use the services of support contractors in evaluating the Offeror’s proposals. Non-government personnel may be exposed to any proprietary source selection sensitive information included in the proposal. The exclusive responsibility for source selection remains with the Government.

The non-government personnel will have signed non-disclosure statements, have been instructed and agreed to abide by the handling procedures imposed by the source evaluation process, and will be aware of source evaluation precautions and penalties. Evaluators may be drawn from this list. If evaluators are obtained from other companies, this list will be amended at that time.

Offerors must not include the following contractors as any part of their proposed team.

· Regulus Group

· Noblis Inc.

Responsibility for All Proposal Costs The FAA is not responsible for, and will not pay or reimburse, any costs incurred by Offerors in the development or submission of any aspect of their proposals under this SIR. This includes costs associated with any aspect of the proposal activity and any research, studies, or designs carried out for the purpose of incorporation into any part of the proposal. It also includes any costs to acquire or contract for any services or products relating to the offer under this SIR.

Communications and SIR Questions SIR Questions Any questions or requests for clarifications regarding any section of the SIR must be prepared in writing and submitted to the Contracting Officer via electronic mail. Interested parties are strongly encouraged to provide comments and questions as early as possible. Questions and requests for clarifications must be identified and segregated by topic, and must make reference to the applicable SIR section or paragraph, e.g. Section H, Provision H-3, subparagraph (a).

Questions will be answered via amendment and provided to all Offerors on the Internet at www.sam.gov. The FAA will not attribute the questions to the submitting Offerors, but the text of the questions and answers may be available to the general public. Accordingly, Offerors must ensure their questions do not contain any proprietary or confidential information.

All questions and requests for clarifications relating to this SIR must be received by the Contracting Officer by the date listed in Section L.4.2. The FAA reserves the right to not answer any requests received outside of the above timeframe. The Offeror is solely responsible for ensuring that the FAA Contracting Officer has received the questions or requests for clarifications.

Furthermore, Offerors should note that the proposal due date will not be extended solely on the basis of question received within or beyond the timeframe mentioned above. The FAA will not provide verbal responses to Offeror questions, concerns, and clarification requests initiated via Offeror telephone calls.

Any Offeror desiring an explanation or interpretation of the SIR, drawings, specifications, etc., is instructed to make such request. Oral explanations or instructions from the FAA given to Offerors before the award of the contract will be binding only if confirmed in writing.

If an Offeror believes that these instructions contain an error, omission, or are otherwise unsound, the Offeror must immediately notify the Contracting Officer in writing with supporting rationale.

Any information concerning the SIR given to any Offeror will be promptly furnished to all other Offerors. Subject to [Section L.7], correspondence other than Proposal delivery may be via email.

FAA Communications with Offerors The FAA may communicate with Offerors orally or in writing during the evaluation and over the course of the source selection process. The FAA reserves the right to conduct communications with none, one, some, or all competing Offerors. 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, at the FAA’s sole discretion. Communications with one or more Offerors do not necessitate communications with other Offerors. The FAA is not required, however, to request any clarifications or accept any Offeror revisions. Content of the communications may vary among Offerors. The FAA is not obligated to advise Offerors of weaknesses, risks, or deficiencies identified in their proposals. Offerors must not assume that they will be contacted or afforded an opportunity to clarify, discuss, or revise their proposal. Therefore, it is critical that each proposal be fully responsive to the solicitation and its provisions. Offerors are instructed to submit proposals with their most favorable cost and non-cost terms.

Offerors must note the following:

· Communications with one Offeror do not require communications with any other Offeror.

· The FAA communications may occur orally or in writing.

· The FAA reserves the right to conduct communications, discussions, and negotiations with one, some, all, or no Offerors.

· The FAA is not obligated to advise Offerors of weaknesses, risks, or deficiencies identified in their proposals.

· Content of the communications may vary among Offerors

· Any information provided in response to an FAA issued communication may be used in the evaluation of proposals.

Conduct of the Operational Capability Demonstrations Operational Capability Demonstrations (OCD) will take place no sooner than 4 weeks after the submission of Technical Volume Part A. The OCD must occur at a US domestic location.

The Government will contact the Offeror at least ten (10) calendar days prior to an Operational Capability Demonstration to schedule a specific date in March 2024. Successful Offerors must be ready as soon as March 4, 20243 to conduct an OCD. The Government will attempt to arrange the demonstrations between Tuesday and Thursday, but reserves the right to schedule on Mondays and Fridays. Offerors should plan to have the demonstrations from 8:30 AM until 5:00 PM to include a up to a 90-minute lunch and caucus period. The Government attendees will provide their own lunch.

The conduct of the demonstration during the first day must be as follows:

· The activities will start promptly at 9:00am.

· Offerors must provide a brief overview of the demonstration to be witnessed.

· Offerors will be allotted up to 150 minutes prior to lunch to start their demonstration.

· The Government may request a break within this 150-minute period.

· Lunch – approximately 90 minutes

· Offerors will be allotted up to 120 minutes after lunch to continue their demonstration.

· Offerors should be prepared for the Government to caucus for approximately 60 minutes after the completion of the demonstration followed by up to 60 minutes of questions from the Government.

· The demonstration will end promptly at 5:00pm each day

The conduct of the demonstration during the second must follow the same format as the first day. The conduct of the demonstration on third day must follow the same format as the first until lunch. The demonstration will end at the after the morning period of 150 minutes.

If the demonstration is conducted at an airport facility, the SAI Program will not arrange for any necessary access. The capability must be completely ready to be demonstrated at the start of OCD.

Offerors must consider the information and methods identified in Attachment J.3 Requirements Compliance Matrix during their demonstration.

Offerors must be prepared to respond during the demonstration to FAA questions regarding any aspects of their technical proposal. Accordingly, Offerors must ensure they make available to the FAA knowledgeable representatives during the entirety of the demonstration.

Based on information presented by the Offerors, the Government may request additional information, demonstration, and/or may request a reiteration of information previously presented. The Government reserves the right to inquire into any technical area of a proposal that it deems appropriate for further investigation or explanation.

General Information Required to Prepare Offers Offerors must comply with all instructions. Failure to comply with the instructions in any way may result in a determination that the proposal will not be evaluated by the FAA. This determination will be made at the sole discretion of the Contracting Officer. Proposals must conform to all incorporated AMS clauses and be prepared in accordance with this section. To aid in the evaluations, proposals must be clearly and 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. Extraneous narratives such as elaborate brochures, and general corporate public relations material must not be submitted.

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.

General statements that the Offeror understands the requirements of the work to be performed or simple rephrasing or restating the FAA’s requirements will not be considered adequate and may result in weaknesses, risks, and/or lower evaluation scores or may be cause for rejection of the proposal and/or result in the Offeror being eliminated from consideration for the contract award.

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, ambiguity, or lack of detail. Submittals containing omissions or incomplete responses to the requirements of this SIR, or that merely paraphrase the Statement of Work, or that use nonspecific phrases such as "in accordance with standard procedures" or "well-known techniques" will also be considered inadequate and may result in weaknesses, risks, and/or lower evaluation scores or may be cause for rejection of the proposal and/or result in the Offeror being eliminated from consideration for the contract award. Offerors must ensure that each volume of their proposal contains all relevant information for the evaluation. Offerors must not assume that information in one volume will be used in the evaluation of another. For example, Offerors must not assume that the technical evaluation will be based upon information contained within Volume II (Cost/Price).

The FAA reserves the right to update QPL requirements and associated instructions in subsequent updates throughout the duration of the program.

It is the Offeror’s responsibility to ensure the completeness of its proposal. The evaluation of proposals will be conducted on the basis of the information contained in the written proposal, communications (to the extent the FAA elects to engage in communications), and past performance information received from other sources, if any. Offerors should assume that the FAA has no prior knowledge of their proposed solution, capability, and/or experience and that the FAA will base its evaluation on the information presented by the Offeror. The Government will not assume that an Offeror possesses any capabilities not specified in the proposal. Offerors are strongly encouraged to ensure that their proposals are complete and fully responsive to the SIR upon initial submission.

The Offeror must mark any data that may contain trade secrets, copyright data, or financial information that the Offeror or proposed team members do not want to be disclosed for any purpose other than the evaluation of the proposal. The markings should be in accordance with AMS clause 3.2.2.3-16, Restricting, Disclosing, and Using Data (July 2004). Owing to the FAA’s obligations under federal law, including the Freedom of Information Act (FOIA), the FAA may require the Offeror to provide justification for its assertion that certain material should be treated as exempt from disclosure.

The proposal must be signed by an official who is legally authorized to obligate the Offeror to a contract.

The FAA will not consider multiple proposals from the same Offeror. Offerors must propose a service meeting all requirements in this SIR; however, each Offeror may propose one option involving enhanced capabilities that are above and beyond the requirements provided within this SIR.

Volume Submissions and Projected Acquisition Milestones The following acquisition milestones are provided for information purposes only and are subject to change:

Proposal Delivery Instructions Offerors are fully responsible for ensuring that proposals are submitted in accordance with the schedule above to the email addresses below:

and

Submissions must be made by 4pm Eastern Time on the due date. Delivery after the appointed time will not be accepted. File sizes must be limited to 15Mb. Multiple emails are permissible.

Alternate Proposals No alternate proposals will be accepted. The Government reserves the right to award a basic ordering agreement and/or a contract based on initial submittals received. Therefore, each Proposal should contain the Offeror’s best terms from a price and technical standpoint. An objection to any of the terms and conditions of this SIR may constitute an exception, which may make the offer unacceptable.

Format Instructions Offerors must furnish the proposal in seven (7) separate volumes:

Volumes must be submitted in the quantities specified below.

Electronic copies, including the Price Model, must be compatible with Microsoft Office 365. The electronic copies must be provided electronically with file names that are consistent with the structure of the proposal. Electronic copies must be print ready in accordance with the instructions below.

Standard page size must be 8-1/2 by 11-inch. The font must be 11 point (with the exception of pre-printed product literature). 8 point font is acceptable for tables, charts, and graphics. Each page must have at least 1” margins on each side of the page. Fold-outs are permissible up to 11" by 17", such sheets must count as two (2) pages. The Offeror’s proposals must not exceed the page limitations set forth in Table 1 below. If page limits are exceeded, those pages in excess of the number allowed may be disregarded and not evaluated. Pages that exceed the maximum page limitation will not be evaluated. All pages of each part must be appropriately numbered, and identified with the name of the Offeror, the date, and the solicitation number to the extent practicable; this information and only this information may be included as headers and footers in the 1” margin space. Offerors must not cross-reference other volumes of the proposal. A single printed side of 8-1/2 by 11-inch paper counts as one page. Pages with printing on both sides count as two pages. A Cover Page, Table of Contents, Table of Tables, Table of Figures, Glossary of Terms, and Index may be included but will not be evaluated and will not be included as part of the page count.

The Presentation Slides for Volume I Operational Capability Demonstration must utilize a corporate PowerPoint presentation template. If animation is used within the presentation, the slide must be legible with all animation layers displayed or printed. Embedded movies must not be used. A Cover Slide, Table of Contents, Table of Tables, Table of Figures, Glossary of Terms, and Index may be included but will not be evaluated and will not be included as part of the page count.

In the event of any conflicts between the Offeror’s prices described within its Price Model and the remainder of its Cost/ Price Volume, the Price Model will take precedence. The Offeror must provide a certification that the prices proposed, and the total proposed price contained in the electronic version of the proposal is exactly the same as the electronic version provided within the Price Model.

In order for the technical proposal to be evaluated strictly on the merit of the material submitted, NO PRICE INFORMATION MAY BE INCLUDED IN VOLUME I. Proposals that do not comply may be rejected.

Additionally, electronic submissions of the Volume II Cost/Price must be submitted with the Government provided Price Model with all imbedded functionality still enabled.

As described in Section M, this SAI SIR is structured into 3 Tiers. Some materials submitted will be used in multiple Tiers of the acquisition and some will be used in one Tier. Table 1Table 1 identifies the applicable Tiers.

Table 1: Proposal Volumes

* The 60 page limit applies to the sum of the pages in Volume I.A and I.B. Offerors have discretion on to how to apportion the 60 page limit across the volumes.

** Documentation of the Operational Capability Demonstration will be a set of presentation slides (limited to no more than 75 slides).

Proposal Revisions Proposal modifications are limited to those modifications required to address FAA communications or specific changes depicted in a SIR amendment. In response to FAA communications, Offerors must limit modifications to their proposals to the pertinent proposal sections and the subjects of the communications. If change pages are required, except for the Price Model, the Offeror must indicate the changes exactly and must not exceed the total page count listed for the original proposal, as set forth herein. Instructions will be issued with any SIR amendment regarding any effect to total page count of the proposals affected. Any information provided by the Offeror outside the scope of the Communication Item or the SIR amendment will not be used in the evaluation. The FAA reserves the right to accept none, some, or all of an Offeror’s proposal modifications.

The FAA may correct administrative errors, such as mathematical errors or inaccurate cross references. In this event, and in the FAA’s sole discretion, the FAA will notify the Offeror of the change and may afford the Offeror an opportunity to submit a corrected proposal. The FAA’s decision to permit one or more Offerors to submit corrected proposals does not require the FAA to allow other Offerors to submit corrected proposals.

Volume I Volume I is comprised of three parts: the Technical written volume, Volume I.A and Volume I.B, and the Operational Demonstration Capability volume, Volume I.C. The requirements for both parts are as follows:

Volume I.A and Volume I.B - Technical Volume The Technical Proposal must describe how the Offeror and its proposed solution will meet the requirements and perform the efforts required by the Performance Work Statement, the SAI Requirements Document, and other sections and attachments of this SIR. The allocation of the page limit for Volume I.A between the individual parts is left to the discretion of the Offeror.

The following requirements apply to the technical volume. The technical volume is considered in Tier 1 and Tier 3. Material addressing Sections L.5.1.1 thru L.5.1.3 must be contained in Volume I.A. Material addressing Sections L.5.1.4 thru L.5.1.5 must be contained only in Volume I.B. The material in Volume I.A addressing the following requirements must be presented in a manner so that information related to the a) items below is clearly identifiable to the reader.

System Factor The Offeror must describe the end-to-end system it proposes for SAI. This must include the following topics:

System Subfactor: Architecture and Overall Solution Offerors must describe the architecture and design of their proposed SAI solution, including the software, hardware, and firmware selected, the associated rationale for each, the processes used, the bandwidth required, the space required, the support functions provided and how this architecture and associated capabilities enable the solution to

a) Meet the critical SAI requirements

b) Meet SAI requirements not identified as critical System Subfactor: Functional and Performance Requirements The Offeror must describe the different functions of its proposed SAI solution including how its proposed solution:

a) Meets the critical SAI functional and performance requirements

b) Meets SAI functional and performance requirements not identified as critical

In addition, the Offeror must provide a detailed description of the following characteristics of the proposed SAI Solution:

· Target display methodology and whether it is data driven or periodic. If periodic, include update rate, update time, and any propagation used. For either type, describe how long Target icons and data tags are displayed when there is excessive dither (e.g., 1.0 seconds), missed updates, or the Target has transitioned into a stationary slow squit rate (1090ES).

System Subfactor: Technology Readiness The Offeror must describe how the proposed end-to-end solution already meets at a minimum Technology Readiness Level 8 (TRL-8). The Offeror must describe how the proposed end-to-end solution has been proven to work in its final form and under expected conditions. Specifically, the Offeror must describe how:

· All solution software has been thoroughly debugged and fully integrated with all operational hardware and software systems.

· All user documentation, training documentation, and maintenance documentation completed.

· Verification and Validation (V&V) was completed.

· All functionality has been successfully demonstrated in simulated operational scenarios.

· The end-to-end solution has been proven in an operational environment.

In addition, if the Offeror is selected to participate in the Tier 2 Operational Capability Demonstration, the Offeror must provide the facility and location where they would conduct the OCD. Offerors are encouraged to provide multiple domestic locations.

System Subfactor: Manufacturing Readiness The Offeror must describe how the proposed solution meets at a minimum Manufacturing Readiness Level 8 (MRL-8). The Offeror must describe how it has demonstrated a pilot line manufacturing capability and is ready to perform a low-rate initial production or has a greater manufacturing capability. Specifically, the Offeror must describe how:

· The detailed design is complete and stable enough to begin production.

· All materials, manpower, tooling, test equipment, and facilities are proven on the pilot line and are available to meet the planned low-rate production schedule.

· Known producibility risks and issues pose no significant challenges for low-rate production.

· Supplier qualification testing and first article inspections have been completed.

· The industrial base has been assessed and shows industrial capability is established to support production.

Implementation Factor The Offeror must describe its Implementation Approach to supporting the SAI. To add specificity to this approach, the Offeror must describe how its approach is tailored to an implementation Nashville International Airport (BNA). The Offeror’s approach must address the following topics:

Implementation Subfactor: Planning The Offeror must describe how it conducts planning for the implementation of a solution and how its approach will accommodate either acceleration or deceleration of the implementation schedule. The Offeror must describe how it coordinates with FAA and non-FAA entities in the planning process. The Offeror must describe how its proposed solution:

a) Meets all the SAI Implementation planning requirements.

Implementation Subfactor: Installation The Offeror must describe how its approach aligns with the FAA processes for implementation into staffed, NAS-operational facilities, and how its installation approach does not disrupt operational airports. The Offeror must describe how it coordinates with FAA and non-FAA entities during installation. The Offeror must describe how its proposed solution:

a) Meets all the SAI Implementation installation requirements.

Implementation Subfactor: Acceptance The Offeror must describe how its implementation approach, including tasks, their durations, and sequencing assuming no delays associated with Government review, ensures the verification of the acceptance criteria established for SAI and minimizes the impact of FAA action and approvals. The Offeror must describe how its proposed solution:

a) Meets the SAI acceptance requirements within the delivery timeframe identified within Section F.7.

Operations and Maintenance Factor The Offeror must describe its Operations and Maintenance Approach to supporting the SAI. This must include the following topics:

Operations and Maintenance Subfactor: Operations Management The Offeror must describe the operations of its solution, the associated maintenance activities, and the management of both these activities. This description must include its approach for planning, developing, deploying and managing software and hardware releases. The Offeror must describe its processes and capabilities for detecting faults and off-nominal operations. The Offeror must describe the processes it employs for restoration of the service. The Offeror must describe how it coordinates with both FAA and non-FAA entities during operations of the system and during service restoral process. The Offeror must describe how its proposed solution:

a) Meets all the SAI Operations Management requirements.

Operations and Maintenance Subfactor: Customer Support The Offeror must describe the Customer Service functions and processes of its solution, the associated trouble ticketing system used, and the escalation and resolution of operational issues. The Offeror must describe how its proposed solution:

a) Meets all the SAI Customer Support requirements.

Operations and Maintenance Subfactor: Training The Offeror must describe the training materials provided with its solution, the types of users its training encompasses, and the time expected for training. The Offeror must describe how its proposed solution:

a) Meets all the SAI Training requirements.

Experience Factor Experience is separate from Past Performance. For this aspect Offerors must describe: Its team’s experience with specific projects and programs within the last 6 years that are directly applicable to the activities and solution requested for SAI. Alternatively, Past Performance evaluates the success of providing solutions. Experience must be identified within Volume I.B.

Enhanced Functionality Factor Offerors may identify enhanced functionality not contained within this SIR and requirements that its system will meet. This functionality can include meeting the examples contained within Attachment J.2 Strategic Plan and the Enhanced Functionality work contained within Section C.4.3.1 - Performance Work Statement. Offerors must provide their approach to addressing these work efforts. These requirements and efforts must be identified within Volume I.B.

If enhanced functionality is offered, the Offeror must provide a detailed description of the following characteristics of the proposed SAI Solution:

· Capabilities the solution provides for the user to enter and display custom data (e.g., scratch pad, closed runways, etc).

· Any ADS-B data filtering capabilities associated with Link Version, Navigation Integrity Code (NIC), Navigation Accuracy Category for…