SBIRS Low

ATTACHMENT 1 - SBIRS LOW COMPONENT STATEMENT OF OBJECTIVES (SOO)

F04701-98-R-0006

SBIRS LOW COMPONENT STATEMENT OF OBJECTIVES (SOO)

1.0 Program Scope

The Space Based Infrared Systems (SBIRS) Low Component Program Definition (PD) effort will result in an initial system design which can be used to develop, manufacture, deliver, operate, and sustain the Low Earth Orbit (LEO) portion of the SBIRS System-of-Systems (SoS) architecture. The SBIRS Low system design includes a space segment and associated ground elements. This design must satisfy, as a minimum, the SBIRS Operational Requirements Document (ORD) requirements as allocated to the Low Component in the SBIRS Requirements Allocation Document (RAD). The design must also reflect PD cost/military utility trade study recommendations (i.e., Cost as an Independent Variable (CAIV) trades). Successful accomplishment of the SBIRS Low PD objectives will support a Milestone II decision to enter Engineering and Manufacturing Development (EMD). In support of a Milestone II decision, the PD contract will contain a provision directing special studies to assess life cycle cost and design impacts resulting from changing/evolving requirements and to provide cost/engineering trades on objective system design changes. The PD contract will also include a provision which will allow for extension of the PD contract effort until such a time, if any, that an EMD contract is awarded. An overview of the acquisition schedule for this PD effort is included as Figure 1. Additional detail is available in the SBIRS Single Acquisition Management Plan (SAMP).

1.1 Background

1.1.1 Congress mandated an accelerated SBIRS Low program deployment and the Department of Defense and the USAF have committed to beginning this deployment in FY04. The SBIRS Low program will be developed as part of the SBIRS SoS architecture. The acquisition of this architecture is proceeding in four increments as is described in the SBIRS Single Acquisition and Management Plan (SAMP) and displayed in Figure 2. Increment 1 consists of the consolidation of the Defense Support Program (DSP), Attack Launch Early Report to Theater (ALERT), and Joint Tactical Ground Station (JTAGS) ground operations. Increment 2 refers to the actual deployment of the SBIRS High Block I. Increment 3 will add the SBIRS Low capabilities to the SoS architecture. Full constellation deployment is expected by mid-FY08. In Increment 4, the SBIRS High/Low system will be updated as driven by the evolving environment to provide best value to the government.

  1. The baseline SBIRS architecture includes satellites in Geosynchronous Earth Orbit (GEO), Low Earth Orbit (LEO), and sensors hosted on satellites in Highly Elliptical Orbit (HEO). Ground assets include: a Continental United States (CONUS)-based Mission Control Station (MCS), a backup MCS (MCSB), a survivable MCS (SMCS), overseas Relay Ground Stations (RGSs), a survivable RGS (SRGS) and Multi-Mission Mobile Processors (M3Ps) with associated infrastructure and associated communications links; and training, launch and support infrastructures. The SBIRS Low Component for Increment 3 provides the LEO satellite constellation for precision midcourse tracking capability critical for effective Ballistic Missile Defense. SBIRS Low Component for Increment 3 will also improve capabilities for missile warning, technical intelligence, and battlespace characterization by complementing the performance of SBIRS Increment 2. The SBIRS Low Component for Increment 3 includes provisions to incorporate associated ground elements to provide any unique command, control, data processing, and external interface capability to the entire SBIRS ground segment.
  2. It is anticipated that the SBIRS System of Systems (SoS) contractor will have total system performance responsibility (TSPR) for SBIRS Increment 3 performance against ORD requirements. The SBIR High contractor has total responsibility for the SBIRS high system specification for Increment 1 and 2. The SIBRS Low contractor has total responsibility for low system specification for Increment 3. TSPR for the integrated ground segment will be resolved during the PD phase, as stated in specific PD SOO objective 2.6

2.0 Specific Objectives

Figure 1 provides an overview of the acquisition schedule for PD. Figure 2 provides a top level description of activities associated with the four increments of the SBIRS Master Acquisition Strategy. The following are specific objectives (priority order not implied):

2.1 Identify the relationship between performance, cost, utility, schedule, and risk to support development of an affordable set of operational requirements for entry into SBIRS Low EMD which maximize utility for the user.

2.2 Design SBIRS Low Component for Increment 3 consistent with the schedule in Figure 1, to include an Increment 3 to Increment 4 transition approach.

2.3 Define and justify an integrated approach to design, produce, test, deploy and sustain the SBIRS Low Component for Increment 3.

2.4 Define, justify and implement a program management approach to assess, handle, and monitor program risks for SBIRS Low Component for Increment 3.

2.5 Define and justify a Test and Evaluation approach for verification of SBIRS Low Component for Increment 3 requirements and support SBIRS SoS requirements verification.

2.6 Refine the current SBIRS Low EMD definition, to include TSPR roles, responsibilities and implementation

Figure 1

 

Figure 2

ANNEX A - CWBS AND CWBS DICTIONARY

F04701-98-R-0006

 

CWBS and CWBS Dictionary

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________*

Reference special RFP Section L 2.1.1.3.2 for instructions.

 

ANNEX B - INTEGRATED MASTER PLAN (IMP)

F04701-98-R-0006

 

IMP

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________*

Reference special clause H.3 and RFP Section L for IMP instructions. The Offeror shall submit an IMP to demonstrate that the program is structured to accomplish technical requirements while minimizing and controlling program risks. The IMP shall capture the core activities and processes necessary to accomplish the SOO.

 

 

ANNEX C - /REFERENCE DOCUMENTS LIST

F04701-98-R-0006

Compliance/Reference Documents List

The Offeror has maximum freedom to propose additional Compliance/Reference documents as appropriate. The documents listed in this RFP may be found in the SBIRS Low Library.

Compliance Documents

SBIRS Operational Requirements Document (ORD), Annex 1, dated 17 Jul 98.

SBIRS Low Component Requirements Allocation Document, dated 15 Jul 98.

Avoidance of Organizational Conflict of Interest (OCI) Regarding the SBIRS Low Component Program Competition, dated 15 May 97.

SBIRS System Protection Guide, 1 Oct 97 and Revision 1, 12 Mar 98

20/44 GHz EMI Assessment of Proposed SBIRS Low Fixed Ground Sites in the Continental United States, June 98

SBIRS Low X-Link ApS4/II, Apr 98

_____________________________________________*

Reference Documents (As Dated Below and Subsequent Releases)

SBIRS Requirements Study Plan (RSP), dated 20 Jul 98.

SBIRS Test and Evaluation Master Plan (TEMP), dated 21 Apr 98.

SBIRS Single Acquisition Management Plan (SAMP), dated 15 Jun 98.

SBIRS System Threat Analysis Report (STAR), dated 14 Jul 98.

SBIRS Integrated Test & Evaluation Plan (ITEP), dated 19 Dec 97.

DOD Joint Technical Architecture Web Page, http://www-jta.itsi.disa.mil/

OSD Risk Management Structure (DoDD 5000.1 and 5000.2-R), dated 15 Mar 96.

http://www.safaq.hq.af.mil/acq_pol/dod5000/final/

AFMC Pamphlet 63-101, Risk Management, dated _9 July 1997, http://afmc.wpafb.af.mil/pdl/afmc/pam/63series/63_101/63-101.pdf

Representative Threat and Scenarios Documents that are listed in the SBIRS Low Library Listing, at http://www.laafb.af.mil/SMC/MT/MTBUSOP/Liblist.htm including the SBIRS Target Book, NMD C1 and C2 Threat Documents, and TMD Campaign Scenarios including NEA, SWA-N, SWA-S, and East Asia."

SBIRS Target Note Book, dated ______**___________.

__________________________________________*

 

 

 

ANNEX D - SBIRS ACRONYM LIST (SAL)

F04701-98-R-0006

 

SBIRS Low Acronym List

Update this Annex per instructions in RFP Section L-2.1.1.

ADM Acquisition Decision Memorandum

AF Air Force

AFFARS Air Force Federal Acquisition Regulation Supplement

AFOTEC Air Force Operational Test and Evaluation Center

AFPEO/SP Air Force Program Executive Officer for Space

AFSPC Air Force Space Command

AIS Automated Information System

ALARM Alert, Locate And Report Missiles

ALERT Attack and Launch Early Reporting to Theater

APB Acquisition Program Baseline

AQ Acquisition

AS Archive Subsystem

ASSAT Aerojet Sensor Simulation and Algorithm Testbed

ATP Authority To Proceed

BMDO Ballistic Missile Defense Organization

BNA Boeing North America

BSC Battle Space Characterization

C&DH Command and Data Handling

C4I Command, Control, Computers, Communication and Intelligence

CAIG Cost Analysis Improvement Group

CAIV Cost As an Independent Variable

CARD Cost Analysis Requirements Description

CBD Commerce Business Daily

CDF Contractor Development Facility

CEO Chief Executive Officer

CFI Call For Improvements

CII Compatibility, Interoperability, and Integration

CINC Commander-In-Chief

CITIS Contractor Integrated Technical Information System

CLS Contractor Logistics Support

CMO Central MASINT Office

COEA Cost and Operational Effectiveness Analysis

COI Critical Operational Issue

CONUS Continental United States

CPAF Cost Plus Award Fee

CPFF Cost Plus Fixed Fee

CRD Capstone Requirements Document

CS Communications Subsystem

CTP Critical Technical Parameter

DAB Defense Acquisition Board

DAE Defense Acquisition Executive

DAES Defense Acquisition Executive Summary

DDTS Distributed Deficiency Tracking System

DFAR Defense Federal Acquisition Regulation

DIA Defense Intelligence Agency

DISA Defense Information Services Agency

DoD Department of Defense

DOT&E Director, Operational Test and Evaluation

DPS Data Processing Subsystem

DSP Defense Support Program

DT Developmental Test

DT&E Developmental Test and Evaluation

DTSE&E Director, Test, Systems Engineering, and Evaluation

DUSD(SP) Deputy Undersecretary of Defense (Space)

EA Environmental Analysis

EC/EDI Electronic Commerce/Electronic Data Interchange

EDS End-to-End Digital Simulation

EELV Evolved Expendable Launch Vehicle

EMC Electro-Magnetic Compatibility

EMD Engineering and Manufacturing Development

EMP Electromagnetic Pulse

ERS European Relay Station

ESH Environmental, Safety and Health

ETERTS End to End Real Time Simulation

ETM Engineering Test Model

FAR Federal Acquisition Regulation

FDS Flight Demonstration System

FIST Final Integrated Satellite Test

FY Fiscal Year

GEO Geosynchronous Earth Orbit

HEO Highly-Elliptical Orbit

HOSV High Orbit Space Vehicle

HWIL Hardware-In-The-Loop

ICE Independent Cost Estimate

ICWG Interface Control Working Group

IDR Initial Design Review

ILS Integrated Logistics Support

IMP Integrated Management Plan

IMS Integrated Master Schedule

IOC Initial Operational Capability

IOT&E Initial Operational Test and Evaluation

IPT Integrated Product Team

IR Infrared

ISP Intelligence Support Plan

IST Integrated System Test

ITEP Integrated Test and Evaluation Plan

ITW/AA Integrated Tactical Warning/Attack Assessment

JITC Joint Interoperability Test Center

JRMET Joint Reliability and Maintainability Evaluation Team

JROC Joint Requirements Oversight Council

JTAGS Joint Tactical Ground Station

JTF Joint Task Force

KPP Key Performance Parameter

LADS Low Altitude Demonstration System

LEO Low Earth Orbit

LMMS Lockheed Martin Missiles and Space

M3P Multi-Mission Mobile Processor

M&S Modeling and Simulation

MASINT Measurement and Signals Intelligence

MCS Mission Control Station

MCSB Mission Control Station Backup

MDA Milestone Decision Authority

MER Manpower Estimate Report

MOE Measure of Effectiveness

MOP Measure of Performance

MRC Major Regional Conflict

MSII Milestone II

MS&T Models, Simulations, and Testbed

MSTI Miniature Space Technology Investigation

MSX Midcourse Space Experiment

MWIR Medium Wave Infrared

NBMD National Ballistic Missile Defense

NCA National Command Authority

NEPA National Environmental Policy Act

NMD National Missile Defense

OA Operational Assessment

OASD Office of the Assistant Secretary of Defense

OCI Organizational Conflict of Interest

OEC Operational Evaluation Command (Army)

OGC Other Government Costs

OIPT Overarching Integrated Product Team

OPRA OT&E/Program Readiness Assessment

OPTEC Operational Test and Evaluation Center (Army)

ORD Operational Requirements Document

OSD Office of the Secretary of Defense

OSG Optical Scene Generator

OT Operational Test

OTA Operational Test Agency

OTA Optical Telescope Assembly

OT&E Operational Test and Evaluation

PDR Preliminary Design Review

PDRR Program Definition and Risk Reduction

PEO Program Executive Officer

PESHE Programmatic Environmental Safety and Health Evaluation

PMA Pointing Mirror Assembly

PPM Pollution Prevention Manager

PRB Payload Reference Bench

RAD Requirements Allocation Document

RFP Request for Proposal

RGS Relay Ground Station

RRG Requirements Review Group

RT Relocatable Terminal

RWD Real World Data

SAE Service Acquisition Executive

SAF/AQ Office of Secretary of the Air Force (Acquisition)

SAF/AQS Office of Secretary of the Air Force (Acquisition), Directorate of Space and Nuclear Deterrence

SAMP Single Acquisition Management Plan

SBIRS Spaced Based Infrared

SBIRS Spaced Based Infrared Systems

SC Standards Conformance

SCIF Special Compartmentalized Information Facility

SCP Service Cost Position

SDR System Design Review

SFR System Functional Review

SMC Space and Missile Systems Center

SMC/MT Space Based Infrared Systems Program Office

SMCS Survivable Mission Control Station

SMTS Space and Missile Tracking System

SOO Statement of Objectives

SPD System Program Director

SRGS Survivable Relay Ground Station

SRR System Requirements Review

SSM Single System Manager

SSTB SBIRS Test Bed

STAR System Threat Assessment Report

STRATSWG Scenario Working Group

STIL Sensor Test Integration Laboratory

SV Space Vehicle

SWF Senior Warfighters Forum

T&E Test and Evaluation

TT&C Tracking, Telemetry, and Control

TBD To Be Determined

TBS To Be Supplied

TDSB Test Data Scoring Board

TEMP Test and Evaluation Master Plan

TES Tactical Event System

TEWG Test and Evaluation Working Group

TI Technical Intelligence

TP Trial Period

TPM Technical Performance Measure

TRD Technical Requirements Document

TSPR Total System Performance Responsibility

UDS Uplink/Downlink Subsystem

USAF United States Air Force

USD(A&T) Under Secretary of Defense (Acquisition & Technology)

USSPACECOM United States Space Command

V&V Verification and Validation

VCRM Verification Cross Reference Matrix

VV&IA Verification, Validation, and Independent Accreditation

WIPT Working Integrated Product Team

 

 

 

 

__________________________*

 

 

EXHIBIT A - CONTRACT DATA REQUIREMENTS LIST (CDRL)

F04701-98-R-0006

 

Contract Data Requirements List (CDRL)

The Offeror has maximum freedom to propose revisions as appropriate. Under the current, streamlined acquisition approach, formal DD Form 1423s should be minimized. Unless dictated by the Data Item Description (DID), contractor format is acceptable for all deliverables. The Offeror may consider describing data products that result from processes described in the IMP. Every attempt should be made to minimize the CDRL by proposing alternate forms of assuring data accessibility. Information can be provided via on-site reviews, team meetings, or other means considered adequate by the Offeror in lieu of formal CDRL items. The Offeror should present the types of data to be made available, the method of accessibility, formatting requirements, and distribution information. This can be done as a formal CDRL item, with text in the Integrated Master Plan (IMP), or any other way that the Offeror believes will produce the proper insight. Formal CDRL items as well as approved DIDs may be used if the Offeror can show that they are the most cost effective approach, but alternate forms of accessibility are strongly preferred. E.g., where possible, delivery shall be by Electronic Data Interchange Network (EDIN), ref CLIN 0006 and SCR H.4, in lieu of paper delivery. The only formal deliverable item, i.e. one requiring a DD 250, is CLIN 0006 (EDI).

The Government has provided the minimum set for a List of Required Data Products, a distribution list, and attached the appropriate DD 1423-1 for each data product which requires formal delivery. The Offeror may add to that list, but all additions should be justified. DIDs that are used must be among those listed in the current Acquisition Management Systems and Data Requirements Control List (AMSDL, DOD 5010.12-L). DIDs should be tailored to assure that only the necessary information is included and that it is in a cost effective format. The government provided CDRL was developed considering only those documents that are needed during the Program Definition phase of the contract. A list of documents needed during the EMD phase will be developed during Program Definition.

 

CONTRACT DATA REQUIREMENTS LIST (CDRL) INSTRUCTIONS

(these instructions apply only to formal CDRL items)

  1. The Contractor shall provide full access to the Government per Special Clause H.4.

2. BLOCK A - Each CDRL must refer to a CLIN.

3. BLOCK 4 - Only the preparation instructions contained in Block 10 of the DID, which may be further adjusted or clarified in Block 16 of DD Form 1423-1, are contractually binding. If a DID is tailored so that "contractor format is acceptable," a traceability matrix shall be provided in the front of the document tracing the contractor format to the DID format. Regardless of the format, the Contractor shall meet the content requirements of the DID as tailored in Block 16 of the CDRL. Any MIL-Spec or -Std referenced in the DID or Block 16 shall be used as guidance only.

4. BLOCK 7 - All data shall include a letter of transmittal as its first page that contains: the contract number, CDRL number being submitted, letter number and date, and distribution.

5. BLOCK 8 - Block 8 is to be left blank. All deliverable data is subject to disapproval via a PCO letter if it does not meet contractual requirements. An entry of the letter "A" in Block 8 of the DD Form 1423-1 indicates specific advanced written approval is required prior to distribution of the data. Regardless of whether there is an "A" in Block 8 or not all deliverable data is subject to disapproval via a PCO letter if it does not meet contractual requirements.

6. BLOCK 9 - All documents shall be marked with the following distribution statement, unless the Contractor determines the appropriate distribution statement to be different: "Distribution limited to DoD and DoD contractors only. Reason: Critical Technology. Date of determination: Contract effective date. Other requests shall be referred to SMC/MTKA." The Contractor is ultimately responsible for correctly marking the data. If the data is improperly marked, it will be rejected via a PCO letter. All documents shall be marked with Distribution Statement "D" unless the contractor determines the appropriate Distribution Statement to be assigned to the document is something other than "D". Either way the contractor is ultimately responsible for correctly marking the data using Mil-Std-1806 as reference. If the data is determined, by the government, to be improperly marked, it will be rejected via a PCO letter.

7. In addition to the distribution statement, classified documents and limited distribution documents, shall be marked with proper destruction notices. In addition to the distribution statement, the notice in paragraph 5.2.1 of MIL-STD-1806 shall be used when appropriate as well as the following notice:

DESTRUCTION NOTICE

For classified documents follow the procedures in DOD Manual 5200.22, Industrial Security Manual, Section 11-19, or DOD Regulation 5200.1, AFR 205-1, Information Security Program, Chapter IX. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

8. If a DID is not tailored so that "contractor format is acceptable", strong justification for the specified format should be included in Block 16 of the CDRL.

9. All documents requiring "Revisions as Required" shall be updated whenever any major revision is made to the document, the program or when requested by the PCO.

10. BLOCK 14 - Data that is "preliminary" or "draft" should be so marked. Data that has limited distribution requirements should be so marked and the reason for the limitations should be shown. The distribution for preliminary/drafts, unless otherwise specified on the CDRL are identified under the column entitled "Draft" and for finals under the column entitled "Final" on the Office Distribution Matrix. The quantities for shipment are expressed by two (2) numbers separated by a "/". The first number represents the number of regular (paper) copies required, the second number represents the number of electronic copies (e.g. disks) required.

11. The following codes are used when preparing the DD Form 1423-1. When a code is used in front of a number with a "CD" following, this indicates the number of days after an event. For example, PR30CD indicates delivery 30 calendar days after a Program Review. In a case where data would be delivered before an event, the example would be 30CDPR, which indicates delivery 30 calendar days before a Program Review.

CD

= Calendar Days

PR

= Program Review

ATP

= Authority to Proceed

2TIME

= Two Separate Submittals

EOC

= End of Contract

ONE/R

= One Time with Revisions

SCR

= Special Contract Requirement

R/ASR

= Revisions as Required

12. DoD 5010.12-M describes the entries in each block of the DD Form 1423-1.

13. All Plans, Procedures, and Specifications shall contain an "Applicable Documents" section. All printed pages of each document shall contain the document control number and the date of the document in either the upper corner, opposite the binding of the page or the center of each page. Document control numbers shall include the revision and volume identification, as applicable. Each page prior to the text shall be numbered in lower-case Roman numerals beginning with page ii following either the cover page or beginning with the Table of Contents. Each page starting with the text to the appendices shall be consecutively numbered in Arabic numerals. If the document is divided into volumes, each such volume shall restart the page numbering sequence.

14. All TOP SECRET documents shall be contained on a separate hard copy and shall be delivered to the Space Based Infrared System Top Secret Control Officer (TSCO) or designated official alternate TSCO. All SENSITIVE COMPARTMENTED INFORMATION (SCI) documents shall be contained on a separate hard copy and shall be delivered to the Space Based Infrared System Special Security Officer (SSO) or designated official alternate SSO.

DATA ITEM DESCRIPTION (DID)

Title: LIFE CYCLE COST ESTIMATE

Number: OT-1998-30001 Approval Date: 04/08/98

AMSC Number: N/A Limitation: Solicitation

DTIC Applicable: No GIDEP Applicable: No

Office of Primary Responsibility: F-SMC/MTA

Applicable Forms:

Use/relationship: The Life Cycle Cost (LCC) Estimate is a prediction of actual life cycle cost of a system. The LCC is the total cost to the Government of acquisition and ownership. It includes the cost of development, acquisition, operation, support, PDRR, EMD, production, sustainment, and disposal.

LCC estimates provide essential data to the Government when considering acquisition versus operating and support cost, comparing competing prototypes, or comparing current versus new systems. Cost as An Independent Variable (CAIV) trades between acquisition versus operating and support costs are of paramount interest.

This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract Integrated Master Plan (IMP).This DID is for one-time use for solicitation F04701-98-R-0006 or F04701-98-R-0008

Requirements:

1. Reference documents. MIL-HDBK-881, Work Breakdown Structure (WBS); DODD 5000.1, Defense Acquisition; DOD 5000.2-R, Mandatory Procedures for Major Defense Acquisition Programs and Major Automated Information System Acquisition Programs; DOD 4245.7-M, Transition from Development to Production; DODD 5000.4, Office of Secretary of Defense Cost Analysis Improvement Group; AFMCP 63-101, Risk Management Handbook; and SMC publication, Cost Risk Identification and Management System (CRIMS) for guidance only. References will be provided by the government as delineated in the contract.

2. Format. Contractor format acceptable.

3. Content. The report shall contain the following:

3.1 Costs based on PDRR, EMD, procurement, sustainment, and disposal. The costs are displayed as fiscal year dollars to include overhead, general and administrative expense, and estimated fee or profit, as applicable.

3.2 Cost Summary: A proposed cost summary for the contract phase and total life cycle using the content outline below. Affordability and CAIV trade studies shall be captured here. Estimates are expected to be refined over the life-cycle, however these initial estimates establish the program cost baseline against which selected offerors will be measured during the contract execution.

3.3 Total Estimate/Purpose: A brief summary of how this estimate was prepared. Includes the "bottom line" total value of the estimate at the 50% confidence level in Then Year dollars.

3.4 Estimate Summary and Time Phasing: Top level estimate summary by major segment (e.g., launch vehicle, space segment, ground segment) to include a point estimate (i.e., the sum of initial estimates from cost models/methodologies, prior to any dollars added to them for risk impacts), ranges, and 50% confidence estimate. Estimates shall be phased in Base Year (BY) and Then Year (TY) dollars using FY 98 OSD inflation rates and tables.

3.5 Issues/Content - A discussion of program and estimate contents, concerns, and assumptions at Program WBS level or lower levels as deemed appropriate with respect to the following:

- Program schedule

- Major factors bearing on estimates

- Business base considerations

- Cost drivers (high cost elements of estimate, risk drivers, etc.) to include a correlation matrix of risk areas to the impacted Contractor WBS elements including the high risk elements identified by the offeror.

- Evaluate the CWBS elements with respect to the following uncertainty category risk areas: hardware, software, design and engineering, technology, manufacturing, schedule, cost estimating, integration, supportability, complexity, interactions/dependencies and threat, as appropriate.

3.6 Programmatic Alternatives: Describes solutions to issues addressed in section 3.5 as well as sensitivity analyses/excursions (e.g., changes in the estimate due to changes in major cost drivers and risk drivers).

4. The LCC Estimate shall contain:

4.1 Overview Section - This section shall briefly describe the detailed WBS section that follows including how the detailed WBS section is organized. The overview sshall describe the detailed spreadsheets in the detailed WBS section. The detailed spreadsheets shall show estimates down to the lowest level. All spreadsheets shall be traceable to the documentation so as to ensure the capability to replicate the estimates as described. This section shall also contain the following:

1. Purpose of estimate

2. Name and telephone number of point of contact for the estimate.

3. Summary program description

4. Scope of estimate

5. Major cost factors bearing on the estimate

6. Risk areas assessments (see Cost Summary paragraph 3.2)

- Summarizes risk mitigation plans to support 50% confidence level estimate

7. Program schedule

8. Ground rules and assumptions

4.2 Detailed Section: Estimates shall be in accordance with the contractor’s extended CWBS. Cost-risk assessments shall be consistent with the offeror’s risk area/CWBS correlation matrix. When the high risk element falls at a sub-level, estimate the cost and cost-risk at that sub-level and indicate the cost impact due to risk at the higher WBS level. All estimates shall use the latest OSD inflation rate tables. Each level estimated shall contain:

- a phasing approach explanation

- a phased estimate by year in program Base Year (BY) and Then Year (TY) dollars for the FYDP

- a phased estimate by year for a To Complete (TC) category in program BY and TY dollars post-Fiscal Year Defense Plan (if applicable)

- an estimating approach explanation

- a risk assessment explanation containing an identification of the risk(s) itself and a description of the pessimistic, most likely and optimistic scenarios or profiles in which different levels of the identified risk(s) occur

- a quantification of the cost-risk in dollars associated with the pessimistic, most likely and optimistic scenarios

- a description of the risk mitigation planned

- an identification of sources of data

4.3 Lower level WBS element estimating methodologies shall contain descriptions and justifications for the estimating approaches used, such as analogies, parametrics, factors, models, tools, formulas, allocation schemes, learning curves, cost-risk techniques, etc., that will enable an independent estimator to replicate the estimate as described. The detailed basis of estimate provided for each of the lower level WBS elements shall include a logical, sequential development of the estimate, cost quantification of risk (if done at that level), methodology, logic and rationales, and source/use/limitations of data utilized in derivation of the estimates.

4.4 "Roll-up" is an acceptable description of methodology if the estimate was developed at a lower WBS level. If an estimating methodology is identical for all lower level elements, methodology need only be described once at the next highest WBS level.

4.5 Key ground rules and assumptions, business base assumptions, and trade analyses shall also be clearly documented.

  1. Global pointers to identify where explanations for

risk, key drivers, estimating approaches, etc., are described; if the explanations are not described at the level currently being discussed.

  1. End of OT-1998-30001

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DOWNLOAD CDRLS AS SEPARATE ATTACHMENT

 

 

ATTACHMENT 2 - RESERVED

F04701-98-R-0006

This attachment is reserved.

 

 

ATTACHMENT 3 - SUBCONTRACTING PLAN FOR SMALL AND SMALL DISADVANTAGED BUSINESS CONCERNS

F04701-98-R-0006

To be inserted by offeror.

 

 

ATTACHMENT 4 - SBIRS LOW COMPONENT CONTRACT SECURITY CLASSIFICATION SPECIFICATION (DD 254) AND INSTRUCTIONS

F04701-98-R-0006

SBIRS Low Component Contract Security Classification Specification
(DD 254) and Instructions

 

COMSEC and/or Cryptographic Access

 

Applicable block: l0a

DOD 5220.22-S applies to contractor facilities and operations. Access to COMSEC material/information is restricted to U.S. citizens holding final U.S. Government clearances and is not releasable to personnel holding only a reciprocal clearance. The COMSEC/Crypto briefing applies only to the use and control of Crypto equipment and specialized COMSEC publications. NACSIM/NACSEM documents are not considered COMSEC controlled material. The Program Manager shall designate the number of personnel requiring cryptographic access. The number will be limited to the minimum necessary, will be on a strict need-to-know basis.

 

 

Critical Nuclear Weapon Design Information

Applicable Block: l0b-d.

The contractor is permitted access to restricted data, formally restricted data, and CNWDI in performance of this contract. Contractor requests for this information will be validated by the COTR and is not releasable to employees who are intending citizens, foreign nationals or those having limited access authorizations. Contractor personnel must be briefed for CNWDI prior to access and debriefed when access is no longer required. Records will be maintained per NISPOM.

 

RESTRICTED DATA AND FORMERLY RESTRICTED DATA

 

This Section contains information and the requirements for safeguarding atomic energy information that is designated "Restricted Data" and "Formerly Restricted Data." Such information is classified under the authority of the Atomic Energy Act of 1954 (as amended) and is under the jurisdiction and control of the Department of Energy (DOE).

The Atomic Energy Act of 1954, as amended, provides for the development, use, and control of atomic energy. The Act establishes policy for handling atomic energy-related classified information designated as Restricted Data (RD) and Formerly Restricted Data (FRD). The Act provides responsibility to DOE to "control the dissemination and declassification of Restricted Data." This clause is intended to ensure reasonable conformity in policy and procedures used by contractors for the control of RD and FRD.

Classified information in the custody of the Department of Defense marked as Restricted Data under the Atomic Energy Act, shall be stored, protected, and destroyed as required.

In accordance with the Atomic Energy Act, all atomic energy information remains classified unless action is taken to declassify material only by the Department of Energy. No other organization can declassify atomic energy information, and once it is declassified, it cannot be reclassified.

"The term Restricted Data (RD) means all data concerning (1) design, manufacture, or utilization of atomic weapons (2) the production of special nuclear material; or (3) the use of special nuclear material in the production of energy, but shall not include data declassified or removed from the Restricted Data category pursuant to Section 142"

The term Formerly Restricted Data (FRD) is information which has been removed from the Restricted Data category after the DOE and the DoD have jointly determined that the information relates primarily to the military utilization of atomic weapons and can be adequately safeguarded as National Security Information in the US. Such data may not be given to any other nation except under the terms of an agreement for cooperation. The disclosure by a contractor of RD and FRD shall not be permitted until an agreement is signed by the US and participating government(s) and disclosure guidance and security arrangements have been established.

 

The following notice shall be affixed on material that contains Restricted Data. This may be abbreviated RD.

Restricted Data

This material contains Restricted Data as defined in the Atomic Energy Act of 1954. Unauthorized disclosure subject to administrative and criminal sanctions.

 

Material classified as RD must indicate the classification guide and the authorized RD classifier. The following marking shall be applied:

Classified by: ___(guide)____________

Classifier: _____(name and title)_______

The following notice shall be affixed on material which contains Formerly Restricted Data. This may be abbreviated FRD.

 

FormerIy Restricted Data

Unauthorized disclosure subject to administrative and criminal sanctions. Handle as Restricted Data in foreign dissemination. Section 144b, AEA 1954.

Material classified as FRD must indicate the classification guide. The following marking shall be applied:

Classified by: _____________(guide)____________

Documents shall be marked to indicate CNWDT, Sigmas, and NNPI, as applicable.

 

Intelligence Information

 

Applicable Block: l0e (1,2)

This contract requires access to SCI. The assistant Chief of Staff for Intelligence, USAF, has exclusive security responsibility for all Sensitive Compartmented Information (SCI) classified material released to or developed under this contract this information must be maintained in an SCI facility (SCIF). DIA Manual 50-5, DoD S-5105.21-M-1, and the USAFINTEL (US AFINTEL 201-1) services provide the necessary guidance for physical, personnel, and information security measures and are part of the security specification for this contract. Contractor compliance with these directives is mandatory unless specifically waived. Inquiries pertaining to classification guidance for SCI will be directed to the Contract Monitor.

The following documents with subsequent revision or changes will be used for specific security classification guidance on this contract: USAFINTEL 201-1, 201-4, 201-9, DoD NISPOM, and all other security guidance listed in Block 13.

No contractor personnel will be granted access to SCI information/material under this contract unless they are filling an SCI billet assigned under the contract. The Contract Special Security Officer (CSSO) will coordinate with the Special Project Office Contract Monitor to ensure billets are requested. The names of contractor personnel requiring accessing to SCI will be submitted to SMC/INS through the Contract Monitor (forms required for a Special Background Investigation will be prepared in accordance with the NISPOM;). Upon receipt of a completed background investigation from DISCO, the CSSO will submit a request for SCI eligibility to SMC/INS in accordance with the NISPOM. Multiple contract employees sponsored by other than SMC/INS should be certified to SMC/INS for placement in an SMC/INS billet.

The contractor will establish and maintain a current access list of SCI personnel on this contract. A copy of this list will be provided to the Contract Monitor annually, or as changes occur. The contractor will also advise the Contract Monitor immediately upon the reassignment of personnel to duties not associated with this contract, to include termination.

SCI furnished in support of this contract remains the property of the DoD Department, Agency, or command releasing it. The contractor will maintain an active accountability of all SCI material received, produced, maintained, and disposed of that is in his/her custody, regardless of whether the material is within a contractor or US Government SCI facility. Upon completion or cancellation of this contract, SCI data will be returned to the custody of SMC/INS unless a follow-on contract specifies that material will be transferred to a subsequent contract. Inventories of SCI material will be conducted in accordance with USAFINTEL 201-1, DIAM 50-5, and DOD S-5105.21-M-l

SCI data furnished to or generated by the contractor will require security handling and controls beyond those in the NISPOM. These supplemental instructions will be furnished and/or made available to the contractor through the Contract Monitor by the User Agency Special Security Office (SMCIINS). Release of Information: SCI with restrictive caveats will be released to contractors only when originator approval has been obtained. The contractor may release such material to any contractor employee working against a billet under this contract and only when a need-to-know exists. The contractor may release such material to any Special Security Office personnel assigned to HQ SMC, HQ Air Force Material Command (AFMC), HQ USAF, or DIA upon demand by such personnel. The contractor will not release this material to other contractor, subcontractor, or Federal Government agency employees unless prior written approval has been granted by the Joint Program Office Contract Monitor. An access certification to an SMC contractor occupied SCIF does not constitute approval to release SMC contractual material to other contractor, subcontractor, or federal government employees: Contract Monitor approval is required. SCI will not be released to non-U.S. citizens (regardless of the level of their security clearance) except with written approval of the originating organization and the Contract Monitor. Contract Monitor approval of an SMC contractor visit certification or permanent certification to another facility will constitute approval to discuss contractual information/material at the facility to be visited.

The contractor may reproduce any SCI related to this contract at the discretion of the Contract Special Security Officer (CSSO), as long as the copies are controlled in the same way as the originals and they remain in the SCIF. No copies of SCI documents will be transferred to other contractors.

A SCIF will be established and maintained by the contractor. The contractor is required to comply with the physical security standards as defined in DCID 1/21, and USAFINTEL 201-1. SCI material released to the contractor under this contract will be stored and worked on only within the proposed facility and upon receipt of an approved physical security accreditation by AFISA/INSCT or Air Force Material Command. AFMC-sponsored SCIF shall not be co-utilized with other government agencies unless covered by an approved co-utilization agreement (CUA). The User Agency SSO is SMC/INS, Los Angeles AFB, CA.

The contractor will comply with the security provisions of DIAM 50-4, 50-5, DOD S5105.2l-M-l, and the SCIF customers BMSEC requirements using the attached as a guide.

This contract requires the use of the Defense Courier Service (DCS). The CSSO will prepare and submit DCS Form 10 in original triplicate to SSO SMC/INS for validation prior to their submittal to the appropriate DCS station (reference to Block 1 1k).

 

A CSSO must coordinate with the Contract Monitor and obtain the concurrence of SMC/INS prior to subcontracting any portion of SCI efforts involved in this contract.

The contractor will nominate a CSSO to SMCIINS. In turn, nomination(s) will be forwarded to MQ AFMC for appointment.

The contractor will not make references to the level of SCI accesses held, even by unclassified acronyms, in advertising, promotional efforts, or recruitment for employees.

The following activity is designated as the User Agency SSO for SCI requirements in accordance with USAFINTEL 201-I, DOD S-5105.21-M-l, and DIA Manual 50-5:

SMC/INS (SMC SSO)

180 Skynet Street

El Segundo, CA 90245-4690

The User Agency Special Security Officer (SSO) is:

JOHN Q. PETIT, GS-13

SMC/INS

(310) 363-0175

The Contract Monitor is

CHARLES L. GREENWELL, GS-12

SMC/MTES

(310) 3630395

 

FOR OFFICIAL USE ONLY (FOUO) HANDLING INSTRUCTIONS

Applicable block: l0J

 

For OFFICIAL USE ONLY (FOUO) Explained.

FOUO information is not classified according to Executive Order, but is exempt from disclosure to the public under exemptions 2 through 9 of the FOIA. Do not consider or mark any other records FOUO. FOUO is not authorized as a form of classification to protect national security Interests.

Prior FOUO Application.

A FOUO marking is not a conclusive basis for withholding a record under the FOIA. When such

a record is requested, evaluate the information in it to determine if FOIA exemptions apply and

whether a discretionary release is appropriate.

Time to Mark Records.

Marking records when they are created gives notice of FOUO content but does not eliminate the need to review a record requested under the FOIA. Examine records with and without markings before release to identify information that needs continued protection and qualifies as exempt from public release.

Distribution Statement.

Information in a technical document that requires a distribution statement according to AFI 61-204 must show that statement. The originator may also apply the FOUO marking, as appropriate.

How to Apply FOUO Markings:

Mark an unclassified document containing FOUO information "FOR OFFICIAL USE ONLY" at the bottom, on the outside of the front cover (if any), on each page containing FOUO information, on the back page, and on the outside of the back cover (if any).

In unclassified documents, note that the originator may also mark individual paragraphs that contain FOUO information to alert the users and assist in the review process.

 

Mark an individual paragraph in a classified document that contains FOUO information, but no classified information, by placing "(FOUO)" at the beginning of the paragraph.

Mark an individual page in a classified document that has both FOUO and classified information at the top and bottom with the highest security classification of information on that page.

Mark an individual page in a classified document that has FOUO information, but no classified information, "FOR OFFICIAL USE ONLY" at the bottom of the page.

If a classified document also contains FOUO information, or, if the classified material becomes FOUO when declassified, place the following statement on the bottom of the cover or the first page. under the classification marking. If declassified, review the document to make sure material is not FOUO and not exempt under FOIA before public release.

Mark other records, such as computer printouts, photographs, films, tape, or slides, "FOR OFFICIAL USE ONLY" or "FOUO" in a way that ensures the recipient or viewer knows the record contains FOUO Information.

For FOUO material sent outside the DoD to authorized recipients, place an expanded marking to explain its meaning. Do this by typing or stamping the following statement on the document before transfer:

This document contains information EXEMPT FROM MANDATORY DISCLOSURE UNDER THE FOJA. Exemption(s) applies (apply). (Further distribution is prohibited without the approval of (enter OPR)).

Procedures for Releasing, Disseminating, and Transmitting FOUO Material.

FOUO information may be sent within DoD components and between officials of DoD components and authorized DoD contractors, consultants, and grantees to conduct official business for the DoD. Inform recipients of the status of such information, and send the material in a way that prevents unauthorized public disclosure. Make sure documents that transmit FOUO material call attention to any FOUO attachments. Normally, FOUO records may be sent over facsimile equipment. To preclude unauthorized disclosure, consider such factors as attaching special cover sheets, location of sending and receiving machines, and availability of authorized personnel to receive the FOUO information. FOUO information may be passed to officials in other departments and agencies of the executive and judicial branches to fulfill a government function. Mark the records "FOR OFFICIAL USE ONLY," and tell the recipient the information is exempt from public disclosure under the FOIA and if special handling instructions apply.

 

Sending FOUO Information by United States Postal Service.

Send records containing FOUO information in a way that will not disclose their contents. When not mixed with classified information, individuals may send FOUO information by First Class Mail or Parcel Post. Bulky shipments, such as distribution of FOUO directives or testing materials, that otherwise qualify' under postal regulations, may be sent by Fourth-Class Mail.

Electrically Transmitted Messages.

Mark each part of an electrically transmitted message that contains FOUO information. Unclassified messages containing FOUO information must show the abbreviation "FOUO" before the beginning of the text.

Safeguarding FOUO Information,

During Duty Hours. During normal duty hours, place FOUO records in an out-of-sight location, if the work area is open to non-government people.

During Non-duty Hours. At the close of business, store FOUO records to prevent unauthorized access. File such material with other unclassified records in unlocked files or desks, etc., when the Government or a Government contractor provides normal internal building security during non-duty hours. When there is no such internal security, locked buildings or rooms usually provide adequate after hours protection. If you desire additional protection, store FOUO material in locked containers, such as file cabinets, desks, or bookcases.

The Termination, Disposal, and Unauthorized Disclosure of FOUO:

Terminating FOUO Material. The originator or other component authority should remove FOUO markings or indicate on the document the markings no longer apply when circumstances show that the information no longer needs protection from public disclosure. When a record is no longer FOUO, tell all known holders, to the extent practical. Do not retrieve records in files or storage only for that purpose.

Disposing of FOUO Material. Destroy FOUO materials by shredding, in any type shredder, to preclude reconstruction.

 

Unauthorized Disclosure. The unauthorized disclosure of FOUO records is not an unauthorized disclosure of classified information. However, Air Force and DoD contractor personnel have a duty to take reasonable actions to protect FOUO records under their control from unauthorized disclosure. Appropriate administrative actions should be taken to fix responsibility for such disclosures and disciplinary action taken where appropriate. Unauthorized disclosure of FOUO information protected by the Privacy' Act (PA) may also result in civil or criminal sanctions against individuals or against the Air Force. Tell the originating organization about an unauthorized disclosure of its records.

Unclassified Controlled Nuclear Information (UCNI).

UCNI is sensitive unclassified information subject to special handling as outlined in DoD Directive 5210.83. The likelihood of your company coming in contact with UCNJ is remote. However, if the situation does arise, employees will protect the information in the same manner as FOUO information, contact the company Security Office who, in turn, will obtain guidance from its cognizant Security Office.

 

EMSEC REQUIREMENTS

EMISSIONS SECURITY ASSESSMENT REQUEST (EASR)

FOR ALL CLASSIFIED SYSTEMS

 

The information on the following pages are EMSEC requirements that must be complied with by government contractors before the processing of classified data can begin. These are the minimum requirements established for the processing of DoD SECRET information. The processing of higher than DoD SECRET call for more stringent requirements.

DD Form 254-F

(1) The contractor shall ensure that emission security (EMSEC) conditions related to this contract are minimized.

(2) The contractor shall provide countermeasures assessment data to the Contracting Officer as an ESAR. The ESAR shall provide only specific responses to the data required in paragraph 3 below. The contractor's standard security plan is unacceptable a "stand alone" ESAR response. The contractor shall NOT submit a detailed facility analysis/assessment. The ESAR information will be used to complete an EMSEC Countermeasures Assessment Review' of the contractor's facility to be performed by the government EMSEC authority using current Air Force EMSEC directives.

(3) When any of the information required in paragraph 4 below changes (such as location or classification level), the contractor shall notify the contracting officer of the changes, so a new EMSEC Countermeasures Assessment Review is accomplished. The contractor shall submit to the Program management Office a new ESAR. The new ESAR will identify the new configuration, a minimum of 30 days before beginning the changes(s). The contractor shall not commence classified processing in the new configuration until receiving approval to do so from the contracting officer.

(a) SYSTEM DESCRIPTION:

I. SYSTEM/FACWITY: Provide full name and address of company submitting request and RFP/contract number and duration. Also, provide a brief title identifying the overall system or facility (e.g., XYZ Missile word processing system, ABC aircraft interactive graphics system, etc.)

2. LOCATION: Identify the system or facility's location and address (including city, state, zip code, facility, building, and room number). Further, identify any other contractor/company/agency located within 200 meters of the facility (building, room, or office where classified process is taking place). Also, identify the Inspectable Space (IS), see below.

3. Additional information may be needed for TOP SECRET or SECRET level with Special Access Required (SAR), Special Category (SPECAT) information or other non-collateral caveats processing and access to classified information outside the continental United States (OCONUS) (Block 11c and 1, if checked): identify the Controlled Access Area (CAA), see below.

The three-dimensional space surrounding equipment that process classified or sensitive information within which EMSEC is not considered practical or where legal authority to identify or remove a potential EMSEC exploitation exists.

The complete building or facility area under direct physical control that can include one or more limited exclusion areas, controlled BLACK equipment areas, or in any combination.

(b) RESPONSIBLE PERSONNEL:

1. SECURITY OFFICER/MANAGER: Provide name, title, office symbol, and telephone number. Include the same for the company appointed EM SEC authority, if applicable.

2. SYSTEM CUSTODIAN: If different from above, provide name, title, office symbol, and telephone number.

(c) OPERATIONAL RISK:

1. Identify the highest level of classified processing.

2. Additional information may be needed for TOP SECRET or SECRET level SAR, SPECAT information or other non-collateral caveats processing and access to classified information OCONUS (Block 11c and 11f, if checked). Further, identify classified processing levels by estimated hours per day/month for each level and a percentage of total material processed (e.g., 10% Top Secret, 55% Secret, etc.) for each level.

(d) EQUIPMENT:

1. List the manufacturer and exact model number, nomenclature (terminal, disk drive, video systems, etc.) and quantity of each piece of equipment involved in classified processing. Do not provide a complete inventory of all the company's processing equipment.

2. List any encryption equipment (i.e., STU-III, KG-84, KG-I 94, etc.;) that might be used for processing and transmission of classified information.

(4) Use of UHF/HF radios, cellular phones, pages, or other types of Resting Frequency transmitters should not be allowed in classified processing facilities/areas unless approved by the EMSEC manager.

 

EMSEC Red/Black Requirements

Countermeasure Application. These paragraphs discusses how to apply the countermeasures and under what conditions they would not be required.

Keep RED and BLACK Signal Lines Separated. Keeping RED signal lines about 6 inches away from BLACK signal lines will reduce coupling to a level low enough to prevent detection at great distances (over one mile). This separation may be reduced to two inches if the RED signal lines are shielded.

Keep RED Signal Lines Separated from BLACK Power Lines. Keeping RED signal lines about 6 inches away from BLACK power lines will reduce coupling to a level low enough to prevent detection at great distances (over one mile). This separation may be reduced to two inches if the RED signal lines are shielded.

Keep RED Processors Separated from BLACK Telephones and Telephone Lines. Keep non-EMSECapproved printers at least 6 feet away from telephones. Do not use the telephone while printing classified information. Keep all non-EMSEC-approved equipment at least 3 feet away from telephone lines; two inches if the telephone lines are shielded.

EMSEC SEPARATION MATRIX

This matrix applies to the processing of Collateral Secret Information.

BLACK

 

RED

CRYPTO EQUIPMENT

UNSHIELDED
SIGNAL AND
TELEPHONE
LINES

SHIELDED
TELEPHONE
LINES

POWER LINES

CRYPTO EQUIPMENT

0

3ft

2in

2in

UNSHIELDED SIGNAL LINES

6 in

6 in

2 in

6in

SHIELDED SIGNAL LINES

2in

2in

2in

2in

EMSEC APPROVED EQUIPMENT

2in

6in

2in

NONE

NON-EMSEC APPR. EQUIP

3 ft

3 ft

2 in

NONE

 

 

ATTACHMENT 5 - GOVERNMENT FURNISHED PROPERTY (GFP) LIST

F04701-98-R-0006

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________*

*.

 

 

ATTACHMENT 6 - GOVERNMENT FURNISHED TEST FACILITIES

F04701-98-R-0006

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________*

.

 

 

ATTACHMENT 7 - SPECIAL TOOLING AND/OR TEST EQUIPMENT

F04701-98-R-0006

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________

____________________________________________________*

 

 

 

ATTACHMENT 8 - PERFORMANCE RISK FORMS

F04701-98-R-0006

RFP F04701-98-R-0006

ATTACHMENT 8

Present/Past Performance "FACTS Sheet"

(TO BE COMPLETED BY OFFEROR)

Request the Offeror complete a separate FACTS Sheet for each relevant contract. See Clause L-2 of this RFP for detailed instructions and limits on number and recency of contracts. Offeror is requested to provide frank, concise comments regarding present/past performance on the program identified in B. below.

  1. OFFEROR: (Including: (1) Name (Company/Division), (2) Address: (3) CAGE Code)
  1. PROGRAM TITLE and CONTRACT NUMBER:
  2. NAME OF CONTRACTING ACTIVITY OR CUSTOMER:
  3. CONTRACT TYPE(S) – PLEASE LIST ALL THAT APPLY (firm fixed price, time & materials, etc.)
  4. CONTRACT $ VALUE:
    1. Original Contract $ Value:
    2. Current $ Value:
    3. Estimate @ Completion:
    4. Primary causes of changes:
    5. If an Award Fee Contract, within the last 3 years, what was the percentage of the award fee for each period?. Provide rating and accompanying rationale:

F. BRIEF DESCRIPTION OF EFFORT AS: _____ PRIME _____ SUBCONTRACTOR

(As a part of this narrative description, please highlight portions considered most relevant to the current acquisition; addressing each factor (if applicable) in the current acquisition as to how and to what extent each factor relates to the program identified in B. above. (See RFP Section M-3.0 for evaluation criteria/ factors.) PLEASE NOTE: The government is not bound by the offeror's opinion of relevancy. The government will perform an independent assessment of relevancy of the data provided or obtained.

G. PERIOD OF PERFORMANCE:

    1. Original Schedule:
    2. Current Schedule:
    3. Estimate @ Completion:
    4. How many times changed:
    5. Primary causes of changes:

H. PRIMARY POINTS OF CONTACT: (The Offeror is responsible for exerting its best efforts to ensure that current information is provided for all individuals.)

Name and Office Symbol

Phone Number

FAX Number

  1. Procuring Contracting Officer

DSN & Comm

DSN & Comm

  • Program Manager
  • DSN & Comm

    DSN & Comm

  • Administrative Contracting Officer
  • DSN & Comm

    DSN & Comm

  • Other (Please Specify)
  • DSN & Comm

    DSN & Comm

    I. Specify, by name, key individual(s) who will participate in the proposed effort under acquisition who also participated in the program identified in b. above, and indicate their contract role. Describe how participation of these key personnel contributed to the success of the previous effort and how this indicates probability of success on the proposed effort.

    J. Use this space to address any aspect of this program considered unique. Describe quality awards or certifications that indicate the Offeror possesses a high-quality process for developing and delivering the product/service required.

    K. Summarize contract issues relative to the number and severity of quality deficiencies recorded/contract discrepancy reports issued, cure notices, show cause letters, termination for default or cause, disputes, claims, latent defects; and, corrective actions taken.

    RFP F04701-98-R-0006

    ATTACHMENT 8

    NOTE TO OFFERORS: This procurement could be similar to commercial supplies/services. Therefore, to assist the Government’s Performance Risk Assessment Group (PRAG) in assessing your present and past performance on relevant commercial contracts, the following letter must be sent to your points of contact (POC’s) for those commercial efforts that you identify to us in your past performance volume. Should you propose to use critical subcontractors, teaming contractors, and/or joint venture partners, you must obtain a similar client authorization letter from each entity. HOWEVER, it is the your sole responsibility, as the Offeror, to then send out these authorization letters with the questionnaires to your own POC’s and to those of your subcontractors, teaming contractors, or joint venture partners.

    SOURCE SELECTION INFORMATION - See FAR 3.104

    SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY

    Client Authorization Letter

    (TO BE ACCOMPLISHED BY OFFEROR)*

     

    Dear (Client):

    We are currently responding to the Department of the Air Force (AF), Los Angeles Air Force Base (LAAFB), Request For Proposal (RFP) F04701-98-R-0006 for the procurement of the Space Based Infrared System (SBIRS) Low Component Program Definition.

    As you know an Offeror’s past performance has become an element of increased emphasis in the AF’s acquisitions. They are requesting that clients of companies who submit proposals in response to their RFP for the Space Based Infrared System (SBIRS) Low Component Program Definition Program be contacted, and that their participation in the validation process be requested. We, therefore, respectfully request and hereby authorize you to complete the attached Questionnaire with regards to work we have performed for you, and forward it directly to the Government Point(s) of Contact at the following address:

    HQ SMC/MTA

    ATTN: Karen Basany, Capt Stuart Mapes

    185 Discoverer Blvd, Suite 2512

    El Segundo, CA 90245-4695

    Reference: RFP: F04701-98-R-0006

    We have identified Mr./Ms. (Name) of your organization as the point of contact based on their knowledge concerning our work. Your cooperation in this matter is appreciated. Any questions may be directed to: [NAME, PHONE NUMBER, FAX NUMBER FOR THE OFFEROR’S POINT OF CONTACT]

     

     

    Sincerely,

     

     

    [OFFEROR'S POINT OF CONTACT]

     

    SOURCE SELECTION INFORMATION - See FAR 3.104

    SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY]

    RFP F04701-98-R-0006

    ATTACHMENT 8

    SOURCE SELECTION INFORMATION - See FAR 3.104

    SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY

    Past Performance Questionnaire Tracking Record

    [TO BE ACCOMPLISHED BY OFFEROR]*

    OFFEROR’S REFERENCES COMPANY/AGENCY NAME:

    REFERENCE NAME:

     

    REFERENCE ADDRESS:

     

    Date Of Action

    Type Of Action (E.G., Sent Questionnaire, Follow-Up Call)

    Person Contacted/

    Phone #

    Company Position Of Person Contacted

    Offeror Contact

    Status Of Questionnaire

    SOURCE SELECTION INFORMATION - See FAR 3.104

    SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY

    RFP F04701-98-R-0006

    ATTACHMENT 8

    Transmittal Letter to Accompany Present/Past Performance Questionnaire

    [TO BE COMPLETED BY OFFEROR*]

    SOURCE SELECTION INFORMATION - See FAR 3.104

    SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY

    MEMORANDUM FOR: [OFFEROR’S POC]

    FROM: [OFFEROR’S ADDRESS AND POINT OF CONTACT]

    SUBJECT: Present/Past Performance Questionnaire for Contract(s) .

    1. We are currently responding to the Department of the Air Force (AF), Los Angeles Air Force Base (LAAFB), Request For Proposal (RFP) F04701-98-R-0006, for the procurement of the Space Based Infrared System (SBIRS) Low Component Program Definition. This RFP is being conducted as a Source Selection and specifically requires that we, as an Offeror, do the following:

    The Offeror shall send out -- and track the completion of -- the Present/Past Performance Questionnaire to each of the Offeror’s, critical subcontractors’, teaming subcontractors’ and/or joint venture partners’ Points of Contact (POC’s). The responsibility to send out and track the completion of the Present/Past Performance Questionnaires rests solely with the Offeror - i.e., it shall not be delegated to any subcontractors, team contractors, and/or joint venture partners. The Offeror shall exert its best efforts to ensure that at least two POC’s, per relevant contract, submits a completed Present/Past Performance Questionnaire directly to the Government not later than [OFFEROR FILL-IN RFP CLOSING DATE]. Each of the Offeror’s POC’s shall telefax its completed Present/Past Performance Questionnaire directly to:

    HQ SMC/MTA

    ATTN: Karen Basany, Capt Stuart Mapes

    185 Discoverer Blvd, Suite 2512

    El Segundo, CA 90245-4695

    The LAAFB telefax number is (310) 363-6882. The POC’s must call Ms Basany, (310) 363-0217, or Capt Mapes, (310) 363-2757, before telefaxing the completed questionnaire(s). Mailing the questionnaire(s) to the address above is an acceptable alternative method of transmission. If mailing, the outside envelope must be marked as follows:

    NOTE: TO BE OPENED BY ADDRESSEE ONLY

    SOURCE SELECTION INFORMATION - See FAR 3.104

    SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY

    2. We have identified subject contract(s) as relevant to this acquisition and you as our POC. As such, please take a few moments of your time to fill out the attached questionnaire and send it directly back to LAAFB. The information contained in the completed Present/Past Performance Questionnaires are considered sensitive and can not be released to us, the Offeror. If you have any questions about the acquisition or the attached questionnaire, your questions must be directed back to the Government’s points of contact identified above. Thank you for your timely assistance.

    Sincerely,

     

    Attachment(s) [OFFEROR’S POINT OF CONTACT]

    Present/Past Performance Questionnaire

    [Client Authorization Letter(s), if applicable]

    SOURCE SELECTION INFORMATION - See FAR 3.104SOURCE SELECTION SENSITIVE - FOR OFFICIAL USE ONLY

    Space Based Infrared System (SBIRS) Low Component,

    Program Definition Studies, Initial Design

    RFP F04701-98-R-0006

    Present and Past Performance Questionnaire*

    Description of SBIRS Low Program (for reference): The SBIRS Low Component provides Low Earth Orbiting surveillance satellite constellation for acquiring and precision tracking of ballistic missiles. SBIRS Low Component will also improve capabilities for missile warning, technical intelligence, and battlespace characterization by complimenting the performance of current Space Based Infrared Systems. The SBIRS Low Component includes provisions to incorporate associated ground elements to provide any unique command, control, data processing, and external interface capability to the entire SBIRS ground segment.

     

    _____________________________________________________________________________

    POC NAME PHONE DATE

    PART A: PLEASE TELL US HOW RELEVANT YOUR PROGRAM IS TO OURS:

    1. Is/was the contractor a ____prime contractor or ____subcontractor?
    2. Did your program provide ____experimental or ____operational space system? Other?______
    3. Did the contractor provide ____satellite vehicle or ____payload(s) or ____ground system?

    Please provide a brief narrative description of your program: ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    PART B: USING THE FOLLOWING QUESTIONS BELOW, PLEASE TELL US IN A NARRATIVE RESPONSE HOW THE CONTRACTOR PERFORMED ON YOUR PROGRAM (if necessary, use continuation pages):

    1. Given the proposal as negotiated, how effective was the contractor’s cost management and performance?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    2. How well did the contractor understand requirements and perform system trades studies considering performance, life cycle costs with CAIV (Cost As Independent Variable)?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    *

    3. How well did the contractor transform system concepts into system specification and development specifications?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    4. Did the contractor demonstrate system engineering capability to define, document, manage, coordinate and control external interfaces?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    5. Did the contractor demonstrate the ability to manage large, complex tasked systems?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    6. How well did the contractor accommodate and integrate space/ground architectures?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    7. Did the contractor perform test and evaluation in a structured and integrated manner that will permit an assessment of performance specifications?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    8. Did the contractor demonstrate the capability to plan and conduct on-orbit operations of space systems—initialization, anomaly resolution and configure for mission operations?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    9. How well did the contractor transition from development to production?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

     

    *

    10. Did the contractor demonstrate the capability to handle high production rate, associated integration and test tasks?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    11. As an integral part of the organization, does the contractor have a comprehensive risk management program that is implemented throughout the life cycle of a program?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    12. How well did the contractor include subcontractors and Others (government) in their Integrated Product Teams?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    13. Did the contractor demonstrate the capability to manage subcontractors and internal (sister) organizations?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

     

    14. How well did the contractor demonstrate the capability to manage software development of a complex configuration consistent with program requirements and constraints?

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    PART C: PLEASE PROVIDE US EXAMPLES OF THE CONTRACTOR PERFORMANCE (if necessary, use continuation pages):

    1. Contractor strengths in conducting contract effort.

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    *

    2. Contractor deficiencies in conducting contract effort.

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    3. Remedial actions taken.

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

    4. Effectiveness of remedial actions

    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

     

     

    PART D: OTHER COMMENTS

     

     

    ATTACHMENT 9 - TECHNICAL DATA PROVIDED WITH RESTRICTIONS

    F04701-98-R-0006

    ____________________________________________________

    ____________________________________________________

    ____________________________________________________

    ____________________________________________________

    ____________________________________________________*

     

     

     

    ATTACHMENT 10 - COMPUTER SOFTWARE PROVIDED WITH RESTRICTIONS

    F04701-98-R-0006

    ____________________________________________________

    ____________________________________________________

    ____________________________________________________

    ____________________________________________________

    ____________________________________________________*