CAMMO_Notional_Section_L_ver_2_0a.pdf

SECTION L for

FA8823-13-R-0009

CONSOLIDATED AIR FORCE SATELLITE CONTROL

NETWORK (AFSCN) MODIFICATIONS,

MAINTENANCE, & OPERATIONS (CAMMO)

SUSTAINMENT CONTRACT

Instructions to Offerors

XX May 2014

Contents

1.0 INSTRUCTIONS TO OFFERORS (ITO) AND INFORMATION FOR PROPOSAL

PREPARATION

1.1 Program Structure and Objectives

1.1.1 Description of Major CLINs and CLIN Structure

1.1.2 System Baseline for Proposal Preparation Purposes

1.2 General Information

1.2.1 Communications

1.2.2 Debriefings

1.2.3 Discrepancies, Errors, and Omissions

1.2.4 Consideration of Alternate Proposals

1.2.5 Electronic Reference Documents

1.3 General Instructions

1.3.1 Description of Section L

1.3.2 Compliance with Instructions

1.3.3 Non-conformance

1.3.4 Proposal Clarity

1.3.5 Embellishments and Elaborate Presentations

1.3.6 Acceptance Period

1.3.7 Records Retainment

1.3.8 Acronyms

1.3.9 Task References

1.4 Organization and Format of Proposals

1.4.1 Page Limitations

1.4.2 Pricing Related Data

1.4.3 Classified Documents

1.4.4 Cross Referencing

1.4.5 Indexing

1.4.6 Glossary of Abbreviations and Acronyms

1.4.7 Binding and Labeling

1.5 Electronic Submittals

1.5.1 Electronic Format

1.5.2 Handling of Version Conflicts

1.6 Use of Non-Government Advisors

1.7 Distribution

2.0 VOLUME I – EXECUTIVE SUMMARY

2.1 Offeror’s Proposed Team

2.2 CAMMO Proposal Approach

2.3 Organization and Management

2.4 Volume Organization

3.0 VOLUME II – TECHNICAL VOLUME

3.1 General

3.1.1 Technical Factor

3.1.2 Technical Risk Factor

3.1.3 Format and Specific Content

3.1.4 Volume Organization

3.2 Technical and Technical Risk Subfactor Sections

3.2.1 Subfactor 1 – Operations

3.2.2 Subfactor 2 – Maintenance

3.2.3 Subfactor 3 – Sustainment

3.2.4 Subfactor 4 – Program Management

3.2.5 Subfactor 5 –Scenario

4.0 VOLUME III – PAST PERFORMANCE

4.1 Organizational Structure Change History

4.2 Teaming Arrangements

4.3 Subcontractor Consent

4.4 Relevant Contracts

4.4.1 Specific Content

4.5 Past Performance Information Forms

4.5.1 Past Performance Questionnaires (PPQs)

4.5.2 PPIF Submission Deadline

5.0 VOLUME IV – PRICE

5.1 General Information

5.1.1 Price Reasonableness

5.1.2 Unbalanced Price

5.1.3 Conformance to Budget Limitation

5.1.4 Total Evaluated Price (TEP)

5.2 Instructions

5.2.1 CLIN Pricing Summary

5.2.2 Special Studies CLIN

5.2.3 Factory Compatibility Testing (FCT) CLIN

6.0 VOLUME V – CONTRACT DOCUMENTATION

6.1 Model Contract/Representations and Certifications

6.1.1 Section A - Solicitation/Contract Form

6.1.2 Section B - Supplies or Services and Costs/Price

6.1.3 Section E - Inspection and Acceptance

6.1.4 Section F - Deliveries or Performance

6.1.5 Section G - Contract Administrative Data

6.1.6 Section H - Special Contract Requirements

6.1.7 Section I - Contract Clauses

6.1.8 Section J - List of Documents, Exhibits & Attachments

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

6.1.10 Section L Clauses - Instructions to Offerors

6.2 Other Information Required

6.2.1 Authorized Offeror Personnel

6.2.2 Government Offices

6.2.3 Company/Division Address, Identifying Codes, and Applicable Designations

ANNEX A: Cross Reference Matrix

ANNEX B: Estimated Man-Hours Gwbs Format

ANNEX C: Past Performance Questionnaire

ANNEX D: Subcontractor/Teaming Partner Consent Letter

ANNEX E: Client Authorization Letter

ANNEX F: Acronym List

Table 1-1 CLIN Structure Table 1-2 Proposal Organization (Table being finalized) Table 1-3 Non-Government Advisors

Table 4-1 Contract Relevancy Matrix Table 5-1 Ceiling Price Compliance Values by Fiscal Year Table 5-2 Government Provided Values (Govt Values to be determined) Table 5-3 TEP Calculation (Placeholder – Table to be Created)

Table 5-4 CLIN Pricing (Table to be finalized) Table 5-5 Special Studies Price Template

Table 5-6 FCT Pricing Menu

1.0 Instructions to Offerors (ITO) and Information for Proposal Preparation

1.1 Program Structure and Objectives

The Consolidated Air Force Satellite Control Network (AFSCN) Modifications, Maintenance, and Operations (CAMMO) acquisition will combine operations, maintenance, and sustainment

(OM&S) requirements from three contracts to consolidate AFSCN services onto a single contract vehicle. This integration of related AFSCN weapon systems services work will enable the prime

CAMMO contractor to optimize resources in order to provide the AFSCN services needed to keep over 170 national security and civil satellites operating to support world-wide operations.

By vertically integrating AFSCN contracted work, the government expects economies of scale, economies of scope, and productivity gains; as well as efficiencies compelled by competition resulting in significant projected savings.

The CAMMO OM&S services will be primarily Fixed-Price Incentive (Firm Target) (FPIF) with an appropriate cost ceiling, target fee and share ratio arrangement between the government and contractor. This approach will require the CAMMO contractor to provide a defined level of service across the network based on system performance measures (e.g., operations performance score and operational availability). This approach will encourage the contractor to implement efficient processes across OM&S and have the opportunity to optimize their workforce, subject to mandatory requirements of the CAMMO Performance Work Statement (PWS) and compliance documents. This approach will reduce the CAMMO contractor’s total profit if mandatory requirements and minimum performance parameters are not met ensuring contract requirements and performance are not sacrificed for cost savings.

This acquisition strategy will provide Offerors the AFSCN’s current design and maintenance data to develop competitive bids that will be awarded based on a technical risk and price tradeoff. The period of performance is set at seven years with an optional six month extension of services to encourage the CAMMO contractor to invest to support increased efficiencies and earn profit share while providing government savings.

Several other CLIN types will be used on CAMMO for task areas that are not as well suited for an FPIF contract. These areas include: Factory Compatibility Testing (FCT); Transition, Travel, Material and Licenses; Remote Site Support; Spares; Repairs; Special Studies; and Sustainment

Modifications. The tables in the next section provide a summary of CLIN types and the CLIN structure.

The objective of CAMMO is to maintain performance with no additional risk at reduced OM&S cost for the AFSCN. This acquisition strategy enables Air Force Space Command (AFSPC) to streamline critical space operations, save scarce funding, and usher in a new era of vertically integrated service-based contracting for the AFSCN.

1.1.1 Description of Major CLINs and CLIN Structure

Table 1-1 shows the different CLINs to be used on CAMMO and provides a brief description. In effort areas where there are multiple CLINs listed, the CLIN number is intended to align with the

Fiscal Year (FY) of the contract option projected award date. For example, CLIN 1600 corresponds to FY 2016, 1700 to FY 2017 and so on.

FA8823-13-R-0009 CLIN Structure

CLIN Description Type Task Title

1400 Transition - Phase-In CPFF Transition – Phase-In

1401 Travel for Transition - Phase-In CR Travel for Transition - Phase-In

1500, 1600, 1700, 1800, 1900, 2000, 2100

Operations, Maintenance, and

Sustainment (OM&S)

FPIF a) General Requirements

b) AFSCN Operational Performance

c) Org Level Mx and Support

d) Depot Level Mx

e) Sustainment Logistics Support

f) Sustaining Support

g) Software Sustainment and Mx

1501, 1601, 1701, 1801, 1901, 2001, 2101

Government-directed Travel and

Other Direct Costs (ODCs)

CR a) Reimbursable Travel

b) Local Purchase

c) Licenses, Service Contracts, Warranties, and Subscriptions

1502, 1602, 1702, 1802, 1902, 2002, 2102

Operating Location Support

Services

FFP Operating Location Support

Services

2400 Transition - Phase-out CPFF Transition – Phase-Out

2401 Travel for Transition - Phase-Out CR Travel for Transition - Phase-Out

3000-3499* Factory Compatibility Testing

(FCT)

FFP Factory Compatibility Testing

(FCT)

3500-3999 Travel and Transportation for FCT CR Travel and Transportation for FCT

4000-4999* Replenishment Spares CR Replenishment Spares

5000-5999 Offsite Stocklisted Item Repairs -

Material Support Division (MSD)

CR Offsite Stocklisted Item Repairs -

Material Support Division (MSD)

6000-6999* Special Studies CPFF Special Studies

7000-7999* Modifications Projects TBD** Modification Projects

9999 Data and Reports NSP Data and Reports

Table 1-1 CLIN Structure

*CLINS to be added as they are needed. Range is listed as a placeholder.

**CLIN type to be determined when modification project is issued.

1.1.2 System Baseline for Proposal Preparation Purposes

The AFSCN baseline is established through a series of documents contained in the Bidders’

Library. The guiding reference document for the AFSCN baseline is the AFSCN Specification

Tree v3.12 which provides the main body of documentation.

Non-AFSCN mission systems are identified in the PWS and any available documentation can be found in the Bidders’ Library.

The Offeror’s proposal for services outlined in the PWS should be developed based upon the above references.

1.2 General Information

To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Failure to meet a requirement may result in an offer being ineligible for award. The response shall consist of the following volumes: Volume I - Executive Summary; Volume II - Technical Volume; Volume III

- Past Performance Volume; Volume IV - Price Volume; and Volume V – Contract Volume.

Proposals shall be delivered in hard copy and electronic form. The electronic version shall be

2010 Microsoft Office Suite compatible and delivered on a PC-compatible compact disk (CD) or digital video disk (DVD).

All volumes of the Proposal shall be submitted to the Government no later than 12:00 pm MST on DD MMMM 2014.

1.2.1 Communications

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

Selection Information – See Federal Acquisition Regulation (FAR) 2.101 & 3.104” in the

Subject line. If email cannot be sent and received encrypted, then an alternative approach should be discussed with the PCO. The Offeror is responsible for ensuring the information is appropriately protected regardless of the transmission method.

The PCO, Ms. Christina Ming, is the primary point of contact for this acquisition. Address any questions or concerns you may have to the PCO at (719) 556-2856 or via email at christina.ming.2@us.af.mil. On all email correspondence, courtesy copy the Contract Specialist, Ms. Sarah Vollbracht (sarah.vollbracht@us.af.mil). Ms. Vollbracht can be reached via phone at

(719) 556-2218.

1.2.2 Debriefings

The PCO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The 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. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

1.2.3 Discrepancies, Errors, and Omissions

If an Offeror believes that the requirements in these instructions lack clarity or contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error. Notifications and content of any Request for Proposal (RFP) amendments will be posted to the Federal Business Opportunities (FBO) website, www.fbo.gov .

The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

http://www.fbo.gov/

1.2.4 Consideration of Alternate Proposals

Proposals that do not address requirements within the PWS will be considered alternate proposals. Alternate proposals will not be considered.

1.2.5 Electronic Reference Documents

All reference and technical documents for this solicitation are available in the CAMMO Bidder’s

Library to assist in preparation of the proposal. Instructions on how to gain access to the

Bidders’ Library are posted in the general information area of the CAMMO posting on FBO.

1.3 General Instructions

1.3.1 Description of Section L

Section L of this Request for Proposal (RFP) is the instructions, conditions, and notices to

Offerors for the source selection. This section is written in accordance with FAR 15 and

AFFARS Mandatory Procedures 5315.3.

1.3.2 Compliance with Instructions

The Offeror’s proposal must include all data and information requested by this Instruction to

Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the PWS, Compliance and Reference Documents

List, Contract Data Requirements List (CDRL), and with all the requirements contained in the

RFP.

1.3.3 Non-conformance

Non-conformance with the instructions provided in the RFP may result in determination of non-responsiveness of the proposal, exclusion from the competitive range or an otherwise unfavorable proposal evaluation. The Government will evaluate proposals and reserves the right to award a contract without conducting discussions with the Offerors except clarifications as described in FAR 15.306 (d) (3). Therefore, each Offeror’s initial proposal should contain the

Offeror’s best terms from price and technical standpoints. The Government reserves the right to conduct discussions if the Source Selection Authority (SSA) determines them to be necessary.

1.3.4 Proposal Clarity

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

1.3.5 Embellishments and Elaborate Presentations

Do not submit elaborate brochures or documentation, binding, detailed art work, or other embellishments.

1.3.6 Acceptance Period

The proposal acceptance period is specified in Section A of the model contract/solicitation. 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.

1.3.7 Records Retainment

In accordance with FAR Subpart 4.8, “Government Contract Files,” the Government will retain one copy of all unsuccessful proposals. The Government will destroy extra copies of unsuccessful proposals.

1.3.8 Acronyms

Acronyms used in Sections L and M of this RFP are defined in Annex F to Section L, Acronym

List.

1.3.9 Task References

When specific tasks are referenced, the Offeror shall provide the paragraph number(s) as found within the Government PWS (GPWS) and Government Work Breakdown Structure (GWBS).

Throughout this document these will be referred to as the PWS and WBS respectively.

1.4 Organization and Format of Proposals

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1-2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1-2. The format of the proposed volumes shall correlate directly with the instructions in Section L. The proposal shall provide a direct correlation to the specific questions and requirements given in each instruction. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Volume

ITO

Paragraph

Number

Title Electronic

Copies

Hard

Copies

Page

Limit

I 2.0 Executive Summary 2 2 10

2.4 Attachment E1: Cross Reference Matrix 2 2 Unlimited

II 3.0 Technical 2 2 80*

Attachment T1: Configuration Management Plan 2 2 TBD

Attachment T2: Modification Management Plan 2 2 TBD

Attachment T3: Software Development Plan 2 2 TBD

Attachment T4: Staffing Plan 2 2 TBD

Attachment T5: WBS Man-hour Estimate 2 2 TBD

Attachment T6: BOE’s for WBS Man-hour

Estimate

2 2 TBD

Attachment T7: Small Business Subcontracting

Participation Plan

2 2 TBD

Attachment T8: Public Private Partnership Plan 2 2 TBD

Attachment T9: Transition Plan 2 2 TBD

III 4.0 Past Performance 2 2 40**

Attachment PP1: Subcontractor Consent Letters 2 2 TBD

Attachment PP2: Client Authorization Letters 2 2 TBD

Attachment PP3: Contract Relevancy Rationale

Matrix

2 2 TBD

Attachment PP4: Past Performance Information

Forms

2 2 TBD

IV 5.0 Price 2 2 Unlimited

Attachment PC1: TEP Calculation Table 2 2 TBD

Attachment PC2: CLIN Pricing Summary Table 2 2 TBD

Attachment PC3: 2 2 TBD

Attachment PC4: 2 2 TBD

V 6.0 Contract Documentation N/A

Table 1-2 Proposal Organization (Table being finalized)

* The page limits of the Technical Volume attachments (Attachments T1-T9) are not counted against the 80 page limit for the rest of the Technical Volume.

** Offeror provided narratives should not exceed 2 pages per submitted contract and should not exceed 40 pages total for all prime and teaming partner/significant subcontractor contracts. The relevancy matrix for both prime and subcontractors should not exceed 10 pages. There is a limit on the number of Past Performance Questionnaires that can be submitted. Follow the guidelines in Section 4.0, "Volume II - Past Performance.”

1.4.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the

Offeror as soon as practicable. When both sides of a sheet display printed material, it shall be counted as two pages. Page limitations may be placed on responses to Evaluation Notices (ENs).

The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Page limits do not apply to indexes, tables of contents, tabs, cover pages, glossaries or requested information identified with an “Unlimited” in Table 1-2.

1.4.1.1 Page Size and Format

A page is defined as each face of a sheet of paper containing information. Page size shall be

8.5 x 11 inches, not including foldouts. Pages shall be typed with single line spacing. Except for the reproduced sections of the solicitation document and Volume III, the text size shall be no less than 12-point 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 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format limitations shall apply to both electronic and hard copy proposals and shall also apply to responses to ENs.

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be clear, legible, and shall not exceed 11 by 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. Text inside graphics, matrices, spreadsheets, focus boxes, and tables shall use single-line spacing and shall be no smaller than 8-point Times New Roman font. Otherwise, text may be used sparingly to describe the depicted pictures or graphics. These limitations shall apply to both electronic and hard copy proposals.

1.4.2 Pricing Related Data

All pricing data shall be addressed ONLY in the Price and Contract Documentation Volumes.

Price trade off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade off decisions.

1.4.3 Classified Documents

The Offeror’s proposal shall be unclassified.

1.4.4 Cross Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. The Offeror shall use a common paragraph numbering and outline system for the volumes and attachments of the proposal.

1.4.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Table of Contents and tab indexing do not count against page limitations for their respective volumes.

1.4.6 Glossary of Abbreviations and Acronyms

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

1.4.7 Binding and Labeling

Each 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. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror’s name. The same identifying data should be placed on the spine of each binder. The “original” proposal shall be clearly differentiated from copies. All document binders shall have a color other than red or other applicable security designation colors. 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.

1.5 Electronic Submittals

1.5.1 Electronic Format

The Offeror shall submit Volumes I, II, III, IV and V in electronic format, using recordable CDs or DVDs. The content and page size of electronic copies must be identical to the hard copies.

The CDs or DVDs shall be labeled with the Offeror’s name, submission date and the volume number(s) and title(s) contained therein. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. Each volume shall be in a different directory on the CD or DVD. If files are compressed, they shall be saved as .zip files. The electronic copies of the proposal shall be submitted in a format readable by Microsoft

(MS) Office 2010, Adobe Acrobat 10.0 (with “Select” and “Copy” enabled to allow for text and graphics transfer), as applicable. The proposal shall include the native file (e.g., .DOC(x)) and

.PDF versions of all textual material. All CDs or DVDs shall be placed in plastic sleeves in the binder containing Volume I. 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.

1.5.2 Handling of Version Conflicts

In the event of a conflict between the hard copy and soft copy, the hard copy will take precedence over the soft copy. In the event of a conflict between the native file and .PDF versions, the native file version will take precedence over the .PDF version.

1.6 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 work for the following companies as non-government advisors for review and analysis:

Company Name

The Aerospace Corporation (FFRDC)

Quantech Services, Inc.

Table 1-3 Non-Government Advisors

Per DoD Source Selection Procedures paragraph 1.4.5.2.1, the Offeror may object to the 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.

1.7 Distribution

The “original” proposal shall be identified. The Offeror’s proposal, including both electronic and paper copies, must be received no later than 1630 hours Mountain Time, 45 calendar days after release of the official RFP. If this date falls on a weekend, proposals will be due the following business day no later than 1400 hours Mountain Time. Proposals received after the cutoff date and time shall be handled in accordance with FAR 52.215-1, “Instructions to Offerors-

Competitive.” Delivery of proposals shall be coordinated with the PCO. Proposals shall be addressed to the PCO and either personally hand carried or delivered by certified carrier to the address below on the proposal due date.

SMC/PKL, Attn: Christina Ming

RE: Solicitation No. FA8823-13-R-0009

1050 E. Stewart Ave

Peterson AFB, Colorado 80914

2.0 Volume I – Executive Summary

The purpose of the Executive Summary Volume is to provide a complete overview of the material that constitutes the Offeror’s proposal. Volume I is provided for informational purposes only and is not evaluated or scored. Any summary material presented in Volume I shall not be considered as meeting the requirements for any portions of other volumes of the proposal. Do not include cost information in this volume other than the total proposed price. A letter of transmittal or executive cover letter shall be included in this volume. This cover letter shall not be counted against the page limitations of the volume. The letter shall not exceed two pages in length. The Executive Summary Volume shall include the following sections:

2.1 Offeror’s Proposed Team

The Offeror shall concisely identify the Offeror’s team including the prime and subcontractors and their locations. Small businesses shall be identified as part of the Offeror’s proposed team structure. The Offeror shall describe the relationships, roles, and responsibilities of the participants. The Offeror shall identify the parent Cost Center for the project (i.e., the business center where project costs are collected and reported).

2.2 CAMMO Proposal Approach

The Offeror shall describe the proposed implementation plan for CAMMO. The Offeror shall provide a concise narrative summary of the entire proposal, including significant risks, highlights of key or unique features, areas of expected efficiencies/potential cost reductions over the Period of Performance, the Total Evaluated Price (TEP), and the total proposed price. The Offeror shall highlight plans to establish capabilities that satisfy the tasks in the CAMMO PWS.

2.3 Organization and Management

The Offeror shall describe its organization, management, roles, and responsibilities. The Offeror shall indicate agreements that have been executed (e.g., subcontracts, interdivisional effort, partnering agreements) to allow work to begin at contract award. The Offeror shall provide an organizational chart that shows prime, subcontractors, and interdivisional transfers. The Offeror shall provide another organizational chart that depicts how the Offeror’s program fits within the company, and includes key names, titles, division names and locations. The Offeror shall summarize the controls and processes to be used to manage cost, schedule, risk, and technical compliance. The Offeror shall summarize the tools and processes proposed to manage performance, cost, and schedule.

2.4 Volume Organization

The Offeror shall provide a master table of contents of 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.

The Offeror shall provide a cross reference matrix for the entire proposal containing, at a minimum, the items shown in Annex A to Section L: “Cross Reference Matrix.” The cross-reference matrix shall be Attachment E1 to Volume I.

3.0 Volume II – Technical Volume

3.1 General

In this volume, the Offeror shall describe their proposed technical approach for meeting the RFP requirements specified by the each of the five subfactors. The Government will evaluate the

Offeror's proposed approach against the associated evaluation criteria in Section M.

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Responses will be evaluated against the Technical and Technical Risk

Subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology for accomplishing/satisfying the subfactor requirements. All the requirements specified in the solicitation are mandatory.

The Offeror’s Technical Volume must be consistent with its Price Volume.

3.1.1 Technical Factor

The purpose is to assess whether the Offeror’s proposal will satisfy the Government’s requirements related to the evaluation criteria. Each Technical Subfactor will receive an

“acceptable” or “unacceptable” rating. Any proposal with one or more “unacceptable” technical ratings for any Technical Subfactor will be unawardable. In accordance with Department of

Defense Source Selection Procedures, the determination of this rating is based on a government assessment of whether the proposed approach meets the minimum requirements of the solicitation. Subfactor ratings will not be rolled into an overall rating for the Technical factor.

3.1.2 Technical Risk Factor

The purpose is to assess the risk of the proposed technical approach. Technical risk, which is manifested by the identification of weaknesses, considers potential for disruption of schedule, increased costs, degradation of performance, the need for increased government oversight, or the likelihood of unsuccessful contract performance. For each criterion within the Technical

Subfactors, the Government may assign weaknesses or significant weaknesses. The evaluation will consider the Offeror’s proposal for mitigating the risk, if and when identified, and why that approach is or is not manageable and appropriate. Subfactor ratings will not be rolled into an overall rating for the Technical Risk factor.

3.1.3 Format and Specific Content

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 Government will evaluate the Offeror’s proposed approach against the Technical and Technical Risk criteria in Section M. The

Offeror’s Technical Volume must be consistent with its Price Volume.

In the Technical Volume, address your technical approach for meeting the Government’s minimum performance or capability requirements of each Technical Subfactor. The volume shall be specific and complete. By submitting a proposal, the Offeror is representing that it will perform all the requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. Using the instructions outlined below, provide the actual methodology that would be used for satisfying the subfactor requirements.

The Offeror proposed solution shall reflect the proposed work with cross references to the WBS, PWS and/or CDRLs as applicable. Careful consideration should be made to thoroughly address all the information requested in each of the subfactors listed.

3.1.4 Volume Organization

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

Table of Contents

List of Tables and Drawings

Glossary

Subfactor 1: Operations

Subfactor 2: Maintenance

Subfactor 3: Sustainment

Subfactor 4: Program Management

Subfactor 5: Scenario

Attachments to Technical Volume

3.2 Technical and Technical Risk Subfactor Sections

The Technical and Technical Risk Factors are each divided into five subfactors. Each subfactor will be evaluated under both the Technical and Technical Risk Factors based on the information requested in this section. Each subfactor will be evaluated and assigned a rating in accordance with Section M. Subfactor 5 (Section 3.2.5) requires that Offerors propose to a hypothetical scenario that will be subject to technical and technical risk evaluation, but will not be subject to a price evaluation.

3.2.1 Subfactor 1 – Operations

In addressing this subfactor, the Offeror is to provide detailed information in their technical approach to performing AFSCN operations. The Government will evaluate the extent to which the proposal meets the requirements for AFSCN operations of key PWS paragraphs. Specifically the Offeror shall provide detailed information which addresses the following areas:

3.2.1.1 Attain and Maintain Certified Operators. The Offeror shall:

3.2.1.1.1 Provide a comprehensive training approach to attain and maintain AFSCN operator certification in order to execute operations. The approach shall include the Offeror’s proposed coursework (classes and class synopsis), description of the

On the Job Training (OJT) component, to include timelines. Describe the approach for maintaining operator certification. (PWS 3.2.1.1)

3.2.1.1.2 Provide information that shows how the contractor’s training program will provide for the integration and implementation of certified operators to assure continued operations.

3.2.1.2 Execution and Support of Operations. The Offeror shall:

3.2.1.2.1 Provide a detailed description of their approach to AFSCN operations in the following areas, and provide information that demonstrates their capability to execute the following elements of AFSCN operations. Identify areas of potential risk and suggested mitigation strategies. (PWS 3.2.1.1, 3.2.1.5, 3.6.3.9, 3.6.4.19)

a) Remote Tracking Station (RTS) operations, RTS mission communications, and satellite operations support to include Automated Remote Tracking Station

(ARTS) and RTS Block Change (RBC) Operations.

b) Operational Control Node (OCN) Operations at Schriever AFB and

Vandenberg AFB.

Management of operations at RTSs and Operational Control Nodes Provide a matrix or process map that shows how operational processes map to both the Offeror’s organizational structure and to the Offeror’s external interfaces (e.g., SMC, 50SW, other contractors).

3.2.2 Subfactor 2 – Maintenance

In addressing this subfactor, the Offeror is to provide detailed information in their technical approach to performing AFSCN maintenance. The Government will evaluate the extent to which the proposal meets the requirements for AFSCN maintenance of key PWS paragraphs.

Specifically the Offeror shall provide detailed information which addresses the following areas:

3.2.2.1 Organizational Structure, Processes, and External Interfaces. The Offeror shall:

3.2.2.1.1 Describe the maintenance organizational structure and the roles, responsibilities, decision authorities, external interfaces, and locations of all contractor functions and leadership to meet the requirements in the PWS. The external interfaces include but are not limited to: SMC, 50SW, other contractors. (PWS 3.3.1, 3.4.2, 3.4.3, 3.4.4, 3.4.6)

3.2.2.1.2 Describe the method for discovering, reporting, and recording discrepancies, malfunctions, or failures; and how the process includes planning, executing, and reporting as activities transition through the different levels of maintenance and engineering functions while interfacing with the government maintenance team to meet the requirements in the PWS. (PWS 3.3.1, 3.4.2, 3.4.3, 3.4.4, 3.4.6)

3.2.2.2 Organizational Level and Depot Level Maintenance. The Offeror shall:

3.2.2.2.1 Provide a detailed approach and methodology for the response to an Emergency

Depot Level Maintenance (EDLM), Urgent Depot Level Maintenance (UDLM), and Maintenance Assistance (MA) request in the timeframe required as described. If the Offeror has unique approaches for specific sites, the response should provide those details. (PWS 3.4.3.1, 3.4.4.1, 3.4.6.1)

3.2.2.2.2 Provide a detailed approach to how the Offeror will implement Level 1

(Organizational) and Level 2 (Depot) maintenance activities and identify any efficiencies and/or operational benefits that can be realized from the proposed approach to fulfill the requirements in the PWS. (PWS 3.3, 3.4)

3.2.3 Subfactor 3 – Sustainment

In addressing this subfactor, the Offeror is to provide detailed information in their technical approach to performing AFSCN sustainment. The Government will evaluate the extent to which the proposal meets the requirements for AFSCN sustainment of key PWS paragraphs.

Specifically the Offeror shall provide detailed information which addresses the following areas:

3.2.3.1 Off Site Repair. The Offeror shall:

3.2.3.1.1 Describe the technical approach and process for establishing an off-site depot level maintenance capability for repairable assets IAW the PWS. The response will clearly show an understanding of the scope of the repair tasking, skills and knowledge required, ability to meet performance standards, facility planning, use of Government Furnished Equipment (GFE) workstations, supplementation of

GFE workstations, and the challenges associated with maintaining a repair capability for legacy equipment. (PWS 3.4.5.2, 3.4.5.3, 3.4.5.4)

3.2.3.1.2 If the Offeror intends to use sub-vendor repair to perform repairs in part, or in whole, the Offeror is to provide their plan for integrating sub-vendor repair to fulfill the requirements of the PWS. Where sub-vendor repair is used the Offeror is to explain the process used to determine the differentiation between using In-house repair and sub-vendor repair and the process (if any) for developing new

In-house repair capability. (PWS 3.4.5)

3.2.3.2 Obsolescence Management. The Offeror shall:

3.2.3.2.1 Provide a detailed description of the approach to the logistics management process as it applies to parts control. Include information on the management methods, processes for identifying and managing parts obsolescence, and overall planning and implementation for Diminishing Manufacturing Sources and

Material Shortages (DMSMS) (PWS 3.5.1.1, 3.5.2.3, 3.6.2.5).

3.2.3.3 Systems Sustainment Engineering. The Offeror shall:

3.2.3.3.1 Provide a Configuration Management Plan, specific to the CAMMO environment, as Attachment T1 to the Technical Volume, to include procedures/ processes/controls for defect tracking, auditing, unique site/side configurations, baseline build, environment and process management. Address how the Offeror will maintain configuration control of the baseline and modification management process as well as demonstrating the capability to store, manage, and implement

Class I/II Engineering Change Proposals (ECP) including Depot Maintenance

Actions. (PWS 3.6.2.7, 3.4.6.2)

3.2.3.3.2 Provide a detailed explanation, with examples, of how systems sustainment engineering processes will be applied to CAMMO requirements for: Reliability, Maintainability, and Availability (RMA); obsolescence; and software sustainment. Include a methodology to ensure processes are followed and improved, and any metrics employed in process implementation/improvement.

(PWS 3.6.2.10, 3.6.2.1, 3.6.2.5, 3.7.2)

3.2.3.4 Cyber Security and Information Assurance. The Offeror shall:

3.2.3.4.1 Reserved

3.2.3.5 Modification Planning. The Offeror shall:

3.2.3.5.1 Provide a Modification Management Plan specific to the CAMMO environment as Attachment T2 to the Technical Volume that will be placed on contract that clearly describes the Offeror’s approach to planning and implementing modifications. Include how the Offeror will allocate resources and manage up to

8 concurrent modifications per year and describe the application of systems engineering principles, requirements analysis, functional analysis, and site integration interdependency. (PWS 3.7.1)

3.2.3.6 Software Sustainment. The Offeror shall:

3.2.3.6.1 Provide a Software Development Plan, specific to the CAMMO environment, as

Attachment T3 to the Technical Volume, which will include all tasks relative to processing software version releases, Software Maintenance Actions (SWMA), and Inter-Range Operations Number (IRON) database change releases. Include identification, analysis, and prioritization of: change requests; Deficiency Reports

(DR); coding and testing; and packaging and delivery. The software development plan shall also include the Offeror’s approach to software assurance, quality, and database accuracy. (PWS 3.7.2, 3.6.2.11)

3.2.3.6.2 Provide a detailed description of the process to update the IRON database and implement IRON updates to the AFSCN. The description shall include the

Offeror’s testing methodology to ensure error free IRON database updates and validation/verification. (PWS 3.3.3)

3.2.4 Subfactor 4 – Program Management

3.2.4.1 Key Technical Staffing. The Offeror shall:

3.2.4.1.1 Provide a Staffing Plan as Attachment T4 to the Technical Volume that shows clear evidence and an implementation timeline (hiring procedures, retention statistics, contingency offers to potential employees, etc.) to enable the Offeror to obtain the proposed staff to perform all tasks in the PWS within the required time constraints.

3.2.4.1.2 Provide an organizational structure which identifies CAMMO key positions.

Provide job descriptions and core competencies for these key positions. (PWS

3.2.1, 3.3, 3.4, 3.6.2, 3.6.3, 3.6.4, 3.7.2)

3.2.4.1.3 Provide estimated man-hours down to the lowest level shown in the WBS for the base year and each option period of the contract. Submit using the format provided in Annex B of Section L and submitted as Attachment T5 to the

Technical Volume.

3.2.4.1.4 For the information provided as Attachment T5 to the Technical Volume, provide as Attachment T6 to the Technical Volume, the Bases of Estimate (BOE). For each WBS level, submit a supporting narrative (tables may be used to support the narrative) which:

a) Provides the rationale used to estimate the WBS man-hours (Attachment T5) with the associated PWS reference.

b) Details the skill mixes required

c) Indicates shift work where applicable

d) Indicates any dependency upon Collective Bargaining Agreements (CBA).

e) Describes proposed integration of operations, maintenance (Level 1/Level 2) and operations support.

f) Provides the rationale that supports changes to man-hour estimates by option period of the contract.

Note: The BOE supporting documents do not count against page limits for the

Technical Volume. They shall be submitted following all formatting requirements for hardcopy and electronic files outlined previously in Section L.

3.2.4.2 Small Business. The Offeror shall:

3.2.4.2.1 Provide a Small Business Subcontracting Participation Plan as Attachment T7 to the Technical Volume, that will be placed on contract and fulfills the requirements in the Contract Volume, that shows the intended methods or path to accomplishing the required small business participation rate. (PWS 3.6.3.11)

3.2.4.3 Public Private Partnership (PPP).

In accordance with 10 USC 2460, 10 USC 2464, and 10 USC 2474, it is the intent of the government to use the PPP with 309 SMXG to facilitate the growth of organic core capabilities.

The Contractor is encouraged to support 309 SMXG in their effort to attain core competency for

ESD 3.0 and RBC software sustainment to fulfill the strategic and contingency plans of the

Department of Defense. 10 USC 2474 Core Logistics Capabilities include those capabilities that are necessary to maintain and repair the weapon system and the workload required to maintain those capabilities. For software sustainment, core capabilities include knowledge and performance of all components of software development from requirements definition to acceptance testing. For additional information on completing the draft Partnership Agreement and Implementation Agreement, Offerors can contact the OO-ALC point of contact Misty Goss

(misty.goss@us.af.mil; 801-777-8173).

The Offeror shall:

3.2.4.3.1 Provide a Public Private Partnership Plan as Attachment T8 to the Technical

Volume that includes a draft Partnership Agreement between the Offeror and the

Ogden Air Logistics Complex (OO‑ALC) 309th Software Maintenance Group

(309 SMXG) and a draft Direct Sales Implementation Agreement that satisfies the requirements of the CAMMO PWS. The ESD 3.0 and RBC partnered workload will be accomplished in the contractor’s facility. (PWS 3.6.3.12) mailto:misty.goss@us.af.mil

3.2.4.4 Transition Plan Phase-in. The Offeror shall:

3.2.4.4.1 Provide a Transition Plan as Attachment T9 to the Technical Volume that will be placed on contract to assume responsibility for performing the tasks in the

CAMMO PWS within the designated phase-in transition period. Identify critical risks and strategies to mitigate these risks associated with assuming full responsibility of the CAMMO requirements.

3.2.4.4.2 Identify critical risks associated with assuming responsibility of specific Phase-In transition period task areas and strategies to mitigate these risks, focusing on preventing any negative impact. Mitigation plans are appropriately mapped to the transition timeline. Specific task areas to be addressed are:

a) AFSCN Test Bed (PWS 3.9.1.2)

b) Repair Line (PWS 3.9.1.3)

c) Electronic Data Interchange (EDI) (PWS 3.9.1.5)

d) Government Furnished Property (GFP)/Government Furnished Equipment

(GFE) (PWS 3.9.1.7)

3.2.5 Subfactor 5 –Scenario

3.2.5.1 Reserved

3.2.5.1.1 Reserved

4.0 Volume III – Past Performance

Each Offeror shall submit a Past Performance Volume with its proposal, containing past performance information as requested in this section. This information is required of the Offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform aspects of the effort the Offeror considers critical to successful performance. The contracts must be recent and relevant in accordance with the criteria established in Section M.

Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.

If no relevant past or present performance information exists, do not submit a Volume III.

Instead, explain in the proposal transmittal letter that no relevant past or present performance exists. The Government reserves the right to obtain information from other sources to assess the

Offeror’s past and present performance.

4.1 Organizational Structure Change History

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

4.2 Teaming Arrangements

If a teaming arrangement is contemplated, the Offeror shall provide information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangements with same partner. If this is a first time joint effort, each party to the arrangement must provide a list of past relevant contracts.

4.3 Subcontractor Consent

Past performance information pertaining to a subcontractor cannot be disclosed to the prime

Offeror without the subcontractor’s consent. Provide with the proposal letters from all subcontractors that will perform major or critical aspects of the requirement as Attachment PP1 to the Offeror’s Past Performance Volume, consenting to the release of their past performance information to the prime contractor.