(CUI) HEMI PWS 5Jan23.docx
DOCX document 55 KB Posted
- Solicitation number
- FA88192023SN001
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Hemisphere Industry Day Brief (As Presented).pptx | PPTX presentation | |
| Industry Day Q-A CRM.xlsx | XLSX spreadsheet | |
| Hemisphere Industry Day Attendees.xlsx | XLSX spreadsheet | |
| DRAFT Hemisphere Industry Day Brief.pptx | PPTX presentation | |
| (CUI) Staffing Matrix 5Jan23.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SPACE SYSTEMS COMMAND
ADVISORY AND ASSISTANCE SERVICES
for Space Domain Awareness & Combat Power and Battle Management, Command, Control & Communications
HEMIsphere Highly Specialized Engineering Support for Multiple Programs and Integration
Version x.x
5 January 2023
Table of Contents
| 1. | SCOPE AND BACKGROUND | 4 |
| 1.1. | Scope Overview | 4 |
| 1.2. | Background | 4 |
| 2. | APPLICABLE DOCUMENTS | 4 |
| 2.1. | Reference Documents | 4 |
| 2.2. | Compliance Documents | 5 |
| 3. | REQUIREMENTS | 6 |
| 3.1. | General | 6 |
| 3.1.1. | Overarching Support | 6 |
| 3.1.2. | Program Management Reviews | 6 |
| 3.1.3. | Event Support | 6 |
| 3.1.4. | Monthly Status Reports | 6 |
| 3.1.5. | Contract Funds Status Reports | 6 |
| 3.1.6. | Contract Phase-Out | 7 |
| 3.1.7. | Training Personnel | 7 |
| 3.1.8. | Security | 7 |
| 3.2. | Life Cycle Acquisition and Sustainment | 8 |
| 3.2.1. | Joint Capabilities Integration Development Systems (JCIDS) Life Cycle | 8 |
| 3.2.2. | System Engineering | 8 |
| 3.2.3. | Program Management | 9 |
| 3.2.4. | Cyber Security | 9 |
| 3.2.5. | Administration and Personnel Management | 9 |
| 3.2.6. | Product Support and Logistics | 10 |
| 3.2.7. | Contracting | 10 |
| 3.2.8. | Finance | 10 |
| 3.2.9. | Integration | 10 |
| 3.2.10. | Test and Operations | 11 |
| 3.2.11. | Intelligence | 11 |
| 3.2.12. | Facilities | 12 |
| 3.2.13. | Launch | 12 |
| 3.3. | General Considerations | 12 |
| 3.3.1. | Inherently Governmental Functions | 12 |
| 3.3.2. | Physical Location | 12 |
| 3.3.3. | Badges and Access to Controlled Areas | 13 |
| 3.3.4. | Training | 13 |
| 3.3.5. | Identification | 13 |
| 3.3.6. | Supplies and Equipment | 13 |
| 3.3.7. | Non-Disclosure Agreements | 13 |
| 3.3.8. | Data Rights | 13 |
| 3.4. | Service Summary | 13 |
| 3.5. | Government Furnished Equipment/Property | 15 |
| 3.6. | Travel | 15 |
| 3.7. | Deliverables | 15 |
List of Tables
| Table 1 Reference Documents | 3 |
| Table 2 Compliance Documents | 4 |
1. SCOPE AND BACKGROUND
1.1. Scope Overview
The scope of this Performance Work Statement (PWS) is to provide Advisory and Assistance Services (A&AS) support to the Space Systems Center (SSC) Space Domain Awareness and Combat Power (SDACP) (SSC/SZ), Battle Management, Command, Control, and Communications (BMC3) (SSC/BC) programs, and their mission partners. Scope will include support for several current and future classified programs. This mission area requires personnel with experience and an in-depth understanding of the environments that include ground, near-space, space, and any system that operates in those environments. SSC/SZ-BC will work with the contractor to meet requirements through deliverable products and level-of-effort support. The tasks for this effort are described below.
1.2. Background
SSC/SZ-BC provides highly classified Space Situational Awareness (SSA) systems, Defensive and Offensive Space Control (DSC/OSC), and space test range assets to meet current and projected Department of Defense (DoD) operational requirements. Program objectives are to develop, deploy, sustain, and support operations for systems that meet strategic and tactical operational needs. SSC provides unrivaled space systems to ensure survival for both the United States Space Force and our nation. These systems span the acquisition life cycle from technology development, system development, procurement, integration, developmental and operational test and analysis, training, program protection analysis, sustainment, mission assurance, anomaly resolution, operations, and contract administrative support. This contract will support multiple SSC/SZ-BC programs, as well as various other Air Force and mission partner programs.
2. APPLICABLE DOCUMENTS
2.1. Reference Documents
All guidance, instructions, policy memorandums, and regulations associated with acquisition, operation, and sustainment of systems within SSC/SZ-BC’s mission areas, including but not limited to, are in Table 1:
| Document Name |
| Document Number |
| Document Date/Version |
| Joint Capabilities Document for Space Control 2006 |
| N/A |
| 28 July 2006 |
Initial Capabilities Document for Space Situational Awareness
| Joint Space Operations Center Mission System Capability Development Document 2010 |
| N/A |
| 21 July 2010 |
| DoD Instruction 5000.02, “Operation of the Defense Acquisition System” |
| DoDI 5000.02 |
| 7 January 2015 |
| Integrated Life Cycle Management |
| AFPAM 63-101/20-101 |
| 7 March 2013, Incorporating Change 2, 23 February 2015 |
| Capabilities-Based Test and Evaluation |
| AFI 99-103 |
| 16 October 2013 |
| Cyber Security |
| DoDI 8500.01 |
| 14 March 2014 |
| DoD SAP PM Handbook to the Joint SAP Implementation Guide (JSIG) and the Risk Management Framework (RMF) |
| JSIG |
| 11 August 2015 |
Table 1 Reference Documents
2.2. Compliance Documents
The documents listed in Table 2 are compliance documents to be used in executing this PWS. When conducting tasks associated with the listed functional areas, these documents shall be used to ensure compliance. The contractor shall also comply with the security documents as identified on the DD254 attached to the contract.
| Function |
| Document Name |
| Document Number/Date/Version |
| Program Management |
| Program and Subcontractor Management |
| SMC-S-019, Rev A (11 Aug 2008) |
| Technical Reviews and Audits on Defense Programs |
| IEEE 15288.2 (10 Dec 2014) |
| Systems Engineering |
| Systems and Software Engineering – System Life Cycle Processes |
| ISO EIA 15288 (15 May 2015) |
| Application of Systems Engineering on Defense Programs |
| IEEE 15288.1 (10 Dec 2014) |
| SMC Risk Management Supplement to IEEE 15288.1 |
| SMC-T-005 (15 May 2015) |
| Specialty Engineering Supplement to IEEE 15288.1 |
| SMC-T-006 (15 May 2015) |
| Human Systems Integration |
| Human Computer Interface Design Criteria Volume 1: User Interface Requirements |
| SMC-S-023 (19 Mar 2010) |
| Human Computer Interface Design Criteria Volume 2: Space System Operation Displays |
| SMC-S-023 (19 Mar 2010) |
| Systems Architecture |
| DoD Architecture Framework |
| DoD Arch V2 02 Vol 1-3 (Aug 2010) |
| Software |
| Software Development |
| SMC-S-012 (16 Jan 2015) |
| Marking of Government Property |
| Identification Marking of U.S. Military Property |
| MIL-STD-130N w/CHANGE I (16 Nov 2012) |
| Configuration Management |
| Configuration Management Requirements for Defense Contracts |
| SAE EIA 649-1 (Nov 2014) |
| SMC Tailoring of EIA 649-1 – ECP Change Classes |
| SMC-T-007 (15 May 2015) |
Table 2 Compliance Documents
3. REQUIREMENTS
3.1. General
3.1.1. Overarching Support
The contractor shall provide overarching Program Management and Systems Engineering support for tasks and programs associated with this contract. The contractor shall provide information technology support, security assistance, and assist the government in meeting other applicable infrastructure requirements. The contractor shall have experience working classified space acquisition programs. The contractor shall interface with the government, Federally Funded Research and Development Centers (FFRDCs), Unaffiliated Research and Development Centers (UARCs), and industry and mission partners.
3.1.2. Program Management Reviews
The contractor shall host and support Program Management Reviews (PMRs) for this contract. The contractor program manager will conduct an initial PMR within 60 calendar days from contract Authority to Proceed to review overall Program Management structure (roles/responsibilities, teaming agreements, processes, plans, etc.). Subsequent PMRs shall include cost and schedule status, manning and resource allocation status, major issues or concerns, security status (indoctrinations, DD 254s, facility actions, etc.), facility updates, and action item review at a minimum. For planning and budgeting purposes, one (1) PMR is estimated per year during the task order (TO) period of performance. PMR format and content will be developed jointly between the government and contractor program managers. The contractor shall provide tailored PMR’s for each TO awarded pursuant to customer needs. (Presentation Material, Agendas, & Minutes, CDRL A001)
3.1.3. Event Support
The contractor shall provide a written record of conferences and meetings, at the request of the government, documenting the name and location of the event, attendees, issues, related responses to issue, and decisions made in response to issues. The format of the minutes shall be in the form of those held by the company’s best practices and shall include all appropriate security markings required by the material contained in the document. Minutes will be disseminated/transmitted through the appropriate communication channels. (CDRL A001)
3.1.4. Monthly Status Reports
The contractor shall develop and deliver a Monthly Status Report (MSR) for their TO. The MSR shall include a summary of work accomplished for the reporting month and notice of any issues impacting performance. (Monthly Status Report, CDRL A002)
3.1.5. Contract Funds Status Reports
The contractor shall provide a monthly Contractor Funds Status Report (CFSR). The CFSR shall provide the current contract funding levels, obligations, burn rates, expenditures, plan vs. actuals, estimated funds run out date, and any areas of concern. (Contract Funds Status Report, CDRL A003)
3.1.6. Contract Phase-Out
The contractor shall provide a transition plan defining transition activities and a schedule that addresses all aspects and activities of transitioning from the current contract to a follow-on contract or task order and, if applicable, to a new contractor. The transition plan shall address transition milestones and timeline, and the best method to minimize the loss of support during the transition period. The contractor shall also provide transition support, to include training, to the new contractor to aid in a smooth transition. (Contract Phase-Out Plan, CDRL A004)
3.1.7. Training Personnel
The contractor shall develop and provide training for the purpose of providing on-the-job and/or classroom training to government personnel, as requested. Training will be regarding areas covered by this PWS. (Training Government Personnel, CDRL A005)
3.1.8. Security
3.1.8.1. The contractor employees shall be U. S. citizens and possess and maintain, at a minimum, a final Secret clearance at all times during the term of the contract. Secret clearances for all contractors shall be completed within 60 calendar days of the Contract Execution Date (CED). The contractor shall have sufficient personnel with clearances in place at CED to execute and manage the contract. The contractor employees supporting Sensitive Compartmented Information (SCI) efforts shall possess a final Top Secret (TS) clearance based on a current T5 investigation, have eligibility for SCI access, and be able to obtain access to SSC/SZ-BC Special Access Programs (SAP). The contract shall have critical positions filled at time of TO award (critical positions are identified in the Staffing Matrix). Depending on the position, additional security screening may also be required (e.g. polygraph examination, etc.). Removal or suspension of clearance may be grounds for immediate removal from the contract, pending the decision of the government Procuring Contract Officer (PCO) as advised by security oversight authorities.
3.1.8.2. The contractor shall comply with the requirements in the National Industrial Security Program Operating Manual (NISPOM) when submitting a request for interim clearance. Should a contractor employee fail to obtain a final Secret security clearance, the employee's authorization for unescorted entry to government-controlled areas will be revoked.
3.1.8.3. The contractor shall identify the contractor personnel security requirements to perform duties documented within this PWS and initiate the necessary personnel security paperwork either with the SAP Management Office (SAPMO) or the applicable security clearance databases (e.g. JPAS, DISS, JADE, etc.). The contractor shall also provide information about personnel in order for SSC/SZ-BC to verify current clearances and eligibility. SSC/SZ-BC will provide the contractor the applicable security classification guidance as required. Work involving access to or production of classified information will be performed at SSC/SZ-BC approved government, FFRDC, UARC, or contractor facilities. All classified material will remain under the control of the government, including disposition of the classified material at the completion of the contract. Other security instructions applicable to this contract are as determined by the Contracts Division (SSC/SZK) and the SAPMO.
3.1.8.4. The contractor shall assist in developing, staffing, and updating security classification guidance and coordinate with the intelligence community, DoD, and the security agent security staffs. The contractor shall assist in completing intelligence community facility accreditation or co-use approvals, individual program access approvals, and review contractor security program plans. Deliverables include security classification guides and all necessary supporting security documentation for the program.
3.1.8.5. The contractor shall provide security support members to the program managers to ensure both HEMIsphere contractors and program office personnel maintain their accreditation at external/temporary duty work locations. The contractor shall provide collateral and/or SAP Visit Access Requests in support of this contract and customer requirements. The contractor shall assist the program office with system security management and coordination with functional security offices.
3.2. Life Cycle Acquisition and Sustainment
3.2.1. Joint Capabilities Integration Development Systems (JCIDS) Life Cycle The contractor shall provide space operations, acquisition, and engineering expertise, technical advice, and assistance for all programs, as required, during the acquisition life cycle. The contractor shall provide draft JCIDS documentation to the applicable government program manager (e.g. Initial Capability Document, Capability Development Document, Capability Production Document, Milestone documentation, acquisition strategies, Memorandums of Agreement, Memorandums of Understanding, and Defense Acquisition Board documentation). All contractor work shall be developed using the latest applicable government guidance (e.g. MIL-STD). The contractor shall recommend acquisition process improvements based upon the latest acquisition improvement guidance. The contractor shall develop or revise, as applicable, draft JCIDS documentation and program budgetary estimates using the latest applicable government guidance, as required.
3.2.2. System Engineering
3.2.2.1. The contractor shall provide systems engineering support. The contractor shall provide support on requirements development, requirements verification planning, test and analysis, program protection, and mission assurance. The contractor shall support engineering and program acquisition efforts for advanced technology, future concept development, and integration activities. The contractor shall provide engineering expertise to program managers at technical interchange meetings, design reviews, program conferences, video teleconferences, telecons, working groups, and informational meetings. The contractor shall lead integrated product teams and working groups and establish customer and contractor interfaces. The contractor shall maintain a broad awareness and understanding of all programs and technology development efforts in execution across the applicable portfolio, as required. The contractor shall develop and deliver products, including but not limited to briefings, white papers, reports, and analysis results upon government request, and support the presentation of these products to internal and external customers. (CDRL A001)
3.2.2.2. The contractor shall identify areas of improvement, provide actionable, feasible recommendations, and execute tasks for reducing risk where appropriate. These recommendations may include technical, organizational, or programmatic changes where appropriate. The contractor shall assist in building and maintaining a government risk program, including risk identification, process definition, and detailed technical risk mitigation plans, as required by the program office.
3.2.2.3. The contractor shall review and provide input on design documentation (e.g. Technical Requirement Documents, System Requirements Documents, specifications, Interface Control Documents, capability requirements documents, Initial Capability Documents, Capability Development Documents, Capability Production Documents, enabling concepts, Analysis of Alternatives, Concept of Operations, system training plans, training material, and other technical documentation for space systems, subsystems, and related systems). The contractor shall develop draft technical requirements and specifications, translate technical requirements into work packages, and review and provide recommendations on technical proposals.
3.2.2.4. The contractor shall provide analytical and operational engineering technical expertise to support mission protection, operations, and mission data assessments. The contractor shall assist the government to resolve technical anomalies. The contractor shall develop, review, and evaluate impact analysis, audits, studies, compliance inspections, and readiness reviews.
3.2.2.5. The contractor shall develop and deliver a SME-level technical and/or programmatic status report of any individual program or of the portfolio, in coordination with the government program manager, upon request by the government. (CDRL A001)
3.2.2.6. The contractor shall provide modeling, simulation, and analysis (MS&A) and architecture development support, including definition and development of Space Protection and Space Control mission area architectures and alternatives (enterprise, mission area, and mission thread products), force packaging, and courses of action to be evaluated by various analysis efforts, and validation to determine the effectiveness of architectures and/or alternatives being evaluated. The contractor shall be proficient in MS&A tools, provide advice and assistance, and interpret results.
3.2.2.7. The contractor shall support program management of robust software planning and development for a spiral/agile acquisition program.
3.2.2.8. The contractor shall assist in maintaining a System Safety program, as required, in accordance with appropriate DoD safety instructions and guidance.
3.2.3. Program Management
3.2.3.1. The contractor shall provide planning, programming, budget, and execution (PPBE) support, to include congressional reporting. The contractor shall maintain awareness of current program schedule, monitor acquisition implementation, report requirement shortfalls, and provide contract assessment based on the identified risks.
3.2.3.2. The contractor shall assist the government to execute source selections subject to FAR 9.505-4. Source selection assistance activities shall include, but are not limited to, coordinating functional meeting requests, developing source selection documentation (e.g. source selection plan, acquisition strategy, non-disclosure agreements, non-compete clauses, etc.), and reviewing and drafting proposal evaluations.
3.2.4. Cyber Security
3.2.4.1. The contractor shall provide cyber security support in accordance with DoDI 8500.01. The contractor shall provide recommendations regarding cyber activities, including techniques, packets, and mission partner responsibilities. The contractor shall understand how the 24th Air Force is structured, and how these cyber capabilities are integrated within the Program Office, as required.
3.2.4.2. The contractor shall draft and staff a program spectrum plan, as required.
3.2.5. Administration and Personnel Management
3.2.5.1. The contractor shall provide administrative assistance, office management, and personnel management to include, but not limited to, document control, configuration and data management, and folder management. The contractor shall assist with managing government civilian record keeping.
3.2.5.2. The contractor shall manage travel bookings via the Air/Space Force travel application (i.e. Defense Travel System).
3.2.5.3. The contractor shall attend and support administration (scheduling, security controls, and/or execution) of meetings and reviews. The contractor shall develop and maintain schedules using standard Microsoft Suite applications (i.e. MS Project).
3.2.6. Product Support and Logistics
3.2.6.1. The contractor shall provide technical support and programmatic assistance to the Product Support Division (SSC/SZP). This support includes systems engineering, architecture development and decision making, integrated logistics planning and execution, acquisition assistance (including contracting, finance, and scheduling activities), and overall product support, as required.
3.2.6.2. The contractor shall develop product support requirements documents to ensure product support considerations are incorporated into system acquisitions. The contractor shall develop and refine the product support requirements, which includes working with government cross-functional teams to develop accurate assumptions, capture data, and perform data analysis. The contractor shall provide guidance, as required, and conduct assessments to facilitate informed decisions on developing and maturing product support elements and adherence to statutory and regulatory directives.
3.2.6.3. The contractor shall implement and manage support functions required to field and maintain the readiness and operational capability of weapon systems, subsystems, and components. The contractor shall provide oversight of the product support functions for fielded systems.
3.2.7. Contracting
3.2.7.1. The contractor shall provide contract and subcontract management support to the Contracts Division (SSC/SZK). The contractor shall assist the government PCO and contract specialists in executing various contracting actions, to include developing requests for proposals, drafting technical evaluations, contract administration, and executing contracts. The contractor shall provide contracts guidance and determinations and technical and operational leadership for the program and business management teams. The contractor shall advise all levels of management on contractual rights and obligations, risk avoidance and mitigation, strategy, and problem solving.
3.2.8. Finance
3.2.8.1. The contractor shall provide financial management support to the Finance Division (SSC/SZF). The contractor shall understand how classified funding is distributed and how to prepare associated documentation using standard Air/Space Force financial systems (e.g. DEAMS, FM Suite, CCAR, etc.). The contractor shall provide office coordination, staffing, and monitoring to support all program funding. The contractor shall work closely with finance personnel, the contracting officer, and contracting officer’s representative or government program manager to monitor funding. The contractor shall advise and assist programs on commitments, obligations, and expenditures of funds. The contractor shall provide cost estimation and analysis, as needed. The contractor shall assist with developing internal government funding documentation and monthly financial reports. (CDRL A001)
3.2.9. Integration
3.2.9.1. The contractor shall advise and assist program managers to identify and minimize the likelihood of interface and integration problems. The contractor shall coordinate and resolve issues and facilitate team communications. Tasks shall include coordinating resolution of program issues and facilitating effective integration of requirements and efforts with other acquisition and sustainment activities. This may include internal system interface issues, as well as external interface issues with multiple government or mission partner organizations.
3.2.9.2. The contractor shall incorporate inputs from the force design, operational imperatives, combatant command integrated priority lists, and future force shaping products to deliver recommendations that enhance government planning and capability. (CDRL A001)
3.2.9.3. The contractor shall provide on-site support at manufacturing facilities, operations centers, and other contractor facilities, as required, to support the tasks in this contract.
3.2.9.4. The contractor shall provide engineering and technical expertise to support ongoing and new/advanced Command and Control (C2) efforts and the contractor shall integrate those efforts with and into the classified portfolio. The contractor shall establish a liaison between the Space C2 and Enterprise Ground Services (EGS) program offices and the SSC/SZ-BC classified program offices. Personnel supporting this effort will focus on integrated C2 solutions with Space C2 and EGS spiral increment efforts to ensure seamless integration of the classified portfolio.
3.2.10. Test and Operations
3.2.10.1. The contractor shall support test planning, events, and demonstrations. The contractor shall draft test requirements, plans, and procedures for Developmental and Operational Testing. The contractor shall evaluate test data. The contractor shall coordinate system level test integration and activities, as appropriate.
3.2.10.2. The contractor shall provide analytical and operational engineering support to current and future developmental and operational units. The contractor shall support operational bed down, training, mission planning, mission protection, anomaly engineering, and transition from acquisition.
3.2.10.3. The contractor shall provide data and signal collection, processing, storage, archiving, analysis, and lessons learned to support test, on-going operations, and future concept developments upon request. The contractor shall perform post-mission analysis and report the results of the plan versus execution. (CDRL A001)
3.2.11. Intelligence
3.2.11.1. The contractor shall develop draft intelligence requirements and staffing packages, analyze intelligence reports, translate technical program requirements into intelligence needs and requirements, and recommend courses of action to support mission-related activities. The contractor shall identify and translate vulnerabilities and deficiencies identified through intelligence products into technical requirements. The contractor shall provide threat assessment, vulnerability, and susceptibility studies and analysis, and modeling and simulation in support of mission objectives. The contractor shall coordinate with internal and external stakeholders and organizations and manage multiple schedules to deliver intelligence products.
3.2.11.2. The contractor shall prepare for threat working groups and intelligence support working groups by maintaining awareness of the current status of the applicable program(s), the current needs of the program(s), by providing the current update on action items, and by coordinating with the intelligence community to acquire necessary documents and products. The contractor shall support training programs for intelligence sensitivities and the transition of future programs to operations and sustainment.
3.2.11.3. The contractor shall utilize acquisition and intelligence community standards and processes to support the program manager in evaluating tradeoffs between cost, schedule, and performance.
3.2.12. Facilities
3.2.12.1 The contractor shall provide a laboratorial environment with direct connection to multi-level data services (including the Unified Data Library access and NSDC access) that meets SSC/SZ-BC’s overarching objectives (outlined in the Space Den’s Statement of Objectives). The contractor shall provide an accredited SAP-Facility and IT infrastructure required for the Space Den, including IT network bandwidth to access near-real time classified operational and experimental data feeds and high-performance processing.
3.2.12.2 The contractor shall provide an office workspace facility that meets program requirements with a capacity of 70 personnel. The contractor shall provide a facility that meets SAP-Facility accreditation requirements. The contractor shall provide IT infrastructure capable of processing information at multiple TS//SAP and SCI security levels.
3.2.13. Launch
The contractor shall advise and assist with conceptual launch vehicle comparisons, selection recommendations, and early integration support. These tasks shall include interfacing with the Launch Systems Enterprise Directorate (SSC/ECL), assisting with new requirement definitions, and recommending changes to existing mission requirements. The contractor shall facilitate communication between SSC/ECL and other government space vehicle and/or launch system procuring agencies. The contractor shall maintain insight into launch activities to ensure mission requirements are being addressed.
3.3. General Considerations
3.3.1. Inherently Governmental Functions
IAW AFI 63-138, 2.5.10, in no event shall the contractor perform duties that are considered “inherently governmental,” including but not limited to committing or obligating the government verbally or in writing contract and contract modifications or signing any contract decision documents.
3.3.2. Physical Location
(U) All documents prepared by the contractor shall be accomplished at government and appropriate contractor locations:
Aerospace Facility (El Segundo, CA) Chantilly, VA Colorado Springs, CO Dayton, OH El Segundo, CA Peterson AFB, CO Reston, VA Schriever AFB, CO Vandenberg, CA Washington, DC Desk or work surface areas, computer equipment, LAN access, and phone service, comparable to those used by government personnel in the same general work area, will be assigned to the contractor by the government for the duration of the task.
3.3.3. Badges and Access to Controlled Areas
The contractor shall meet applicable USSF/USAF installation/base requirements for issuance of badges and access to Controlled Areas. At the Aerospace Complex, the contractor employees shall also comply with facility requirements identified in the Facility Use Agreement (FUA).
3.3.4. Training
The contractor shall be responsible for the employment, training (job specific and required for security), guidance, and supervision of personnel assigned to perform tasks under this contract. These personnel should be knowledgeable of and be able to apply the guidance found in the reference documents identified in Section 2, or as specified by the contracting officer. When applicable, contractor personnel shall attend training provided by the government, such as Defense Acquisition University (DAU) courses when commercial training is inadequate.
3.3.5. Identification
Contractor personnel, consultants, or subcontractors shall identify themselves as contractors during meetings, telephone conversations, in electronic messages, or in correspondence related to this contract.
3.3.6. Supplies and Equipment
The contractor may be required to provide supplies and support items during the execution of this contract, as directed by the contracting officer.
3.3.7. Non-Disclosure Agreements
The contractor shall be responsible for obtaining all non-disclosure agreements with all applicable corporate, supplier, and sub-tier contractors with proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this contract.
3.3.8. Data Rights
The government shall retain unlimited rights to all data and deliverables developed over the course of this contract. During the period of the contract, records, documents, and associated papers shall be available for review at any time, per government request. If the contractor cannot provide the government with unlimited data rights, the contractor shall provide rationale and grant government purpose rights in lieu of unlimited data rights.
3.4. Service Summary
| Performance Objectives |
| Performance Thresholds |
| PWS Reference |
General, Acquisition, Sustainment, & Operations Support, & Other Program Support
| Contractor provides meaningful/relevant input to programs in all phases of development. |
| Contractor provides input within allocated timeframe with no more than 10% assigned tasks more than 3 days late. |
| Contractor coordinates resolution of issues, facilitates team communication, and provides engineering expertise to program managers at all assigned system and subsystem level events. |
| Contractor meets requirements of attending assigned program-level events 95% of the time with no more than 10 major events missed per year. Contractor actively participates in meetings by providing technical insight, timely responses, and meaningful solutions. |
| Contractor drafts, reviews, and advises the government regarding design documents, requirements documents, contracts documents, enabling concepts, concepts of operations, system training plans, training material, test requirements, work specifications, and other technical documentation, as requested to execute the assigned programs. |
| Contractor provides input within allotted timeframe with no more than 10% assigned tasks more than 3 days late. |
| Contractor provides engineering expertise via briefings, reports, and informational analyses as needed. |
| Contractor provides input within allotted timeframe with no more than 10% assigned tasks more than 3 days late. |
Business Relations
| Comply with applicable security requirements |
| No more than 2 verified Classified Message Incident (CMI) security violations per year. |
Deliverable Reports
| Timely delivery of required reports and CDRLs |
| Contractor provides reports and CDRLs within allotted time with 0 late submissions. |
Personnel
| Personnel possess required security clearances. |
| 100% of contractor personnel possess and maintain required security clearance (Secret up to TS/SCI) and complete 100% annual security training. |
| Provide qualified personnel in a timely manner. |
| New or replacement personnel are identified within 30 days and are in place within 5 days of program clearances being administered. Temporary replacements with appropriate clearances and qualifications are in place within 10 working days of vacancy. |
3.5. Government Furnished Equipment/Property
The government shall provide workspace, computers, telephones, and voicemail service connectivity in the facilities for contractor personnel performing work under this contract at El Segundo, CA; Schriever AFB, CO; Vandenberg SFB, CA; Wright-Patterson AFB, OH. The contractor shall pay infrastructure costs to the Aerospace Corporation as required for office space use. These costs will be charged to a cost reimbursable contract CLIN.
3.6. Travel
This contract covers activities and responsibilities executed by SSC/SZ-BC and their mission partners at various CONUS locations. The contractor may be required to travel for temporary duty (TDY) to other government and contractor sites in CONUS and OCONUS locations in support of programs. In the case of OCONUS travel, all contractor personnel shall have a valid passport. Travel requirements will be determined and approved by the government in advance. The duration of all trips will be 3-5 days or as directed. Travel costs will be reimbursed as provided in the Joint Travel Regulations (JTR).
3.7. Deliverables
| Number |
| Title |
| Frequency |
| Date |
| A001 |
| Presentation Material, Agendas, Minutes |
| As required |
| A002 |
| Monthly Status Report |
| Monthly |
| 10 working days after end of fiscal month |
| A003 |
| Contract Funds Status Report |
| Monthly |
| 10 working days after end of fiscal month |
| A004 |
| Contract Phase-Out Transition Plan |
| 90 days prior to end of contract |
| A005 |
| Training Government Personnel |
| As required |
File details come from the government source that posted it. Updated .