Section_L.pdf

SECTION L: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

SECTION L: RFP FA8806-14-R-0001 Page-1

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES

TO OFFERORS

Range and Network Division

Systems Engineering and Integration

FA8806-14-R-0001

5 March 2015

SECTION L: RFP FA8806-14-R-0001 Page-2

[This page intentionally blank]

SECTION L: RFP FA8806-14-R-0001 Page-3

TABLE OF CONTENTS

1 Program Structure and Objectives

1.1 Budget/Funding Information

1.2 Schedule Information

2 General Instructions

2.1 General Information

2.1.1 Point of Contact

2.1.2 Debriefings

2.1.3 Discrepancies, Errors, and Omissions

2.1.4 Electronic Reference Documents (Bidders’ Library)

2.1.5 Communication

2.1.6 Consideration of Alternate Proposals

2.1.7 Use of Non-Government Advisors

3 Proposal Submission and Electronic Format

3.1 Proposal Delivery

3.2 Submission of Electronic Proposals

3.3 Organization/Number of Pages/Page Limits

3.4 Page Size and Format

3.5 Binding and Labeling

3.6 Cross-referencing

3.7 Indexing

3.8 Classified Information

4 Volume I – Executive Summary

4.1 Offeror’s Proposed Team

4.2 Proposal Approach

4.3 Organization and Management

4.4 Attachment E1 to Volume I: Master Table of Contents and Cross-Reference Matrix

5 Volume II – Technical

5.1 General Instructions

5.2 Format and Specific Content

5.2.1 Subfactor 1: Integration

SECTION L: RFP FA8806-14-R-0001 Page-4

5.2.2 Subfactor 2: Systems Engineering

5.2.3 Subfactor 3: Domain Knowledge

5.2.4 Subfactor 4: Program Management

5.2.5 Technical Volume Attachments

6 Volume III – Cost/Price

6.1 General Instructions

6.1.1 Cost/Price Reasonableness and Realism

6.1.2 Estimating Techniques and Methods

6.1.3 Cost/Price Data

6.1.4 Cost or Pricing Data Requirements

6.1.5 Rounding

6.1.6 Pricing Arrangement/Contract Type

6.1.7 General

6.2 Cost/Price Volume Organization

6.2.1 Section 1 – Introduction

6.2.2 Section 2 – Data other than Certified Cost/Price Data

6.2.3 Cost Summary by Cost Elements

6.2.4 Probable Subcontractors

6.2.5 Schedule of Rates

6.2.6 Special Studies

6.2.7 Extension of Services Instructions (FAR 52.217-9, Option to extend services)

6.2.8 Cost Attachments

7 Volume IV – Past Performance

7.1 General

7.2 Offeror's overall past performance Volume IV, Past Performance Submittal

7.3 Relevant Contracts

7.4 Specific Volume Content

8 Volume V – Contract Documentation

8.1 Solicitation/Representations and Certifications

8.1.1 Volume V, Section A: Solicitation/Contract Form

8.1.2 Volume V, Section B: Supplies or Services and Costs/Prices

8.1.3 Volume V, Section G: Contract Administration Data

SECTION L: RFP FA8806-14-R-0001 Page-5

8.1.4 Volume V, Section H: Special Contract Clauses

8.1.5 Volume V, Section I: Contract Clauses

8.1.6 Volume V, Section J: List of Attachments

8.2 Attachments to the Solicitation

8.2.1 Exhibit A to Volume V: Contract Data Requirements List

8.2.2 Attachment CD1 to Volume V: Contract Work Breakdown Structure

8.2.3 Attachment CD2 to Volume V: DD 254 Contract Security Classification

8.2.4 Attachment CD3 to Volume V: Organization Conflict of Interest Mitigation Plan .41

8.2.5 Attachment CD4 to Volume V: Compliance and Reference Document List

Tailoring

8.2.6 Attachment CD5 to Data Rights Document

8.2.7 Attachment CD6 to Performance Incentive Plan

8.2.8 Attachment CD7 to Government Furnished Equipment/Government Furnished

Information

8.2.9 Attachment CD8 to Professional Employee Compensation

8.2.10 Appendix A to Volume V: Representations and Certifications

8.2.11 Appendix B to Volume V: Exceptions to Terms and Conditions

8.2.12 Appendix C to Volume V: Authorized Contractor Representatives

8.2.13 Appendix D to Volume V: Cognizant Government Offices

8.2.14 Appendix E to Volume V: Administrative Changes

SECTION L: RFP FA8806-14-R-0001 Page-6

TABLES

Table 1 Planned Government Funding ($M, includes fee)

Table 2 Proposal Organization

Table 3 Cross-Reference Matrix (sample)

Table 4 Technical Volume Table of Contents

Table 5 Process Maturity Matrix

Table 6 PWS Task Status Table

Table 7 Proposed Staffing with Years of Experience (one for each year)

Table 8 Designated Key Personnel

Table 9 Sample Efficiencies Table

Table 10 Cost/Price Volume Outline

Table 11 Sample of Cost Summary Table

Table 12 Relevant Contracts

Table 13 Solicitation Exceptions

FIGURES

Figure 1 RN SE&I Mission Partners

SECTION L: RFP FA8806-14-R-0001 Page-7

Information To Offerors (ITO)

For

Range and Network Systems Engineering & Integration (RN SE&I)

1 Program Structure and Objectives

The Range and Network (RN) Division will acquire an SE&I contractor to produce and manage the technical baselines for the Division. The Government maintains complete oversight and final decision authority and accountability for all key SE&I functional and technical baseline products, but assigns the responsibility for executing key functions and products to the SE&I contractor. Specific tasks areas for which the Government will retain responsibility are based on the following criteria: (1) Government-only functions per FAR requirements where the

Government has well-established internal domain expertise to effectively perform the task area;

and (2) tasks the Government has retained to avoid/mitigate potential organizational conflict of interest (OCI) issues. The SE&I contractor’s tasks will be interdependent and cooperative but not duplicative with those that are performed by the Government’s organic (military and civilian) resources, Federally Funded Research and Development Centers (FFRDC) contractors, development and sustainment prime contractors and Systems Engineering and Technical

Assistance (SETA) contractors. The RN SE&I contractor will be responsible for all products and deliverables described in the performance work statement (PWS).

The focus of this effort is to integrate new systems and services into the baseline and goes beyond simply executing systems engineering processes. This contract provides expertise to establish relationships, processes, and other execution tools needed to overcome the technical, operational, and cultural challenges. Furthermore, this contract will bring the same level of capability across RN’s three separate and distinct baselines: Launch & Test Range System

(LTRS), Air Force Satellite Control Network (AFSCN), and Space Training Acquisition Office

(STAO).

The top priority for the RN SE&I contract is to provide robust integration capabilities to RN acquisition and operational stakeholder communities on modernization and sustainment projects.

RN is comprised of three different technical baselines. LTRS, AFSCN, and STAO programs are primarily in sustainment. These programs contain large projects to modernize and sustain the three systems. Having an integration contractor to help bridge the gap between the sustainment, operations and acquisition communities is critical to the warfighter receiving the proper hard-ware and software to complete their mission. The RN SE&I contractor will help RN get projects operationally accepted and turned over to the appropriate Government customers.

The RN SE&I contractor will be held responsible for all phases of the life cycle integration. The

RN SE&I contractor will help in the development of Request for Proposals (RFPs) for sustain-ment and development contractor efforts, which may include the following, Sections L&M

(instructions and evaluation criteria), Statement of Work (SOW)/PWS, Exhibit A/Contract Data

Requirements List (CDRLs), requirement documents, interface documents, employment concept, and project architecture. The RN SE&I contractor will also assess all applicable RFP components and recommend relevant system integration, technical, and programmatic details.

The RN SE&I contractor will review all submitted proposals. The RN SE&I contractor will facilitate and coordinate acquisition activities involving both Government and industry.

SECTION L: RFP FA8806-14-R-0001 Page-8

The RN SE&I contractor will also develop, document, execute (upon Government approval), maintain, and evolve key RN processes to aid in integration. This includes technical baseline management; implementing the Government-defined architecture; requirements and interface control, risk and opportunity management; systems engineering planning; configuration management (CM); data management; interface control; information assurance (IA)/ cybersecurity; test, evaluation and verification; modeling, simulation and analysis; acquisition logistics and sustainment; schedule management; and systems safety. The detailed task descrthis matrixions are provided in the PWS for the RN SE&I efforts.

The scope of the SE&I ranges from performing systems integration in each of RN’s three programs down to performing systems engineering for a specific integrated product team (IPT) within one of RN’s programs. To achieve these ends, the contractor will be required to support the acquisition strategies based on innovative best value solutions, proven business concepts, and best practices to provide RN with repeatable, defined, accurate, timely, well-documented and managed processes that produce quality deliverables that meet system operator and user needs.

The RN SE&I contractor’s role in the accomplishment of the mission will involve tracking of modernization projects and interaction with Government customers to ensure successful integration, development and implementation of common processes and facilitation of improved and dynamic communications; development of new tools and techniques to predict risks/issues early enough in modernization; development contract efforts to minimize the effect on the specific RN program; development and maintenance of a disciplined process for systems baseline documents and interfaces; integration of modernization and sustainment projects that meet operational user requirements.

As illustrated below in Figure 1, RN SE&I Mission Partners, the SE&I contractor will be a mission partner in the integration of three RN program’s technical management and systems engineering activities. The end result will be a robust integration team to help RN provide modernization and sustainment products to its operational stakeholders.

Figure 1 RN SE&I Mission Partners

SECTION L: RFP FA8806-14-R-0001 Page-9

1.1 Budget/Funding Information

Table 1 is the funding profile the Government plans to make available for the RN SE&I contract.

The Government does not guarantee that such funds will be appropriated for any particular fiscal year. This is for informational purposes only.

Table 1 Planned Government Funding ($M, includes fee)

FY16 FY17 FY18 FY19 FY20 FY21 TOTAL (FY16-21)

$43 $43 $41 $42 $42 $43 $254

1.2 Schedule Information

The RN SE&I contract will be a one year contract plus five one-year options with one possible six-month extension of services option in accordance with FAR 52.217-9, Option to Extend

Services.

2 General Instructions

Each Offeror’s proposal must include all data and information requested in Section L and be submitted in accordance with these instructions. In developing the proposal, the Offeror shall comply with all the requirements contained in the solicitation. Non-conformance with the instructions provided in the Instructions to Offerors (ITO) may result in an unfavorable proposal evaluation.

The Government will evaluate proposals and reserves the right to award a contract without conducting discussions with the Offerors except for clarifications as described in FAR 15.306(d)

(3). Therefore, each Offeror’s initial proposal should contain the Offeror’s best terms from the cost, price and technical standpoints.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated assertions. The proposal should not simply rephrase or restate the Government’s requirements, but rather provide convincing rationale to address how the Offeror intends to meet these requirements. The Offeror shall assume the Government has no prior knowledge of the Offeror’s capabilities and experience. The Government will perform its evaluation based on the information presented in the Offeror’s proposal.

Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not to be submitted.

The proposal acceptance period is specified in Section A of the solicitation. The Offeror shall make a clear statement in Section A of Volume V Solicitation of the Offeror’s proposal that the offer is valid for a minimum of 365 calendar days from proposal submission.

In accordance with FAR 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.

SECTION L: RFP FA8806-14-R-0001 Page-10

2.1 General Information

2.1.1 Point of Contact

The Procuring Contracting Officer (PCO), Mr Alan R. Mak, is the sole point of contact for this acquisition. Address any questions or concerns to the PCO at (310) 653-1472 or via e-mail at alan.mak@us.af.mil. On all e-mail correspondence, courtesy copy the Contract Specialist, Mr Albert Yeh, at albert.yeh.2@us.af.mil.

2.1.2 Debriefings

The PCO 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. An Offeror desiring a debriefing must make its request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.1.3 Discrepancies, Errors, and Omissions

If an Offeror believes the requirements in these instructions lack clarity or contain an error, omission, or are otherwise unsound, the Offeror shall immediately contact the PCO in writing with supporting rationale and remedies the Offeror is asking the PCO 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.

2.1.4 Electronic Reference Documents (Bidders’ Library)

2.1.4.1 A Bidders’ Library has been established containing the compliance and reference documents relevant to RN SE&I. All Offerors will need to have/complete the following for access:

(1) DoD approved Common Access Card or External Certification Authority

(2) Information Assurance/Information Protection completion certificate

(3) Livelink User Agreement (2 Apr 2008)

(4) DD Form 2875 (August 2009), System Authorization Access Request

For all Bidder’s Library Access requests, please contact Mr Yeh at albert.yeh.2@us.af.mil.

2.1.5 Communication

Exchanges of source selection information between Government and Offerors will be made only through the PCO. Email may be used to transmit such information to Offerors only if the email can be sent and received password protected, encrypted, and includes “Source Selection

Information - see FAR 2.101 & 3.104” in the subject line.

2.1.6 Consideration of Alternate Proposals

Proposals that depart from the stated requirements within the PWS or do not meet program objectives will be considered alternate proposals, and will not be considered for award.

SECTION L: RFP FA8806-14-R-0001 Page-11

2.1.7 Use of Non-Government Advisors

Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who are employed by the following companies as non-Government advisors for review and analysis:

Company Name Address

The Aerospace Corporation (FFRDC) P.O. Box 92957

Los Angeles, CA 90009-2957

Space EA Systems 222 N. Sepulveda Blvd, Suite 2000

El Segundo, CA 90245

BTAS, Inc. 400 Continental Blvd, Suite 600

El Segundo, CA 90245

Per DoD Source Selection Procedures, paragraph 1.4.5.2.1, the PCO must obtain written consent from the Offeror before release of their proposal information to any non-Government advisor.

The Offeror shall expressly state in the Executive Summary (Volume I) whether or not it consents to the release of its proposal information to the above non-Government advisors.

The individuals participating in the review and analysis of proposals have signed individual non-disclosure agreements with the Government which strictly prohibits any release or disclosure of information outside of the source selection team.

These contractors also have 'associate contractor agreements' in their contracts that require them to work with any other contractor (or Offeror) in order to provide any other agreements that may be necessary to carry out their contracted activity. Therefore, before an Offeror objects to release of its proposal information to these non-Government advisors, you are strongly encouraged to engage early with these companies to obtain any other agreements required for sharing proposal information with these non-Government advisors.

3 Proposal Submission and Electronic Format

3.1 Proposal Delivery

Electronic and paper copies of the original proposal must be received by Monday, 27 April 2015 at 3:00 PM PDT. The delivery address for the written proposals is: Space and Missile Systems

Center, 483 N. Aviation Blvd., El Segundo, CA 90245-2808, to the attention of the PCO, Mr

Alan R. Mak. A transmittal letter may be used to forward the proposal to the PCO. This letter is only for administrative purposes and will not be evaluated. Delivery of proposals shall be coordinated at least 24 hours in advance of the due date/time with the PCO. Proposals received after the due date at noon, Pacific Time, shall be treated in accordance with FAR 15.208.

The Government requests Offerors submit Attachment CD3 to Volume V, the OCI Mitigation

Plan, within 21 calendar days of RFP release.

The Government requests Offerors submit Volume IV, Past Performance, within 21 calendar days of solicitation release.

SECTION L: RFP FA8806-14-R-0001 Page-12

NOTE: If any section of the Past Performance Volume IV is classified above SECRET (up to

TOP SECRET(TS)/SENSITIVE INFORMATION(SI)/TALENT KEYHOLE(TK)), it must be provided in paper-only format (no electronic media) and hand-delivered to the RN Division

(Security Office, Point of Contact Mr Vernal Bitton). The submitting entity must pre-coordinate with the program office, before official delivery. The following information must be provided for the individuals making the delivery: Sensitive Compartmented Information (SCI) security clearance and a point of contact (POC), as well as an inventory of items to be delivered.

3.2 Submission of Electronic Proposals

The Offeror shall submit copies of the proposal as defined in Table 2 Proposal Organization, below. The Offeror shall submit Volumes I, II, III, and V in electronic format, using CDs or

DVDs. Submit two electronic soft copies on separate CDs or DVDs. Each volume shall be in a separate directory or folder. The content and page size of electronic copies must be identical to the hard copies. In the event there are any inconsistencies between the hardcopy and softcopy of the proposal, hardcopies will take precedence. The CDs or DVDs shall be labeled with the

Offeror’s name, submission date and the volume number(s). The Offeror shall submit Volume

IV in electronic format in accordance with timelines defined in Section L, paragraph 3.1. How-ever, any section of Volume IV that is classified (up to TS/SI/TK) shall be delivered in paper format only and not in electronic media.

The electronic copies of the proposal shall be in a format readable by Adobe Portable Document

Format (PDF) Reader 9.0 (with “Select” and “Copy” enabled to allow for text and graphics transfer), Microsoft (MS) Word 2007, MS Excel 2007, MS Project 2007, or MS PowerPoint

2007. The narrative for Volume III shall be in MS Word 2007 format. The RN SE&I Cost Price

Template shall be in MS Excel 2007 format. For the Volume I, II, III, and V submission, all CD-

ROMs/DVDs shall be placed in plastic sleeves and submitted in the Volume I binder. For the

Volume IV submission, all CD-ROMs/DVDs shall be placed in plastic sleeves and submitted with the Volume IV binder. Hypertext links may be used to facilitate navigation within the document. Use separate files to permit rapid location of all portions, including exhibits, annexes, and attachments, if any. No file compression is allowed.

The PCO, at the request of any Offeror, may allow early “uploading” of sample proposal information on the Air Force servers used for source selection, time permitting, and subject to availability of the source selection facility. This information would be checked for compatibility with the source selection facilities servers, workstations and source selection software. All information in this “test run” would not be part of the source selection evaluation and will be erased upon completion of the test. The Offeror will notify the PCO no later than 14 calendar days prior to the proposal due date if it wishes to take advantage of uploading sample proposal information with the Air Force servers. The Offeror would provide sample data on a CD/DVD and the Government would perform compatibility tests with the source selection facilities servers. Any sample proposal information shall be in the same format as the proposal to be delivered. Whenever possible, the file name should also include an indication of the contents.

For example, “MC2_Att2_IMS” is preferred over “MC2_Att2”.

3.3 Organization/Number of Pages/Page Limits

The Offeror shall prepare the proposal as set forth in Table 2 below. A complete proposal consists of the following:

SECTION L: RFP FA8806-14-R-0001 Page-13

a. Five separate volumes and attachments, all of which shall be within the required page limits specified in Table 2. Specific bounding instructions are cited for attachments requiring separate binding. The format of the proposed volumes shall correlate directly with the instructions in Section L. The proposal must provide a direct correlation to the specific questions and requirements given in each instruction.

b. 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 pages will be returned to the

Offeror as soon as practicable. Page limitations do not apply to title pages, tables of contents, list of figures, list of abbreviations, glossaries, or indexes. A cross-reference matrix shall not be counted in the page limits. Number all pages. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified limits for EN responses will be identified in the communications forwarding the ENs to the Offerors.

c. The Offeror shall use a common paragraph numbering system among the tasking statements in the Contract Work Breakdown Structure (CWBS) consistent with the PWS and Work

Breakdown Structure (WBS).

Table 2 Proposal Organization

Volume Title Soft

Copies

Hard

Copies Page Limit

I Executive Summary, not including Cover

Letter

2 2 5

Attachment E1: Master

Table of Contents and

Cross-Reference Matrix

2 2 Unlimited

II Technical 2 2 See below

Technical Volume

(excluding attachments) 2 2

100 pages (Integrated

Master Plan (IMP) and

Integrated Master

Schedule (IMS) for scenarios does not count toward page limit)

Attachment T1:

Program Management

Plan

2 2 50

Attachment T2:

Resumes of Key

Personnel, Proposed

Staffing with Years of

Experience and

Statements of

Assurance

2 2

Two pages per resume;

25 pages for proposed staffing and justification;

one page per statement

SECTION L: RFP FA8806-14-R-0001 Page-14

Volume Title Soft

Copies

Hard

Copies Page Limit

Attachment T3:

Transition Plan 2 2 25

Attachment T4:

Efficiencies Table 2 2 5

III Cost/Price 2 2 See below

Cost/Price Narrative 2 2 Unlimited

Attachment CP1: RN

SE&I Contractor Cost

Price Template

Not

Required Unlimited

IV Past Performance 2 2

15 pages

(subcontractor/teaming partner consent forms, and organizational structure change history does not count toward page limit)

V Contract

Documentation 2 2 See below

Standard Form 33 and

Solicitation (Sections

A-K)

2 2 Unlimited

Exhibit A: Contract

Data Requirements List

Attachment CD1:

CWBS

2 2

60 pages (shall be bound separately from Volume

V - Contract

Documentation)

Attachment CD2: DD

Form 254 2 2 Unlimited

Attachment CD3: OCI

Mitigation Plan 2 2 Unlimited

Attachment CD4:

Compliance and

Reference Documents

List

2 2 5 pages

SECTION L: RFP FA8806-14-R-0001 Page-15

Volume Title Soft

Copies

Hard

Copies Page Limit

Attachment CD5:

Rights in Technical

Data

2 2 5 pages

Attachment CD6:

Performance Incentive

Plan

2 2 17 pages

Attachment CD7:

Government Furnished

Equipment

(GFE)/Government

Furnished Information

(GFI)

Attachment CD8:

Professional Employee

Compensation

2 2 Unlimited

Appendix A: Represen-tations and

Certifications

2 2 Unlimited

Appendix B:

Exceptions to Terms and Conditions

2 2 Unlimited

Appendix C:

Authorized Contractor

Representatives

2 2 Unlimited

Appendix D: Cognizant

Government Offices 2 2 Unlimited

Appendix E:

Administrative

Changes

2 2 Unlimited

3.4 Page Size and Format

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 (for text sections of the proposal) shall be 8.5 x 11 inches, not including foldouts.

Except for the reproduced sections of the solicitation document, the text size shall be no less than

12-point font, Times New Roman. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch

SECTION L: RFP FA8806-14-R-0001 Page-16 margins on the top and bottom and 3/4 inch side margins. The Government will only evaluate information in section that follows the font and margin guidelines. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

These limitations shall apply to both electronic and hard copy proposals.

Legible tables, charts, graphs, and figures shall be used wherever practical to depict organiza-tions, systems and layout, implementation schedules, and plans. These displays shall be clear, legible and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as two pages. Foldouts displaying printed material on both sides of the sheet shall count as four pages. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics, but not for pages of text. All segments of the document that are primarily text shall use single-line spacing and no smaller than 12-point font, Times New

Roman. Matrixes, spreadsheets, focus boxes, and tables shall use single-line spacing and be no smaller than 10-point font, Times New Roman. Text inside graphics shall be no less than 8-point font, Times New Roman. Otherwise, text shall be used sparingly to describe the depicted pictures or graphics and shall use single-line spacing and be no smaller than 10-point font, Times

New Roman. These limitations shall apply to both electronic and hard copy proposals.

3.5 Binding and Labeling

Each hardcopy or paper volume of the proposal should be separately bound in a D-3-ring loose-leaf binder, permitting the volume to lie flat when open. Staples shall not be used. Each binder shall have a cover, spine, and title page each clearly marked with the Offeror’s name, volume number, binder identifier, copy number, and solicitation identification. The volume number, binder identifier, and copy number shall be in no less than 16 point font, Times New Roman.

The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have applicable security designation colors other than red. 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.

Each volume shall include a table of contents and acronym list that will not count against the page count identified in Table 2.

3.6 Cross-referencing

To the greatest extent possible, each volume shall be written on a standalone basis so that its content may be evaluated with a minimum of cross-referencing to other volumes of the proposal.

Information required for proposal evaluation not found in its designated volume will be considered omitted from the proposal.

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

3.7 Indexing

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

SECTION L: RFP FA8806-14-R-0001 Page-17

3.8 Classified Information

Classified information may be provided for the Past Performance volume only. Where classified information (no higher than TS/SI/TK) is required in the Offeror’s response, it shall be provided separately as a classified addendum and bound in a D-3-ring-binder in a classified annex(es) to

Volume IV, Past Performance. If both Collateral Secret and TS/SI/TK information are being provided, separate classified addendums will be submitted for each level of classification. Each entry in the classified addendum(s) shall reference the Past Performance volume, page number, and paragraph number to which it applies. Similarly, a reference shall be placed in the unclassified Past Performance 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 the unclassified portions of the proposal. The classified addendum(s) shall be separately bound with an applicable security designation color cover, conforming to the DD Form 254 provided in this solicitation. Pages in a classified addendum will be included in the page count for the applicable volume.

If any section of the Volume IV Past Performance is classified SECRET or above (up to TS/

SI/TK), it must be provided in paper only format (no electronic media) and hand delivered to the

SMC/RN Program Security Office by noon, Pacific Time, on the day Volume IV is due.

Individuals/companies shall contact, 48 hours prior to delivery, the RN Program Security Office point of contact Mr Bitton, at (310) 653-2765 to coordinate transmission of SCI information.

4 Volume I – Executive Summary

The purpose of the Executive Summary Volume is to provide an overview of the Offeror’s proposal. The Executive Summary Volume is not evaluated, scored or used to clarify other discrepant information in other volumes. Any summary material shall not be considered as meeting the requirements for any portions of other volumes of the proposal. A letter of transmittal or executive cover letter not exceeding two pages in length shall be included in

Volume I. This letter will not be counted against the page limitations associated with the

Volume. The Executive Summary Volume shall include the sections below.

4.1 Offeror’s Proposed Team

The Offeror will briefly identify the Offeror’s team including the prime and teammates. The

Offeror will describe the relationships, roles, and responsibilities of all team members. The

Offeror will identify the parent Cost Center for the project (i.e., the business center where project costs are collected and reported).

4.2 Proposal Approach

The Offeror will describe their overall approach for the contract. The Offeror will provide a concise narrative summary of the entire proposal, including significant risks, highlights of key or unique features, and total proposed price. The Offeror will highlight plans to develop and provide capabilities that meet the tasks defined in the PWS.

4.3 Organization and Management

The Offeror will summarize its organization, management, roles, and responsibilities. The

Offeror will indicate agreements that have been executed (e.g., subcontracts, interdivisional efforts) to allow work to begin at contract award. The Offeror will provide an organization chart

SECTION L: RFP FA8806-14-R-0001 Page-18 that shows prime, subcontractors, and includes key personnel. The Offeror will provide another organization chart that depicts how the Offeror’s program fits within the company, clearly identifies the entire chain of command from the Offeror’s Chief Executive Officer to the

Program Manager, and includes key names, titles, division names and locations. The Offeror will summarize the approach and methodology to be used to manage cost, schedule, risk, and technical compliance.

4.4 Attachment E1 to Volume I: Master Table of Contents and Cross-Reference Matrix

The Offeror will provide a master table of contents for the entire proposal and shall clearly and concisely describe the physical structure of the proposal to include the presentation structure, the interrelationships between volumes and sections or subsections of the overall proposal, and where material may be found for each major element of the evaluation as defined in Section L of this solicitation. In addition, the Offeror may provide a tutorial to explain the process of navigating through the proposal, and any limitations on use of hyperlinks. Offeror format is acceptable. In addition, the Offeror will provide a cross-reference matrix for the entire proposal containing, at a minimum, the items shown in Table 3 Cross-Reference Matrix (sample). The

Offeror will provide Attachment E1 as a separate section within Volume I.

Table 3 Cross-Reference Matrix (sample)

Proposal Section L Section M

Volume/Paragraph Paragraph Paragraph

II/3.2.2 5.2.1.1 2.2.3.1

II/4.3.3 5.2.1.2 2.2.3.2

5 Volume II – Technical

In this volume, the Offeror shall describe its proposed approach for meeting the solicitation requirements addressed by each Technical subfactor, as well as the risks to schedule, cost, or performance associated with this approach. The content of the Offeror's Technical Volume must be consistent with the cost/price proposed in the Offeror’s Cost/Price Volume. The Offeror shall not include cost information in the Technical Volume.

5.1 General Instructions

The Technical Volume shall be specific and complete. Legibility, clarity, and coherence are essential. Your responses will be evaluated against the Technical subfactors defined in Section

M, Evaluation Factors for Award. Using the instructions below, provide the actual methodology you would use for accomplishing/satisfying these subfactors. All 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 neither necessary nor desirable for you to state so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. The Technical Volume shall be organized according to the Technical Volume Table of Contents shown below.

SECTION L: RFP FA8806-14-R-0001 Page-19

Table 4 Technical Volume Table of Contents

Subfactor 1: Integration

Subfactor 2: Systems Engineering

Subfactor 3: Domain Knowledge

Subfactor 4: Program Management

Attachment T1: Program Management Plan

Attachment T2: Resumes of Key Personnel and Statements of Assurance

Attachment T3: Transition Plan

Attachment T4: Efficiencies Table

5.2 Format and Specific Content

The Offeror must address in a comprehensive manner their understanding of, approach to, and ability to accomplish the Integration, Systems Engineering, and Program Management contract requirements. Within each subfactor, the Offeror must address the risks of their approach toward the items addressed in that subfactor.

5.2.1 Subfactor 1: Integration

The intent of this subfactor is to solicit the Offeror’s specific integration capabilities and approaches to be used to ensure that capabilities delivered by various prime contractors are properly integrated into the systems managed by RN programs (AFSCN, LTRS, STAO).

Integration addresses everything from operational need identification and prioritization through acquisition support through operations acceptance and the turnover of project capabilities to sustainment. The nature of RN programs and projects can vary substantially. Specific integration tasks should be considered and addressed which must be tailored for each project.

5.2.1.1 Approach for Performing Integration

a. Provide a summary of your overall integration approach that addresses stakeholder concerns. Describe expected key integration issues and risks which could impact timely operations acceptance for each RN program. Include issues and risks associated with

IA/cybersecurity.

b. For each major integration task area (PWS 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8.1, 4.8.2, 4.8.3, 4.8.4, 4.8.5, 4.8.6, 4.8.7), describe what applicable SE&I processes and tools will be used.

Explain how and why these processes/tools are applicable to these integration tasks.

Additionally, explain what integration risks are addressed by applying these processes/tools to accomplish integration tasks.

5.2.1.2 Specific Integration Support for Three Scenarios

a. Describe specific approach to performing integration, including any systems engineering process support where needed, from project start through the design and development process, system test and operational test, operations acceptance and turnover (PWS 4.4

SECTION L: RFP FA8806-14-R-0001 Page-20 through all of 4.8) to ensure capabilities are delivered in a timely manner for operational use for the following three scenarios. Provide an IMP and IMS for each scenario that identifies the tasks, expertise, and resources for the integration approach.

1. A six-year Telemetry Upgrade program is envisioned for both the Eastern Range (ER) and Western Range (WR). Identify key integration activities that would need to be accomplished over the life of the program per the Draft Integration OI and Integration tasks within the PWS and challenges associated with these activities. Demonstrate how your approach for performing this integration would facilitate obtaining timely operational acceptance of the upgraded capability.

2. As the AFSCN finishes with the Asynchronous Transfer Mode to Internet Protocol network conversion, the network will require a new protocol for the link between the user command and control systems and the tracking stations to replace the existing protocols

(ADCCP and EXU). This new protocol is expected to bring new capabilities to the users with respect to both directives to the tracking station and status of the tracking station.

The new protocol will be developed by separate technical experts, but will require the RN

SE&I contractor to perform all the integration. Demonstrate how your approach for performing this integration would facilitate obtaining timely operational acceptance of the upgraded capability.

3. A space training system is being acquired for a new program/mission supporting Mission

Ready operators. Identify key integration activities that would need to be accomplished.

Define how existing space training architecture and capabilities are leveraged to provide a cost-effective space training system for a new program. Demonstrate how your approach for performing this integration would facilitate obtaining timely operational acceptance of the upgraded capability.

b. Identify key integration risks and issues for each scenario that are likely to arise and how these will be resolved.

5.2.2 Subfactor 2: Systems Engineering

5.2.2.1 Evolution of SE Processes

a. Describe the proposed process changes necessary to evolve Requirements Management process to level 4C (common optimized/efficient) by the end of year two as required by PWS

Table 5-2 Process Maturity Matrix.

b. Explain the risks associated with this Requirements Management process evolution and how these might be mitigated.

c. Describe the proposed process changes necessary to evolve CM process to a level 4C

(common optimized/efficient) by the end of year two as required by PWS Table 5-2 Process

Maturity Matrix.

d. Explain the risks associated with this CM process evolution and how these might be mitigated.

SECTION L: RFP FA8806-14-R-0001 Page-21

Table 5 Process Maturity Matrix

PWS Task Item Baseline

AFSCN

Maturity

Level

Baseline

LTRS

Maturity

Level

Baseline

STAO

Maturity

Level

Maturity (Period 1-2)

/Sustainment (Periods 3-6)

Level Required

5.2.1 Configuration

Management

2 3 2 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

5.2.2 Data Management 3 3 2 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

5.2.3 Requirements

Management

3 3 2 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

5.2.4 Risk and

Opportunities

Management

2 3 1 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

5.2.5 Architecture

Management

3 2 1 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

5.2.6 Test 2 3 2 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

5.2.7 Security

Engineering

2 3 2 Period 1: Evolve to 2C

Period 2: Evolve to 3C

Sustainment Level: 3C

5.2.8 IA/Cybersecurity 2 3 2 Period 1: Evolve to 2C

Period 2: Evolve to 3C

Sustainment Level: 3C

5.2.9 System Safety 3 2 2 Period 1: Evolve to 3C

Sustainment Level: 3C

5.2.10 Reliability, Maintainability, Availability

3 1 2 Period 1: Evolve to 3

Period 2: Evolve to 3C

Sustainment Level: 3C

5.2.11 Total Life Cycle

Analysis

3 3 2 Period 1: Evolve to 3C

Period 2: Evolve to 4C

Sustainment Level: 4C

SECTION L: RFP FA8806-14-R-0001 Page-22

Key:

0 = No process

1 = Ad hoc process

2 = Defined/repeatable process

3 = Mature/effective process

SE process that results in successful accomplishment of particular SE functions for which it is responsible. Process objectives are met or exceeded.

4 = Optimized/efficient process

Resources required to run SE process are minimized or optimized while maintaining acceptable level of effectiveness.

C = Common across RN Programs

Same SE process is used for multiple RN Programs with limited tailoring as needed to address RN Program differences.

Current Government evaluation of the Government process is in the following Table 5

Process Maturity Matrix.

Table 6 PWS Task Status Table provides supplemental qualifying information related to systems engineering tasks by program/functional organization.

Table 6 PWS Task Status Table

PWS Task Status by Program/Functional Organization

5.2.1 Configuration Management (CM)

RN SE&I contractor will migrate to common CM plans, processes, and tools. RN SE&I will manage the execution of the CM process within RN. RN SE&I will process Change

Request Forms that have been validated by the command through the appropriate CCB.

AFSCN: CM process in place along with associated OI. AFSCN SETA manages execution of the process within RN. AFSCN A&AS and the AFSCN supplier processes

CCB packages and bring them to ICWG, ERB, and CCB.

LTRS: CM process in place along with associated OI. LTRS SE&I manages execution of the process within RN. LTRS SE&I processes RFCs and brings them to ERB and CCB.

STAO: CM process and associated OI are in an infant state.

SECTION L: RFP FA8806-14-R-0001 Page-23

PWS Task Status by Program/Functional Organization

5.2.2 Data Management (DM)

RN SE&I contractor will migrate to common RN DM Plans, processes, and tools. The

RN SE&I contractor will manage the RN integrated DM process.

AFSCN: DM process is in place along with associated OI. AFSCN A&AS manages execution of the process within RN.

LTRS: DM process is in place along with associated OI. LTRS SE&I manages execution of the process within RN.

STAO: Uses same DM POCs and processes as AFSCN.

5.2.3 Requirements Management

RN SE&I contractor will migrate requirements baselines to a common requirements management tool.

AFSCN: Requirements baseline including traceability from the System to the Configura-tion Item level is managed by the Satellite Control Network Contract contractor in

Requisite Pro.

LTRS: Requirements baseline including traceability from the System to the Subsystem and in some cases from the Subsystem to the Configuration Item level is managed by

SE&I in DOORS. The sustainment contractor manages traceability from Subsystem requirements to Configuration Item requirements for projects in DOORS as well. RN

SE&I contractor will integrate project requirements baseline information including traceability into the LTRS requirements baseline.

STAO: Uses the development contractor's requirements management processes that was

Capability Maturity Model Integration (CMMI) Level 3 validated. These requirements for the Standard Space Trainer are captured in DOORS, which is maintained by the development contractor. The RN SE&I contractor will work with the development contractor to understand the current requirements and ensure traceability across STAO’s requirement baselines.

SECTION L: RFP FA8806-14-R-0001 Page-24

5.2.4 Risk and Opportunity Management

RN SE&I contractor will evolve AFSCN and LTRS Risk Management into a common

Risk and Opportunity Management process that is applied independently to all three RN programs.

AFSCN: Risk Management Plan and Process exists and AFSCN program risks have been identified and boarded. RN SE&I contractor will execute the plan, track the status of risks, and run the AFSCN Risk and Opportunity Management Board (ROMB).

LTRS: Risk Management Plan and Process exists and LTRS program risks have been identified and boarded. RN SE&I contractor will execute the plan, track the status of risks, and run the LTRS ROMB.

STAO: Currently uses the contractor's risk management processes to manage and track

STAO program risks. RN SE&I contractor will develop a STAO Risk and Opportunity

Management Plan, execute the plan, track the status of risks, and run STAO ROMB.

5.2.5 Architecture Management

RN SE&I contractor will migrate to common architecture tools.

AFSCN: The development contractor has produced as-is and to-be AFSCN architecture products in Architex. The RN SE&I contractor will inherit these architecture baselines and verify accuracy, make necessary updates, and manage/maintain these baselines.

LTRS: LTRS SE&I has produced as-is, to-be, and future LTRS architecture products in

System Architect that are baselined. The LTRS SE&I contractor is migrating these architectures to Enterprise Architect. The RN SE&I contractor will inherit these architecture baselines and verify accuracy, make necessary updates, and manage/ maintain these baselines.

STAO: The development contractor has produced top level as-is (SV-1) diagrams. The

RN SE&I contractor will inherit these diagrams, verify accuracy, make necessary corrections, produce as-is, to-be, and future SST architecture for RN to baseline.

5.2.7

Security Engineering

RN SE&I contractor will provide for physical security of RN personnel at Los Angeles

Air Force Base (LAAFB). This includes facilitating security clearances, travel, operating the Sensitive Compartmented Information Facility (SCIF), and providing necessary information security services.

Security requirements are common to all three programs within RN. RN SE&I contractor only provides these services at LAAFB. Other locations receive these services from host bases.

SECTION L: RFP FA8806-14-R-0001 Page-25

5.2.8 Information Assurance/Cybersecurity

RN SE&I contractor will establish common IA/cybersecurity processes throughout RN programs, provide strategic level implementation of IA/cybersecurity policy, provide tactical level IA/cybersecurity requirements for RN projects and will provide tactical level assessment of IA/cybersecurity posture for RN systems.

AFSCN: DIACAP packages are produced by the prime development contractor.

DIACAP packages are presently managed by the Information Assurance Manager (IAM) and their current SETA/SE&I support. The RN SE&I contractor will manage and build new DIACAP packages and evaluate whether projects are proceeding to meet IA/ cybersecurity requirements. RN SE&I contractor will migrate the packages to the Risk

Management Framework (RMF).

LTRS: DIACAP packages are produced by the prime development contractor. DIACAP packages are presently managed by the IAM and their current SETA/SE&I support. The

RN SE&I contractor will manage and build new DIACAP packages and evaluate whether projects are proceeding to meet IA/cybersecurity requirements. RN SE&I contractor will migrate the packages to the RMF.

STAO: DIACAP packages are produced by the Government with support from the prime development contractor. DIACAP packages are presently managed by the IAM and their current SETA/SE&I support. The RN SE&I contractor will manage and build new

DIACAP/Risk Management Framework packages and evaluate whether projects are proceeding to meet IA/cybersecurity. RN SE&I contractor will migrate the packages to the RMF.

5.2.9 System Safety

RN SE&I contractor will establish common System Safety processes throughout RN programs.

AFSCN: System Safety Management Plan (SSMP) and processes are presently managed by their current SETA/SE&I support. The RN SE&I contractor will execute the plan, track status of risks.

LTRS: SSMP and processes are presently managed by their current SE&I support. The

RN SE&I contractor will execute the plan, track the status of risks.

STAO: SSMP does not currently exist for STAO. RN SE&I contractor will execute the plan, track status of risks.

SECTION L: RFP FA8806-14-R-0001 Page-26

5.2.10 Reliability, Maintainability, Availability

RN SE&I contractor will establish common RMA processes throughout RN programs.

Operators, maintainers, and sustainers collect, process, and report the data required by the RMA guide.

AFSCN: Approved AFSCN RMA Guide exists.

LTRS: Approved LTRS RMA Guide exists.

STAO: RMA metrics are currently tracked by the contractor during installation and by

AFSPC/A3TT during the annual SIMCERT. The SE&I contractor will collect and validate RMA metrics as required.

5.2.11 Total Life Cycle Analysis

RN SE&I contractor will establish common total life cycle process throughout RN programs.

AFSCN: Approved Life Cycle Sustainment Plan (LCSP) exists.

LTRS: Approved LCSP exists.

STAO: Approved LCSP exists.

5.2.3 Subfactor 3: Domain Knowledge

Describe the depth and breadth of relevant technical expertise, along with expertise in the LTRS and AFSCN or equivalent/similar system functional areas.

5.2.4 Subfactor 4: Program Management

The Offeror shall submit a Program Management Plan that describes an overall…