TSA IV 2nd Draft Section L - ITO.docx

SECTION L

Instructions, Conditions and Notices to Offerors

FOR THE

TRAINING SYSTEMS ACQUISITION (TSA) IV

Solicitation #FA8621-21-R-0030

10 November 2020

Prepared by:

Agile Combat Support Directorate, Simulators Program Office (AFLCMC/WNS) 2300 D Street, Bldg. 32 Wright-Patterson AFB, OH 45433

FA8621-21-R-0030

Section J, Attachment 9 – Section L, ITO

TABLE OF CONTENTS

Page ii TSA IV Structure and Objectives Objectives The United States Air Force (USAF) must maintain a qualitative advantage by being better trained in a multi-domain full spectrum employment that enables warfighters to interact in a highly dynamic, realistic manner to train their forces as they intend to fight. Providing a relevant and realistic initial and operational training environment is a critical step for achieving readiness and lethality for our warfighters. The Training Systems Acquisition (TSA) IV Indefinite Delivery/Indefinite Quantity (ID/IQ) contract is key to meeting this challenge.

The Simulators Division (WNS) located at Wright-Patterson Air Force Base (WPAFB), Ohio leads the development, acquisition, and sustainment efforts necessary to meet every Air Force Major Command’s (MAJCOM) simulation and training requirement. The Simulators Program Office (SPO) is responsible for end-to-end lifecycle management of Air Force (AF) training systems encompassing complex aircrew, maintenance, and system-specific training systems in support of warfighter training at operating locations worldwide. The SPO customers include AF active duty, reserve, National Guard and Department of Defense (DoD) joint warfighter, as well as Foreign Military Sales (FMS). Aircraft platforms that are supported include: fighter, bomber, cargo/airlift/tanker, unmanned aerial vehicles (UAVs), pilot training aircraft, and special operations that include helicopter platforms. Additionally, the Program Office supports non-aircraft, system-specific simulation/training requirements.

Air Force Life Cycle Management Center (AFLCMC), Agile Combat Support Directorate, Simulators Division (AFLCMC/WNS) plans to competitively award multiple TSA IV ID/IQ contracts to streamline and standardize training system acquisition and support procurement processes. This acquisition will utilize the FAR 15 Source Selection Process to conduct a partial set-aside competition targeting a range of 10-15 awards in an Unrestricted Pool and a competition targeting a range of 10-15 awards reserved for small business (e.g., Small Business Pool). The Government reserves the right to award more or fewer ID/IQ contracts than indicated in the range above, or to award no contracts at all, if the Source Selection Authority (SSA) determines it is in the Government’s best interest. Offerors must identify whether they will be competing in the unrestricted or small business set-aside pool. Offerors may only submit a proposal for one of the two pools for initial contract award. Unrestricted task orders will be available for competition for all prime TSA IV contract holders while other task orders will be set-aside for those in the TSA IV Small Business Pool.

Only U.S. companies may be considered for award. A foreign-owned or foreign-influenced company that has been approved through the Defense Security Service (DSS) as a U.S. subsidiary may also be considered as a U.S. prime on TSA IV. Foreign-owned companies may participate as a subcontractor on TSA IV task orders.

Approach TSA IV will establish a flexible and responsive capability to meet our customers’ training systems needs by providing a base of pre-qualified contractors who can be rapidly accessed through both competitive and noncompetitive methods, as appropriate, to provide the required products and services described in the TSA IV Statement of Objectives (SOO). Each task order will specifically define the work to be performed by the contractor.

Offerors are advised that the Government will evaluate technical acceptability and past performance for prime offerors only. Note: if the prime offeror is a joint venture, the Government will evaluate technical acceptability and past performance for that joint venture and its partners. Prime ID/IQ holders will be able to form subcontracting teams as necessary at the task order level, including with entities who do not hold TSA IV ID/IQ contracts.

The ordering period for TSA IV is 10 years. The ordering period is defined as the time period that task orders can be issued under this contract. The ordering period is broken out as follows: a 5-year base, plus one 2-year option and one 3-year option, if exercised.

The Government intends to award basic ID/IQ TSA IV contracts that will allow for a variety of contract types, including but not limited to, Firm-Fixed Price (FFP), Fixed Price Incentive Firm (FPIF), Fixed Price Level of Effort (FP-LOE), Cost Plus Fixed Fee (CPFF), Cost Plus Incentive Fee (CPIF), and Cost Reimbursable No Fee (CRNF). Applicable contract type contract line item numbers (CLINs) will be specified on each individual task order.

In accordance with FAR 52.216-19, the stated “minimum order amount” of $1,000 will be obligated via orders issued after announcement of successful offerors. Offerors must receive a basic contract award to be eligible to receive a task order award. The minimum amount identified on the contracts represents the only funding liabilities for the Government against the basic contracts. Task orders issued under these contracts will be incrementally or fully funded in accordance with (IAW) federal appropriations law. The aggregate ceiling of the TSA IV program is $32.5B.

Proposal Preparation Instructions This section of the ITO provides general guidance for preparing proposals, as well as specific instructions on the format and content of the proposal. Offerors are required to submit one proposal with sufficient information concerning all factors to enable Government personnel to fully ascertain the offeror’s capabilities to perform the requirements. The offeror’s proposal must include all data and information requested by the ITO and must be submitted IAW these instructions. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Alternate proposals are not acceptable. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation and may render the proposal unawardable.

The proposal shall be clear and concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and that the Government will base its evaluation on the information presented in the offeror’s proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

Offerors are advised that the costs of any response to or otherwise incurred as a result of responding to this proposal request are not chargeable to this proposal effort.

The proposal acceptance period is specified in Section A of the model contract/ solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid until the date specified in Section A of the model contract/solicitation.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one digital copy of all unsuccessful proposals. The Government will not return any proposals and will destroy any additional digital or printed copies of proposals.

General Information Point of Contact (POC) The Contracting Officer (CO), Steve Godby, (937) 713-2731, e-mail: steven.godby@us.af.mil and Contract Specialist, Marcia Hall, (937) 656-8265, e-mail: marcia.hall@us.af.mil are the exclusive POCs for this acquisition. Written questions or requests for clarification may be sent via email to these individuals. It is encouraged that any such questions or requests be submitted within 10 days after the RFP release date. Answers to such questions and clarifications will be provided via posting questions and answers (Q&As) and/or RFP amendments on the betaSAM website (https://beta.sam.gov). In the event of conflict between the answer to questions and the RFP, the RFP shall take precedence.

Debriefings The CO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to receive their debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing and must make their request within three days after being notified that they have been excluded from the competition.

The CO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.506.

Discrepancies If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale, as well as, the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right, and it is the Government’s intent, to award this effort based on the initial proposal, as received, without discussions.

Electronic Reference Documents All referenced documents for this solicitation are available on the betaSAM website (https://beta.sam.gov). Potential offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation. The TSA IV solicitation web page is: https://beta.sam.gov/opp/20d7dbc5eacc4ed685510259e68bc8ec/view?keywords=%22TSA%20IV%22&sort=-relevance&index=&is_active=true&page=1.

Communications Exchanges of source selection information between the Government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104 – Controlled Unclassified Information (CUI)” in the Subject line. Otherwise, source selection information will be transmitted via DoD SAFE (https://safe.apps.mil/) or made available for pick-up by a local representative.

Organization/Number of Copies/Page Limits The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits as specified in the table. The contents of each proposal volume are described in the ITO paragraph as noted in the following table.

· Attachment 1: Systems Engineering Management Plan

· Attachment 2: Configuration Management Plan

· Attachment 3: Risk Management Plan (RMP)

· Attachment 4: Quality Assurance Program Plan (QAPP) 25 pages maximum per plan (not included in 30-page Technical Volume maximum)

20 pages maximum to allow for introductory information, including Business Relationship page.

· Attachment 1: Small Business Subcontracting Plan (SBSP) (large business offerors only) No page limit

· SBSP – no page limit

Page Limitations Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Offerors will be notified of any excess page count. Each page shall be counted, except as indicated in the paragraphs below. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

Classified Information No classified information is required or permitted in the offeror’s response.

Cross Referencing To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. The offeror shall complete the cross-reference matrix located at Section L Attachment 1, which correlates the RFP with the offeror’s proposal, for Volume II only. The offeror may prepare a cross-reference matrix in another format as long as it adheres to these instructions. The cross-reference matrix will reference the Proposal Volume/Paragraph and applicable SOO, Section L, and Section M paragraphs. The matrix will not be included in the volume page count.

If this matrix conflicts with any other requirement, direction, or provision of this proposal request, the other reference shall take precedence over this matrix. Additionally, to the extent this matrix discloses details as to the manner by which the Government intends to evaluate the offeror’s proposal for award, evaluation factor references in the matrix are for information purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of the evaluation criteria in Section M (RFP Attachment 11) of the RFP.

Indexing Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tables of contents do not count against the page limitations for their respective volumes. Tab indexing shall be used to identify sections and do not count against the page limitations for their respective volumes.

Glossary of Abbreviations and Acronyms Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

Marking All proposal pages shall include the following legend at the bottom of each page:

SOURCE SELECTION INFORMATION

CONTROLLED UNCLASSIFIED INFORMATION

See FAR 3.104 and 2.101 Page Size and Format Page size shall be 8.5 x 11 inches. Pages shall be single-spaced as defined in paragraph settings/spacing in Microsoft Word, with a double space between paragraphs. Except for the reproduced sections of the proposal request document, the text size shall be no less than 12-point Times New Roman. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs.

Legible tables, charts, graphs, figures, diagrams, and schematics shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and legible and shall not exceed 11x17 inches in size and shall be counted as two pages. For these displays, the text shall be no smaller than 10-point. Transmittal letters will not be considered in the overall page count nor will they be evaluated.

Electronic Offers Submit proposal Volumes I, II, and IV on a single CD-R/DVD-R. Submit Volume III, Past Performance on a separate CD-R/DVD-R. Offerors shall also submit all proposal volumes via DoD SAFE (https://safe.apps.mil/). No hard copies of proposals will be accepted. Each volume shall be in separate directories on the CD-R/DVD-R. Use separate files to permit rapid location of all portions, including exhibits, annexes, addenda, and attachments, if any. If files are compressed, the necessary decompression application must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 2010 or later. Offerors may also submit the proposal in Adobe Acrobat 9.0 or later. Do NOT submit any documents in PDF format that are copied as “images”. When creating PDF files always submit with textual search and copy functions enabled.

The file-naming convention for the proposal volumes is as follows. It is permissible to expand on these file names if a list of the content of each is provided. It is permissible to shorten these file names as long as the Volume number and title, Factor/Subfactor number, and a keyword or phrase is utilized to ensure clarity and consistency.

Proposal Submission The offeror’s proposal shall be prepared and submitted in four volumes: Executive Summary (Volume I), Technical Acceptability (Volume II), Past Performance (Volume III), and Contract Documentation (Volume IV). All volumes must be received via electronic media (CDR/DVD-R). Proposals shall be sent to the Contracting Officer at the address below:

AFLCMC/AZ

ATTN: Mr. Steve Godby (TSA IV Acquisition) 1755 Eleventh Street Building 570, Room 218 Wright-Patterson AFB OH 45433 Deadlines Offerors are requested to submit Volume III, Past Performance by XX February 2021. Failure to submit Volume III by the earlier date will not result in offeror disqualification. All remaining TSA IV proposal volumes must be received by 1500 EST on XX March 2021.

Volume I Executive Summary In the Executive Summary Volume, the offeror shall provide the following information.

Narrative Summary A concise narrative summary of the entire proposal and a highlight of any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

Within this volume, offerors need to identify if they will be competing in the unrestricted pool or small business set-aside pool. Also, within this volume, offerors shall identify if they are submitting a proposal as a joint venture. The joint venture partners shall be identified. Offerors shall include a copy of the joint venture partnership agreement as an attachment to Volume I. This agreement will not be included in the 5-page limit.

Table of Contents A master table of contents of the entire proposal (Volumes I through IV).

Volume II – Technical Acceptability General The Technical Acceptability Volume is limited to 30 pages. In this volume, address your proposed approach/process to meeting the requirements of each Technical subfactor. The Technical Acceptability Volume should be specific and complete. Legibility, clarity, brevity, and coherence are important. Your proposal will be evaluated against the Technical Factor as defined in Section M, Evaluation Factors for Award. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

Volume II Organization The Technical Acceptability Volume shall be organized according to the following general outline:

Table of Contents (not included in the 30-page limit) List of Table and Drawings (not included in the 30-page limit) Glossary (not included in the 30-page limit) Cross Reference Matrix (not included in the 30-page limit) Factor 1: Technical

· Subfactor 1: Engineering and Innovation

· Subfactor 2: Sustainment

· Subfactor 3: Courseware Development/Instruction

· Subfactor 4: Program Management Attachment 1: Systems Engineering Management Plan (SEMP) (25-page limit inclusive of TOC, acronyms, etc. Not included in the 30-page Volume limit) Attachment 2: Configuration Management Plan (CMP) (25-page limit inclusive of TOC, acronyms, etc. Not included in the 30-page Volume limit) Attachment 3: Risk Management Plan (RMP) (25-page limit inclusive of TOC, acronyms, etc. Not included in the 30-page Volume limit) Attachment 4: Quality Assurance Program Plan (QAPP) (25-page limit inclusive of TOC, acronyms, etc. Not included in the 30-page Volume limit) Note: The plans within Attachments 1 through 4 will become Master Plans and attached to the awarded TSA IV contracts. These master plans may be updated, as necessary, on individual task orders.

Technical Subfactors Subfactor 1: Engineering and Innovation The offeror shall submit the following processes for engineering and innovation to deliver modifications to training systems to maintain concurrency with the aircraft to include integrating new technologies. In addition, the offeror shall identify any risk (if any) associated with the proposed processes for this subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks.

a. Systems Engineering: Provide a SEMP, prepared IAW Data Item Description (DID) DI-SESS-81785A (Section L Attachment 2) that describes the offeror’s processes which will be applied to tasks executed under the TSA IV contract. The SEMP shall address the offeror's technical processes and technical management processes, as well as adoption and application of emerging Systems Engineering initiatives and practices. The Simulators Division’s Organizational Systems Engineering Plan (OSEP) is provided as Section L Attachment 3 to assist in developing the SEMP. (SOO paragraph 4.2)

b. Configuration Management (CM) and Control: Provide a CMP IAW DI-SESS-80858D (Section L Attachment 4) that describes the offeror’s approach to implement and maintain CM and change control processes throughout the training system/device lifecycle, to include management of multiple/overlapping baselines when necessary. The CMP shall address processes to transition modifications from a development baseline into a training baseline. The CMP shall describe the offeror’s change control processes and the tools that will be used to maintain CM for a training system. The Agile Combat Support (ACS) Directorate CMP is provided as Section L Attachment 5 to assist in developing the offeror’s CMP. (SOO paragraph 4.13)

c. Concurrency Modifications: Describe the offeror’s change management process to identify, track, and implement modifications into the training system as a result of maintaining concurrency with the aircraft, trainer-unique changes, sustainability issues, obsolescence, and technology improvement including the offeror’s process for identifying, obtaining, and controlling source data needed to perform contract requirements. In addition, provide innovative concepts the offeror would apply to training system concurrency. (SOO paragraph 4.14 and 5)

d. Integration: Describe the offeror’s process or identifying, evaluating, and integrating beneficial new technologies into the Air Force Simulator environment, generally across two or more “families” of simulators, to improve performance, reduce cost, or enhance lifecycle supportability. (SOO paragraph 4.6) Subfactor 2: Sustainment The offeror shall submit the following processes for Training System Support Center (TSSC) operations and Contractor Logistics Support (CLS), to include Distributed Mission Operations (DMO) and Diminishing Manufacturing Sources and Materiel Shortages (DMS/MS). In addition, the offeror shall identify any risk (if any) associated with the proposed processes for this subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks.

a. TSSC: Describe the offeror’s process for TSSC operations, responsibilities, and interaction with development teams. Include the offeror’s process to augment the technical staff to flex and meet greater TSSC demands. (SOO paragraph 6.3)

b. CLS: Describe the offeror’s process for managing the support resources, technical data, spares, support equipment, maintenance, Government-Furnished Property (GFP) accountability, device status reporting, student throughput, and technicians to sustain training systems and ensure normal and surge trainer availability requirements. (SOO paragraph 6.1)

c. DMO: Describe offeror’s process for executing DMO requirements, to include resource allocation, scheduling, coordination, establishing connectivity for pre-mission briefings, mission execution, post-mission debriefing activities, and security. (SOO paragraph 6.2)

d. DMS/MS: Describe the offeror’s process for forecasting, identifying, monitoring, and mitigating deficiencies due to obsolescence and DMS/MS issues within the training system. (SOO paragraph 5) Subfactor 3: Courseware Development/Instruction The offeror shall submit the following processes for training system courseware development and instruction. (SOO paragraph 6.4) In addition, the offeror shall identify any risk (if any) associated with the proposed processes for this subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks.

a. Courseware Development: Describe the offeror’s process for the development and planning for lifecycle sustainment of computer-based training products for training systems. Include a description of how the offeror implements levels of complexity/interaction, Sharable Content Object Reference Model (SCORM) or equivalent compliance, Commercial Off-The-Shelf (COTS)/Government Off-The-Shelf (GOTS) tools, and validation programs.

b. Student Instruction: Describe the offeror’s process for meeting student instruction requirements and student throughput requirements including when surge requirements may occur, and address changes in class sizes and course lengths over the life of the program. Include the offeror’s process for hiring, training, and qualifying instructor workforce without impacting student throughput.

c. Training Management: Describe the offeror’s process to operate and maintain a training management system and process for analyzing and reporting student data to improve or enhance student performance. Also include the offeror’s approach for flexibility of providing instruction (e.g., adaptive types of training, Pilot Training NEXT, virtual instruction [e.g., virtual reality (VR)/augmented reality (AR), etc.]). Describe how different technologies could be applied to address learning objectives, within the overall context of instructional program objectives.

Subfactor 4: Program Management The offeror shall submit the following processes for managing and executing tasks under the TSA IV contract. In addition, the offeror shall identify any risk (if any) associated with the proposed processes for this subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks.

Program Management: Describe the offeror’s program management approach that includes: (SOO paragraphs 4.1 and 4.10 with its subparagraphs)

· Organizational structure of a management integrated product team that will be prevalent for a TSA IV task order. Describe methods that will be used for providing stakeholder insight to program data and status.

· Program review procedures and requirements including definition of required participants, completion criteria and review content, and action item resolution.

· Process for selecting and managing subcontractors. In addition, offerors shall also provide its process for how it will meet the 20% small business participation task order requirement IAW Section H Clause TSA IV-HXX.

· Process for obtaining appropriate facility and personnel security clearances and approvals. Describe offeror’s current security classification and how the offeror will apply available resources to accomplish facility upgrades and obtain security approvals when needed for tasks at higher levels of classification.

· Process for maintaining sufficient cybersecurity certified personnel and obtaining and maintaining an Authority to Operate (ATO)

· Recruitment process (incentives and benefits) for acquiring and retaining qualified personnel, and continued education/training. The Offeror shall describe its process to continue contract performance in the case of a labor dispute.

Risk Management: Provide a RMP IAW DI-MGMT-81808 (Section L Attachment 6) that describes the offeror’s risk management system and associated tools and processes, and how the risk management system will be applied to improve program performance. In addition, the offeror shall identify any risk (if any) associated with the proposed processes/approaches for each subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks. (SOO paragraphs 4.1 and 4.10.1) Quality Assurance: Provide a QAPP IAW DI-QCIC-81794A (Section L Attachment 7) that describe the offeror’s process for implementing a quality management system that addresses the offeror’s accountability for contract requirements. (SOO paragraph 12 and subparagraphs) Volume III –Past Performance General Each offeror shall submit a Past Performance Volume containing relevant past performance information on contracts which have had at least six months of performance within the last five years and are either active or have been completed within five years preceding the date of this solicitation. Past performance information shall be provided using the Past Performance Information Tool as described in Section L Attachment 8, for each referenced contract. In addition to the data provided in this volume, the Government may use the Contractor Performance Assessment Reporting System (CPARS) and/or similar systems of other Government departments and agencies, questionnaires tailored to the circumstances of this acquisition, Defense Contract Management Agency (DCMA) channels, interviews with program managers and COs, and other sources known to the Government, including commercial sources.

The Business Relationships page generated from the Past Performance Information Tool is counted within the Introductory Information in the Past Performance Volume.

Offerors shall send a Past Performance Questionnaire (Section L, Attachment 9) directly to the POCs for the efforts identified. All respondents shall be instructed that all responses are to be provided directly to the Government CO (Steve Godby, steven.godby@us.af.mil) or Contract Specialist (Marcia Hall, marcia.hall@us.af.mil) not later than XX March 2021. Offerors shall provide a listing of the individuals to whom the questionnaires were sent with contact information (name, phone, email, etc.). This is needed in case the Government has to follow-up with any POCs for questionnaires not received. This listing is excluded from the volume page count.

For each identified effort for a commercial customer, the offeror shall also submit a Client Authorization Letter (Section L, Attachment 10), authorizing release to the Government of requested information on the offeror’s performance.

Specific Content As discussed in paragraph 1.1 above, only U. S. companies will be considered for award as a prime TSA IV contract holder. If a foreign-influenced company has been approved through the DSS as a U.S. subsidiary, then they are considered a U.S. company and may be a U.S. prime on TSA IV. However, in order for past performance to be considered relevant, the contract reference must have been performed by the U.S. Company submitting the proposal. A foreign parent company is not the offeror, so the foreign parent company’s past performance will not be considered relevant to what the U.S. subsidiary is proposing to do. In addition, in order for past performance to be considered relevant for the prime offeror, it is the Government’s intention to only evaluate the prime offeror submitting the proposal and not its parent/affiliate companies.

Offerors are required to explain what aspects of contracts are deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate. Provide a list of past performance information of no more than three of the most relevant contracts which have at least six months of performance and are either active or have been completed for Federal agencies and/or commercial customers within five years preceding the date of this solicitation. If an offeror is submitting a proposal as a joint venture, past performance information is required from that joint venture. This information may be from work performed as the joint venture or from one or more of the companies that formed the joint venture as long as the total number of contracts submitted does not exceed three.

Using the Past Performance Information Tool, explain how your performance is relevant to Technical Subfactors 1 through 4 for aircraft training systems. Aircraft training systems includes aircrew, maintenance, mission/DMO, part task trainers, Live Virtual Constructive (LVC); as well as air traffic control; etc., for Federal agencies and commercial customers. Specifically describe and compare the type of work and scope of effort (including number of sites and trainers). Past performance will be rated for each Technical Subfactor, with the order of importance for the subfactors in descending order with Subfactor 1 being the most important.

The offeror may include a discussion of efforts accomplished by the offeror to resolve problems encountered on the submitted contracts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly describe management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate.

Organizational Structure Change History Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a “roadmap” describing all such changes in the organization of your company within the past five years. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government may consider past performance information provided by other sources, as well as that provided by the offeror; your “roadmap” should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

Volume IV Contract Documentation Model Contract/Representations and Certifications The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror’s proposal shall include a signed digital copy of the Model Contract, and Sections A through K.

Section A - Solicitation/Contract Form Completion of blocks 13 through 16, signature for block 17, and date for block 18 of the Standard Form 33 is required. Signature by the offeror on the SF33 constitutes an offer, which the Government may accept. The “original” signed copy should be clearly marked.

Section B - Supplies or Services The offeror shall not complete Section B. The contract clauses pertinent to this section and that are required to be filled-in will be completed on each individual task order.

Section C - Description/Specifications/Work Statement The contract clauses pertinent to this section are contained in Section C of the solicitation. There are no clauses within Section C requiring fill-ins.

Section E - Inspection and Acceptance The contract clauses pertinent to this section and that are required to be filled-in will be completed in Section E of each individual task order.

Section F - Deliveries or Performance The contract clauses pertinent to this section and that are required to be filled-in will be completed in Section F of each individual task order.

Section G - Contract Administrative Data Upon Award, Section G data will be provided by the Government.

Section H - Special Order Requirements The contract clauses pertinent to this section and that are required to be filled-in will be completed in Section H of each individual task order.

Section I - Order Clauses The contract clauses pertinent to this section and that are required to be filled-in will be completed in Section I of each individual task order.

Section J – Attachments The following Section J attachments will be included as part of the TSA IV contract:

Attachment 1, SOO Attachment 2, DD 254 Attachment 3, Quality Assurance Surveillance Plan (QASP) The following attachments will be added to the contract after contract award:

Attachment 4, Systems Engineering Management Plan (SEMP) Attachment 5, Configuration Management Plan (CMP) Attachment 6, Risk Management Plan (RMP) Attachment 7, Quality Assurance Program Plan (QAPP) Attachment 8, Small Business Subcontracting Plan (SBSP) (large businesses only) Note: Large business offerors are to submit their SBSP as an attachment to Volume IV.

Section K - Representations, Certifications, and other Statements of Offerors The offeror’s completed representations, certifications, acknowledgements, and statements shall be submitted IAW FAR 52.204-8 “Annual Representations and Certifications.”

Exceptions to Terms and Conditions Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall specifically identify each paragraph and/or specific part of the solicitation to which the exception is taken. As stated in paragraph 2, above, non-compliance with any solicitation requirement, including exceptions the Government deems unacceptable, may render a proposal unawardable. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the following format.

Page Requirement/ Portion Rationale

Other Information Required Authorized Offeror Personnel Provide the name, title, email, and telephone number of the company/division POC authorized to negotiate with the Government and who can obligate your company contractually. Also, provide the name, title, email, and telephone number of the CEO, Division President, and/or Vice President.

Government Offices Provide the mailing address, email, telephone and fax numbers, and facility codes for the cognizant DCMA, DCAA, and Government Paying Office. Also, provide the name, email, and telephone number for the Administrative Contracting Officer (ACO).

Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division’s street address, county and facility code; CAGE code; DUNS code; size of business (large or small); and labor surplus area designation.

Non-Government Advisors Offerors are advised that contractors will participate as non-Government advisors in the evaluation of proposals. These advisors will sign non-disclosure agreements and will be authorized access to only those portions of the proposal data and discussions that are necessary to enable them to provide specific advice on specialized matters or on particular problems. The non-Government advisors will not determine or establish initial or final assessments of offeror’s proposals. The non-Government advisors will not have access to Past Performance Information. They will have access to offeror proprietary, confidential, or privileged commercial data. The non-Government advisor support will be provided by:

PESystems POC: Maurice “Mo” McDonald 5100 Springfield Street, Suite 400 Dayton, Ohio 45431-1251 maurice.mcdonald@pesystems.com Office: (937) 425-0321 Cell: (937) 903-3005 Offerors shall provide, in the Contract Documentation Volume, a copy of paragraph (2) below or provide written objection to disclosure as indicated in paragraph (1). If the offeror objects to disclosure of a portion of the proposal, the consenting paragraph (2) shall be provided for the remainder of the proposal.

1. Any objection to disclosure:

i. Shall be provided in writing to the Contracting Officer within the Contract Documentation Volume of the proposal; and

ii. Shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the Offeror objects to disclosure to non-Government advisors.

2. I understand that proprietary, confidential, or privileged commercial data submitted to the Government in response to this solicitation may be released to non-Government advisors. I consent to the release of any (unless objection is provided in (1) above) proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-Government advisors for review and analysis:

Signature: Firm:

Name (individual authorized to commit firm):

Title:

Date of Execution:

The CO will evaluate any objection to disclosure and make a determination whether the non-Government advisor(s) shall be permitted to participate in the source selection. The CO shall inform the objecting offeror of the final determination, and, if the use of non-Government advisors has been changed, shall inform all offerors of the change.

Small Business Subcontracting Plan (SBSP) Large businesses shall submit, on a plant or division-wide basis, a SBSP (see FAR 19.701) that contains all the elements required by the clause at FAR 52.219-9, Small Business Subcontracting Plan. The SBSP shall be submitted as part of Volume IV and has no page limit. The SBSP shall include the subcontracting goals expressed at the ID/IQ contract level as a percentage of annual total obligated dollars on awarded task orders for each of the following: small business, veteran-owned small business, service-disabled veteran owned small business, HUBZone small business, small disadvantaged business, and women owned small business. The SBSP shall also describe the offeror’s approach to meeting each of its subcontracting goals.

A plan, when incorporated in an individual contract, shall apply to that contract throughout the life of the contract. Although plans shall be effective for the life of the contract after approval by the contracting officer, it is incumbent upon contractors to maintain and update plans to include goals each time they win a task order award. Changes required to update plans are not effective until approved by the contracting officer. Failure to submit an acceptable plan may make the offeror’s proposal un-awardable. A contractor’s comprehensive SBSP and its successors, which are authorized by and approved under the test program of Section 834 of Pub. L. 101-189, as amended, may be submitted in lieu of the SBSP described above.