E-IDS Draft SIR Section L.pdf

693KA7-18-R-00003

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 1

TABLE OF CONTENTS

Section L - Instructions, Conditions, and Notices to Offerors

L. 1 3.1-1 Clauses and Provisions Incorporated by REFERENCE

L. 2 Clauses and Provisions Incorporated in Full Text

L. 3 General Information Required to Prepare Offers

L.3.1 Contractors Providing E-IDS Program Support

L.3.2 Responsibility for All Proposal Costs

L.3.3 Communications and SIR Questions

L.3.3.1 SIR Questions

L.3.3.2 FAA Communications with Offerors

L.3.3.3 Conduct of the Operational Capability Demonstrations

L. 4 General Information Required to Prepare Offers

L.4.1 Volume Submissions and Projected Acquisition Milestones

L.4.2 Proposal Delivery Instructions

L.4.3 Alternate Proposals

L.4.4 Format Instructions

L.4.5 Proposal Revisions

L. 5 Volume I – Technical

L.5.1 Part A: Technical

L.5.1.1 Factor A.1: Approach

L.5.1.2 Factor A.2: Data Rights

L.5.1.3 Factor A.3: Systems Engineering

L.5.1.4 Factor A.4: System Development

L.5.1.5 Factor A.5: Test and Evaluation

L.5.1.6 Factor A.6: Implementation

L.5.1.7 Factor A.7: Operations, Maintenance, and Logistics

L.5.1.8 Factor A.8: Program Management

L.5.1.9 Factor A.9: Experience

L.5.2 Part B: Operational Capability Demonstration

L.5.2.1 Factor (B.1): User Customization

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 2

L.5.2.2 Factor (B.2): System Management and Control

L.5.2.3 Factor (B.3): Performance During Degraded Operations

L.5.2.4 Factor (B.4): Data Management

L.5.2.5 Factor (B.5): Interface Flexibility

L. 6 Volume II – Cost/Price

L. 7 Volume III – Past Performance

L. 8 Reserved

L. 9 Volume V – Offer and Other Documents

L.9.1 SF 33

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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 3

Section L - Instructions, Conditions, and Notices to Offerors

L. 1 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 (JUL

2004)

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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 4

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)

L. 2 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 (JUL 2016)

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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 5

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

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.

(2) The contractor must provide a list of equipment and software to the FAA Security Operations

Center (SOC) for monitoring during the testing.

(3) The contractor must provide a list of FAA equipment and/or networks to the SOC to which the contractor equipment will connect.

(4) The contractor must provide to the SOC a list of protocols, ports, services, etc. required for the normal operation of the contractor hardware and software.

(5) The contractor must configure all hardware and software in the most restrictive mode to demonstrate features and functions of the contractor provided hardware and software.

(6) The contractor must remove the sample IT equipment and/or software from the FAA system or network if it causes adverse effects on the FAA system or network, or when directed by the

FAA.

(End of provision)

3.2.2.3-5 DESCRIPTIVE LITERATURE (JUL 2004)

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 6

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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 7

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 ELECTRONIC OFFERS (JUL 2004)

(a) The offeror (you) may submit responses to this SIR by the following electronic means indicated below. Your offer must arrive at the place and by the time specified in the SIR.

(b) Electronic 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 electronic offers that do not include required information, or that reject any of the terms, conditions and provisions of the SIR.

(d) We reserve the right to make award solely on the electronic offer. However, if the CO requests, you must promptly submit the complete original (hard copy) signed proposal.

(e) Send your offer electronically to David L. Reynolds, Contracting Officer Federal Aviation Administration 600 Independence Ave, SW Washington DC 20001

(202) 267-0795 David.L.Reynolds@faa.gov

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 8

(f) If you chose to send your offer electronically, we will not be responsible for any failure attributable to transmitting or receiving the offer.

(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.2.3-38 REQUIREMENTS FOR CERTIFIED COST OR PRICING DATA OR OTHER

INFORMATION

(JUL 2010)

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

(End of provision)

3.2.2.3-38 REQUIREMENTS FOR CERTIFIED COST OR PRICING DATA OR OTHER

INFORMATION

(JUL 2010) - ALTERNATE I (JUL 2010)

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

(c) Submit the cost proposal electronically as indicated below.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 9

3.2.2.3-38 REQUIREMENTS FOR CERTIFIED COST OR PRICING DATA OR OTHER

INFORMATION

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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 10 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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 11

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.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 12

L. 3 General Information Required to Prepare Offers

L.3.1 Contractors Providing E-IDS 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.

• CSRA

• Cobec Consulting

• Evans Incorporated

• Human Solutions Inc.

• The Mitre Corporation

• Noblis Inc.

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

L.3.3 Communications and SIR Questions

L.3.3.1 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. 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.faaco.faa.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.

All questions and requests for clarifications relating to this SIR must be received by the

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 13

Contracting Officer by the date listed in Section L. The Offeror is solely responsible for ensuring that the FAA Contracting Officer has received the questions or requests for clarifications.

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.

L.3.3.2 FAA Communications with Offerors

.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 communications may be used in the evaluation of proposals.

L.3.3.3 Conduct of the Operational Capability Demonstrations

Operational Capability Demonstrations will be scheduled no sooner than 6 weeks after the submission of Technical Volume Part A. Demonstrations will be conducted at an Offeror’s facility within 25 miles of the FAA headquarters building in Washington, DC.

The Government will contact the Offeror at least twenty-one (21) calendar days prior to an

Operational Capability Demonstration to schedule a specific date. The Government will attempt to arrange the demonstrations between Tuesday and Thursday, but reserves the right to schedule on Mondays and Fridays. Offerors should reserve one day for the demonstration. Offerors should plan to have the demonstrations from 9:00 AM until 5:00 PM to include a 60 minute lunch. The Government attendees will provide their own lunch and may wish to separately caucus over lunch.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 14

The conduct of the demonstration must be as follows:

• The activities will start promptly at 9:30am.

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

• Offerors will be allotted up to 120 minutes prior to lunch to start their demonstration.

• The Government may request a small break within this 120-minute period.

• Lunch – up to 60 minutes

• Offerors will be allotted up to 90 minutes after lunch to complete their demonstration.

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

Government.

Offerors must be prepared to respond during the demonstration to FAA questions regarding any aspects of their technical proposal.

Based on information presented by the Offerors, the Government may request additional information 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.

The Offerors presenters must be either key personnel or personnel identified in the proposal as holding a leadership position within the Offeror’s proposed organization as identified in the proposal.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 15

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

L.4.1 Volume Submissions and Projected Acquisition Milestones

The following acquisition milestones are provided for information purposes only and are subject to change.

ACTIVITY DATE

SIR Release [Date – TBD, current expectations are Winter 2018]

Deadline for Offerors’ SIR Questions and Discrepancy Notification per Section L.3.3.1

14 Days after SIR release

Volume I Part A – Technical Volume II – Cost/Price Volume III – Past Performance Volume IV – Reserved Volume V – Offer and Other Documents

60 days after SIR release

Volume I Part B.1 – Operational Capability Demonstration Presentation Slides

One week prior to scheduled Operational Capability Demonstration

Volume I Part B.2 – Operational Capability Demonstration

No sooner than 6 weeks after submission of Volume I Part A

Contract Award Late Fall 2019

L.4.2 Proposal Delivery Instructions

Offerors are fully responsible for ensuring that proposals are submitted in accordance with the schedule indicated by 11:00AM Eastern Standard Time to the following address:

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 16

David L. Reynolds, Contracting Officer Federal Aviation Administration 600 Independence Ave, SW Washington DC 20001

(202) 267-0795 David.L.Reynolds@faa.gov

Delivery after the appointed time will not be accepted.

L.4.3 Alternate Proposals

No alternate proposals will be accepted. The Government reserves the right to award a contract based on initial submittals received. Therefore, each Proposal should contain the Offeror’s best terms from a price and technical standpoint.

L.4.4 Format Instructions

Offerors must furnish the proposal in six (6) separate volumes:

Volume Number Volume Title

I.A Part A: Technical

I.B Part B.1: Operational Capability

Demonstration Presentation Slides

II Cost/Price

III Past Performance

IV Reserved

V Offer and Other Documents

Volumes must be submitted in the quantities specified below. Each volume must be contained in a separate 3-ring binder.

Electronic copies, including the Cost Model, must be compatible with Microsoft Office 2016 including the Cost Model. The electronic copies must be provided on DVDs or CDs with file names that are consistent with the structure of the proposal.

Each volume must also be marked to indicate whether it is an original or copy. Paper size must be 8-1/2 by 11-inch white paper with printing on one side only. The font (typewritten or printed letters) must be 12 point (with the exception of pre-printed product literature). Each page must have at least 1” margins on each side of the page. Fold-outs for complete spreadsheets and organizational charts are permissible up to 11" by 17", with printing on only one side, if secured with the volume; 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

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 17 excess of the number allowed will 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 Cover Page, Table of Contents, Glossary of Terms, and Index may be included but will not be evaluated and will not be included as part of the page count.

With the exception of the Cost Model, in the event of a conflict between the contents of the hard copy version of the proposal and the contents of the electronic version, the hardcopy version will take precedence. In the event of any conflicts between the Offeror’s prices described within its

Cost Model and the remainder of its Cost/ Price Volume, the Cost Model will take precedence.

The Offeror must provide a certification that the prices proposed and the total evaluated price contained in the hardcopy version of the proposal is exactly the same as the electronic version provided within the Cost 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 Cost Model with all imbedded functionality still enabled.

Offerors should assume that the FAA has no prior knowledge of their proposed solutions, capabilities, or experiences and that the FAA will base its evaluation solely on the information presented in their proposals.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 18

Table 1: Proposal Volumes

Volume Volume Title Page

Limit

Number of

Paper

Copies

Number of

Electronic

Copies

I.A Technical 150 3 2

I.B.1 Operational Capability Demonstration

Presentation Slides

75* 3 2

II Cost/Price None 3 2

III Past Performance 30 3 2

IV Reserved 10 3 2

V Offer and Other Documents None 3 2

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

L.4.5 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 Cost 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 may correct administrative errors, such as mathematical errors or inaccurate cross references. In this event, the FAA will notify the Offeror of the change and may afford the Offeror an opportunity to submit an updated proposal.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 19

L. 5 Volume I – Technical

The technical volume consists of the written technical proposal and material presented in support of and during the Operational Capability Demonstration.

L.5.1 Part A: Technical

The Technical Proposal must describe how the Offeror will perform the efforts required by the

Statement of Work. In addition, the Technical Proposal must describe the Offeror’s proposed solution to provide the services as specified in the E-IDS System Specification Document. The allocation of the page limit for Volume I between the individual parts is left to the discretion of the Offeror.

L.5.1.1 Factor A.1: Approach

The Offeror must describe:

a) Its technical approach to providing an E-IDS solution. This must include

i. Their characterization of the E-IDS requirements and how their technical approach facilitates derivation of lower level requirements

ii. How their technical approach ensures that the proposed solution is consistent with the E-IDS concept of operations

iii. How their technical approach addresses the operational needs of E-IDS users and maintainers

iv. How their proposed solution will readily integrate into the NAS including implementation and operations.

b) Its proposed E-IDS solution including:

i. The architecture and design of their E-IDS solution, including the software, hardware, and firmware selected and the associated rationale for each

ii. How their technical approach will successfully develop and deploy the E-IDS solution given their experience and capability demonstrated

c) The architecture and design of its Demonstration Capability.

i. The Offeror must include information flow, software, hardware, and firmware used as well as functions of the Demonstration Capability.

ii. The Offeror must identify how its demonstration capability adapts to the inclusion of additional interfaces and incorporates changes to existing interfaces.

iii. The Offeror must describe how these aspects are applicable to their E-IDS solution.

d) How its approach facilitates the objectives of the E-IDS program as identified in

Attachment J.2 of this SIR.

L.5.1.2 Factor A.2: Data Rights

The Offeror must describe its proposed Data Rights for the E-IDS solution, to include the rights and data:

a) Afforded to the Government

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 20

b) Afforded to the Prime Vendor

c) Afforded to Subcontractors

d) Afforded to Proprietary Software used by the System

L.5.1.3 Factor A.3: Systems Engineering

The Offeror must describe:

a) Its systems engineering approach used for their solution development. This includes:

i. The management approach including the organization of the efforts to execute systems engineering activities

ii. The work groups the Offeror proposes to establish and their purpose

iii. The processes and performance metrics to be used within their systems engineering effort

iv. The tools utilized with their systems engineering approach and the rationale for their choice

b) How its systems engineering approach supports and integrates with the FAA’s

i. Systems Engineering Processes

ii. Test Processes

iii. Solution Implementation Processes

iv. In-Service Management Processes

And how this approach will lead to successful and timely development, implementation and operation of the E-IDS system.

L.5.1.4 Factor A.4: System Development

The Offeror must describe:

a) Its proposed solution for E-IDS. This includes

i. Its proposed software development processes, and hardware development processes if required

ii. Its method of incorporating the E-IDS interfaces into their proposed solution

iii. The rationale for the selection of the above items and how they best meet the requirements of the E-IDS system

b) The initial allocation of system functionality to their proposed hardware, COTS software, and custom developed software

c) Its solution development approach including processes, tools, management products, and incorporation of the IESP

L.5.1.5 Factor A.5: Test and Evaluation

The Offeror must describe:

a) Its overall approach to the test program planned for verification of all requirements and in accordance with the SOW, the E-IDS System Specification Document, the Verification

Requirements Traceability Matrix (VRTM), and the Test and Evaluation Master Plan

(TEMP). This must include describing

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 21

i. How its test and evaluation approach assures all E-IDS functional and performance requirements of the FAA E-IDS System Specifications are met

ii. How its approach to supporting the FAA leads to successful completion of

Operational Test in a timely fashion

iii. How its approach for testing will support the successful fielding and acceptance of Operational Clusters and quickly identify and minimize site-based connection issues and cluster operation issues.

b) How its proposed test capabilities, e.g. simulators and tools, methods, processes, and staffing will

i. Be used for Development Test, including site acceptance testing for the operational cluster

ii. Be available for Operational Test

iii. Emulate the operational environment

c) How its test approach will assure in all phases of testing that their E-IDS solution will integrate

i. With the IESP environment

ii. With all the associated NAS systems, services, and interfaces

L.5.1.6 Factor A.6: Implementation

The Offeror must describe its approach to supporting the E-IDS implementation. This must include:

a) How its approach aligns with the FAA processes for implementation into staffed, NAS-operational facilities

b) How its approach will accommodate either acceleration or deceleration of the implementation schedule

c) How its approach minimizes repeat visits to sites

d) How its approach will accommodate parallel operations of their proposed solution and the systems it replaces

L.5.1.7 Factor A.7: Operations, Maintenance, and Logistics

The Offeror must describe:

a) The process of transferring the software of its developed system to new hardware platforms.

b) Its approach for planning, developing, deploying and managing software releases

c) How its proposed solution incorporates and manages multiple operational software baselines

d) How their proposed solution integrates with FAA enterprise and local monitoring

e) Their process for managing and tracking software and hardware components of their proposed solution

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 22

L.5.1.8 Factor A.8: Program Management

Offerors must describe:

a) Its program organization for E-IDS including the reporting hierarchy, names of managers and proposed key personnel, their titles, and their functional responsibilities. The Offeror must describe its work breakdown structure (WBS) and how it is compliant with the FAA

Standard Work Breakdown Structure (see attachment in section J). Offerors must describe the reporting chain of the program manager within the structure (e.g., to whom the program manager reports and the level of that official within the structure). Offerors must discuss the level of authority/empowerment of the program manager

b) The roles of the prime contractor and all team members in terms of how the full range of effort defined in the Statement of Work will be allocated and managed within the team.

Offerors must also describe the teammate’s experience in performing their designated role within the proposed team and any previous experience working together as a team.

c) Its approach for ensuring effective and efficient interaction with the FAA Program

Management Office (PMO), including location and staffing of the Offeror’s PMO and technical support staff. Offerors must describe the benefits of their proposed approach

d) Its Program Management Organization (PMO) for E-IDS and how it would fit into their corporate organizational structure. If an Offeror’s submission represents a team response, Offerors must provide this information for each major team member and describe the inter-company reporting relationships. Offerors must provide an issue resolution escalation process. Discuss their management approach toward cost, schedule and technical performance monitoring and control.

L.5.1.9 Factor A.9: Experience

Experience is separate from Past Performance. For this Factor Offerors must describe:

a) Its team’s experience with specific projects and programs within the last 6 years in:

i. Systems engineering of similar size, complexity, and mission essential systems

ii. Software and System development of similar size, complexity, and mission essential systems

iii. Test and Evaluation of similar size and complexity systems with active participation of the customer

iv. Implementation and transition of similar large-scale systems at multiple locations simultaneously with multiple users

v. Maintenance, operations, and logistics of similar large-scale systems with the customer assuming maintenance and operation of the system

vi. Training. This includes its capability and experience with developing training of similar size and complexity to the training described in the SOW

vii. Program Management

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 23

Offerors must include the projects listed in past performance and the Operational

Capability Demonstration.

b) Identify key technical and management personnel proposed for this effort, their proposed roles and responsibilities, and their positions within the Offerors reporting hierarchy. The required key personnel are:

i. Program Manager

ii. System Architect

iii. Chief Systems Engineer

iv. Test Manager

v. Implementation Lead

vi. Contracts Manager

vii. Training Manager

c) Offerors must also describe the extent to which team members and staff have worked together in previous prime / subcontractor relationships and other business relationships and why that is relevant to E-IDS.

L.5.2 Part B: Operational Capability Demonstration

The scheduling and general activities of the Operational Capability Demonstration are described in Section L.3.3.3 above. Offerors must demonstrate to the FAA identified aspects of an operational capability. Offerors are responsible for ensuring that the capability is functioning for the time and location scheduled, including that all equipment, connectivity, and related software are functioning at the demonstration.

L.5.2.1 Factor (B.1): User Customization

The Offeror must demonstrate the User Interface customization aspects of its capability.

Specifically:

a) The degree of standardization and customization provided by the capability

b) How its operational capability is customized by a data administrator for different operational positions and uses to meet the operational needs of the user

c) How this new customization is transitioned into operational use

L.5.2.2 Factor (B.2): System Management and Control

The Offeror must demonstrate the System Management and Control Functionality of its capability. Specifically:

a) How this functionality provides situational awareness to the maintainer(s) and user(s) of the capability and how this functionality displays the status of system components at the enterprise and local level

b) How this functionality provides diagnostics and restoration of the capability

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 24

L.5.2.3 Factor (B.3): Performance During Degraded Operations

The Offeror must demonstrate the operation of its capability:

a) During different degraded and failed modes of system components

b) Through the restoral process from degraded and failure states

L.5.2.4 Factor (B.4): Data Management

The Offeror must demonstrate how data is managed within its operational capability. This includes how:

a) Data is input, validated, correlated, retained, and tracked,

b) The capability incorporates data from legacy systems being replaced with this capability

c) The data management scales with added interfaces, users, and data streams

L.5.2.5 Factor (B.5): Interface Flexibility

The Offeror must demonstrate the System Interfaces and Protocols accommodated by its capability; specifically, the different interface types and protocols that are used by the capability.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 25

L. 6 Volume II – Cost/Price

Offerors must use the Government provided Cost Model (see Attachment J-9 [To be released later]). The Cost Model must be completed by the Offeror, will contain the Offeror’s submitted prices, and will identify the Offeror’s total evaluated cost of the proposal. The Cost Model

Description (see Attachment J-10 [To be released]) contains detailed instructions which Offerors must follow on the use of the Cost Model.

Offerors must include the following in their Cost / Price volume:

a) All information necessary to fully address the requirements of this SIR

b) Completed pricing schedules in electronic format within the Cost Model as defined in

Section B of the SIR and described in the Cost Model Documentation. Evaluated cost will be computed using the prices provided in the Cost Model price tables, multiplied by the quantities contained in the Cost Model

c) A complete error-free electronic copy of the Cost Model as run with their proposed prices and Offeror specified quantities for items requiring Offeror definition

d) The algorithms to use to calculate the associated fee for each incentive fee type CLIN proposed

e) Sufficient supporting information for any proposed Cost Reimbursable CLINs including:

i. A statement as to whether or not their accounting and other systems have been determined to be adequate for reimbursable contracts by the Defense Contract Audit Agency (DCAA)

ii. DCAA Point of Contact (Name of Auditor, DCAA Office, Address, Phone #, and email address

iii. For each organizational element being proposed as cost reimbursable on this SIR -copies of the most recent Forward Pricing Rate Agreement (FPRA) and the most recent copies of the following DCAA Approval Letters or Audit Reports:

Estimating System Review, Accounting System Review, Billing System Review, and Purchasing System Review

f) Sufficient supporting information for the proposed labor category level skill mix proposed including:

i. A description of the minimum education level, experience level, and required skills

ii. Any translation used between experience and education

iii. Relationships with FPRA labor categories and rates and rationale for differences

Offerors must provide a basis of estimate for each CLIN and sub-CLIN priced within its proposal in sufficient detail to allow the evaluators to determine the fairness, reasonableness, balance, and realism of the proposed cost/price. Each basis of estimate must provide a narrative describing the rationale for the labor categories, levels, and hours proposed as well as any material and other direct costs. This narrative must be contained within Volume II.

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 26

Offerors are instructed that the Teammates, labor category, labor category levels, labor hours by category, year, and level, and the labor category descriptions may be extracted from the Cost

Model and provided without prices to the Technical Evaluation Team for use in their evaluation.

The Offeror must provide existing verifiable data, the judgment factors, rationale, and methodology applied by it to project from known data to its estimate, and the contingencies used by the Offeror in its proposed price. Offerors’ Cost/Price Volume must be consistent with its

Technical Volume.

Performance Incentives

The FAA use of performance incentives is to motivate performance by the Contractor in meeting the requirements stated in Section C. Where requested in the Performance Requirements

Summary (PRS) (Attachment J.15 [To be released later]), Offerors must propose reasonable and attainable performance measures, acceptable performance levels (APLs), evaluation frequency, data source, surveillance method, and an associated award fee percentage or any credit percentages. When proposing award fee, Offerors should consider the requirements in Section H.

Offerors must propose these for:

• Systems Engineering

• System Development

• Test and Evaluation

• Implementation

• Program Management

Offerors must provide a rationale for each proposed APL describing how the proposed APL aligns with the objectives described in the Attachment J.2 and how it will result in the desired performance.

Offerors must propose performance measures and APLs for award fee at least through year three

(3) of the contract. In the Cost/Price Volume, Offerors must propose an award fee amount for the base period and all option periods.

Offerors must propose an incentive fee structure that will demonstrate reasonable risk allocation between the FAA and the Offeror and, also, provide the Offeror with incentives for efficient and economical contract performance. Offerors must describe how the proposed APLs will integrate with the contract structure.

For pricing purposes, Offerors are directed to make the following assumptions:

• For Installation and site survey CLINs, Offerors must price the median number of display positions for each category.

• For incentive fee CLINs, maximum fees are 13%

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 27

• For incentive fee CLINs, the share ratio for costs exceeding the target cost must be no less than 80% Government and no greater than 20% contractor

• For incentive fee CLINs, the share ratio for costs under the target cost must be no less than 80% Government and no greater than 20% contractor

08/03/2018 Section L – Instructions, Conditions, and Notices to Offerors

Draft 28

L. 7 Volume III – Past Performance

Offerors must provide a minimum of three (3) examples of…