ATTACHMENT20SectionL.docx

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

L-I - SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

NOTICE: Pursuant to Federal Acquisition Regulation (FAR) 52.252-1, "SOLICITATION PROVISIONS INCORPORATED BY REFERENCE," the following provisions are incorporated herein by reference:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION PROVISIONS:

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION PROVISIONS:

L-II - SOLICITATION PROVISIONS IN FULL TEXT

NOTICE: The following provisions are hereby incorporated in full text:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION PROVISIONS:

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION PROVISIONS:

D. ADMINISTRATIVE AND ONE-TIME USE PROVISIONS:

L-III INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The Government intends to award a single Indefinite Delivery Indefinite Quantity (IDIQ) contract for the Ground Subsystems Support Contract (GSSC) in Fiscal Year 2015. 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).

2.0 General Instructions

a. The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with (IAW) these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Statements of Objectives (SOO), and Contract Data Requirements List (CDRL). Nonconformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

b. 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 simply rephrase or restate the Government's requirements but 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.

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

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

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

2.1 General Information

2.1.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 Ms. Jody Lindley at 6014 Dogwood Ave, Bldg. 1258, Hill AFB UT 84056-5820 or via e-mail to the following: Jody.Lindley@us.af.mil. Bidder(s) shall submit comments and questions to the PCO via e-mail and when appropriate, answers will be published on the 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.

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

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

2.1.4 Electronic Reference Documents

The referenced documents for this solicitation are available on FedBizOpps 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. Technical documents not available in the public domain will be made available through the Bidder’s Library per instructions posted on FedBizOpps.

2.1.5 Classified Bidder’s Library/Vault

2.1.5.1 The Classified Bidder’s Library will reside within the vault of Building 1258, 6014 Dogwood Ave, Hill AFB UT 84056. It will consist of only hard copies of classified documents that may be necessary to propose to the GSSC. Visits are by appointment only (see contact information below) to view classified or other restricted access documentation that only exists in hard copy form in the Intercontinental Ballistic Missile Systems Directorate (ICBMSD) vault. The library will be open during normal business hours, Monday through Thursday for 9 hours (0700-1600) per day and 7 hours (0700-1100 and 12001500) on Friday. All contractors will be treated equally, and will be provided access to the documents/information as described. The library will consist only of data that the ICBMSD believes is necessary to prepare a proposal. Offerors are encouraged to check the data list prior to setting an appointment. Requests for additional data will be considered by the Government and will be added at the discretion of the Government. No more than one contractor will be scheduled in the library at any given time. No more than four (4) persons per visit, per contractor will be permitted. There will be no copying of data and nothing with which to record data allowed in the vault. Mail order requests for data/documentation will not be honored. Contractors will not be permitted to remove data from the vault.

2.1.5.2 Each contractor will be limited to four (4) two-hour visits. All visits must be scheduled, through Joint Personnel Adjudication System (JPAS), using the Security Management Office (SMO) code HP1MFGKQ, with the Future ICBM Sustainment and Acquisition Construct Data POC, Mr. Paul Catmull (Paul.Catmull@us.af.mil) or his alternate, Mr. Jason Nelson (Jason.Nelson.2@us.af.mil). Visitors must have, at a minimum, a Secret clearance with access to restricted data.

2.1.6 Exchanges with Offerors

Exchanges of source selection information between Government and offerors will be controlled by the PCO. 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 IAW Section L Attachment 1. Otherwise, source selection information will be transmitted via other means as appropriate.

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

2.1.8 Submission, Modification, Revision, and Withdrawal of Proposals

2.1.8.1 Proposals and modifications to proposals shall be submitted in both paper and electronic media to the address located in paragraph 2.5 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.

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

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

2.1.9 Alternate Proposals

Proposals that do not address requirements within this ITO or meet program objectives will be considered alternate proposals and will not be considered.

2.1.10 Use of Non-Government Advisors

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

Los Angeles CA 90009-2957

2.1.10.2 Per DOD Source Selection Procedures, paragraph 1.4.5.2.1 and AFFARS MP5315.3 Source Selection Procedures, support contractors, including Federally Funded Research and Development Center (FFRDC) employees may not serve as an advisor to the Past Performance Team, 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) but in no event will non-Government advisors have access to any offeror’s past performance information.

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

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 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 Table 2.2. The volumes identified in the Table shall be separately bound in three ring, loose leaf binders, as necessary. Page limitations will still apply to each respective volume as shown in Table 2.2. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.2 - Proposal Organization Table

Number

COPIES

HARD

COPIES

PAGE LIMIT

(not to exceed)

· Transition Strategy, max. 25 of 225 pages

· Awardable Tasks, max. 40 per task of 225 pages (CSOWs will not be included in page count).

· Sample Sustainment Scenario (max. 25 and will not be included in page count).

· Key Personnel Resume, max. 4 pages per resume, including prime and subs (will not be included in page count)

· Small Business Subcontracting Plan (will not be included in page count)

· Note: Consent letters will not be included in page count.

2.2.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.2.1.1 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). These limitations shall apply to both electronic and hard copy proposals.

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 6.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 ITO, PWS, and/or specification paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item, using the Government provided template (Section J Attachment 11). 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 V 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:

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.4 Sample Sustainment Scenario

The Government intends to release a sample sustainment scenario. This sample task will be representative of the type of sustainment situations that commonly arise on the Ground Subsystems and will be used for evaluation purposes only. Do not include cost/price data in the technical solution for the sample sustainment scenario. Details of the sample task will not be provided in the original RFP release, but will be provided to offerors before the RFP responses are due to the Government. The details for the sample task will be posted on FedBizOpps. Offerors will be given a reasonable, but limited amount of time to provide a response to the sample task. No additional proposal preparation time will be given for this task.

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:

AFNWC/PZBF

Attn: Ms. Jody Lindley 6014 Dogwood Avenue, Building 1258 Hill AFB UT 84056-5820 Jody.Lindley@us.af.mil

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. Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is “For Official Use Only” and “Source Selection Information–See FAR 2.101, Definitions and FAR 3.104, Procurement Integrity”.

2.6 Proposal Inquiries

All inquiries must be submitted via e-mail to the PCO listed above. 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.

3.0 Volume I – Executive Summary

The Executive Summary Volume is not evaluated, scored, or used to clarify other discrepant information in other volumes. Do not include cost information in 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 highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.2 Table of Contents

Include a master table of contents of the entire proposal.

4.0 Volume II – Technical Volume

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.2 Format and Specific Content

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.1 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 the Technical Risk Rating assigned in the evaluation.

4.2.2 Volume Organization

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

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.3 Technical Subfactors

The Technical subfactors for the Ground Subsystems Support Contract are:

Subfactor 1: Engineering Services Subfactor 2: Awardable Tasks Subfactor 3: Transition Subfactor 4: Program Management Support

4.2.3.1 Subfactor 1: Engineering Services

The purpose of this subfactor is to assess the offeror’s approach (processes/methodologies) and capabilities to provide a sufficient level of engineering services required to maintain Ground Subsystems operational readiness. This subfactor includes Configuration Management, Hardware Development/Sustainment, Software Development/Sustainment, Ground Subsystems Assessment, Aging Surveillance, Team Structure and Partnerships, and the Sample Sustainment Scenario. The offeror’s technical proposal shall describe their processes and methodologies for providing the required engineering services. 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.3.1.1 Configuration Management (PWS 1.6.4.1.6.1, 1.6.4.1.6.2) The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how their program team (including subcontractors) will satisfy or exceed the following hardware, software, and firmware configuration management requirements. The offeror shall provide explicit evidence that demonstrates the use of the approach (processes/methodologies) and capabilities on efforts of similar magnitude and complexity and how it applies to Ground Subsystems requirements.

a. Configuration Identification

b. Configuration Control

c. Configuration Status Accounting

d. Configuration Audits

4.2.3.1.2 Hardware Development/Sustainment (PWS 1.6.4.1.8.1, 1.6.4.1.8.5, 1.6.4.1.10.2, 1.6.4.2.1, 1.6.4.2.3.2, 1.6.4.2.5.1.1, 1.6.4.2.5.1.2, 1.6.4.2.5.2, 1.6.4.2.5.2.1, 1.6.4.4.1.1, 1.6.4.4.1.2, 1.6.4.4.1.3) The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how their program team (including subcontractors) will satisfy or exceed the following hardware development/sustainment requirements. The offeror shall provide explicit evidence that demonstrates the use of the approach (processes/methodologies) and capabilities on efforts of similar magnitude and complexity within the field of strategic nuclear weapons and how it applies to Ground Subsystems requirements.

a. System Safety

b. Parts, Materials, and Maintenance

c. Test and Evaluation

d. Deficiency Identification, Resolution, Implementation, and Documentation

4.2.3.1.3 Software Development/Sustainment (PWS 1.6.4.1.12, 1.6.4.1.12.2.7, 1.6.4.1.12.2.8, 1.6.4.2.2.6) The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how their program team (including subcontractors) will satisfy or exceed the following software development/sustainment requirements for both nuclear and non-nuclear certified software. The offeror shall provide explicit evidence that demonstrates the use of the approach (processes/methodologies) and capabilities on a strategic inertial-guided nuclear ballistic missile system to develop, sustain, integrate, and test software and how it applies to Ground Subsystems requirements.

a. Development and Modification

b. Anomaly Resolution and Integration

c. Test and Evaluation

4.2.3.1.4 Ground Subsystems Assessment (PWS 1.6.4.3.1.9, 1.6.4.3.4.1, 1.6.4.3.4.2, 1.6.4.3.4.3, 1.6.4.3.5.7, 1.6.4.3.5.8) The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how their program team (including subcontractors) will satisfy or exceed the following Ground Subsystems Assessment requirements. The offeror shall provide explicit evidence that demonstrates the use of the approach (processes/methodologies) and capabilities on efforts of similar magnitude and complexity within the field of strategic nuclear weapons and how it applies to Ground Subsystems requirements.

a. Performing and reporting nuclear hardness and survivability assessments

b. Performing and reporting nuclear surety assessments

c. Performing and reporting mission reliability assessments

4.2.3.1.5 Aging Surveillance (AS) (PWS 1.6.4.3.3)

The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how their program team (including subcontractors) will satisfy or exceed the following aging surveillance requirements. The offeror shall provide explicit evidence that demonstrates the use of the approach (processes/methodologies) and capabilities on efforts of similar magnitude and complexity within the field of strategic nuclear weapons and how it applies to Ground Subsystems requirements.

a. Providing service life assessments, detecting/quantifying, and reporting aging trends

b. Maintaining an AS database

4.2.3.1.6 Team Structure and Partnerships (PWS 1.6.3.1.6.2, 1.6.3.1.6.2.2, 1.6.3.1.6.2.2.1, 1.6.3.1.6.2.2.2, 1.6.3.1.6.2.2.3) The offeror’s proposal shall provide their intended team structure including partnerships that demonstrate how the offeror will provide the required level of skills and experience to perform the acquisition and sustainment services for this contract. Provide the following:

a. Team organization chart(s) and written explanation, detailing the roles and responsibilities and capabilities of all team members (to include subcontractor, supplier, and interdivisional team). Specifically explain relevance of skills and prior strategic nuclear weapon/ICBM acquisition/sustainment experience of the team, as well as their interdependencies, key relationships, and communication channels.

b. An affirmative statement that the offeror has not entered into an exclusive teaming arrangement as defined in the No Exclusive Teaming Arrangement H Clause.

c. Skill level, education, and strategic nuclear weapon/ICBM acquisition/sustainment experience of key personnel. Provide resumes for all key personnel as a separate attachment to the Technical Volume.

d. The blend of skill sets and strategic nuclear weapon/ICBM acquisition/sustainment experience levels for the remainder of personnel.

4.2.3.1.7 Sample Sustainment Scenario

The offeror shall describe their processes, analysis, and rationale that determine their selected corrective action for the sample sustainment scenario. The offeror shall describe in their solution all actions needed to resolve the situation and what actions they will take that support the Government. The solution shall define the issue, incorporate all appropriate technical documentation and provide full implementation details. The offeror’s solution shall be complete and take into account the necessary actions to maintain/sustain the weapon system throughout its lifecycle. From the list of documents in the Bidder’s Library, the offeror shall document in table format all technical documentation that will be affected with incorporation of the proposed solution.

4.2.3.2 Subfactor 2: Awardable Tasks (Statements of Objectives (SOO))

4.2.3.2.1 Awardable Task 1 – Simulated Electronic Launch Minuteman (SELM)/Guided Missile Launcher Electrical Circuit (GMLEC) (Section J, Attachment 6 (Statement of Objectives))

a. The offeror shall provide their proposed solution, detailing how they satisfy or exceed all SOO requirements to complete the SELM/GMLEC replacement IAW ICBMSD processes. A proposed Contractor Statement of Work (CSOW) shall be included.

b. The offeror shall demonstrate the application of capabilities identified in response to Subfactor 1 Elements: Configuration Management, Hardware Development/Sustainment, and Software Development/Sustainment and any other PWS paragraphs necessary to successfully complete the tasks. The additional PWS paragraphs shall be noted in the solution description.

4.2.3.2.2 Awardable Task 2 - Software Modification Task (Section J, Attachment 9 (Statement of Objectives))

a. The offeror shall provide their proposed solution, detailing how they satisfy or exceed all SOO requirements to complete the software modification task IAW ICBMSD processes. A proposed CSOW shall be included.

b. The offeror shall demonstrate the application of capabilities identified in response to Subfactor 1 Elements: Configuration Management, Hardware Development/Sustainment, and Software Development/Sustainment and any other PWS paragraphs necessary to successfully complete the tasks. The additional PWS paragraphs shall be noted in the solution description.

4.2.3.3 Subfactor 3: Transition

4.2.3.3.1 Tasks and Responsibilities Transfer (PWS 1.6.3.2.3.1, 1.6.3.2.3.2, 1.6.3.2.3.3) The offeror shall provide a transition strategy, describing the approach for transferring responsibilities from the Partial Bridge Contract (PBC) to the GSSC contractor, including identifying how Government-furnished property (GFP), software code and associated compilers, data, documentation, tools, and models can be effectively used in the execution of sustainment and acquisition support requirements while minimizing negative impacts to on-going Ground Subsystems efforts. The approach shall include transition risk identification and mitigation for transitioning Ground Subsystems tasks from the PBC to the GSSC contractor. The proposed approach shall demonstrate how the offeror will assume the full responsibilities of the GSSC effort no later than 6 months after the Post Award Conference.

4.2.3.3.2 Facilities, Equipment, and Qualified Personnel (PWS 1.6.3.2.3.3.1, 1.6.3.2.3.3.2) The offeror shall describe their facilities, equipment, and qualified personnel or their ability to obtain facilities, equipment, and qualified personnel necessary to meet the requirements of the PWS. If the offeror does not have current possession and/or access to these necessary facilities and/or equipment, the offeror shall submit with their proposal an approach for gaining access to and/or establishing the necessary facilities and/or equipment within the 6-month transition period along with supporting information that the offeror is knowledgeable of the work to be performed.

4.2.3.4 Subfactor 4: Program Management Support

The purpose of this subfactor is to assess the offeror’s ability to provide a sufficient level of program management services required to manage the sustainment and acquisition activities for Ground Subsystems.

4.2.3.4.1 Small Business Subcontracting Plan (PWS 1.6.3.1.6.5) The offeror’s proposal shall include a Small Business Subcontracting Plan, detailing their approach to meet subcontracting goals IAW H clause.

4.2.3.4.2 Cost Management Process (PWS 1.6.3.1.4)

The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how they will meet the cost management requirements and provide explicit evidence of following that approach.

4.2.3.4.3 Time Management Process (PWS 1.6.3.1.1.3, 1.6.3.1.3) The offeror’s technical proposal shall provide their approach (processes/methodologies) and capabilities, detailing how they will meet the time management and earned value management requirements and provide explicit evidence of following that approach.

4.2.3.4.4 Quality Management Process (PWS 1.6.3.1.5)

The offeror’s proposal shall provide their capabilities and processes, detailing how they will meet quality management, quality assurance, and quality control requirements and provide and explicit evidence of following these processes.

5.0 Volume III - Past Performance

5.1 General

Each offeror shall submit a Past Performance Volume with its proposal, containing past performance information IAW the format contained in Section L Attachments located in Section J of the solicitation. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners 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. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

5.2 Early Proposal Information

Each offeror is requested to submit the Past Performance Volume (Volume III) 14 calendar days prior to the proposal due date. However, past performance information will be accepted up to the due date. Offerors are required to comply with the Past Performance Information Tool (PPI) IAW Section L Attachment 2. Offerors shall complete Section 1 of the Past Performance Questionnaire (see Section L Attachment 4) and e-mail it and the Performance Questionnaire Cover Letter (see Section L Attachment 3) to all POCs the offeror has listed in the Past Performance Information Sheets (see Section L Attachment 5). The POCs will complete the questionnaires and forward them by email directly to Ms. Jody Lindley at Jody.Lindley@us.af.mil. Respondents to the questionnaires shall not send the completed information sheets back to the offeror! Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The Past Performance Evaluation Team will conduct such follow-up with any POC as necessary. Failure to submit early past performance information will not result in offeror disqualification.

5.2.1 Consent and Client Authorization Letters

The offeror shall submit a consent letter (see Section L Attachment 6, Subcontractor/Teaming Partner Consent Form for the Release of Past Performance Information to the Prime Contractor), signed and executed by the subcontractors, teaming partners, and/or joint venture partners, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall submit a client authorization letter signed by the commercial client (see Section L Attachment 7, Commercial Client Authorization Letter), authorizing release to the Government of information on the offeror's performance.

5.3 Recent/Relevant Contracts

Submit past performance information for five (5) recent contracts (within the past 5 years) for the prime and up to three (3) recent (within the past 5 years) contracts for all subcontractors/teaming partners and/or joint venture partners performing more than 10% of the costs of the contract, considered most relevant in demonstrating an ability to perform the proposed effort. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, provision 2.1 Evaluation Factors, paragraph 2.1.2 Past Performance Factor. Offerors shall use the Roles and Responsibilities Worksheet (see Section L Attachment 8) to indicate how much each team member will contribute towards each Technical subfactor. The data from the worksheet will be used by the Government to determine the past performance relevancy of information provided by the offeror via the Past Performance Information Sheets (see Section L Attachment 5).

5.3.1 Specific Content

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. This 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 (e.g., submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems). Categorize the relevant information into the specific Technical subfactors and Cost/Price Factor 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. A pamphlet or other commercial document describing such reorganizations may suffice. 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 past performance information provided by other sources, as well as that provided by the offeror(s), 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. This historical roadmap will not count against the page limits of Volume III Past Performance.

6.0 Volume IV - Cost/Price

6.1 General Instructions

6.1.1 Cost/Price Reasonableness and Realism

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

6.1.2 Total Evaluated Price (TEP) Pricing Matrix Section J Attachment 13 Offerors shall populate the pricing and cost cells as appropriate. The Government will use this worksheet to calculate the TEP.

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

It is not necessary to propose these CLINs. The CRNF CLINs will be established when requirements become known and funds are available. Actual costs incurred under these CLINs will be reimbursed to the contractor as approved by the ACO.

6.1.3 Labor Rate Matrix, Section J Attachment 15:

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 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 can be found in the Labor Category Descriptions, Section J Attachment 12.

6.1.3.1 Labor Rates. The offeror shall submit one rate to be used for the prime contractor (including interdivisional units, subsidiaries, affiliates, divisions, sectors, groups) and all subcontractor(s). 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.

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

6.1.5 Cost or Pricing Data Requirements

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

6.1.5.2 Facility costs will not be priced separately. Offerors need to account for this cost in their rate structure. For offerors interested in the Enhanced Use Lease (EUL) facility on Hill AFB, the points of contact are Gary Stewart, Sunset Ridge Development – 801-870-2701 – gary.stewart@huntcompanies.com or Travis Lish – Woodbury Corp. – 801-485-7770 – t_lish@woodburycorp.com (note this is t_lish).

6.1.6 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 15. All rates and labor categories shall conform to the Labor Rate Matrix. Provide rationale behind the proposed labor hours, labor mix, and any material considered major under 6.4.1 Major Material Items and Equipment.

6.1.7 Basis of Estimate (BOE)

The offeror shall provide a priced BOE for Cost-Plus Award Fee (CPAF) line items 0001, 0006, 0007, 0010, 0022 (Awardable Tasks 1 & 2) to third level WBS detail. With the exception of the Awardable Tasks to be proposed in accordace with 6.1.6 above, the contractor shall show base labor rate, material (if applicable), a breakout of all indirect rates applied and fee. The offeror shall ensure the statutory requirements of DFARS 216.405-2(3)(iii) are complied with in regard to base fee. Also, indicate the basis for these rates and reference (if applicable) the current Forward Rate Pricing Agreement (FRPA) or audit the rates were taken from. Additionally, the offeror shall provide the rationale behind proposed labor hours, labor mix, and any material considered major under 6.4.1 Major Material Items and Equipment. The organization of this BOE shall follow the offeror’s technical proposal, and be arranged in a logical fashion.

6.1.8…