Atchm_12_B-52_TS_Section_L_3Apr15.pdf

FA8621-15-R-6338

Attachment 12 - Section L 30 March 2015

SECTION L

INSTRUCTIONS TO OFFERORS

FOR THE

B-52 TRAINING SYSTEMS

SECTION L

Instructions to Offerors (ITO)

L-I INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR

PROPOSAL PREPARATION

1.0 Program Description

1.1 The efforts anticipated under the resultant contract include the operations, maintenance, and sustainment support for the B-52 Training Systems. Specifically, these efforts include Contractor Logistics Support (CLS) and Training System Support Center (TSSC) services for the Aircrew Training Devices (ATDs); concurrency and fidelity upgrades for ATDs and Maintenance Training Devices (MTDs); development, production, and fielding of new ATDs and MTDs, as required; contract transition activities; and ATD and MTD studies and analysis efforts, as required.

1.2 This is a follow-on services acquisition and will be competitively awarded to a small business. The contract period of performance includes a maximum four (4) month transition period, 4 years of CLS (one year base, plus three 1-year options), 8 years of TSSC services (one year base, plus seven 1-year options), 8 years of modifications for concurrency and fidelity upgrades, and 8 years for acquisition of new devices.

Table 1.2 Tentative Contract Timeline

2.0 General Instructions

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.

2.1 General Information

2.1.1 The proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the B-52 Training Systems Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation and deemed nonresponsive.

2.1.2 These instructions prescribe the format of proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of information essential to the understanding and comprehensive validation of proposals. The instructions permit the inclusion of any additional data or information an offeror deems pertinent. Offerors are cautioned to follow the detailed instructions fully and carefully, as the Government intends to make an award based on initial offers received, without discussion of such offers. The Government may make a final determination regarding acceptability solely on the basis of the proposal as submitted without requesting any further information. However, if deemed necessary, and at its sole discretion, the Government may request additional information from offerors clarifying or supplementing, but not substantially changing, any proposal submitted.

2.1.3 The proposal shall be clear, concise, and shall include a level of detail which allows for an effective evaluation and substantiation of the validity of the offerors assertions. 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 will therefore base its evaluation only on the information presented in the proposal.

2.1.4 Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

2.1.5 The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in the proposal documentation volume that the proposal is valid for 270 days from the closing date for receipt of proposals.

2.1.6 In accordance with Federal Acquisition Regulation (FAR) Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.1.7 North American Industry Classification System (NAICS) code The NAICS code for this acquisition is 336413 and size standard is <1000 employees.

2.1.8 System for Award Management (SAM)

Contractors will not be eligible to receive a contract award from a Department of Defense (DoD) activity unless they are registered in SAM. Contractors shall be registered in the DoD SAM Database prior to award of any contract, basic agreement, basic ordering agreement, or blanket purchase agreement in accordance with FAR 52.204-7. Firms must register on a one-time basis and annually confirm accuracy and completeness of registration information. On-line registration and instructions can be accessed at https://www.sam.gov.

2.1.9 Data Universal Numbering System (DUNS) Number

DUNS Number applies to offers exceeding $25,000. The offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation “DUNS” followed by the DUNS number that identifies the offeror’s name and address. If the offeror does not have a DUNS number, Dun and Bradstreet should be contacted to obtain one at no charge. An offeror within the United States may call 1-800-333-0505. The offeror may obtain more information regarding the DUNS number, including locations of local Dun and Bradstreet Information Services offices for offerors located outside the United States, from the internet homepage at http://www.dnb.com/. If an offeror is unable to locate a local service center, an email may be sent to Dun and Bradstreet at custserv@dnb.com.

2.1.10 Point of Contact

The Contracting Officer (CO), Mr. David Moorhead, (937), 255-0897 e-mail:

david.moorhead@us.af.mil and Contract Negotiator/Buyer, Ms. Rebecca Johnson, (937) 255- 3905, e-mail: rebecca.johnson.19@us.af.mil are the exclusive Points of Contact (POC) 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 of the Request for Proposal (RFP) release date. Answers to such questions and clarifications will be provided to all offerors by posting questions and answers on the B-52 Training Systems Support solicitation on Federal Business Opportunities (FBO) https://www.fbo.gov/spg/USAF/AFMC/ASC/FA8621-15-R-6338/listing.html. In the event of conflict between the answer to any questions and the RFP, the RFP shall take precedence.

2.1.11 Debriefings

The Government may exclude a proposal from this competition prior to discussions or competitive range determination without evaluating the proposal against the Evaluation Factors as defined in Section M, if an initial assessment of the proposal shows the proposal to be grossly deficient. Grossly deficient proposals are proposals that fail to address essential requirements of the solicitation, or fail to furnish information demonstrating compliance with mandatory solicitation requirements set forth in the solicitation, or in some other manner do not represent a reasonable initial effort by the offeror to address the requirements of the solicitation.

The Government retains the right, at any time during the evaluation process, to exclude a proposal from further consideration, without allowing the offeror an opportunity to revise its proposal, if that proposal is found to be grossly deficient.

The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with 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 request a post-award debriefing.

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

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

2.1.13 Electronic Reference Documents

All referenced documents for this solicitation are available on the FBO website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The B-52 Training Systems Support solicitation FBO webpage is:

https://www.fbo.gov/spg/USAF/AFMC/ASC/FA8621-15-R-6338/listing.html

2.1.14 Communications

Exchanges of source selection information between 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” in the Subject line. Otherwise, source selection information will be transmitted via USPS or pick-up and delivery by a local representative. In order to facilitate the sending and receiving of encrypted emails, offerors must use Microsoft (MS) Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit source selection information via encrypted email, you will need to contact the CO indicated on the face page of the solicitation prior to that first submittal in order to exchange Public Key Infrastructure credentials.

2.1.15 Notice to Offerors Regarding Funds Availability

Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to hold in abeyance this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

2.2 Proposal Preparation Instructions:

2.2.1 Proposal Format: These instructions prescribe the format of proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of information essential to the understanding and comprehensive validation of proposals. The instructions permit the inclusion of any additional data or information an offeror deems pertinent within the page limitations specified herein.

2.2.1.1 The Government may make a final determination regarding acceptability solely based on the proposal as submitted without requesting any further information. However, if deemed necessary, and at its sole discretion, the Government may request additional information from offerors clarifying, but not changing, any proposal submitted.

2.2.1.2 At any time during this competition if the CO determines that adequate price competition no longer exists, offerors may be required to submit information to the extent necessary for the CO to determine the reasonableness of the price.

2.3 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization table (Table 2.3 below). The titles and contents of the volumes shall be as defined in Table 2.3, all of which shall be within the required page limits and with the number of copies as specified. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

VOLUME ITO

Paragraph Number

VOLUME TITLE PAGE LIMIT # SOFT

COPIES

# HARD

COPIES

I 3.0 Executive Summary 10 2 8 II 4.0 Technical Capability 200 2 8 III 5.0 Past Performance 5 pages per contract (plus 5 pages for information explaining organizational changes) Total: 35

2 4

IV 6.0 Price Unlimited 3 4 V 7.0 Contract Documentation Unlimited 2 4

Table 2.3 Proposal Organization

Multi-media video files (e.g. Quick Time, Windows Media Player, Real Player, .avi, .mpeg, etc.) will not be accepted as part of any proposal submission and will be destroyed without review if received as part of a submission.

2.3.1 Page Limitations

Page limitations shall be treated as maximums. The page count in the paper version of the proposal must match the electronic page count. If exceeded, the excess pages will be removed from the back of the volume and not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Each page shall be counted except as described in subparagraphs below. Line 1.5 spacing is not required in tables, charts, graphs, call-out boxes and figures. Page limitations also 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.

2.3.1.1 Page Size and Format

Page size and format shall be consistent throughout the submission. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be typed with 1.5 line spacing, to include spacing between paragraphs.

Except for the reproduced sections of the solicitation document, the text shall be no less than 12 point and in Times New Roman font.

Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. At least 1-inch margins on the top and bottom and ¾-inch side margins shall be used. Pages shall be numbered sequentially by volume. These page size and format restrictions shall also apply to responses to Engineering Notices. These limitations shall apply to both electronic and hard copy proposals.

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and may only be used for large tables, charts (including schedules), graphs, diagrams and schematics; not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8point and in Times New Roman font. Transmittal letters will not be considered in the overall page count nor will they be evaluated. These limitations shall apply to both electronic and hard copy proposals

2.3.2 Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Price and Contract Documentation Volumes IV and V. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

2.3.3 Classified Information

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

2.3.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume or cross-referenced will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall complete the Proposal Traceability Matrix (PTM, Appendix L-6), indicating the Proposal Volume II reference information as it relates to the ITO (Section L), Evaluation Factors for Award (Section M), and the PWS references found therein. The PTM will only cross-reference the Proposal Volume II paragraphs to the applicable Section L, Section M, and PWS paragraphs, and WILL NOT be included in the Volume II page count.

The matrix is a management tool for both the offeror and government to ensure that no requirement is overlooked and therefore is not for evaluation purposes. Data in the PTM will not be evaluated in accordance with Section M.

2.3.5 Indexing

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. The Cover page, PTM, Definitions, Table of Tables, and Table of Figures pages DO NOT count against the page limitations for their respective volumes.

2.3.6 Glossary of Abbreviations and Acronyms

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

2.3.7 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. All “original” submissions of each volume shall be 2-hole punched at the top of each page and bound with a rubber band. Do not submit original volumes in a three-ring binder.

A cover sheet (which does not count against the page limitations for its respective volume) shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, the offeror's name, and submission date. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors (e.g. blue). Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. All material shall include the following information located in the footer of each page:

SOURCE SELECTION INFORMATION FOR OFFICIAL USE ONLY –

See FAR 2.101 and FAR 3.104

2.4 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies of the proposal submitted. Electronic storage media shall be submitted in one of the following formats: on virus-free CD-R or DVD-R. The Government will not accept any proposal submitted through any media in rewriteable format (i.e. flash drive or CD-RW) media. For electronic copies, indicate on the disc the offeror name, volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. Each volume shall be on a different CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by MS Office Word 2010 (*.docx), MS Office Excel 2010 (*.xlsx), MS Office Project 2010 (*.mpp), and MS Office Power Point 2010 (*.pptx), or Adobe Acrobat 9.0 or later, as applicable. Do not submit any documents in Portable Document Format

(PDF) format that are copied as “images”. Always create PDF files to enable textual search and copy functions. All documents must be editable and not password protected. In the event that there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.5 Proposal Submission

The offeror’s proposal shall be prepared and submitted in five volumes: Executive Summary (Volume I), Technical Acceptability (Volume II), Past Performance (Volume III), Price (Volume IV), and Contract Documentation (Volume V). All volumes must be received via two different media, electronic (CD-R or DVD-R) and paper. The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand carried to the source selection facility at the following address:

AFLCMC/AZK

ATTN: Mr. David Moorhead (FA8621-15-R-6338) 1755 Eleventh Street Building 570, Room 113 Wright-Patterson AFB OH 45433-7404

2.6 Deadline

All proposal volumes must be received by 1500 local Dayton, Ohio time on XX May 2015.

3.0 Volume I - Executive Summary

In the Executive Summary Volume, the offeror shall provide the following information:

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks and mitigation activities, as well as highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M, Evaluation Factors for Award. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

The offeror shall provide documented evidence that they currently hold a valid U.S. Facility Security Clearance of Top Secret (Draft DD Form 254, Section 1.a.) and storage capability at the Secret level (Draft DD Form 254, Section 1.b.) or their plan to obtain this by contract award.

Note: If an offeror has existing security documentation demonstrating the facility clearance and storage capability requirements, this documentation may be included as an attachment to Volume I and will not be included in the page limit.

The offeror shall also detail their plan to obtain TOP SECRET clearance to operate at the Barksdale and Minot Weapon System Trainer (WST) facilities. If the Offeror already possesses the ability to operate at the TOP SECRET level they shall state so and provide evidence of in the response. (PWS paragraph 2.1.10)

3.2 Table of Contents

Include a master table of contents of the entire proposal.

4.0 Volume II - Technical Capability Volume

4.1 The Technical Capability Volume shall be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these Factors and Subfactors. 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.

4.2 Format and Specific Content

The Technical Capability Volume is limited to 200 pages.

4.2.1 Volume Organization

The Technical Capability Volume shall be organized according to the following general outline:

(1) Table of Contents (not included in the 200-page limit)

(2) List of Tables and Drawings (not included in the 200-page limit)

(3) Glossary (not included in the 200-page limit)

(4) Proposal Traceability Matrix (see Attach. L-6)(not included in the 200-page limit)

(5) Subfactor One: Program Management

(6) Subfactor Two: Contractor Logistics Support

(7) Subfactor Three: Training System Support Center

(8) Subfactor Four: Trainer Modifications

4.2.2 Technical Capability

In the Technical Capability Volume, address your technical solution for meeting or exceeding (where possible) the Government’s minimum performance requirements of each technical subfactor. (Note that credit will only be given for exceeding minimum performance requirements for Subfactors 3 and 4.)

4.2.2.1 Technical Capability Risk

For all Subfactors, address Technical Risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with DoD Source Selection Procedures as provided in Section M, Table 3, Technical Risk Rating.

Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: PWS or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation. (PWS paragraph 2.1.9)

4.2.2.2 Schedule Assumptions

Actual start dates for requested schedules are unknown. The offeror shall provide conceptual schedules for purposes of government schedule evaluation only. Start dates should be considered notional. Format should be MS Project 2010 – Gantt Chart based to the lowest manageable work level.

4.2.3 Specific Subfactor Proposal Content:

PWS references below are not all-inclusive of all applicable PWS sections. Refer to PTM, Appendix L-6 for applicable PWS sections.

4.2.3.1 Subfactor 1: Program Management

4.2.3.1.1 The offeror shall provide a detailed description of their home office organizational and support structure that demonstrates that the contractor has an organizational structure that grants the contractor program manager sufficient authority to execute all requirements and also provides timely and responsive support for execution of all CLS, TSSC, modifications, and the development of studies under this solicitation. This description should include specific detail of where in the organization the B-52 Training Systems program manager (PM) is assigned, information on reporting chains and levels of authority to manage all required efforts under this solicitation, the role of the PM and the relationship to supporting functional organizations, e.g., engineering, quality assurance, finance, etc. and identification of key personnel by position.

The Offeror shall reference the PWS, Paragraph 2.1.1 for key personnel positions and use the descriptions and qualifications provided in Section J, Attachment 3, Price Matrix and describe how they will execute this program. (PWS paragraph 2.1) The offeror shall provide a detailed, comprehensive Integrated Master Plan (IMP) for all aspects of the proposal.

4.2.3.1.2 The offeror shall describe their company process to attract, recruit, and retain sufficiently trained and qualified personnel to perform all elements of this solicitation, including staffing levels, and personnel qualifications for CLS and TSSC operations. (Note: the Offeror shall not provide this information for the priced options requested under this solicitation.) This description should include the role of the program manager in this process, as well as the role of other key personnel. The offeror’s approach shall provide the steps and typical timelines for completion of the hiring process from advertising a position until the new employee begins work, and the training process to have fully qualified personnel. (PWS paragraph 2.1).

4.2.3.1.3 The offeror shall describe an initial transition methodology which transitions B-52 TS Support from the incumbent contractor as specified in the PWS, up to a 120-day transition period. Specifically, the offeror shall identify the plan for a 30-day transition, 60-day transition, 90-day transition, and 120-day transition. At a minimum, this description should provide an explanation of key tasks for each element of the transition along with schedules, exit criteria, personnel resources and training, and infrastructure planned for, Barksdale and Minot Air Force Bases operating locations. (PWS paragraph 6.1.1).

4.2.3.1.4 The Offeror shall describe arrangements with subcontractors, teaming partners or other entities, which the contractor plans to utilize to meet the PWS requirements This description should include the names of all organizations, the unique qualifications of each organization, the specific work to be accomplished by each organization, the work share to be performed by each organization, any Associate Contractor Agreements that will be required and the types of information to be exchanged there under. (PWS paragraphs 2.1, 2.1.7, and 2.1.8)

4.2.3.2 Subfactor 2: Contractor Logistics Support

4.2.3.2.1 The Offeror shall describe their approach for CLS to ensure a minimum 95% availability of the B-52 ATDs and individual stations as referenced in PWS Paragraph 3.3, to include the role of Program Management in this process, as well as the role of other key personnel.

This description should include a staffing plan which describes the contractor’s approach to support all of the potential training device availability schedules, maintenance schedules, facility management, and Distributed Mission Operation training events and other areas described within PWS paragraph 3.0.

4.2.3.2.2 The offeror shall describe their approach to address obsolescence and diminishing manufacturing sources management Additionally, the offeror shall provide their approach for management of , obsolescence, and failure rate tracking for the B-52 ATDs, spares and support equipment in accordance with (IAW) PWS paragraph 3.1.20 and 3.13.

4.2.3.3 Subfactor 3: Training System Support Center (TSSC)

4.2.3.3.1 The Offeror shall describe their Baseline Management approach for maintaining and merging multiple, concurrent software and hardware development efforts, configuration management functions and mission planning. This description should include the activities required and an explanation of the key tasks involved and the entrance/exit criteria associated with establishing/modifying the configuration baseline(s). The description shall include an efficient labor skill mix capable of meeting the project labor scope. (PWS Paragraph 4.3)

4.2.3.3.2 The Offeror shall describe their approach and anticipated manpower needed, by year, for the TSSC to accomplish Distributed Mission Operations Mission Package (DMO/MP) standards updates throughout the life of the contract and to ensure the completion of all standards through MP15 within the first 3 years. This includes MP10 and 11 in the base year;

MP12 and 13 in Option Year 1; and MP14 and 15 in Option Year 2. This description shall use the definitions of resources provided in Section J, Attachment 3, “B-52 TS Price Matrix”, to provide an explanation of the labor skill mix (including required numbers of staff broken out by discipline category, experience levels, and academic degree levels) along with a discussion of the role of the PM and any other key personnel in this process. The Offeror shall also indicate that, given the same level of effort required to complete DMO/MP through MP15 within the first 3 years, their stated approach and the proposed manpower levels will/will not remain constant for each of the remaining TSSC option years. (PWS paragraph 4.3.11)

4.2.3.3.3 The Offeror shall describe their approach and anticipated manpower needed, by year, for the TSSC to accomplish B-52 Software Block updates to the trainer Offensive Avionics System. This description shall use the definitions of resources provided in Section J, Attachment 3, “B-52 TS Price Matrix”, to provide an explanation of the labor skill mix (including required numbers of staff broken out by discipline category, experience levels, and academic degree levels). The description should include an schedule which details the steps from initial development through training device Ready for Training verification along with a discussion of the role of the PM and any other key personnel in this process. (PWS paragraph 4.3.12)

Note: the offeror may provide a single labor matrix addressing each of the sections above, provided the government can clearly differentiate the labor associated with each of the measures of merit in Section M, 2.2.3 Subfactor 3.

4.2.3.4 Subfactor 4: Trainer Modifications

4.2.3.4.1 The offeror shall provide their technical approaches to include individual schedules for the government defined upgrades (Combat Network Communications Technology (CONECT), Identify Friend and Foe (IFF) Mode S/5, and 1760 Internal Weapons Bay, Increment 1.1) in accordance with the PWS (PWS paragraphs 2.2 and 4.1). At a minimum, the Trainer Modifications approach shall demonstrate technical understanding of the requirements, trainer operations, and deliverables. The technical proposal shall address the entire modification cycle IAW the PWS including design, development, reviews, testing, manufacturing, delivery schedule, installation, integration, and sustainment. The proposal shall provide insight into the systems engineering processes and procedures, development of milestone events, event entry and exit criteria, and deliverables IAW the trainer upgrades.

4.2.3.4.2 The Offeror shall provide separate risk identification and mitigation plans, identifying risk elements and corresponding mitigation for each of the three defined upgrades (a total of three risk plans) (PWS paragraph 2.1.9)

4.2.3.4.3 The Offeror shall provide a detailed IMP and an Integrated Master Schedule (IMS) for the CONECT upgrade only that clearly defines:

CONECT development for WST and Offensive Station Mission Trainer (OSMT) CONECT production/install for 3 WSTs and 2 OSMTs

The IMS shall contain milestones, with corresponding completion dates, for accomplishing all development and production aspects of the upgrade effort(s). (PWS paragraph 4.1 and 4.2) Note: IMP and IMS do not count towards page limit.

4.2.3.4.4 The offeror shall present their approach to relocate the SIL and B-52G WST Flight Station. This approach shall ensure on-site personnel will be capable and available to fully meet the requirements of the PWS and SIL availability. The offeror’s approach shall also ensure a realistic ability to provide experienced, knowledgeable, and capable personnel, which are available to initiate and execute concurrency and trainer modernization modifications and upgrades as required. The approach shall also address the ability to meet facility and facility security requirements for the needs of housing and operating the WST SIL and housing requirements for the B-52G WST Flight Station. The approach shall also include a transition schedule to relocate the WST SIL and B-52G WST Flight Station to ensure the SIL is ready for use by the Government prior to being needed for development efforts. (PWS paragraph 6.1.2) Note: transition schedule WILL NOT count towards page limit if attached separately.

4.2.3.4.5 No component Government Furnished Equipment (GFE) will be provided for the three trainer modification priced options (CONECT, IFF, and 1760) and offerors shall not include GFE requirements for these priced options as part of their proposal. Request for GFE for the modifications will cause the offeror’s proposal to be non-compliant with the terms and conditions of the Request for Proposal and may render the proposal ineligible for award.

5.0 Volume III - Past Performance

5.1 General

PPI Tool. Each Offeror shall submit a Past Performance Volume with its proposal, containing Past Performance Information (PPI) of no more than six contracts which are active or have been completed within five years preceding the date of this solicitation. A minimum of three of the six contracts must be from the Small Business prime. Each contract submitted in Volume III shall be no more than five pages in length. Use the online PPI Tool described in Appendix L-1 to develop this Volume. This information shall be provided for the offeror and significant subcontractors, teaming partners, joint venture partners, and suppliers who are proposed to perform 10 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. The Business Relationships page generated from the PPI Tool is counted within the Introductory Information in the Past Performance Volume.

In addition to the data provided in this volume, the Government will use data obtained from other sources (described below) in the evaluation of past performance:

Past Performance Questionnaires (PPQ). The Government depends on past performance information, particularly relevant commentary, received from agencies which have firsthand experience with an offeror. For the evaluation of the offeror’s performance, the Government is requesting the Offeror send the PPQ (Appendix L-3) directly to customers that could provide relevant past performance information. A cover letter explaining the use of the questionnaire and instructions for completion and submittal is provided (Appendix L-2, PPQ Cover Letter).

The Offeror shall provide the government contact information (name, title, email address, and phone number) for two POCs at each agency the Offeror requests complete/submit the PPQ as part of Volume III. This contact information shall be included as an attachment to Volume III and WILL NOT count against the Volume III page count. It is important that the completed questionnaire(s) be sent directly to the Government (see email address on PPQ, Appendix L-3) NOT LATER THAN 30 days after RFP release. Note that once the questionnaire is filled out, it becomes source selection sensitive and must be handled accordingly.

Client Authorization Letter. If the Offeror identifies past or present performance for a commercial client, the Offeror shall send to each client a Client Authorization Letter (see Appendix L-4), authorizing the client to release requested information on the Offeror’s performance to the Government. Client Authorization Letter(s) shall be attachments to Volume III and WILL NOT count against the Volume III page count.

Consent Letter. For each subcontractor/teaming partner identified in your proposal, the Offeror shall send the Consent Letter template (see Appendix L-5 template) to each subcontractor, teaming partner, and/or joint venture partner, authorizing Government release of past performance information to the Offeror so the Offeror can respond to such information. Consent Letter(s) shall be attachments to Volume III and WILL NOT count against the Volume III page count.

5.2 Early Proposal Information

Each Offeror is requested to submit the Volume III, 15 days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in Offeror disqualification.

5.3 Relevant Contracts

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. Submit PPI (in accordance with Appendix L-1) on no more than six recent contracts completed or ongoing for Federal agencies and commercial customers within five years preceding the date of this solicitation that you consider most relevant in demonstrating your team’s ability to perform the proposed effort. A minimum of three of the six contracts must be from the Small Business prime. 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 contracts submitted do not exceed six contracts. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, Evaluation Factors for Award. Specifically describe and compare the type of work and scope of effort. Include a description of the breadth and depth of the work performed.

5.3.1 Specific Content

The Offeror may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts 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 demonstrate 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. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. The offerors shall categorize the relevant information into the specific Technical subfactors used to evaluate the proposal.

5.3.2 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. 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 intends to consider present and 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. The organizational change history will be no more than five pages in length.

6.0 VOLUME IV – PRICE

6.1 General Instructions

These instructions are to assist you in submitting information for the price proposal.

Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal. Data submitted in the proposal should be information only essential to document or support the price position. No pricing information shall be included in any other volume, including cover letters, unless specifically requested in the respective volume. If price information is included elsewhere in the documentation, the contractor will be deemed unacceptable and the proposal will not be evaluated.

Offers should be sufficiently detailed to demonstrate their completeness, reasonableness and realism. The burden of proof for credibility of proposed prices rests with the offeror.

Additionally, unbalanced pricing may be a reason to reject an offeror’s proposal.

In the Price Volume IV, the offeror shall provide the following information:

a. Insert prices in Section J, Attachment 3, “B-52 TS Price Matrix” for each worksheet, including all option periods in accordance with instructions provided in 6.2 below.

When completing each worksheet specify the unit price, for each quantity range for each ordering period.

b. A statement that the offeror and all subcontractors are in compliance with the Service Contract Act (SCA) of 1965, as amended. For certain labor categories, the Department of Labor (DOL) Wage Determinations (WD) (Section J, Attachments 5 & 6) provides the minimum qualification requirements and wages to allow the offeror to propose either SCA or non-SCA covered personnel for certain labor categories. It is the responsibility of the offeror and the subsequent contract awardee to comply with the SCA.

c. The offeror shall identify all employees performing computer systems analyst and computer programming work. These employees are exempt from the SCA, and statutory overtime, only if the employee meets the criteria specified in DOL regulation 29 CFR Part 541 for the computer-related occupations. This requirement applies even though they may be represented by a union or the classifications are listed in any Collective Bargaining Agreement (CBA).

d. Specific classes of employees performing work on this contract may be exempt from the SCA provisions (as implemented by Section I, FAR Clause 52.222-41) if the employee meets the criteria specified in DOL regulation 29 CFR Part 541 for the Executive, Professional, Administrative, or Computer-related occupations. Wages and benefits for employees exempt from the SCA are not governed by either a DOL area WD or a CBA-based WD, thus the wage and benefit escalation for exempt employees is not recoverable under Section I FAR Clause 52.222-43. Offerors shall address planned wage and benefit escalation for all exempt employees accordingly.

Offerors shall not build any escalation into the contract price for the non-exempt employees because that escalation is recoverable under Section I, FAR Clause 52.222-43 (see paragraph b of the clause).

6.1.1 Estimating Techniques and Methods

When responding to the Cost/Price Proposal requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods, to develop their estimates. Identify deviations (if any) from your standard estimating procedures (including overhead and General and Administrative applications) in preparing this proposal volume. Indicate whether you have Government approval of your estimating and purchasing systems and provide evidence of such approval.

Provide a summary description of your pricing/methodology and any assumptions used as it pertains to this acquisition.

The offeror shall model their price proposal via the use of a Microsoft Excel workbook(s), and shall submit both a paper hard copy and electronic soft copy. The electronic copy must include working models of the cost proposal that is based on the offeror’s various estimating methodologies used in the proposal. For example, if input parameters change, the Excel model should automatically recalculate the new funding requirements.

6.1.2 Organization of Pricing Data

Data submitted in the proposal should be information essential to document or support the cost/price position. It should be concise and well organized. The price proposal shall provide sufficient detail to demonstrate price credibility and to enable the price evaluators to verify data presented is reasonable. Explain how and why your estimate was built, and why it is credible and correct. All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Price Volume. This information and documentation shall not be included elsewhere in the proposal.

a. All development prices are to be displayed by Contract Line Item Number (CLIN).

b. All prices shall be in “then-year” dollars, that is, inflated, not constant (base year) dollars, except for those portions of the contract (Sustainment) which meet the requirements of the SCA. SCA requires these dollars be proposed in Base Year values.

c. All loaded labor rates shall be rounded to the nearest penny. All other dollar amounts provided shall be rounded to the nearest dollar. All other rates and factors shall use no more than two (2) decimal places.

d. Each page of pricing information shall contain subtotals at logical breaks and totals, as appropriate.

e. Prices in this proposal will include estimates for Program Management, CLS/TSSC, Development, Production, Studies and Transition costs. These estimates will track to your proposed prices in the contract. If any other Government costs are required, these prices also will be included in the offeror’s proposal.

6.1.3 Price Information

Information beyond what is required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support the price position. All supporting information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal. If price information is included elsewhere in the documentation, the contractor will be deemed unacceptable and the proposal will not be evaluated.

6.1.4 Pricing Assumptions

Summarize all significant pricing assumptions, scope limitations, and/or qualifications of the Cost/Price proposal. The Pricing Assumptions section shall not exceed two pages.

6.1.5 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than certified cost or pricing data may be required to support price reasonableness and/or realism. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and/or realism and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit cost or pricing data as defined under FAR 2.101.

6.1.6 Cost Reimbursement CLINs

The Offeror shall not propose prices for the Cost Reimbursement CLINs as they are provided by the Government in the Government Estimate Column. The Offeror shall provide the fully burdened rate which will be applied to the Government Estimate, and the Total Price will be calculated for the identified cost CLINs. These include the CLS and TSSC Materials CLINs 0006 – 3006 & 0010 - 7010, and Travel- TSSC CLINs 0012 – 7012, Travel – TSSC DMO 0013

–…