SECTION_L.pdf

Attachment 4 - Section L

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

L-I - Solicitation Provisions Incorporated by Reference

NOTICE: Pursuant to FAR 52.252-1, "SOLICITATION PROVISIONS INCORPORATED BY REFERENCE," the following provisions are incorporated herein by reference:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION

PROVISIONS:

PARAGRAPH TITLE DATE

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION

SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT

SOLICITATION PROVISIONS:

D. MAJCOM FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION

file:///C:/Users/FarringtonB/Desktop/far/FAR52.246.doc%23b522521

L-II - Solicitation Provisions in Full Text

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

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION

PROVISIONS:

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION

SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT

SOLICITATION PROVISIONS:

D. MAJCOM FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION

E. ADMINISTRATIVE AND ONE-TIME USE PROVISIONS:

L-III - INFORMATION TO OFFERORS (ITO)

AND INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The FAB-T program will make use of an approach which will provide for award of up to two development/production contracts after a full and open, best value competition.

The contracts will include options to effectuate a possible down-select to one contractor for production. This approach allows the program to maintain competition for the maximum time based on available funding. The initial development effort will include an FPIF contract for Command Post Terminal (CPT) with Presidential and National Voice Conferencing (PNVC) capability, with FPIF and FFP options for production of this capability. The contract will also include an FPIF option for the development of Integrated Tactical Warning and Attack Assessment (ITW/AA) and TT&C capability, and associated FFP options for production.

A demonstration will be conducted during the source selection. The demonstration will be used in evaluating the technical risk associated with Offeror’s proposed technical solution.

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

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. The FedBizOpps web page is http://www.fedbizopps.gov/.

file:///C:/Users/FarringtonB/Desktop/far/FAR15.DOC%23b15505 file:///C:/Users/FarringtonB/Desktop/far/FAR15.DOC%23b15506 http://www.fedbizopps.gov/ http://www.fedbizopps.gov/

2.1.5. Oral Presentations

The oral presentation shall discuss 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. In addition, the oral presentation shall discuss the proposed technical approach for transitioning and operating all aspects of the FAB-T end state, the assumption(s) that the plan is based on, and the risks that could limit the Offeror’s ability to complete the transition.

The Offeror shall discuss the objectives, success criteria, scope of the demonstration, the complete architecture of the demonstration environment (to include, for example, the drivers/simulators) and associated demonstration methodology. At the conclusion of the demonstration, the Offeror shall provide an outbrief including a summary of their objectives, success criteria, and results.

The oral presentation and the conduct of the demonstration shall not exceed 8 hours.

Ten (10) copies of all briefing materials shall be provided prior to the oral presentation.

Any chart included in the submitted briefing materials but not briefed during the established time limits will not be evaluated.

The Government will notify Offerors by phone, email, or FAX of the order of presentations by ____________

By ____________the Offeror must notify the Contracting Officer in writing of the name, phone, e-mail, and FAX number of the individual to whom the Government should give notice.

Each Offeror is required to provide a recording (voice and video) of the demonstration and the oral presentation to the Government.

2.1.5.1 Demonstration

2.1.5.1.1 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.6) as possible.

2.1.5.1.2 The demonstration shall be conducted at the Offeror’s facility with the Offeror’s equipment.

2.1.5.1.3 The Offeror shall submit the following with the written proposal submission:

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

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

A description of all major 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 relates to the proposed end state.

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 includes ―Source Selection Information – See FAR 2.101 & 3.104‖ in the Subject line.

Otherwise, source selection information will be transmitted via _________.

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 file:///C:/Users/FarringtonB/Desktop/far/Far02.doc%23T2101 file:///C:/Users/FarringtonB/Desktop/far/FAR03.DOC%23b3104

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:

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

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 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), Performance Work Statement (PWS), 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 fourin http://www.dtic.mil/whs/directives/infomgt/forms/forminfo/forminfopage51.html file:///C:/Users/FarringtonB/Desktop/far/FAR52.215.doc%23b522151 file:///C:/Users/FarringtonB/Desktop/far/FAR03.DOC%23b31044 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.

2.4 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the Contracting Officer and mailed or hand carried to: 104 Barksdale St, Bldg 1520, Hanscom AFB, MA 01731-2117.

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

file:///C:/Users/FarringtonB/Desktop/far/Far02.doc%23T2101 file:///C:/Users/FarringtonB/Desktop/far/FAR03.DOC%23b3104

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

In accordance with DODI 8580.1, Information Assurance (IA) in the Defense Acquisition System and DODI 5200.39, DODI Critical Program Information (CPI) Protection Within the DoD, the contractor shall provide CPI and information necessary for the preparation of a Program Protection Plan (PPP) to be completed by the government in accordance with the PPP outline and guidance, version 1.0 dated July 18, 2011, and subsequent revisions from the Deputy Assistant Secretary of Defense for Systems Engineering. The contractor shall provide information the government requires to prepare the PPP, as required by DODI 5000.02, Operation of the Defense Acquisition Systems and DODI 5200.39. CPI must be protected by the contractor.

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 hardware, firmware, and software end state architecture; as well as its design and functionality that achieves all of the requirements as described in the GTRD and objectives as described in the SOW. The description of the architecture and design shall be at a level suitable to convey to the Government file:///C:/Users/FarringtonB/Desktop/Downloads/MP5315.3.doc%23p5512 file:///C:/Users/FarringtonB/Desktop/Downloads/MP5315.3.doc%23p5512 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) 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 Element (MPE), 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 also describe the 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. 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.

4.2.3.4 The Offeror shall describe the approach for selecting the software architecture, processor types, and major interfaces; and a description of how the process considers the incorporation of open architecture into the system design process.

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, growth capacity, software specific information assurance aspects, and technology update/refresh strategy.

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, implementation, and testing progress and maturity as well as compliance to performance requirements.

4.2.4 Subfactor 2: Integrated Processes

4.2.4.1 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 captured in the Offeror’s CSOW, Integrated Master Plan (IMP), and Integrated Master Schedule (IMS).

4.2.4.2 The Offeror shall provide, in the Software Development Methodology (SDM), the methods, practices, and FAB-T- specific tailoring that:

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

(b) Describes the specific isolation features within the software architecture that will allow portability of the software from one member of a processor family to another, or to another processor family.

(c) Describes the approach for 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. Also discuss how the software is designed to be portable within a processor family or across processor families with minimal impact to the software design.

(d) Establishes the process for incrementally implementing, testing, verifying and demonstrating the following:

System capabilities (requirements and functionality)

Risk mitigation approaches (via design and / or implementation enhancements)

Issue resolution (via design and / or implementation enhancements)

(e) Describes 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.

(f) Establishes 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.

(g) Establishes 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). If other than UML is used, the contractor shall describe the rationale for selecting an alternate notation as well as the level of its standardization.

(h) Establishes 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.

(i) Establishes 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.

(j) Establishes the approach to developing, tracking and demonstrating all software builds, inclusive of incrementally implemented capabilities (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).

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

(k) Establishes the process for 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.

(l) Describes 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.

(m) Establishes the procedures for developing software test plans and test cases;

identify specific plans and test cases in the IMS.

(n) Establishes 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).

(o) Describes how activities are tailored based on the criticality of the software (Critical Program Information (CPI) and Critical Technology (CT)).

(p) Establishes the process for identifying and managing security critical and safety critical software along with the implications to the architecture, system, subsystems, hardware, and software.

(q) Establishes the approach to 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.

(r) Establishes 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.

(s) Describes the plan for using software metrics to provide Government management visibility into the software development process and progress.

(t) Establishes the software reuse management approach that includes:

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.

For any unused code, an explanation of why unused code will remain in the product. 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).

Describe how dead code will be removed or the process for providing a risk assessment to the Government as part of a request to retain the dead code in the product.

4.2.4.3 The Offeror shall define the minimum CMMI maturity level at which they will operate all processes on the FAB-T program.

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 Identify all moderate to high risks to the program and apply or describe your 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 code growth

iv. Information Assurance

v. Security Verifications

vi. System Survivability and Vulnerability

vii. Environmental Qualifications

viii. Terminal Interfaces (both internal and external)

4.2.4.6 The Offeror shall describe the method they will apply Supply Chain Risk Management (SCRM) as well as control of sensitive information (e.g., obfuscation) in dealing with subcontractors and suppliers.

4.2.4.7 The Offeror shall describe how their technical approach will meet the reliability and maintainability requirements of the program and adhere to the principles and 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 describe 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 their approach to hardness assurance planning and their 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 include the responsible agency, the criteria and schedule aspects. Identify existing certifications.

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

4.2.4.13 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.14 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.15 The Government desires to obtain or have the ability to obtain Government Purpose Rights and necessary proprietary data to support the system in sustainment.

In Attachment XX in the model contract, the Offeror shall identify and price any technical data or software that will be delivered with restrictions on use, reproduction or disclosure. All asserted limitations on data rights shall include supporting documentation. The Offeror shall provide a roll up of all prices for technical data or software with less than Government Purpose Rights for Option XXX. Any technical data or software deliverables not mentioned in Attachment XX, will be conveyed with Unlimited Rights.

4.2.5 Subfactor 3: Small Business

4.2.5.1 For Offerors that have a Defense Contract Management Agency (DCMA) review of Offeror’s Small Business Subcontracting Program (DCMA Form 640), submit the DCMA Form 640. 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. This factor will be evaluated on a PASS/FAIL basis.

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 _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 a Prime shall submit information in accordance with Attachment 2 on five (5) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on one (1) recent contract performed by three (3) of your key teaming partners or subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, paragraph 1.4.9. Only ongoing work or work completed during the past three (3) years from the date of issuance of this solicitation will be considered.

5.2.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an Offeror has overcome past problems is required. Categorize the relevant information into the specific Technical Capability subfactors and Cost/Price factor used to evaluate the proposal.

5.2.2 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

6.0 Volume IV - Cost/Price

6.1 General Instructions

6.1.1 Cost or Price Reasonableness and Realism

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed cost/price.

Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness.

The burden of proof for credibility of proposed costs/prices rests with the offeror.

6.1.2 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non- Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the work breakdown structure (WBS).

6.1.3 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.1.4 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5 . If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

6.1.5 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154031 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154033 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154035 https://cs.eis.af.mil/airforcecontracting/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC#b154031

6.1.6 Subcontractors Cost or Price Reporting Requirements

Any subcontractor that will be responsible for 10% or more of the proposed effort must submit separate Cost/Price Volumes in accordance with the guidelines given to the Prime Contractor/Offeror below. Proposal may be submitted directly to the government if information is considered to be proprietary.

6.2 Volume Organization

SECTION 1 – The Offeror shall prepare a proposal summary that includes an introduction, table of contents, overview, and summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement. An Earned Value Management System summary, labor category descriptions, escalation rates, and month to hour labor conversions shall also be included.

SECTION 2 – The Offeror shall provide cost or pricing information on cost formats as provided in Appendix X and in accordance with the directions below.

SECTIO…