DRAFT ETR Section L 10-5-18 CJM.pdf

10/12/2018 693KA8-18-R-00007

Page L-1

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

TABLE OF CONTENTS

L.1 FAA Acquisition Management System Clauses

L.1.1 3.1-1 Clauses and Provisions Incorporated by Reference (July 2011)

L.1.2 Clauses and Provisions Incorporated in Full Text

L.2 Questions, Concerns, and Clarifications

L.3 General Instructions

L.3.1 Schedule

L.3.2 Alternate Proposals, Deviations, and/or Exceptions

L.3.3 Date, Place and Time for Submission of Proposals and Equipment

L.3.4 Compliance

L.3.5 Expenses Related to Offeror Submissions

L.3.6 Communication with Offerors

L.3.7 Participation of Non-Government Personnel

L.3.8 Number of Awards

L.3.9 Use of Commercial-Off-the-Shelf (COTS)/Non-Developmental Items (NDI) ……………………………………………………………………………….12

L.4 Proposal Organization and Preparation Instructions

L.4.1 Proposal Organization

L.4.2 Proposal Format

L.5 VOLUME DESCRIPTIONS

L.5.1 Volume I - Technical Proposal

L.5.1.1 Part A - Capabilities and Attributes (Subfactor 1.1) L.5.1.2 Part B - Contractor Master Test Approach (Subfactorn1.2) L.5.1.3 Part C – Operational Capabilities Test (Subfactor 1.3) L.5.1.4 Part D – FAA-E-7868 Self Evaluation Form

L.5.2 Volume II - Management Proposal

L.5.2.1 Part A – Key Personnel (Subfactor 2.1) L.5.2.2 Part B.1 – Management Approaches (Subfactor 2.2) L.5.2.3 Part B.2 – Configuration Management (Subfactor 2.3) L.5.2.4 Part B.3 – Integrated Support Approach (Subfactor 2.4) L.5.2.5 Part C – Training (Subfactor 2.5) L.5.2.6 Part C – Technical Support Services (Subfactor 2.6)

L.5.3 Volume III – Past Performance

L.5.4 Volume IV - Price

Page L-2

L.5.4.1 Part A: Completed Section B - Price Model L.5.4.2 Part B: Price Narrative

L.5.5 Volume V - Quality System Plan

L.5.6 Volume VI – Miscellaneous Documentation

L.5.6.1 Part A: Standard Form (SF) 33, "Solicitation, Offer and Award” L.5.6.2 Part B: Section K -Representations, Certifications & Other Statements 22 L.5.6.3 Part C: Responsible Prospective Contractors L.5.6.4 Part D: Exceptions, Deviations, or Assumptions L.5.6.5 Part E: Executive Summary

L.6 SECTION L ATTACHMENTS

Page L-3

L.1 FAA Acquisition Management System Clauses L.1.1 3.1-1 Clauses and Provisions Incorporated by Reference (July 2011) This screening information request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make the full text available, or Offerors and Contractors may obtain the full text via Internet at:

http://conwrite.faa.gov.

3.2.2.3-1 False Statements in Offers (July 2004) 3.2.2.3-6 Submittals in the English Language (July 2004) 3.2.2.3-7 Submittals in U.S. Currency (July 2004) 3.2.2.3-9 Notice of Possible Standardization (July 2004) 3.2.2.3-7 Submittals in U.S. Currency (July 2004) 3.2.2.3-12 Amendments to Screening Information Requests (July 2004) 3.2.2.3-13 Submission of Information/Documentation/Offers (July 2004) 3.2.2.3-14 Late Submissions, Modifications, and Withdrawals of Submittals (July 2004) 3.2.2.3-15 Authorized Negotiators (July 2004) 3.2.2.3-16 Restriction on Disclosure and Use of Data (July 2004) 3.2.2.3-17 Preparing Offers (July 2004) 3.2.2.3-18 Prospective Offerors Requests for Explanations (March 2009) 3.2.2.3-19 Contract Award (July 2004) 3.6.2-7 Pre-award On-Site Equal Opportunity Compliance Review (July 2011)

L.1.2 Clauses and Provisions Incorporated in Full Text 3.2.2.3-4 Samples (July 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

Page L-4

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

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

(1) You provided the same product to us ___N/A_____ [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)

Page L-5

3.2.2.3-5 Descriptive Literature (July 2004)

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

(1) Design;

(2) Materials;

(3) Components;

(4) Performance characteristics; or

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

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

(c) The Offeror (you) must mark or highlight the items you are submitting as descriptive literature so we can readily find them in you 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 FAA under an earlier FAA contract that is the same as the product offered under this SIR.

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

Earlier contract number _____________________________________

Date of earlier contract ______________________________________

Contract line item number of product supplied ___________________

Name and address of government activity

Page L-6 to which you delivered the product _________________________________

Date of final delivery of product _______________________

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

(End of provision)

3.2.2.3-20 Offers (January 2018)

(a) The Offeror (you) must submit responses to this SIR by the following electronic means electronic mail. 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 Michael.R.Villano@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".

(End of provision)

3.2.4-1 TYPE OF CONTRACT (APRIL 1996)

The FAA contemplates award of an Indefinite Delivery/Indefinite Quantity contract resulting from this Screening Information Request. Delivery Orders will primarily be issued as Firm-Fixed Price (FFP) or Time and Materials (T&M); however, the Government reserves the right to use other contract types, as appropriate.

(End of provision) mailto:dave.keehan@faa.gov

Page L-7

3.6.1-17 NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM

(NAICS) CODE (JANUARY 2016)

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

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

For NAICS codes based on annual receipts, the annual average receipts for the last three fiscal years cannot exceed: N/A

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

(End of provision)

3.9.1-3 PROTEST (OCTOBER 2011)

AS A CONDITION OF SUBMITTING AN OFFER OR RESPONSE TO THIS SIR (OR

OTHER SOLICITATION, IF APPROPRIATE), THE OFFEROR OR POTENTIAL

OFFEROR AGREES TO BE BOUND BY THE FOLLOWING PROVISIONS

RELATING TO PROTESTS:

(a) Protests concerning Federal Aviation Administration Screening Information Requests

(SIRs) or awards of contracts shall be resolved through the Federal Aviation Administration (FAA) dispute resolution system at the Office of Dispute Resolution for Acquisition (ODRA) and shall be governed by the procedures set forth in 14 C.F.R. Parts 14 and 17, which are hereby incorporated by reference. Judicial review, where available, will be in accordance with 49 U.S.C. 46110 and shall apply only to final agency decisions. A protestor may seek review of a final FAA decision only after its administrative remedies have been exhausted.

(b) Offerors initially should attempt to resolve any issues concerning potential protests with the Contracting Officer. The Contracting Officer should make reasonable efforts to answer questions promptly and completely, and, where possible, to resolve concerns or controversies. The protest time limitations, however, will not be extended by attempts to resolve a potential protest with the Contracting Officer.

(c) The filing of a protest with the ODRA may be accomplished by mail, overnight delivery, hand delivery, or by facsimile or if permitted by order of the ODRA, by electronic filing. A protest is considered to be filed on the date it is received by the ODRA during normal business hours. The ODRA's normal business hours are from 8:30 am to 5:00 pm Eastern Time.

(d) Only an interested party may file a protest. An interested party is one whose direct economic interest has been or would be affected by the award or failure to award an

Page L-8

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 an SIR that are apparent prior to bid opening or the time set for receipt of initial proposals shall be filed prior to bid opening or the time set for the receipt of initial proposals.

(2) In procurements where proposals are requested, alleged improprieties that do not exist in the initial solicitation, but which are subsequently incorporated into the solicitation, must be protested not later than the next closing time for receipt of proposals following the incorporation.

(3) For protests other than those related to alleged solicitation improprieties, the protest must be filed on the later of the following two dates:

(i) Not later than seven (7) business days after the date the protester knew or should have known of the grounds for the protest; or

(ii) If the protester has requested a post-award debriefing from the FAA Product Team, not later than five (5) business days after the date on which the Product Team holds that debriefing.

(f) Protests shall be filed at:

(1) Office of Dispute Resolution for Acquisition Federal Aviation Administration 800 Independence Ave., S.W.

Room 323 Washington, DC 20591

Telephone: (202) 267-3290 Facsimile: (202) 267-3720; or

(2) Other address as specified in 14 CFR Part 17.

(g) At the same time as filing the protest with the ODRA, the protester shall serve a copy of the protest on the Contracting Officer and any other official designated in the SIR for receipt of protests by means reasonably calculated to be received by the Contracting Officer on the same day as it is to be received by the ODRA. The protest shall include a signed statement from the protester, certifying to the ODRA the

Page L-9 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)

L.2 Questions, Concerns, and Clarifications The CO is the sole point of contact for this acquisition. Offerors are instructed to direct general questions, concerns, and clarifications to the CO listed in Section G.4 of this SIR.

All Offeror questions, concerns, and clarification requests specific to the SIR must be made in writing using the question/clarification template provided with the SIR announcement and submitted to the CO via email not later than the date specified in Section L.3.1, Table L-1, Offeror questions concerns, and clarifications due. See Attachment L06. Written inquiries received within this timeframe will be answered in writing and provided to all Offerors prior to the required date for submittal of the Offeror proposals. The Government reserves the right to not answer any requests received outside of the above timeframe. Furthermore, Offerors should note that the proposal due date will not be extended solely on the basis of questions received within or beyond the timeframe mentioned above. The Government will not provide verbal responses to Offeror questions, concerns, and clarification requests initiated via Offeror telephone calls.

Copies of FAA specifications, standards, and publications applicable to this solicitation may be obtained from the Contracting Officer. Requests must be submitted by email to Michael.R.Villano@faa.gov and must clearly identify the desired material by title and number and state the intended use of the material. All requests for FAA documents must be received by the Government no later than ten (10) business days after the release date of this solicitation.

L.3 General Instructions L.3.1 Schedule Table L-1 represents the procurement schedule.

Table L-1 Procurement Schedule

Date Emergency Transceiver Replacement (ETR) SIR released TBD Offeror questions, concerns, and clarifications due TBD Offeror written proposal and OCT Equipment due TBD mailto:%20Michael.R.Villano@faa.gov mailto:%20Michael.R.Villano@faa.gov

Page L-10

L.3.2 Alternate Proposals, Deviations, and/or Exceptions Alternate proposals are not authorized to be submitted in response to this SIR and will not be evaluated. Therefore, with respect to specific terms or conditions of this SIR, any objection to any of the terms and conditions of this SIR may constitute a deficiency, which could make the offer unacceptable.

The FAA reserves the right to award a contract without communications after evaluation of initial written submissions. The FAA also reserves the right to conduct Offeror specific communications/discussions and permit Offerors to revise their proposals, if the CO deems these measures are appropriate and in the best interest of the FAA. The FAA reserves the right to reject any exception for any reason.

Any deviations and/or exceptions to any requirements listed in this SIR must be identified by the Offeror at the time of proposal submission and submitted in proposal Volume VI, Miscellaneous Documentation, Part D: Exceptions, Deviations or Assumptions.

L.3.3 Date, Place and Time for Submission of Proposals and Equipment Offerors assume full responsibility for ensuring that all proposal and equipment submissions are received by 2:00 PM Eastern Time (ET) on the date specified in the Section L.3.1, Table L-1, Offeror written proposal due and OCT Equipment due.

All Offeror proposal submissions to this SIR must be made by electronic mail to Michael.R.Villano@faa.gov. The subject field of the electronic mail message must be in the format, “Offeror name - 693KA8-18-R-00007 - Proposal Submission” where “Offeror name” is the name of the Offeror. The FAA will not accept any submission made by facsimile, telex, telegraph, postal delivery services, or any other means. If the identified Contracting Officer does not receive a proposal by the specified date and time, it may not be accepted.

L.3.4 Compliance

All proposals will be screened initially for completeness, accuracy, and timeliness. A proposal that does not meet the initial screening criteria may be excluded from the competition. The Government will notify the Offerors if they are removed from further competition.

It is the Offeror’s responsibility to ensure the completeness of the proposal. The evaluation of proposals will be conducted on the basis of the information contained in the written proposal. The Government will not assume that an Offeror possesses any capabilities not specified in the proposal.

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

mailto:%20Michael.R.Villano@faa.gov.

mailto:%20Michael.R.Villano@faa.gov.

Page L-11

L.3.5 Expenses Related to Offeror Submissions The Government will not pay or reimburse any costs incurred by the Offeror in the development, submission, or any other part of their offer. This includes costs associated with any aspect of the OCT activities.

L.3.6 Communication with Offerors The FAA may, at any time, communicate with Offerors on an individual basis to clarify particular aspects of their proposal, to negotiate the terms and conditions of the proposed contract, or to seek clarification or additional information regarding Offerors’ submissions. Communication with potential Offerors may take place throughout the source selection process. The purpose of communications is to ensure mutual understandings between the FAA and the Offerors on all aspects of the procurement, including the Offerors’ proposals. Communications with one Offeror does not necessitate communications with other Offerors. Information disclosed as a result of oral or written communication with an Offeror may be considered in the evaluation of an Offeror’s proposal. The FAA also reserves the right to allow Offerors to revise their proposals.

All communications will be conducted through the FAA Contracting Officer. Each Offeror must provide in its submission cover letter: a point of contact, telephone number, and email address for purposes of initiating all communications.

L.3.7 Participation of Non-Government Personnel Offerors are notified that the Government may have responses to the SIR, to include any written technical proposals or other written information provided in response to this solicitation, reviewed by non-Government personnel (i.e., Contractor personnel) supporting the source evaluation. Companies participating in the source selection include the following:

KM Systems Group 2011 Crystal Drive Arlington, Virginia 22202

ITstrategy 6337 29th Street North Arlington, Virginia 22201

Solentus 241 18th Street, Suite 405 Arlington, Virginia 22202

THANE

Capital Gallery 600 Maryland Avenue, Washington, DC 20024

Veracity Engineering L'Enfant Plaza 955 L'Enfant Plaza SW Ste 700 Washington, DC 20024

The exclusive responsibility for source selection will remain with the Government. All non-Government personnel will be required to sign non-disclosure of information agreements before they are provided access to any responses to this SIR.

If an Offeror objects to the disclosure of information to these non-Government entities, it must notify the CO in writing no later than 5 calendar days after SIR release and must include a detailed statement of the basis of the objection.

Page L-12

L.3.8 Number of Awards The FAA anticipates making one award resulting from this SIR. The FAA reserves the right to not make an award.

L.3.9 Use of Commercial-Off-the-Shelf (COTS)/Non-Developmental Items (NDI) Offerors are encouraged to propose the use of COTS and/or NDI to the maximum extent possible. The FAA intends to use COTS and/or NDI to reduce cost and schedule risks.

L.4 Proposal Organization and Preparation Instructions L.4.1 Proposal Organization Offeror proposal submissions will consist of written volumes and Operational Capability Test (OCT) Equipment as described in Section L.5. All Offerors are required to submit all volumes, OCT Equipment and participate in the OCT as described in SIR Attachment M01, OCT Plan.

Offerors must submit their proposal in accordance with the organization and submission requirements presented in Table L-2 below.

Page L-13

Table L-2 Proposal Organization and Submission Requirements Volume Number Volume Title Page Limit Submission Instructions

I

Technical Proposal Part A: Capabilities and Attributes 50

Electronic mail to CO

File Format: PDF Part D must be submitted in MS Excel

Part B: Contractor Master Test Approach 150

Part C: White papers, data analysis reports, and all supporting documentation for requirements listed in Attachment L04

None

Part D: FAA-E-7868 Self-Evaluation Form using Attachment L05 11

OCT delivered ETR equipment, hand-carried equipment, cables, and connectors IAW OCT Plan, Attachment M01

None Delivered or hand-carried to WJHTC

II

Management Proposal Part A: Key Personnel Resumes – (Using template in

Attachment L01)

3 pages per resume

(12 pages total)

Electronic mail to CO File Format: PDF

Part B: Management Approaches Part B.1 Program Management Approach Part B.2 Configuration Management Approach

Part B.3 Integrated Support Approach

100 for Part B, Approaches

Electronic mail to CO File Format: PDF

Part C: Written Response to Subfactors 2.5 Training, and 2.6, Technical Support Services

50 Total Electronic mail to CO File Format: PDF

III Past Performance Part A: Past Performance Summaries (using

Part I template in Attachment L02) Part B: Past Performance Customer Surveys

(using Part II template in Attachment L02)

Part A: 2 pages per contract reference

(4 pages total)

Part B: None

Part A: Electronic mail to CO File Format: PDF

Part B: Electronic mail to CO by customer completing survey File Format: PDF

IV Price Proposal Part A: Completed Section B - Price Model Part B: Price Narrative

None

Part A: File Format: MS Excel

Part B: File Format: PDF

V Quality System Plan 100* Electronic mail to CO File Format: PDF

VI Miscellaneous Documentation Part A: Standard Form 33 Part B: Section K Representations, Certifications and Other Statements of Offerors Part C: Responsible Prospective Contractors Part D: Exceptions, Deviations or Assumptions Part E: Executive Summary

Parts A, B, C, and D: None

Part E: 10 pages

File Format: PDF for signed documents

* Quality manual, ISO compliance documentation, and sample COTS materials do not count toward page count

Page L-14

L.4.2 Proposal Format Offerors are permitted to submit only one (1) proposal. Offerors must submit proposals according to the following:

a) Proposals must be provided in standard letter size 8-1/2 by 11-inch format. 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.

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-2. 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, ISO 9001:2008 Quality Documents, COTS documentation, Contractor submittal letter and subcontractor commitment letters, if applicable, and transmittal letters. Any submission exceeding a page limitation may only be evaluated up to the established page limitation.

c) 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 not be considered adequate. Similarly, submittals that contain omissions or incomplete responses to the requirements of this SIR, that merely paraphrase the Statement of Work or that use nonspecific phrases such as "in accordance with standard procedures" or "well-known techniques" will also be considered inadequate. Deficiencies of this kind will render the proposal non-responsive and may be cause for rejection of the offer.

d) 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 (July 2004).

e) Proposal volumes cannot be contained in the same file and must be complete in and of itself so that evaluation of one may be accomplished independently of the other. The individual e-mail responses including attachments must be less than 10 MB. As such, vendors are permitted to submit their responses via multiple e-mails if necessary due to the size constraints. Offerors must not password protect or compress (e.g. zip) any submitted files. The file name must adhere to the following naming convention using the Volume/Part names listed in Table L-2:

“Offeror Name - ETR VOL # - Volume/Part Name”

Examples:

ABC Company - ETR VOL I – Technical Proposal

Page L-15

ABC Company – ETR VOL IV – Price Proposal – Part A Price Model

f) A cover page must be affixed to each volume that clearly identifies each volume title, volume number, solicitation number, and Offeror’s name. Whenever practical, enclosed headings, subheadings, titles, sequences of material and a number identification system must be used. Information not in its appropriate section or not appropriately referenced may be assumed to have been omitted and potentially not evaluated.

g) All proposal volumes must contain a table of contents, and glossary with the definitions of all acronyms and abbreviations used within the volume. These items do not count against the page limits (if applicable).

h) Cost or pricing information must not be included in any volume other than Volume IV (Price Proposal).

i) The FAA will only use Adobe Acrobat Pro 2015 Release, or Microsoft Excel 2016 software to read and evaluate Offeror proposals. The FAA has no special software or monitors to review diagrams, drawings, or illustrations such as those created using Computer Aided Design and Manufacturing (CAD/CAM). Submitted proposals that are not compatible with the Adobe Acrobat Pro 2015 Release, Microsoft Excel 2016, will not be evaluated.

L.5 VOLUME DESCRIPTIONS

A description of the required contents of the numbered volumes is provided in the subsections below. All information must be provided in these volumes as specifically prescribed.

L.5.1 Volume I - Technical Proposal Factor 1 – Technical

The Offeror must provide the following information for the subfactors as described below.

L.5.1.1 Part A - Capabilities and Attributes (Subfactor 1.1) The Offeror must provide a description of the capabilities and attributes of the ETR solution to meet the requirements of the Product Description FAA-E-7868 Section 3, Requirements. Where the Offeror’s equipment exceeds these requirements, the Offeror may list them and explain the added value to the Government, if any.

As part of the Capabilities and Attributes description, the Offeror must provide a general pictorial representation of the LRU(s) and their relationships as installed in the ET configuration, and describe how the LRU architecture provides resiliency, flexibility, and scalability. The offer must describe its proposed Maintenance Data Terminal solution

Page L-16 and how it will allow the Government to effectively and efficiently maintain the radio equipment, e.g. change parameter settings, observe readouts, set/recall settings, etc.

L.5.1.2 Part B - Contractor Master Test Approach (Subfactor1.2) The Offeror must submit a Contractor Master Test Approach (CMTA) that describes its overall approach and strategy to meet the requirements in SOW Section C.3.8 Testing. The CMTA may be submitted in the Offeror’s preferred format; however, the CMTA must include the following:

• the Offeror’s understanding of all ET test activities including sequence, durations, and interdependencies,

• a description of facilities, certification of test equipment, reporting, and Offeror’s proposed process for correction of deficiencies.

• the Offeror’s management of the test program, including staffing and an organizational chart with positions/persons responsible.

L.5.1.3 Part C – Operational Capabilities Test (Subfactor 1.3) The purpose of the Operational Capabilities Test (OCT) is to verify compliance to the FAA-E-7868. The OCT Plan is contained in this solicitation as Attachment M01. The OCT Verification Requirements Traceability Matrix (VRTM) is provided in Attachment M02. OCT Test Case Descriptions are attached to the OCT Plan as Attachment B.

The Offeror must perform “Demonstration (D)” identified in the OCT Plan and VRTM at the William J. Hughes Technical Center (WJHTC). After the demonstrations are complete, the Government will “Test (T)” and Inspect (I) the equipment without the Offeror being present in accordance with the OCT Plan.

For requirements identified as “Analysis (A)” in the VRTM and provided in SIR Attachment L04, the Offeror must provide supporting technical data in accordance with the OCT Plan. If material from existing documents are to be used as supporting technical data, remove the company name prior to submission. VRTM responses and supporting documentation for requirements marked as “Analysis (A) must accompany the Volume I, Part C submission.

Further information regarding submission of equipment and Offeror OCT participation is explained below.

Submission of Equipment:

All Offerors must submit their proposed equipment in accordance with the OCT Plan to the address below:

FAA William J. Hughes Technical Center Atlantic City International Airport, Building 70 Atlantic City, NJ 08405

Page L-17

Attn: Philip Randazzo, ANG-E62

Telephone: (609) 485-6630

The Offeror must submit equipment in accordance with Section 5.1.3.1 of the OCT Plan (M01), which lists the equipment submission requirements and submittal method, e.g.

delivered vs. hand carried.

OCT Participation:

Offeror roles and responsibilities for OCT participation are identified in Attachment M01, OCT Plan, Section 5.1.3. The Government will only test one Offeror at a time. The OCT evaluation conducted at the William J. Hughes Technical Center (WJHTC) in Atlantic City, NJ, is envisioned to last 20 business days for each Offeror. The Offeror's relative position in the OCT sequence will be determined randomly, however all Offerors’ OCT equipment are due at the WJHTC as listed in Section L.3.1, Table L-1.

Offerors must anticipate that their OCT participation may begin as soon as five days after proposals are due since the sequence of the OCTs will be determined randomly.

The Offeror must support OCT as identified in the OCT Plan Attachment M01.

Instructions for access to the WJHTC are provided in SIR Attachment L03. The Government will not reimburse Offerors for any expenses incurred in connection with the

OCT.

L.5.1.4 Part D – FAA-E-7868 Self Evaluation Form Each Offeror must perform a self-evaluation of their equipment against each requirement in Product Description, FAA-E-7868. The results of this assessment (meets/does not meet) must be recorded on the FAA-E-7868, Self-Evaluation Form provided in L05 and submitted as Part D of the Technical Proposal. If cases arise where the FAA OCT evaluation determines that the equipment does not meet a requirement, but the self-evaluation shows the requirement is met, the FAA can request clarification to resolve the discrepancy.

If cases arise where the Offeror states that they do not meet a “shall”, the Offeror must submit a Remediation Plan that indicates how the Offeror intends to meet that “shall”.

There will be no additional cost to the price of the equipment to implement the remediation in Section M.

L.5.2 Volume II - Management Proposal Factor 2 – Management

The Offeror must provide the following information for the subfactors as described in the subsections below.

L.5.2.1 Part A – Key Personnel (Subfactor 2.1) Using the template provided in SIR Attachment L01, Offerors must provide a resume for

Page L-18 all proposed Key Personnel as described in Section H.7 - Key Personnel and Facilities.

Key Personnel positions include: ETR Program Manager, ETR Chief Engineer/Architect, ETR Logistics Manager, and ETR Training Lead.

L.5.2.2 Part B.1 – Management Approaches (Subfactor 2.2) The Offeror must submit a Program Management Approach (PMA) as Part B.1 of the Management Proposal. The PMA may be submitted in the Offerors format; however, the PMA must demonstrate understanding of all ETR Program Management requirements and include the following:

1. Overall Approach. The Offeror must address its overall approach, methodology and understanding of the management requirements of this effort.

2. Production Capability. The Offeror must demonstrate the capability to meet the estimated ordering requirements of Section B including the capability to provide parts for the full 5-year life of the contract, plus three option years.

The Offeror must demonstrate the capability to meet or exceed the required delivery schedule and demonstrate the corporate commitment to achieving the proposed delivery schedule goals. The number, locations, and production capacities of the Offeror's facilities must be described along with an indication of current and anticipated production rates based upon other contractual obligations.

3. Integrated Master Schedule Approach (IMSA). The Offeror must depict the flow of work and the task interdependencies necessary to accomplish the program objectives from contract award to In Service Decision (ISD) and identify any critical paths. The IMSA, at a minimum, must include all production, test, configuration management activities, quality control activities, integrated logistics support activities, and other major and critical milestones.

The IMSA must include all activities and activity inter-dependencies of the Contractor, subcontractors, and dependencies on the FAA for all parts of the SOW. The IMSA must be risk adjusted and supported by risk analysis with appropriate mitigating factors identified.

4. Subcontractor Controls. If a subcontractor is to be used, the Offeror must:

identify the subcontractor; identify lines of authority and linkage of the subcontractor to the Offeror; provide written acknowledgement of the relationship; provide information as to the subcontractor’s capacity to do the work; identify the percentage of the requirement to be performed by the subcontractor; identify by paragraph title, the SOW or Product Description requirements to be subcontracted; and demonstrate the Offeror's capability to manage and integrate the proposed subcontractor's effort into the overall

PMA.

Page L-19

The Offeror must limit its PMA to the criteria listed above. PMA appendices or subordinate documents such as the Integrated Support Approach, Configuration Management Approach, and Quality Systems Plan, and the Contractor Work Breakdown Structure must not be included in the Offeror’s PMA submission for subfactor 2.2.

L.5.2.3 Part B.2 – Configuration Management Approach (Subfactor 2.3) The Offeror must submit a Configuration Management Approach (CMA) as Part B.2 of the Management Proposal. The CMA may be submitted in the Offeror’s format; however, the CMA must demonstrate the Offeror’s understanding of all configuration management requirements. The Offeror must describe its procedures for documenting and disseminating information on revisions to the hardware (down to the board level) and the software, as well as its procedures for updating the commercial manual/technical instruction book and the long-term supportability data package.

L.5.2.4 Part B.3 – Integrated Support Approach (Subfactor 2.4) The Offeror must submit an Integrated Support Approach (ISA) as Part B.3 of the Management Proposal. The ISA may be submitted in the Offeror’s format; however, the ISA must describe the Offeror’s understanding of and approach to managing all logistics management requirements (except Training, addressed elsewhere). The Offeror must provide a response to the requirements contained in the SOW Section C.3.6, all subparagraphs through C.3.6.9. The Offeror must provide a response to all requirements contained in the SOW Section C.3.6 and subparagraphs through C.3.6.9.

The ISA must also describe how when fielded, the ET will be supportable for the system’s life cycle, and how its warranty and non-warranty repair service will ensure quality and timely repair of all components.

L.5.2.5 Part C – Training (Subfactor 2.5) The Offeror must describe its understanding and approach to meeting the training requirements in section C.3.6.10. The Offeror must provide sample copies of its COTS training materials or describe its COTS training materials. The Offeror must describe how its experience, and lessons-learned developing past training programs will facilitate the development of a FAA-approved training course materials.

L.5.2.6 Part C – Technical Support Services (Subfactor 2.6) The Offeror must describe its team structure and the Offeror’s process to respond to and execute Government-issued task orders. The Offeror must demonstrate that the required expertise and knowledge is readily available to address requirements for logistics, training, testing, and engineering task orders. The Offeror must describe its approach and methodology to promptly respond to ad-hoc task orders resulting from Operational Testing, Field Familiarization test activities, or any other activity or event that may require additional, unanticipated Contractor technical support services.

Page L-20

The Offeror must describe its proposed Telephonic Support and how it will assist the Government resolve equipment engineering, maintenance, operation, and training problems for the life of the contract and warranty period. Offeror’s description should include their proposed hours of operation, account/caller verification process, number of steps to talk to a knowledgeable service representative, average hold times, problem tracking visibility and communications, and any other protocols, features, or performance metrics that demonstrate the responsiveness and effectiveness of its telephonic support.

L.5.3 Volume III – Past Performance

Using Attachment L02, Past Performance, the Offeror must cite, and describe two (2) contracts (Government or non-Government) that are on-going or were completed within the past five (5) years of similar size, scope and complexity to the ETR SOW.

The Offeror must complete Part I, of Attachment L-02 which must not exceed two (2) pages in length. For each contract referenced, the following must be provided:

• Block 3: A description that includes the system or product that was provided;

program and contract management requirements; configuration management requirements; testing support; training provided; and a description of the logistics support provided. Offerors must also describe the outcome of their efforts (e.g., whether the delivery was on time and, if not, why).

• Block 4: Offerors are responsible for ensuring that their write up includes a full description of the relevance to ETR requirements.

The Offeror must provide the related Attachment L02, Part II, Past Performance Customer Survey, to two customer points of contact (program/technical and contracts) for each reference cited in Part I. The customer POC’s must complete the Past Performance Customer Survey and return it to the FAA Contracting Officer. The Offeror is responsible for ensuring that its past-performance surveys are submitted timely; the Government reserves the right to contact the Offeror’s past-performance references and to consider references that are received after proposals are due.

L.5.4 Volume IV - Price Factor 3 – Price

The Offeror must not include pricing in any other proposal volume except Volume

IV.

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 or pricing data.

Page L-21

Not Separately Priced Items. If the Offeror elects to designate a CLIN in Section B as Not Separately Priced (NSP) because it is included within the configuration or engineering design of another priced item, the Offeror must indicate so in the Price Model by entering a zero dollar amount ($0). For all NSP CLINs (both those designated by the Offeror and NSP CLINs designated by the Government), the Offeror must describe in their Price Narrative, where the NSP CLINs are priced.

L.5.4.1 Part A: Completed Section B - Price Model The Offeror must complete all Section B - Price Model pricing for the base period and all option periods. Prices submitted in the Price Model are binding on the Offeror, unless otherwise negotiated, and will be incorporated into Section B of the contract.

Each Offeror’s completed Price Model must be submitted in Microsoft Excel 2016. The submitted Price Model must not be read-only, must not contain any locked cells other than those already locked by the Government, and must not be password-protected, in whole or in part. All formulas must remain as formulas, not set to values. The FAA reserves the right to reject proposals that do not comply with these requirements.

Offerors must propose firm-fixed unit prices for FFP items and labor rates for personnel listed in the technical support service CLINS for each item listed in the Price Model.

For the Operational Test (OT) Emergency Transceiver Kit Equipment (CLIN 0001), the FAA anticipates all labor costs associated with the OT process will be included in the firm fixed price for CLIN 0001. For Production Equipment (CLINs 1001-8001), the FAA anticipates the ongoing program management, configuration management, logistics, and test labor associated with production will be included in the firm fixed price of the equipment.

Offerors must propose a single fully burdened ceiling labor rate for each labor category inclusive of all contract periods, for all labor categories utilizing the qualification descriptions in Attachment J03, Labor Categories. The fully burdened rates must include direct labor and all indirect costs applicable to that direct labor (such as fringe benefits, overhead, G&A, etc.), and profit. The fully burdened rate will be applicable whether the work is performed by the prime contractor or a subcontractor.

L.5.4.2 Part B: Price Narrative The Offeror must provide a narrative describing the rationale, methodology and calculation used to determine the proposed pricing. The narrative must include any information the Offeror believes to be essential for the Government’s understanding of their proposed pricing. The narrative must individually address each CLIN in Section B and the following areas:

1. Rationale used for proposed escalation.

Page L-22

2. Identify all proposed indirect rates, to include allocation bases, describe how rates are applied. In addition, Offerors must identify and provide any indirect cost rate that would be applied to ODCs, materials, and travel costs.

L.5.5 Volume V - Quality System Plan

The Offeror must submit a Quality System Plan that describes the Offeror’s specific implementation of a quality management system needed to comply with the requirements set forth in Clause 3.10.4-13 Higher-Level Contract Quality Requirement (October 2015). The Offeror must submit evidence of achieved formal third-party registration to ANSI/ISO/ASQ Q9001-2008, if available.

L.5.6 Volume VI – Miscellaneous Documentation

The Offeror must provide the documentation below in the parts identified below.

L.5.6.1 Part A: Standard Form (SF) 33, "Solicitation, Offer and Award” 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 block 15a, the Offeror must provide the Contractor Establishment Code (CEC) applicable to the Offeror.

The number should be preceded by "CEC". The period for acceptance must be at least 300 calendar days.

L.5.6.2 Part B: Section K -Representations, Certifications & Other Statements of Offerors

The Offeror must complete all Representations, Certifications, and Other Statements included in Section K.

Page L-23

L.5.6.3 Part C: Responsible Prospective Contractors

The Offeror must be found responsible prior to award of this contract. As a minimum, to be determined responsible, a prospective Offeror must:

a) Have adequate financial resources to perform the contract and the ability to obtain resources;

b) Be able to comply with the required or proposed delivery or performance schedule, taking into consideration all other business commitments;

c) Have a satisfactory record of integrity and business ethics;

d) Have a satisfactory performance record; and

e) Have the necessary organization, experience, accounting, and operational controls.

The Offeror must provide the following:

a) Sufficient information to demonstrate the financial capability to fund and perform a contract of this size and duration. This includes:

• A Dun and Bradstreet Comprehensive Insight report, not more than six (6) months old;

• Proof of any existing Line(s) of Credit by a U.S. Banking Institution; and

• Certified Financial Statements that demonstrate the firm’s annual revenue for the last three (3) completed company fiscal years.

b) A description of all legal action(s) under Federal Government contracts in excess of $5M within the past three (3) years for, claims, equitable adjustments, pending or ongoing cure notices, Terminations for Convenience, and/or Terminations for Default.

c) Identify any member on your team that appears in the System for Award Management (SAM) with an exclusion record. Exclusion records identify those parties excluded from receiving federal contracts, certain subcontracts, and from certain types of federal financial and non-financial assistance and benefits. These are also commonly known as “suspensions” and “debarments”. Describe the circumstances surrounding the company/individual with the exclusion record.

L.5.6.4 Part D: Exceptions, Deviations, or Assumptions The Offeror must state any exceptions, deviations, or assumptions taken with any of the requirements of the SIR. Any exceptions, deviations, and assumptions taken must contain sufficient justification to permit evaluation. All exceptions, deviations, and assumptions, as well as benefits to the FAA, must be fully explained for each exception, deviation, and assumption taken. Exceptions and deviations will not themselves automatically cause a proposal to be deemed unacceptable. A large number of exceptions and/or deviations, or one or more significant exceptions and/or deviations not providing benefit to the FAA may, result in rejection of your proposal as unacceptable or otherwise non-compliant.

Offerors who do not have any exceptions, deviations, or assumptions taken with the SIR requirements should state so in Volume VI, Part D.

Page L-24

L.5.6.5 Part E: Executive Summary

The Offeror must submit an Executive Summary that summarizes the offer, highlights the salient features of the proposal, and includes a description of the approach and plans toward satisfying the…