Draft Section L.docx

TFM-2 DRAFT SIR Section L

PART IV - SECTION L: INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

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

1.13-1 Notice of Earned Value Management System (January 2006)

The Offeror's (you/your) response to this screening information request (SIR) must include proof of a certified EVMS or provide a plan (the plan) to implement a certified system that complies with the EVMS criteria (the criteria) stated in subparagraph (b) of clause 1.13-2, "EVMS." You must submit the following as part of your proposal for Contracting Officer (CO) approval:

(a) Documentation demonstrating that your EVMS has been American National Standard ANSI/EIA 748 certified and EVM surveillance documentation demonstrating that you have maintained an American National Standard ANSI/EIA 748 compliant EVMS at the time this SIR is issued; or

(b) The plan that explains how your EVMS will be certified for each guideline of the American National Standard ANSI/EIA 748 Standard.

(c) Names of subcontractors. If you have not yet identified subcontractors, you must identify any part of the work you intend to award to subcontractors. The CO must approve the subcontractors before you sign contracts with them.

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

AS STATED PER SIR SECTION L.6.

(End of provision)

3.2.4-1 Type of Contract (April 1996)

The FAA contemplates award of a hybrid IDIQ contract that includes CPFF, CPIF, and T&M CLINs resulting from this Screening Information Request.

(End of provision)

3.6.2-34 Service Contract Act - Place of Performance Unknown (April 1996)

(a) This contract is subject to the Service Contract Act, and the place of performance was unknown when the Screening Information Request (SIR) was issued. In addition to places or areas identified in wage determinations, if any, attached to the SIR, wage determinations have also been requested for the following: _______________ (insert places or areas). The Contracting Officer will request wage determinations for additional places or areas of performance if asked to do so in writing by _______________ (insert time and date).

(b) Offerors who intend to perform in a place or area of performance for which a wage determination has not been attached or requested may nevertheless submit offers. However, a wage determination shall be requested and incorporated in the resultant contract retroactive to the date of contract award, and there shall be no adjustment in the contract price.

(End of clause)

3.2.2.3-22 Period for Acceptance of Offer (July 2004)

The Offeror (you) agree 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.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)

L.1 General Instructions

L.1.1 Compliance with Instructions

Offerors must comply with all instructions in Section L when developing proposals. Failure to comply with the instructions may result in a determination that the Offeror’s proposal is non-compliant. This determination will be made at the sole discretion of the Government. Proposals must conform to all incorporated AMS clauses and provisions and be prepared in accordance with this section. To aid in the evaluations, proposals must be clearly and concisely written, as well as, neat, indexed (cross indexed as appropriate), and logically assembled. All material submitted should be directly pertinent to the requirements of this SIR.

L.1.2 Expenses Related to Offerors Submissions

Offerors are warned that the FAA is not responsible for, and will not pay, reimburse, credit or otherwise compensate any costs incurred by the Offerors in the development or submission of any aspect of their proposal under this SIR. This includes costs associated with any aspect of the proposal activity and any research, studies, or designs carried out for the purpose of incorporation into any part of the proposal. It also includes any costs to acquire or subcontract for any services or products relating to the offer under this SIR.

No pre-contract costs will be allowed on this contract. Pre-contract costs are defined as any costs incurred at the Offeror’s risk in anticipation that any such costs may later be charged to any resulting contract, and to the extent that they would have been allowable if incurred after the date of the contract and to the extent authorized by the Contracting Officer.

L.1.3 Alternative Proposals

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

L.1.4 SIR Questions

Any questions or clarifications regarding any section of the SIR must be prepared in writing and submitted to the Contracting Officer via electronic mail at sharonda.holmes@faa.gov. Questions/clarifications must be identified and segregated by topic, and must make reference to the applicable SIR section or paragraph (e.g., Section H, Provision H-3, subparagraph (a)).

Pertinent questions will be answered via amendment and provided to all Offerors on the Internet at www.faaco.faa.gov. The FAA will not attribute the questions to the submitting Offerors, but the text of the pertinent questions and answers will be made available to the general public.

All questions and clarifications relating to this SIR must be received by the Contracting Officer within two weeks of SIR issuance, at 3:00 PM Eastern Time. The Offeror is responsible for ensuring that the FAA Contracting Officer has received the questions or clarifications.

Oral explanations or instructions from the FAA given to Offerors before the award of the contract will be binding only if confirmed in writing.

If an Offeror believes that these instructions contain an error, omission, or are otherwise unsound, the Offeror must immediately notify the Contracting Officer in writing with supporting rationale. Discrepancies not brought to the attention of the FAA prior to proposal submission, are waived.

L.1.5 Equal Access to Information

Any information concerning the SIR given to any Offeror will be promptly furnished to all other Offerors. If the information is necessary in submitting proposals, or if the lack of it would be prejudicial to any other Offeror, the information will be furnished as an amendment to the SIR.

L.1.6 FAA Communications to Offerors

All communications will be documented and controlled through the Contracting Officer. The following conditions apply to Offeror communications:

· Communications with one Offeror do not require communications with any other Offeror.

· The FAA communications may occur orally or in writing; but oral communication by the FAA is not binding unless followed-up in writing.

· The FAA reserves the right to conduct communications, with any individual competing Offeror, some, or all competing Offerors, as the situation warrants.

· The FAA is not obligated to advise Offerors of weaknesses, risks, or deficiencies identified in their proposals.

· Content of the communications may vary between Offerors.

· Any information provided in response to an FAA issued communications may be used in the evaluation of proposals.

· The FAA may make an award based on initial offers without communications.

L.1.7 Proposal Modifications

The FAA reserves the right to make contract award selection based on initial proposal submissions. However, if requested by the FAA, proposal modifications are limited to those modifications required to address FAA communications and specific changes depicted in a SIR amendment.

In response to FAA communications, Offerors are instructed to 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, as set forth herein.

In the response to a SIR amendment, instructions will be issued with the amendment regarding any effect to total page count of the proposals affected. With respect to proposal modifications, any information provided by the Offeror outside the scope of the communication item, discussion item, or the SIR amendment will not be used in the evaluation.

The FAA may correct administrative errors, such as mathematical errors or inaccurate cross references. In this event, the FAA will notify the Offeror of the change and may afford the Offeror an opportunity to submit an updated proposal.

A modification resulting from the FAA’s request, as described above, that is received after the time and date specified in the request, may not be considered unless the late receipt is attributable to mishandling by the FAA.

L.1.8 Notification of Intent to Withdraw Proposal

Offerors are instructed that proposals may be withdrawn by written notice received by the FAA at any time before selection or in-person, by the Offeror, or by an authorized representative if the representative’s identity is made known and the representative signs a receipt for the proposal before award. Proposals may not be withdrawn by facsimile or electronic mail.

L.1.9 Disposition of Proposals

Proposals will not be returned.

L.1.10 Non-FAA Personnel Participation

Offerors are hereby notified that the FAA may utilize contractor support personnel to assist during the evaluation of the offers. All non-FAA personnel and their corporations have signed, or will sign before the evaluation process begins, Non-Disclosure and Conflict of Interest statements. The exclusive responsibility for source selection will remain with the FAA.

The following companies may participate in this process:

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

L.1.11 Organizational Conflict of Interest (OCI)

Applicable FAA AMS clauses:

3.1.7-2 Organizational Conflicts of Interest (August 1997) 3.1.7-4 Organizational Conflict of Interest – Mitigation Plan Required (April 2012)

Pursuant to AMS Guidance T3.1.7, an organizational conflict of interest means that because of an 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.

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, are considered to have an unacceptable COI risk and are 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 Government has OCI concerns with the following companies due to their direct or indirect support of the TFMS (e.g. WP4) and TFDM programs:

A3 Technology, Inc.

Advanced Systems Allied Tech Group Apptis

APTAS (CAA)

Architecture Technology Corporation ARCON Corporation Aurora Sciences AvMet B3 Solutions Battelle Memorial Institute Big Texas Sky Boeing Booz Allen Hamilton CEXEC, Inc.

Constellation Aviation Solutions, LLC

CSSI

Cummings and Associates, Inc.

Dag Consulting DTIS Corp.

Dovel Technologies

ETIS

JMA Solutions LS Technologies MCR Federal LLC Metron Aviation MIT Lincoln Laboratory

MITRE

Mosaic ATM NATS USA, Inc.

Noblis North Star Group LLC Northgrass Group Regulus Group Safety Net Solutions Science Applications International Corp. (SAIC) SEMCON Group LCC Spectrum Engineering Services SRA International Superior Technical Solutions LLC System Enginuity

TASC

Tecolote Research Inc.

Tetratec TND Consulting Veracity Enterprise Tech Services (VETS) URS Corporation Wydah Corp.

L.1.12 List of Interested Subcontractors

Below is a list of potential subcontractors that have expressed interest in the requirement.

North Potomac, Maryland

Vienna, VA 22182

Arlington, VA

Innoviss, Inc.

8401 Connecticut Ave Suite 700 Chevy Chase, MD 20815

L.2 Proposal Submission and Delivery Instructions

L.2.1 Volume Submission and Projected Acquisition Milestones

The following acquisition milestones are provided for informational purposes only and are subject to change. The projected dates for milestones for this procurement are:

L.2.2 Proposal Delivery Instructions

Offerors are instructed to submit proposals in sealed packages addressed to the office as shown below, and to mark on package the time specified for receipt, the SIR number, and the name and address of the Offeror.

ADDRESS: Proposals must be sent to the Contracting Officer at the following address:

Sharonda Holmes, AAQ-240 Federal Aviation Administration 800 Independence Ave. SW Room 406 Washington DC 20591

FOR HAND-DELIVERY: THIS IS A SECURE BUILDING. IT MAY BE NECESSARY TO CALL FROM THE LOBBY TO GAIN ACCESS TO THE ADDRESS IDENTIFIED ABOVE. THE FOLLOWING INDIVIDUALS MAY BE CONTACTED FOR PURPOSE OF DELIVERING A PROPOSAL:

Sharonda Holmes (540) 422-4660

TIME AND DATE: Proposals must be received by the Contracting Officer by XX calendar days after SIR issuance, at ____PM Eastern Time.

SIGNED ORIGINALS: The Offeror must submit an original signed version of all proposal documents. Use of reproductions of signed originals is authorized for all other copies of the proposal.

PROPOSAL SUBMISSION: Offerors assume the full responsibility of ensuring that proposals are received at the place and time specified above. The Offeror is responsible for ensuring that a time-stamped receipt from the CO is received in acknowledgement of the proposal delivery.

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

L.2.3 Submit Legally Binding Documentation

This SIR constitutes a formal document for which an award may be made without communications. Offerors are instructed to comply with all terms and conditions contained in preparation of their proposals. Oral explanations or instructions given by Offerors before signing applicable legal instruments will not be binding.

L.3 Proposal Preparation and General Format Instructions

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

In addressing the requirements of Section L, Offerors are instructed to ensure that all aspects of the factors in Section M are addressed. Also, unless explicitly instructed otherwise, for each section Offerors should address the entire lifecycle of the contract.

L.3.1 General Preparation Instructions

Proposals must include supporting rationale, substantiation of all claims, and factual information to facilitate the FAA’s evaluation. General statements that the Offeror understands FAA objectives or simple rephrasing or restating of FAA objectives will be considered inadequate and may result in weaknesses, risks, and/or lower evaluation scores or may be cause for rejection of the proposal. Similarly, proposals that contain omissions or incomplete responses to the SIR requirements or use non-specific phrases such as “in accordance with standard procedures” or "well-known techniques" will also be considered weaknesses or risks. Weaknesses or risks of this kind may be cause for rejection of the offer and/or result in the Offeror being eliminated from consideration for the contract award.

Offerors should assume that the FAA has no prior knowledge of their proposed solution, capability, and/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 evaluators to determine the ability of the Offeror and the proposed solution to meet the SIR requirements. Lack of detail in a proposal may be deemed a weakness or risk by evaluators. Offerors must not assume that they will be contacted or afforded an opportunity to clarify, discuss, or revise their proposal if FAA evaluators identify omissions or lack of detail.

The Offeror need not repeat information within the same volume if that information is required in response to two or more proposal requirements. Such information should be presented in detail in the one area of the volume where it contributes most critically to the discussion of the SIR requirement. In other areas where discussion of the same information is necessary, the Offeror must refer to the initial discussion and identify its location within the proposed volume. If the Offeror determines that the same or similar information is required in separate volumes, that information must be addressed in full text in each volume.

All proposals will be screened initially for timeliness and adherence to Section L instructions. Offeror proposals that do not meet initial screening criteria will not be evaluated further. Any data that may contain trade secrets, copyright data, and/or financial information which the Offeror or proposed subcontractors do not want disclosed for any purpose other than the evaluation of the proposal must be marked in accordance with AMS 3.2.2.3-16, Restricting, Disclosing, and Using Data (July 2004).

L.3.2 General Format Instructions

Offerors are instructed to assemble and identify proposal separate volumes in accordance with the table below. Offerors are instructed to ensure that all volume titles and associated content must be compiled and delivered within the page limitations, and with the number of copies, shown on Table L 1. The Offerors proposal must comply with the limits set forth in Table L.1.

Table L.1 Proposal Organization

Part B – Master Abbreviations and Acronym List

Part C – Executive Summary

Part D – Detailed Technical Proposal

NOTE: Tables of Content and dividers will not be counted in the page limitations. A page printed on both sides will count as two pages.

If a proposal volume exceeds the maximum page limits, those pages over the limit will not be evaluated or considered.

In the event of a conflict between the contents of the hard copy version of the proposal and the contents of the electronic version, the hard copy version will be the copy of record. The Offeror must provide a certification that the hard copy version of the proposal is exactly the same as the electronic version.

L.3.3 Binding and Labeling

Offerors are instructed to mark all volumes with the solicitation number. Offerors are instructed to 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 elsewhere in Section L

Each volume of the proposal must be bound together in separate three (3) ring binders. A cover sheet must be affixed to each binder, clearly marked with the Binder Label (i.e. Technical, Cost/Price, etc.), the copy number, the SIR identification, and the Offeror’s name.

The binder label and copy numbers must appear on the spine of the volume binder to permit identification when the volume is placed in a vertical position in a storage cabinet. Volumes with page counts exceeding one binder’s capacity must be identified in the following format: (i.e. Technical Proposal, Book 1, Copy X of 10; Technical Proposal, Book 2, Copy X of 10”, etc.)

Each page must contain header or footer information identifying the solicitation number, volume number, page number, and total number of volume pages.

L.3.4 Indexing

Tab indexing must be used to identify all Volumes and Sections listed in Table L.1. Each volume must be organized such that a search of FAA required documents is not necessary to review the proposal. Information not in its appropriate section and not appropriately referenced may be assumed by the FAA to have been omitted. 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 are not included in the total page count.

L.3.5 Format

No foldouts are allowed in any volume. The pages in all volumes are to be printed in Times New Roman font; no smaller than 12 point, except for footnotes which may be 10-point; on standard 8.5” by 11” paper. Margins should be at least one inch on all four sides. Printing on both sides in portrait style is preferred.

Organizational structures, implementation schedules, and plans may be depicted in charts, graphs, or tables in landscape style to provide clarity to the proposal. The type size must not be less than 12 point Times New Roman with an exception for charts, graphs or tables, which must not be less than 10 point.

L.3.6 Electronic Copies

In addition to hard copies, proposals must be submitted in electronic files on CD or DVD. Electronic copies must be formatted using Microsoft Office 2010. All files must be editable. All MS Excel files must include cell references and calculations. The electronic copies must be provide file names that are consistent with the structure of the proposal and must be marked with Offeror’s identification, SIR number, volume name(s), and volume number(s).

L.3.7 Exclude Cost/Price Information from Non-Cost Volumes

Unless specific instructions are contained within a given volume, the Offeror is instructed not to include any cost/price information in any of the volumes other than the Cost Volume.

L.3.8 Debriefing

The Offeror may request a debriefing by providing an email request to the Contracting Officer at Sharonda.Holmes@faa.gov within three (3) business days after being notified of contract award. The Contracting Officer will notify the Offeror, via email with receipt requested, of their debriefing date, time, and location. The Offeror must respond back to the Contracting Officer’s email formally acknowledging receipt. This will serve as official notification of the debriefing. The Offeror must provide any questions to the Contracting Officer, via the email above, no later than seven (7) calendar days before the Offeror’s scheduled briefing date and time.

L.4 VOLUME I – TECHNICAL PROPOSAL

L.4.1 General

Offerors are instructed to provide information for each of the sections described below in the Technical Volume. Offerors must fully substantiate the approach and demonstrate an understanding of the requirements. Technical proposals must be submitted without any reference to cost/pricing information.

The Technical Proposal must show how the Offeror's approach will comply with SIR requirements. The proposal must include explanations of the techniques and of the procedures to be followed in the proposed approach. Clarity and completeness of discussion and analysis relating to the technical approach are required. Such discussions and analysis should be oriented towards competent technical personnel who may have no prior familiarity with the specific methods of analysis and display chosen by the Offeror.

Offerors are instructed to identify risks throughout their proposal responses. Offerors must identify areas of risk associated with the described approaches and plans and must propose mitigation strategies.

L.4.2 Detailed Requirements

L.4.2.1 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.4.2.2 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.4.2.3 Part C – Executive Summary

Offerors must provide an executive summary that provides an overview of the entire technical proposal, excluding cost information. The executive summary should highlight the major areas of the proposal and provide the reader with a general understanding of the proposed approach. This section will not be evaluated.

L.4.2.4 Part D – Detailed Technical Proposal

Based on this SIR, the FAA anticipates awarding a contract under which the Contractor will be responsible for maintaining the existing system (in-service management), and for developing, integrating and deploying enhancements (solution implementation) across the system. The Offeror’s technical proposal must address in detail how the Offeror will meet the SIR requirements.

Technical Factor 1 Organization Sub-factor A -- Structure:

The proposal must describe the organizational structure and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor B -- Staffing:

The proposal must describe the key personnel qualifications and experience and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements. Resumes must be submitted for all Key Personnel identified in Section H.

Sub-factor C -- Communication & Coordination:

The proposal must describe the methods of communication and coordination, across the organization, subcontractors, teams, etc. and with Government representatives and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor D -- Resource Management:

The proposal must describe the methods for estimating, allocating and tracking personnel and other resources and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor E -- Performance Management:

The proposal must describe the methods for defining and measuring system and program performance and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Technical Factor 2: Development & Deployment Sub-factor A -- Requirements:

The proposal must describe the methods for defining and managing system and software- level requirements and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor B -- Design and Development:

The proposal must describe the methods for defining and managing system and software-level design information and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor C -- Test & Evaluation:

The proposal must describe the methods for verifying and reporting requirements compliance and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor D -- Deployment:

The proposal must describe the methods for planning, preparing for, conducting and evaluating hardware and software deployments, updates and transitions and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Technical Factor 3: In-Service Management Sub-factor A -- Monitoring & Control:

The proposal must describe the methods for monitoring and managing system performance and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor B -- User Support:

The proposal must describe the methods for responding to problems and user help requests and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor C -- Continuity of Operations:

The proposal must describe the methods for identifying and mitigating risks and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor D -- Security:

The proposal must describe the methods for meeting physical and information security requirements and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

Sub-factor E -- Lifecycle Management:

The proposal must describe the methods for managing hardware and software assets and substantiate how it is conducive to achieving a successful transition and efficient execution of the SIR requirements.

L.5 VOLUME II -- PAST EXPERIENCE AND PERFORMANCE

Information about the Offeror's past performance and past experience is being obtained to assist the Government in its evaluation of the relevance and quality of the Offeror’s past performance and past experience as it relates to the probability of successful accomplishment of this specific government requirement. This information will be obtained from two sources, 1) the Offeror will provide information about their past experience and 2) the Offeror’s customers will provide information about the Offeror’s past performance. For purposes of this SIR, “past experience” relates to services the Offeror has previously performed as a prime contractor for the government and/or private industry customers; and “past performance” information will be an assessment of how well the Offeror performed those services.

The Offeror’s past performance submission must consist of the following:

(a) Descriptions of three instances of past experience providing, currently for more than 12 months or that have been completed within the last three years, products and services of similar size, scope and complexity as compared to the requirements of this SIR;

(b) A completed “Previous Contracts List” using the format provided in Attachment J-10 that provides summary information about the three contracts the Offeror provided per paragraph (a) above; and

(c) A completed Past Performance Survey Record Form (in the format as shown per Attachment J-10 to this SIR)

All cited contracts included on the Previous Contracts List must be for work performed by the proposing organization within the Offeror’s corporate structure. For purposes of this evaluation, the more experience the Offeror has in performing services of a like and similar size, scope and complexity as the requirements described in this SIR, the better (and the more similar the environment, the better). However, do not describe more than three.

The Offeror is responsible for exerting its “best efforts” to ensure the cited customers (as noted in the Prior Contracts Contact List) submit the past performance survey form, Attachment J-10, directly to the Government’s Contracting Officer no later than the proposal submission due date. The survey respondent must be the CO and/or COR with minimum experience of one-year working on the contract.

Offerors are cautioned that failure to demonstrate “best efforts” may result in an unsatisfactory rating for this component of past performance. The Offeror must submit the "Past Performance Survey Record Form”, Attachment J-10, to document "best efforts" follow up with each customer listed on the “Previous Contracts List” (Attachment J-10__) to encourage completion and timely submission of the past performance surveys to the Government. If the Offeror does not have three different contracts which meet the criteria set forth, the Offeror shall so clearly state.

The Government may conduct follow up discussions and/or verifications with any of the people identified in the Past Performance Surveys that are submitted. The information contained in the past performance surveys will be considered sensitive and will not be released to Offerors.

L.6 VOLUME III -- COST PROPOSAL

L.6.1 General

Offerors are instructed to provide information for each of the sections described below in the Cost Volume.

The Cost Volume must be in a separate, sealed package, plainly marked "Cost Proposal." Pricing data must not be included with any other Volume and, if included within other volumes, it will be discarded and excluded from the evaluation. The government reserves the right to request other than pricing data in the review of the Cost Volume.

The pricing instructions are applicable to the prime contractor and all subcontractors. Proposed subcontractors may submit their cost proposals, separately from the prime contractor cost proposal, directly to the Contracting Officer. Offerors must submit their pricing for the total scope of the program effort across the entire contract period of performance (base period and all options) using the template provided in Attachment J-9, DOT F4220.344 Contract Pricing Summary.

Offerors must include in its price proposal:

a. all information necessary to fully address the requirements of this SIR

b. all costs elements inherent to the solution proposed in the technical proposal

c. all information relating to the proposed pricing and all required supporting documentation in the section of the proposal designated as the Cost Proposal.

Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal. The burden of proof for credibility of proposed pricing rests with the Offeror

L.6.2 Detailed Requirements – Part A of Cost Proposal

L.6.2.1 Completed SIR Section B

The Offeror must complete Tables from Section B, ‘Contract Line Item Numbers’ for the total scope of the program effort across the entire contract period of performance (base period and all options).

L.6.2.2 Complete Cost Template

In support of evaluating the total cost as described in Section M, the Offeror must complete the cost template that is provided as Attachment J-9 to this SIR.

The pricing in the cost template must match the pricing included in the completed Section B.

The FAA included hours for CLINs 6, 7, and 8 in the cost template for evaluation purposes only for the T&M CLINs. CPIF CLIN 11 sub-CLINs for the base period must be priced based on the requirements in the SIR. CLIN 11 sub-CLINs for the option period must be cost to reflect a nominal release [add description]

L.6.2.3 Complete DOF F4220.344 Contract Pricing Summary

The Offeror must complete and provide form DOT F4220.344 Contract Pricing detail for all CLINs and sub-CLINs included in the total cost calculation per the Cost Template in Attachment J-9.

L.6.2.4 Part B – Supporting Cost/Price Documentation

The Offeror must provide a basis of estimate for each CLIN/sub-CLIN, included in the total cost calculation per the Cost Template in Attachment J-9, within its proposal in sufficient detail to allow the evaluators to assess the cost/price reasonableness, cost realism, balance, and completeness/ consistency/traceability of the proposed price. Pricing must be fully supported and traceable from direct cost through application of indirect cost and fee.

The Offeror must provide existing verifiable data, the judgment factors, rationale, and methodology applied by it to project from known data to its estimate, contingencies, and assumptions used by the Offeror in its proposed pricing, which must be documented in a single table referencing the applicable proposal volume, section, and paragraph. Offeror’s must provide a matrix mapping the SOW to the proposed cost elements in their BOE. Offeror’s Cost Proposal must be consistent with its Technical Proposal.

Each basis of estimate must provide a narrative describing the rationale for the labor categories, levels, and hours proposed as well as any material and other direct costs.

Bases of estimate will be used to evaluate the Cost Proposal and will not be used in the evaluation of the Technical Proposal.

L.6.2.4.1 Detailed Narrative

Direct Labor: The Offeror must:

a) Discuss the rationale used for development of the proposed direct labor rates. If an Offeror choses to use blended rates, then the mix of labor assumed for the blended rates must match the mix of labor proposed for the CLIN.

b) If DCAA FPRA/approved bid rates were utilized, provide explanation of rate buildup and explain any differences between DCAA approved rates and proposed rates.

c) Discuss the use and rationale of escalation for direct labor.

d) Verify that its proposed rates reflect a Not-To-Exceed 40 hour workweek.

e) Include for itself, and any proposed subcontractors, the following certification as part of its cost proposal: “The proposed direct labor rates in this proposal reflects a workweek not to exceed 40 hours and does not include uncompensated overtime.” The certification must also include the name and title of the signing official.

Direct Labor Hours: The Offeror must:

a) Provide a breakdown by labor category by type and level of experience per CLIN.

b) Verify that its proposal (including subcontractor) proposes hours in accordance with SIR instructions.

c) Verify its offer does not include labor for the following administrative functions: contract administration, subcontract administration, human resources, and contract/invoice accounting.

d) Verify they have provided the applicable Section K certification relating to the treatment of the above administrative functions under the resultant contract, unless labor for administrative functions as mentioned above are verified to be in accordance with the contractor’s disclosed accounting practice.

Indirect Rates: The Offeror must:

a) Discuss the rationale used to develop each proposed indirect rate.

b) Discuss the extent that DCAA FPRA/approved indirect rates were utilized, and explain any differences between DCAA and approved rates and proposed rates.

c) Clearly explain the application of each rate.

Other Direct Costs: The Offeror must:

a) Address any proposed other direct costs, such as travel, materials, consultants, and interdivisional transfers.

b) Provide a justification/narrative of all proposed ODCs.

Fee: Offeror must address their rationale of the proposed fee structure and clearly define its fee basis.

Fair and Reasonable: The Offeror must include their analysis of the subcontractors/ consultant/ interdivisional-transfer proposal, including a determination that the proposed pricing is fair and reasonable.

L.6.2.5 Proposing fees for each of the CPIF CLINs:

The FAA will not agree to incentives wherein the proposed total possible incentive fee for a CLIN (cost, schedule and quality incentive fees combined) amounts to more than 15% of proposed target costs for that CLIN. As an example, when including incentives for all three issues (cost, schedule and quality) the following ranges have proven successful for the purpose of providing adequate incentive for each of the noted areas while limiting total possible fee to no more than 15% of proposed target cost:

Target Cost Incentive: No more than 3% of Target Costs Combined Schedule Incentives: No more than 5% of Target Costs and no less than 4% Quality Incentive: No more than 4% of Target Costs and no less than 3% Minimum Cost Incentive: $0.00 Maximum Cost Incentive: No more than 6% of Target Costs Share Ratio of 50/50, 60/40 or 70/30

Although the above information is provided in terms of “a percentage of target costs” it should be noted that each incentive for each CLIN will be specified as a dollar figure in the awarded contract. The awarded contract will NOT be a cost-plus-percentage-of-cost contract. The “percentage of target cost” language is used here simply to facilitate understanding of what may be “proposed” by the Offeror.

The ranges shown above are provided as an example of what has proven successful for previous FAA CPIF software development contracts. For this SIR, the Offerors may propose the Incentive Fees they consider appropriate so long as incentive fees are proposed for Cost Incentive, Schedule Incentive and Quality Incentive (all three) and the total combined possible incentive fee per CPIF CLIN does not exceed 15% of proposed target cost. Should an Offeror choose to propose incentive fees outside of the ranges noted above, the proposal should include a detailed explanation of the rational basis for the proposed incentive fee structure (per CLIN).

With respect to the Schedule Incentive, each development CLIN will include individual schedule milestones as shown in H.10 (Detailed Design Review, Acceptance Test, and Ready for Operations). Therefore, the proposed schedule incentive must be apportioned between these three schedule milestones.

L.6.3 – Part C - Professional Employees Compensation Plan

Pursuant to AMS Clause 3.6.2-15, Evaluation of Compensation for Professional Employees, Offerors must submit a “Professional Employees Compensation Plan.”

L.6.4 Part D – Assumptions

The Offeror must explicitly state any assumptions taken regarding the Offeror’s Cost Proposal. Each assumption must be specifically related to a specific paragraph/section of the SIR.

L.6.5 Certification of Accuracy and Consistency of Cost/Pricing Data in Proposal

Offerors are required to submit pricing information in several formats when responding to this SIR (reference SIR Sections L.6.2). By submission of their proposal in response to this SIR, the Offeror certifies that the cost/pricing data supplied is accurate and consistent between and across the various formats required for cost/pricing data submission and between the Cost Proposal and the Technical Proposal. Furthermore, the Offeror understands that they will be held liable for any discrepancies found after contract award, between the different formats for data submission and any discrepancies discovered between the Cost Proposal and the Technical Proposal. This includes the cost for conducting a new procurement should that become necessary due to discovery of any such discrepancies.

L.7 VOLUME IV – SMALL BUSINESS SUBCONTRACTING PLAN AND MENTOR

PROTÉGÉ PROGRAM DOCUMENTATION

L.7.1 Small Business Subcontracting Plan

Volume IV must address how the Offeror will assist the FAA to meet its Small Business subcontracting goals.

Offerors must provide a detailed subcontracting plan that demonstrates it will fulfill all of the requirements contained within AMS Clause 3.6.1-4, Small, Small Disadvantaged, and Women-Owned Small Business Subcontracting Plans. The subcontracting plan must identify subcontractors who meet the criteria of the North American Industry Classification System (NAICS) codes listed in Section H. Offeror’s subcontracting plans must fully address each of the eleven items set forth in AMS Clause 3.6.1-4.

The…