FIA2T_Atch_J-7_Section_L_20160208.docx

FA8307-16-R-0049

Flexible Information Assurance Acquisition Tool (FIA2T) Section L - Instructions, Conditions and Notices to Offerors 4 February 2016 Section J Attachment 7

Section L - Instructions, Conditions and Notices to Offerors

PROPOSAL PREPARATION INSTRUCTIONS

INFORMATION TO OFFERORS

Table of Contents

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.

Contractual Effort: A single contract or a single delivery/task order placed under a master Single Award or Multiple Award Indefinite Delivery, Indefinite Quantity (IDIQ) delivery/task order contract (FAR 16.501-1); or a single delivery/task order placed under a Federal Supply Schedule (FAR 8.405-2) or a single delivery/task order placed under a master Single Award or Multiple Award Blanket Purchase Agreement (BPA) (FAR 8.405-3 or FAR 13.303).

Distinct: (past performance) Clearly different and separate from other past performance submittals.

Offeror: The Offeror is defined as the Prime Contractor that is submitting the proposal. All mandatory technical, security, and past performance requirements shall be in the Offeror’s name. References to Offeror in this RFP excludes using any subcontractors/team members as a viable means to meet the proposal requirement unless specifically stated as allowed to be used in the response of that particular section (i.e. Technical Subfactors 1 and 2, Cost/Price).

Partial Small Business (SB) Set-aside: A pre-defined scope of work (SOO element 2.1) that has been set-aside for SB considerations.

Partial Small Business (SB) Set-aside Pool: A set of SB Offerors that proposed to the Partial SB Set-Aside requirements and were deemed acceptable for contract award.

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

Realistic schedule: A proposed schedule that covers all known tasks, time and proper resources in an orderly and convincing fashion.

Reasonable or Reasonableness: For a price to be Reasonable, it must represent a price to the Government that a prudent person would pay in the conduct of competitive business.

Recent submittal: (past performance) a past performance submittal must be ongoing or have been completed within the past 8 years prior to the date of this solicitation.

Relevant: Having performed some contractual tasks in the past that logically have bearing or logical connection to cryptographic the FIA2T SOO Areas.

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.

Relevant Submittal: a referenced contractual effort that is completed or on-going for Information Assurance related products (hardware and/or software, COMSEC equipment, cryptographic key material, data distribution/ management equipment, and ancillary/related equipment. This Relevant past performance submittal will describe a similar scope of work covering one or more FIA2T Statement of Objectives (SOO) areas.

Sample Tasks: Engineering tasks/requirements that seem real but are not current requirements in the AF cryptographic program offices. Sample Tasks 1 and 2 are for the UNRESTRICTED pool and the Small Business Sample Task is for the Partial SB Set-Aside pool.

Size, Weight and Power (SWaP): System or sub-system characteristics expressed in volume, weight and power.

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, a statement that is logically valid, based on proven engineering principles that are tested and proven to be free from defects and high risks are mitigated.

Subcontracting: One prime contractor delivering required tasks or products is under one contract with additional contractor(s) providing some of the tasks under a separate agreement with the prime.

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.

Suitability: Of the right type or quality for a particular purpose or occasion.

Supply Chain Risk Management (SCRM): A systematic process of identifying susceptibilities, vulnerabilities and threats throughout DoD’s “supply chain” and developing mitigation strategies to combat those threats whether presented by the supplier, the supplied product and its subcomponents, or the supply chain. These includes risks that adversaries will insert malicious code into or otherwise subvert the design, manufacturing, production, distribution, installation, or maintenance of information communication technology (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.

Susceptibility: The likelihood of being affected, or a tendency to be affected, by a specific thing.

Team: A prime contractor and all proposed first-tier subcontractors.

UNRESTRICTED Pool: A set of Offerors (SBs or other than SBs) that proposed to the UNRESTRICTED requirements and were deemed acceptable for contract award.

Validate: To confirm or the act of confirming truthfulness or soundness.

Section 1: General Instructions for the UNRESTRICTED and Partial SB Set-Aside pools

General Instructions for the UNRESTRICTED and Partial SB Set-Aside Pools The FIA2T multiple award (MA) indefinite delivery, indefinite quantity (IDIQ) contract will be awarded via FAR Part 15 full and open competition with a Partial SB Set-Aside IAW FAR 19.502-4(b). Under the FIA2T IDIQ contract all work will be divided into two competitive "pools” the Partial Small Business (SB) Set-Aside pool and UNRESTRICTED pool.

The UNRESTRICTED pool is open to all interested parties regardless of business size.

The Partial SB Set-Aside pool will result in SB awardees becoming eligible to receive a contract award IAW FAR 19.502-4(b). The SB partial set-aside involves future delivery/task orders described in the FIA2T SOO task 2.1, Materiel Solutions Analysis (MSA) phase.

SB Offerors may elect to compete for award in the UNRESTICTED pool and/or the Partial SB Set-Aside pool based on the Offeror's submission of Section L, Attachment L-14, Small Business Choice of Competition. Other than SB Offerors shall submit no more than one (1) proposal for consideration into the UNRESTRICTED pool. SB Offerors shall submit no more than one (1) proposal for consideration into the UNRESTRICTED pool and shall submit no more than one (1) proposal for consideration into the Partial SB Set-Aside pool; the Offeror shall indicate which pool(s) they are proposing towards in Section L, Attachment L-14, Small Business Choice of Competition Form.

Each volume in Section L identifies if it applies to the UNRESTRICTED pool and/or the Partial SB Set-Aside pool. The Offerors shall follow the proposal submission requirements for their selected competition pool(s).

Point of Contact The contracting officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO e-mail. Email is the preferred method of communication. The PCO for this acquisition is:

Ralph M. Urias, Jr.

230 Hall Blvd, Suite 205 San Antonio, TX 78243 ralph.urias@us.af.mil Phone number: 210- 925-1072 Discrepancies If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the CO in writing with supporting rationale immediately, but no later than 10 work-days after release of the RFP.

Transmittal of Sensitive or Classified Attachments If there will be sensitive information, in either the proposal or the RFP, the Offeror will contact the PCO above to discuss how to transmit said information.

Proposal Format General Guidance This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal.

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

All the requirements specified in this solicitation are mandatory.

The Offeror is representing that its firm shall perform all the requirements specified in the solicitation by submitting its proposal.

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.

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

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

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.

Unnecessarily elaborate presentations, brochures, documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

The proposal shall provide cross-referencing between volumes.

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.

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

Page Format Restrictions and Limitations 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.

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

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

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

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:

a. Any reproduced sections of the Government solicitation shall be as they appeared in the Solicitation.

b. The font shall be no smaller than 8 point for text in tables, charts, graphs, and figures.

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

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

Proprietary statements and page numbers can fall within the defined margin area.

Each required section within a volume shall be numbered consecutively.

These page format restrictions shall also apply to responses to ENs, if necessary.

Foldouts Foldout pages shall only be used for large tables, charts, graphs, diagrams, and schematics. Foldout pages shall not be used for pages of text.

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

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

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

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

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

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

Foldout pages shall fold entirely within the volume.

Page Limitations Page limitations shall be treated as maximums.

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

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.

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

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.

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 Proposal Copies All copies of an Offeror’s proposal shall be submitted together.

Staples shall not be used.

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

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

Hard (Printed) Copies 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.

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.

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.

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.

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

Electronic Copies

1) General requirements:

a. All electronic copies shall be submitted on CD-ROM in Adobe Acrobat 10.0 (PDF searchable text format) and Microsoft Word 2010. 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.

b. No files shall be embedded in the proposal files.

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

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

e. The copies in Adobe PDF and Microsoft Word 2010 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.

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

2) Exceptions:

a. 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 2010 (.MPP file extension). Any Cost/Price model submitted as part of Volume IV, Cost/Price, shall be consistent with the information contained in the original paper proposal submission. Electronic copies shall be submitted in Microsoft Excel 2010 format (data file should be .XLS file format) containing computation formulas.

Proposal Organization and Page Limit The Offeror shall prepare the proposal as set forth herein.

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

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

Specific format requirements are identified in Section L.1.4, Proposal Format General Guidance.

The contents of each proposal volume are described in the ITO paragraph as noted in Table L1 for the UNRESTRICTED pool and Table L2 for the Partial SB Set-Aside pool.

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

In compliance with FAR 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 L1. UNRESTRICTED Pool Proposal Organization and Page Limits

(L.1.8)

ORIGINAL UNBOUND

(L.1.11)

HARD COPIES

(L.1.12)

E- COPIES

(L.1.13)

75**

L.5.2 L.5.3

Unlimited

* Page limitations do not apply to: B-Table Labor Definitions (Cost Format Attachment, L.7.6.13); and, certificates, certification letters, test plans, procedures, reports, and results used to support technical competencies/capabilities (L.3).

** Page limitations do not apply to: Design Approach Work Breakdown Structure (L.3.2.6); Design Approach Integrated Master Schedule (L.3.2.8).

*** Page limitation for Past Performance Information is unlimited; however, Program Details tab is limited to 32,000 characters.

**** Page limitation applies only to the paragraph L.7.3 and not to the remainder of that Section (L.7.3.1 through L.7.3.17).

Table L2. Partial SB Set-Aside Pool Proposal Organization and Page Limits

(L.1.8)

ORIGINAL UNBOUND

(L.1.11)

HARD COPIES

(L.1.12)

E- COPIES

(L.1.13)

L.6.2 L.6.3

L.6.9 Client Authorization Letter

Unlimited

* Page limitations do not apply to: B-Table Labor Definitions (Cost Format Attachment, L.8.6.13); and, certificates, certification letters, test plans, procedures, reports, and results used to support technical competencies/capabilities (L.4).

** Page limitations do not apply to IMS and Contractor Statement of Work (CSOW) (L.4.2.5).

*** Page limitation for Past Performance Information is unlimited; however, Program Details tab is limited to 32,000 characters.

**** Page limitation applies only to the paragraph L.8.3 and not to the remainder of that Section (L.8.3.1 through L.8.3.14).

Common Volume Content Executive Summary 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. The salient features should tie in with Section M evaluation criteria. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

Table of Contents Each volume shall contain a detailed Table of Contents to delineate the subparagraphs within that volume. The Table of Contents will not count against the page limitations for the respective volumes.

Master Table of Contents Volume I, Contract Documentation, shall contain a consolidation of the individual Table of Contents for all Volumes (I through IV).

A separate e-file of the Master Table of Contents shall be provided in accordance with Electronic Copy requirements in Section L.1.13.

Cover Page Each volume shall contain a cover page indicating which pool the Offeror’s proposal applies to.

Tables and Figures Each volume shall contain a list of all tables and figures within that volume. The List of Tables and Figures will not count against the page limitations for the respective volumes.

Glossary of Abbreviations, Acronyms and Terms of Reference Definitions Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. One glossary may be developed for the entire proposal and provided in each volume. Glossaries do not count against the page limitations for their respective volumes.

Tab Indexing Tab indexing shall be used to identify sections within each volume. For the UNRESTRICTED pool, tabs shall be created for items identified in the Title column of Table L-1. For the Partial SB Set-Aside pool, tabs shall be created for items identified in the Title column of Table L-2. Tabs do not count against the page limitations for their respective volumes.

Volume 1: Contract Documentation for the UNRESTRICTED and Partial SB Set-Aside pools

Volume I – Contract Documentation for the UNRESTRICTED and Partial SB Set-Aside pools Reference Section M.3.

Validity Statement The proposal acceptance period is specified in the SF 33, Page 1, Block 12 of the model contract/RFP (see Section L.2.5.1). The Offeror shall make a clear statement in this volume that the proposal is valid until this date.

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.

Exceptions to Terms and Conditions 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. 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. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. 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. This information shall be provided in the format and content of Table L3 below.

Table L3. Exception to Terms and Conditions Submittal Template

Small Business Subcontracting Plan - (UNRESTRICTED pool only) 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. The FIA2T small business subcontracting goal is 37%. The small business subcontracting plan should also identify and specify 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 shall submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU, and MI.

Model Contract/Representations and Certifications The purpose of this section is to provide information to the Government for preparing the contract document and supporting file. The Offeror’s proposal shall include a signed copy of Sections A through K. This includes:

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. The remainder of the model contract sections A through K shall be 2 (two) hole punched at the top of the page.

Section B – Supplies or Services and Costs/Prices Submit “as is” from Government final Request for Proposal.

Section C – Descriptions/Specification/Statement of Work Section D – Packaging and Marking Section E – Inspection and Acceptance Section F – Deliveries or Performance Section G – Contract Administrative Data To be completed by PCO upon contract award.

Section H – Special Contract Requirements Section I – Contract Clauses 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 to the Offeror’s model contract submitted in Volume I.

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

ATTACHMENT 1 FIA2T: STATEMENT OF OBJECTIVES

(Refer to Section J Attachment 1 for the UNRESTRICTED pool and Section J Attachment 9 for the Partial SB Set-Aside)

ATTACHMENT 2 CONTRACT SECURITY CLASSIFICATION SPECIFICATIONS (DD FORM 254)

(Refer to Section J Attachment 2)

ATTACHMENT 3 SCHEDULE B-TABLES – FFP RATES

(Refer to Cost/Price Section L.7.6.13 for the UNRESTRICTED pool and Section L.8.6.13 for the Partial SB Set-Aside pool.)

ATTACHMENT 4 SUBCONTRACTING PLAN (IF APPLICABLE)

(Refer to Section L.3.2.4)

ATTACHMENT 5 B-TABLE LABOR DEFINITIONS

(Refer to Cost/Price Section L.7.6.13 for the UNRESTRICTED pool and Section L.8.6.13 for the Partial SB Set-Aside pool.)

ATTACHMENT 9 FIA2T STATEMENT OF OBJECTIVES (SOO) FOR SMALL BUSINESS SET-ASIDE (ONLY) (Refer to L.4. & M.4)

ATTACHMENT 10 FIA2T DELIVERY ORDER/TASK ORDER ORDERING PROCEDURES

ATTACHMENT 11 FIA2T ON/OFF RAMPING PROCEDURES

Section K – Representations, Certifications, and other Statements of Offeror Complete representations, certifications, acknowledgements, and statements.

Evidence of Financial Responsibility The 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.

Immediately upon receipt of the RFP, the Offeror shall submit an e-mail to the PCO to request the Financial Capability Risk Assessment. 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, e-mail 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.

Teaming A Joint Venture (JV) will be considered a sole business entity. Mentor-Protégé (M-P) is a relationship and not a business entity.

Each TA or LOI shall explain the work each team member will perform by SOO work area.

For the UNRESTRICTED pool the Offeror will include each team member’s labor definitions and FFP labor rates as required by L.7.6.7 and L.7.6.6 in the Cost Format at L.7.6.13.

For the Partial SB Set-Aside pool the Offeror will include each team member’s labor definitions and FFP labor rates as required by L.8.6.7 and L.8.6.5 in the Cost Format at L.8.6.13.

Volume 2: Technical Competencies/Capabilities for the UNRESTRICTED Pool

Volume II – UNRESTRICTED Pool Technical Competencies/Capabilities Reference Section M.3 General Information Glossary of Abbreviations, Acronyms and Terms of Reference Definitions (Reference Microsoft Word file “FIA2T_AtchL-1_Glossary Acronyms_20150728.docx”) Offeror’s Library Reference Table (Reference Microsoft Excel file “FIA2T_AtchL-2 Offerors Library Reference Table 20150728”) Sample Tasks Start Date for Planning Schedule planning for all Sample Tasks shall assume a start date of 1 January 2017. This parameter has been included in all schedule related templates.

Technical Risk [reference Section M.3] There is no separate volume for the Technical Risk but discussions about risk should be highlighted in yellow in the Technical Volume. The Offeror shall integrate a sound risk approach into its Technical submittal including: identification of any risks associated with its implementation of Technical requirements and how it intends to mitigate those risks.

Sample Tasks Teaming Rules The Offeror may utilize teaming/subcontracting in order to fulfill the requirements of the Sample Tasks described in Section L.3.2. and L.3.3. In doing so, the Offeror shall ensure that all requirements are met in describing how the work is to be performed (e.g. IMS, Work Breakdown Structure (WBS)).

Subfactor 1 - Design Approach (Sample Task 1) Reference Section M.3.1.

Sample Task 1 Summary Description Sample Task 1, Universal Cryptographic Module (UCM) represents a notional cryptographic engineering and manufacturing development activity for a single channel cryptographic embeddable microelectronic component device designed for integration into higher level communications component assemblies for fixed (both permanent and transportable) and mobile (i.e., human-portable, vehicular, ship-borne, airborne, and space-borne) platforms requiring encryption or decryption of data communications links. The UCM will be a Tailored Top Secret and Below (TSAB) National Security Agency (NSA) certified, space flight qualified COMSEC embeddable solution. The technology readiness level must be justified to be at TRL 6 or higher at initiation of the effort. The proposed response will be used to determine the Offeror’s development and security certification planning ability as well as capabilities/processes maturity to design and develop a validated/certified high assurance cryptographic electronics that meet the performance and security requirements defined in (1) .

Sample Task 1 Schedule Constraints Offeror shall propose a realistic and substantiated schedule for Sample Task 1 with target duration of 30 months from the start date defined in Section L.3.1.3. A schedule with longer or shorter durations is acceptable with appropriate substantiation of activity durations, dependencies and resource utilization.

Summary Description of Design Approach The Offeror shall describe its design approach and tradeoffs for the design and development of the UCM to achieve SWaP, environmental and security requirements specified in Section (1) , Sample Task 1, Universal Cryptographic Module (UCM) System/Security Requirements Document. The Offeror shall discuss potential risks, risk mitigation approach(es), predictive SWaP methodologies, predictive SWaP assessment tools, vulnerability assessment tools, security compliance tools, modeling and simulation, design techniques, prototyping and metrics used throughout development.

The Offeror shall clearly explain the basis of its design approach or combination of approaches to be used. For example:

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

a. Type of technology (application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), Software running on a processor, etc.) Examples of products on which this specific technology has been successfully implemented by the Offeror.

b. 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 Very High Speed Integrated Circuit (VHSIC) Hardware Description Language (VHDL) implementation of algorithms that currently run on the ‘UVW’ FPGA will be ported to the new, lower power ‘XYZ’ FPGA”; “Advanced Encryption Standard (AES) crypto engine implemented in ‘JKL’ ASIC will be used ‘as designed’ and converted from .25 micron Complementary Metal Oxide Semiconductor (CMOS) to .180 micron Silicon on insulator (SOI) for the UCM ASIC”, etc.)

c. Any certifications achieved with this technology, e.g., FIPS 140-X, Security Level Y; NSA Top Secret Controlled Cryptographic Item (CCI); NSA Secret and Below (SAB) Cryptographic High Value Product (CHVP); etc.

d. For existing Software that is being proposed to be reused for the UCM Sample Task, 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.

e. Algorithms specified for the UCM that have been successfully implemented by the Offeror, including key length and modes of operation. (Response does not need to be classified.)

(2) Government Furnished Information (GFI) supplied from NIST or NSA cryptographic developments – if the Offeror is proposing to use cryptographic developments supplied by NSA or NIST, supply the following information as part of the proposal:

a. Explain the Offeror’s experience with embedding applicable cryptographic developments

b. Specific applicable experience in producing cryptographic products using an embedded cryptographic development

c. Examples of cryptographic products in which the Offeror has successfully embedded applicable cryptographic developments

d. Any certifications achieved for cryptographic products using embedded applicable developments, e.g., FIPS 140-X, Security Level Y; NSA Top Secret CCI; NSA SAB CHVP; etc.

e. Experience with implementing cryptographic algorithms and their various modes

f. 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:

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

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

c. Any certifications achieved for similar new cryptographic development efforts, e.g., FIPS 140-X, Security Level Y (1 – 4); NSA Top Secret CCI; NSA SAB CHVP; etc.

d. Experience in creating new designs with the cryptographic algorithms and their various modes The Offeror shall describe the approach to achieve NSA TSAB certification of the UCM as well as where direct/indirect NSA involvement is needed during the design and development phases. Note that because this is a fictional task, no actual NSA involvement is to be pursued, nor any discussion with them on the security requirements provided as part of the Security-System Requirements Document (S/SRD), Information Assurance Systems Requirements Document (IASRD) and Technical Systems Requirements Document (TSRD). These documents have been tailored to be at the UNCLASSIFIED//FOUO level and apply to this fictional UCM only. Any inquiries regarding the security requirements should be forwarded to the PCO, not to NSA. The Offeror shall describe a comprehensive Systems Security Engineering (SSE) process for protection of mission critical functions to achieve trusted systems and networks. Specifically, the Offeror shall describe employment of a disciplined, structured SSE process, including criticality analysis, in arriving at the UCM design and the identification and mitigation of threat and vulnerability risks.

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

The Offeror shall identify the maturity of the selected technologies. Technologies for acceptance in completing this Sample Task must be Technology Readiness Level (TRL) 6 or higher (as of the start date of the Sample Task) per DoD Technology Readiness Assessment Deskbook, April 2011 (available on www.acq.osd.mil/chieftechnologist/publications/docs/TRA2011.pdf). For any technologies proposed, the Offeror must describe and explain how its proposed technologies are a minimum TRL 6. The Offeror shall present a description of: how the maturity of the technology was assessed; the relevant environment to which the technologies have been tested or operated in; results from lab reports, test reports, specification sheets, or operational studies to indicate the performance of the technology for operational success to substantiate meeting the assessed TRL.

Design Approach Milestone Entrance/Exit Criteria, Work Breakdown Structure (WBS), and IMS To support the soundness of the Offeror’s design approach, the Offeror shall prepare and submit a table of milestone entrance/exit criteria, a WBS extended to level 5, and IMS which incorporates the tasks, resources, milestones and WBS in accordance with the instructions provided below.

Design Approach Major Milestones Entrance/Exit Criteria The Offeror shall complete the entrance and exit criteria identified in Table L4 below. Entrance criteria shall be consistent with the tasks, documentation, reports, approvals, test articles availabilities and deliveries associated with the design approach.

Table L4. Sample Task Entrance/Exit Criteria for Milestone Events

[To Be Addressed By Offeror in IMS] Exit Criteria [To Be Addressed By Offeror in IMS]

Validate proposed implementation of requirements within system design

Agree on plan of action to evaluate risks inherent in the PMB

Shall be held concurrent with other scheduled activities

Validate allocated requirements to configuration items within Offeror’s system preliminary design

Validate traceability between Government system and functional performance requirements and Offeror’s system design

Review the Offeror’s proposed Key and Certificate Management Architecture

Review traceability between Government’s system requirements and Offeror’s system design

Verify system is ready to enter into formal Government witnessed testing

Design Approach Work Breakdown Structure The Offeror shall extend the WBS Dictionary definitions in the Government template from Section (2) to Level 5 based on their proposed design approach, applicable certified processes and consistent with MIL-STD-881C, DEPARTMENT OF DEFENSE STANDARD: WORK BREAKDOWN STRUCTURES (WBS) FOR DEFENSE MATERIEL ITEMS (03-OCT-2011). WBS Level 1 to 3 definitions shall not be modified by the Offeror.

Design Approach Direct Labor Resources Definitions The Offeror shall follow the instructions in Section L.7.6.1 to provide their definitions for all direct labor classifications necessary to implement their design approach and consistent with their cost accounting system. No cost rate information is to be included.

Design Approach Integrated Master Schedule The Offeror shall provide a detailed IMS that meets the delivery requirements for Design Approach - Sample Task 1. The intent of the IMS is to obtain a functionally integrated understanding of the proposal with clear tracks between the technical, schedule and cost elements in a way that provides the Government confidence that the effort is structured to be executable for the resources indicated.

The IMS shall identify at a minimum all tasks and their durations, milestones reviews/audits/events, documentation deliveries (including reasonable review times), tests, test articles availabilities and deliveries, task labor/material resources and associated hours, needed to comply with requirements of the Sample Task. The scheduled tasks shall be directly traceable to the milestone entrance/exit criteria, Sample Task 1 S/SRD requirements and Design Approach WBS.

All tasks/activities in the IMS shall be soundly linked together showing predecessor/successor relationships and resources applied. The activities and tasks shall be sufficient to account for the requirements of the S/SRD and consistent with design approach.

The Offeror shall submit the IMS using an electronic format compatible with Microsoft Project 2010 (“.mpp”). The Microsoft Project templates provided in Section (3) contains the list of major milestones, the Government WBS summary task elements, non-work schedule for Government holidays, and common project start date data already populated. Offerors shall not change the aforementioned factors in the Microsoft Project file or remove or delete summary tasks, major milestones, rows, columns in the GANNT view of Microsoft Project. Summary tasks, major milestones, rows, columns and resources may be reordered/sequenced by Offeror if deemed to better illustrate Sample Task approach. The Offeror shall:

(1) Extend tasks/activities, including in-house, inter-divisional, subcontractor, and associate contractor activities, consistent with the Offeror’s proposed approach, the Offeror’s proposed WBS for the Sample Task, and the applicable Offeror’s certified processes.

(2) Populate predecessor/successor relationships consistent with milestone events (Table L4) and task dependencies necessary to execute proposed Sample Task 1 approach.

(3) Populate the work resources in the Resource Sheet view of Microsoft Project with direct labor and other direct resources (e.g., design, test, or fabrication Facilities, Equipment or Services) requiring time (hours, days, weeks, etc.) to perform tasks/activities. Complete the six fields shown in Resource Sheet for each resource as follows (example inputs provided in the Microsoft Project Template):

a. Initials and Resource Name fields for direct labor shall be consistent with the Labor Codes and Position Titles from the Labor Category Descriptions template completed by the Offeror for Section L.7.6.13. If more than one labor resource in the same labor category is planned, either provide unique designator for the Initials and Resource Name or use labor category name and adjust the Max. Units field percentage as described below.

b. Ensure all values for the Type field are set to “Work.”

c. Input a percentage (except 0%) of resource availability. For labor, 100% is equivalent to 1 full time equivalent person/unit resource availability for the entire schedule. If using a single resource to represent multiple resources of the same type, adjust the percentage above to reflect total availability of all resources of the type (e.g., 3 resources at 100% availability each = 300%; 3 resources at 50% availability each = 150%, etc.)

d. Select either “Gov’t FY Calendar w/ Holidays” or “24 Hours” for the Base Calendar field, as appropriate.

e. DO NOT include labor rate/cost information. Labor rate/cost information is to be provided in Volume IV: Cost/Price only.

(4) Assign resources as defined above and hours or percentage of task utilization for each resource associated to each tasks/activities assigned consistent with proposed Sample Task approaches and schedule constraints.

Design Approach Attachments

(1) Sample Task 1, Universal Cryptographic Module (UCM)…