FA8307-14-R-0002-0001.pdf

SCHEDULE OF CHANGES

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

28 APR 2014

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFLCMC/HNCKA CODE FA8307 7. ADMINISTERED BY (If other than Item 6) CODE

AFLCMC/HNCK

CYBER/NETCENTRIC DIRECTORATE

230 HALL BLVD, STE 114

SAN ANTONIO, TX 78243-7007

KELLEN J. CURRY 210-925-2861

kellen.curry.1@us.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

FA8307-14-R-0002

X

9B. DATED (SEE ITEM 11)

15 JUL 2014

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, X 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 0 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 ITEM APPLIES ONLY TO MODIFICATION OF CONTRACTS/ORDERS,

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

(X )

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

10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE 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 copies to the issuing office.

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

1. The purpose of this Amendment is to clarify the Pre-Proposal Conference start time and correct the fax number for solicitation responses.

2. The start time annotated in AFFARS Clause 5352.215-9001, Notice of Pre-Bid/Pre-Proposal Conference (MAY 1996) - Alternate I (MAY 1996) (TAILORED), is hereby changed from 10:00am CST to 08:00am CST.

3. The fax number in Section L, Para 2.1.1. (Point of Contact) is hereby changed from 210-925-1143 to 210-925-2463.

4. All other terms and conditions remain unchanged.

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.

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

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

LORI A. ROBARGE

15B. CONTRACTOR/OFFEROR

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.14.0 FAR (48 CFR) 53.243

Created 28 Apr 2014 10:54 AM

LIST OF ATTACHMENTS

FA8307-14-R-0002 0001

DOCUMENT PGS DATE TITLE

ATTACHMENT 13 70 28 APR 2014 SECTION L, PROPOSAL PREPARATION

INSTRUCTIONS

FA8307-14-R-0002 Attachment 13

Section L: Instructions, Conditions and Notices to Offerors

28 April 14

Section L – Instructions, Conditions and Notices to Offerors

PROPOSAL PREPARATION INSTRUCTIONS

INFORMATION TO OFFERORS (ITO)

DEFINITIONS: The following terms when italicized in the text of Sections L & M, and their definitions/acronyms, shall be applicable to this Request For Proposal (RFP) only.

Offerors shall use these definitions/acronyms while preparing proposals for this acquisition.

Critical Component – A component which is or contains Information and Communication

Technology (ICT) including hardware and software, whether custom, commercial, or otherwise developed, and which delivers or protects mission-critical functionality of a system or which, because of the system’s design, may introduce vulnerability to the mission critical functions of a covered system.

Information and Communication Technology (ICT) – Includes all categories of ubiquitous technology used for the gathering, storing, transmitting, retrieving, or processing of information

(e.g., microelectronics, printed circuit boards, computing systems, software, signal processors, mobile telephony, satellite communications, networks, etc.). ICT is not limited to information technology (IT) as defined in section 11101 of title 40, U.S.C., rather this term reflects the convergence of IT and communications.

Integrator – The company(s) contracted by a Platform Program Management Office to install

Mini Crypto (MC) devices into a host platform.

Key Interfaces – Common boundaries shared between system modules that provide access to critical data, information, material, or services; and/or are of high interest due to rapid technology change, a high rate of failure, or costliness of connected modules; or are important from an interoperability standpoint.

Mission-Critical Functions – Any function, the compromise of which would degrade the system’s effectiveness in achieving the core mission for which it was designed.

Operational Effectiveness – The overall degree of mission accomplishment of a system when used by representative personnel in the environment planned or expected for operational employment of the system considering organization, training, doctrine, tactics, survivability, vulnerability, and threat. (CJCSI 3170.01)

Operational Suitability – The degree to which a system can be placed and sustained satisfactorily in field use with consideration given to availability, compatibility, transportability, interoperability, reliability, wartime usage rates, maintainability, environmental, safety and http://acqnotes.com/Career%20Fields/Evaluation%20of%20Survivability.html occupational health risks, human factors, habitability, manpower, logistics, supportability, logistics supportability, natural environmental effects and impacts, documentation, and training requirements. (CJCSI 3170.01)

Operator – Refers to the operating command which is the primary command operating a system, sub-system, or item of equipment. Generally applies to those operational commands or organizations designated by Headquarters, US Air Force to conduct or participate in operations or operational testing, interchangeable with the term "using command" or “user.” In other forums the term “warfighter” or “customer” is often used. (AFI 10-601)

Realistic – Achievable based on known facts within the program’s time and resources limitations.

Relevant Environment – The specific subset of the operational environment that is required to demonstrate critical "at risk" aspects of the final product performance in an operational environment. It is an environment that focuses specifically on stressing the technology in question. Note: A relevant environment is required for Technology Readiness Levels 5 and 6.

Reference CPSD TRA Guidance for supporting information as necessary.

Size, Weight and Power (SWaP) – Actual spatial dimensions expressed in length (cm) X width

(cm) X height (cm) (size), measure of heaviness expressed in grams (weight) and the rate of transferring energy expressed in milliwatts (power) for MC as specified in the System

Requirements Document (SRD).

Software – The programs, routines, and languages that control the functioning of the hardware and direct its operation. The programs used to operate the systems to include application software, system/subsystem software, firmware, and middleware.

Sound – When used in a program management context, the artifact is well constructed, (i.e., has all necessary components in proper relationship to each other). When used in a technical or design context, is logically valid, based on proven engineering principles that have been tested and proven to be free from defect.

Substantiate – Support with proof of evidence or provide relevant analysis, i.e. trade-off studies for design approach or technology selection, test data, test reports, commercial/government standards, or product specifications.

Supply Chain Risk – The risk that adversaries will insert malicious code into or otherwise subvert the design, manufacturing, production, distribution, installation, or maintenance of ICT components that may be used in DoD systems to gain unauthorized access to data, to alter data, to disrupt operations, or to interrupt communications.

Supply Chain Risk Management (SCRM) – A systematic process of identifying susceptibilities, vulnerabilities and threats throughout DoD’s “supply chain” and developing of mitigation strategies to combat those threats whether presented by the supplier, the supplied product and its subcomponents, or the supply chain.

Tactical Key Management (TKM) – The use of the robust flexible keying capabilities that shall not require the use of classified pre-placed materials and traditional manual Key loading devices by using a combination of asymmetric Keys and ephemeral Random Key Generation internal to the MC module.

Team Members – Group consisting of the prime contractor and all first-tier subcontractors as evidenced in a signed Teaming Agreement (TA) or Letter of Intent (LOI) proposing to perform any of the work defined in section L, Table 4-1 Team Members.

1 Program Structure and Objectives

(a) The Government intends to award one (1) contract. The Government reserves the right to make more awards or none based on the quality and quantity of proposals received and/or funding availability for this program.

(b) The Offeror shall submit no more than one (1) proposal.

2 General Instructions

2.1 General Information

2.1.1 Point of Contact

(a) The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition.

(b) Address any questions or concerns you may have to the PCO.

(c) Written requests for clarification may be sent to the PCO via fax or email.

(d) Email is the preferred method of communication.

The PCO for this acquisition is as follows:

Lori A. Robarge

320 Hall Blvd, Suite 100

San Antonio, TX 78243-7058 lori.robarge@us.af.mil

FAX: 210- 925-2463

2.1.2 Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the PCO in writing with supporting rationale immediately, but no later than 10 work-days after release of the RFP.

2.1.3 Transmittal of Sensitive or Classified Attachments

(a) Sensitive or classified Section J Attachments 5, 9, 10, and 12 will be transmitted directly only to qualified Offerors. To obtain the attachments stated above, the System Security Officer for each Offeror intending to propose as a prime contractor must notify the contracting officer by email (see paragraph 2.1.1) as soon as possible and provide the following information:

• Company name

• Addresses where proposal work will be performed

• CAGE Codes

• Security points of contact for receiving the RFP attachments, including address, e-mail address, and telephone and fax numbers

• Delivery address to accept sensitive or classified attachments

(b) A current U.S. SECRET facility clearance and storage capability is required for proposal development.

mailto:lori.robarge@us.af.mil

(c) After the request is received with the information listed above and upon verification of the required facility clearance and storage capability, Section J Attachments 5, 9, 10 and 12 will be mailed via U.S. Postal Service registered mail or the current Government approved express delivery service.

(d) Exchanges of source selection information between Government and Offerors will be controlled by the Contracting Officer. 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.

2.2 Organization/Distribution/Number of Copies/Page Limits

(a) Table 2.1 Proposal Organization

(1) The Offeror shall prepare the proposal as set forth herein.

(2) The titles and contents of the volumes shall be as defined in this section.

(3) All titles and contents shall be within the required page limits and within the number of copies as specified.

(b) Specific format requirements are identified in paragraph 2.3 Proposal Format.

(c) The contents of each proposal volume are described in the ITO paragraph as noted in Table

2-1 below.

(d) In the event that this table conflicts with the detailed instructions in the paragraphs that follow, the detailed instructions shall take precedence.

(e) In compliance with Federal Acquisition Regulations (FAR) Subpart 4.8 (Government

Contract Files), the Government will retain one copy of all unsuccessful proposals. The

Government will destroy any extra hard copies of such unsuccessful proposals.

Table 2-1: Proposal Organization

ITO PARAGRAPH NUMBER 2.3.10.3 2.3.9.1 2.3.9.2 2.3.9.3

VOLUME

ITO

Paragraph

Number TITLE

PAGE

LIMIT

ORIGINAL

UNBOUND

HARD

COPIES

E-

COPIES

3 VOLUME I – CONTRACT DOCUMENTATION

I

3.1 Executive Summary 5

1 3.2(a) Master Table of Contents Unlimited

3.2(b) Table of Contents file://52mpls-fca-001/cpsd/Collaborative/HNC-Acquisition/MC%20Murder%20Board/Docs%20for%207%20Jan%20RFP/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 file://52mpls-fca-001/cpsd/Collaborative/HNC-Acquisition/MC%20Murder%20Board/Docs%20for%207%20Jan%20RFP/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104

3.2(c) List of Tables and Figures

3.2(d)

Glossary of Abbreviations and

Acronyms

3.3 Validity Statement

3.4 Contact Information

3.5 Exceptions to Terms and Conditions

3.6 Subcontracting Plan

3.7

Government Furnished Property

(GFP)

3.8

Model Contract/Representations and

Certifications

3.9 Financial Responsibility

3.10 Teaming

4 VOLUME II – TECHNICAL

II

4.1(a) Executive Summary 5

1 9 1

4.1(b) Table of Contents

Unlimited 4.1(c) List of Tables and Figures

4.1(d)

Glossary of Abbreviations and

Acronyms

4.1 (g) Table 4-1 Team Members

200*

4.2 Technical Performance

4.3 Design Approach

4.4 Program Management

4.5 Production and Support Approach

4.6 Systems Engineering

4.7 Small Business Participation

5 VOLUME III – PAST PERFORMANCE

III

5.1(a) Executive Summary 5

1 4 1

5.1(b) Table of Contents

Unlimited 5.1(c) List of Tables and Figures

5.1(d)

Glossary of Abbreviations and

Acronyms

5.2 Past Performance Summary

35**

5.3

Organizational Structure Change

History

5.4 Past Performance Information

5.5 Past Performance Questionnaire

5.6 Consent Letter

5.7 Client Authorization Letters

6 VOLUME IV – COST/PRICE

IV 6.1(a) Executive Summary 5

6.1 (b) Table of Contents

Unlimited

1 3 1

6.1 (c) List of Tables and Figures

6.1 (d)

Glossary of Abbreviations and

Acronyms

6.2 Estimating Methodology

6.3 Cost/Price Summary

6.4 Required Information

* Page limitations do not apply to the Contractor Statement of Work (CSOW), the Contractor Work Breakdown

Structure (CWBS), the CWBS Dictionary, the Integrated Master Plan (IMP), the Integrated Master Schedule (IMS)

(reference Section L, paragraphs 4.6.1.1 – 4.6.1.4); certificates, certification letters, test plans, procedures, reports, and results (reference Section L, paragraph 4.3 (b)); Table 4-2, System Requirements Document (SRD) Technical

Approach Cross-Reference; Table 4-3, Information Assurance Security Requirements Document (IASRD) Technical

Approach Cross-Reference; Table 4-4 Proposed SRD Threshold Changes; and Table 4-5, Cross Reference Table.

Classified information will be subject to applicable page limits for this volume.

** Page limitations do not apply to the Past Performance Information Sheets (Attachment L-1), Past Performance

Questionnaires (Attachment L-2), Consent Letters (Attachment (L-3), Client Authorization Letters (Attachment L-

4).

2.3 Proposal Format

2.3.1 Guidance

(a) This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal.

(b) The Offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions.

(c) All the requirements specified in this solicitation are mandatory.

(d) The Offeror is representing that its firm will perform all the requirements specified in the solicitation by submitting its proposal.

(e) These instructions are intended to elicit brief and specific responses; however, simply stating that the Offeror understands and intends to comply with this effort or paraphrasing statements in the RFP is inadequate.

(f) The offer shall be compliant with the requirements as stated in the RFP. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

2.3.2 Sufficient Detail

(a) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims.

(b) The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements.

(c) The Offeror shall assume that the Government has no prior knowledge of its facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal.

2.3.3 Elaborate Presentations Not Desired

Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2.3.4 No Cross-Referencing

(a) 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.

(b) Each response to each subfactor shall be self-contained. No cross-referencing between subfactor responses is allowed.

2.3.5 Tab Indexing

(a) Tab indexing shall be used to identify sections within each volume.

(b) Tabs for items identified in the Title column of Table 2-1 Proposal Organization shall be utilized.

(c) Tabs do not count against the page limitations for their respective volumes.

2.3.6 Table of Contents

(a) Table of Contents

(1) Each volume shall contain a detailed Table of Contents to delineate the subparagraphs within that volume.

(2) The Table of Contents will not count against the page limitations for the respective volumes.

(b) Master Table of Contents

(1) Volume I, Contract Documentation, shall contain a consolidation of the individual

Table of Contents for all Volumes (I through IV).

(2) A separate e-file of the Master Table of Contents shall be provided in accordance with

Electronic Copy requirements in paragraph 2.3.9.3.

2.3.7 List of Tables and Figures

(a) Each volume shall contain a list of all tables and figures within that volume.

(b) The List of Tables and Figures will not count against the page limitations for the respective volumes.

2.3.8 Glossary of Abbreviations and Acronyms

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

(b) One glossary may be developed for the entire proposal and provided in each volume.

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

2.3.9 Proposal Copies

(a) All copies of an Offeror’s proposal must be submitted together.

(b) Staples shall not be used.

(c) Be sure to identify appropriate markings such as the legend at FAR 52.215-1(e), Restriction on disclosure and use of data.

2.3.9.1 “Original” Unbound Proposal

The Offeror shall submit an original of each volume, clearly identified as “original.” The

“original” shall be formatted as follows:

(a) Clearly marked as “Original”

(b) Unbound

(c) Hole-punched with a standard two-hole punch at the top of each page

(d) Printed head-to-foot so that each page can be read when placed in a standard two-hole file folder

(e) Each volume shall have a cover sheet, clearly marked with volume number, “ORIGINAL,”

Offeror’s name, solicitation title, and solicitation number

(f) For classified information, reference Section L, paragraph 4.8, Classified Information.

2.3.9.2 Hard Copies

(a) Each hard copy volume of the proposal shall be printed head-to-head and separately bound in a three-ring loose-leaf binder, which shall permit the volume to lie flat when open.

(b) A cover sheet shall be bound in each book, clearly marked as to volume number, copy number, Offeror’s name, solicitation title, and solicitation number.

(c) A label shall be placed in the front cover of each binder clearly identifying volume number, copy number, Offeror’s name, solicitation title, and solicitation number.

(d) A label shall be placed in the spine of each binder clearly identifying volume number, copy number, Offeror’s name, solicitation title, and solicitation number.

(e) All unclassified document binders shall have a color other than red or other applicable security designation colors.

(f) For classified information, reference Section L, paragraph 4.8, Classified Information.

2.3.9.3 Electronic Copies (E-Copies)

(a) General requirements

1) All electronic copies shall be submitted on CD-ROM in Adobe Acrobat 8.0 (PDF searchable text format) and Microsoft Word 2007. A separate CD-ROM shall be used for each volume. Each CD-ROM and protective sleeve shall be clearly marked with the volume number, Offeror’s name, solicitation title, and solicitation number.

2) No files shall be embedded in the proposal files.

3) Electronic file directory titles and organization shall reflect the titles and organization of these instructions.

4) Each directory shall contain a Master Table of Contents for that directory.

5) The copies in Adobe PDF and Microsoft Word 2007 format shall be exact duplicates of the “original” paper proposal. The CD-ROMs will be used for proposal evaluation. If discrepancies are identified between the electronic proposal and the “original” paper proposal, the paper proposal shall prevail.

6) Offerors shall ensure electronic copies on CD-ROM are virus-free.

(b) Exceptions

(1) The Integrated Master Schedule (IMS) shall be delivered for use in electronic format only (CD-ROM) as part of Volume II, Technical. It shall be in Microsoft Project 2003

(.mpp file extension).

(2) Any Cost/Price model submitted as part of Volume IV, Cost/Price, must be consistent with the information contained in the original paper proposal submission. Electronic copies shall be submitted in Microsoft Excel 2007 format (data file should be .XLS file format) containing computation formulas.

(3) For classified information, as part of Volume II, Technical, reference Section L, paragraph 4.8, Classified Information.

2.3.10 Page Format Restrictions and Limitations

2.3.10.1 Page Format

(a) All pages shall be printed double-sided on recycled paper as much as practical. For example, original letters are exempted from the double-sided requirement.

(b) Pages shall be 8.5 x 11 inches, not including foldouts.

(c) Text pages shall be portrait-oriented. Graphics and tables may be landscape-oriented if required to properly present the information.

(d) Pages shall be typed with at least single-line spacing.

(e) No condensed fonts are allowed. Font shall be Times New Roman or Arial. The font size shall be no less than 12 point except for the following.

(1) Any reproduced sections of the Government solicitation shall be as they appeared in the Solicitation.

(2) The font shall be no smaller than 10 point for text in tables, charts, graphs, and figures.

(3) The font for table cell, chart, graph, or figure labels shall be no smaller than 10 point.

(f) Margins on all four edges of each sheet shall be at least one inch.

(g) Proprietary statements, security markings, and page numbers can fall within the defined margin area.

(h) Each required section within a volume shall be numbered consecutively.

(i) These page format restrictions shall also apply to responses to Evaluation Notices (ENs).

2.3.10.2 Foldouts

(a) Foldout pages shall only be used for large tables, charts, graphs, diagrams, and schematics.

(b) Foldout pages shall not be used for pages of text.

(c) Legible tables, charts, graphs, diagrams, schematics, and figures shall be used wherever practical to depict organizations, systems, and layout, implementation schedules, design drawings, plans, etc.

(d) These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size.

(e) Each printed side of a foldout shall count as two pages.

(f) For tables, charts, graphs, and figures, the font shall be no smaller than 10 point.

(g) All information (except documentation numbers, classification markings, and page numbers) shall be contained within an image area of 9 x 15 inches.

(h) Foldout pages shall fold so that the Government can read and evaluate them without removal from proposal binder.

(i) Foldout pages shall fold entirely within the volume.

2.3.10.3 Page Limitations

(a) Page limitations shall be treated as maximums.

(b) Each side of each 8.5 x 11-inch sheet that displays printed material shall be counted as one page for page limitation purposes.

(c) Each side of each sheet (larger than 8.5 x 11-inches) that displays printed material shall be counted as two pages for page limitation purposes.

(d) If page limits are exceeded, the excess pages will not be read or considered in the evaluation of the proposal.

(e) If the page format, such as margins or fonts, is not in compliance with the directions in the ITO, then the electronic documents will be modified to bring them into compliance and any pages in excess of the required page limit will not be read or considered in the evaluation of the proposal.

(f) The page count of the Classified Annex to Volume II, Technical, is included in the total page count of Volume II, Technical.

2.3.10.4 Pages Counted

These pages shall not be counted:

(a) Cover pages

(b) Table of contents

(c) List of figures

(d) Glossaries

(e) Tabs

(f) Dividers

(g) Blank pages

3 VOLUME I - CONTRACT DOCUMENTATION

3.0 Volume Organization

(a) Executive Summary

(b) Master Table of Contents

(c) Table of Contents

(d) List of Tables and Figures

(e) Glossary of Abbreviations and Acronyms

(f) Validity Statement

(g) Contact Information

(h) Exceptions to Terms and Conditions

(i) Subcontracting Plan, if applicable

(j) Government Furnished Property (GFP)

(k) Model Contract/ Representations and Certifications

(l) Financial Responsibility

(m)Teaming

3.1 Executive Summary

(a) The Executive Summary is a concise, narrative summary of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding price.

(b) The salient features should tie in with Section M evaluation criteria.

(c) Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.2 Standard Proposal Information

(a) Provide a Master Table of Contents for the entire proposal (all volumes).

(b) Provide a Table of Contents for Volume I per ITO paragraph 2.3.6.

(c) Provide a List of Tables and Figures for Volume I per ITO paragraph 2.3.7.

(d) Provide a Glossary of Abbreviations and Acronyms for Volume I per ITO paragraph 2.3.8.

3.3 Validity Statement

(a) The proposal acceptance period is specified in the Standard Form (SF) 33, Page 1, Block 12 of the model contract/RFP.

(b) The Offeror shall make a clear statement that the proposal is valid until this date in this volume.

3.4 Contact Information

Offeror shall provide a single point of contact and one alternate for all matters dealing with its proposal. Provide name, position title, address, phone and fax number, and e-mail address.

Offeror shall provide mailing address for receipt of classified information.

3.5 Exceptions to Terms and Conditions

(a) Offeror is required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors.

(b) Failure to meet a requirement may result in an offer being ineligible for award. Offeror must clearly identify any exception to the solicitation requirements and provide complete accompanying rationale.

(c) Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

(d) Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation.

(e) This information shall be provided in the format and content of Table 3-5 below.

Table 3-5: Solicitation Exceptions

SOLICITATION

DOCUMENT

PARAGRAPH/

PAGE

REQUIREMENT/PORTION RATIONALE

Contract Clause, RFP paragraph, Model Contract, ITO, etc.

Applicable page and paragraph numbers

Identify the requirement or portion to which exception is taken

Justify why the requirement will not be met

3.6 Subcontracting Plan

Submit the subcontracting plan in accordance with Section I, 52.219-9. This plan shall be at a separate tab, if applicable.

3.6.1. Subcontracting Plan - Participation of Small Businesses (SB), Historically Black

Colleges and Universities, or Minority Institutions (HBCU/MI)

If the Offeror is other than a small business, the Offeror shall submit a Small Business

Subcontracting Plan in accordance with FAR 52.219-9, that also identifies and specifies the extent of Offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU), and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the Offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the Offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU, and MI.

3.7 Government Furnished Property (GFP)

The Government plans to provide the items listed in Section J, Attachment 6 of the solicitation as

GFP. If the Offeror requires the use of GFP other than those specified, and which is currently in the Offeror’s possession, the Offeror shall provide a listing including quantity, federal stock number, nomenclature, date needed, and duration of availability, rental value per FAR 45.1 and

45.2, reason for need, and cross reference to cost/price volume paragraphs which pertain to

GFP. The Offeror shall also provide the written authorization from the cognizant PCO, as applicable. The Offeror shall supply this information in the format shown in Table 3-7.

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR52.215.doc#b522199 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR45.doc http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR45.doc

Table 3-7: Required Information for Using GFP

Quan-tity

Federal

Stock #

Nomen-clature

Duration of Need

Rental

Value

Reason for Need

Cross Ref.

to Cost

Prop

3.8 Model Contract / Representations and Certifications

(a) The purpose of this section is to provide information to the Government for preparing the contract document and supporting file.

(b) The Offeror’s proposal shall include a signed copy of Sections A through K. This includes:

3.8.1 Section A - Solicitation/Contract Form

Completion of blocks 13, 14, 15A, 15B, 15C, 16, and signature and date for blocks 17 and 18 of

SF 33. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" (of the SF 33 only) shall be clearly marked under separate cover and shall be provided without any punched holes.

3.8.2 Section B - Supplies or Services and Costs/Prices

To be completed by Offeror. This includes the Unit price/total item amount for all CLINS.

3.8.3 Section C - Description/Specification/Statement of Work

3.8.4. Section D - Packaging and Marking

3.8.5 Section E - Inspection and Acceptance

3.8.6 Section F - Deliveries or Performance

To be completed by Offeror.

3.8.7 Section G - Contract Administrative Data

To be completed by PCO upon contract award.

3.8.8 Section H - Special Contract Requirements

3.8.9 Section I - Contract Clauses

3.8.10 Section J - List of Attachments

The following is a list of attachments or exhibits, which will be made part of each contract upon award and which shall be attached (except Attachment 10 will be provided separately under classified material handling procedures) to the Offeror’s model contract submitted in Volume I.

Complete the following attachments in Section J of the RFP and provide as indicated below:

Section J, Attachment 2, MC CDRL Applicability Table, with the CSOW paragraph for each

CDRL requirement; and provide as an attachment.

EXHIBIT A CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, EXHIBITS A001-A007, ADMINISTRATIVE

EXHIBIT B CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, EXHIBITS B001-B010, LOGISITICS

EXHIBIT C CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, EXHIBITS C001-C002 CONFIGURATION

MANAGEMENT

EXHIBIT D CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, EXHIBITS D001-D013, SECURITY

EXHIBIT E CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, E001-E026, ENGINEERING

EXHIBIT F CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, F001-F021, TEST

ATTACHMENT 1 IMPLEMENTATION OF FAR CLAUSE 52.217-9

ATTACHMENT 2 MC CDRL APPLICABILITY TABLE

ATTACHMENT 3 INTENTIONALLY LEFT BLANK

ATTACHMENT 4 CONTRACTOR STATEMENT OF WORK (CSOW)

ATTACHMENT 5 MC SYSTEM REQUIREMENTS DOCUMENT (SRD)

ATTACHMENT 6 GOVERNMENT FURNISHED INFORMATION (GFI)

ATTACHMENT 7 INTENTIONALLY LEFT BLANK

ATTACHMENT 8 CONTRACTOR WORK BREAKDOWN STRUCTURE (CWBS)

ATTACHMENT 9 TELECOMMUNICATIONS SECURITY REQUIREMENTS

DOCUMENT (TSRD)

ATTACHMENT 10 INFORMATION ASSURANCE SECURITY REQUIREMENTS

DIRECTIVE (IASRD)

ATTACHMENT 11 CONTRACT SECURITY CLASSIFICATION SPECIFICATIONS

(DD FORM 254)

ATTACHMENT 12 OFFERORS’ LIBRARY

ATTACHMENT 13 INTENTIONALLY LEFT BLANK

ATTACHMENT 14

ATTACHMENT 15

INTENTIONALLY LEFT BLANK

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

ATTACHMENT 16

ATTACHMENT 17

INTEGRATED MASTER PLAN (IMP)

SUBCONTRACTING PLAN (IF APPLICABLE)

3.8.11 Section K - Representations, Certifications, and other Statements of Offerors

Complete representations, certifications, acknowledgments, and statements.

3.9 Financial Responsibility

(a) Offeror shall provide the last three (3) years of financial statements and year-to-date financial information through the last quarter available. If audited, reviewed, compiled, or certified financial statements are available, these shall be submitted.

(b) The above information shall be provided for each team member, including the prime, which is anticipated to perform 20 percent or more of the proposed work, to include production. If the prime is a combination of firms (for example, a partnership or joint venture), discuss the financial responsibilities among the companies. Historical and year-to-date financial data shall be submitted for each company that makes up the prime, and the ability to fund contract performance shall be addressed for the combined firm.

(c) Immediately upon receipt of the RFP, the Offeror shall submit an e-mail to the PCO to request the Financial Capability Risk Assessment for each team member, including the prime, that is anticipated to perform 20 percent or more of the proposed work, to include production. The following information must be provided to the PCO in order to initiate a

Financial Capability Risk Assessment by Defense Contract Audit Agency (DCAA): Firm name, POC, and full contact information to include address, phone, fax, email address, and cognizant

DCAA office. The Government requests the information not later than 15 work-days after the release of the RFP. Failure to submit early proposal information will not result in Offeror disqualification.

3.10 Teaming

(a) All team members must have a signed Teaming Agreement (TA) or Letter of Intent (LOI).

(1) If any first-tier subcontractor is projected to perform any of the efforts listed in

Section L, Table 4-1, a signed TA or LOI shall be provided for that subcontractor.

(2) Each TA or LOI shall explain the work the team member will perform on this proposed effort.

(3) First-tier subcontractors projected to perform work not identified in Section L, Table

4-1, may be included as team members at the prime contractor’s discretion. The Offeror shall provide a signed TA or LOI for that subcontractor.

(b) A subcontractor without a TA or LOI with the Offeror is not considered part of the “team” and will not be evaluated as such.

(c) Technical, Past Performance Information, and Past Performance Questionnaires submitted for work proposed on this effort as detailed in Section L, Table 4-1 for subcontractors without a

TA or LOI will not be evaluated.

(d) The Government will consider the Offeror and all subcontractors a team when evidence of a signed TA or LOI is provided in Volume I, Contract Documentation.

(e) A Joint Venture (JV) will be considered a sole business entity.

(f) Mentor-Protégé (M-P) is a relationship and not a business entity. M-Ps require formal TAs or LOIs to qualify for consideration as a team member.

(g) The proposal shall present a complete, coherent presentation of team member abilities as applicable.

4 VOLUME II – TECHNICAL

4.0 Volume Organization

(a) Executive Summary

(b) Table of Contents

(c) List of Tables and Figures

(d) Glossary of Abbreviations and Acronyms

(e) Table 4-1 Team Members

(f) Technical Performance

(g) Design Approach

(h) Program Management

(i) Production and Support Approach

(j) Systems Engineering

(k) Small Business Participation

4.1 General Information

(a) Provide a duplicate copy of the Executive Summary per ITO paragraph 3.1.

(b) Provide a Table of Contents for Volume II per ITO paragraph 2.3.6.

(c) Provide a List of Tables and Figures for Volume II per ITO paragraph 2.3.7.

(d) Provide a Glossary of Abbreviations and Acronyms for Volume II per ITO paragraph 2.3.8.

(e) The Technical Volume shall be specific and complete.

(f) Marketing information shall not be included.

(g) Evidence of capabilities is required to receive credit for evaluation factors. In each instance where evidence is provided, the specific subsidiary and division of the team member proposing to perform the efforts shall be the organization used to fulfill the requirements of this solicitation.

In addition, complete Table 4-1: Team Members, below and provide as a separate tab.

Table 4-1: Team Members

TASK TO BE

PERFORMED

NAME, SUBSIDIARY, AND

DIVISION OF TEAM

MEMBER(S) PROPOSING

TO PERFORM

TEAM MEMBER’S

PROPOSED ROLE,

EITHER AS A PRIME OR

SUBCONTRACTOR

NSA Type 1 Certification

System Development &

Integration

Software Design &

Development

Testing and Evaluation

(Qualification Testing)

LRIP & Full Rate Production

Support Equipment

Help Desk

Data (Operators Guide &

Embedment Manual)

(h) Legibility, clarity, and coherence are very important.

(i) The Offeror’s responses will be evaluated against the Factors defined in Section M, Evaluation Factors for Award.

(j) Provide, as specifically as possible, the actual methodology to be used for accomplishing and satisfying the requirements.

(k) Technical Risk Rating. There is no separate volume for the Technical Risk Rating but discussions about risk should be highlighted in yellow in the Technical Volume. The

Offeror shall integrate the following into its Technical submittal: identification of any risks associated with its implementation of Technical requirements and how it intends to mitigate those risks.

4.2 Technical Performance (Reference Section M, Subfactor 1.1, Technical Performance)

(a) Describe the Offeror’s technical approach to meeting or exceeding the threshold for each requirement identified in the SRD and to meeting the requirements of the IASRD. Do not merely restate the requirements specified in the solicitation. Discuss all performance trade-offs used in developing the proposed technical approach.

(b) This approach shall substantiate how the Offeror’s design and associated verification will meet the MC threshold for Section 3 (Subsystem Requirements) within the SRD.

(c) The Offeror must identify and substantiate the maturity of all applicable Critical

Technologies (CTs) to include at a minimum, the following three CTs: SWaP, TKM, and use of

Suite B algorithms and protocols. Note that selected technologies for entry into Engineering &

Manufacturing Development (EMD) must be at least a Technology Readiness Level (TRL) 6.

Criteria for identifying critical technologies and TRLs are identified in the CPSD TRA

Guidance, in Section J, Attachment 12.

(d) If applicable, the Offeror shall substantiate SRD thresholds they intend to exceed.

(e) The Offeror shall provide a cross-reference table (Table 4-2: SRD Technical Approach

Cross-Reference) in the following format for ALL SRD requirements. Table 4-2 shall be included in Volume II at a separate tab.

Table 4-2: SRD Technical Approach Cross-Reference

SRD

Requirement

Number

Page Number of Offeror’s

Discussion/

Substantiation

Paragraph Number of Offeror’s

Discussion/

Substantiation

Indicate

Whether

Meet or

Exceed

Threshold

(f) The Offeror shall provide a cross-reference table (Table 4-3: IASRD Technical Approach

Cross-Reference) in the following format for ALL IASRD requirements. Table 4-3 shall be included in Volume II at a separate tab.

Table 4-3: IASRD Technical Approach Cross-Reference

IASRD

Requirement

Number

Page Number of

Offeror’s

Discussion

Paragraph Number of Offeror’s

Discussion

(g) The Offeror shall complete Table 4-4 – Proposed SRD Threshold Changes in the following format only if in the previously-described Technical Approach, the Offeror proposes to exceed any SRD threshold requirements. If the Offeror proposes to exceed any SRD threshold requirements, the proposed threshold change shall be entered in Table 4-4 below. If acceptable to the Government, the accepted SRD paragraph change shall replace in its entirety the original

SRD threshold paragraph and shall be made a part of the contract as Appendix 1 to the SRD

(Section L, 3.8.10, Attachment 5). Table 4-4 shall be included in Volume II at a separate tab.

Table 4-4 – Proposed SRD Threshold Changes

Government SRD

Requirement Number

Proposed SRD Threshold Paragraph in its entirety

(h) The Offeror shall identify risks associated with the Offeror’s approach to meeting or exceeding all the requirements of the SRD and meeting the requirements of the IASRD. Classify the identified risks as "high", "moderate", or "low" based on the probability of occurrence for each identified risk and the associated impact to the program if it occurs. Provide rationale for each risk assessment. For all risks identified as "moderate" or "high" include a discussion of how the Offeror plans to mitigate each risk. Then show how application of the Offeror’s proposed mitigation strategies changes the Offeror’s original risk assessment, i.e., lowers probability, or lessens consequence, or both.

4.3 Design Approach (Reference Section M, Subfactor 1.2 – Design Approach)

(a) The Offeror shall describe the approach to achieve NSA certification of the MC as well as where direct NSA involvement is needed during the design and development phases.

(1) The Offeror shall describe a secure approach to TKM, specifically the Operational

Effectiveness, the Operational Suitability, and how the Offeror plans to implement TKM in a tactical environment without traditional key fill and no connectivity to the Global

Information Grid. Describe the risks associated with this approach in obtaining NSA

Type 1 Certification for Secret and Below. Include all resources required for fielding and operational use of TKM.

(2) The Offeror shall describe a secure approach and its Operational Effectiveness and

Operational Suitability for certificate provisioning to include initial MC module loading, certificate renewal, device certificate provisioning (request, acquire, install) and management to include processes for certificate distribution, update, and revocation that is NSA certifiable. Include all resources required for fielding and operational use.

(b) In order for the Government to assess technical risk, the Offeror’s approach to implementation of the crypto functions will be closely examined. Clearly explain the approach or combination of approaches to be used. For example:

(1) Existing cryptographic development – If the Offeror is proposing to use or reuse existing crypto developments for the MC design, supply the following information as a part of the proposal:

Type of technology (ASIC, FPGA, Software running on a processor, etc.)

Examples of products on which this specific technology has been successfully implemented by the Offeror.

NOTE: Specific means the same software that performs cryptographic functions running on the same hardware device. If there is any variation between what has been implemented and what is being proposed, explain it in detail, (e.g., “Same VHDL implementation of algorithms that currently run on the ‘UVW’ FPGA will be ported to the new, lower power ‘XYZ’ FPGA”; “AES crypto engine implemented in JKL ASIC will be used ‘as designed’ and converted from .25 micron CMOS to .090 micron CMOS for the MC ASIC”, etc.”

Any certifications achieved with this technology, e.g., FIPS 140-X, Level Y;

NSA Top Secret CCI; NSA SAB CHVP; etc.

Any test plans, procedures, and reports/results associated with developments intended to be reused

For existing Software that is being proposed to be reused for the MC program, the Offeror shall describe the software engineering environment used to generate unmodified code including software development and code generation tools used, independent peer review processes, and the software testing environment.

Algorithms that will be used on MC that have been successfully implemented by the Offeror, including key length and modes of operation

Indicate the maturity of the algorithm implementation, e.g., in development; development complete, pre-SVT; SVT complete, awaiting certification; certified as a part of the ‘ABC’ product, or other.

(2) GFI-NSA supplied cryptographic developments – If the Offeror is proposing to use cryptographic developments supplied by NSA, supply the following information as part of the proposal:

Explain Offeror’s experience with embedding relevant cryptographic developments

Specific relevant experience in producing cryptographic products using an embedded cryptographic development

Examples of cryptographic products in which the Offeror has successfully embedded relevent cryptographic developments

Any certifications achieved for cryptographic products using embedded relevant developments, e.g., FIPS 140-X, Level Y; NSA Top Secret CCI;

NSA SAB CHVP; etc.

Experience with the cryptographic algorithms required for MC and their various modes

Any test plans, procedures, and reports/results associated with developments intended to be reused

(3) New cryptographic development – If the Offeror is proposing a new development for the cryptographic functions, supply the following information as part of the proposal:

Explain Offeror’s experience in implementing cryptographic algorithms and functions in different products

Types of implementation, e.g., ASICs, FPGAs, Software, etc.

Any certifications achieved for similiar new cryptographic development efforts, e.g., FIPS 140-X, Level Y; NSA Top Secret CCI; NSA SAB CHVP;

etc.

Experience in creating new designs with the cryptographic algorithms required for MC and their various modes

(c) The Offeror shall describe its approach and possible tradeoffs for the design and development of the MC modules to achieve SWaP requirements. The Offeror shall discuss potential risks, risk mitigation approach, predictive SWaP methodologies, predictive SWaP assessment tools, modeling and simulation, design techniques, prototyping and metrics used throughout development.

(d) The Offeror shall identify the key interfaces and criteria for selection (i.e. access to critical data, information, material, services, etc.). The Offeror shall describe its open system approach and selection of established (non-proprietary) industry standards which provide desired performance, cost, industry acceptance, long term availability, supportability, and upgrade potential.

(e) The Offeror shall describe its employment of a modular and functionally-partitioned design and its impact on development, maintenance and modification. The Offeror shall identify the discrete, cohesive, and self-contained units and well-defined interfaces to permit substitution and/or reuse of such units (software/hardware) with similar components or products from alternate sources with minimum impact on existing units.

(f) If applicable, the Offeror shall substantiate an approach with a representative subsystem model or prototype that successfully demonstrated operation in a relevant environment. The system model or prototype demonstrated must have combined all government-identified CTs

(SWaP, TKM, use of Suite B algorithms and protocols), as well as those CTs proposed in the technical performance approach. Provide supporting information necessary to achieve TRL 6, as defined by the CPSD TRA Guidance Table 1.

(g) The Offeror may choose to implement a proprietary (IRAD) cryptographic engine, develop an entirely new cryptographic engine, or a combination of those in its design approach or the

Offeror may elect to use the GFI NSA-owned cryptographic engine. NOTE: The NSA provided cryptographic engine IS NOT currently certified as a Type 1 device; therefore the Offeror shall be required to go through the process to achieve a Type 1…