Attachment 4 - Draft SIR - Section L (Release).docx

SIR 693KA7-23-R-00002

Surface Movement Radar, Model 4 (SMR4) Section L

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

Table of Contents

POINT OF CONTACT

The Contracting Officer (CO) and Contract Specialist (CS) are the points of contact for this acquisition. All questions or concerns must be addressed to the contracting point of contacts, listed below:

Troy Teachey, Contracting Officer, AAQ-210 Federal Aviation Administration 600 Independence Ave., SW Washington DC 20591 202-267-0522 Troy.Teachey@faa.gov

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

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

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)

CLAUSES AND PROVISIONS INCORPORATED IN FULL TEXT

AMS 3.2.2.3-5 Descriptive Literature (July 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.

AMS 3.2.2.3-20 Offers (January 2018)

(a) The offeror (you) must submit responses to this SIR by uploading files to the FAA Knowledge Services Network (KSN) site specified in Section L.5.2. The FAA will provide a secure upload capability at the specified link. Your offer must be uploaded to the specified link by the time specified in the SIR 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.

(d) Send your offer by uploading files to the FAA Knowledge Services Network (KSN) site 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".

(End of provision) 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.

(End of provision) AMS 3.2.2.3-38 Alternate II Requirements for Certified Cost or Pricing Data or Data Other Than Certified Cost or Pricing Data (Jan 2022)

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

(b) The offeror must provide the following data:

1.__[Contracting Officer (CO) insert the data and the format that are required, including the access to records necessary to permit an adequate evaluation of the proposed price ]*___ 2.__________"__________________________ 3.__________"__________________________ 4.__________"__________________________ [CO should describe the information and format required for this provision.]

(End of clause) 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), and Time and Materials (T&M) type contract resulting from this Screening Information Request (SIR).

(End of provision) AMS 3.6.1-17 North American Industry Classification System (NAICS) Code (January 2021) The North American Industry Classification System (NAICS) code for this procurement is:

334511. 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 twelve-month period cannot exceed 1,250.

(End of provision) 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.

(End of provision)

GENERAL INSTRUCTIONS

Compliance with Instructions Offerors must comply with all instructions in Section L when developing proposals. Failure to comply with the instructions may result in a determination that the Offeror’s proposal is noncompliant. This determination will be made at the sole discretion of the Government. Proposals must conform to all incorporated AMS clauses and provisions and be prepared in accordance with this Section L. 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.

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.

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

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

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

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

Alternate Proposals Alternate proposals are not authorized and will not be accepted.

SIR Questions The FAA Contracting Officer (CO) is the sole point of contact for this acquisition. All questions or requests for clarification regarding any section of the SIR must be prepared in writing and submitted to the Contracting Officer 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 be identified and segregated by document, and must make reference to the applicable SIR section, page and or paragraph.

All questions will be answered via amendment and 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 Officer by . The Offeror is responsible for ensuring that the FAA Contracting Officer has received the questions or clarifications.

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 but no later than . Discrepancies not brought to the attention of the Contracting Officer prior to proposal submission, are waived.

Equal Access to Information 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. Each Offeror must provide in its submission cover letter a point of contact, telephone number, and email address for purposes of initiating all communications.

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:

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

Government communications may occur orally or in writing;

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

Content of the communications may vary between Offerors; and, Any information provided in response to a Government issued communication may be used in the evaluation of proposals.

The purpose of these communications is to ensure that there is mutual understanding between the Government and Offerors on all aspects of this procurement. Offerors are responsible for ensuring that the FAA CO has actually received the question(s) or request(s) for clarification.

Any questions or requests for clarifications regarding any section of this SIR must be prepared in writing and submitted to the FAA CO, via email at the email address identified in Section L.1. The CO must receive all questions and requests for clarifications within fourteen (14) calendar days after the date that the SIR is released to industry. Questions or requests for clarification must be identified and segregated by topic, and make reference to the applicable SIR section, sub-section and paragraph.

The FAA will not attribute authorship of any question or request for clarification to the inquiring Offeror, but the question(s) and answer(s) will be made available to the general public via an amendment to the SIR.

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.

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.

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.

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.

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:

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 name(s) of these replacements or additional support contractors as well as the FAA SIR number will be provided.

The exclusive responsibility for source selection will remain with the FAA.

Organizational Conflict of Interest Pursuant to AMS Guidance 3.1.7, an organizational conflict of interest means that because of an existing or planned activity, an offeror or contractor is unable or potentially unable to render impartial assistance to the agency, or has an unfair competitive advantage, or 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 COI 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 Clause 3.1.7-2, FAA has OCI concerns with the following companies and their subcontractors are prohibited from bidding in any role:

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

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.

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.

PROPOSAL SUBMISSION AND DELIVERY INSTRUCTIONS

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

Table 1 -Procurement Schedule 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 .

2) DELIVERY LOCATION: [Insert KSN Link Here (TBD)].

3) Proposals are 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.

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

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.

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

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

Offerors must mark each sheet of restricted data with the following legend:

“Use or disclosure of information contained on this sheet is subject to the restriction on the title page of this proposal.”

Offerors are warned that this restriction does not limit the Government’s right to use the information if it is obtained from another source without restriction.

PROPOSAL PREPARATION

This section provides general guidance for preparing proposals, as well as 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.

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 or may be cause for rejection of the proposal and result in the Offeror being eliminated from consideration for the contract award.

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.

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 AMS 3.2.2.3-16, “Restricting, Disclosing and Using Data (July 2004).”

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.

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. Electronic copies of proposals will not be returned to Offerors.

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.

Electronic Copies of Proposals The offeror (you) must submit responses to this SIR by the following electronic means: Upload to FAA KSN Site and Email for Subcontractor Proprietary Data. Your offer must arrive at the place and by the time specified in the SIR. 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 2016 (e.g., Excel, Word, PowerPoint)

2) Microsoft Project 2016

3) Adobe Acrobat Reader 11.0 The Offerors must submit any MS Excel spreadsheets in a format that allows formulas within the spreadsheets to be reviewed and manipulated.

Price Data 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.

PROPOSAL ORGANIZATION

The Offeror’s proposal submission must consist of Volume I – Technical Proposal, Volume II – Past Performance, Volume III – Management Proposal, and Volume IV – Price Proposal. The volumes must be organized as follows:

1. System Engineering Design and Development

2. System Performance

3. System Test and Evaluation

4. Implementation

5. Lifecycle Support

2. Systems Engineering Management Plan (SEMP)

3. System/Subsystem Specification (SSS)

4. Proposal Compliance Matrix

5. Description of System Performance Support Information N/A

1. Program Management

2. Draft Integrated Master Schedule (IMS)

3. Offeror’s Risk, Issue, and Opportunity (RIO)

2. Resumes N/A

1. Total Price Summary

2. Firm Fixed Price (FFP) CLIN Pricing

3. Cost Plus Fixed Fee (CPFF) CLIN Pricing Report Sample

4. Cost Reimbursable (CR) Estimated Travel Pricing

5. Time & Material (T&M) Schedule of Rates

6. T&M CLIN Pricing

7. Labor Category Crosswalk

PART B – Detailed Narrative and Supporting Documentation – Cost Type CLINs

1. Direct Labor Rates and Hours

2. Indirect Costs

3. Other Direct Costs/ Subcontractors/ Interdivisional Transfer Materials

4. Fee – CPFF CLINS

5. T&M Labor Category CLINs Detailed Narrative

6. Detailed Narrative and Supporting Documentation – Firm Fixed Price CLINs

PART C – Cost / Price Exceptions, Deviations or Assumptions

PART D – Basis of Estimate

1. Cost Type CLINs

Part E – Enhancements – System/Subsystem Specification

1. Supporting Documentation for Enhancements

2. Basis of Estimate for Enhancements

2. General (AMS T.3.2.3 Appendix 1)

3. Basis of Estimate

4. Subcontractors

1. Contractor Start Date

2. Estimated Material and ODCs

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 sound, complete, valid and achievable; demonstrate an understanding of the requirements, and address all requirements of the Technical Proposal.

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

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

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

2) Opportunities and approach for accomplishment.

3) Potential risks and mitigation strategies.

4) Major milestones.

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

Systems Engineering Design and Development The Offeror must provide a detailed description of their systems engineering design and development of the SMR4, including:

1) How the proposed SMR4 satisfies the functional and performance requirements specified in SMR4 System Specification, FAA-E-XXXX (Attachment J-5), including:

a. The Offeror must provide a detailed description of the scope of development required for the Offeror’s system to meet all specified requirements or identification of requirements that cannot be met. For SMR4 system performance requirements that cannot be met, the Offeror must provide a detailed description of the actual performance their system can achieve.

b. The Offeror must complete the SMR4 System Specification Crosswalk (Attachment J-XX) to trace SMR4 System Specification, FAA-E-XXXX requirements to the Offeror’s System/Subsystem Specification (See Section L.8.8.1).

2) Engineering Process, which defines:

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

b. The strategies that will be employed during the design and development process to reduce risk and to meet cost, performance, and scheduling milestones

3) Software Engineering and Development Process, which defines:

a. Its software development organization and its methodology for project tracking, quality control and oversight.

b. Approach for producing certifiable software and all aspects of the software life cycle processes to include planning, development, verification, configuration management, and quality assurance, including RTCA/DO-278A Assurance Level 4 (AL4).

c. Approach to interface with existing NAS Surface Surveillance systems, including Airport Surface Detection Equipment – Model X (ASDE-X) and Airport Surface Surveillance Capability (ASSC) that is achievable and ensures data and performance integrity.

4) Data Rights to Source Code, Software, and Firmware

a. The Offeror must describe any applicable data rights restrictions to be placed on software (including source code), firmware, and Commercial-off-the-Shelf (COTS) software-firmware, and related technical documentation to be used and/or delivered by the Offeror and subcontractors as part of the SMR4 system requirement.

5) Plans and process to develop and implement a security program to address information/data security needs and considerations for the security requirements in the SMR4 System Specification FAA-E-XXXX.

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

a. Describe the features your system has for minimizing false targets due to clutter, weather, radio frequency interference, and multipath.

b. Describe the capabilities your system has for minimizing interference with other SMRs operating within the same frequency band.

c. Describe the features your system has for mitigating multiple time around clutter and time sidelobes. If your system is not susceptible to these phenomena, explain how system design mitigates these concerns (e.g., pulse compression is not used).

d. Describe what features your system has for plot extraction and its impact on target resolution. Include how large plot integrity is maintained and the ability to distinguish smaller targets in proximity to other targets (e.g., vehicle and aircraft).

e. Describe how your system handles merging and unmerging of target tracks when the plot data becomes unresolved, or when a target enters radar coverage near an established track.

f. Describe the redundancy capabilities of your proposed system.

g. Describe any anti-icing capabilities of your Antenna Array, to include Antenna Array Heater options and functionality.

System Performance The Offeror must provide evidence that their proposed system meets the requirements of their System/Subsystem Specification (SSS). The Offerors proof must include, but is not limited to, the following key performance parameters:

1) Coverage Volume

2) Probability of Detection

3) Range and Azimuth Resolution

4) Positional Accuracy

5) False Tracks Pertaining to the subject, please see Section L.8.8.5 – System Performance Support Information, and Section L.6.2.2 – Electronic Copies of Proposals for instructions.

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 system design and performance requirements as delineated in the SOW and SMR4 System Specification. 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 your 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.

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

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

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

3) Approach to efficiently install and optimize the SMR4 into an operational environment while minimizing impacts to Air Traffic and local airport operations during SMR4 implementation.

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

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

2) Plans for developing a training program that ensures NAS engineers gain the capability to provide second level support engineering support to Technical Operations personnel through the system lifecycle.

3) Plans for managing and providing required supply support functions including an Interim Contractor Depot Level Support (ICDLS) and the transition of depot functions to the FAA Logistics Center.

4) Plans for developing Technical Instruction Books that ensures technical personnel responsible for maintenance on equipment used in the NAS have accurate reference materials.

Technical Proposal – Appendices Offeror System Specification Crosswalk (Volume I, Appendix 1) The Offeror must provide a crosswalk between the requirements in the SMR4 System Specification, FAA-E-XXXX (Attachment J-5) and the requirements in the Offeror’s System/Subsystem Specification (SSS). The crosswalk must identify which SMR4 requirements are currently met by the Offeror’s proposed system and which ones require development. The Offeror must identify any SSS requirements that specify enhanced system capabilities associated with their system that the Offeror wants the Government to consider as a system enhancement. The Offeror must utilize the SMR4 System Specification Crosswalk (Attachment J-XX) for completing the crosswalk. The spreadsheet must be completed in accordance with the Instruction tab in the spreadsheet.

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

System/Subsystem Specification (Volume I, Appendix 3) The Offeror must provide their SSS that was developed in support of their proposed system, as part of their proposal. Contractor format is acceptable. The Offeror must include requirements within their SSS that fully define all capabilities of the proposed system, including those capabilities that exceed the requirements in SMR4 System Specification, FAA-E-XXXX (Attachment J-5). The Offeror’s price proposal must separately address the additional price associated with full verification of the requirements associated with each individual enhanced system capability. At the post-award conference, the Government will identify which, if any, enhanced capabilities and requirements from the Offeror’s SSS that the Offeror must fully verify as part of the formal test and evaluation program.

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

System Performance Support Information (Volume I, Appendix 5) To support the FAA's evaluation of the proposed system, the Offeror must provide test data supporting the claims in their technical proposal with respect to the key performance parameters identified in Section L.8.4. The test data provided must meet the following requirements:

1. Test data provided must be from a system that has been previously accepted by an ANSP for operational use. The data provided must be from the proposed system or from a system representing the production baseline that it is derived from.

1. Test data must include test reports and test procedures accepted by an ANSP for verification of the identified key performance parameters. At a minimum, these documents must include how requirements were tested and the result of the test.

1. The Offeror must submit video captures of high resolution or better video with plot data overlay from a system installed at an active airport. Video captures must demonstrate full adapted range, close-in of a large aircraft, close-in of a small aircraft, and close-in of a vehicle. Video captures must be viewable using commercially available viewing software (e.g., Windows Media Player). If possible, video capture should be from playback of data associated with the test reports.

All electronic files and documentation specified in the paragraphs above must be submitted to the FAA as specified in Section L.6.2.2. These recordings and test reports will be utilized by the FAA to evaluate the systems capabilities relative to the SMR System Specification.

VOLUME II PAST PERFORMANCE (Volume II, Section 1) Past Performance Descriptions The Offeror must submit three (3) past performance descriptions for contracts of similar scope and complexity as the SMR4 Program requirements, including implementation and support requirements. The submissions must be for contracts of recent experience – ongoing or completed within the past five (5) years. The Offeror must submit three (3) past performance descriptions for each subcontractor whose costs exceed 10% of the contract value.

In the absence of relevant past performance as defined above, three (3) recent past performance descriptions closest to the SMR4 Program requirements, as defined in this SIR, may be submitted.

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

Past Performance Description Format The Offeror must use the format provided in Sections L.9.2.1 and L.9.2.2 for each past performance description. The information provided must also be listed in Attachment J-XX, Past Performance List, providing contract and contact information, so that the FAA may review and discuss this with the customers for each contract.

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

1) Company Name;

2) Company Role: Prime or Subcontractor;

3) Program Title;

4) Name of Customer;

5) Customer Address/ Full Mailing Address;

6) Reference: Telephone and Email of Contracting Officer and Program Manager/ Technical Point of Contact that can be traced to the past performance survey;

7) Date the Past Performance Survey is Completed

8) Contract Number;

9) Contract Type(s);

10) Period of Performance;

11) Contract Dollar Value;

12) Scope of Contract: For example, the number of systems delivered for operational use, and other support services that were provided.

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

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

Contract Performance:

1) Quality

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

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

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

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

e. Steps taken to correct and prevent performance problems

2) Timeliness

a. Original Completion Dates for Major Contract Milestones

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

c. Estimated or Actual Completion Dates for Major Contract Milestones

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

e. Steps taken to correct and prevent delivery schedule problems

3) Cost Control

a. Initial Contract Value

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

c. For Completed Contracts: Final value. If different from initial value, please explain.

d. Reasons for changes in cost or cost overruns

e. Steps taken to correct and prevent cost/price problems

4) Program Management

a. Describe actions taken to identify, communicate, and mitigate risks in a timely manner

b. Describe Earned Value Management activities and reporting

c.