FA8214-12-R-0001-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE Page 1

2. AMENDMENT/MODIFICATION NO.

FA8214-12-R-0001-0002

3. EFFECTIVE DATE

13 FEB 2012

4. REQUISITION/PURCHASE REQ. NO.

F2DCAH1346B002

5. PROJECT NO (If applicable)

6. ISSUED BY CODE

DEPARTMENT OF THE AIR FORCE, DIRECTORATE OF CONTRACTING

AFNWC PKMA

6014 DOGWOOD AVENUE BLDG 1258

HILL AIR FORCE BASE UT 84056-5816

BUYER: Kirk A Dean kirk.dean@hill.af.mil Phone: (801) 777- 5668 Fax: (801) 777-0990 No Collect Calls

7. ADMINISTERED BY (If other than item 6) CODEFA8204

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

CODE

X

9A. AMENDMENT OF SOLICITATION NO.

FA821412R0001

9B. DATED (SEE ITEM 11)

9-JAN-2012

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods. ( a ) By completing Items 8 and 15, and returning copies of the amendment; ( b ) By acknowledging receipt of this amendment on each copy of the offer submitted; or ( c ) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return 3 copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

ROUTINE

See Page 2.

15A. NAME AND TITLE OF SIGNER (Type or print)

15B. CONTRACTOR/OFFEROR

BY ________________________________________________________

(Signature of person authorized to sign)

15C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16B. UNITED STATES OF AMERICA

BY ____________________________________________________

(Signature of Contracting Officer)

16C. DATE SIGNED

FACILITY CODE

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE

30-105 STANDARD FORM 30 (REV. 10-83)

PRESCRIBED BY GSA

FAR (48 CFR) 53.243

X

X X

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

Amendment/Modification FA8214-12-R-0001-0002

Continuation of block 14. DESCRIPTION OF AMENDMENT/MODIFICATION

The purpose of this amendment is to:

1) Replace the previous ISC Performance Work Statement (PWS) dated 9 Jan 2012 with the attached PWS Rev 01, dated 13 Feb 2012.

Changes: Sections 1.6.2.10, 1.6.2.11 and 1.6.5.3 modified; CDRL table updated

2) Add the following H-Clauses: 9952.737-H737 - Distribution Control of Technical Information 9952.738-H738 - Commercial Computer Software License 9952.739-H739 - Data Delivery or Otherwise Furnished by the

Contractor

3) Replace the previous CDRLs A049, A084, A088, A124, A128 and A130 dated 12 Dec 2011 with the attached CDRLs A049, A084, A088, A124, A128 and A130 dated 10 Feb 2012.

Changes: CDRL A049: Changed Block 3 to Data Transition Plan CDRL A084: Added 1.6.2.11.2 to Block 5 CDRL A088: Added 1.6.2.11.2 to Block 5 CDRL A124: Changed block 5 to 1.6.2.11.2 CDRL A128: Changed block 5 to 1.6.2.11.5 CDRL A130: Changed block 5 to 1.6.2.11.6

4) Add the following CDRLs dated 10 Feb 2012, as attached.

A131 - Technical Requirements Document A132 - Command Media

5) Add the following clauses: 252.227-7014 - Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation

252.227-7027 - Deferred Ordering of Technical Data or Computer Software

6) Replaced the previous Section L.

Changes: Added reference of PWS paragraph 1.6.2.11 to the Data Transition and Hosting section under paragraph 4.2.4

7) Attach Section K - Attachment 1 - Identification and Assertion of Use, Release, or Disclosure Restrictions. See Section K Provision 252.227-7017.

Request for Proposal FA8214-12-R-0001-0002

PART I - THE SCHEDULE

SECTION H

SPECIAL CONTRACT REQUIREMENTS

9952.737-H737 DISTRIBUTION CONTROL OF TECHNICAL INFORMATION (FEB 2012)

a. The following terms applicable to this clause are defined as follows:

1. Technical Document. Any recorded information (including software) that conveys scientific and technical information or technical data.

2. Scientific and Technical Information. Communicable knowledge or information resulting from or pertaining to the conduct or management of effort under this contract. (Includes programmatic information).

3. Technical Data. Recorded information related to experimental, developmental, or engineering work that can be used to define an engineering or manufacturing process or to design, procure, produce, support, maintain, operate, repair, or overhaul material. The data may be graphic or pictorial delineations in media such as drawings or photographs, text in specifications or related performance or design type documents, or computer printouts. Examples of technical data include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, meeting minutes, catalog item identifications, and related information and computer software documentation.

b. Except as otherwise set forth in the Contract Data Requirements List (CDRL), DD Form 1423, or paragraph e.

below, the distribution of any technical documents prepared under this contract, in any stage of development or completion, is prohibited outside of the contractor and applicable subcontractors under this contract unless expressly authorized/directed by the Contracting Officer in writing

c. Except as otherwise set forth in the CDRL or otherwise directed by the Government (e.g., paragraph d. below) all technical documents prepared under this contract shall be marked with the following distribution statement, warning, and destruction notice:

1. DISTRIBUTION STATEMENT D: Distribution authorized to DoD and U.S. DoD contractors only for administrative or operational use, 10 February 2012. Refer other requests for this document to AFNWC/NIE, 6054 Dogwood Ave, Bldg 1255, Hill AFB, UT 84056-5816.

2. WARNING - This document/software contains technical data/software whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or the Export Administration Act of 1979, as amended, (Title 50, U.S.C., App 2401 et seq). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DOD Directive 5230.25.

3. DESTRUCTION NOTICE - For classified documents, follow the procedures in DOD 5220.22M, National Industrial Security Program Operating Manual, Chapter 5, Section 7, or DOD 5200.1R, Information Security Program Regulation, Chapter 6, Section 7. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

d. The prime and subcontractors are authorized to use technical documents generated or held under this contract for purposes of this contract or any other AFNWC contract, solicitation or program and to flow such technical documents to each other, DOD officials and other DOD contractors having a need to know in connection with this contract or any other AFNWC contract, solicitation or program. When there is any doubt as to ¯need to know for purposes of this paragraph, the Contracting Officer‘s Representative (COR) will provide direction. The authorization provided by this paragraph e. is subject to strict compliance with contract security requirements, export control requirements, contractor proprietary restrictions/markings and/or the provisions of any applicable non-disclosure agreements which may be in effect.

9952.738-H738 COMMERCIAL COMPUTER SOFTWARE LICENSE (FEB 2012)

a. Unless otherwise approved by the PCO, commercial computer software licenses shall designate the Government as a primary or contingent licensee, able to replace the contractor as the primary licensee upon notifying the licensor. A copy of the negotiated license shall be furnished to the PCO. Per DFARS 227.7202, the terms of the licenses must be consistent with Federal procurement law and must satisfy user needs. This includes the contractor's / subcontractor's needs for the software to perform this contract and the Government's needs for the software to accomplish the Government's ultimate objectives. At a minimum, this shall include the rights to make an archive copy of the software, to relocate the computer on which the software resides, to re-host the software on a different computer, to permit access by support contractors, and to permit the Government to transfer the license to another contractor.

b. Nothing in this clause shall take precedence over any other clause or provision of this contract. Government concurrence, as defined in paragraph a. above, does not in any way affect the Government's technical data rights as established by the terms and conditions of this contract.

9952.739-H739 DATA DELIVERED OR OTHERWISE FURNISHED BY THE CONTRACTOR (FEB 2012)

a. All technical data delivered, or otherwise furnished to the Government, including data on the contractor‘s Integrated Data Environment (IDE) shall be marked in accordance with DFARS 252.227-7013 and associated DFARS.

In the same manner, the contractor shall comply with and provide the Government rights in noncommercial computer software and noncommercial software documentation, both developed and or procured, in accordance with DFARS

252.227.7014 and associated DFARS provisions. Data shall be marked only with conforming and justified markings in accordance with DFARS requirements at the time it becomes accessible to the Government. Note that “proprietary” or similar markings are non-conforming markings. The contractor shall take all steps necessary to ensure the Government obtains appropriate rights in all data from both the contractor and subcontractors at any tier, including the inclusion of adequate contract clauses in all subcontracts and the flow down of such clauses to subcontracts at any tier. Limited or Restricted rights technical data or computer software or computer software documentation as specified in DFARS 252.227-7013 and 252.227-7014 shall NOT be delivered or otherwise furnished by the contractor under or in conjunction with this contract without prior approval of the Contracting Officer or the Contracting Officer‘s Representative. The Contractor shall ensure that quality control procedures are in place to validate accuracy of electronically transmitted data or data otherwise furnished to the Government, including formats, date of delivery and method of data delivery.

b. Contract Data Requirements List (CDRL) deliverables include CDRL items referenced in the PWS and Section J of this contract. The contractor shall officially deliver unclassified CDRL data electronically to the Government’s IDE.

Data is not considered delivered and billable until such time as it’s approved as required and assigned a data item number and is indexed in the Government’s IDE. Unclassified CDRL data may also be required to be delivered to additional addresses, as specified in Block 16 of the DD Form 1423. If electronic delivery to the Government via the methods above is not possible, the contractor shall deliver the CDRL data to the Government, to the recipient identified in the CDRL 1423, via encrypted email or other physical media (e.g., CD or DVD). In addition, CDRLs and other unclassified correspondence related to this contract shall be posted to the contractor‘s IDE, furthermore the subcontractor shall maintain an internal repository (IDE) of data developed under this contract. Upon government request, the contractor shall be able to reproduce any data developed under this contract quickly, efficiently and at low cost. In the event that the metadata structure (database fields, etc) of the contractor’s IDE differs from the Governments, the contractor shall notify the Government and recommend updates to the Government’s IDE to ensure compatibility across IDE’s.

c. Authorized government agents shall have unrestricted access to the contractor’s IDE, including the contents of the DAL (CDRL A130). In accordance with CDRL A130 and DI-MGMT 81453, data that is indexed on the DAL shall be marked in accordance with 252.227-7013 prior to being indexed on the DAL. The DAL shall be updated continuously to ensure integrity of data and markings. DAL data and documents shall be kept separate (by database field or otherwise) from all other contract data. In the event that the Government requires data from the DAL, it will be requested using the deferred ordering clause, 252.227-7027 as required.

d. The contractor shall deliver classified CDRL data IAW the DD254 and DoD 5220.22M.

e. All data transmitted to the Government shall be of sufficient quality that the Government is able to read the data both online and in printed form. If the Government receives a document that has quality/readability issues, the contractor shall make the necessary corrections prior to the data be accepted and archived by the Government. In the event that the Government receives data that cannot be accessed without uncommon software, the contractor will also provide information regarding the format of the data, including the proper software for accessing the data (this should be a rare circumstance). The contractor shall work efficiently and effectively to correct any and all quality issues.

f. Data shall be delivered or otherwise furnished to the Government virus-free and in a searchable, manipulative and editable format, including Microsoft Word, Excel, PowerPoint, Project and/or Access. Adobe (.pdf files), picture files, and other electronic image media are acceptable only if allowed in Blocked 16 of the DD Form 1423 for a given data item. If files contain links, the links must be intact and maintained throughout all revisions. Delivered data, including presentations and reports, shall not contain embedded proprietary contractor pricing information. All proprietary cost and pricing information should be included by attachment referenced in the body of data. The purpose of this restriction is to eliminate situations where entire data items have limited data rights as a result a single or minor inclusion of proprietary cost and pricing data. By separating the limited rights data into an attachment, larger bodies of data can remain unlimited while referencing limited rights data as required. Unclassified documents shall not contain embedded classified information.

PART II - CONTRACT CLAUSES

SECTION I

CONTRACT CLAUSES

252.227-7014 RIGHTS IN NONCOMMERCIAL COMPUTER SOFTWARE AND NONCOMMERCIAL

COMPUTER SOFTWARE DOCUMENTATION (MAR 2011)

(IAW DFARS 227.7203-6(a)(1))

252.227-7027 DEFERRED ORDERING OF TECHNICAL DATA OR COMPUTER SOFTWARE

(APR 1988)

(IAW DFARS 227.7103-8(b))

PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

SECTION J

LIST OF ATTACHMENTS

Form Number Description/File Name Date Number of Pages N/A ISC Performance Work Statement (PWS) Rev

13FEB2012 112

DD 1423 Updated Contract Data Requirements List

(CDRL)

CDRLs A049, A084, A088, A124, A128, A130, A131 and A132

10FEB2012 8

N/A Section K Attachment 1 Identification and Assertion of Use, Release, or Disclosure Restrictions

UNDATED 7

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

L-I - SOLICITATION PROVISIONS IN FULL TEXT

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

52.215-1 INSTRUCTIONS TO OFFERORS--COMPETITIVE ACQUISITION

(In accordance with (IAW) FAR 15.209) The Government intends to evaluate proposals and award a contract without discussions with Offerors, however the Government reserves the right to conduct discussions.

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

1.0 Program Structure and Objectives

The Government intends to award a single contract for the Integration Support Contract (ISC). The contractor will perform Engineering and Program Management Support services referenced in the PWS.

2.0 General Instructions

a. This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested and must be submitted in accordance with these instructions. Any Offeror who submits an incomplete package may be considered non-responsive. The Offeror shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Fixed-Price Labor Hour Rate Matrix, CLIN Pricing Matrix, Contract Data Requirements List (CDRL), and Solicitation. Non-conformance with the instructions provided in this ITO will 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. Responses that simply restate the PWS requirements provided by the Government may be rated less favorably since they do not effectively present the case for how the Offeror will accomplish those requirements. It is required that any reasonable response show, by citing applicable experience, quality and education of personnel, policies, practices, procedures, standards, software systems, tools, facilities, plans, or other means of achieving results, exactly how the Offeror will accomplish the designated requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information provided in the Offeror's proposal.

c. The Offeror shall provide the details of experience of both their company and the key personnel proposed to perform the technical requirements. The Offeror must also provide the policies, practices, tools, software systems, management systems and facilities to depict how they will perform each requirement.

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

e. 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 through this date.

f. 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 Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to Mr. Kirk Dean at 6014 Dogwood Ave, Bldg 1258, Hill AFB, UT 84056-5820 or via e-mail to the following:

Kirk.Dean@hill.af.mil. Bidder comments and questions will be received by the CO via e-mail and answers will be published on the Federal Business Opportunities (FBO) website.

2.1.2. Debriefings

The CO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. After award, the CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.1.3. Discrepancies

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

2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the FBO website at http://www.fbo.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The Integration Support Contract (ISC) FBO web page is https://www.fbo.gov/index?s=opportunity&mode=form&id=a4135a2b0ffc7dbc3d765bad6d12c719&tab=core&_cview=

1. Technical documents not available electronically will be made available through the Bidder’s Library IAW para 2.1.5.

2.1.5 Classified Bidder’s Library/Vault

The Classified Bidder’s Library will reside within the vault of Building 1258. It will consist of only hard copies of classified documents. Visits are by appointment only (see contact information in the next paragraph) to view classified or other restricted access documentation that only exists in hard copy form in the ICBM SPO vault. The library will be open, during normal business hours, Monday through Thursday for nine hours (0700-1600) per day and seven hours (0700-1100 and 1200-1500) on Friday. All contractors will be treated equally, and will be provided access to the documents/information as requested. The library will consist of data that the SPO believes is necessary to write a proposal. Offerors are encouraged to check the data list prior to setting an appointment. Requests for additional data will be considered and a decision rendered. 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 on is 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.

Each contractor will be limited to three (3) two-hour visits. All visits must be scheduled, through Joint Personnel Adjudication System (JPAS), using the Security Management Office (SMO) code HP1MFGKQ, with the FISAC Data POC, Mr. Paul Catmull (Paul.Catmull@hill.af.mil) or his alternate, Mr. Thom Ganey (Thomas.Ganey@hill.af.mil).

Visitors must have, at a minimum, a secret clearance.

2.1.6 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Otherwise, source selection information will be transmitted via other means as appropriate.

2.1.7 Oral Presentation – Oral presentations will not be allowed.

2.1.8 Amendments to Solicitation – If this Request for Proposal 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.9 Submission, modification, revision, and withdrawal of proposals

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

2.1.9.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.9.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.2 Organization/Number of Copies/Page Limits

2.2.1 The title page of each volume must show:

Solicitation Number Name, address, telephone and e-mail address of the Offeror.

Volume number and name (e.g. Volume I, Technical Volume and copy number (i.e. Original, copy 1, copy 2, etc.)).

2.2.2 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. The Executive Summary can be combined with the Technical volume binder, but does not count against the Technical volume page limit. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.2 - Proposal Organization

VOLUME ITO

Paragraph Number

VOLUME TITLE SOFT

COPIES

HARD

COPIES

PAGE LIMIT

(not to exceed) I 3.0 Executive Summary 2 6 4 II 4.0 Technical

- Sample Problem response (max

10 of 175 pages)

- Transition Plan (max 20 of 175 pages)

- Management Plan that includes the Human Resources Plan (max 15 of 175 pages) Note: Resumes do not count towards page limit. The Small Business Subcontracting Plan and Compensation Plan for Professional Employees will be part of Volume V.

2 6 175

III 5.0 Past Performance Note: Consent letters do not count towards page limit

2 3 6 per PPIS

IV 6.0 Cost/Price 2 3 unlimited

V 7.0 Contract Documentation 2 3 unlimited

2.2.3 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 forwarding the ENs to the Offerors. Each page shall be counted except the following: blank pages, title pages, tables of contents, tabs, glossaries, resumes provided as part of the Human Resources Plan, and those noted in the Proposed Organization Chart as unlimited.

2.2.3.1. Page Size and Format

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, and shall be printed double-sided. Pages shall be typed with 1.5 line spacing. Except for the reproduced sections of the solicitation document, the text size shall be 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 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and 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. These limitations shall apply to both electronic and hard copy proposals.

2.2.3.2 Cost or Pricing Information

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

2.2.3.3 Classified Information

Classified information is not to be submitted in the proposal. A DD Form 254 is required for the performance of this contract.

2.2.3.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The Offeror shall 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 L – Attachment 7).

2.2.3.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.3.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each.

Glossaries do not count against the page limitations for their respective volumes.

2.2.3.7 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. The outside of each binder shall include a cover sheet, clearly marked as to 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 in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

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. 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 in a different directory 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, MS Office Excel 2007, MS Office Project 2003 (and Primavera P6), and MS Office Power Point 2007, 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. 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. 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 is not necessary.

2.4 Distribution

The original proposal shall be identified. The proposal shall be addressed to the CO and mailed to:

AFNWC/PKMA

Attn: Mr. Kirk Dean 6014 Dogwood Avenue Hill AFB, UT 84056-5820 Kirk.Dean@hill.af.mil

2.5 Proposal Inquiries

All inquiries must be submitted via e-mail to the CO listed above. Questions will be answered as quickly as possible, during the proposal preparation period.

3.0 Volume I - Executive Summary

In the executive summary volume, the Offeror shall provide the following information:

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material provided 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 important. Offeror’s responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award, as well as the PWS. Using the instructions provided below, provide, as specifically as possible, the actual methodology to be used for accomplishing/satisfying the Technical subfactors and the requirement found in the PWS. All the requirements specified in the solicitation are mandatory. This proposal submission represents commitment to accomplishing and satisfying all the requirements specified in this solicitation. It is necessary to provide the processes (including procedures, methods, and tools) to be used to accomplish/satisfy the requirement. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation or the PWS.

4.2 Format and Specific Content

4.2.1 Technical

In the Technical Volume, address the proposed approach to meeting or exceeding the minimum performance or capability requirements of each Technical subfactor, as well as the risks in the proposed approach in terms of technical performance, cost, and schedule.

4.2.1.1 Risk Identification

Address risks by identifying those aspects of the proposal which have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract 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 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.

4.2.2 Volume Organization

The Technical Volume shall be organized to follow the outline of the PWS and shall address each PWS requirement while still addressing, in more detail, the subfactors below. The Offeror’s proposal shall specifically address the PWS paragraph 1.6 REQUIREMENTS and all of its subparagraphs. Offerors shall not address Appendix “C” 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 prior to contract start date. Offerors may use a numbering system that is convenient for the proposal organization; however, to ease the evaluation process, sections shall be identified in both name and PWS section reference, if applicable, for each required section of the PWS (e.g. 1.6.1.2.1 Weapon System Assessment in the PWS shall have a corresponding section Weapon System Assessment (PWS Section 1.6.1.2.1) in the Offeror’s Proposal).

Sections from the PWS shall be addressed in the order in which they appear in the PWS. An exception to this will be if the Offeror chooses to “bundle” the requirements to show the interrelationships of the requirements. In these cases, it is necessary to clearly and accurately indicate those requirements (by paragraph number) being addressed. Plans should be included as separate appendices and will count against the Technical Volume page limit.

Subfactors – As stated above, the Technical Volume shall be organized to follow the outline of the PWS and shall not follow the outline of the Subfactors below. The Subfactors are provided to show emphasis areas that should be addressed in more detail within the PWS organized Technical Volume.

4.2.3 Subfactor 1: Systems Engineering

The transition from the current IPIC to the FISAC end state will be heavily reliant upon the ISC for success. A key capability of the ISC will be to provide systems engineering to enable the ICBM SPO to be the weapon system integrator. The Offeror shall provide details that clearly demonstrate evidence of the full capability and extensive experience their team possesses for executing systems engineering to meet the PWS requirements. The Offeror’s proposal shall address the following PWS paragraphs and all of their subparagraphs:

a. WEAPON SYSTEM SUSTAINMENT (PWS 1.6.1)

b. PROGRAM MANAGEMENT SUPPORT (PWS 1.6.2)

c. FDE SUPPORT (PWS 1.6.3)

d. KNOWLEDGE TRANSFER (KT) (PWS 1.6.4)

Special Emphasis will be given to processes for performing:

- Nuclear Surety (PWS 1.6.1.1.1)

a. To satisfy the nuclear surety requirements and demonstrate a level of competence in execution that ensures the nuclear surety needs of the weapon system will be met.

b. To support the SPO and interface with subsystem contractors to ensure nuclear surety is maintained across all interfaces and in all interactions.

c. To identify and address nuclear surety shortfalls across the ICBM Weapon System enterprise.

- Systems Current Capability Maturity Model Integration (CMMI) level 3 or equivalent (SEAM qualification for systems engineering in PWS 1.6.1.1)

- Systems Effectiveness (PWS 1.6.1.1.4)

- System Requirements Analysis and Determination (PWS 1.6.1.1.6)

- Hardware and Software Sustaining Engineering (PWS 1.6.1.2)

4.2.3.1 Sample Problem

The government will also evaluate the Offeror’s response to a Sample Problem to determine the Offeror’s understanding of a nuclear missile system and assess the effect their understanding has on the risk the Offeror can successfully execute the proposed approach. Response to the Sample Problem should be included as a separate appendix and is included in the Technical Volume page count.

4.2.4 Subfactor 2: Transition

The purpose of this subfactor is to establish the Offeror’s capability to effectively manage the transition from the ICBM Prime Integration Contract (IPIC) to a new sustainment contract with multiple SPO managed contracts to minimize risks to the weapon system. The Offeror’s proposal shall address the following PWS paragraph and its subparagraphs:

TRANSITION (PWS 1.6.5)

Special Emphasis will be given to processes for performing the following:

Note: Human Resource Plan 1.6.5.2 will be evaluated under 4.2.5 Subfactor 3: Management.

Transition Risk Identification and Mitigation:

The Offeror shall identify risks and mitigating activities:

a. Identify the risks for transitioning tasks from the Partial Bridge contract to the ISC.

b. Provide the analysis, scoring, and ranking of the identified risks and the criteria used.

c. Propose the mitigation strategies to overcome the identified transition risks.

Transition Plan (PWS 1.6.5.1)

a. An initial proposed schedule, by task, with proposed exit criteria, showing when responsibility for the task will be transferred from the Partial Bridge contract to the ISC.

b. Indicate coordination and integration activities anticipated.

Data Transition and Hosting (PWS 1.6.2.11 and 1.6.5.3) Propose a detailed two-step approach for identifying the requirements and developing a solution to address the requirements. Actual identification of the requirements, development and implementation of the solution will be done following ISC contract award. Specifically address:

a. Gap analysis with the Government and the incumbent in a coordinated effort to identify and transition the required data, tools, and models used in support of the successful assessment, sustainment, and maintenance of the weapon system.

b. Development or creation of tools/models that are unavailable, and validating the results with historical data.

c. Capture or replication of relevant data needed to perform integration tasks and ensuring successful sustainment and maintenance of the weapon system.

d. Hosting and storing ICBM weapon system data.

e. Transferring ICBM weapon system data to the Government prior to completion of the ISC PoP.

f. Identification and retrieval of critical documents, drawings, and other program technical historical and reference data.

g. Scheduling of the key data transition elements and milestones.

h. Sharing of data in an integrated data environment.

i. Version Control

4.2.5 Subfactor 3: Management

The purpose of this subfactor is to establish the Offeror’s ability to develop plans and appropriately staff and manage their organization to meet the requirements of the PWS.

Special Emphasis will be given to:

Management Plan:

The Contractor shall be responsible for managing all aspects of the contract, to include cost, schedule, performance, and contract management. The Contractor shall ensure integration of all technical and program elements detailing:

a. Offeror’s organizational structure to include identification of key positions.

b. Interactions that will occur between the contractor organization and the ICBM SPO, AFGSC, Subsystem contractors, and the transition contracts (i.e. F-900 IPIC contract clause and Partial Bridge contract).

c. Plan to incorporate continuous process improvement in execution of the ISC.

d. Small Business Subcontracting Plan. This plan will be used to establish the Small Business

Subcontracting goals and requirements (see H-133, Small Business Subcontracting Requirements clause). This plan will be submitted as part of the Volume V, Contract Documentation.

Human Resource Plan (PWS 1.6.5.2)

a. How critical skill sets and experience will be identified.

b. How critical skill sets and experience will be acquired for Offeror’s staff.

c. Methodology for determining labor category mix, by percent, used in proposing Contractor Manpower

Equivalents (CME) for Sustaining Engineering (CLINs X001), FDE Support (CLINs X020), Demonstration/Validation Support (CLINs X040), and Fuze Support (CLINs X101), demonstrating their understanding of the requirement.

d. How Offeror will work with all stake holders to minimize disruption in ongoing activities during recruiting efforts.

e. How Offeror will retain critical skill sets / experience and transfer knowledge/skills within their workforce.

f. What portions of this plan have already been implemented by the Offeror and address the results.

g. Resumes for individuals identified in the contractors Key Personnel Qualification Guidelines (PWS 4.11) and other key positions identified by the Offeror.

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 J. This information is required for the Offeror and major subcontractors, teaming partners, and/or joint venture partners proposed by the Offeror to perform the work outlined in the solicitation (“major” for past performance purposes is defined as performing greater than 10% of the total annual effort). 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.1.1 Consent and Client Authorization Letters - The Offeror shall submit a consent letter (see Section L- Attachment 4), 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 5), authorizing the release of requested information on the Offeror's performance to the Government.

5.2 Early Proposal Information

Each Offeror is requested to submit the Past Performance Volume (Volume IV) 14 calendar days prior to the proposal due date. However, past performance information will be accepted up to the due date without negative ramifications.

Offerors shall complete Section 1 of the Past Performance Questionnaire (see Section L- Attachment 3) and e-mail it and the Performance Questionnaire Cover Letter (see Section L- Attachment 2) to all points of contacts (POCs) the Offeror has listed in the Past Performance Information Sheets (see Section L- Attachment 1). The POCs will complete the questionnaires and forward them by e-mail directly to Mr. Kirk Dean at Kirk.Dean@hill.af.mil. Offerors should attempt to have Past Performance Questionnaires submitted 14 calendar days prior to the proposal due date; however, questionnaires submitted after the proposal due date will still be accepted. 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.

5.3 Recent/Relevant Contracts

Submit past performance information for up to 5 recent contracts for the prime and up to 3 recent contracts for major subcontractors, teaming partners, and/or joint venture partners 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 Evaluation Factors, Past Performance Factor. Offerors shall use the Roles and Responsibilities Worksheet (see Section L- Attachment 6) 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 1).

5.3.1 Specific Content

Offerors are required to provide rationale for those aspects of the contracts deemed relevant to the proposed effort and specifically, to which 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. The Offeror is required to clearly identify actions taken to overcome problems and the impacts of those actions in terms of improvements achieved, solutions reached, or problems resolved.

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 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 description of all such changes in the organization of your company. Show how these changes impact the relevance of any efforts identified 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), the description should be specifically applicable to the efforts identified.

6.0 Volume IV - Cost/Price

6.1 Primary Purpose

The primary purpose of the cost proposal is to provide the Government with a clear understanding of how the cost estimates and prices were developed.