SECTION L 20120301 cdl.pdf

1 (of 44) FA8307-12-R-0003 Attachment 16, Revision 1

Attachment 4 - Section L

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

L-III - INFORMATION TO OFFERORS (ITO)

AND INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

FAB-T provides the strategic nuclear and non-nuclear command and control with Extremely High Frequency (EHF), wideband, protected and survivable communications terminals for Beyond Line-of-Sight communications. FAB-T is part of the terminal and control segments of the Advanced EHF (AEHF) satellite system. It is required to provide Telemetry, Tracking, and Commanding (TT&C) of the AEHF and Milstar satellites and to fully utilize the increased capacity of the AEHF constellation. The FAB-T Alternate Source program will develop and field airborne and ground based Military Satellite Communications (MILSATCOM) terminal capability. FAB-T provides both wideband and survivable protected communications to the strategic and tactical warfighter. Terminals are compatible with AEHF satellites and legacy Milstar EHF satellite systems.

In this acquisition, FAB-T Alternate Source capabilities are prioritized to ensure the replacement of the existing ground-fixed, ground-transportable, and airborne command post terminals for the E-4 and E-6 aircraft. It will enable backward compatibility to existing Milstar EHF Low Data Rate (LDR) communications and provide AEHF Extended Data Rate (XDR) satellite communications in support of strategic nuclear and tactical operational requirements. Ground-based fixed, airborne Command and Control (C2) and transportable FAB-T terminals will ensure that nuclear C2 facilities remain connected to the President of the United States, Secretary of Defense, and Combatant Commanders to provide positive control and nuclear surety of Nuclear Response forces.

1.1. Budget/Funding Information

The Government will not be providing a funding profile.

2.0 General Instructions

(a) This section of the Information 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 must include all data and information requested by the ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), Government Technical Requirements Document (GTRD), Contract Data

2 (of 44) FA8307-12-R-0003

Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) The proposal shall be clear and 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. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror's proposal.

(c) Elaborate brochures or documentation, binding, detailed art work or other embellishments are unnecessary and are not desired. Similarly, for oral presentations, elaborate productions are unnecessary and not desired.

(d) The proposal acceptance period is specified in Section A of the model contract/solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through that date.

(e) In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.1 General Information

2.1.1. Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation.

2.1.2. Debriefings

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

The CO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

3 (of 44) FA8307-12-R-0003

2.1.3. Discrepancies

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

This reservation includes matters of additional or substitute pages of the initial proposal.

2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.5. Demonstration

2.1.5.1 The demonstration shall be conducted at the Offeror’s facility using equipment provided by the Offeror. The combined overview, demonstration, and outbrief shall not exceed four (4) hours in total and shall be completed within one day. Within that 4 hours will be one 10-minute break. Each Offeror is required to provide a recording (audio and video) of the overview, demonstration, and outbrief to the Government.

This recording shall be provided to the Government at the conclusion of the out brief.

The Government PCO will contact Offerors within three weeks after the proposal due date to provide a tentative schedule for delivery of briefing materials (see paragraph 2.1.5.4) to the Government and the conduct of the demonstration itself. The Offeror can expect at least five (5) business days from time of notification to submittal of briefing materials to the Government. Any chart included in the submitted briefing materials but not briefed during the established time limits may or may not be used in the Government's evaluation.

2.1.5.2 The major objectives of the demonstration are as follows:

(a) The ability to perform the hardware and software processing associated with acquiring the downlink and uplink, and to logon to an Advanced Extremely High Frequency (AEHF) Satellite at Extended Data Rate (XDR) to provide voice communications; the ability to perform the processing associated with acquiring the downlink and uplink, and to logon to the Milstar satellite at Low Data Rate (LDR) to communicate Emergency Action Messages (EAMs).

(b) The ability to demonstrate as many of the GTRD functional and performance requirements (identified in paragraph 4.2.3.1) as possible.

2.1.5.3 The Offeror shall submit the following as “Appendix A” of Volume II of the written proposal submission:

A description of the demonstration including an enumerated list of the capabilities that will be demonstrated, traceability of those capabilities to the GTRD, the procedures to be used and the Offeror’s success criteria for each demonstrated capability.

4 (of 44) FA8307-12-R-0003

The complete architecture/design of the demonstration unit, as well as the drivers, simulations, and environment used for the demonstration.

A description of all demonstration hardware, software, and firmware system and sub-system components and the platforms (hardware and operating system) on which they are hosted, the runtime relationships, and the dependencies between the software system and sub-system components. For hardware and software components of the demonstration proposed for reuse in the end state, the Offeror shall also describe obsolescence concerns and life expectancy.

A description of how the demonstration’s architecture, hardware, and software relate to the proposed end state.

A description of the proposed technical approach for transitioning to the FAB-T end state, including how the architecture, hardware, and software will be modified to satisfy the GTRD requirements, the assumptions that the technical approach is based on, and the risks that could limit the Offeror’s ability to deliver a sufficiently mature and integrated solution that will meet GTRD requirements within the Offeror’s proposed schedule.

The name, title, telephone number, and email address of the person for the Government to contact to provide the tentative demonstration schedule.

2.1.5.4 Prior to the beginning of the demonstration, the offeror shall provide an overview briefing of the demonstration, including a description of the demonstrated hardware and software configuration, and how the design forms the basis for a fully-capable FAB-T, specifically identifying which aspects of the demonstrated configuration will be reused in the final FAB-T design. The Offeror shall discuss the objectives, scope of the demonstration, and the complete architecture of the demonstration environment/methodology (e.g., live, simulated, drivers).

The Offeror shall provide printed copies of a short Demonstration Outline. This Outline shall briefly describe each step of the demonstration and note GTRD requirements being demonstrated.

At the conclusion of the demonstration, the Offeror shall provide an out brief to include a summary of the demonstration objectives, results, current maturity levels, and perceived risks.

Briefing materials shall contain only information necessary to convey an understanding of the proposed approach and demonstration to the Government. These materials are not to be used to provide additional information not otherwise found in the written proposal. Briefing charts shall be limited to 75 pages and the Demonstration Outline shall be limited to 10 pages.

2.1.6 Communications

Exchanges of source selection information between the Government and Offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and

5 (of 44) FA8307-12-R-0003 includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

Otherwise, source selection information will be transmitted via facsimile.

2.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.2. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.2 - Proposal Organization

VOLUME ITO

Paragraph Number

VOLUME TITLE COPIES PAGE LIMIT

I Executive Summary 5

II 4.2.1.1 Technical Capability 10 65

2.1.5.1.3 Appendix A

Demonstration Description 10 10

III 5.0 Past Performance 5 9 per questionnaire

IV 6.0 Cost/Price 2 V 7.0 Contract Documentation 5

2.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the Offeror as soon as practical. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Each page shall be counted except the following:

Section and Volume cover pages IMP/IMS documents Master Table of Contents, any other tables of contents, glossaries, CMM Level certification documents, and reports.

Small Business Contracting Plan and Small Business Participation Plan

2.2.1.1. Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages.

Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 10 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout

6 (of 44) FA8307-12-R-0003 software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs.

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

These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and each 8.5 x 11 inch surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point.

2.2.2 Cost or Pricing Information

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

All cost or pricing information shall be provided as spreadsheets that include all formulas used for calculations of all cost or price information. If proprietary tools are used for estimating or calculating costs; all inputs, tool settings, and outputs used from these tools shall be provided.

2.2.3 Classified Information

Where classified information is required in your response, it shall be provided as a classified supplement and bound in a single classified addendum to:

ESC/HNS

Attn: Security 5 Eglin Street Hanscom AFB MA 01731-2100

Each entry in the classified addendum shall be referenced to the proposal volume, page number, and paragraph number to which it applies. Similarly, a reference shall be placed in the unclassified volume where the classified insert applies, giving the page and paragraph numbers within the addendum where it can be found. Binding shall conform to the same directions as those given in this ITO for unclassified portions. The classified addendum shall be separately bound with an applicable security designation color cover, conforming to the DD Form 254 and the Security Classification Guide (SCG) provided in this solicitation. Pages in a classified addendum will be included in the page count for the applicable volume.

2.2.4 Cross-Referencing

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

7 (of 44) FA8307-12-R-0003 found in its designated volume will be assumed to have been omitted from the proposal.

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

The Offeror shall fill out the cross-reference matrix at Attachment 1 of this ITO indicating the proposal reference information as it relates to the ITO, Statement of Work (SOW), Work Breakdown Structure (WBS), Integrated Master Schedule (IMS), Integrated Master Plan (IMP), Contract Line Item Number (Numbers (CLIN)), and CDRL references found therein.

2.2.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

2.2.7 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name. The same identifying data should be placed on the spine of each binder. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies.

For electronic copies, indicate on each CD or DVD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The Offeror shall submit volumes one through four in electronic format, using recordable CDs or DVDs. Each volume shall be in a different directory on a CD/DVD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2007, MS Office Excel 2007, MS Office Project 2007, and MS Office Power Point 2007, as applicable. All text (alpha-numeric characters and symbols) shall be fully searchable (i.e., there should be no text in pictures, bitmaps, etc.). In the event that hard copies and electronic copies of a proposal are submitted, and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

8 (of 44) FA8307-12-R-0003

2.4 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the Contracting Officer and mailed or hand carried to: ESC/HNT 5 Eglin Street, Bldg 1624, Hanscom AFB, MA 01731-2100. Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is "For Official Use Only" and "Source Selection Information--See FAR 2.101 and FAR 3.104".

3.0 Volume I - Executive Summary

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

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price.

The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.2 Table of Contents

Include a master table of contents of the entire proposal.

4.0 Volume II - Technical Capability Volume

4.1 General

The Technical Capability Volume must be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical Capability subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible, the actual methodology you would use for accomplishing/satisfying these subfactors. All of the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation.

It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 Format and Specific Content

4.2.1 Technical Capability

In the Technical Capability volume, address your proposed approach to meeting the GTRD requirements described in this RFP, as well as the risks in your proposed approach in terms of Technical Capability performance, cost, and/or schedule.

4.2.1.1 Technical Capability and Proposal Risk

Address Technical Capability Risk by identifying those aspects of the proposal you consider to have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of

9 (of 44) FA8307-12-R-0003 unsuccessful contract performance. Classify each risk in accordance with AFFARS MP5315.3, Table 2 – Technical Capability Risk Ratings. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOW or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigations for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

4.2.2 Volume Organization

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

1. Table of Contents

2. List of Table and Drawings

3. Glossary

4. Cross Reference Matrix

5. Subfactor One

6. Subfactor Two

7. Subfactor Three

4.2.3 Subfactor 1: Architecture, System Design and Performance

4.2.3.1 The Offeror shall describe the hardware, firmware, and software end state architecture; as well as its design, performance, and functionality that achieves all of the requirements as described in the GTRD and tasks as described in the SOW. The description of the architecture and design shall be at a level suitable to convey to the Government that the proposed design will meet all FAB-T GTRD requirements and must identify all risks and mitigation strategies associated with this proposed approach.

The Offeror shall describe in particular how the proposed design meets the following subset of GTRD functional and performance requirements:

(a) System Startup (reference GTRD paragraph 3.3.1.1)

(b) Uplink/Downlink Acquisition and Tracking (reference GTRD paragraphs

3.3.3.1 and 3.3.3.2)

(c) Mission Reliability to include the allocation to software and how it will be achieved (reference GTRD paragraphs 3.10.1.1 and 3.10.1.2)

(d) Probability of Correct Message Receipt (reference GTRD paragraph 3.3.23)

(e) Transmit Power (reference GTRD paragraph 3.3.13.1.2)

(f) Receiver Performance (reference GTRD paragraph 3.3.13.2.2)

(g) Capacity and Data Rate (reference GTRD paragraphs 3.2.2.1.1 and

3.2.2.1.1.1)

(h) System Survivability and Vulnerability (reference GTRD paragraph 3.3.23 and subparagraphs and paragraph 4.2.4)

(i) Security Verifications (reference GTRD paragraphs 3.3.10 and 4.2.10)

(j) Environmental Conditions (reference GTRD paragraph 3.3.26 and all referenced environmental tables)

10 (of 44) FA8307-12-R-0003

The Offeror shall describe the interoperability with the Milstar and AEHF systems, interoperability with Army, Navy and other AF terminal types, and interoperability with all of the systems with which it must interface, including, for example: the AEHF Satellite Mission Control Subsystem (ASMCS), the Mission Planning Subsystem (MPSS), the Presidential and National Voice Conferencing (PNVC) Baseband Interface Group (BIG), and baseband equipment and interfaces defined in the following tables of the GTRD Table 3-2, Red CPTR Baseband Interfaces; Table 3-3 Black CPTR Baseband Interfaces; and Table 3-6, Legacy Devices

4.2.3.2 The Offeror shall describe each hardware and software component, its heritage, the GTRD requirements driving the modifications or development, and the scope of modification and test required to transition to the fully capable FAB-T design.

The Offeror shall describe how the design supports the offeror’s Information Assurance approach and also describe the hardware and software component external and internal interfaces and the verification approach.

4.2.3.3 The Offeror shall identify the Critical Technology Elements (CTEs) and supporting evidence for the Technology Readiness Levels (TRLs) asserted for each CTE. CTEs and TRLs are defined in the “Department of Defense Technology Readiness Assessment (TRA) Guidance”, April 2011. The Offeror shall describe the approach to maturing the CTEs to a level where the technology has been proven to work in its final form and under expected conditions by the end of the development phase, i.e. before production.

4.2.3.4 The Offeror shall describe the approach for selecting the software architecture, processor types, and major interfaces.

4.2.3.5 The Offeror shall describe the proposed software architecture including the technical definition of the proposed software architecture (e.g., processors, buses, languages, object oriented design, open systems), sizing, throughput, and utilization.

4.2.3.6 The Offeror shall identify all software products, including both deliverable and non-deliverable products, developed or otherwise used in the development and delivery of the FAB-T system.

4.2.3.7 The Offeror shall describe the specific Technical Performance Measures (TPMs) for assessing, measuring, or demonstrating design and implementation, measurement schedule, progress and maturity of system compliance to performance requirements.

4.2.3.8 The Offeror shall describe the cryptographic architecture, the major interfaces, a description of how cryptographic functions are employed, and how they meet the requirements of the GTRD. The offeror shall describe the anticipated repair and support concept and identify any specific features that provide realistic advantages for life cycle costs.

4.2.4 Subfactor 2: Program Execution

11 (of 44) FA8307-12-R-0003

4.2.4.1 Schedule: The Offeror shall provide an Integrated Master Schedule (IMS) that is consistent with the FAB-T program milestones in the Integrated Master Plan (Attachment to model contract). Identify most likely critical path(s), margins relative to FAB-T program milestones and effective measure(s) to mitigate identified schedule risk. Include subcontracted activities in this schedule. Address scheduling dependencies with other external organizations (e.g., IA certification, platform integration, etc.).

System Milestone No later than

Demonstration 9 months after ATP Initial Delivery of Command Post Terminals w/PNVC

End of FY15

a. The Offeror shall provide a single IMS in Microsoft Project 2007 format using CDRL B0XX as guidance. At a minimum, the IMS shall contain the lowest CWBS level reflected in the Offeror’s proposal. The IMS shall provide detailed tasks, timelines and significant milestones as described in the IMP (Attachment to Model Contract) and be traceable to the CDRLs, CWBS, CSOW, and CLINs. The IMS shall be able to roll up to level 4 of the CWBS. The IMS shall include all activities to be performed by the Offeror, its proposed subcontractors, and FAB-T contract-related Government activities supported by the Offeror.

b. The Offeror shall provide a schedule risk assessment in this Volume with analytical evidence that indicates the confidence level of the IMS presented. The Offerors shall provide a three-point schedule, at Risk intervals, for all activities included in the IMS, and identify critical path and near critical path items regardless of CWBS level. Near critical path items are tasks that are within 30 calendar days of the critical path. The Offeror shall enter schedule assumptions in a specified field of MS Project (e.g., a Text Field).

c. The IMS shall contain sorting, filtering, and roll-up capabilities by key events for various views (e.g., a one-page top-level view and a multi-page mid-level views, gantt standard view). In addition, the Offeror shall provide a detailed task dictionary that defines tasks and acronyms presented in the IMS. This dictionary may be provided in MS Word.

d. The Offeror shall clearly identify schedule margins along the critical and near critical paths that are consistent with contract deliverables, FAB-T system events and contract milestone reviews.

4.2.4.2 The Offeror shall describe the engineering and management processes that will support the execution of the program and achieve the objectives as described in the SOW. This description shall address the Offeror’s integrated processes from a top-level perspective. The details of the Offeror’s integrated processes effort shall be

12 (of 44) FA8307-12-R-0003 captured in the Offeror’s CSOW, Integrated Master Plan (IMP), and Integrated Master Schedule (IMS).

4.2.4.3 The Offeror shall describe in the Software Development Methodology (SDM), the processes, methods, and practices for:

(a) The software lifecycle model for the program that shows the alignment of software development processes with IEEE/EIA-12207, ISO/IEC-15288, DoD-D-8500, and DoD-D-8570.

(b) Addressing architectural issues for software associated with interfacing the target processor and/or proposed components. Include in the description, a discussion of and rationale for how functionality is allocated across the design.

(c) Incrementally implementing, testing, verifying and demonstrating the following, specifically addressing the Block 1 and Block 2 requirements in the GTRD:

System capabilities (requirements and functionality) Risk mitigation approaches (via design and / or implementation enhancements) Issue resolution (via design and / or implementation enhancements)

(d) The plan to manage the development, integration, verification, and demonstration of future requirements into the system, including the approach to growth and portability of system software in the system/software architecture.

(e) The complete set of Systems/Software Engineering Environment (S/SEE) development and test tools necessary to accomplish the software effort. Include a description of the software development environment and integration labs.

(f) The software development and documentation methodology and the rationale for its selection. Describe both architectural design and detailed software design (e.g., Unified Modeling Language (UML) ™ models, drawings).

(g) The software coding standards that will be implemented on this program.

Standards shall specifically address application of security principles that include high assurance software development principles of least privilege and security of the development.

(h) The methods, tools, and procedures for identifying, categorizing and correcting software vulnerabilities especially as relates to the “SysAdmin, Audit, Network, Security (SANS) Common Vulnerability Enumeration (CVE) and Common Weakness Enumeration (CWE) Top 25 Most Dangerous Programming errors”.

Include specific Information Assurance (IA) and assured coding technique training for software developers and software quality assurance personnel.

(i) Developing, tracking and demonstrating all software builds, inclusive of incrementally implemented capabilities (specifically addressing the GTRD Block 1 and Block 2 requirements and functionality), and all related tasks and activities including:

All builds and related activities, inclusive of incrementally implemented capability demonstrations referenced in the Integrated Master Schedule

(IMS).

13 (of 44) FA8307-12-R-0003

Each build identified in the SDP, IMS, or lower level scheduling/development tools include traceability to specific functions and requirements from the Software Requirements

Document/Technical Requirements Document or lower level specifications that are clearly mapped to Computer Software

Configuration Items (CSCIs) and each CSCI’s functional modules, and are clearly linked to the specific tasks called out in the Integrated Master Schedule (IMS).

(j) Placing all source code developed or obtained for the purposes of this project, including legacy, Free and Open Source Software (FOSS), in a formal software versioning system.

(k) The methods and tools (e.g., Integrated Digital Environment) for providing the Government Program Office with secure access to builds that are under formal configuration control as well as the results of code checks on builds.

(l) Developing software test plans and test cases; identify specific plans and test cases in the IMS.

(m) The types and frequency of software quality control and auditing functions performed including the use of independent code reviews and code coverage;

exception handling, patch management, software entering test; the use of code evaluation tools or other tools for identifying coding errors; vulnerability identification, defect detection and containment (including categorization, prioritization, resolution, and retest).

(n) Tailoring activities based on the criticality of the software (Critical Program Information (CPI) and Critical Technology (CT)).

(o) Identifying and managing security critical and safety critical software along with the implications to the architecture, system, subsystems, hardware, and software.

(p) Conducting software Information Assurance (IA) and vulnerability analyses, detection, and prevention especially for security critical software and any dead or unused code contained within reused or modified products. Include a discussion of outsourcing, selection of vendors, anti-tamper provisions, and anonymity.

(q) Establishing the Software Assurance (SWA) related system architecture, design, and development activities required that includes:

Evaluating software developer-contractor team SWA risks.

Ensuring personnel security clearance.

Securing the development environment.

Evaluating the contractor team’s software development out-sourcing policy.

Identifying system critical COTS software source code pedigree and risk.

Providing repeatable trusted development activities encompassing the complete lifecycle of the system.

Incorporating software vulnerability analysis tools and training.

Ensuring that code changes are assessed to determine the impact on the overall system security posture.

(r) Using software metrics to provide visibility into the software development process and progress.

(s) The software reuse management approach that includes:

14 (of 44) FA8307-12-R-0003

The plan of detailed engineering and management tasks for each software reuse product, and methods for maintaining awareness of reused software sources, maturity, and configurations.

Identification of all code with reuse or open source origins.

Description of all reused code, its specific origin, how it is controlled, how performance requirements have been verified, and how it has been analyzed for vulnerabilities. If vulnerabilities have been identified, the contractor shall describe how they were overcome and why reused or open source code is not a risk to the program.

A process for removal or managing the risk of unused or non-operational code which will remain in the product, consistent with all certification requirements. This explanation shall include the results of analysis that illustrates why it does not present any IA or reliability risks for each application of reused or modified products (e.g., no unknown logic paths or unintended consequences resulting in unknown system states).

4.2.4.4 The Offeror shall identify and describe what analyses and tradeoffs are planned in order to achieve a system design that meets the GTRD requirements.

4.2.4.5 The Offeror shall identify all moderate to high risks to the program and apply the risk process to include for each risk:

(a) Scoring using the standards of Risk Management Guide for DoD Acquisitions, Sixth Edition, Version 1.0, August 2006, and shall provide the metrics and rationale that were used to justify the scoring.

(b) Mitigation plans that describe how the risk will be reduced over time.

(c) Specifically identify risks, if any, associated with the following areas (as a minimum):

i. Terminal Performance

ii. Software development schedule

iii. Software reuse

iv. Software code growth

v. Information Assurance

vi. Security Verifications

vii. System Survivability and Vulnerability

viii. Environmental Qualifications

ix. Terminal Interfaces (both internal and external)

x. Production

4.2.4.6 The Offeror shall describe the Supply Chain Risk Management (SCRM) processes and techniques that will be used to achieve system protection and mission effectiveness to include the approach to identifying, assessing, and mitigating risks of sole-source and foreign sources; addressing counterfeit parts; and the plan to control/load firmware/software for externally acquired products/components.

4.2.4.7 The Offeror shall describe how the technical approach will meet the reliability and maintainability requirements of the program and adhere to the principles and

15 (of 44) FA8307-12-R-0003 guidance of ANSI/GEIA STD-0009. The description shall detail the time phased activities necessary at all levels of the supply chain to model, grow, and maintain the required reliability, as well as the activities necessary to demonstrate that the required reliability has been achieved. The description shall also include how Reliability and Maintainability activities are integrated into the Systems Engineering Process.

Elements to be addressed shall include, but are not limited to:

(a) Reliability and Maintainability Predictions and Models, including Software reliability.

(b) Failure Modes, Effects, and Criticality Analysis (FMECA).

(c) Reliability Integration with Systems Engineering processes.

(d) Reliability and Maintainability Verification.

(e) Reliability Engineering techniques (e.g., Highly Accelerated Life Test, Environmental Stress Screening (ESS), De-rating).

(f) Failure Reporting, Analysis, and Corrective Actions System.

(g) Appropriate R&M expertise and staffing levels across the program life-cycle.

4.2.4.8 The Offeror shall describe specific design features intended to improve producibility, including how they will reduce production cost, production schedules, and/or production risks.

4.2.4.9 Describe the technical approach and the coordination process to address the impacts of integrating FAB-T with the ground, E-4, and E-6 platforms.

4.2.4.10 Describe the approach to hardness assurance planning and the process for ensuring that the proposed design will meet the FAB-T nuclear hardness requirements as follows:

(a) Describe the process for qualifying parts for use in the FAB-T design. This should include, but not limited to, estimating the number of components and time to be qualified, where the work will be done, a description of the facilities and needed test capacity.

(b) Describe the process for controlling sources of parts to maintain hardness.

(c) Describe the process for allocating Probability of Survival (Ps) to LRUs and components and the implications for Radiation Lot Acceptance Testing (RLAT).

4.2.4.11 Describe all certifications required of the FAB-T system to support an Approval to Operate, to include the responsible agency, the criteria and schedule aspects. Identify existing certifications.

Describe Offeror’s approach to attaining the required certifications associated with IA and Security Verifications as follows:

(a) Identify “type 1” certified crypto.

(b) Describe the interface and connection of ancillary capabilities to the crypto.

(c) Describe the certification approach; to include but not limited to, interim certification milestones, and planned risk reduction activities.

(d) Describe any Information Assurance Boundary (IAB) code reviews conducted.

Summarize any category I, II, & III comments and their disposition .

(e) Describe any events, for example but not limited to, NSA reviews, Technical

Review Board (TRB), and FCA/PCA and their outcomes relative to certification.

16 (of 44) FA8307-12-R-0003

4.2.4.12 The Offeror shall identify the location where they will be manufacturing FAB-T products. The Offeror shall describe their manufacturing process for preparing for and producing the system including how quality is assured. The Offeror shall describe their process control methodology. The Offeror shall describe their plan to demonstrate how their proposed production processes, tooling, and test equipment will meet program requirements. The Offeror shall provide an assessment of the maturity of the manufacturing operation that will be used to produce FAB-T terminals using the DoD Manufacturing Readiness Level Deskbook (25 June 2010, Draft) as a guide. The Offeror shall describe the plan to demonstrate pilot line capability and readiness to begin Low Rate Initial Production (LRIP) in time to support the Government Milestone C Decision.

4.2.4.13 The Offeror shall describe their approach to provide sustainment capability for an USAF organic 2 level maintenance concept supporting all system configuration items; manage obsolescence for delivered prime mission equipment and sustainment items; technical data rights; initial training capability and total life cycle cost control.

4.2.4.14 The Government shall consider all data rights unlimited unless the contractor contests these rights. All data and software items shall be listed in Attachment 8, FAB- T Data Assertions List, and the contractor shall provide pricing for any contested rights to the level of Unlimited and Government purpose Rights.

4.2.5 Subfactor 3: Small Business

4.2.5.1 For Offerors that have a Defense Contract Management Agency (DCMA) Review of Contractor’s Comprehensive Subcontracting Program (DCMA Form 640), submit cognizant DCMA Office point of contact name, phone number and address.

For those Offerors, other than small businesses, that do not have a DCMA Form 640 review, the Offeror shall submit information that is commensurate with the information as described in the DCMA Memorandum of Understanding between DCMA and the U.S. Small Business Administration, dated November 12, 2009, which is located on HERBB/FedBizOpps.

4.2.5.2 Small Business Subcontracting Plan (to be submitted as an attachment to the Model Contract per para 7.3.4.2) Offerors, unless otherwise exempt due to being a small business concern or a company performing outside of any State, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto Rico, shall, in accordance with FAR 19.7 and FAR 52.219-9-Alternate II, and DFARS 252.219-7003, submit a Small Business Subcontracting Plan. If the Offeror is a participant in the Department of Defense (DoD) Comprehensive Subcontracting Test program specified in DFARS 219.7, the Offeror shall provide a copy of the approved comprehensive plan. If the offeror is a participant in the DoD Comprehensive Subcontracting Test program specified in DFARS 219.7, the offeror shall provide a copy of the approved

17 (of 44) FA8307-12-R-0003 comprehensive plan. Failure to submit and negotiate a subcontracting plan acceptable to the Contracting Officer shall make the offer ineligible for award of a contract.

4.2.5.3 Small Business Participation Plan (to be submitted as an attachment to the Model Contract per para 7.3.4.2) The Offeror shall submit a Small Business Participation Plan which will be used for the purposes of evaluating the extent to which offerors identify and commit to small business in contract performance on the FAB-T program. The plan will be incorporated into the resulting contract. The Participation Plan is required from all offerors, including small businesses and companies with commercial subcontracting plans and comprehensive subcontracting plans.

A. The following target small business participation goals are provided to "assist" in the development of your Small Business Participation Plan. The percentages are based on total subcontracting dollars and first, second and third tier subcontracting dollars can be counted towards meeting your small business participation goals.

Small Business - TBD Small Disadvantaged Business - TBD Woman-Owned Small Business - TBD HUB Zone Small Business - TBD Service-Disabled Veteran-Owned Small Business - TBD Veteran-Owned Small Business - TBD

B. ALL offerors shall provide (1) through (3) below:

1) A table which lists the following:

a) All proposed first, second, and third tier subcontractors, individually by name with their addresses

b) Subcontractor business type (large, small (SB), small disadvantaged to include HBCU/MI (SDB), women-owned (WOSB), HUB Zone, veteran-owned (VOSB), service-disabled veteran-owned (SDVOSB)), as determined by the SBA size standard for the specific work being subcontracted. List all applicable categories for each subcontractor.

c) The principal service/supply being provided by the subcontractor.

d) The complexity of the service/product provided. A brief narrative on complexity of subcontract services/products must describe:

Product: Complex performance specifications or stringent tolerances Services: Advanced professional skills or application of innovative technologies.

e) Expected dollar value of the subcontract.

2) A table which summarizes the total 1st, 2nd and 3rd tier subcontract dollars proposed for each category of small business: SB, SDB, WOSB, HUBZone, VOSB and SDVOSB. Subcontractors that qualify for inclusion in more than one category shall be included in each category for which they qualify. For example, the value of subcontracts at all three tiers to be awarded to a WOSB in a HUBZone shall be included in WOSB, HUBZone and SB totals.

18 (of 44) FA8307-12-R-0003

3) A copy of binding agreements and enforceable commitments executed with the firms identified in the table required by B.1 above.

A sample of the table described in B.1 is provided below

Name of 1st, 2nd, and 3rd Tier Subcontractors

Subcontractor Address

Type of Business (Large, SB, HUBZone, SDB,WOSB, VOSB, SDVOSB)

Principal Supply/Service Provided

Complexity of Product/Service Provided

Dollar Amount of Subcontract

XYZCorp. 123 Main St.

Anytown, NY 01345

Large Castings Manufactured to .01 tolerance

$1,500,000

Acme, Ltd. 456 First Ave.

Somewhere, NY 54321

SB, SDB,

VOSB

Logistics software

Utilizing ISO 9000 and S100D Standards with

XML

$ 75,000

Note 1: The CCR & SBA Dynamic Small Business Search (http://www.bpn.gov/ccr/ and http://web.sba.gov/pro-net/search/dsp_dsbs.cfm) databases will be viewed to verify the small business category or categories of the proposed small businesses in the table. The offerors shall list all applicable business types for which each subcontractor qualifies. The definition of a small business concern is as set forth in 13 CFR 121.105. The definition of subcontractor is as set forth in FAR 19.701.

Note 2: The Participation Plan is in addition to, not in place of, the subcontracting plan. If a subcontracting plan is required, (See FAR 19.702.) the plan shall be submitted by the offeror in accordance with FAR 52.219--9 - Alternate II stating cumulative subcontracting goals and for each option in dollars, percentages of total subcontracted amount and percentage of total contract value. (See AFFARS 5319.704(a)(1).)

Note 3: Offerors are reminded that in accordance with DFARS 215.304(c)(i) (C), the small businesses and HBCU/MIs considered in evaluation shall be listed in any subcontracting plan submitted pursuant to FAR 52.219-9 to facilitate compliance with DFARS 252.219-7003(g). In addition, all goals accepted and incorporated into the resulting contract will be subject to FAR Clause 52.219-16, liquidated Damages- Subcontracting Plan", unless the offeror is a participant in the Comprehensive Subcontracting Program.

Note 4: Offerors are reminded that the Small Business Subcontracting Plan (required from large businesses only) shall correlate with the proposal information on small business participation as well as all other sections of the proposal.

4.2.5.4 Small Business Innovation

19 (of 44) FA8307-12-R-0003

The offeror shall cite current and planned initiatives to assist, promote, and utilize all categories of small business in the FAB-T program. Demonstrate examples of how the offeror is maximizing SB opportunities and using SB in mission critical aspects (e.g.

technology innovation) throughout the proposed program.

5.0 Volume III - Past Performance

5.1 General

Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 2. This information is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 30% or more of the proposed effort based on the total proposed price or perform aspects of the effort the Offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the Offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance.

5.2 Relevant Contracts

Offerors intending to serve as…