CSS-FD SIR Section L - DRAFT_v2.0.pdf

SECTION L Solicitation #

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS CSS-FD

L - i

SECTION L: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

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

L.2 AMS CLAUSES AND PROVISION INCORPORATED IN FULL TEXT

L.3 POINT OF CONTACT FOR TECHNICAL INQUIRIES

L.4 GENERAL ACQUISITION PROVISIONS AND INSTRUCTIONS

L.4.1 RESPONSIBILITY FOR PROPOSAL COSTS

L.4.2 TIME FOR RESPONSE TO SIR QUESTIONS

L.4.3 PERIOD OF OFFER

L.4.4 OFFEROR COMMUNICATIONS

L.4.5 PROPOSAL MODIFICATIONS

L.5 SUBMISSION INSTRUCTIONS

L.6 PROPOSAL PREPARATION INSTRUCTIONS

L.6.1 PROPOSAL FORMAT

L.6.2 DISCREPANCY NOTIFICATION

L.6.3 RESTRICTED DISCLOSURE LABELING

L.6.4 EXCLUDED CONTRACTORS

L.7 VOLUME I – TECHNICAL/MANAGEMENT VOLUME

L.7.1 EXECUTIVE SUMMARY

L.7.2 TECHNICAL/MANAGEMENT PROPOSAL

L.7.2.1 Factor 1 – Technical Approach L.7.2.2 Factor 2 – In-Service Management L.7.2.3 Factor 3 – Management Approach

L.8 VOLUME II – PAST PERFORMANCE PROPOSAL SUBMISSION

L.9 VOLUME III – PRICE PROPOSAL SUBMISSION INSTRUCTIONS

L.9.1 GENERAL

L.9.2 PRICE PROPOSAL BID MODEL

L.9.3 PRICE NARRATIVE

L.9.4 BASIS OF ESTIMATE

L.10 VOLUME IV – SMALL-BUSINESS SUBCONTRACTING PLAN

L.11 VOLUME V – OFFER AND OTHER DOCUMENTS

L.11.1 RESPONSIBILITY DETERMINATION INFORMATION

L.11.2 SOLICITATION/CONTRACT FORM

L.11.3 REPRESENTATIONS AND CERTIFICATIONS

L.11.4 POTENTIAL ORGANIZATION CONFLICTS OF INTEREST (OCIS) AND OCI MITIGATION PLAN

L - 1

SECTION L: INSTRUCTIONS, CONDITIONS, AND NOTICES TO

OFFERORS

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

(JULY 2019)

This screening information request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make the full text available, or offerors and contractors may obtain the full text via the internet at: https://fast.faa.gov/contractclauses.cfm.

Clause Clause Title

3.2.2.3-1 False Statements in Offers (April 2024)

3.2.2.3-6 Submittals in the English Language (September 2020)

3.2.2.3-7 Submittals in U.S. Currency (September 2020)

3.2.2.3-12 Amendments to Screening Information Requests (April 2024)

3.2.2.3-13 Submission of Information/Documentation/Offers (April 2024)

3.2.2.3-14 Late Submissions, Modifications, and Withdrawals of Submittals (April

2024)

3.2.2.3-17 Preparing Offers (April 2024)

3.2.2.3-18 Prospective Offerors Requests for Explanations (April 2024)

3.2.2.3-19 Contract Award (July 2004)

3.2.2.3-31 Facilities Capital Cost of Money (July 2004)

3.6.2-7 Pre-award On-Site Equal Opportunity Compliance Review (July 2023)

L.2 AMS CLAUSES AND PROVISION INCORPORATED IN FULL TEXT

AMS 3.2.2.3-15 Authorized Negotiators (April 2024)

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

Name:______________________________________________

Title:_______________________________________________

Phone number:_______________________________________

Email:______________________________________________

(End of provision) https://fast.faa.gov/contractclauses.cfm

L - 2

3.2.2.3-16 Restricting, Disclosing and Using Data (April 2024)

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

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

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

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

Numbers or other identification of pages:

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

3.2.2.3-20 Offers (January 2018)

(a) The offeror (you) must submit responses to this SIR by the following electronic means: email

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 _maria.j.ashby@faa.gov.

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

AMS 3.2.4-1 Type of Contract (April 1996)

L - 3

The Government contemplates award of a hybrid indefinite delivery, indefinite quantity (IDIQ) contract resulting from this SIR with a combination of firm fixed price (FFP), cost reimbursable, and time and materials (T&M) contract line item numbers (CLINs) and task orders (TOs), as issued.

3.9.1-3 Protest (April 2024)

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.

L - 4

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

L - 5

AMS 3.2.2.3-2 Minimum Offer Acceptance Period (July 2004)

(a) 'Acceptance period,' as used in this provision, means the number of calendar days the FAA

(we, us) has to award a contract from the date the SIR specifies for receiving offers.

(b) This provision supersedes any language about the acceptance period appearing elsewhere in this SIR.

(c) We require a minimum acceptance period of TBD calendar days [the CO should insert the number of days].

(d) The offeror (you) may specify a longer acceptance period than the period shown in paragraph

(c). To specify a longer period, fill in the blank: The offeror allows the following acceptance period: _____ calendar days.

(e) We may reject an offer allowing less than the FAA's minimum acceptance period.

(f) You agree to fulfill your offer completely if the FAA accepts your offer in writing within:

(1) The acceptance period stated in paragraph (c) of this provision; or

(2) Any longer acceptance period stated in paragraph (d) of this provision.

(End of provision)

AMS 3.3.1-36 Availability of Funds - Option Periods under a Continuing Resolution (April

2008)

Due to the possibility of the enactment of a continuing resolution in lieu of an annual appropriation, full fiscal year funding may not be available for an entire contract option period.

In the event of a continuing resolution, FAA will only be liable for an amount based on the time period specified by the continuing resolution. The amount of funds made available by the continuing resolution will be specified by subsequent modification. If the contractor provides services in excess of the funded amount or beyond the covered period, the contractor does so at its own risk.

(End of Clause)

AMS 3.6.1-17 North American Industry Classification System (NAICS) Code (October

2022)

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

L - 6

541511

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 $34.0M .

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

(End of provision)

L.3 POINT OF CONTACT FOR TECHNICAL INQUIRIES

The Contracting Officer (CO) is the sole point of contact for this acquisition. Offerors are instructed to direct all questions or concerns to the CO listed in Section G of this SIR.

L.4 GENERAL ACQUISITION PROVISIONS AND INSTRUCTIONS

L.4.1 RESPONSIBILITY FOR PROPOSAL COSTS

The Government 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.

L.4.2 TIME FOR RESPONSE TO SIR QUESTIONS

Any questions or clarifications regarding any section of the SIR must be prepared in writing and submitted to the CO via electronic mail. Questions/clarifications must be identified and segregated by topic and must make reference to the applicable section or paragraph, if applicable

(e.g., Section H, Provision H-3, subparagraph (a)). The Government will provide all Offerors with a copy of all questions and the associated responses. The source of the questions/clarification will not be identified.

All questions and clarifications relating to this SIR must be received by the CO by MONTH XX, 20XX. The Offeror is responsible for ensuring that the FAA CO has actually received the questions or clarifications.

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

L.4.3 PERIOD OF OFFER

L - 7

Proposals must be binding for 360 calendar days from the proposal due dates. Offerors may propose a validity period more than 360 days. If selected for award, all prices, terms, conditions, and other commitments within the proposal are binding.

L.4.4 OFFEROR COMMUNICATIONS

All communications will be documented and controlled through the CO to ensure that Offerors are treated equitably and with the same level of interest. Communications with one Offeror does not require communications with any other Offeror.

The Government communications may occur orally or in writing. If the Government communicates with Offerors it may be in the form of Communication Items. Communication

Items may be limited to questions requesting further clarification of specific content in an

Offeror’s proposal. The Government is not obligated to advise Offerors of weaknesses or risks identified in their proposals. Communication Items will be conveyed in writing.

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

L.4.5 PROPOSAL MODIFICATIONS

Proposal modifications are limited to those modifications required to address Government-identified Communication Items or specific changes depicted in a SIR amendment. In response to Government-issued Communication Items, Offerors are instructed to limit modifications to their proposals to the pertinent proposal section and the subject of the Communication Item. If change pages are required, the Offeror must not exceed the total page count listed for the original proposal, as set forth herein. In the response to a SIR amendment, instructions will be issued with the amendment regarding any effect to total page count of the proposals affected. Any information outside the scope of the Communication Item or the SIR amendment will not be considered during the evaluation.

If the modification is for an administrative change such as a mathematical error or inaccurate cross reference, Offerors will not be afforded the opportunity to update their proposals other than to correct the administrative error noted in the communication.

L.5 SUBMISSION INSTRUCTIONS

Offerors are instructed to assemble and identify proposal volumes in accordance with the Table

L-1. Offerors must ensure that all volume titles and associated content are compiled and delivered within the page limitations.

Proposals must be submitted no later than 3:00 PM Eastern Time (ET) on [TBD] via email.

With the exception of the Past Performance Survey responses that are submitted to the CO via e-mail, the FAA will not accept any submission made by facsimile, e-mail, or any other means. If the CO does not receive a complete proposal submission by the specified date and time via email, it may not be evaluated.

L - 8

No alternate proposals will be accepted.

Table L-1: Proposal Organization

VOLUME NUMBER VOLUME TITLE PAGE LIMIT

I Technical/Management 30

II Past Performance 6

III Price No limit

IV Small-Business Subcontracting Plan 5

V Offer and Other Documents No limit

L.6 PROPOSAL PREPARATION INSTRUCTIONS

This section provides general guidance for preparing proposals as well as instructions on format and content of the proposal.

It is incumbent upon the Offerors to ensure that all requirements of Section L are addressed.

Offerors should not assume that the FAA will contact any Offeror if Section L requirements are not met.

L.6.1 PROPOSAL FORMAT

a) Proposals must be provided in standard letter size 8-1/2 by 11-inch format. Unless otherwise specified, the font for text must be Times New Roman, size 12 point, with one-inch margins for the left, right, top and bottom of each page. The font for graphics, illustrations, and charts must be eight point or larger. The Offeror may not use oversize pages. The proposal pages must be numbered sequentially. Any items imbedded within a document must be objects only, not links. Offeror responses to be submitted using a

SIR attachment form or worksheet, must follow the formatting for that attachment.

b) A page is defined as one face of a sheet of paper containing information. Proposals must not exceed the page limitations listed in Table L-1.

c) The following materials are excluded from the page count limitation: Volume Covers, Title Pages, Tabs, Tables of Content, Lists of Figures, Glossaries, Acronyms, Abbreviation Lists, Contractor submittal letter, and transmittal letters. Any submission exceeding a page limitation will only be evaluated up to the established page limitation.

d) Proposals must contain comprehensive, concise, and factual information. General statements that the Offeror understands the requirements of the work to be performed or simple rephrasing or restating of the Government’s requirements will be considered inadequate. Similarly, submittals that contain omissions or incomplete responses to the requirements of this SIR, that merely paraphrase the Performance Work Statement (PWS)

L - 9 or that use nonspecific phrases such as "in accordance with standard procedures" or

"well-known techniques" will also be considered inadequate. Deficiencies of this kind will render the proposal non-responsive and cause the offer to be rejected.

e) Any trade secrets, copyright data, or financial information that the Offeror or proposed subcontractors do not want disclosed must be marked in accordance with Clause 3.2.2.3-

16, Restricting, Disclosing and Using Data (April 2024).

Each proposal requirement (Volume) must be in its own file. The file name must adhere to the following naming convention using the Volume/Part names listed in Table L-1.

“Offeror Name – CSS-FD VOL # - Volume - and Description”

L.6.2 DISCREPANCY NOTIFICATION

If an Offeror believes that these instructions contain an error, omission, or are otherwise unsound, it must immediately notify the CO in writing with supporting rationale. Otherwise, Offerors are instructed to confirm that they know of no discrepancies. Offerors must provide this notification by TBD.

L.6.3 RESTRICTED DISCLOSURE LABELING

Offerors who include in their proposals information that they do not want to disclose to the public for any purpose or 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 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.” However, 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.

L.6.4 EXCLUDED CONTRACTORS

The firms listed below have provided assistance to the Government in this acquisition and all participants have signed Non-Disclosure and Conflict-Of-Interest (COI) statements. Offerors must not include these contractors or their subcontractors as part of their team. The Government currently intends for the following companies to participate in the evaluation, but reserves the right to include others:

• Capital Group, LLC

• Cavan Solutions

• ITstrategy, Inc.

• LS Technologies, LLC

• Mosaic ATM

• Nira, Inc.

• Noblis, Inc.

• Regulus Group

• Space Metrics, Inc.

L - 10

L.7 VOLUME I – TECHNICAL/MANAGEMENT VOLUME

The Offerors’ Technical/Management Volume must fully substantiate their approach and demonstrate an understanding of the requirements. Offerors are instructed not to include product manuals, sales brochures or vendor "slick sheets” as a response to Section L requirements.

L.7.1 EXECUTIVE SUMMARY

The Offeror must provide an Executive Summary that summarizes the contents of its

Technical/Management Proposal. The Executive Summary must not contain any cost or pricing information.

L.7.2 TECHNICAL/MANAGEMENT PROPOSAL

The Offeror must submit a Technical/Management Proposal that addresses the following three

(3) Factors.

L.7.2.1 Factor 1 – Technical Approach

L.7.2.1.1 Sub-factor 1 – Technical Solution

In relation to the five elements outlined below, the Offeror must provide its solution to meet the requirements identified in Attachment J-1, Functional and Performance Specification (FPS).

L.7.2.1.1.1 Element 1 – Core Services

Provide your proposed solution for Core Services and:

1. Describe how your proposed solution for Data Validation and Data Transformation

Services meets the requirements identified in FPS Sections 3.1.1 and 3.1.2.

2. Describe how your proposed solution for Flight Data Reconciliation Service meets the requirements identified in FPS Section 3.1.3.

3. Describe how your proposed solution for Flight Object Management and Flight Identifier

Management Services meets the requirements identified in FPS Section 3.1.4 and 3.1.5.

4. Describe how your proposed solution for Constraint Service meets the requirements identified in FPS Section 3.1.7.

5. Describe how your proposed solution for Orchestration Service meets the requirements identified in FPS Section 3.3.

L.7.2.1.1.2 Element 2 - CSS-FD SWIM Services

Provide your proposed solution for CSS-FD SWIM Services, and:

1. Describe how your proposed solution for implementation of the CSS-FD SWIM Services aligns with FF-ICE, ICAO, and FIXM guidance contained within the CSS-FD Service requirements identified in FPS Section 3.2 and Section 5.2.3.

2. Describe how your proposed solution for Flight Data Reconstitution and Flight Data

L - 11

Request Services meets the requirements identified in FPS Sections 3.2.1 and 3.2.4.

3. Describe how your proposed solution for Filing Service meets the requirements identified in FPS Section 3.2.2.

4. Describe how your proposed solution for Data Publication Service meets the requirements identified in FPS Section 3.2.3.

5. Describe how your proposed solution for Trial Service meets the requirements identified in FPS Section 3.2.5.

L.7.2.1.1.3 Element 3 – Data and Systems Management

Provide your proposed solution for Data and Systems Management, and:

1. Describe how your proposed solution for Identity and Access Management meets the requirements identified in FPS Section 3.1.6.

2. Describe how your proposed solution for Data Management Services meets the requirements identified in FPS Section 3.1.8.

3. Describe how your proposed solution for System Monitoring and Management meets the requirements identified in FPS Section 3.4.

4. Describe how your proposed solution for System Logging meets the requirements identified in FPS Section 3.5.

L.7.2.1.1.4 Element 4 – Performance

1. Describe how your proposed solution meets the Flight Plan Handling Performance requirements identified in FPS Section 4.1.

2. Describe how your proposed solution meets the System Load requirements identified in

FPS Section 4.2.

3. Describe how your proposed solution meets the Reliability, Maintainability and

Availability requirements identified in FPS Section 4.3.

L.7.2.1.1.5 Element 5 – Architecture, Interfaces, Integration, and Security

1. Describe how your proposed solution can effectively integrate into and optimize the use of the GSCE identified in Attachment J-9, FAA Cloud Architecture.

2. Describe how your proposed solution considers the design characteristics in PWS Section

C.4.2.5.1 and supports the strategic objectives in Attachment J-0, CSS-FD Strategy, resulting in software that encourages interoperability, flexibility, and enhances sustainability of the CSS-FD solution.

3. Describe how your proposed solution supports the interfaces to other FAA Enterprise

Architecture Elements and the Data Interfaces identified in FPS Sections 5.1 and 5.2.

4. Describe how your proposed solution supports the evolution and development of the

CSS-FD Business Rules and the Flight Object outlined in Attachment J-10, CSS-FD

Business Rules and Attachment J-12, Flight Object (FO) Workbook.

5. Describe how your proposed solution is extensible based on the criteria defined in PWS

L - 12

Section 4.2.5.1 to effectively integrate Phase 2 capabilities.

6. Describe how your proposed solution enables the “High” impact level system authorization of CSS-FD in accordance with Attachment J-2, Security Controls.

L.7.2.1.2 Sub-factor 2 – Solution Development

In relation to the three elements outlined below, the Offeror must describe its proposed approach to satisfying the requirements in Section C.4.2 of the PWS and achieve the objectives in

Attachment J-0, CSS-FD Strategy.

L.7.2.1.2.1 Element 1 – System Engineering

1. Describe your System Engineering approach and methodologies used to address all design, development, integration, test, and in-service management to ensure successful delivery and operation of CSS-FD.

2. Describe your approach to conducting Requirements Review(s) (PWS Section C.4.2.2) and Software Design Review(s) (PWS Section C.4.2.4), how it supports your software development approach and aligns with your proposed schedule milestones in Section F.

3. Describe your approach to developing software documentation to meet the requirements of PWS Section C.4.2.3. Describe your approach to ensuring quality and configuration management during the development of software documentation.

4. Describe your proposed approach to Security requirements of PWS Section C.4.3 and

Attachment J-2, Security Controls to achieve an initial security authorization, on an annual recurring basis, and when there are major changes.

L.7.2.1.2.2 Element 2 – Software Development

1. Describe your Software Development approach and plan, methodology, techniques, software measurements reporting, and tools that will be employed to satisfy all PWS requirements, address all aspects of the software development lifecycle, resulting in successful delivery of CSS-FD.

2. Describe how your proposed Software Development approach incorporates configuration management and quality assurance to ensure the successful delivery of CSS-FD.

3. Describe your approach for utilizing FAA-provided GSCE and/or Contractor environments including the use of development, test, and production environments throughout the CSS-FD lifecycle (i.e., solution development and in-service management).

4. Describe your approach to conduct Collaborative Design Workshops to promote collaboration and facilitate Government acceptance.

5. Describe your experience implementing your proposed Software Development approach for work efforts of similar size, scope and complexity to CSS-FD.

L.7.2.1.2.3 Element 3 – Test and Evaluation

1. Describe your proposed approach to plan, manage, document, and conduct a Test and

Evaluation program that satisfies the requirements in PWS Section C.4.2.6.

L - 13

2. Describe how your proposed Test and Evaluation approach aligns with your software development approach to support the achievement of schedule milestones in Section F.

3. Describe your proposed Test Capability Accreditation approach to ensure tests are acceptable for the intended purpose and will yield accurate results.

4. Describe how your proposed Test and Evaluation approach incorporates configuration management and quality assurance to ensure successful delivery of CSS-FD.

5. Describe your experience utilizing your proposed Test and Evaluation approach for work efforts similar in size, scope and complexity to CSS-FD.

L.7.2.2 Factor 2 – In-Service Management

1. Describe your proposed In-Service Management approach including software maintenance and Tiered Support.

2. Describe your proposed approach to training development to support the achievement of schedule milestones contained in Section F.

3. Describe your knowledge, skill and experience developing and validating training of a similar nature to those identified in the PWS Section 4.5.6.

4. Describe your experience utilizing your proposed approach for In-Service Management for work efforts similar in size, scope and complexity to CSS-FD.

L.7.2.3 Factor 3 – Management Approach

1. Describe your proposed program management organization that will oversee the required work efforts identified in PWS Section C.4. Discuss the role and responsibility of any subcontractors, if applicable.

2. Describe your proposed program management approach to ensure the successful execution of the work efforts identified in PWS Section C.4 regarding cost, schedule, and technical performance.

3. Describe your proposed program management approach to facilitate effective collaboration with the Government.

4. Describe how your proposed Key Personnel possess the expertise, experience, and qualifications necessary to successfully accomplish the responsibilities of their respective positions, as described Attachment J-6, Labor Category Qualifications.

5. Provide an integrated master schedule (IMS) and schedule narrative to include the following:

• Section F milestones and deliverables in Attachment J-4, Contract Data

Requirements Listing (CDRLs),

• Program critical path,

• High-risk efforts, and

• Schedule risk

6. Describe your performance management approach to ensure the performance measures identified in Attachment J-11, Performance Requirements Summary are successfully met and alignment with the Attachment J-0, CSS-FD Strategy objectives to include:

L - 14

• Total amount of award fee proposed in terms of percentage of total evaluated price.

• If additional performance measures are proposed, describe how the criteria will be measurable and independently verifiable by the Government.

• Provide a rationale for the proposed additional performance measures and how they will ensure CSS-FD program success.

L.8 VOLUME II – PAST PERFORMANCE PROPOSAL SUBMISSION

The Past Performance Volume Proposal Submission consists of two parts:

Part A – Consists of a Past Performance Summary for each Past Performance References provided by the offeror as part of its proposal submission. Each offeror must identify three (and no more than three) previous or ongoing Past Performance References that are both relevant and recent, as defined in SIR Section M.7.2.1.

Part B – Consists of customer responses to the Past Performance Survey. The points of contact identified by the offeror in Volume II, Part A must submit the survey responses to the CO. The past performance summaries and surveys must correspond to the Past Performance References identified by the offeror in Volume II, Part A.

Each offeror must complete Block 1, “Offeror Information,” of the Past Performance Survey form and then provide it to two customer points of contact for each Past Performance Reference and ask them to complete the survey portion. If a Past Performance Reference is for work performed under a Federal Government contract, the customer points of contact must be the CO and a member of the program staff for the work effort. The program staff points of contact must be individuals with firsthand knowledge of the offeror’s performance, such as a Contracting

Officer’s Representative (COR) or Program Manager (PM). For past performance under other contracts, such as commercial contracts, the Past Performance Survey must be provided to individuals with duties similar to those of the Government CO and COR/PM.

Each point of contact must rate the Offeror’s performance under the referenced contract in terms of quality of work efforts performed and services delivered, timeliness of performance, cost control, program management, and customer relationship, as detailed on the form. Each customer point of contact must e-mail the completed survey to the CO at the e-mail address listed in

Section L.5. The e-mail submissions must be sent from the Government or corporate e-mail addresses of the points of contact. The CO must receive the completed surveys no later than the proposal submission date and time listed in Section L.5. It is the responsibility of Offerors to follow-up with customer point of contact to ensure they submit the completed surveys by the submission deadline.

L.9 VOLUME III – PRICE PROPOSAL SUBMISSION INSTRUCTIONS

L.9.1 GENERAL

L - 15

The Offeror must submit a comprehensive set of pricing data in its Price Proposal that addresses the full scope of their CSS-FD solution and approaches proposed in its

Technical/Management Proposal. Pricing data must not be included in any other volume; if it is, the proposal may be excluded from the evaluation.

The Government anticipates that adequate price competition will exist, so Offerors are not required to submit certified cost and pricing data with their proposals. The Government anticipates that the data required by this SIR will be adequate for its price evaluation; however, the Government reserves the right to request additional information other than certified cost and pricing data if needed to determine the fairness and reasonableness of proposed prices.

L.9.2 PRICE PROPOSAL BID MODEL

Each offeror must submit a completed Price Proposal Bid Model (Attachment L-xa) that contains proposed prices for each contract year across the base period and all option periods. Instructions for populating the Price Proposal Bid Model are provided in the CSS-FD Price Proposal Bid

Model User Instructions (Attachment L-xb).

Failure to submit a fully populated CSS-FD Price Proposal Bid Model may result in an offeror’s proposal being rejected and the offeror not being eligible for the CSS-FD contract award.

L.9.3 PRICE NARRATIVE

The Offeror must submit a Pricing Narrative with its offer that:

Provides sufficient detail to demonstrate that the proposed prices are fair and reasonable;

• Identifies the rationale for any proposed year-to-year escalation;

• Describes the basis for proposing any CLIN as Not Separately Priced (NSP) if it is included within the price of another item and identifies the CLIN(s) where it is included;

and

• Provides rationale and supporting data for proposed labor rates including indirect rates, the basis of the base labor rates, profit, overhead, and year-to-year escalation rates.

L.9.4 BASIS OF ESTIMATE

Each offeror must provide BOEs for all CLINs. The BOEs must identify the labor categories of the personnel providing the support, the period of performance, the labor hours across the period of performance including any variation in the level of support.

The BOEs must identify any planned use of available Government-furnished items and the corresponding adjustments to the proposed prices.

The BOEs must identify all assumptions upon which the prices are dependent.

The BOEs must provide clear traceability between the underlying cost recovery elements and each proposed CLIN. Supporting data within the BOEs must explain what is included in the

L - 16 price of each CLIN and must contain sufficient detail to allow the evaluators to assess the reasonableness, realism, balance, and technical consistency of the proposed prices. Each offeror must clearly identify and explain any CLINs that have interdependencies with other CLINs.

The offeror must provide a separate version of its BOEs that have all Pricing information redacted. The BOEs without Pricing information are referred to as “Technical BOEs” and are for use by the Technical/Management Evaluation Team.

L.10 VOLUME IV – SMALL-BUSINESS SUBCONTRACTING PLAN

The Government is committed to assuring that, to the maximum extent practicable, opportunity is provided to Small Business concerns to participate in the performance of this contract, consistent with efficient performance. A subcontracting plan is required from all offerors who are not small businesses. Each Offeror that is a large business must provide a detailed subcontracting plan that fulfills all requirements contained within AMS Clause 3.6.1-4, Small

Business Subcontracting Plan (April 2024) and addresses the following goals:

• At least 25 percent of the total planned subcontract dollars to Small Businesses;

• At least 14 percent of the total planned subcontract dollars to Small Disadvantaged

Business (SDB);

• At least 5 percent of the total planned subcontract dollars to Women Owned Businesses

(WOB); and

• At least 3 percent of the total planned subcontract dollars to Service Disabled-Veteran

Small Businesses (SDVOSB).

Any non-Small Business offeror that fails to submit an acceptable subcontracting plan or to correct deficiencies within the time specified by the CO may be ineligible for award.

L.11 VOLUME V – OFFER AND OTHER DOCUMENTS

Offerors must provide the information listed in the following sections.

L.11.1 RESPONSIBILITY DETERMINATION INFORMATION

To be eligible for award the Offeror must be determined to be responsible in accordance with

FAA Acquisition Management System (AMS) Source Selection Policy 3.2.2.7 (April 2022). At a minimum, in order to be determined responsible, an Offeror must:

(1) Have or be able to obtain adequate financial resources to perform a contract;

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

(3) Have a satisfactory performance history;

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

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

(a) Production control;

(b) Property control systems;

(c) Quality assurance programs; and

L - 17

(d) Appropriate safety programs; and

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

To assist in this determination, the Contracting Officer may request additional Offeror financial statements and reserves the right to conduct a pre-award survey of any offeror and offeror’s subcontractor. A pre-award survey does not necessarily mean that an Offeror has been selected for award.

L.11.2 SOLICITATION/CONTRACT FORM

The Offeror must complete Standard Form (SF) 33, "SOLICITATION, OFFER AND AWARD” blocks 13 through 18. The representative who signs this form must be authorized to contractually bind the company providing the offer. In SF 33, block 12, the Offeror must include a period of acceptance for its proposal by the FAA of at least TBD calendar days from due date of proposal.

L.11.3 REPRESENTATIONS AND CERTIFICATIONS

Offeror’s must complete and submit all Representations and Certifications included in Section I, Contract

Clauses, and Section K, Representations and Instructions.

L.11.4 POTENTIAL ORGANIZATION CONFLICTS OF INTEREST (OCIS) AND OCI

MITIGATION PLAN

The Offeror must disclose all potential conflicts in accordance with AMS clauses 3.1.7-1, 3.1.7-

2, 3.1.7-4, and 3.1.7-5 in the context of its performance of the CSS-FD contract relative to other contractual or corporate commitments and obligations that have been made or are planned by the

Offeror (including team members and subcontractors). If any potential conflict of interest is identified, the Offeror must submit an OCI Mitigation Plan as part of the Miscellaneous Volume.