Draft LOSC PWS.pdf

Performance Work Statement (PWS) For

Launch Operations Support Contract

(LOSC)

Contract # TBD

Space Launch Delta 30 – Vandenberg Space Force

Base (VSFB), CA

1/14/26

Contract FA4610-2X-D-00XX

Performance Work Statement (PWS) Launch Operations Support Contract (LOSC)

Attachment 1

Launch Operations Support Contract (LOSC)

1. Program Introduction

1.1. Introduction. Vandenberg Space Force Base (VSFB), home of Space Launch Delta 30 (SLD 30), plays a vital role in the execution of national defense priorities as both the focal point for the nation’s Western Range (WR) and as a host installation supporting a number of defense, civil and commercial organizations. VSFB's success in providing assured access to space and supporting test activities and tenant operations relies on the proper functioning of its facilities and infrastructure. These resources enable personnel and assets to deliver the capabilities needed for successful operations and test activities. LOSC is key to ensuring facility and infrastructure readiness for these missions. As such, LOSC requires an effective, customer-focused, responsive, and reliable service model with an emphasis on preventative and predictive maintenance.

Furthermore, due to increased operational activity, a changing defense landscape, and the modernization of base support processes, LOSC also needs a flexible and innovative business approach.

1.2. Scope. LOSC is a non-personal services contract providing maintenance, repair, modification, and modernization for facilities, property, and equipment at VFSB and associated geographically-separated sites to ensure successful performance of operations and test activities.

1.2.1. The Contractor is responsible to provide all personnel, equipment, tools, materials, supervision, training, processes, other items and services necessary to meet all contract requirements.

1.2.2. The Contractor is responsible for planning and executing all preventive and corrective maintenance and repair to facilities and systems necessary to achieve the greatest operational availability for mission success. Planning includes the prioritization of these efforts within the available funding based on mission requirements, personnel and hardware safety, life-cycle costs, and performance improvements.

1.2.3. The scope of property and equipment (P&E) covered by this contract includes Building Equipment (BE), Real Property (RP), Real Property Installed Equipment (RPIE) facilities, and facility infrastructure.

Henceforth, P&E will be used in the PWS as a general term for all assets covered in the above categories and listed in the Appendix I, Property and Equipment Responsibility List.

1.2.4. Facility infrastructure is defined as RP that supports facility operations and use. These items include, but are not limited to, water and gas mains, roads and parking areas, power production and electrical distribution, heating, cooling, ventilation, internal and external ladders, waste systems, and roofing.

1.3. Overview. LOSC is an Indefinite Delivery Indefinite Quantity (IDIQ) contract. Services within this PWS will only be performed if ordered under a fully executed Task Order (TO). TOs may be issued by individual Contract Line Item Number (CLIN) (e.g. Cost Plus Fixed Fee [CPFF] CLINs) or a combination of like CLINs (e.g.

Firm Fixed Price [FFP] CLINs) as reasonably possible, on an annual or as-needed basis for routine tasks.

Maintenance and repair services will be provided under FFP CLINs for SLD 30 and tenant organizations on the facilities listed in Appendix I, Property and Equipment Responsibility List. Sustainment, modification and modernization projects will be accomplished under a CPFF CLIN. Typically, these projects will be accomplished for facilities listed in Appendix I, Property and Equipment Responsibility List, but can include additional facilities on a case-by-case basis.

1.4. Period of Performance.

The expected period of performance is as follows:

• Phase-in Period (3-months): 1 Jan 2028 through 31 Mar 2028

• Base Ordering Period (12 months): 1 Apr 2028 through 31 Mar 2029

Launch Operations Support Contract (LOSC)

• Option Period 1 (12 months): 1 Apr 2029 through 31 Mar 2030

• Option Period 2 (12 months): 1 Apr 2030 through 31 Mar 2031

• Option Period 3 (12 months): 1 Apr 2031 through 31 Mar 2032

• Option Period 4 (12 months): 1 Apr 2032 through 31 Mar 2033

• Option Period 5 (12 months): 1 Apr 2033 through 31 Mar 2034

• Option Period 6 (12 months): 1 Apr 2034 through 31 Mar 2035

• Option Period 7 (12 months): 1 Apr 2035 through 31 Mar 2036

• Option Period 8 (12 months): 1 Apr 2036 through 31 Mar 2037

• Option Period 9 (12 months): 1 Apr 2037 through 31 Mar 2038

• Option Period (6-months): 1 Apr 2038 through 30 Sep 2038 (if Government elects to exercise option IAW 52.217-9)

1.5. Performance Location. Performance locations include:

• Vandenberg Space Force Base

• Pillar Point Air Force Station

• Oak Mountain

• Santa Ynez Peak

Should the Government require additional place(s) of performance, the Government and Contractor will work together to determine a reasonable solution to accommodate the additional place(s) of performance.

1.6. Government Team.

1.6.1. Program Management Team. Program Manager (PM) refers to the SLD 30/PM program management team assigned responsibility for LOSC.

1.6.2. Contracting Team. Contracting Officer (CO) refers to the 30 CONS contracting team assigned responsibility for LOSC.

1.6.3. Contracting Officer Representatives (CORs). CORs monitor collectively all technical aspects of the contract and assist in contract administration. The CORs are authorized to perform the following functions: ensure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements (including Government drawings, designs, specifications);

monitor Contractor's performance and notify the PM, CO, and Contractor of any deficiencies; and coordinate availability of government furnished property. The designated CORs will be identified to the Contractor by separate letter from the CO stating the responsibilities and limitations of each COR, especially with regard to changes in cost or price, estimates or changes in delivery and/or completion dates. The COR is not authorized to change any of the terms and conditions of the contract. Each COR’s area of responsibility will be specific and cited in the COR’s designation letter.

Launch Operations Support Contract (LOSC)

2. Program Management

The Contractor shall:

2.1. General Program Management. Provide all qualified personnel, equipment, tools, materials, supervision, training, processes, other items and services necessary to meet all contract requirements. Ensure that supplied resources comply with all applicable regulatory and certification requirements.

2.1.1. Use of Updated Publications. Reference the latest version or replacement for all publications and documentation identified in Appendix D, Mandatory and Advisory Publications. Notify the PM and CO within 60 days if there are questions, concerns, or costs involved in complying with the updated versions or replacements. Provide the CO with justification if the Contractor believes compliance with the new mandatory publications and documents is not possible.

2.1.2. Use of Updated Information Systems. Perform all PWS requirements using the latest versions or replacements of Government information systems when those systems have been previously directed for use. Notify the PM and CO within 60 days if there are questions, concerns, or costs involved in meeting PWS requirements with the updated or replacement systems. Provide the CO with justification if the Contractor believes meeting PWS requirements with the new or updated systems is not possible.

2.1.3. Management Plan. Develop, execute and update a risk-based Program Management Plan (PMP) that details the contractor's plan to provide responsive, flexible, integrated and customer-focused services in support of the Space Force mission and is based on priorities set by the contractor with close coordination and input from SLD 30. (CDRL A009, Program Management Plan)

2.1.4. Pre-work Coordination. Coordinate any activity that may impact operations with the user(s) of the facility and equipment in advance so that impacts can be assessed and mitigated as required. Coordinate any activity that may impact range systems through the Maintenance Operations Coordination Center (MOCC). Do not proceed without approval from user(s) and, if applicable, the MOCC.

2.1.5. Personnel. Provide employees that meet all certification, licensing, experience, and training requirements listed in the PWS and associated compliance documents. Provide employees with, at a minimum, SECRET clearance eligibility. (Note: Access to the Local Area Network (LAN) and restricted areas will be granted only to those contractors with a favorable Tier 1 investigation.)

2.1.5.1. Training. At beginning and throughout contract execution contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Ensure applicable personnel are properly trained and certified as required by Occupational Safety and Health Administration (OSHA) and Environmental Protection Agency (EPA) regulations and federal, state and local environmental laws, regulations and rules. Training and associated costs for the training is the responsibility of the Contractor unless otherwise specified within the contract or approved by the Government prior to costs being incurred. Have annual and periodic training certifications of all employees readily available for Government inspection documentation.

2.1.5.2. Required Positions. Upon contract award, designate a Program Manager with full authority to act for the contractor on all matters relating to the contract, committing resources, coordinating contract activities and providing technical support to the Government.

2.1.5.3. Identification of Contractor Personnel. Require all contractor personnel and subcontractors to identify their company affiliation:

Launch Operations Support Contract (LOSC)

• When conversing face-to-face and over the telephone with Government personnel or in situations where the contractors could be misconstrued as Government personnel

• In electronic mail signature blocks

• On all documents or reports produced by contractor

• On any attendance sheet or any coordination documents they review

• In work-space areas where collocated space with their Government program customers, where practical

2.1.5.4. Contractor Emergency Reporting/Accountability. Report the status of their employees to the PM within one (1) hour of being notified of exercises and Real-World, time-sensitive events directing accountability of personnel.

2.1.5.5. Report Deaths. Report to the PM within one business day the (i) death or injury of any personnel potentially related to work under this contract, (ii) any death or serious injury to personnel while on government property or on official business travel, or (iii) actions by personnel that might expose USSF to adverse publicity.

2.1.5.6. Take Action on Threats. Take immediate action when an employee is identified as a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its population. Notify security forces as soon as possible. Notify the PM, CO, and COR within an hour during business hours or the first hour of the next business day.

2.1.6. Customer Relations. Establish and maintain open lines of communication with the PM, CO, and other technical points of contact at all levels. Provide clear visibility into schedules, technical performance, and risk. Participate as a team member in working issues, devising solutions to problems, and developing future plans.

2.1.7. Work Area Closures. Observe all work-area closures as directed for mission launches or hazardous operations at no added cost to the Government and schedule activities around all scheduled closures.

2.1.8. Hours/Days of Operation. Provide support primarily during Core Business Hours. Align management and business operations duty hours to coincide with SLD 30 normal duty hours, 0730 to 1630, Monday through Friday, excluding the legal public holidays listed in Table 1.

Table 1: Legal US Public Holidays

Holidays New Year’s Day, January 1 Labor Day, First Monday of September Martin Luther King Jr.’s Birthday, third Monday of January

Columbus Day, Second Monday of October

Presidents Day, third Monday of February Veterans Day, November 11 Memorial Day, last Monday of May Thanksgiving Day, fourth Thursday of

November Juneteenth, June 19 Christmas Day, December 25 Independence Day, July 4

2.1.8.1. Adjusted Hours of Operation. Schedule personnel outside of normal hours and on holidays as needed to meet mission requirements (e.g. support launch and scheduled operations). Establish management controls to minimize the use of overtime and keep personnel fit for duty when working

Launch Operations Support Contract (LOSC) outside normal hours of operation or extended business days, such that the non-standard schedules or additional hours do not increase mission or personal risk. Ensure availability of personnel to fulfill response times specified in this PWS.

2.1.8.2. Mission Essential Services. Respond to emergency situations outside of normal duty hours that have not been earlier identified. The Delta Commander on behalf of the Government may request emergency services for accidents, rescue operations, civil disturbances, natural disasters, and contingency operations, etc. During Crisis declared by the Government, perform mission essential services (DFAR 252.237-7023 Continuation of Essential contractor Services). Mission essential personnel and crisis response will be based on the type and location of crisis. Surge to full-time operation (24 hours per day, seven days per week) during wartime and other emergencies as requested by the PM and directed by the CO.

2.1.9. Exercises, Checklists and Inspections. Take part in all higher headquarters-directed, Delta and installation exercises and inspections (e.g., shelter in place, fire drills, emergency response, active shooter, Range Operational Readiness Inspections (ORIs), Unit Compliance Inspections (UCIs), Guardian Challenge Exercises, TEMPEST, cyber, environmental inspections) to the extent such participation does not put an operation at risk, cause an operational delay or failure, or cause a potential for a security risk, unless exempted by the PM or CO.

2.1.10. Public Release of Information. Avoid release, publication or disclosure of any information, verbal, written, electronic, or visual, concerning any aspect of this contract, its performance, or any related activity taking place on Government installations without prior written approval of the CO.

2.1.11. Program Management Review (PMR). Schedule, coordinate, and execute quarterly PMRs (CDRL A028, Program Management Review). Provide briefing charts to the Government 48 hours in advance of the meeting.

2.1.12. Meeting Support

2.1.12.1. Participate in a Multi-functional Team (MFT) meeting with the PM and stakeholders monthly for program status discussions and issue resolution. Present the status of work performed, pending TOs, cost of work performed (for cost CLINs), risks, issues, recommendations, etc.

2.1.12.2. Schedule and conduct Technical Interchange Meetings (TIMs), as required, to clarify requirements and resolve risks and issues.

2.1.12.3. Participate in meetings as requested by the Government to understand work requirements, obtain and provide scheduling information, coordinate ongoing and upcoming work efforts, address issues and risks, and review financial and performance information.

2.1.12.4. Ensure that the contractor personnel needed to accomplish the intent of the meeting are properly prepared and in attendance.

2.2. Contract Management

2.2.1. Task Order Management

2.2.1.1. Generate written proposals using the procedures in Appendix H, Task Order Procedures, and submit the proposals to the CO and PM. (Note: The Government cannot guarantee that all requested proposals will result in an awarded task order.)

2.2.1.2. Submit proposals within five working days of request for urgent TOs and ten working days for routine TOs.

Launch Operations Support Contract (LOSC)

2.2.1.3. Urgent Task Orders. (Note: In exceptional cases during the performance of this contract, the CO may direct the Contractor to start urgent TOs by issuing an Authorization to Proceed (ATP) letter.

If the direction is provided after hours or on the weekend, a verbal ATP will be given and formalized on the next business day. The Government will issue the TO effort within 15 working days of issuance of the ATP.) Do not exceed the agreed upon labor hours or total estimated cost in the ATP letter.

2.2.1.4. Launch Support and Other Services TOs. Launch Support (PWS 5.1, CLIN X005) and Other Services TOs (PWS 4.34, CLIN X007) TOs are in-scope, un-priced work covered under the basic contract. These routine tasks are assigned by the PM and approved by the CO. TOs are individually funded and cannot exceed a 365-day period of performance except under exceptional circumstances.

2.2.1.9.1 Notify the PM in writing within 30 days when an extension to the Period of Performance is required against CLIN X005 and X007 TOs.

2.2.1.9.2 Submit a Form DD250 to the PM and COR NLT two weeks after the completion of work effort and final invoicing. Ensure the TO is not closed until the DD250 has been signed off by the Government.

2.2.2. Associate Contract Agreement (ACA). Establish and update ACAs for any portion of the contract requiring joint participation to meet the Government's requirement. Deliver a copy of each ACA to the

CO.

2.2.2.1. Associate Contractor Identification. Name the associate contractors and their relationships;

the program involved; and the relevant Government contracts of the associate contractors. Describe the associate Contractor personnel to work with by general subject matter. Specify the categories of information to be exchanged or support to be provided. Include the expiration date (or event) of the ACA. Show potential conflicts between relevant Government contracts and the ACA. Include agreements on protection of proprietary data and restrictions on employees.

2.2.2.2. Contract Requirements / Liability. Not seek relief of any contract requirements, nor any adjustments to the contract terms due to a failure to resolve a disagreement with an associate Contractor. (Note: Liability for the improper disclosure of any proprietary data contained in or referenced by any ACA shall rest with the parties to the ACA, and not the Government.)

2.3. Financial Management.

2.3.1. Cost Accounting System. Utilize a financial accounting system that meets generally accepted accounting principles and complies with cost charging and reporting per DoD Financial Management Regulation (FMR) 7000.14-R Vol. 11a, Chapters 12 and 13 and DoD Instruction 3200.18. Ensure the system meets the requirements of applicable Federal, State, and other jurisdictions; the accounting system adequacy standards of the Defense Contract Auditing Agency (DCAA), and the requirements of the Federal Acquisition Regulations (FAR). Ensure the system identifies, tracks, and reports all costs by hours, dollars, Job Order Number (JON), Contractor Work Breakdown Structure (CWBS), and customer’s identifications. Ensure the system is fully capable of recording costs associated with multiple Government funding lines of accounting (LOA) to include invoicing different LOAs through Wide Area Work Flow.

2.3.2. Cost Accounting. Ensure all costs are burdened with overhead, General and Administrative expenses (G&A), fee and any other cost to the contractor, as applicable in PWS paragraphs 2.3.4and 7, for each reporting period.

Launch Operations Support Contract (LOSC)

2.3.2.1. Define the final cost objective as the JON. Additionally, associate all costs to the correct level within the PWS. (Note: JONs may be assigned to specific programs, projects, events, and/or fund sources. Accuracy of cost reporting to the correct JON and Government-funding year is critical.)

2.3.3. Contractor Work Breakdown Structure (CWBS). Establish and maintain a CWBS that correlates to the third level of the PWS. (CDRL A029, Contractor Work Breakdown Structure).

2.3.4. Task Order Fee. For Launch Support and Other Services TOs, apply approved Forward Pricing Rate Agreement labor rates and a fixed fee of xx% of the proposed estimated cost on fully burdened labor, materials, subcontractors and G&A only. (Note: Launch Support and Other Services TOs will be CPFF. The estimated cost and fixed fee amount on CLINs X005 and X007 of the IDIQ contract are based historical costs and were estimated at time of award. Estimated contract requirements do not represent or a guarantee or warranty and variances between estimated requirements and awarded task orders will not result in liability on the part of the government. The Government cannot guarantee that TOs will be issued in amounts that equal the total amounts on CLINs X005 and X007 of the IDIQ.)

2.3.4.1. Not be entitled to a fixed fee that has not been awarded at the task order level.

2.3.5. Payment for Completed Work. For partially completed work as described in the TO’s PWS, only bill for the percentage of the fee specified in the contract’s schedule equaling the percentage of the completed work. Only bill for full fee if the TO requirements were completed in full.

2.3.6. Billable Hours. Avoid holding contractor morale and recreational activities during core business hours, since these are not billable hours. Require employees to use personal time to attend Government morale and recreational activities.

2.3.7. Mass Severance Pay. Ensure that no contingency for abnormal or mass severance pay is included in the contractor’s pricing. (Note: There is no requirement in the Fair Labor Standards Act [FLSA] for severance pay. Severance pay is a matter of agreement between an employer and an employee [or the employee's representative]).

2.3.8. Rough Order of Magnitude (ROM) Estimates. Develop ROM estimates per PM request as part of assessing the initial technical, budget, and schedule feasibility of a project, service, or other contract-related activity. Provide estimates that are accurate to +/- 50% of the negotiated price and sufficient for an initial conceptual technical or service approach to inform a “Go or No-Go” decision by the customer as to whether to go ahead to the formal proposal stage or whether more discussion or more options are needed. Deliver estimates to the PM NLT than 10 WD after the request is delivered.

2.3.9. Reports. Provide the following reports:

2.3.9.1. Contract Funds Status Report (CFSR). Report cost and schedule data for all TOs monthly on a CFSR and using the same level of detail and breakout required for JOCAS II reporting and FIAR compliance (CDRL A020, Contract Funds Status Report).

2.3.9.2. Cost Performance Report (CPR). Report cost monthly for each CWBS line item (CDRL A019, Cost Performance Report).

2.3.9.3. Requisition Summary Report. Submit a summary of all purchases (e.g., rental, lease, training, travel, services, material, equipment, supplies, and Project Funds Management Record [PFMR]). (CDRL A012, Requisition Summary Report)

2.3.9.4. Reimbursement Cost Reporting. Electronically submit semi-monthly JOCAS reports (CDRL A021, Job Order Cost Accounting System II Report) with the JON as the highest reportable level and the CWBS as the lowest reported element within the JON. Burden the WBS with Cost of Money, Launch Operations Support Contract (LOSC) overhead, G&A expenses, and any other cost to the Contractor for each reporting period. Provide data that accurately reflects the correct JON and Government-funding year. Associate all costs with the correct level within the PWS with the final cost objective defined as the JON. Strictly adhere to the upload process and delivery described in the CDRL to maintain JOCAS II certification. Complete corrections and adjustments to JOCAS cost and financial data within 3 business days of COR request.

Display fiscal integrity in cost adjustments from earlier fiscal-year tasking. Report cost adjustments from earlier fiscal-year tasking with current-month transactions. Trace cost adjustments to the adjusted fiscal-year recorded balances.

2.3.9.5. Notify the PM and the CO in writing when 75% of funded contract values have been exceeded (TOs, CPFF and CR CLINs) in accordance with FAR requirements.

2.3.9.6. Respond to the Government, as requested, in support of short notice suspense requests regarding budget cut drills, analysis data, historical data, and any other financial or business-related data or analysis.

2.4. Data Management. Accurately and continuously update and maintain contract documentation and records as part of their documentation archive.

2.4.1. Computerized Maintenance Management System (CMMS). Coordinate with SLD 30/SC via the Change Control Board (CCB) for use of the CMMS on the Non-classified Internet Protocol Router network (NIPRnet).

2.4.1.1. Make the CMMS accessible to Government representatives at all times.

2.4.1.2. Only use software approved for use on the NIPRnet.

2.4.2. CDRL Data. (Note: A listing of CDRL deliverables for this PWS located in Appendix C, Contract Data Requirements List (CDRL) Deliverables. The Government reserves the right to review all data deliverables for a period of 10 business days, unless otherwise specified, prior to acceptance.) Treat a deliverable as accepted by the Government if no response is provided within the 10-day period unless the Government explicitly states otherwise in the TO.

2.4.3. Records Management System

2.4.3.1. Maintain a central data library of contract-related documentation, both electronic and hard copy that includes, but is not limited to: CDRL deliverables, certifications and reports, drawings, procedures, studies and results, non-destructive inspection (NDI) reports, radiographic film, warranties, correspondence, historical data, technical manuals, manufacturer’s instructions and recommendations, operation and test procedures, permit required records and any other data necessary or desirable to the Government and PM. Retain permit-associated records with the permitted equipment. Make documentation searchable and accessible for review by the PM and other Government representatives at all times. Only conduct database development and modifications that are non-proprietary and transfer any developed products along with associated code/documentation to the Government at the end of the contract.

2.4.3.2. As-Built Drawings. Provide new configuration, Piping & Instrumentation Diagram (P&ID), electrical, wiring diagrams or as-built drawings. Include these files in the Central Library and provide them to 30 CES for inclusion into the Civil Engineering Drawing Vault.

2.4.3.3. Operation and Maintenance Manuals. Update and maintain all operation and maintenance manuals associated with P&E. Existing manuals may be used until revised or superseded by the manufacturer. (Note: Manuals may be converted and stored in electronic media.) Turn over all

Launch Operations Support Contract (LOSC)

Page 10 of operations and maintenance manual data (hardcopy and electronic) to the 30 CES upon completion/termination of the contract.

2.4.3.4. Procedures. Maintain and/or develop operation, maintenance, test, and inspection procedures (e.g. grounding/LPS verification, Fire Alarm and Fire Suppression system verification, operation of a special piece of equipment, etc.) in the Central Library and identify them in the CMMS.

2.4.3.5. Warranties. Obtain and archive in the Central Library warranty documentation on all warranted equipment and material the contractor installs. Track full warranty information in the CMMS. Avoid any action that would void a warranty without prior PM approval. Request and oversee the execution of warranty service within the life of the contract.

2.4.3.6. Document all changes to P&E listed in Appendices X-X on an annual basis. Document P&E removed from operational status as well as any form/fit/function equipment upgrades/replacements. (CDRL A008, P&E Responsibility List)

2.4.3.7. Submit DD Forms 1354 or similar documents to the VSFB real estate office to capture transfers, changes, additions, or deletions of real property completed during the performance of this contract to ensure the posting and documentation of the total cost of a new facility or a capital improvement is in the installation’s real property database.

2.4.4. Information Technology (IT) Asset Management

2.4.4.1. Accountable Property Officer (APO) Duties. Perform APO duties for all Government-furnished equipment (GFE) IT assets per DAFMAN 17-1203, Paragraph 2.3.6. This includes those systems in the network boundary of which the Contractor has touch-maintenance responsibilities.

Provide all equipment, tools, materials, and other items and services, unless specified in this contract as GFE.

2.4.4.2. Property Custodian (PC) Duties. Perform PC duties for all Government-furnished equipment (GFE) IT assets per DAFMAN 17-1203, Paragraph 2.3.7.

2.4.4.3. Client Systems Technician (CST). Perform CST duties for all Government-furnished equipment (GFE) IT assets per DAFMAN 17-1203, Paragraph 2.3.7.

2.4.4.4. Procurement of IT Hardware Assets. Use the current approved Government system and process to obtain a quote to buy communication equipment per DAFMAN 17-1203, Paragraph 2.5.

2.4.4.5. Unit Software Management. Prior to introduction of software to NIPRNET connected assets, request a Security Impact Assessment from the Base Software License Manager. Avoid loading software until approval is received. Manage unit software per DAFMAN 17-1203 Chapter 3. Maintain and update software licenses and a software inventory for all software used by the Contractor. Make sure manufacturer licenses, warranties, and agreements on all software and hardware are current, transferable, and not voided.

2.4.4.6. Coordinate through the Equipment Control Officer (ECO) to identify accountability, transfer, and acquire disposition instructions for Government-Furnished IT systems and associated equipment.

2.4.4.7. Notify the ECO for replacements of IT equipment as required for maintenance swap-outs and maintenance trouble tickets before the equipment is removed from the account.

2.4.4.8. Require personnel accessing government computers complete the Cyber Awareness Challenge computer-based training course.

2.4.5. Cybersecurity Program Appoint an Information System Security Manager (ISSM), who also functions as the Information System Security Officer (ISSO), IAW DAFMAN 17-1304, for standalone computer

Launch Operations Support Contract (LOSC)

Page 11 of systems. Implement a cybersecurity program IAW AFI 17-101, Risk Management Framework (RMF) for Space Force Information Technology (IT) and DAFMAN 17-1301, Computer Security (COMPUSEC). The ISSM supplements the SLD 30 Cybersecurity Office (WCO) in managing and protecting assigned IT and Personal Wireless Communication Systems (PWCS) hardware. Interface with SLD 30/SC cybersecurity personnel on all cybersecurity program matters and obtain the necessary cybersecurity certification in order to maintain privileged access to the Space Force’s network system IAW DAFMAN 17-1301, Computer Security (COMPUSEC).

Comply with DoD 8500 Series instructions, Air Force Instruction (AFI) 10-701, and proper cybersecurity standards and procedures per AFI 17-130. Obtain COR approval for use of software or hardware not on the approved products list. Manage the security of Critical Program Information (CPI) and Controlled Unclassified Information (CUI) in Reference Libraries. Implement zero trust principles IAW the DoD Zero Trust Strategy and DoD Zero Trust Reference Architecture or replacements per assigned DoD Impact Levels.

2.4.6. Information System (IS) Access. Ensure that all Contractor personnel requiring use of IS devices (e.g., desktop PCs, laptops, notebooks, tablets, smartphones etc.) completes a DD From 2875, System Authorization Access Request (SAAR) and an AF Form 4394, Air Force User Agreement Statement-Notice and Consent Provision form. Ensure all users complete the Cyber Awareness Challenge course to the to gain and maintain system access.

2.5. Quality Management. Provide a quality management function for all activities performed under this PWS.

2.5.1. Quality Management System (QMS). Implement an operational QMS upon completion of the Contract Phase-in period. Maintain the QMS throughout the life of the contract. Ensure the QMS complies with AS9100D (Note: Certification is not required). Make QMS documentation and data available and accessible to the Government for review. Ensure QMS records are intact and available to the Government for the life of the contract. Include in QMS documentation, at a minimum, all procedures; processes; training and certification records; completed work orders; results of inspections and audits; nonconformance data; and corrective and preventive action records.

2.5.2. Quality Management Plan. Develop and execute a Quality Management Plan that describes how the Contractor will proactively ensure activities meet contract requirements. (CDRL A011, Quality Management Plan)

2.5.3. Corrective Actions. Provide corrective and preventive action plan with a root cause analysis within 15 business days as required by the Corrective Action Request (CAR) to COR and PM. Implement corrective and preventive action plans upon COR and PM approval. Provide a CAR closure memo to PM upon satisfactory completion of corrective and preventive actions.

2.5.4. Quality Activity Status. Provide status of quality management activities (e.g., CAR status, audit schedules, audit results, internally identified nonconformance status, results of internal QMS Management Review, etc.) to the Government. (CDRL A030, Monthly Status Report)

2.6. Property Management. Government property (GP) includes both Government-Furnished Property (GFP) and Contractor-Acquired Property (CAP). It includes material, equipment, special tooling, special test equipment, and real property. Government property does not include intellectual property and software. Manage all GP in accordance with Federal Acquisition Regulation (FAR) 52.245-1 and associated DFARS clauses.

2.6.1. Property Management System. Establish, implement, and maintain a Property Management System per FAR clauses 52.245-1 and 52.245-9, Defense Federal Acquisition Regulation Supplement (DFARS)

Launch Operations Support Contract (LOSC)

Page 12 of clauses 252.211-7003, 252.245-7003, 252.245-7005, DFARS Procedures, Guidance, and Information (PGI) 245.1, 245.4, and 245.6, DoDI 4161.02 (latest version), DoDI 5000.64 (latest version), DAFI 23-111 (latest version) and DAFMAN 17-1203 (latest version). The Contractors’ Property Management System (CPMS) shall supplement the Government-approved Accountable Property System(s) of Record (APSR). This includes but is not limited to the Wide Area Workflow (WAWF), GFP Module, Item Unique Identification (IUID) Registry, and Electronic Data Access (EDA) found in the Procurement Integrated Enterprise Environment (PIEE) and any contractually imposed requirements and sound business practices to control, use, preserve, maintain, repair, protect and preserve GFP and CAP property and all IT Asset Management (ITAM). Deliver a Property Management Plan (CDRL A031, Property Management Plan).

(Note: The Government will complete an initial review and acceptance of the GP System to decide adequacy based on the initial Property Management Plan which is required to be delivered within 90 days of contract award. The Government will conduct subsequent reviews, updates, and acceptance of the system at least annually [or more often if necessary] to ensure an effective Property Management Plan and System is in place.) Disclose any significant changes to the Property Management Plan to the Contracting Officer and Government Property Administrator prior to implementation of any changes.

2.6.1.1. Government Property (GP) Inventory Report. Deliver the GP Inventory Report on an annual basis (CDRL A002, GFP Inventory Reporting). Include in the report all GFP and CAP in the Contractor’s possession (to include subcontractors) associated to the contract. (Note: This report applies to all GP furnished by the Government or acquired, fabricated, or otherwise provided by the contractor in performance of the contract.)

2.6.1.2. Government Furnished Material (GFM) by National Stock Number (NSN) Report. Deliver the GFM by NSN Report on a quarterly basis. Order the report (required IAW DFARS PGI 245.103-73 for GFM only) first by contract number; within each contract number ordered by contract line item number (CLIN) or exhibit line item number (ELIN); within each CLIN or ELIN ordered by GFM line item. (CDRL A032, Government Furnished Material (GFM) by National Stock Number (NSN)).

2.6.1.3. Property Loss / Damage Reporting. Document the Loss, Theft, Damage, or Destruction (LTDD) of Government or User-Accountable Property in Procurement Integrated Enterprise Environment (PIEE) for reporting LTDDs. Report LTDD to the Government Property Administrator (GPA) and CO within an hour of discovery for classified and unclassified GFP, per FAR Part 52.245- 1(h), DFARS 252.245-7005 and DoD Financial Management Regulation (DoD FMR) 7000.14-R, Volume 12, Chapter 7, Financial Liability for Government Property Lost, Damaged, Destroyed, or Stolen. Submit formal LTDD reporting and all investigative and supporting documentation into PIEE within 5 business days of notification to the CO and GPA. All LTDD reports shall be processed through the GFP Module in PIEE. A request to repurchase LTDD items must be approved by the Contracting Officer prior to any repurchase.

2.6.1.4. Property Documentation, Reutilization, and Disposal. Document, Reutilize, and Dispose of GP IAW FAR 52.245-1(j) and DFARS 252.245-7005. Complete the Inventory Disposal Schedule using the Plant Clearance capability of the Government Furnished Property (GFP) Module of the Procurement Integrated Enterprise Environment.

2.6.1.5. Property Identification / Receiving Reports. Tag, label, and mark GP per DFARS 252.245- 7005. Tag and register all delivered items in the Item Unique Identification (IUID) Registry IAW FAR 52.245-1 and DFARS 252.211-7003. Submit a Material Inspection and Receiving Report as required for the delivery of CAP by using Tag, label, and mark GP per DFARS 252.245-7005. Tag and register all delivered items in the Item Unique Identification (IUID) Registry IAW FAR 52.245-1 and DFARS

Launch Operations Support Contract (LOSC)

Page 13 of

252.211-7003. Submit a Material Inspection and Receiving Report as required for the delivery of CAP by using the WAWF application in the (PIEE) e-Business Suite. GFP and delivered CAP systems, components, subcomponents, assemblies, parts, spares, special tooling, and special test equipment associated to a system shall be identified upon IUID registration and maintained within the GFP Module and Contractor’s Property Management System.

2.6.1.6. Incidental Property. Inventory items considered incidental to the place of performance (e.g., furniture, desks, chairs, office equipment, etc.) within 90 days after full contract performance start.

Establish and maintain a simple record to capture basic item identification, such as description, quantities, and building locations. (Note: The Government will not require any other inventories, other than Phase-out, of Incidental Property without a contract modification.) Account for Incidental Property. Receive pre-approval from the Government before acquisition of items considered Incidental Property. Notify the Government when Incidental Property is no longer required by the Contractor or considered beyond economical repair. (Note: The Government will provide disposition instructions.) Make sure that disposal of property is per Department of Defense Manual (DoDM) 4160.21-M and DFARS 252.245-7005, Management and Reporting of Government Property.

2.6.1.7. Procedures for Obtaining Government Fuel. Obtain QR codes for vehicles authorized to use government fuel. Request QR codes from the Vehicle Purchase Media Manager IAW DLA P-29 paragraphs 2.3 and 2.4. Acknowledge receipt of permanent QR Codes and affix codes to vehicles.

Request deactivation of QR codes no longer required. Accept responsibility for all fuel purchases made using the organization’s Customer QR Code until the purchase media is deactivated or the fuel purchase authorization with DLA Energy is deactivated or the fuel purchase authorization with DLA Energy is terminated.

2.7. Safety Management. Establish and maintain a safety program that complies with all federal, state, county, and local regulatory requirements to include applicable Department of Labor (DoL), DoW, and Air Force safety standards IAW with the terms of this contract, Space Systems Command Manual (SSCMAN) 91- 710, and state/federal Occupational Safety and Health Administration (OSHA) regulations.

2.7.1. System Safety Program Plan. Submit a System Safety Program Plan (SSPP) to the Space Launch Delta 30/Safety Assessment (SLD 30/SEA) for review and approval. (CDRL A026, System Safety Program Plan)

2.7.2. Injuries, Damage, and Close Calls. Investigate thoroughly and take proper corrective actions for injuries, damage and close calls resulting from Contractor activities.

2.7.3. Anomaly Reporting. Report anomalies including DAF property mishaps, and OSHA recordable mishaps, if a contractor is injured because of a facility or equipment issue, to SLD 30/SE. Provide a verbal report as soon as possible, and an electronic or written report to the PM, COR and SLD 30/SE within 4 hours. Provide electronic copy of report within four hours. Use proper safety procedures to make sure actions or inactions during the performance of this contract do not cause injuries to personnel or property. (CDRL A022, Accident/Incident Report)

2.7.4. Contractor Safety Inspections & Investigations. Inspect Government furnished facilities as required by 29 Code of Federal Regulations (CFR) 1925 and follow DAFI 91-202, The Department of the Air Force (DAF) Mishap Prevention Program, Para 3.13.3. Provide self-inspection results to the location’s proper Safety Office and COR. The Delta Safety Office will perform facility inspections as part of the MFT.

Appoint a qualified Safety Representative to support and go with the SLD 30/SE representatives during any inspections and investigations. Provide a response and corrective action for discrepancies discovered during Government safety inspections within 30 calendar days of receipt and provide updates every 90

Launch Operations Support Contract (LOSC)

Page 14 of days until fully resolved. Thoroughly investigate injuries, damage and close calls resulting from contractor activities and take appropriate corrective actions.

2.7.5. Provide a response and corrective action for discrepancies discovered during safety inspections within 30 days of receipt and provide updates every 180 days until fully resolved. All discrepancies shall be mitigated until properly resolved.

2.7.6. Attend the Launch Support Team brief, when directed, and be responsible for removing all non-essential LOSC personnel and equipment from the launch Impact Limit Line area, unless a waiver letter is provided to Range Pad Safety Launch Support Team Chief.

2.7.7. Attend various TIMs with the SLD 30/SEAL to address technical issues relating to pressure vessels, cranes and Lightning Protection Systems (LPS).

2.7.8. Inform the CO within 30 days if there is an increase in the costs of services exceeding $25,000 per year as a result of any safety-related compliance changes.

2.8. Security Management. Comply with VSFB security requirements imposed by the SLD 30/CC while on VSFB premises and geographically separated sites. Obtain all necessary passes, decals, badges, or other items required for access to perform contract services at VSFB. Account for all such media issued to contractor personnel and these media shall be surrendered to the 30th Security Forces Squadron (30 SFS) Pass and Registration Section upon completion or termination of the contract or upon termination of an individual’s employment with the contractor. Comply with all SLD 30 policies regarding entry to the installation, rules of the road, contingency operations compliance, and photography prohibitions.

2.8.1. Ensure all contractor personnel are briefed by the 30 CES Unit Security Manager on established security requirements and procedures.

2.8.2. Controlled and Restricted Area Escorting. Escort non-badged LOSC contractor employees or subcontractors who require access to controlled and restricted areas to perform tasks associated with LOSC requirements.

2.8.3. Security Operating Procedures. Develop written operating procedures per Department of Air Force Instruction (DAFI) SSC Supplement 31-101 Chapter 9.22.5 and 10 for security measures to include: entry and exit control; bomb threat and other emergency evacuation; training requirements; entry requirements and internal circulation control; robbery checklist; alarm systems; escort; and emergency entry. Take responsibility for personnel to whom they permit site and facility access. (CDRL A033, Security Operating Procedures).

2.8.4. Delta Anti-Terrorism/Force Protection (AT/FP) Program Support. Take part in the Delta AT/FP Program as defined in SLD 30 Plan 10-245. Adhere to instructions received from the Delta Antiterrorism Officer, Station Commanders, or higher authority.

2.8.5. Operations Security (OPSEC). Attend security and Operational Security (OPSEC) orientation under Homeland Security Presidential Directive (HSPD) Title 12. Schedule initial and annual refresher training (for all assigned contractor personnel) through the 30 CES Unit Security Manager.

Adhere to OPSEC requirements per AFI 10-701 and SLD 30 OPSEC Plans. Follow instructions received from the SLD 30 OPSEC Signature Managers, Commander, or higher authority. Appoint a primary and alternate OPSEC Coordinator. Notify the SLD 30 OPSEC Signature Managers via written communications within 90 days of full contract performance start or upon change in assignment of these representatives.

Ensure all contractor personnel complete initial OPSEC training within 90 days of assignment to the contract, and then complete annual refresher, mission, and event driven OPSEC training (as applicable).

(Note: The Contractor may contact the OPSEC Signature Manager or designated OPSEC unit

Launch Operations Support Contract (LOSC)

Page 15 of representative for annual refresher, mission, and event driven OPSEC training instructions or training materials.)

2.8.6. Main Base Access. Ensure all contractor vehicles the size of a standard bread delivery truck or larger enter through the Lompoc Gate (located at intersection of Santa Lucia Road and Pine Canyon Road) unless otherwise directed by 30 SFS. (Note: There is a vehicle check pull-off area at that gate, and the contractor will be required to submit to a vehicle search prior to gaining entry to the base. Contractor should plan and allow for delays as a result of in-place security procedures.)

2.8.7. Base Access Letter. To request base access, send a letter to the CO. Place the letter on company stationery and include: contractor’s company address and telephone number, the contract number, names of the contractor’s on-site Program Manager and contractor’s Security Manager, and their alternates, requiring access to VSFB, their social security numbers, and duty hours. Submit updated letters as changes occur. (Note: After approval, this letter will be maintained on file with Security Forces at the Visitor’s Control Center, Building 17596. Entry requirements are subject to change, without notice, due to installation and world situations.)

2.8.8. Security Manager. Upon contract award, designate, in writing to the CO, a Security Manager who shall be the contractor’s point of contact for all security matters. Within five (5) working days of contract award, ensure the contractor’s Security Manager contacts the 30 CES Unit Security Manager (in the CES compound located at 1172 Iceland Ave) for assistance in accomplishing contractor personnel security requirements.

2.8.9. Key Control. Immediately report occurrences of lost or duplicate key/keys to the CO. The Contractor is responsible for the cost of rekeying caused by loss of key/keys in their control.

2.9. Facilities Management.

2.9.1. Real Property Accountability. Manage, report, and account for RP assigned to the Contractor consistent with DAFI 32-9005. See Attachment X for assigned RP. Permit access to all Government-furnished real property for facility inspection, data collection, and maintenance.

2.9.2. Facility Manager Appointment. Appoint a Facility Manager (FM) and Alternate FM (AFM) consistent with SLD 30I 32-1001 for each assigned facility (Attachment X). Report the name and contact information for all FM and AFM, via written communication, to the 30 CES customer service center and the COR.

2.9.3. Facility Manager Roles. Perform the following functions for all assigned facilities:

2.9.3.1. Follow SLD30I 32-1001 for assistance in maintaining and upgrading Contractor facilities and support equipment designated as RP/RPIE.

2.9.3.2. Maintain key control for assigned facilities.

2.9.3.3. Act as the facility emergency management, Hurricane Condition (HURCON), fire, earthquake, and safety representatives. Post changes in Force Protection FPCON) conditions IAW SLD 30I 32- 1001. Follow COR direction for facility security. Post changes in FPCON conditions.