Attachment 18 LISC OMS Section L_ Instructions to Offerors.pdf

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

FA8811-13-R-0001

Launch and Test Range System (LTRS)

Integrated Support Contract (LISC)

SECTION L

Attachment 18: Instructions, Conditions, and Notices to Offerors

20 March 2013

THIS PAGE INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1.0 General Instructions

1.1 Points of Contact

1.2 Discrepancies, Errors, and Omissions

1.3 Considerations of Alternate Proposals

1.4 Offerors’ Library

2.0 Proposal Submission and Electronic Format

2.1 Proposal Delivery

2.2 Submission of Electronic Proposals

2.3 Proposal Content

2.4 Page Size and Format

2.5 Binding, Labeling, Tables of Contents, and Acronym List

2.6 Cross Referencing

2.7 Indexing

2.8 Technical Capability Attachments

2.9 Constraints

3.0 Program Overview

3.1 Ceiling Price Compliance Information

4.0 Volume I - Executive Summary

4.1 Offeror’s Proposed Team

4.2 LISC OM&S Overview

4.3 Organization and Management

4.4 Master Table of Contents and Cross Reference Matrix

5.0 Volume II – Factors 1 & 2 – Technical Capability and Technical Risk

5.1 Technical Capability Master Table of Contents

5.2 General Instructions

5.2.1 Subfactor 1 – Operations

5.2.2 Subfactor 2 – Maintenance and Sustainment

5.2.3 Subfactor 3 – Program Management and Systems Engineering

5.3 Attachment TC1 to Volume II: Basis of Estimate (BOE)

5.3.1 Staffing level and Skill Mix Schedule

5.3.2 Rationale

5.4 Attachment TC2 to Volume II: Contract Work Breakdown Structure

5.5 Attachment TC3 to Volume II: System Engineering Management Plan

5.6 Attachment TC4 to Volume II: Transition Plan

5.7 Attachment TC5 to Volume II: Public-Private Partnering Plan

5.7.1 Public-Private Partnering (PPP)

5.7.2 Partnering Plan Requirements

5.8 Attachment TC6 to Volume II: Small Business Participation Plan

5.9 Attachment TC7 to Volume II: Small Business Subcontracting Plan

6.0 RESERVED

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

7.0 Volume III – Factor 3 – Past Performance

7.1 General

7.2 Relevant Contracts

7.3 Past Performance Volume Organization

7.3.1 Section 1 - Volume Introduction

7.3.2 Section 2 - Past Performance Narratives

7.3.3 Page Limitation

7.3.4 Specific Volume Contents

8.0 Volume IV – Factor 4 – Price

8.1 General Instructions

8.1.1 Reasonableness

8.1.2 CLIN Pricing Summary

8.1.3 Then-Year Funding Requirements

8.1.4 CLIN Pricing Table

8.1.5 Technical Support

8.1.6 Organic Depot Support

8.1.7 Interim Contractor Support

9.0 Volume V – Contract Documentation

9.1 Model Contract / Representations and Certifications

9.1.1 Section A - Solicitation / Contract Form

9.1.2 Section B - Supplies and Services and Prices / Costs

9.1.3 Section H - Special Contract Requirements

9.1.4 Section K - Representations, Certifications, and Other Statements of Offerors

9.1.5 Attachments to the Model Contract

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

1.0 General Instructions

a. The Offeror’s proposal shall include all data and information requested herein and shall be submitted in accordance with these instructions. In developing the proposal, the Offeror shall comply with all the requirements contained in this Request for Proposal (RFP). Non-conformance with the instructions provided in this RFP may result in an unfavorable proposal evaluation. Offerors are expected to submit the highest quality proposals in the initial submittal.

b. The Offeror’s proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not 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 that the Government has no prior knowledge of the Offeror’s facilities and experience, and will make its evaluation based solely on the information presented in the Offeror’s proposal.

c. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

d. The proposal acceptance period of 270 calendar days is specified in Section A of this RFP. By signing block 17 of Standard Form 33 of the model contract, the Offeror represents that its offer is valid for 270 calendar days from the proposal due date.

e. In accordance with Federal Acquisition Regulation (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.

f. Offerors are advised that technical and cost / price data submitted to the Government in response to this solicitation may be released to non-Government advisors for review and analysis. The non-Government support will be provided by The Aerospace Corporation and Quantech Services, Inc.

g. The Government intends to conduct discussions with Offerors after establishing a competitive range based on the ratings of each proposal against all evaluation criteria.

However, the Government reserves the right to award without discussions if it is in the best interest of the Government.

h. The Procuring Contracting Officer (PCO) will promptly notify the Offeror of any decision to exclude it from the competitive range, whereupon the Offeror may request a debriefing in accordance with FAR 15.505. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506.

Upon either 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. In accordance with FAR 15.505(a)(3), Offerors are entitled to no more than one debriefing. If eliminated from

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

competitive range, an Offeror may request a pre-award debriefing or a delayed debriefing to be conducted after award.

1.1 Points of Contact

The PCO, Mr. William Althoff, is the primary point of contact for this acquisition.

Address any questions or concerns to the PCO at (310) 653-1663 (prior to proposal receipt), (310) 653-8509 (after proposal receipt), or William.Althoff@us.af.mil. On all email correspondence, courtesy copy the lead Contract Specialist, Andrew Doud, (310) 653-1517, or Andrew.Doud@us.af.mil.

1.2 Discrepancies, Errors, and Omissions

If an Offeror believes the requirements in these instructions lack clarity or contain an error, omission, discrepancy, ambiguity, or are otherwise unsound, the Offeror shall immediately contact the PCO in writing with supporting rationale. Government responses will be placed in the LISC Offeror’s Library and posted to the Internet for access by all Offerors.

1.3 Consideration of Alternate Proposals

Alternate proposals will not be considered.

1.4 Offerors’ Library

An Offerors’ Library has been established containing documents to assist in preparation of the proposal. Access to the library can be granted after the user registers at the website which is located at https://www.liscbidderslibrary.com. The point of contact for issues with access to the Offerors’ Library is Andrew.Doud@us.af.mil.

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

2.0 Proposal Submission and Electronic Format

2.1 Proposal Delivery

a. The Offeror’s proposal, including both electronic and paper copies (2 soft copies and 1 hard copy each, per Table 1, below), must be received not later than 45 calendar days (1400 hours Pacific Time) after posting of the LISC OM&S RFP to www.fbo.gov. If this date falls on a weekend, proposals will be due the following Monday (1400 hours Pacific Time). Proposals received after cutoff date and time will be handled in accordance with FAR 52.215-1, Instructions to Offerors-Competitive Acquisition. Delivery of proposals shall be coordinated with the PCO. The delivery address for proposals is: SMC/RNK (Attn: Mr. William Althoff), 2400 South Pacific Ave., Building 410, San Pedro, CA 90731.

Personal delivery of proposals shall be coordinated 24 hours in advance of the due date/time with the PCO to ensure timely submission.

2.2 Submission of Electronic Proposals

a. In addition to a hard copy, two soft copies of the proposal shall be delivered on CD- ROMs or DVD-ROMs. The discs shall be labeled with the Offeror’s name, the submission date and the volume number(s) and title(s) contained therein. If more than one disc is required, use the minimum number required. All discs shall be placed in plastic sleeves in one binder separate from the other proposal volumes.

b. The electronic copies of the proposal shall be in a format readable by Adobe Acrobat

9.0 (with “Select” and “Copy” enabled to allow for text and graphics transfer), Microsoft (MS) Word 2007, MS Excel 2007, @Risk 4.1.4, ACEIT 7.1, SEER-SEM 7.3 with PPMC (PPMC is optional), MS-Project 2007 Pro, MS-Power Point 2007, and Internet Explorer

8.0. All Excel spreadsheets and ACEIT models shall be supplied in “active” format with all formulas and data sources included and fully functional so that the Government may use them during the evaluation. Each electronic file shall be clearly marked to show the proposal volume number, solicitation number, and Offeror’s name. Hypertext links shall 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. Each volume shall be in a different CD-ROM or DVD-ROM directory. If files are compressed, the necessary decompression program (e.g., WINZIP) must be included. The proposal shall include the native file (e.g., .DOC) and .PDF versions of all textual material.

c. In the event of a conflict between the hardcopy and softcopy, the hardcopy will take precedence over the softcopy. In the event of a conflict between the native file and .PDF versions, the native file version will take precedence over the .PDF version.

2.3 Proposal Content

a. The Offeror shall prepare the proposal as set forth in Table 1, included below. A complete proposal will consist of five separate volumes, all of which shall be within the required page limits specified in Table 1. 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.

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

* SPA = Strategic Partnering Agreement or equivalent, PA = Partnering Agreement or equivalent, IA = Implementation Agreement or equivalent, ISR = Individual Subcontract Report

Table 1: Proposal Organization

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 (for paper copies) will be returned to the Offeror as soon as practical. 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. When both sides of a sheet display printed material, it shall be counted as two pages. All pages shall be numbered.

c. The Offeror shall use a common paragraph numbering system among the tasking statements in the Work Breakdown Structure (WBS) and Performance Work Statement

(PWS).

d. The PCO, at the request of any Offeror, will allow early “uploading” of sample proposal information on the Air Force servers used for source selection. This information will be checked for compatibility with the source selection facility’s servers, workstations and software. All information in this “test run” will be erased when the test is completed.

Vol. Title Soft

Copies Hard

Copies Page Maximum

I Executive Summary 2 1 10

IA

Master Table of Contents and Cross Reference Matrix

2 1 Unlimited

II Technical Capability

Main Volume

2 1

(excl. Process BOE Staffing Tables &

BOEs for paragraphs 8.1.5 and 8.1.6)

Attachment TC1: Basis of Estimate (BOE) and Labor Hour Baseline

2 1

(excl. BOE tables)

Attachment TC2: Contractor Work Breakdown Structure (CWBS)

2 1 Unlimited

Attachment TC3: Systems Engineering Master Plan 2 1 20 Attachment TC4: Transition Plan 2 1 Unlimited

Attachment TC5: Public-Private Partnering Plan

2 1

(excl. SPA, PA, IA)* Attachment TC6: Small Business Participation Plan 2 1 10 Attachment TC7: Small Business Subcontracting Plan 2 1 Unlimited

III Past Performance 2 1

(Introduction, SF294/295s, ISRs excluded)

IV Price 2 1 Unlimited V Contract Documentation 2 1 Unlimited

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

2.4 Page Size and Format

a. 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 RFP, the text size shall be 12-point Times New Roman font with no font kerning. Use at least 1-inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These limitations shall apply to both electronic and hard copy proposals. For further information on electronic proposals, please see paragraph 2.2 above.

b. Tables, charts, graphs, and figures shall be used wherever practical to depict organizations, 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 for each side used.

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 12-point Times New Roman font. Text inside graphics, matrices, spreadsheets, focus boxes, and tables shall use single-line spacing and shall be 10-point Times New Roman font. Otherwise, text may be used sparingly to describe the depicted pictures or graphics and shall use single-line spacing and be no smaller than 8-point Verdana font or 10-point Times New Roman font.

2.5 Binding, Labeling, Tables of Contents, and Acronym List

a. Each hardcopy of the proposal must be separately bound in a D-3-ring loose-leaf binder, which shall permit the volume to lie flat when open. Do not overload binders and do not use staples. Each binder shall have a cover, spine, and title page clearly marked with the Offeror name, volume number, binder identifier, copy number, and solicitation identification. Binders can be any color other than red. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1, Instructions to Offerors-Competitive Acquisition, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

b. More than one Technical Capability (TC) attachment may be combined in sequential order in a single binder. However, Offerors are encouraged to use separate binders for individual Volume II TC Attachments when such binding will facilitate Government review (e.g., Attachment TC1). Offerors must identify the TC Attachment numbers contained in the binder in addition to the information required in paragraph 2.5a above.

c. Each volume shall include a table of contents and acronym list that will not count against the page count identified in Table 1: Proposal Organization.

2.6 Cross Referencing

To the greatest extent possible, Volume II shall cross reference to applicable TC attachments and Volume V. The electronic copy of Volume II shall contain hyperlinks to all such cross-references. All other information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. The Offeror shall use a common paragraph numbering and outline system for the volumes and attachments of the proposal.

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

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

2.8 Technical Capability Attachments

a. Section L refers to Attachments TC1 through TC7, which will be used as reference material to assist in the evaluation of Technical Capability Subfactors and must support the Offeror’s proposed approach. Throughout the Technical Capability instructions and criteria, TC Attachments are referenced where they are needed to substantiate the Offeror’s proposal. The instructions for several TC Attachments require the Offeror to provide the content of a specific item. Except as otherwise indicated in the RFP, an Offeror’s format is acceptable.

b. Use of second tier references in any TC Attachment is not acceptable. For example, statements such as the following are unacceptable: “Specific processes at our subcontractor will be in accordance with Subcontractor Process Plan XYX” or “This process will be done using our corporate process XYZ”. Instead, the Offeror must extract the applicable process information from those documents and include it in the TC Attachments.

2.9 Constraints

a. The Offeror shall propose the PWS and WBS released with the RFP. No changes to the PWS or WBS are allowed. However, the Offeror may propose a Contractor WBS (CWBS) that provides a lower level breakout of the WBS released with the RFP.

b. All available Government-Furnished Property (GFP) for LISC OM&S is listed in Attachment 12. Offerors are not permitted to propose additional GFP.

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

3.0 Program Overview

The Government has a need for a single Operations, Maintenance, and Sustainment (OM&S) contract that: (1) maintains mission assurance through responsive OM&S and

(2) reduces Range OM&S costs. Today, a substantial amount of resources is expended on the Ranges in order to maintain current levels of operational performance. Resource needs continue to rise in an era of declining military budget, creating the necessity for the Government to seek efficiencies in LTRS OM&S.

In particular, LISC OM&S requirements enable Offerors to streamline Range manpower levels while specifying expected Range performance to maintain the Range and ensure availability of all asset and infrastructure capabilities required for all scheduled operations. Areas expected to produce efficiencies in relation to today’s contract structure include, but are not required or limited to, program management, operations, maintenance, sustainment, scheduling, systems engineering, and logistics. In addition, LISC OM&S requirements are established to correct deficiencies with today’s Reliability, Maintainability, and Availability (RMA) process by ensuring data is consistently collected and reported at both Ranges, enabling better reliability-centered investment decisions across the LTRS enterprise. Ultimately, LISC OM&S will meet the Air Force Space Command (AFSPC) vision of improving LTRS efficiency and effectiveness while continuing ER and WR mission success.

The Government seeks an Offeror that provides the following: (1) Meets PWS requirements at the best value, (2) proposes continuous improvement in Range efficiency while demonstrating cost avoidance and control, and (3) is responsive to Space Wing Commanders during mission execution.

3.1 Ceiling Price Compliance Information

Proposals must not exceed the Total 3400 Ceiling Price for all FPIF CLINs by Government Fiscal Year. Those Ceiling Prices are provided in Table 2 below. Each Fiscal Year aligns to one LISC Period of Performance (PoP). In addition to the overall constraint, additional constraints must be adhered to as follows: (1) “Depot 3400” dollars may be spent only on Sustainment and Depot-Level Maintenance CLINs (1402, 1502, 1602, …, 2302); and (2) “Non-Depot 3400” dollars may be spent on any of the 3400-funded CLINs, including Sustainment and Depot Level Maintenance CLINs.

Table 2: LISC OM&S Offeror FPIF CLIN Ceiling Price Compliance Values by Fiscal

Year (Totals do not include Award Fee)

($ in Millions) FY14 FY15 FY16 FY17 FY18 FY19 FY20 FY21 FY22 FY23 Total

Phase-In 3400 7.48 n/a n/a n/a n/a n/a n/a n/a n/a n/a 7.48 Non-Depot 3400 77.58 78.74 79.92 81.12 82.34 83.57 84.82 86.10 87.39 88.70 830.27 Depot 3400 97.95 99.42 100.91 102.42 103.96 105.52 107.10 108.71 110.34 111.99 1,048.31

TOTAL 3400 183.00 178.16 180.83 183.54 186.29 189.09 191.93 194.80 197.73 200.69 1,886.06

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

4.0 Volume I - Executive Summary

The purpose of the Executive Summary Volume is to provide a complete overview of the Offeror’s proposal. This volume is not evaluated or scored. Any summary material presented in this volume shall not be considered as meeting the requirements for any portions of other volumes of the proposal. Do not include price information in this volume. A letter of transmittal or executive cover letter shall be included in the volume.

This cover letter shall not be counted against the page limitations of the volume and shall not exceed two pages in length. The Executive Summary Volume shall include the following sections.

4.1 Offeror’s Proposed Team

The Offeror shall briefly identify the Offeror’s team including the prime, subcontractors, and interdivisional team locations. The Offeror shall identify the parent Cost Center for the project (i.e., the business center where project costs are collected and reported).

4.2 LISC OM&S Overview

The Offeror shall describe the proposed implementation plan for the LISC OM&S contract. The Offeror shall provide a concise narrative summary of the entire proposal, including highlights of key or unique features. The Offeror shall highlight plans to meet PWS requirements while decreasing price to the Government over the life of the contract.

4.3 Organization and Management

The Offeror shall describe its organization, management, roles, and responsibilities.

The Offeror shall provide an organization chart that shows prime, subcontractors, and includes personnel key to the success of the proposed effort. The Offeror shall provide another organization chart that depicts how the Offeror’s management structure 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 shall discuss the Offeror’s proposed relationship with the Government, including SMC, 30 SW, and 45 SW.

4.4 Volume IA – Master Table of Contents and Cross Reference Matrix

The Offeror shall 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 RFP. The Cross Reference Matrix shall ensure complete traceability throughout the RFP sections and proposal volumes and attachments (e.g. CLINs, Sections L & M, CWBS, PWS, etc.) and contain, at a minimum, the items shown in Table 1: Proposal Organization. Traceability to the CWBS should be provided at level 3 or lower. In addition, the Offeror shall explain any limitations on the use of hyperlinks contained in the proposal. The format of this discussion is at the discretion of the Offeror; however, active links to proposal material

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

from the matrix are encouraged. The Offeror shall provide Volume IA in a separate binder from Volume I.

Proposal CLIN PWS

CWBS

(level 3 or lower)

Section L Section M

Vol /Para. Para. Ref. Para. Para.

II / 3.2.2 3.2.1 2.5.4 4.3.2 4.3.2

III / 4.3.3 3.2.2 3.4.6 4.3.6 4.3.6

Table 3: Cross Reference Matrix (Sample)

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

5.0 Volume II – Factors 1 & 2 – Technical Capability and Technical Risk In this volume, the Offeror shall describe its proposed approach for meeting the RFP requirements addressed by each technical subfactor. The Government will evaluate the Offeror's proposed approach against the Technical evaluation criteria in Section M.

5.1 Technical Capability Master Table of Contents

Technical Capability Volume Outline

Subfactor 1: Operations Subfactor 2: Maintenance and Sustainment Subfactor 3: Program Management and Systems Engineering Attachment TC1: Basis of Estimate (BOE) and Labor Hour Baseline Attachment TC2: Contractor Work Breakdown Structure (CWBS) Attachment TC3: Systems Engineering Master Plan Attachment TC4: Transition Plan Attachment TC5: Public-Private Partnering Plan Attachment TC6: Small Business Participation Plan Attachment TC7: Small Business Subcontracting Plan

5.2 General Instructions

The Technical Capability Volume shall be specific and complete. By submitting a proposal, the Offeror is representing that the proposed approach is sufficient to perform all the requirements specified in this RFP. Do not merely reiterate the objectives or reformulate the requirements specified in this RFP. Using the instructions outlined below, provide the actual methodology that would be used to address the criteria of these subfactors. The indicated information, at a minimum, shall be provided for the following subfactors set forth below. Throughout this volume, provide references to the PWS, CWBS, BOEs, and Contract Data Requirements Lists (CDRLs).

5.2.1 Subfactor 1 – Operations (requirements primarily reference PWS 3.1 and 3.2)

5.2.1.1 Planning Phase. Provide the process for producing Universal Documentation System (UDS) documentation (e.g., Statement of Capability, Program Support Plan, and Operations Directive) and how the associated products are generated, coordinated, distributed, and approved to meet range user requirements. Identify the information required from the Range user and the Government coordination required . Identify the decision points necessary to commit resources to the range user in support of a mission.

a. Provide a Process BOE identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed process. The period for the Process BOE should be the timeline required to complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

provided below; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.1.2 Operations Scenario. Provide a plan to launch both missions according to the Operations Scenario presented in Table 4. The scenario below serves only to illustrate the Offeror’s understanding and approach, and is not to be construed as a definition or limitation of scope for the effort envisioned in the PWS.

Reference Operations Directives for similar missions have been provided in the Offerors’ Library (located in the “Mission Planning Documentation” folder under the “Eastern Range” tab).

Launch Vehicle Range User Launch Date (T-0) Launch Azimuth

Delta IV USAF Day 0 Easterly

Atlas V NRO Day 0 + 48 hrs. Northerly

Table 4: Operations Scenario

a. Include a single schedule that outlines the timeline and sequence of activities across the generation, execution, and recovery phases of both launches. Describe the processes and associated activities across generation, execution, and recovery phases of each operation. Limit Range configuration items to operationally-accepted equipment within the LTRS CI Tree. Identify the limiting factors that must be accounted for to comply with PWS requirements and meet the launch dates in Table 4. Describe the activities that will be used to manage each limiting factor and include them in the schedule.

CWBS

Reference Labor Category Skill Level Labor Hours

CWBS

Reference Labor Category

Offeror defined

Labor Hours Proposed to Execute Process x.x.x Program Manager Level‐2 2 x.x.x Operator Mid‐level 10 x.x.x Engineer Senior‐leve 8 x.x.x Engineer Junior‐level 4 x.x.z Engineer Junior‐level 3

Sect. M Reference: x.x.x.x.x a.

Sect. L Reference: x.x.x.x.x a.

PWS Reference(s): x.x.x

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

b. Provide an Instrumentation Coverage Plan (ICP) for each launch. This ICP is not meant to contain the detail required in CDRL A050. In the ICP, identify the required and mandatory Range instrumentation and communication assets needed to support the launches from the following subsystems:

i. Radar

ii. Telemetry

iii. Command

iv. Optics

v. Communications

c. Identify key activities and describe the process for configuring and checking out Range instrumentation and communication assets in the ICP.

i. Provide a Process BOE identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed process. The period for the Process BOE should be the timeline required to complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1

d. Provide the Day of Launch timeline for the Delta IV mission. Identify constraints and discuss the approach to managing constraints throughout the operation to ensure compliance with the PWS requirements.

e. Describe the approach to conducting operations on Day of Launch for the Delta IV launch. Include the command and control concept for all activities as well as the individual site operations concept. Describe the mission communications strategy. Include the approach for operating all sites and instruments utilized in each operation and how information rolls up from each site to the command center and to the Government Range team.

Describe how the Offeror’s approach, operations concept and organization, and manning strategy enable response to various technical contingencies and anomalies. Describe the proposed skill mix across operations, maintenance, and engineering for the Delta IV launch.

i. Provide a Process BOE identifying the required skill mix (labor hours, skill levels, and labor categories) for conducting day of launch activities.

The period for the Process BOE should be the timeline required to

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1.

In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.1.3 Recovery Phase. Provide a process for assessing range performance after the launch. Include an approach to support Government mishap investigations, should one occur. Describe the measures that will preserve all data, information, and system configuration (i.e. as configured when catastrophic launch event occurs) for analysis in a catastrophic launch event.

5.2.1.4 For any labor hour reductions proposed in the BOEs (in Attachment TC1) between any two Periods of Performance (PoP) that affect the manning for any process proposed in this subfactor, the Offeror must describe and justify how these efficiencies will be achieved. An efficiency is any method by which the Offeror manages resources to meet the PWS requirements and operational baseline in the RFP with fewer labor hours than in the previous PoP. An efficiency may not be based on any planned or presumed changes in the configuration or mission requirements of the LTRS. Address the following areas:

a. Indicate the functional areas impacted by the efficiencies . If an efficiency affects a Process BOE proposed in this subfactor, then include an updated Process BOE.

b. Identify the contribution of each efficiency to the proposed labor hour reductions between any two PoPs. For example, for any labor hour reductions the Offeror proposes between any two PoPs within any CWBS element, the Offeror must account for the full amount with one or more efficiencies.

c. Identify and describe all assumptions that are a basis for proposed efficiencies. Do not assume the Government will approve the assumptions.

d. Identify and describe risks associated with the efficiency and provide mitigation plans.

e. Provide traceability to the BOE(s) that contain the labor hour levels and skill mix of the work force both before and after the efficiency is implemented.

Unless otherwise specified, the Government will assume the manning and labor hour changes contained in the BOEs are completely allocable to the efficiency in question.

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

5.2.2 Subfactor 2 – Maintenance and Sustainment (requirements primarily reference PWS 3.3, 3.4, 3.5, and 3.7)

5.2.2.1 Describe the maintenance and sustainment organizational structure. Describe the roles, responsibilities, decision authorities, and locations of all functions and leadership. Describe the processes and associated activities for maintaining the LTRS at both the organizational and depot levels in accordance with the PWS. Describe how the process transitions through the different levels of maintenance and engineering functions while interfacing with the Government maintenance team. Describe the method for discovering and recording discrepancies, malfunctions, or failures taking into consideration that 1) older Range equipment does not have fault monitoring (Fault Detection and Fault Rectification) and 2) some Range assets sit idle for extended periods of time while other systems are operating 24/7. Describe any differences in performing these processes when maintenance issues occur during a Range operation.

Map the process to the maintenance organizational structure.

5.2.2.2 Describe the maintenance job control concept for Level 1 and Level 2 maintenance activities including a work planning approach to execute maintenance activities within constrained timeframes caused by a dynamic scheduling environment. Describe the approach to re-apply maintenance materiel and re-direct personnel resources on all available and applicable Range assets as a result of changes caused by a dynamic scheduling environment. Provide a Process BOE for this approach identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed approach. The period for the Process BOE should be the timeline required to complete the process. If the approach spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.2.3 Describe the process for responding to Emergency Depot Level Maintenance (EDLM) events and map it to the prescribed response times in the PWS.

Describe the various options available to continue launch operations when the asset cannot be restored.

a. Provide a Process BOE for this strategy identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed strategy. The period for the Process BOE should be the timeline required to complete the process. If the strategy spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.2.4 Provide in Attachment TC 5 as instructed in 5.7 (below), Public-Private Partnering Plan, a description of the strategy for partnering with Ogden Air Logistics Center (OO-ALC) or, if applicable, other organic depot(s) the Offeror intends to utilize.

5.2.2.5 Provide and describe a Reliability, Maintainability, Availability (RMA) data collection, analysis, and trending process and associated activities in accordance with the PWS and LTRS RMA Guide. Describe the process for identifying, prioritizing, tracking, assessing, and recommending mitigations and resolutions for LTRS Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues.

a. Describe how products will be reported, packaged, and delivered to the Government. Indicate how often RMA products will be provided to the Government.

b. Describe a methodology for developing options (e.g. configuration changes, investment decisions) for the Government based on RMA analysis.

Describe the considerations (e.g. complexity, cost, etc.) used to develop the options.

c. Provide traceability from the Offeror’s RMA process to the LTRS RMA Guide

d. Provide a Process BOE identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed RMA process. The period for the Process BOE should be the timeline required to complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.2.6 Provide and describe Logistics/Supply Chain Management processes and associated activities for the LTRS at both the organizational supply and wholesale inventory control levels in accordance with the PWS, including:

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

a. How and to what extent the approach will provide real time total asset visibility, documentation, and reporting through the Standard Base Supply System (SBSS), IMDS, AFEMS, and the Offeror’s inventory data management system (e.g. Gold, Maximo, etc.) that identifies the physical location and ownership of any asset in accordance with the CFO Act or any asset that has been identified by the Government as a critical item or system in accordance with Air Force Manual (AFMAN) 23-110. Identify the limitations that prevent attainment of real time total asset visibility for the whole supply system.

b. Provide a Process BOE identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed process. The period for the Process BOE should be the timeline required to complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.2.7 For any labor hour reductions proposed in the BOEs (in Attachment TC1) between any two Periods of Performance (PoP) that affect the manning for any process proposed in this subfactor, the Offeror must describe and justify how these efficiencies will be achieved. An efficiency is any method by which the Offeror manages resources to meet the PWS requirements and operational baseline in the RFP with fewer labor hours than in previous PoP. An efficiency may not be based on any planned or presumed changes in the configuration or mission requirements of the LTRS. Address the following areas:

a. Indicate the functional areas impacted by the efficiencies . If an efficiency affects a process BOE proposed in this subfactor, then include an updated process BOE.

b. Identify the contribution of each efficiency to the proposed labor hour reductions between any two PoPs. For example, for any labor hour reductions the Offeror proposes between any two PoPs within any CWBS element, the Offeror must account for the full amount with one or more efficiencies.

c. Identify and describe all assumptions that are a basis for proposed efficiencies. Do not assume the Government will approve the assumptions.

d. Identify and describe risks associated with the efficiency and provide mitigation plans.

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

e. Provide traceability to the BOE(s) that contain the labor hour levels and skill mix of the work force both before and after the efficiency is implemented.

Unless otherwise specified, the Government will assume the manning and labor hour changes are completely allocable to the efficiency in question.

5.2.3 Subfactor 3 – Program Management and Systems Engineering (requirements primarily reference PWS 2.1, 2.2, 2.10, 3.7, and 3.10)

5.2.3.1 Provide a LISC OM&S-specific organizational chart that starts at the level of the Offeror’s Chief Executive Officer and clearly identifies the proposed management chain of command, specifying each person’s name, title, division name, and location. In addition, describe the management approach including the authority, accountability and responsibility of the Offeror’s Program Manager to execute the requirements of the PWS. Describe how the Offeror's management approach provides for interface and interaction with the Government. Identify and describe the participating companies proposed to execute LISC OM&S. Include all prime and subcontractors. Describe the relationships, roles and responsibilities of the participating companies.

Describe where all participating companies fit in the organization and identify the interdependencies, communication channels, and any key relationships with subcontractors.

a. Complete Volume V Attachment 13 in accordance with the instructions provided in Section L 9.1.5.4.

5.2.3.2 Describe how the approaches and processes outlined in the proposal ensure compliance with FAR 22.1008-2, union work rules, and Collective Bargaining Agreement (CBA) constraints. Explicitly state whether the Offeror intends to accept existing Collective Bargaining Agreements (CBA), negotiate new CBAs, or not utilize a represented workforce. Describe how union labor, if utilized, will be managed over the life of the contract. Describe the challenges you anticipate with your proposed approach and resolutions.

5.2.3.3 Provide in Attachment TC1: Basis of Estimate manpower levels and skill mixes for LISC OM&S. Provide in Attachment TC2 the Contractor Work Breakdown Structure (CWBS). Provide in the technical volume the BOEs for Technical Support and Organic Depot Support based on the representative descriptions of effort provided in paragraphs 8.1.5 and 8.1.6 (do not include labor rates in the technical volume). The Government is providing a labor hour baseline for a twelve-month period. This baseline is for informational purposes only and does not represent a proposal requirement. It is solely intended to facilitate the Offeror’s understanding of the Government’s estimate of direct labor hours utilized to complete the tasks in PWS sections 3.1, 3.2, 3.3, 3.4, 3.5, 3.7, 3.8, 3.9, 3.10, and 3.12 with the existing contracts. The labor hour baseline (twelve-month length) is as follows:

a. Eastern Range Operations & Level-1 Maintenance (PWS 3.1, 3.2, 3.3):

894,600 hours

b. Western Range Operations & Level-1 Maintenance (PWS 3.1, 3.2, 3.3):

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

921,000 hours

c. Level-2 Maintenance, Sustainment, Supply & Sustainment Modifications (PWS 3.4, 3.5, 3.7-3.10, 3.12): 1,305,000 hours

5.2.3.4 Provide in Attachment TC6: Small Business Participation Plan, a description of the Offeror’s proposed use of small businesses. Provide in Attachment TC7 a Small Business Subcontracting Plan. For each Period of Performance, calculate and provide the percentage of dollars to be subcontracted to first-tier small businesses in accordance with the following formula: X/Y * 100, where:

X equals total dollars proposed to be subcontracted to first-tier small businesses; and Y equals the sum of proposed target prices for CLINs xx01-xx08 and the pre-determined values for CLINs xx09-xx10 (as provided in Table 7).

5.2.3.5 Provide and describe in Attachment TC3, Systems Engineering Management Plan, the processes for the Range System Engineering disciplines and associated activities for the LTRS in accordance with the PWS.

a. Describe the Offeror’s Range engineering interface to the Government and associated contractors that is consistent with the LTRS SEP

b. Provide a Process BOE for Range Systems Engineering processes identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed process. The period for the Process BOE should be the timeline required to complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph

5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning.

The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1. In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

c. Provide a configuration control process for operational configuration baseline changes that is consistent with the LTRS Configuration Management Plan.

i. Provide a Process BOE identifying the required skill mix (labor hours, skill levels, and labor categories) to execute the proposed process.

The period for the Process BOE should be the timeline required to complete the process. If the process spans multiple years, provide labor hours for each year. Describe how the skill mix proposed in the Process BOE will be utilized to execute the process. A template for the Process BOE has been provided in paragraph 5.2.1.1 a.; Offeror format is acceptable, but must include all information in the template. No

SECTION L, ATTACHMENT 18: INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

additional information shall be included in the Process BOE table such as descriptions of the Offeror’s proposed use of manning. The Process BOE shall draw upon the relevant BOE(s) proposed in Attachment TC1.

In other words, the skill mix proposed in the Process BOE can be a subset of a single BOE or a combination of multiple subsets of the BOEs proposed in Attachment TC1.

5.2.3.6 Configuration Scenario. Provide the approach to ensure the Operational Baseline is maintained with positive configuration control given the following scenario. The Air Force Network Operations Center (AFNOC) issues a C4- NOTAM that impacts the software for the routers in the communications subsystem. The C4-NOTAM mandates an update of the vendor-provided configuration software.