FA8307-14-R-0002-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

12 JUN 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)

31 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 X 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 1 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.)

SEE SCHEDULE OF CHANGES

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 11 Jun 2014 3:43 PM

SCHEDULE OF CHANGES

FA8307-14-R-0002 0002

SCHEUDULE OF CHANGES:

Amendment 0002 makes the following changes to the solicitation document.

1. The response date for the submission of proposals is changed from 15 July 2014 to 31 July 2014, 10:00 am CST.

2. CLIN 0004 is updated with the following language: "If Option is exercised, the Contractor shall produce and deliver 50 EACH MC devices as described by the approved Product Baseline (as defined in MIL- HDBK-61A) IAW the CSOW, incorporated in the contract under Section C - Description/Specs/Work Statement, to meet the delivery schedule IAW Section F. The contractor shall also deliver any special test equipment developed for EMD."

3. CLINs 0014 and 0015 are updated to cross-reference CLIN 0013.

4. Section (b), para (1) of clause 52.246-18 WARRANTY OF SUPPLIES OF A COMPLEX NATURE (May 2001) is updated with the following language: "The Contractor warrants that for one (1) year all supplies furnished under this contract will be free from defects in material and workmanship and will conform with all requirements of this contract; provided, however, that with respect to Government-furnished property, the Contractor's warranty shall extend only to its proper installation, unless the Contractor performs some modification or other work on the property, in which case the Contractor's warranty shall extend to the modification or other work."

5. Government Furnished Property Clause 52.245-1 is added.

6. Government responses to contractor submitted questions are included as an attachement to this amendment.

7. The following attachments in Section J have been updated:

Exhibit G CONTRACT DATA REQUIREMENTS LIST (CDRL), B005, LOGISTICS

PRODUCT DATA SUMMARIES

Attachment 2 MC CDRL APPLICABILITY TABLE Attachment 3 STATEMENT OF OBJECTIVES (SOO) Attachment 13 SECTION L, PROPOSAL PREPARATION INSTRUCTIONS Attachment 14 SECTION M, EVALUATION FACTORS FOR AWARD

8. All other terms and conditions remain unchanged.

Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount

0004 OPTION CLIN (supply) __________

Noun: OPTION 1 - LOW RATE INITIAL PRODUCTION (LRIP) -

OT&E

NSN: N - Not Applicable DD1423 is Exhibit: AF Contract type: J - FIRM FIXED PRICE Inspection: SOURCE Acceptance: SOURCE

FOB: DESTINATION

Descriptive Data:

If Option is exercised, the Contractor shall produce and deliver 50 EACH MC devices as described by the approved Product Baseline (as defined in MIL-HDBK-61A) IAW the CSOW, incorporated in the contract under Section C - Description/Specs/Work Statement, to meet the delivery schedule IAW Section F. The contractor shall deliver support equipment and special test equipment identified and approved in EMD required to support MC embedment and operation. This includes software programs that may be needed to support sustainment of the embedded MC module.

Quantity: 50 EA. MC DEVICES Contract Type: FIRM FIXED PRICE Period of Performance: Contractor to Propose a Period of Performance between 0 and 12 Months

Option will be exercised IAW Section J, Attachment 1, "Implementation of FAR Clause 52.217-9".

Inspection/Acceptance: Orgin FOB: Destination

0014 OPTION CLIN (supply) __________

Noun: OPTION 3 - DATA - FRP (NOT SEPARATELY PRICED) NSN: N - Not Applicable DD1423 is Exhibit: AF Contract type: J - FIRM FIXED PRICE Inspection: DESTINATION Acceptance: DESTINATION

FOB: DESTINATION

Descriptive Data:

If Option is exercised, the Contractor shall provide data, associated with CLIN 0013 and in accordance with the Contract Data Requirements List (CDRL) identified in Section J, Exhibits A-F. Data is not priced separately.

Period of Performance: 12 Months

Option will be exercised IAW Section J, Attachment 1, "Implementation of FAR Clause

Inspection/Acceptance/FOB: Destination

Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount

0015 OPTION CLIN (service) __________

Noun: OPTION 3 - TRAVEL - FRP DD1423 is Exhibit: AF Descriptive Data:

If Option is exercised, the Contractor shall perform travel in support of CLIN 0013. The contractor shall perform travel IAW the CSOW, incorporated in the contract under Section C -Description/Specs/Work Statement, on a cost reimbursement basis only. No profit or fee will be paid in support of this CLIN. All travel will be IAW the Joint Travel Regulation

(JTR).

Contract Type: COST Period of Performance: 12 Months

TOTAL ITEM AMOUNT__________

Option will be exercised IAW Section J, Attachment 1, "Implementation of FAR Clause

LIST OF ATTACHMENTS

DOCUMENT PGS DATE TITLE

EXHIBIT G 3 11 JUN 2014 CONTRACT DATA REQUIREMENTS LIST (CDRL),

DD FORM 1423, B005, LOGISTICS PRODUCT

DATA SUMMARIES

ATTACHMENT 2 3 16 MAY 2014 MC CDRL APPLICABILITY TABLE

ATTACHMENT 3 42 15 MAY 2014 STATEMENT OF OBJECTIVES (SOO)

ATTACHMENT 13 70 28 MAY 2014 SECTION L, PROPOSAL PREPARATION

INSTRUCTIONS

ATTACHMENT 14 14 28 MAY 2014 SECTION M, EVALUATION FACTORS FOR

AWARD

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoD 5010.12-M for detailed instructions.)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

Item I. Signature of CDRL approval authority.

Item J. Date CDRL was approved.

Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.

DD FORM 1423-1 (BACK), FEB 2001

UNCLASSIFIED

MINI CRYPTO CDRL APPLICABILITY TABLE

Data

Item Title Data Item Description SOO Reference TSRD Reference CSOW

A001 Report, Record of Meeting Minutes DI-ADMN-81505 3.1.3

A002 Presentation Material DI-ADMN-81373 3.1.3

A003 Contract Work Breakdown Structure DI-MGMT-81334D 3.1.4

A004 Integrated Program Management Report (IPMR) DI-MGMT-81861 3.1.4

A005 Data Accession List(DAL) DI-MGMT-81453A NOT 1 3.1.5

A006 Quality Program Plan (QPP) DI-QCIC-81722 3.1.4

A007 Design-To-Cost, Life Cycle Cost and Variance Analysis Report DI-FNCL-80449 3.1.3

B001 Production Report DI-MGMT-81867 Table 1, Pre-LRIP PRR

B002 Manufacturing Plan DI-MGMT-81889 3.1.4

B003

Manufacturing Readiness Assessment Report

[Technical Report - Study/Services] DI-MISC-80508B 3.1.3

B004 Logistics Product Data DI-SESS-81758A 3.1.6

B005 Logistics Product Data Summaries DI-SESS-81759 3.1.6

B006 Level of Repair Analysis (LORA) Report DI-SESS-81872 3.1.3

B007

Commercial Off-The-Shelf (COTS) Manual and Associated

Supplemental Data DI-TMSS-80527C 3.1.6

B008

Interface and Operators Guide

[Guidelines for Use in Operation if INFOSEC Equipment/Systems

(Type IV)] DI-TMSS-81584 3.1.7, 3.1.2.5

B009 Engineering Data for Provisioning (EDFP) DI-SESS-81874 3.1.6

B010

Source Data For Forecasting Diminishing Manufacturing Sources and

Material Shortages (DMSMS) DI-SESS-81656 3.1.6.7

C001 Engineering Change Proposal (ECP) DI-CMAN-80639C 2.13

C002 Contractor's Configuration Management Plan DI-CMAN-80858B 3.2.4

D001 Program Protection Implementation Plan (PPIP) DI-ADMN-81306 3.1.3

D002 Source/Vendor List/ Foreign List DI-MGMT-80894A 3.2.8

D003 OPERATIONS SECURITY (OPSEC) PLAN DI-MGMT-80934C 3.1.4

D004 Information Systems Security (INFOSEC) Anonymity Plan (IAP) DI-MGMT-81717D 3.1.6.9

D005 Customized Microelectronics Devices Source Protection Plan DI-MGMT-81763 3.2.8

D006 Security Evaluation Document (SED) DI-MISC-81762 2.2

D007 Counterfeit Prevention Plan DI-MISC-81832 3.1.6

D008 GIDEP DI-QCIC-80125B 3.1.3

D009 GIDEP Alert Response DI-QCIC-80126B 3.1.3

D010 Security Verification Plan and Procedures DI-QCIC-81689 2.3

D011 Security Verification Report DI-QCIC-81690 2.3

D012 RESERVED

D013

Information Security (INFOSEC) Boundary Configuration Management

Plan DI-SESS-81343A NOT 1 2.1.1

Logistics

Management

Configuration Management

Security

FA8307-14-R-0002

DISTRIBUTION STATEMENT A:

Approved for public release; distribution is unlimited.

UNCLASSIFIED Page 1

Data

Item Title Data Item Description SOO Reference TSRD Reference CSOW

Management

E001 Configuration Audit Plan DI-SESS-81646 NOT 1 2.9

E002 Configuration Audit Summary Report DI-CMAN-81022C 2.9

E003 Interface Control Document (ICD) DI-CMAN-81248A 3.9

E004 Interface Requirements Specification (IRS) DI-IPSC-81434A NOT 1 3.1.3.2 4.0

E005 Software Version Description (SVD) DI-ISPC-81442A NOT 1 3.1.3

E006

Software Metrics Report

[Software Development Status Report (SDSR)] DI-MCCR-80459 3.1.3

E007 Software Development Plan DI-IPSC-81427A 3.1.3.15

E008

Design Considerations Trade Study Report

[Technical Report - Study/Services] DI-MISC-80508B 3.1.3

E009 System Engineering Management Plan (SEMP) DI-SESS-81785 3.1.3

E010 Safety Assessment Report DI-SAFT-80102B 3.1.3

E011

Hazardous Materials Management Program (HMMP) Plan Using NAS

411 DI-MGMT-81398B 3.1.6

E012

Embedment Manual

[Communications Security Equipment System Document (CSESD)] DI-MGMT-81719 5.0

E013

SHRS (S/W/H/W Requirement Spec)

[Technical Report - Study/Services] DI-MISC-80508B 3.1.3.2 2.6

E014 Key and Certificate Management Architecture DI-MISC-80508B 3.1.3

E015

SPLER (S/W and Programmable Logic Evaluation Report

[Technical Report - Study/Services] DI-MISC-80508B 2.8.1

E016

SDPDD (S/W Development Process Description Document)

[Technical Report - Study/Services] DI-MISC-80508B 2.5

E017

Key and Certificate Management Plan

[Technical Report - Study/Services] DI-MISC-80508B 3.1.3

E018

SHDD (S/W/H/W Design Description)

[Technical Report - Study/Services] DI-MISC-80508B 3.1.3.2 2.7

E019 Corrective Action Plan DI-RELI-80254 As Needed

E020

Reliability Growth Plan and Metrics Report

[Technical Report - Study/Services] DI-MISC-80508B 3.1.3.9

E021 Product Drawings/Models and Associated Lists DI-SESS-81000E 3.1.3.2, 3.1.2.5 2.11.2

E022 Failure Analysis and Corrective Action Report (FACAR) DI-SESS-81315B 3.1.3.9

E023 GERBER Printed Wiring Board (PWB) Data DI-SESS-81693 2.11.2

E024

Engineering Database and Configuration Management Information

(EDCMI)

[Technical Report - Study/Services] DI-SESS-81694 2.12

E025 INTERFACE DESIGN DESCRIPTION DI-IPSC-81436A NOT 1 3.1.3.2

F001

EMI Control Plan

[Electromagnetic Interference Control Procedures (EMICP)] DI-EMCS-80199C 3.1.3

F002 Electromagnetic Interference Test Procedures (EMITP) DI-EMCS-80201C 3.1.3

F003 Electromagnetic Interference Test Report (EMITR) DI-EMCS-80200C 3.1.3

F004 TEMPEST Control Plan DI-EMCS-81687 3.1.3

F005

TEMPEST Test Procedures

[TEMPEST Test Plan] DI-EMCS-81683 3.1.3

F006 TEMPEST Test Evaluation Report DI-EMCS-81684 3.1.3

F007 Environmental Stress Screening Procedures and Implementation Plan DI-ENVR-81014 3.1.3

F008

Program Test Plan

[Test Plan] DI-NDTI-80566A 3.1.2

F009 Software Test Plan (STP) DI-IPSC-81438A 3.1.2

F010

Software Test Procedures

[Software Test Description (STD)] DI-IPSC-81439A 3.1.2

F011 Software Test Report (STR) DI-IPSC-81440A 3.1.2

F012

Notification of Test and Test Readiness Review (TRR)

[Notification of Test/Trials] DI-MISC-81624 3.1.2

F013 RESERVED

F014

Qualification Test Procedures

[Test Procedure] DI-NDTI-80603A 3.1.2

F015 Qualification Test Report (QTR) DI-QCIC-81890 3.1.2

F016 Acceptance Test Plan DI-QCIC-80553A 3.1.2

F017

Acceptance Test Procedures

[Test Procedure] DI-NDTI-80603A 3.1.2

Test

Engineering

FA8307-14-R-0002

DISTRIBUTION STATEMENT A:

UNCLASSIFIED Page 2

Data

Item Title Data Item Description SOO Reference TSRD Reference CSOW

ManagementF018 Acceptance Test Report (ATR) DI-QCIC-81891A 3.1.2

F019 First Article Qualification Test Plans and Procedures DI-NDTI-81307A 3.1.2

F020

Highly Accelerated Life Cycle Test Procedure

[Test Procedure] DI-NDTI-80603A 3.1.2

F021

Highly Accelerated Lifecycle Test and First Article Test Report

[Test/Inspection Report] DI-NDTI-80809B 3.1.2

FA8307-14-R-0002

DISTRIBUTION STATEMENT A:

UNCLASSIFIED Page 3

FA8307-14-R-0002 ATTACHMENT 3

United States Air Force (USAF)

Mini Crypto (MC)

Statement of Objectives (SOO)

Version - 1.0

10 April 2014

DISTRIBUTION STATEMENT: Approved for public release; distribution is unlimited.

ii

THIS PAGE INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. BACKGROUND

2. SCOPE

3. OBJECTIVES

3.1 Engineering & Manufacturing Development (EMD)

3.1.1 Prime Mission Product

3.1.2 Test and Evaluation (T&E)

3.1.3 Systems Engineering

3.1.4 Program Management

3.1.5 Data

3.1.6 Product Support

3.1.7 Training

3.2 Low Rate Initial Production (LRIP) Objectives

3.2.1 Prime Mission Product (WBS 4.1)

3.2.2 Operational Test and Evaluation (OT&E) (WBS 4.2)

3.2.3 Systems Engineering

3.2.4 Program Management

3.2.5 Data

3.2.6 Product Support

3.2.7 Training

3.3 Full Rate Production

3.3.1 Prime Mission Product (WBS 5.1)

3.3.2 Program Management

3.3.3 Data

3.3.4 Product Support

4. ACRONYMS

1. BACKGROUND

Current combat operations have driven the transformation of war fighting techniques and the types of tools required to maintain military dominance in asymmetric warfare. Many of the devices used in the battlefield have taken advantage of advances in miniaturization of electronics resulting in equipment with low Size, Weight and Power (SWaP) parameters. These Small

Form-Factor (SFF) devices provide tactical and strategic advantages, supporting sensitive and even classified operations. It is during these operations that the data, command and control messages, and sensitive information must be protected against all adversaries. Additionally, these modern war fighting missions are dynamic, requiring a modern key management process for mission-time generation and over-the-air distribution of crypto keys to tactical devices on an as-needed basis.

The Air Force Life Cycle Management Center, COMSEC Products Branch (AFLCMC/HNCC) in collaboration with Air Force Space Command (AFSPC) Cyber Support Squadron (CYSS), the

Lead Command, identified a number of SFF tactical platforms in need of a cryptographic solution. Without a cryptographic solution in these tactical devices, communications may become increasingly vulnerable to compromise and exploitation. Additionally, analysis showed an embeddable solution does not exist to address the full set of security needs.

In order to guide the design, development, and procurement of a new cryptographic device that provides low SWaP cryptographic capabilities for tactical SFF systems, the United States Air

Force (USAF) established Mini Crypto (MC), an Acquisition Category III (ACAT III) Program.

The MC program received an approved Materiel Development Decision (MDD) from the

Program Executive Officer (PEO) on April 10, 2013 to develop and produce a cryptographic solution for embedment into SWaP-constrained tactical devices. The new MC device delivered by this program will meet the operational requirements of current and future tactical war fighting systems and will integrate the appropriate National Security Agency (NSA) tenets. It will allow for operational readiness and support secure information sharing with more than just Department of Defense (DoD) operations, allowing for secure communications with coalition partners and friendly forces.

2. SCOPE

This Statement of Objectives (SOO) defines the efforts to be accomplished by the Offeror. The contract scope includes Engineering and Manufacturing Development (EMD), Low Rate Initial

Production (LRIP) and Full Rate Production (FRP). The effort will include design, development, production, documentation, integration, testing, certifications, training, maintenance, and logistics of all MC Modules, including hardware and software.

3. OBJECTIVES

The primary objective of the MC program is to develop and produce a low-cost, low-SWaP, NSA Type 1 certified module that can be embedded in a variety of SFF communication devices.

This module will be capable of protecting information at the Secret and Below (SaB) level, utilize Tactical Key Management (TKM) and require Cryptographic High-Value Product

(CHVP) handling to maximize protection of and minimize the burden on the warfighter. The effort addressed by this SOO is focused on creating a complete crypto subsystem that contains all elements needed for full functionality and facilitates embedment into a host platform.

Detailed objectives are described below, with corresponding references to the Work Breakdown

Structure (WBS) elements identified in Table 3, Table 4 and Table 5.

a. EMD to be successfully accomplished within the period of performance specified in the contract; all assumptions clearly stated to achieve your proposed schedule.

b. Production of required LRIP units to be accomplished within the period of performance of LRIP option specified in the contract with all assumptions clearly stated to achieve this schedule.

c. Production of FRP units to be accomplished within the period of performance of the FRP option specified in the contract with all assumptions clearly stated to achieve this schedule.

The Offeror shall levy on proposed teammates and subcontractors the same requirements, restrictions and statutes that are levied on the Offeror by this contract. This “flow-down” shall apply to all tiers of proposed teammates and subcontractors associated with the program during both the development and production phases of the program.

3.1 ENGINEERING & MANUFACTURING DEVELOPMENT (EMD)

The Offeror should plan for seamless transition of appropriate/applicable activities and processes which begin during the EMD phase, but which must continue through FRP.

3.1.1 Prime Mission Product

The Offeror shall develop a detailed design for a cryptographic module that meets program objectives as specified in Section 3.0 above. (WBS 3.1)

3.1.1.1 The Offeror shall develop a detailed design that meets the threshold requirements identified in the MC System Requirements Document (SRD), plus all requirements specified in the Telecommunications Security Requirements Document (TSRD) and the

Information Assurance Security Requirements Directive (IASRD) for the MC program.

If the Offeror proposes to exceed any threshold requirements, they will be incorporated into the subsequent contract as the new thresholds, will be priced separately, and if Key

Performance Parameters (KPPs), the additional cost will be identified. (WBS 3.1)

3.1.1.2 The Offeror shall develop and deliver 4 each prototypes post-Preliminary Design

Review (PDR) and prior to Critical Design Review (CDR) that will demonstrate limited functional capabilities of the MC module. At minimum, the functional prototype shall be based on the allocated baseline and meet the interface requirements specifications to support early integration testing. (WBS 3.1)

3.1.1.3 The Offeror shall develop and deliver 3 each emulators, post-CDR and prior to Test

Readiness Review (TRR) that demonstrates the functionalities and interfaces of MC.

The emulator shall be a representation of the MC module to assist platform developers and integration efforts. The emulator shall also include module software loading, certificate renewal, certificate provisioning and management. (WBS 3.1)

3.1.1.4 The Offeror shall implement Government-approved subsystem detailed designs, based on the Product Baseline by developing, building and delivering 89 each Production

Representative Engineering Development Models (PREDMs). PREDMs shall be acceptance tested utilizing Government Approved Acceptance Test Plans and

Procedures prior to delivery. Offeror shall identify additional PREDMs required to support Developmental Test and Evaluation (DT&E). (WBS 3.1.1, 3.3.1)

3.1.2 Test and Evaluation (T&E)

3.1.2.1 The Offeror shall determine test asset quantities to be produced that are sufficient to provide adequate test assets to meet the test events schedule. Integrated testing will include: Developmental Test & Evaluation (DT&E); NSA Type 1 certification, (Cryptographic Verification and Security Verification); TEMPEST characterization and

Red/Black separation; Reliability; Operational Assessment (OA); and dedicated

Operational Testing. It is the objective of the Government to work closely and collaboratively with the Offeror during T&E, through formal and informal interchange meetings held at the Offeror’s facility. The Offeror shall provide a schedule of dry run qualification events and allow for Government participation. Test events will work toward reducing program risk and optimizing the number of test events to the greatest extent possible. Seamless verification activities will follow the spirit of “no secrets” testing through coordination with the system developers, users, and the program office by maintaining open book access to test data, test event observation, and continuous feedback. (WBS 3.2)

3.1.2.2 The Offeror shall develop a test allocation table that uniquely identifies test assets to test events. The Offeror shall document any assumption of variant quantity and sparing that are necessary to execute the test program (and any rework and retesting). (WBS

3.2)

3.1.2.3 The Offeror shall utilize a comprehensive Verification and Validation process that is integrated with other T&E activities and employs at minimum modeling, testing, and simulation. (WBS 3.2)

3.1.2.4 The Offeror shall provide and deliver Government-approved qualitative and quantitative verification methods for DT&E. (WBS 3.2)

3.1.2.5 The Offeror shall develop and deliver 2 each Government-approved developmental test sets that can visually demonstrate and display information through a Human Machine

Interface/Graphical User Interface (HMI/GUI) during DT&E. The Offeror shall ensure the developmental test set is not restricted to a specific operating system and allows for intuitive user interaction, prior to TRR. (WBS 3.2)

3.1.2.6 The Offeror shall support and participate in test and evaluation activities for planning and execution of DT&E, OAs, product acceptance testing, and testing that supports certification. (WBS 3.2)

3.1.2.7 The Offeror shall develop, conduct, and deliver various test plans, test procedures, and test reports throughout the EMD phase to support the development of the MC modules.

Activities include but are not limited to Integrated Test Team (ITT) meetings, test planning and test data review meetings, TRR, Government-witnessed developmental and operational test events, and module certification testing activities. (WBS 3.2)

3.1.2.8 The Offeror shall provide support for Government-conducted test events which will be held at Government and/or Offeror facilities. The Offeror shall provide a comprehensive Program Test Plan (PTP) that incorporates all required testing events

(individual plans, procedures, and reports), including NSA-mandated tests to achieve

Type 1 accreditation through Security Verification Testing (SVT). The plan shall also include developmental test and evaluation objectives, operational test and evaluation objectives, and certifications to be achieved. The PTP schedule is to be reflected in the

Integrated Master Schedule (IMS) and Integrated Master Plan (IMP). (WBS 3.2.1, 3.2.2, 3.2.3)

3.1.2.9 The Offeror shall develop and deliver TEMPEST plans and reports; and conduct

TEMPEST testing to provide the TEMPEST characterization of the final MC design.

TEMPEST characterization of the MC design supports the integration into and accreditation of host platforms. (WBS 3.2)

3.1.2.10 The Offeror shall support the MC Program Management Office (PMO) and NSA Lead

Service Provider activities leading to NSA Type 1 certification. (WBS 3.2.2)

3.1.2.11 The Offeror shall assist Lead Developmental Test Organization (LDTO) and

Operational Test Organization (OTO) test team members in identifying, documenting and resolving deficiencies in accordance with (IAW) the Offeror’s configuration and data management plans and Technical Order (TO) 00-35D-54, USAF Deficiency

Reporting, Investigation, and Resolution, 1 Nov 11. The Offeror shall participate in

Deficiency Review Boards. (WBS 3.2.1, 3.3.1)

3.1.2.12 The Offeror shall demonstrate that all critical components used in the MC system are free of intentional defects and malicious design alterations. A ‘critical’ component refers to any logic-bearing or state-holding component that can be maliciously altered to produce vulnerabilities to the end system. Reference Aerospace Standard (AS) 5553 and AS 6081, Counterfeit Parts: Avoidance, Detection, Mitigation and Disposition.

(WBS 3.2)

3.1.2.13 The Offeror shall develop, deliver, and demonstrate Acceptance Test Plans and

Procedures. Acceptance Test Plans and Procedures shall include Environmental Stress

Screening. Acceptance Testing shall be used to demonstrate that items procured fulfill the product requirements and specifications. (WBS 3.2)

3.1.2.14 The Offeror shall develop and deliver First Article Qualification Test Plans and

Procedures. First Article Qualification Test Plans and Procedures shall be used to support the assessment of production readiness prior to Full-Rate Production. (WBS

3.2)

3.1.2.15 The Offeror shall develop and deliver Highly Accelerated Life-Cycle Testing (HALT) plans, procedures, and reports; and conduct HALT to develop Highly Accelerated

Stress Screening that shall be incorporated into the manufacturing processes. The

Offeror shall conduct at minimum two HALT events, one prior to the CDR and another prior to TRR. The intent of conducting a HALT is to identify design weaknesses and manufacturing process problems and increase the margin of strength in the design.

(WBS 3.2)

3.1.2.16 The Offeror shall develop and deliver Qualification Test Plans, Procedures, and

Reports; and conduct Qualification Testing to ensure the final product meets the design requirements and specifications. (WBS 3.2)

3.1.2.17 The Offeror shall provide notifications of Government witnessed test events prior to testing. Government approval to proceed with Government witness test events is required. (WBS 3.2)

3.1.2.18 The Offeror shall develop and deliver Software Test Plans, Descriptions, Procedures, and Reports; and conduct Software Testing to ensure the software meets the design requirements prior TRR. (WBS 3.2)

3.1.3 Systems Engineering

3.1.3.1 As part of the systems engineering process, the Offeror shall plan for, schedule, and conduct technical reviews and audits appropriate to EMD including but not limited to:

Integrated Baseline Review (IBR), System Requirements Review (SRR), System

Functional Review (SFR), PDR, CDR, Developmental Test Readiness Review (DTRR), OA, Physical Configuration Audits (PCA) (to include hardware and software), LRIP

Production Readiness Review (PRR), System Verification Review (SVR) and

Functional Configuration Audit (FCA). Reviews and audits shall be event-driven and based on Government-approved entrance and exit criteria as noted in Table 1. In addition to the formal review processes, it is the objective of the Government to work closely and collaboratively (particularly on high-risk areas such as but not limited to software development/integration and testing), through frequent formal and informal technical interchange meetings held at the Offeror’s facility. (WBS 3.3)

3.1.3.2 The Offeror shall implement sound systems engineering processes to develop functional, allocated, and product baselines. (WBS 3.3)

3.1.3.3 The Offeror shall prepare and follow an effective Government-approved Systems

Engineering Management Plan (SEMP). The Offeror shall prepare required system safety related plans, analyses, and reports. (WBS 3.3)

3.1.3.4 The Offeror shall invoke a requirements management process and tool with bidirectional traceability to include but not limited to the SRD/System Specification to all decomposed requirements, design specifications, test plans/procedures/scripts, and hardware and software configuration items. The Offeror shall control all program data via the Offeror’s configuration and data management plans. The Offeror shall provide a graphical representation of their requirements management hierarchy, test plans, design, hardware and software configuration items, and how their hierarchy links to the

Government’s SRD. The Offeror shall provide a requirements traceability report with each delivery of the [Software Hardware Requirements Specification (SHRS). The

Offeror shall deliver requirements in a format capable of importing into IBM®

Rational® Dynamic Object Oriented Requirements System (DOORS®). The Offeror shall provide the traceability from the Government’s System Requirements Document

(SRD), to the Systems Specification and subsequent requirements, design and test documentation. This traceability shall be importable into DOORS 9.3 or later and be used to automate the creation of the same traceability in DOORS. The Offeror shall provide updates to this delivery as necessary to the Government. At a minimum, the delivery shall include for each requirement:

a. Decomposed requirement(s)

b. Link ID to “parent” requirement (if the parent requirement is provided by the

Government, the Link ID shall be the DOORS Absolute Number provided by the Government)

c. Test methodology

d. Link ID to the test plan/procedure/script

e. Link ID to the design/requirements/implementation specification (WBS 3.3.1)

If the Offeror uses IBM’s Dynamic Object Oriented Requirements System (DOORS), the Offeror shall use DOORS partitioning to support the requirements management process. The Government will provide the Offeror a DOORS partition to include the following:

a. DOORS [SRD] module

b. DOORS Satisfies link module

The Offeror shall use DOORS capabilities to enforce only using the DOORS linksets specified in the DOORS link modules to enforce referential integrity.

The Offeror shall provide a DOORS archive file of the projects/folders/formal modules/link modules used to maintain the requirements/testing/analysis/design at a minimum prior to every technical review and once when the Government approves the product baseline.

3.1.3.5 The Offeror shall establish a system and track maturity of the MC Program design throughout the EMD phase of the program. Meaningful metrics shall be established, tracked, and shared with the Government. (WBS 3.3.1)

3.1.3.6 As part of the systems engineering process, the Offeror shall plan for and conduct hardware and software deficiency reporting, analysis, tracking, and resolution. All critical and major deficiency reports (DRs) shall be resolved before proceeding through the next major review/audit (as specified in Table 1) after the DR was initiated. The

Offeror’s deficiency reporting system shall be compatible with the Government’s Joint

Deficiency Reporting System (JDRS) (Ref: TO 00-35D-54). (WBS 3.3)

3.1.3.7 The Offeror shall participate and provide identification, investigation, test, management, and resolution support for the Government's JDRS (USAF TO 00-35D-

54) and Government’s Configuration Control Board (CCB). The Offeror shall identify and generate DRs for any MC deficiency that impacts Operational Safety Suitability and Effectiveness and the Program Protection Implementation Plan (PPIP) of systems and their sub and/or support systems to include trainers, test, and support equipment.

(WBS 3.3)

3.1.3.8 As part of the systems engineering process, the Offeror shall plan for and conduct a trade study on the design decisions that have a significant impact on factors such as, but not limited to subsystem operational effectiveness, Reliability, Availability, and

Maintainability (RAM), certification, design to cost goals, performance, ease of integration, and life cycle costs. The Offeror shall provide a problem statement, identify constraints, identify alternatives and establish the analysis level of detail to be agreed upon by the Government. Producibility constraints shall be considered during cost and trade study. The Offeror may propose and plan additional trade studies, not to exceed 4 additional studies, to address other or partition design decisions. (WBS 3.3)

3.1.3.9 The Offeror shall provide a comprehensive Reliability Growth Plan to achieve RAM requirements. The plan shall include logical deliverables of supporting documentation on the reliability growth of the design. The approach to meet RAM requirements shall include built-in test (BIT), fault detection and isolation, elimination of false alarms, redundant/degraded system management, reliability and reliability growth models, modularity, mitigation of failure modes, manufacturing quality assurance, and as necessary maintenance procedures and training. The Offeror shall implement a reliability growth program with the focus on performing activities for identifying and eliminating failure modes. The Offeror shall use the DoD Guide for Achieving

Reliability, Availability, and Maintainability (3 Aug 05), MIL-HDBK-344A, MIL-

HDBK-2164A, and MIL-HDBK-189C. (WBS 3.3)

3.1.3.10 The Offeror shall provide a Corrective Action Plan and Failure Analysis and Corrective

Action Report resulting from test events and environmental stress screening failures.

(WBS 3.2, WBS 3.3)

3.1.3.11 The Offeror shall develop and implement stress screens based on results from the

Reliability Growth program and accelerated testing to the manufacturing processes.

(WBS 3.3)

3.1.3.12 A Failure, Mode, Effects, and Criticality Analysis (FMECA) shall be performed to identify ways in which the product can fail to identify performance consequences. The

FMECA, or equivalent, shall be documented on product hardware and software and to the indentured level consistent with the design progression. (WBS 3.3)

3.1.3.13 The Offeror shall develop, design, and produce MC devices while mitigating the growth of Metal Whiskers. The Offeror shall address in the Reliability Growth Plan, a mitigation plan for unavoidable usage of any material that can cause whisker growth and employ practices that prevent whisker formation and its effect on the reliability and maintainability of the MC devices. (Ref: JEDEC/IPC Joint publication JP002, Current

Tin Whiskers Theory and Mitigation Practices Guideline and Airworthiness Advisory, AA-05-01, 9 May 2005). (WBS 3.3.3)

3.1.3.14 The Offeror shall conduct self-assessments of manufacturing readiness throughout the period of performance specified using the definitions, criteria, and processes defined in the Manufacturing Readiness Level Deskbook and AF ManTech Manufacturing

Readiness Assessment (MRA) Questions v11.3 (available at www.dodmrl.com ) as a guide. The results of the assessments shall be provided to the Government. (WBS 3.3)

3.1.3.15 The Offeror shall specify (in an appendix to the SOW) the locations and frequencies of any assessments of manufacturing readiness, along with all the resources to perform or support these assessments. The Offeror shall identify its approach for flowing down these requirements as a function of risk. The Offeror shall address how assessments of manufacturing readiness will be executed and monitored to ensure achieving the required level in accordance with their Manufacturing Maturity Plans (MMP). (WBS

3.3)

3.1.3.16 The Offeror shall support the Government with the assessments of manufacturing readiness of the prime Offeror. The prime Offeror shall lead the assessments at the suppliers with Government participation unless clearly specified differently in the proposal. The Offeror shall address how Manufacturing Readiness Levels (MRLs) will be monitored to ensure achieving the required level in accordance with their MMP.

(WBS 3.3)

3.1.3.17 The Offeror shall develop and use a Life-Cycle Cost Model to estimate life-cycle costs based on evolving product designs and changing program assumptions. The Offeror shall deliver Design-to-Cost and Life-Cycle Cost estimates. (WBS 3.3.1)

3.1.3.18 All parts shall be procured from the original equipment manufacturer (OEM) or its franchised/authorized distributor, and shall come with an OEM certificate of compliance. In cases where a part is not available through a franchised or authorized distributor, the Offeror shall procure parts from a distributor that complies with

AS9120, the Offeror shall test the parts per AS5553 (Appendix E), and the Offeror shall notify the Government. (WBS 3.3)

3.1.3.19 The Offeror shall develop a plan for mitigating the supply chain risk to the system’s critical components, the failure of which would result in either catastrophic or critical compromise of mission capability, or in significant mission degradation. This plan shall be documented as a Microelectronics Source Protection Plan. (WBS 3.3)

3.1.3.20 The Offeror shall demonstrate visibility into its supply chain for each critical component. This visibility shall be documented in a Counterfeit Prevention Plan. (WBS

3.3.2)

3.1.3.21 The Offeror shall conduct Level of Repair Analysis (LORA) commensurate with the level of design, operation and support data available. Identify characteristics from the

LORA for those items identified as item candidates. Such characteristics shall include source of supply, level of maintenance, disposition of unserviceable items, unit cost and reliability. (WBS 3.3)

3.1.3.22 The Offeror shall implement procedures and processes for their participation, and their Team Members’ participation, in the Government-Industry Data Exchange

Program (GIDEP) program, including the submission of alerts/advisories to GIDEP http://www.dodmrl.com/ when warranted. The processes and procedures shall describe how the Offeror (a) receives alerts and advisories from GIDEP and other agencies, or internal sources, (b) determines any impact to their product design and already manufactured hardware, (c) implements corrective action procedures when design and/or produced hardware are affected, and (d) how all of the above flow down to Team Members. (WBS 3.3)

3.1.3.23 The Offeror shall reduce and control the effects of Electromagnetic Interference (EMI) on and from the MC module. (WBS 3.3)

3.1.3.24 The Offeror shall develop and deliver a Key and Certificate Management Architecture

(KCMA) to describe the overall Tactical Key Management (TKM) Architecture; and a

Key and Certificate Management Plan (KCMP) to describe the products and plans necessary to support the design.

Elliptic Curve Cryptography (ECC) is patented technology by Certicom Corporation.

For use of ECC, the Offeror shall work with the United States Government (USG), namely the National Security Agency (NSA) to obtain a patent license or sublicense agreement from Certicom Corporation. Information regarding ECC patents can be found at: http://www.nsa.gov/business/programs/quick_facts.shtml. (WBS 3.3)

3.1.3.25 The Offeror shall document the software development approach in a Software

Development Plan (SDP), shall implement the SDP requirements, and shall maintain the SDP. The SDP shall describe the Offeror’s software development and quality processes. Software processes documented in the SDP shall be integrated and consistent with the IMP and IMS. The Offeror shall address their approach and processes for the management of software risks; software activity planning and statusing; the use of software metrics; and the management of software suppliers, including flow down of performance and process requirements. The Offeror shall comply with the requirements of the SDP for all computer software to be developed, integrated, or maintained under this effort. (Ref: USAF Weapon Systems Software Management Guidebook, 15 August

2008). (WBS 3.1.2, 3.3.1)

3.1.3.26 The Offeror shall develop, deliver, and/or conduct the necessary activities associated with the MC TSRD to support NSA Type 1 certification. (WBS 3.1, WBS 3.3)

3.1.3.27 The Offeror shall host a Software Development Process Review for the government to review the software development processes of the Offeror and/or team members performing software development for the MC program. The review shall be held in conjunction with the Systems Functional Review. The Offeror and/or team members shall support biannual site visits demonstrating the processes are being implemented during the software development. The Offeror shall provide evidence and artifacts to substantiate the Offeror’s processes are implemented throughout the software development. (WBS 3.3.1)

3.1.4 Program Management

http://www.nsa.gov/business/programs/quick_facts.shtml

3.1.4.1 The Offeror shall conduct periodic Technical Interchange Meetings (TIMs), as required, to include technical performance measure reporting. Team member participation may be required, as agreed to by the prime Offeror and the Government. (WBS 3.3.2)

3.1.4.2 The Offeror shall conduct quarterly Program Management Reviews (PMR) with the

Government at the Offeror’s facility or by any other agreed upon method. PMR shall include resource management reporting. Team member participation may be required, as agreed to by the prime Offeror and the Government. (WBS 3.3.2)

3.1.4.3 The Offeror shall perform and participate in project management activities to ensure…