L_TFM2_Amend-1_2016-09-09.pdf

TFM-2 SIR DTFAWA-16-R-00010 Ammendent 1 Section L

PART IV -- SECTION L

INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

TABLE OF CONTENTS

L.1 FAA AMS CLAUSES

L.2 GENERAL INSTRUCTIONS

L.2.1 COMPLIANCE WITH INSTRUCTIONS

L.2.2 EXPENSES RELATED TO OFFERORS SUBMISSIONS

L.2.3 ALTERNATIVE PROPOSALS

L.2.4 SIR QUESTIONS OR CLARIFICATIONS

L.2.5 PROPOSAL MODIFICATIONS

L.2.6 NOTIFICATION OF INTENT TO WITHDRAW PROPOSAL

L.2.7 DISPOSITION OF PROPOSALS

L.2.8 NON-FAA PERSONNEL PARTICIPATION

L.2.9 ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

L.2.10 COMMUNICATIONS

L.3 PROPOSAL SUBMISSION AND DELIVERY INSTRUCTIONS

L.4 PROPOSAL GENERAL CONTENT, ORGANIZATION, AND FORMAT INSTRUCTIONS

L.4.1 PROPOSAL CONTENT

L.4.2 PROPOSAL ORGANIZATION

L.4.3 PROPOSAL FORMAT

L.4.3.1 SIGNED ORIGINAL

L.4.3.2 BINDING AND LABELING

L.4.3.3 INDEXING

L.4.3.4 FORMAT OF HARD COPIES

L.4.3.5 FORMAT OF ELECTRONIC COPIES

L.5 INSTRUCTIONS FOR VOLUME I – TECHNICAL & MANAGEMENT PROPOSAL

L.5.1 GENERAL

L.5.2 PART A – TABLE OF CONTENTS

L.5.3 PART B – MASTER ABBREVIATION AND ACRONYM LIST

L.5.4 PART C – EXECUTIVE SUMMARY

L.5.5 PART D – TECHNICAL AND MANAGEMENT EXCEPTIONS, DEVIATIONS AND ASSUMPTIONS

L.5.6 PART E – TECHNICAL AND MANAGEMENT FACTORS

L.5.6.1 FACTOR 1 -- OPERATIONS AND MAINTENANCE

L.5.6.2 FACTOR 2 -- SECURITY

L.5.6.3 FACTOR 3 -- ENGINEERING, DEVELOPMENT, TEST AND IMPLEMENTATION

L.5.6.4 FACTOR 4 -- PROGRAM MANAGEMENT

L.6 VOLUME II –PAST PERFORMANCE

L.6.1 PART A -- EXPERIENCE NARRATIVES

L.6.2 PART B -- PAST PERFORMANCE REFERENCES

L.6.3 PART C -- PAST PERFORMANCE SURVEY RECORD

L.7 VOLUME III – COST / PRICE PROPOSAL

L.7.1 GENERAL

L.7.2 GOVERNMENT PRICING GUIDANCE AND CONSTRAINTS

L.7.3 COST/PRICE PROPOSAL ORGANIZATION

L.7.3.1 PART A -- COST/PRICE WORKBOOK (MS EXCEL FILE) AND SUPPORTING DETAIL DATA

L.7.3.2 PART B – DETAILED NARRATIVE, AND SUPPORTING COST/PRICE DOCUMENTATION

L.7.3.3 PART C -- COSTS/PRICE EXCEPTIONS, DEVIATIONS AND ASSUMPTIONS

L.7.3.4 PART D -- BASIS OF ESTIMATE (BOE)

L.8 VOLUME IV – CONTRACT TRANSITION PLAN

L.9 VOLUME V -- OFFER AND OTHER DOCUMENTS

L.9.1 PART A -- MASTER TABLE OF CONTENTS

L.9.2 PART B -- SOLICITATION, OFFER & AWARD FORM, SF-33

L.9.3 PART C – COMPLETED SIR SECTION K

L.9.4 PART D – BUSINESS AND FINANCIAL CAPACITY

L.9.5 PART E – ORGANIZATIONAL CONFLICT OF INTEREST (OCI) ISSUES

L.9.6 PART F – EARNED VALUE MANAGEMENT SYSTEM (EVMS)

L.9.7 PART G – MASTER LIST OF EXCEPTIONS, DEVIATIONS AND ASSUMPTIONS

L.9.8 PART H -- SMALL BUSINESS SUBCONTRACTING AND MENTOR PROTÉGÉ PROGRAM

ATTACHMENTS

L.1 FAA AMS CLAUSES

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.

(End of clause)

Clause Number and Title

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-11 Unnecessarily Elaborate Submittals (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-16 Restricting, Disclosing and Using Data (July 2004) 3.2.2.3-17 Preparing Offers (July 2004) 3.2.2.3-18 Prospective Offeror’s Requests for Explanations (March 2009) 3.2.2.3-19 Contract Award (July 2004) 3.2.2.3-31 Facilities Capital Cost of Money (July 2004) 3.2.2.3-72 Announcing Competing Offerors (July 2004) 3.2.2.7-8 Disclosure of Team Arrangements (April 2008) 3.6.2-7 Preaward On-Site Equal Opportunity Compliance Review (July 2011)

L.1.1 Clauses and Provisions Incorporated in Full Text

The version(s) of clauses incorporated in this SIR are in effect on the date of the issuance of the SIR release is applicable unless otherwise specifically noted.

3.2.2.3-20 Electronic Offers (July 2004)

(a) The Offeror (you) must submit an electronic (soft copy) of the proposal in response to this SIR by the following electronic means: CD or DVD must be delivered with proposal hard copies per instructions in L.2 General Instructions & L.3 Proposal Submission and Delivery Instructions, and to the extent possible, you must maintain the same content, organization and format as the hard copies, as detailed in L.4 Proposal General Content, Organization, and Format Instructions.

(b) The FAA reserves the right to decline to consider electronic offers that do not include required information, or that reject any of the terms, conditions and provisions of the SIR.

(c) Send your offer electronically to: not applicable per paragraph (a).

http://conwrite.faa.gov/

(d) The FAA is not responsible for any failure or problem relating to an Offeror’s attempt to submit, or the submitted, electronic offer.

(End of provision)

3.2.2.3-22 Period for Acceptance of Offer (October 2014))

The offeror (you) agrees that 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 Alternate II Requirements for Certified Cost or Pricing Data or Other Information (July 2010)

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

(b) The Offeror must provide the following information:

Offeror must provide information identified in Section L.7 of this SIR.

This SIR requires submission of “other than certified cost and pricing data” as stated in Section I, however the government reserves the right to request certified cost and pricing data if the CO deems it necessary in order to determine if proposed prices are fair and reasonable.

(End of provision)

3.2.4-1 Type of Contract (April 1996)

The FAA contemplates award of a hybrid contract that includes Cost-Plus Fixed Fee (CPFF), Cost-Plus Incentive Fee (CPIF), Firm Fixed Price (FFP) and Time & Materials (T&M) CLINs resulting from this SIR.

(End of provision)

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:

541512 Computer Systems Design Services.

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

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

(End of provision)

3.9.1-3 Protest (October 2011)

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

OFFEROR OR POTENTIAL OFFEROR AGREES TO BE BOUND BY THE FOLLOWING

PROVISIONS RELATING TO PROTESTS:

(a) Protests concerning FAA SIRs or awards of contracts must be resolved through the Federal Aviation Administration dispute resolution system at the Office of Dispute Resolution for Acquisition (ODRA) and must 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 must 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 Standard 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 must 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 must 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 must 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 must 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 must 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) http://www.faa.gov/

L.2 General Instructions

L.2.1 Compliance with Instructions

The FAA reserves the right to award a contract based on initial offers received, without communications. Therefore, Offerors are put on notice that it is in their best interest to put their best proposal forward and not rely on communications.

The FAA will review all proposals for completeness, clarity and adherence to this Section L.

The FAA reserves the right to reject proposals that are incomplete, incoherent, or do not adhere to Section L instructions.

L.2.2 Expenses Related to Offerors Submissions

The government will not pay, reimburse, credit or otherwise compensate any costs incurred relating to competition for this SIR.

L.2.3 Alternative Proposals

Offerors are invited to submit one and only one proposal. The submission of more than one proposal per Offeror will be considered an alternate proposal. The FAA will not consider alternate proposals.

L.2.4 SIR Questions or Clarifications

The Offeror must submit any question, clarification, notification of discrepancy, error, omission or similar, relating to this SIR in writing to the Contracting Officer via electronic email at Sharonda.Holmes@faa.gov, no later than 3:00pm Eastern Time on the 10th calendar day following the day of SIR release. The Offeror is responsible for ensuring that the FAA Contracting Officer has received the communication. For each communication, the Contractor must identify the issue, segregate the topic, and reference the applicable SIR section and paragraph (e.g., Section H, Provision H-3, subparagraph (a)).

The FAA will post any SIR amendment(s), and any question and answer the FAA determines helpful, on the internet at https://faaco.faa.gov.

L.2.5 Proposal Modifications

The FAA will not accept proposal modifications, unless permitted, or requested by the FAA in writing.

In response to FAA communications, Offerors must limit modifications to their proposals to the pertinent proposal section and the subject of the communications. If change pages are required, the Offeror must not exceed the total page count listed for the original proposal set forth in this Section L unless directed otherwise by the Contracting Officer in writing.

mailto:Sharonda.Holmes@faa.gov http://https/faaco.faa.gov

In the response to a SIR amendment, instructions will be issued with the amendment regarding any effect to total proposal page count limitations.

The FAA reserves the right to identify, correct, and/or account for administrative errors, such as mathematical errors or inaccurate cross references. The FAA reserves the right to request an updated proposal.

The FAA reserves the right to treat responses received after the time and date specified in the request, as a late offer and handled in accordance with AMS 3.2.2.3-14.

L.2.6 Notification of Intent to Withdraw Proposal

The Offeror must submit notification of intent to withdraw proposal in writing to the FAA Contracting Officer, prior to the FAA’s selection decision announcement. The Offeror must transmit notification through the designated authorized negotiator, as identified in Section K.

L.2.7 Disposition of Proposals

The FAA will not return any proposals received.

L.2.8 Non-FAA Personnel Participation

The FAA reserves the right to utilize contractor support personnel to assist during the evaluation of offers. All participating non-FAA personnel will sign Non-Disclosure of Information and Conflict of Interest statements. The exclusive responsibility for source selection will remain with the FAA.

Individuals serving as advisors or evaluators are only authorized to access proposal information necessary to enable them to carry out their duties relating the SIR. To object, the Offeror must send the Contracting Officer, a written detailed statement describing the objection no later than 7 business days after the day of SIR release.

B3 Solutions Best Value Technology, Inc. (BVTI) Engility Corporation Infina, Ltd.

JMA Solutions LLC MCR Federal LLC MITRE Corporation Noblis Regulus Group LLC SEMCON Group LCC Source Selection Consulting LLC Tecolote Research, Inc.

L.2.9 Organizational Conflict of Interest (OCI)

Applicable FAA AMS clauses are provided in Section I of the SIR.

Pursuant to AMS Guidance T3.1.7, an organizational conflict of interest means that because of existing or planned activities, an Offeror or contractor is unable or potentially unable to render impartial assistance to the agency, or has an unfair competitive advantage, or the Offeror or contractor’s objectivity is or might be impaired.

For example, companies which are providing, will provide, or have provided, program management support to the Government related to the planning for a competitive procurement or oversight of the awarded contract, may be considered to have an unacceptable COI risk and ineligible to provide products or services to implement requirements under this contract.

Companies which support(ed) the Government in development of concepts and system requirements for work within the scope of future acquisitions may be considered to have an unfair competitive advantage and thus may be considered ineligible to provide products or services to implement the requirements under this contract unless the Contracting Officer has approved a mitigation plan.

The following companies are not eligible for award as a prime or subcontractor due to OCI concerns:

A3 Technology, Inc.

Advanced Science & Technologies LLC Advanced Systems, Inc.

Air Traffic Operations Evolution Allied Tech Group, Inc.

APTAS Technologies Architecture Technology Corporation ARCON Corporation Aurora Sciences, LLC AvMet Applications, Inc.

B3 Solutions Battelle Memorial Institute Big Texas Sky, Inc.

Boeing Booz Allen Hamilton Best Value Technology, Inc. (BVTI) CEXEC, Inc.

CNA

COBEC Consulting, Inc.

Constellation Aviation Solutions, LCC CSSI, Inc.

Cummings and Associates, Inc. (CAA) Dag Consulting DTIS Corp.

Dovel Technologies Engility Corporation (f.k.a. TASC) Enroute Computer Services Enterprise Solutions, Inc.

Evans, Inc.

FlightView, Inc.

Genco Systems, Inc.

Grant Thorton LLP Hi-Tech Solutions, Inc.

Human Solutions, Inc.

Humanproof, Inc.

Infina, Ltd.

Insight Global Jerry Thompson and Associates (JTA), Inc.

JMA Solutions LLC Manassas Consulting Services, Inc.

Mantech International MCR Federal LLC Metron Aviation, Inc.

MIT Lincoln Laboratory MITRE Corporation Mosaic ATM North American Technical Services, Inc.

Noblis

North Star Group LLC Northcross Group Northrup Grumman Corporation Regulus Group LLC Safety Net Solutions, Inc.

Science Applications International Corporation SEMCON Group LCC Source Selection Consulting LCC Spectrum Engineering Services Sunhillo Technical Services

Superior Technical Solutions LLC Tecolote Research, Inc.

TND Consulting LLC URS Corporation Veracity Engineering Veterans Enterprise Tech Services (VETS), LLC

Wydah Corp.

Zionsoft, Inc.

L.2.10 Communications

The Offeror must direct any communication to the Contracting Officer identified in L.3. The FAA reserves the right to consider any information disclosed as a result of oral or written communications with an Offeror in the evaluation.

The FAA reserves the right to conduct communications for reasons including, but not limited to, enhancing FAA understanding of an Offeror’s proposal, obtaining information that would allow reasonable interpretation of the Offeror’s proposal, facilitate the FAA’s evaluation process, or clarify ambiguities in the Offeror’s proposal.

L.3 Proposal Submission and Delivery Instructions

The Offeror must deliver its proposal submission to the following FAA Contracting Officer:

Sharonda Holmes, AAQ-250 Contracting Officer

Federal Aviation Administration 800 Independence Avenue, SW

Orville Wright Building (FOB10A) Room 406

Washington DC 20591

HAND-DELIVERY: Offerors will not have access to this above facility without proper credentials, or an authorized escort. For coordination of hand delivery of proposal, the Offeror must provide security with the following point of contact information:

Jamie Mosko ACQ-250, Decision Support Systems Branch

202-267-9388

TIME AND DATE: Proposals must be received by the Contracting Officer by no later than 3:00pm, Eastern Time on the 42nd calendar day after the day of SIR issuanceNovember 7, 2016.

PROPOSAL SUBMISSION: An Offeror assumes the full responsibility of ensuring that proposals are received at the place and time specified above. Offerors are cautioned that offers delivered to the mail processing center within the Federal Office Building at 800 Independence Avenue will undergo additional security scrutiny that can delay delivery of the proposal. For deliveries by courier, the room number must be included to complete the delivery to the Contracting Officer. Please note that there are no provisions for acceptance of late offers sent by overnight courier service regardless of the date of mailing except U.S. Postal Service Express Mail and Next Day Service as provided in AMS Clause 3.2.2.3-14. The FAA reserves the right to reject those proposals not submitted in accordance with the delivery instructions above.

L.4 Proposal General Content, Organization, and Format Instructions

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

L.4.1 Proposal Content

The Offeror must include a cover submittal letter with the proposal. The submittal letter must include the Offeror’s acknowledgement of any and all SIR amendments in accordance with AMS 3.2.2.3-12 Amendment Screening Information Requests (July 2004).

Proposals must include supporting rationale and substantiation of all factual information to facilitate the FAA’s evaluation. The FAA reserves the right to determine general statements of the Offeror’s understanding of FAA objectives, or simple rephrasing and/or restating of FAA objectives as inadequate; as a result the FAA reserves the right to assess a weakness for such statements. Similarly, the FAA reserves the right to assess weakness and risks for proposals that contain omissions, contain incomplete responses to the SIR requirements, or use non-specific phrases such as “in accordance with standard procedures” or "well-known techniques".

Offerors should assume that the FAA has no prior knowledge of their proposed solution, capability, or experience and that the FAA will base its evaluation on the information presented by the Offeror.

Proposals must contain enough detail to enable the FAA to determine the ability of the Offeror and the proposed solution to meet the SIR requirements. Offerors must not assume that they will be contacted or afforded an opportunity to clarify, discuss, or revise their proposal.

If, within the same volume, information is required in response to more than one SIR requirement, the Offeror need not repeat information but may reference the information and identify its location.

Unless clearly instructed otherwise, the Offeror must not include any cost or price information in any of the volumes other than the Cost/Price Volume.

L.4.2 Proposal Organization

Offerors must assemble and identify separate proposal volumes in accordance with Table L.4-1 below. Offerors must ensure all content is delivered within the page limitations and with the number of copies shown in the table below. The FAA reserves the right to make additional copies of submitted proposal information (hard and soft) as necessary to support the evaluation process.

Table L.4-1 Proposal Volumes

Volume Title Page Limit

Hard Qty

Soft Qty

I

Technical & Management

Original plus 7 8

Part A – Table of Contents None Part B – Abbreviations and Acronyms None Part C – Executive Summary

225* Part D – Technical and Management Exceptions, Deviations and Assumptions Part E – Detailed Technical Proposal

II

Past Performance

Original plus 3 4 Part A – Experience Narratives 15

Part B – Past Performance References None Part C – Past Performance Survey Record None

III

Cost/Price Original plus 6 7

Part A – Cost/Price Workbook and Supporting Detail Data None Part B – Detailed Narrative, and Supporting Documentation None Part C – Cost/Price Exceptions, Deviations and Assumptions None Part D – Basis of Estimate None

IV Contract Transition Plan None Original plus 7 8

V

Offer and Other Documents

Original plus 1

Part A – Master Table of Contents None Part B – Solicitation, Offer & Award form SF-33: Model Contract None Part C – Completed Section K None Part D – Business and Financial Capacity None Part E – Organizational Conflict of Interest (OCI) Issues None Part F – Earned Value Management System Certification or Plan None Part G – Master List of Exceptions, Deviations and Exceptions None Part H – Small Business Subcontracting and Mentor Protégé Program None

*Vol. I, Part E Detailed Technical Proposal page count limit excludes the integrated schedule required by Factor 3B.

L.4.3 Proposal Format All volumes must be titled as identified in Table 4-1. Offeror must provide a definition for all acronyms and abbreviations throughout the proposal. Acronym list(s) will not count against page limits.

L.4.3.1 Signed Original

The Offeror must submit an original version of the proposal in hard copy format. The original version must include the signed submittal letter as required in Section L.4.1. The Offeror must also provide original signatures on each transmittal letter, for each volume, as required in Section L.4.3.2.

L.4.3.2 Binding and Labeling

The Offeror must mark all volumes of the proposal, including electronic (CD/DVD) labels, as "Source Selection Sensitive."

Offerors must mark all volumes with the solicitation number. Offerors must submit a transmittal cover letter of not more than one page for each volume. This page will not count towards the page limit for the volumes. The volume transmittal letters described in this section are different from the signed submittal letter for the overall proposal called for in Section L.4.1.

The Offeror must bind each volume of the proposal in a separate three (3) ring binder. The Offeror must label the binder with both a cover label and a spine label.

The cover label must be clearly marked with the following information:

1) Volume name (i.e. Technical and Management, Cost/Price, etc.);

2) “Original” or “Copy” designation, with a copy number (e.g. Copy # X of Y);

3) Book number, if volume capacity necessitates more than one binder (e.g. Book #X of Y);

3) SIR number and Amendment number (if applicable);

4) Offeror’s name, and;

5) Date of submission.

The spine label must appear on the spine of the binder to permit identification when the volume is placed in a vertical position in a storage cabinet.

The Offeror must label each page of the proposal in the header or footer section with the SIR/Amendment number, Volume, Book, and Page number.

L.4.3.3 Indexing

Tab indexing must be used to identify all Volumes and Sections listed in Table 4-1. Each volume must have a tab index of contents. Proposals must be clearly and concisely written as well as being neat, indexed (cross-indexed as appropriate), and logically assembled. Within each volume, labeled dividers must separate major divisions and sections. Dividers must not include any proposal content.

L.4.3.4 Format of Hard Copies

All volumes may use a combination of 8.5” by 11” or 11” by 17” pages (per limitations in paragraph below) All pages in all volumes are to be 8.5” by 11” portrait orientation with margins no smaller than one inch. The font used for text must be Times New Roman. Font size no smaller than 12 point, except for footnotes which may be no smaller than 10-point. Line spacing must be no less than the single (1.0) spaced. For hard copies, printing on both sides is preferred. A page printed on both sides will count as two pages.

All 8.5 by 11 pages must be printed in portrait orientation unless Ccharts, figures, or tables fill the page, in which case they may be in printed in either portrait, or landscape orientation., and Charts, figures, or tables will be counted against page count limits and . Tthe font size for these inserts must not be less than 10 point. Foldouts may be used for paper size up to 11” by 17” pages must printed in portrait orientation, folded to 8.5” by 11”, and must be secured within the volume binder. The FAA will count 11” by 17” print outs as two pages for each side, i.e., a two sided print of 11” by 17” will be counted as four pages.

L.4.3.5 Format of Electronic Copies

In addition to hard copies, proposals must be submitted in electronic files on CD or DVD.

Electronic copies must match original hard copy of record. Additional information will not be evaluated or considered. The FAA must be able to edit all files using Microsoft Office 2010 software; the Offeror is responsible for ensuring software versions are compatible with this version. All MS Excel files must include cell references and calculations. The electronic copies must be marked with Offeror’s name, SIR /Amendment number, volume name(s), and volume number(s).

L.5 Instructions for Volume I – Technical & Management Proposal

L.5.1 General

Offerors must provide information for each of the Factors and Subfactors described below in the Technical & Management.

This volume must clearly and completely describe how the Offeror's approach will comply with SIR requirements and include explanations of the techniques and processes to be followed.

L.5.2 Part A – Table of Contents

The Offeror's proposal must contain a table of contents that identifies major subparagraphs by number, title, and page number.

L.5.3 Part B – Master Abbreviation and Acronym List

The Offeror must provide a list of all abbreviations and acronyms, along with their definitions, used in the proposal.

L.5.4 Part C – Executive Summary

Offerors must provide an executive summary that provides an overview of the entire volume.

The executive summary should highlight the major areas of the proposal and provide the reader with a general understanding of the proposed approach.

L.5.5 Part D – Technical and Management Exceptions, Deviations and Assumptions

The Offeror must explicitly state all exceptions, deviations and assumptions relating to the Offeror’s Technical and Management Proposal and include them in this part of Volume I. Each exception, deviation and assumption must be mapped, or have a reference to, a specific paragraph/section of the SIR and the Offeror’s proposal.

L.5.6 Part E – Technical and Management Factors

The proposal must address the following evaluation factors and sub-factors. The Offeror’s must provide an index between their proposal and each of the factors and sub-factors below.

L.5.6.1 Factor 1 -- Operations and Maintenance

Subfactor A – First Level Support

The Offeror must describe the proposed approach to meeting the First Level Support requirements in Section C.10.1 for monitoring, operating, maintaining and supporting 24/7/365 sustainment of the TFMS products listed in Section C, Appendix A, at all locations specified in Section F.5, and assure the system meets the functional and performance requirements in the System Subsystem Specification (SSS) and Interface Requirements Specification (IRS) provided in Attachment J-2.

The Offeror must clearly identify how their help desk approach will respond to system problems and user/customer/client help requests in a timely manner. The Offeror must describe the proposed approach, starting from when a user/customer/client help request is received, through the implementation of the request resolution or escalation to Second Level Engineering. The Offeror must also provide details associated with help desk metrics collected throughout the process and how those metrics contribute to measuring system performance.

Tools, processes and metrics used in the proposed approach must be described in detail. The Offeror must describe how their approach will include government approval of system changes and planned outages, as well as how notifications about system impacts will be communicated to users/customers/clients and other stakeholders. The Offeror must discuss their approach to TFMS system/service restoration and how the approach will minimize the impact to users/customers/clients. The Offeror must include details of the approach for escalation for unresolved issues.

Subfactor B – Second Level Engineering (SLE) and Support

The Offeror must describe the proposed approach to meeting the Second Level Engineering (SLE) and Support requirements defined in Section C.10.2 for the TFMS products listed in Section C, Appendix A, at all locations specified in Section F.5, and assure the system meets the functional and performance requirements in the System Subsystem Specification (SSS) and Interface Requirements Specification (IRS) provided in Attachment J-2.

The Offeror must detail how the proposed approach: assesses and categorizes the severity of problems of hardware and software problems, as defined in Section H.10.2; performs root cause analysis; identifies problem resolution alternatives; assesses their implementation risk and impact; and efficiently packages software patches/updates for timely deployment.

The Offeror must describe how the proposed approach works with and/or utilizes other related key engineering processes and tools, such as change management, development and test of system changes.

The Offeror must also discuss the collection, analysis and use of system performance metrics, such as identifying trends to proactively address potential future problems.

Subfactor C – Aeronautical Adaptation Data

The Offeror must describe the proposed approach to meeting TFMS adaptation requirements defined in Section C.10.2.4, and how it plans to keep the underlying data current with changes to the National Airspace System. The Offeror must describe any tools planned for use with the process and how those tools contribute to timely, accurate and verified adaptation changes to the system and its services. The Offeror must address, in its approach, all types of adaptation that require recurring data collection, change assessment, and application of updates.

The Offeror must describe proposed processes and tools used to determine possible risks and impacts from deploying adaptation data updates (e.g. execution errors, failure to complete on time), how these will be mitigated and contingency plan(s).

L.5.6.2 Factor 2 -- Security

Subfactor A -- Access Management and Configuration Control

The Offeror must describe the proposed approach to accomplish user/customer/client identification, authentication and access control. See Section C.4, FAA Order 1370.82A, Information Systems Security Program, Chapter 3, Sections 2, 6, and 8; FAA Security Authorization Handbook, Section 3, paragraph 3.2.1.5; and NIST 800-53 Rev 4 under the Control Identifiers of Access Control (AC), and Identification and Authentication (IA).

The Offeror must describe the proposed approach to ensure privacy protection, data loss prevention and encrypted media protection. See Section C.4, NIST 800-53 Rev 4 controls of System and Communication Protection (SC-7), Physical and Environmental Protection (PE-4), and Media Protection (MP-7).

The Offeror must describe the proposed approach to prevent unauthorized changes to system configuration. See Section C.4, FAA Order 1800.66, Configuration Management Policy and NIST 800-53 Rev 4 Configuration Management (CM) control family.

The Offeror must describe the proposed approach to provide system integrity flaw detection and remediation. See Section C.4, NIST 800-53 Rev 4 System Integrity (SI) control family.

Subfactor B -- Event Logging, Auditing and Analysis

The Offeror must describe the propose approach to detect and log security events. See Section C.4, NIST 800-53 Rev 4 Audit and Accountability (AU) control family.

The Offeror must describe the proposed approach to analyze security event logs and protect logs against modification and deletion to required functions. See Section C.4.

Subfactor C -- Security Risk Management

The Offeror must describe the proposed approach to identify system security weaknesses and risks. See Section C.4, NIST 800-53 Rev 4 Developer Security Testing and Evaluation (SA-11).

The Offeror must describe the proposed approach to mitigate risks and remediate weaknesses, e.g., Plan of Action and Milestones (POAM). See Section C.4, NIST 800-53 Rev 4 CA-2 Security Assessments (CA-2); NIST Special Publications 800-60, 800-88; and FIPS Publication 199.

The Offeror must describe the proposed approach to analyze the security impacts of system changes. See Section C.4, NIST 800-53 Rev 4 Development Process, Standards, and Tools (SA- 15).

L.5.6.3 Factor 3 -- Engineering, Development, Test and Implementation

Subfactor A -- Engineering Process

The Offeror must describe the proposed approach, addressing all pertinent engineering disciplines, to modify and enhance TFMS, from requirements analysis to implementation (see Section C.5), considering the following: (1) the requirements identified for the first three potential TFM2 releases defined under Section J-6, Attachments J-6.A-H; and (2) the timing of release durations and milestones identified in Section F.4.1. The Offeror must describe the features that make the proposed engineering process viable, adhered to, and effective.

The Offeror must describe how the proposed overall engineering process addresses development of multiple, concurrent, overlapping system releases. The Offeror must identify and address all inter-dependencies related to the engineering process in general, and any inter-dependencies related to the engineering process based on the specific requirements and timelines associated with Releases 1 through 3. The Offeror must describe the process for maintaining traceability of requirements from their origin to the lowest level component. The Offeror must describe the process for conducting solution alternative assessments, e.g., use commercial vs. developing new software.

The Offeror must describe its proposed software engineering and development process model(s) (e.g., linear, sequential, incremental, spiral, etc.) including reasons for selecting the model(s) and it benefits to enhancing the TFMS. The Offeror must explain, in general, as well as based on the requirements of the first three releases, how the proposed model is applicable and supports multiple overlapping releases. The Offeror must describe how the model(s) will be applied in all phases of the system development life cycle.

Subfactor B -- Release Technical Approach, Schedule and Milestones

The Offeror must provide an integrated schedule of the first three potential releases, described in Section J-6 Future Requirements, Attachments J-6.A-H, which includes activities associated with system engineering, design, development, test and implementation of the releases by the milestone dates identified in Section F.4. The schedule must account for the activities shown in Section F, Figure F-1, Typical Release Timeline. The schedule must account for the development and Government review times of the CDRLs related to these activities (see Section C). The schedule must identify interdependencies, within and across releases, and the critical path. The schedule will not be counted against the page limitation of Volume I, Part E.

For each of the three potential TFMS releases, the Offeror must provide a basis ofan estimate of the software size and, productivity rate, and such basis must include and the technical basis of these estimates, such as the software estimation methodology used, assumptions, engineering tradeoff analyses, design decisions, risks and mitigation steps. The Offeror must clearly articulate how the basis of estimate applies to schedule activities and durations.

Subfactor C -- Development Environment

The Offeror must describe how the proposed development environment (see C.5.5) will provide the services necessary to enhance the TFMS software. The Offeror must discuss in detail the functions provided by the development environment, as well as the level of automation provided for each of the functions. The Offeror must provide a description of the tool or tools chosen to support software development. At a minimum, the Offeror must discuss:

a. The tool(s) used to track requirements from the Government-provided documents to the Contractor-maintained documents;

b. The tool(s) used for configuration management and approach for concurrently managing multiple versions of product software, e.g., release in current operations, release undergoing formal Government acceptance testing, and release under development;

c. How the development environment and toolset accommodates Government involvement and oversight of software development activities and work products;

d. How the development environment aids in engineering analysis, design, software development, test, and maintenance;

e. The extent to which the development environment ensures software reuse and extensibility;

f. The degree of cohesion among the tools in the development environment; and

g. The benefits and risks associated with the proposed development environment and tools.

Subfactor D -- Test and Implementation

The Offeror must describe a proposed approach for testing TFMS system changes and implementing them into operational use at the sites specified in Section F.5.1. The proposed approach must address the following:

a. Internal testing (e.g. unit, integration, qualification) to ensure timely identification and resolution of problems;

b. Formal acceptance testing (see C.7);

c. Implementation strategy, risk mitigation and how impact to operations is estimated, minimized and communicated; and

d. Criteria for assessing readiness.

L.5.6.4 Factor 4 -- Program Management

Subfactor A – Program Structure and Key Personnel

The Offeror must describe its proposed program organization and how the organization facilitates program execution (see Section C.3). The description must contain a graphical representation of the organizational structure identifying all proposed key personnel and providing the company affiliation of each person on the chart.

The Offeror must describe the lines of communication and issue-escalation processes internally within the organization and externally with the Government and other program stakeholders.

The Offeror must discuss the responsibility, accountability and decision making authority of the Program Manager and other key managers/leaders in the organization. In addition, the Offeror must describe the roles of subcontractors in the program organization.

The Offeror must describe the approach for planning and allocating work within the program organization. For work allocated to subcontractors, the Offeror must describe the approach for:

overseeing subcontractor activities; identifying and addressing performance issues; integrating subcontractor personnel into the proposed management and technical approaches; and sharing information among all organizational elements, including subcontractors.

The Offeror must list names of individuals proposed as Key Personnel for the labor categories listed in Section H.1 Key Personnel. The Offeror may propose additional key personnel positions in addition to the FAA identified categories. Offeror must submit resumes for all proposed key personnel listed and all resumes must meet the minimum qualification requirements in Section J

- Attachment J-7. Resumes must specify the proposed individual’s time commitment to the TFM2 Program (as a percentage of full-time) and include specific experience and background relative to the position, TFM2 program requirements and the Offeror’s proposed development and management approaches.

The Offeror must describe the approach to obtaining and retaining qualified personnel to ensure the size, experience and expertise of the workforce is adequate and minimizes program risk associated with staff turnover.

Subfactor B – Risk Management

The Offeror must describe its proposed risk management and mitigation process (see Section C.3.3). The Offeror must detail how program and system risks are identified, categorized, prioritized, mitigated, and tracked within this proposed approach.

The Offeror must identify how the process ties into other technical and management processes.

The Offeror must explain how the status of each risk factor and its mitigation strategy will be communicated to the FAA and throughout their organization.

Subfactor C – Performance Management

The Offeror must propose performance metrics for the TFMS and the program, as well as the proposed approach (i.e. techniques, tools and methods) to measure, track, and report this performance information in all phases of the program life cycle (see Section C.3.5).

The Offeror must describe any proposed reporting systems planned for capturing performance metrics and the system’s advantages and disadvantages.

The Offeror must propose methods and procedures for financial management including accounting, cost management, cost estimation, and budget development. The Offeror must describe a proposed plan for establishing and maintaining measurement baselines.

The Offeror must describe an approach to measure and maintain product quality throughout the program lifecycle. The Offeror must detail the proposed quality control mechanisms and discuss the risks and benefits.

The Offeror must describe how the performance and quality data will be used to improve program execution and its approach for continuously refining the data to be collected.

The Offeror must also describe how the measurement system will facilitate Government insight into program performance and quality progress and status.

L.6 VOLUME II –PAST PERFORMANCE

L.6.1 Part A -- Experience Narratives

Offeror must provide information on three instances of past performance considered both recent and relevant in demonstrating ability to perform the SIR requirements and work efforts. Offeror must include rationale supporting assertion of recency and relevance for each of the three instances. Contracts cited as examples must be of similar in size, scope and complexity to this SIR. The FAA has provided (see Section L Attachment L-1, TFM2 Size, Scope and Complexity Summary Supplemental to assist Offerors in chosing their three relevant examples). Size, scope and complexity of work under this contract is not limited to L-1.

At least two of the three contracts included must be for work performed by the proposing prime vendor. Proposed subcontractor experience must be no more than one instance.

For purposes of this SIR;

“Recent” means that the instance of relevant past performance must have been performed for more than the last 12 consecutive months, or completed within the last three years of the date of proposal submission.

“Relevant” relates to services performed for the government or private industry customers of essentially similar size, scope and complexity as compared to the requirements of this SIR (see Section L Attachment L-1, TFM2 Size, Scope and Complexity Summary).

L.6.2 Part B -- Past Performance References

For each of the three instances cited in Part A L 6.1, the Offeror must provide reference information using the format provided in Section L Attachment L-2A, Past Performance References, which must identify the respective CO or COR (or the private sector equivalent position).

L.6.3 Part C -- Past Performance Survey Record

The Offeror must provide a record, using the format provided in Attachment L-2B, Past Performance Survey Record Form, of its best efforts to have each of the references cited in Part B to complete and return the Past Performance Survey Form, Attachment L-2C, directly to the Government’s Contracting Officer no later than the proposal submission due date. The survey respondent must be the CO or COR (or the private sector equivalent position).

L.7 VOLUME III – COST / PRICE PROPOSAL

L.7.1 General

The Cost/Price Volume III must be in a separate package plainly marked "Volume III: Cost/Price Proposal." Cost/pricing data must not be included with any other proposal volume.

Offerors must provide information as instructed in each of the sections below in the Cost/Price Volume. Offerors must include information to substantiate and fully address all aspects of proposed technical and management approach to the SIR requirements.

The cost/pricing instructions and required level of detail are applicable to the prime Offeror, all proposed subcontractors, and/or each division or segment of the prime company, if proposed as intercompany work. Proposed subcontractors may submit their cost/price detailed cost/pricing data directly to the Contracting Officer, separate from the prime contractor cost/price proposal.

The Prime Offeror must ensure that all cost/price proposal information, including subcontractors’, is submitted in accordance with the requirements of this SIR.

L.7.2 Government Pricing Guidance and Constraints

For all CLIN(s):

Offerors should base CLIN Period of Performance dates on the contract award target date of February 1, 2017.

The TFMS system is continuously updated and documents such as the system-level requirements, design materials, and other system documents will change to reflect the current information. In order to ensure that all competitors are addressing the same system state, the government establishes the static point in time as March 21, 2016 for evaluation purposes.

Offerors must address requirements only using this referenced point of time. Offerors must only use system information in the documents published in this SIR for proposal preparation purposes.

Offerors must not combine costs for operations or sustainment, with development of new capabilities in the same CLIN. Offerors must propose costs associated with the related TFMS Development and Future Enhancement capabilities under the related CLINs (11A, 11B, or 11C).

An example of a TFMS typical release timeline is provided in Section F, Figure F-1. This timeline is included as a notional timeline anticipated for developing and deploying new releases under CLIN(s) 11A, 11B, and 11C. This information is relevant to estimating work for future enhancements.

The following provides additional guidance and constraints for each CLIN included in this

SIR:

CLIN 1 First Level Support

All of the documents in Attachments J-2-Current System-level Requirements, J-3-GFI, and J-4- GFE/GFP are relevant to estimating the work under CLIN 1.

Attachment L-1 provides supplemental information on the TFMS size, scope and complexity which includes performance metrics and recurring system checks/actions and is relevant to estimating pricing for CLIN 1.

TFM Production Center (TPC) space and workstations are GFE/GFP and must be used for Contractor staff normally working at the TPC.

Operation and Sustainment costs associated with developing and deploying a new release under CLIN 11 must not be included in CLIN 1, but rather in the applicable release.

CLIN 2 Second Level Engineering (SLE)

All of the documents in Attachments J-2, Current System-level Requirements, J-3, GFI, and J-4, GFE/GFP are relevant to estimating the work under CLIN 2.

Attachment L-1 provides supplemental information on a summary of the TFMS size, scope and complexity which includes custom software application sizes and technology and is relevant to estimating pricing for CLIN 2. For pricing purposes, the average patch development, test and deployment is two four per year at 5,000 SLOC each.

Second Level…