Attach_12_Section_L.pdf

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1.0 Proposal Format

1.1 General: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the Ground Subsystem Support Contract (GSSC) 2.0 as the Government will review only one proposal per offeror. Proposals received are subject to the requirements specified in FAR 52.215-1, unless otherwise tailored in an Addendum to the solicitation. Proposals must be received by AFNWC/PZBA, 6008 Wardleigh Rd Bldg 1580, Hill Air Force Base, UT 84056, Attention: Mr. Corey Taggart or corey.taggart@us.af.mil, no later than the date and time specified in Block 9, Section A of the solicitation.

The Government intends to award a single Indefinite Delivery Indefinite Quantity (IDIQ) contract for the GSSC 2.0 in Fiscal Year 2020 for an 18 year contract. The contractor will perform Integration, Program Management Support, Engineering Services (Systems Engineering, Sustainment Engineering, Ground Subsystems Assessment, and Test Support), and Emergency Response referenced in the Performance Work Statement (PWS). The contractor may be awarded future work within the scope of GSSC for acquisition of hardware/software or other related acquisition programs.

The offeror’s proposal must include all data and information requested by these instructions to offeror (section L).

The offeror shall be compliant with the basic and each task order’s Performance Work Statement (PWS) and CDRLs.

The Proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not rephrase the Government’s requirements, rather shall provide a description addressing how the offeror intends to meet these requirements and convincing evidence of the effectiveness and the offeror’s ability to execute their proposed methodology. Where supporting evidence of capabilities is based on systems other than Minuteman III (MMIII), the offeror shall clearly demonstrate how the capabilities will translate/apply to MMIII Ground Subsystems. The proposed approach must be sound (well developed), feasible, effective, and clearly demonstrate with explicit evidence the full capability and experience their team possesses for performing activities to meet PWS requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its Technical Factor evaluation solely 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.

The proposal acceptance period is specified in Section A of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for a minimum of 365 days from solicitation closing.

In accordance with 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.

1.2 Communications:

1.2.1 Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to Corey Taggart at the address or email address cited in paragraph 1.1. Offerors shall submit comments and questions to the PCO via e-mail and when appropriate, answers will be published on the mailto:corey.taggart@us.af.mil

Federal Business Opportunities (FedBizOpps) website. Written requests for clarification may be sent to the PCO at the address located in Section A of the solicitation.

1.2.2 Exchanges of source selection information between Government and offerors will be controlled by the Procuring Contracting Officer (PCO). Email may be used to transmit such information only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mailing or facsimile. In order to facilitate the sending and receiving of encrypted emails, offerors must use 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 your source selection information via encrypted email, to the offeror shall contact the PCO indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). Otherwise, source selection information will be transmitted via direct mailing or AMRDEC SAFE at https://safe.amrdec.army.mil/safe/guide.aspx .When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted. When sending encrypted source selection files, ensure “Source Selection Information” is in the subject line of the email.

1.2.3 Submission, Modification, Revision, and Withdrawal of Proposals

1.2.3.1 Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address located in paragraph 1.1 of this document, and show the time and date specified for receipt, the solicitation number, and the name and address of the offeror. Late proposals will only be considered IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

1.2.3.2 Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the proposal wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

1.2.3.3 Proposals may be withdrawn by written notice received at any time before award. Proposals may be withdrawn in person by an offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

1.2.4 Debriefings – The PCO 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, Pre-Award Debriefing of Offerors.

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. The PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506, Post-Award Debriefing of Offerors. 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.505 or 15.506, as applicable.

1.2.5 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 PCO in writing with supporting rationale, as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. Government responses will be published on the FedBizOpps website for access by all offerors. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

1.2.6 Amendments to Solicitation – If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by the date and time specified in the amendment(s) by signing and returning the front page of each.

https://safe.amrdec.army.mil/safe/guide.aspx

1.2.7 Use of Non-Government Advisors – Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who work for the following companies as non- Government advisors for review and analysis

Company Name Address BAE Systems Inc. 6008 Wardleigh Rd Bldg 1580

Hill Air Force Base, UT 84056

1.2.7.1 Per DOD Source Selection Procedures, paragraph 1.4.6.2, Non-Government advisors may not serve as Chairperson of a Source Selection Advisory Council (SSAC), or as a Source Selection Authority (SSA). Access to offerors’ proposals shall be restricted to only those portions for which the individual’s expertise is required to support the evaluation (e.g., software support contractor only reviews software hours proposed).

1.2.7.2 The individuals participating in the review and analysis of proposals have signed individual non-disclosure agreements with the Government which strictly prohibits any release or disclosure of information outside of the Source Selection Team.

1.2.7.3 Offerors shall follow and complete the instruction in Section K.001 of the solicitation.

1.3 Budget Information

Awardable tasks as listed in Table 1 will be funded annually. Table 1 below contains the FY20 planned budget for the 18 years of this contract broken out per awardable task order. This information has been estimated based on historical averages to sustain the MMIII Ground Subsystems. Any proposed task order that is under the provided budget in Table 1 relays an unrealistic bid and may be grounds for the offeror to be eliminated from the competition.

Table 1 GSSC 2.0 Planned Budget ($ TY)

The budget listed in Table 1 is not a commitment by the Government and can change at any time.

Millions 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 General Sustainment

19.30 19.88 20.48 21.09 21.72 22.37 23.05 23.74 24.45 25.18 25.94 26.72 27.52 28.34 29.19 30.07 30.97 31.90 16.91

ALCS

Sustainment

2.30 2.37 2.44 2.51 2.59 2.67 2.75 2.83 2.91 3.00 3.09 3.18 3.28 3.38 3.48 3.58 3.69 3.80 2.01

Codes 3.50 3.61 3.71 3.82 3.94 4.06 4.18 4.30 4.43 4.57 4.70 4.84 4.99 5.14 5.29 5.45 5.62 5.78 3.07 GMATS CLS 6.70 6.90 7.11 7.32 7.54 0.70 0.72 0.74 0.76 0.79 0.81 0.84 0.86 0.89 0.91 0.94 0.97 1.00 0.53

HAC RMPE

CLS

5.30 5.46 5.62 5.79 5.97 6.14 6.33 6.52 6.71 6.92 7.12 7.34 7.56 7.78 8.02 8.26 8.50 8.76 4.64

IOSSP 18.10 18.64 19.20 19.78 20.37 20.98 21.61 22.26 22.93 23.62 24.32 25.05 25.81 26.58 27.38 28.20 29.05 29.92 15.86 SACCS CLS 2.10 2.16 2.23 2.29 2.36 2.43 2.51 2.58 2.66 2.74 2.82 2.91 2.99 3.08 3.18 3.27 3.37 3.47 1.84 Trainers CLS 5.10 5.25 5.41 5.57 5.74 5.91 6.09 6.27 6.46 6.65 6.85 7.06 7.27 7.49 7.71 7.95 8.18 8.43 4.47

2.0 Volume Organization

2.1 General:

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 and with the number of copies as specified in the Table.

Volume Volume Title Page Limits

Number of Hard Copies

Number of Soft Copies

Description

I General Information

N/A 2 2 General Information Volume:

- General Information

- Cross Reference Matrix

- Offeror Labor Category Description and Mapping

- Labor Hour Summary

II Technical 400 8 2 Technical Volume 400 pages includes:

- - Program Management Plan – 40 pages max

- - Transition Plan – 20 pages max

- - Task Order Technical Description – 200 pages max for all task order (except General Sustainment)

- General Sustainment task order – 140 pages max III Cost/Price N/A 3 2 Cost/Price Proposal Volume

IV Contract Documentation

N/A 2 2 Contract Documentation Volume:

- RFP compliance

- Other Information

2.1.1 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 and (for paper copies) will be shredded. If Evaluation Notices (ENs) are issued, page limitations may be placed on responses. The specified page limits for EN responses will be identified in the letters forwarded with the ENs to the offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, tabs, glossaries, and all reproduced sections of the solicitation.

2.1.2 Page Size and Format

a. 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. Except for the reproduced sections of the solicitation document, the text size shall be Times New Roman font and no less than 12 point. 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 size and format restrictions shall apply to responses to Evaluation Notices (EN).

b. Organizations, systems and layout, implementation schedules, plans, and etc. shall be depicted in tables, charts, graphs, or figures wherever practical. These items shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8 point and searchable for text in MS Word and/or PDF formats to the maximum practical extent. Ensure all tables, foldouts, graphics, and figures in the electronic version of the proposal are pasted into the proposal in a format that allows a word search by the host program (do not paste as pictures) to the maximum practical extent. These limitations shall apply to both electronic and hard copy proposals.

2.2.2 Cost or Pricing Related Data

2.2.2.1 All cost data requested in 5.0 of this section should be in .XLS file format (MS-Excel 2010 or earlier) compatible format. All electronic cost/pricing data submission should be IAW Section 2.3.

2.2.2.2 All cost or pricing data shall be addressed only in the Cost/Price Proposal and Contract Documentation Volumes. Cost tradeoff 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 tradeoff decisions.

2.2.3 Classified Information

Classified information is not to be submitted as part of the proposal. A DD Form 254, Contract Security Classification Specification, Department of Defense is required for the performance of this contract.

2.2.4 Cross-Referencing

2.2.4.1 Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

2.2.4.2 Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity, but must be hyperlinked IAW Section 2.3.2.

2.2.4.3 The offeror shall provide a cross-reference matrix indicating by PWS, Section L and Section M paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item, using the Government provided template (Section J Attachment 9). The cross-reference matrix does not count towards the volume page limit.

2.2.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2.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.2.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. The outside of each binder shall include a cover sheet, clearly marked, identifying volume number, title, copy number, solicitation identification, and the offeror's name. 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. Be sure to apply all appropriate markings including those prescribed IAW 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.

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and the electronic copy, the hard copy will take precedence and will be used for evaluation. The offeror shall submit Volumes I through IV in electronic format, using virus-free CD-R. In no cases shall the offeror use CD-RW. For electronic copies, indicate on each CD the 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 separate 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 Microsoft (MS) Office Word 2007-2013, MS Office Excel 2007-2013, MS Office Project 2007-2013 (and Primavera P6), and MS Office Power Point 2007-2013, as applicable, and not in PDF format.

2.3.1 Electronic File Names

For electronic submissions, the file naming convention for the proposal volumes is as follows:

Volume File Name Executive Summary execsum.xxxx Technical tech.xxxx Past Performance pastperf.xxxx Cost/Price price.xlsx Contract Documentation contv.xxxx

NOTE: You may expand on these file names as appropriate; just provide a list of the content of each electronically, in the master Table of Contents in Volume I. xxxx = appropriate default file extension for document type (e.g., .doc/docx for MS Word, .xls/xlsx for MS Excel, etc.)

2.3.2 Hyperlink

The Table of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that clicking the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. The Table of Contents shall include the file names, as well as page numbers where content is cross-referenced between subfactors. Also, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. Hyperlinking references between different filenames are not necessary.

2.5 Distribution

2.5.1 The original proposal shall be identified “Original”. The proposal shall be addressed to the PCO and mailed or hand-carried to the address cited in paragraph 1.1.

2.5.2 Delivery of proposals shall be coordinated at least 24 hours in advance of the due date/time with the PCO. Proposals received after the due date and time specified in the solicitation shall be treated IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

2.5.3 Offerors are cautioned that Hill AFB has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

2.6 Proposal Inquiries

All inquiries must be submitted via e-mail to the PCO. Questions, if appropriate as determined by the Government, will be answered as quickly as possible, during the proposal preparation period. Government responses will be published on the FedBizOpps website for access by all offerors.

2.7 Marking

2.7.1 Each page containing proprietary information should be so marked.

2.7.2 Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

3.0 Volume I, General Information

3.1 General: Volume I, General Information shall consist of the completed Cross Reference Matrix in Section J, Attachment 6, Offeror’s Labor Category Description and Mapping in Section J, Attachment 8, Labor Hour Summary in Section J, Attachment 9. For any amendments to the offerors proposal this volume will include a cover letter delineating any changes from initial proposal, to include changes/revisions (if needed) for Final Proposal Revisions (FPR).

3.1.1 Cross Reference Matrix. The offeror shall fill out the Cross Reference Matrix, Section J, Attachment 6, and submit with the proposal indicating where in its proposal the information can be found as it relates to the PWS, Section L, and Section M. The cross reference matrix will help an offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Section M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation. This attachment will be used for reference only and will not become contractually binding.

3.1.2 Offeror Labor Category Description and Mapping. The offeror shall fill out the Offeror’s Labor Category Description and Mapping in Section J, Attachment 8 and submit with the proposal. The labor category description shall provide a title and description in the appropriate columns for each of the labor categories the offeror anticipates using on awardable and future add-on task orders.

The offeror shall also map the offeror’s labor categories in the Mapping column to the appropriate corresponding Government labor category using the reference number detailed in Government Labor Category Description in Section J, Attachment 7. This attachment will become contractually binding (except the mapping column).

3.1.3 Labor Hour Summary.The offeror shall fill out the Labor Hour Summary in Section J, Attachment 9 and submit with the proposal. The Labor Hour Summary will be used as a tool to evaluate the Subfactor 1 – Technical Expertise. This attachment will be used for reference only and will not become contractually binding.

4.0 Volume II, Technical Proposal

4.1 General: The Technical Volume should 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 approaches (processes/methodologies) and capabilities you would use for accomplishing/satisfying these 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.1.1 Format and Specific Content: The following information shall be provided in the written technical proposal and will be used to assess the proposed technical approach and associated technical risk in accordance with Section M, Evaluation Basis for Award.

The written technical proposal shall address each of the following to describe the offeror’s proposed approach to performing the requirements set forth in the PWS.

4.2 Technical Approach

4.2.1 Technical

In the Technical Volume, address the proposed approach, capabilities, and evidence of meeting or exceeding the minimum performance or capability requirements of each Technical subfactor.

4.2.1 Basis of Estimates (BoE): BoEs must be provided for each awardable task order. BoEs should describe the work to be performed as described in the PWS and laid out as closely to the WBS provided as possible. BoEs will also include labor category, hours, and justification/rationale for the estimate.

4.2.2 Technical write-up/summary of each awardable task order: Each awardable task order should identify a summary of the work to be performed, special expertise, knowledge, tools, etc., that gives the offeror an advantage in performing the work.

4.2.3 Technical Risk

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 IAW DOD Source Selection Procedures 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: Statement of Work (SOW) or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic “work-around” or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation. The Government evaluators will determine file://fsicbm/ICBMData/AFNWC%20NIA/FISAC%20GSSC%20NOV%202012/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/1.%20%20Published%20Baseline/MP5315.3.doc#p5512 the Technical Risk Rating assigned in the evaluation. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach.

4.2.4 Volume Organization

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

Section Title 1 Table of Contents 2 List of Tables and Drawings 3 Glossary 4 Cross Reference Matrix 5 Subfactor 1: Technical Expertise 5-1 Subject Matter Experts 5-2 Recruiting/Retention Plan 5-3 Technical Skill Mix 6 Subfactor 2: Transition 6-1 Transition Plan 6-2 Facilities and Equipment 7 Subfactor 3: Program Management 7-1 Program Management Plan 7-2 Subcontract Management Plan 7-3 Small Business Participation

Note: Offerors shall not address Appendix “C”, Safety, Fire Protection and Health Specification, Industrial Security Requirements of the PWS in their proposal. However, the successful offeror shall be required to obtain 75th Air Base Wing Safety Office approval of their Safety Plan after contract award.

4.2.5 Technical Subfactors

The Technical subfactors for the GSSC 2.0 are:

Subfactor 1: Technical Expertise Subfactor 2: Transition Subfactor 3: Program Management

4.2.5.1 Subfactor One: Technical Expertise

The purpose of this subfactor is to assess the offeror’s approach (processes/methodologies) and capabilities to provide a sufficient level of technical expertise required to maintain Ground Subsystems operational readiness. This subfactor includes the offeror’s Subject Matter Expert(s), Recruitment and Retention Plan, and Technical Skill Mix compared to Labor Hours. The offeror shall prepare and deliver these items describing the approach to meet the entire scope of the contract, with a special focus on specific awardable task orders as directed in subsequent paragraphs. The offeror’s technical proposal shall describe their processes and methodologies for providing the required technical expertise. These processes and methodologies must be sound, feasible, effective, and demonstrate explicit evidence of the full capability and experience their team possesses for performing activities to satisfy or exceed the PWS requirements.

4.2.5.1.1 Subject Matter Experts (SME): The offeror shall submit as part of Volume II a description of specific SMEs required to meet the requirements of the PWS to include: number of years experience and any professional certifications of these individuals employed by the offeror at time of proposal submission.

4.2.5.1.1.1 In addition to the SME description required in 4.2.5.1.1, the offeror shall provide information on specific awardable task orders that show evidence of its current level of Technical Expertise as required below.

4.2.5.1.1.2 ICBM Operational Software Sustainment Program (IOSSP)

4.2.5.1.1.2.1 The offeror shall provide appropriate detail to demonstrate a full understanding of the following IOSSP software programs including but not limited to: programming language, familiarity with the program/code, software line of codes, and provide a description of the processor:

Program Language SLOC Processor

OGP ADA 30 K MGS (MIL-STD-1750A)

OFP ADA 6 K MGS (MIL-STD-1750A)

COP ADA, C & Assembly 85 K Vax SMC-810 MOTP FORTRAN 25 K Vax SMC-810 STSS FORTRAN 58 K Vax 3185 MPE Adobe Flex/Actionscript 11 K NCS Computer XPQ-3140 (Win 7)

4.2.5.1.1.3 Higher Authority Communications/Rapid Message Processing Element (HAC/RMPE)

4.2.5.1.1.3.1 The offeror shall identify experience working on HAC/RMPE system (or similar systems).

4.2.5.1.1.3.2 The offeror shall also show evidence of its knowledge of the required hardware and firmware of major components and sub-components including test and support equipment necessary to sustain the HAC/RMPE.

4.2.5.1.1.4 Codes

4.2.5.1.1.4.1 The offeror shall provide evidence of its knowledge of Common Certification Operating System (CCOS), Strategic Air Command Code Processing System Application Program (SAP,) and WCPS Minuteman Application Program (WMAP) software or similar system(s).

4.2.5.1.1.4.2 The offeror shall provide a written description detailing expertise and knowledge of ICBM Codes Processing System (ICPS)/WCPS-unique equipment, associated test equipment, and experience.

4.2.5.1.1.4.3 The offeror shall also show evidence of its knowledge of the required activities and intervals to conduct the ICPS Maintenance Technician and Code Controller training courses.

4.2.5.1.1.5 Trainers Contractor Logistics Support (CLS)

4.2.5.1.1.5.1 The offeror shall describe its relative MMIII Trainers maintenance technical expertise.

4.2.5.1.1.6 Ground Minuteman Automated Test System (GMATS) CLS

4.2.5.1.1.6.1 The offeror shall describe its GMATS technical expertise.

4.2.5.1.2 Recruitment and Retention Plan: The offeror shall submit as part of Volume II a Recruitment and Retention Plan to include but not be limited to: a description of how SMEs are grown, promoted and retained within the company; how the company addresses recruitment specifically for technical expertise; and a description of employee turn-over rates and how the company is addressing loss of critical skills.

4.2.5.1.2.1 In addition to its overall recruitment and retention approach, the offeror shall provide its recruitment and retention approach to the following specific areas to the below identified awardable task orders:

4.2.5.1.2.2 IOSSP

4.2.5.1.2.2.1 The offeror shall describe its recruitment and retention approach to maintain expertise and security clearances necessary to sustain the following IOSSP domains:

• Airborne Vehicle Equipment (AVE)

▪ Operational Ground Program (OGP)

▪ Operational Flight Program (OFP)

• Console Operations Program (COP)

• Mission Planning Element (MPE)

• Minuteman Operational Targeting Program (MOTP)

▪ Strategic Targeting Support Software (STSS)

• Squadron Data Simulator (SDS)

• Wing Code Processing System (WCPS)

4.2.5.1.2.3 Trainers CLS

4.2.5.1.2.3.1 The offeror shall describe its recruitment and retention approach specific to Trainers personnel.

4.2.5.1.2.4 GMATS CLS

4.2.5.1.2.4.1 The offeror shall describe its recruitment and retention approach specific to GMATS personnel.

4.2.5.1.3 Technical Skill Mix: The offeror shall submit as part of Volume II a summary of all labor categories proposed to perform the work of the awardable task orders at the level of the budget provided in Table 1. The summary shall include total hours per labor category. This summary shall be provided by completing and delivering Section J, Attachment 9, Labor Hours Summary.

4.2.5.1.3.1 In addition to the Labor Hour Summary in Section J, Attachment 9, the offeror shall provide Technical Skill Mix information for specific awardable task orders as required below:

4.2.5.1.3.2 General Sustainment

4.2.5.1.3.2.1 The offeror shall also provide a written description with rationale why the skill mix was chosen for the General Sustainment task order.

4.2.5.1.3.3 IOSSP

4.2.5.1.3.3.1 The offeror shall describe the skill set required to sustain the following software laboratories:

• AVE – Boeing-Huntington Beach, CA

• COP – Lockheed Martin, Colorado Springs, CO

• MPE – Northrop Grumman-Omaha, Bellvue, NE

• MOTP – Northrop Grumman-Space Park, Space Park, CA

• DARTS – Northrop Grumman-Omaha, Bellvue, NE

• WCPS – Boeing-Huntington Beach, CA

4.2.5.1.3.4 HAC/RMPE

4.2.5.1.3.4.1 The offeror shall provide a detailed description describing the skill set required to sustain the HAC/RMPE. Specifics to describe include the Message Processor (MP), Communication Integrator/Backup (CI/B) and assembly code, and Transmission Integrator (TI) with assembly code.

4.2.5.2 Subfactor Two: Transition

4.2.5.2.1 Transition Plan: The offeror’s Transition Plan shall describe what products are required from incumbent or other contractors/companies to perform all task orders. The transition plan shall include, but is not limited to: Data products; unique data/hardware required to effectively perform tasks; a description of how data will be used and incorporated; a schedule for products to be provided, reviewed and available for use; items requiring training; recommended communication method(s); recommended delivery format for each data item; and Intellectual Property that is known.

4.2.5.2.2 Facilities and Equipment: The offeror shall detail what facilities and equipment will be required to perform the requirements in the PWS. Facilities and equipment shall include any government provided, contractor provided, or company owned along with required schedule. The offeror shall demonstrate the ability to obtain, utilize and qualify personnel within 6 months of contract award to sufficiently utilize the listed equipment and facilities that are not company owned. Include additional information describing the offeror’s knowledge and capability to perform the work.

4.2.5.2.3 HAC/RMPE

4.2.5.2.3.1 Describe the approach for transitioning the following:

• Multiple baseline schedule delivering as ordered by USSTRATCOM

• Technical baseline documents (specifications, technical orders, etc) as required for twice a year software builds

• Concept for Software Support for HAC/RMPE through transition (i.e. emergency urgent software updates)

4.2.5.2.4 Codes

4.2.5.2.4.1 Describe the approach to transition equipment, GFP, and documentation at various locations.

4.2.5.2.5 Trainers CLS

4.2.5.2.5.1 Describe the approach to transition equipment, GFP, and documentation at various locations specifically to support Trainers.

4.2.5.2.6 GMATS CLS

4.2.5.2.6.1 Describe the approach to transition equipment, GFP, and documentation at various locations specifically to support

GMATS.

4.2.5.2.6.2 Describe the approach to transition Huntron repair from contractor site to depot repair shall be included.

4.2.5.3 Subfactor Three: Program Management

4.2.5.3.1 Program Management Plan (PMP): Offeror must provide a PMP IAW CDRL A0007. The PMP must also include Subcontracting Management Plan and Small Business Participation Plan.

4.2.5.3.2 Subcontractor Management: The offeror shall identify the use of subcontractors in each awardable Task Order.

Subcontractor joint ventures shall be identified in the proposal including rationale. The offeror shall identify its teaming arrangement status with each identified subcontractor (e.g. on contract, in negotiations, etc.) and provide a projected for award date with each subcontractor and for each associated contractor agreement.

4.2.5.3.3 Small Business Participation: The offeror shall describe its Small Business participation approach to address the goals within PWS paragraph 1.4.3.3.6.2. The Small Business participation approach shall also include the extent to which such firms are specifically identified in proposals and the extent of commitment to use such firms. The Small Business participation Plan is not to be confused with the offeror’s Small Business Subcontracting Plan required in FAR Clause 52.519-9.

5.0 Volume III, Cost/Price

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness, balance, and realism (where identified) of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs/prices rests with the offeror.

5.1 Total Evaluated Price (TEP) Pricing Matrix Section J Attachment 14 Offerors shall populate the pricing and cost cells as appropriate. The offeror shall provide a cost summary by major cost elements by contract year as shown in the TEP Worksheets. The Government will use this worksheet to calculate the TEP.

5.2 Award Fee Pools

The offeror shall propose award fee pools for each Task Order for the base year and option periods. The offeror’s proposed award fee pool shall be expressed as a percentage rate for all fee-bearing elements (Labor Contract Line Item Number (CLIN) less Cost of Money) associated with the work. The proposed award fee percentage shall be the same for each Task Order and future task orders.

The offeror shall not propose a base fee.

5.3 Transition

The offeror shall submit a firm-fixed price dollar amount for all transition. The Government will include transition costs in the TEP.

5.4 Cost Reimbursable No Fee (CRNF) Contract Line Item Numbers (CLIN).

The offeror shall propose CRNF CLINs for Material and Travel. These proposed CLINs will not be included in TEP but will be used for funding purposes only.

5.4.1 Material Costs

The offeror shall propose material costs for the first year of each Task Order. The material costs include any sales tax, special privilege tax, discounts, and freight; it does not include any costs that are consistent with common G&A expenses (e.g., corporate software licenses, corporate business systems) and any indirect rates (e.g., material handling, G&A). The offeror shall include all applicable indirect rates to the Material Cost.

5.4.2 Travel Costs

The offeror shall propose travel costs for the first year of each Task Order using estimated unburdened cost of travel. The offeror shall include all applicable indirect rates (e.g., material handling, G&A) to the Travel Cost.

5.5 Labor Rate Matrix, Section J Attachment 10:

Offerors shall populate the pricing and cost cells, as appropriate, according to the instructions on the worksheet. The Government will use this worksheet to price all future contractual modifications and awards. Provide only the Prime’s fully burdened Labor Rates (to include all associated direct and indirect costs, EXCEPT profit/fee) for each labor category specified. Descriptions of the labor categories shall map to the Labor Category Descriptions, Section J Attachment 8.

5.5.1 Labor Rates

The offeror shall submit one rate to be used for the prime contractor (including interdivisional units, subsidiaries, affiliates, divisions, sectors, groups). The proposed Labor Rates for each of the Government specified labor categories shall include all applicable direct and indirect costs, including facilities capital cost of money. Profit/Fee shall not be included in the rates, but should be included separately as a percentage on the appropriate row. These rates shall be used for all future contractual modifications and all future awards not already priced otherwise on the basic contract. The base rates will be used for all pricing arrangements after the application of the appropriate profit/fee percentage. Share ratios/ceilings/min-max and other incentive fee type arrangements for Fixed-Price Incentive Firm and Cost-Plus Incentive Fee arrangements will be negotiated at the time they are utilized after award. Refer to the pricing attachments for additional instructions.

5.5.1.1 Basis of Estimate (BOE). The offeror shall provide a priced BOE for Cost-Plus Award Fee (CPAF) line items 0005 for each awardable task order. The contractor shall show base labor rate, a breakout of all indirect rates applied and fee. Also, indicate the basis for these rates and reference (if applicable) the current Forward Pricing Rate Agreement (FPRA) or audit the rates were taken from. Additionally, the offeror shall provide the rationale behind proposed labor hours, labor mix, travel (first year only) and any material (first year only). The organization of this BOE shall follow the offeror’s technical proposal, and be arranged in a logical fashion.

5.6 Subcontractor Costs

The offeror shall submit a list of the proposed subcontractors and interdivisional transfers showing (a) the supplier, (b) description of effort, (c) type of contract, (d) price and hours proposed by each, (e) price and hours included in prime’s proposal to the Government, and (f) commercial item / service determination support, if applicable. The offeror shall conduct cost or price analyses of subcontracting costs in accordance with FAR 15.404-3 and include those results in the cost/price volume.

In the event a subcontractor’s contract type is Cost, the subcontractor shall submit cost data at the same level of detail is required of the offeror. Any subcontractor proprietary cost data required shall be submitted directly to the PCO at the address cited in paragraph

1.1. The Government will review all major subcontractors and reserves the right to review and request additional data.

For purposes of the Cost/Price Volume only, a major subcontractor is defined as a subcontractor, other than the offeror itself, that will perform ten (10) percent or more of contract scope based on labor hours or total cost.

5.7 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

5.8 Cost or Pricing Data Requirements

5.8.1 In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided IAW FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data other than Certified Cost or Pricing Data. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. 254b) apply, the offeror shall be required to submit additional cost or pricing data.

5.8.2 Facility costs will not be priced separately. Offerors need to account for this cost in their rate structure.

5.8.3 Awardable Tasks

The offeror shall bid all awardable tasks as if they were post-award tasks to be priced under the Labor Rate Matrix, Section J Attachment 10. All rates and labor categories shall conform to the Labor Rate Matrix. Provide rationale behind the proposed labor hours, and labor mix.

5.8.4 Contract Data Requirements Lists (CDRLs)

CDRLs will not be separately priced. Cost required to produce each CDRL should be included in the offeror’s proposed labor hours.

5.9 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

5.10 Volume Organization

The Cost/Price Volume shall be organized according to the following general outline:

Section Title 1 Table of Contents 2 Listing of Abbreviations and Acronyms (used within pricing volume) 3 Cross Reference Matrix 4 General 4-1 TEP Pricing Matrix Worksheet 4-2 Labor Rate Matrix 4-3 Transition 4-4 Basis of Estimate 5 Estimating Methodology 5-1 Estimating Techniques and Methods 5-2 Estimating System 5-3 Pricing Assumptions 5-4 Purchasing System 5-5 Accounting System 5-6 Explanation of Estimating Methods Used 6 Other Information 6-1 Offeror’s Labor Category Description and Mapping 6-2 Professional Employee’s Compensation Plan

5.11 Estimating Methodology

All information requested under 5.11 only applies to CPAF CLINs 0005 of each awardable task order.

5.11.1 Estimating Techniques and Methods

5.11.1.1 When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non- Cost Estimating Relationships, commercially available parametric cost models, in-house developed parametric cost models, etc.) to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the WBS.

5.11.1.2 Provide a summary description of your standard estimating system or methods. Provide a summary description of your purchasing system or methods. Identify deviations (if any) from your standard estimating procedures in preparing this proposal volume. If a Forward Pricing Rate Agreement (FPRA) has been negotiated with the ACO covering the period of the proposal, provide appropriate comments and the date of agreement. 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 as it pertains to this acquisition. Because the contemplated contract type is other than Firm Fixed-Price, indicate whether you have Government approval of your accounting system and provide evidence of such approval. If your accounting system has been disapproved in whole or in part, provide the status of action taken to correct noted deficiencies. Also, identify any deviations from your standard procedures in preparing this proposal.

5.11.2 Pricing Assumptions

Summarize all significant pricing assumptions, scope limitations, and/or qualifications of the cost proposal. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Cost/Price Volume, if any. Provide complete rationale for any exceptions. This section shall not exceed five pages.

5.11.3 Purchasing System

Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

5.11.4 Accounting System

Indicate whether you have Government approval of your accounting system and if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

5.11.5 Direct Labor & Indirect Rates

If a FPRA has been negotiated with the ACO covering the period of the proposal, provide appropriate comments and the date of agreement.

5.11.6 Explanation of Estimating Methods Used

Explain the methodology used to estimate each cost element. As a minimum, provide the following information for each cost element. In a portion of the required information is not applicable for a particular cost element, so state.

5.11.7 Past Experience-Based Estimates

Where cost estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort, including similarities and differences, and how cost data available from the past experiences was adapted to the current effort.

5.11.8 Learning Curve Estimates

Where cost estimates are based upon learning/improvement curve applications, identify the specific area subject to learning, the curve hypothesis (unit or cumulative)…