Draft Pono PWS_June 2026.docx

Pono Performance Work Statement Contract Number: TBD Date: 6/10/2026

Table of Contents

Research Support…………………………………………………………………………………………15

Performance Work Statement (PWS) 1 Introduction/Background The overall objective of this effort is to obtain Advisory and Assistance Services (A&AS) encompassing Professional Engineering and Management expertise necessary to ensure the Research and Development (R&D) and Operational Missions conducted at the Air Force Research Laboratory’s (AFRL’s) Air Force Maui Optical & Supercomputing (AMOS) site to support systems, research and operations with sustained reliability. Specifically, the AMOS site is acquiring strategic planning and management support that will ensure they maintain proper Research and Development technology focus, Operations & Integration with R&D projects, and execute funding for current and future Operations and R&D needs.

AFRL has identified a need for A&AS support encompassing scientific and technical strategic planning expertise, operations and maintenance support, and professional engineering and management services for space and directed energy research and development of technologies and systems. Future DoD space systems will be significantly more complex and diverse than any previously developed space system. In order to meet the needs of demand, the Information and Spectrum Warfare Directorate requires expertise and experience in intra-organizational program integration, technology transition, acquisition program interface, and warfighter implementation partnering to execute the mission.

1.1 Mission Overview

15th Space Surveillance Squadron (15 SPSS): 15 SPSS principal responsibilities are to support space and directed energy technologies. The site provides facilities and specialized optical and support equipment to enable development of directed energy technologies that support evolving tactical and strategic warfighter requirements.

The AMOS site was selected based on its ideal viewing environment as well as geographic location. The dry clean air contributes to the site’s outstanding astronomical seeing conditions. In addition, AMOS has historically supported operational Space Domain Awareness (SDA) as a “Contributing Sensor” to the Space Surveillance Network. The AMOS site includes the Maui Space Surveillance Complex (MSSC) located on the 10,000-foot summit of Haleakala Mountain in Maui, Hawaii, the Remote Maui Experiment (RME) Site on Haleakala Ranch near the Tech Park in Kihei, the Maui High Performance Supercomputing Center (MHPCC) and the main business offices in the Kihei Tech Park.

Facilities: Provides “Base Level” services typical of Military Installations including maintaining communications infrastructure and networks for facilities on site. Facilities requirements also include administration management and customer support, facility and infrastructure repair, demolition of Real Property/Real Property Installed Equipment (RP/RPIE), maintenance and support, operations (physical plant operations), grounds maintenance, refuse collection and disposal and limited architect/engineer services (planning, programming, design and construction management). The environmental management program ensures protection of human health and the local environment. Logistics support includes central shipping and receiving, property control and accountability, vehicle control, pickup and delivery, warehouse storage and other logistics support for local government personnel and mission partners working on site.

Mission Equipment Operations: Provides services to external customers such as tasking, collection, processing, and dissemination (TCPED) for operations Mission Equipment Maintenance and Sustainment: Ensures execution of comprehensive and effective maintenance strategies. Programs materiel solutions and logistical design. Ensures lifecycle sustainment, obsolescence, and upgrade planning. Ensures digital twin engineering, interfacing, and configuration control.

Upgrade/Modernization Projects & Visiting Experiments: Enables upgrades and modernizations to End of Life (EOL) infrastructure for all facilities as well as special studies, projects, and experiments sponsored by external stakeholders. Enables technology transition across acquisitions, contributing, and dedicated sensor baselines. Integration and adaptation solutions for complex technologies. Systems Engineering and Project Management expertise contributing to the value stream delivery to stakeholders.

Vanguard: The Maui’s Computing Center mission statement is to evaluate and optimize early production computing technology and provide breakthrough software solutions to significantly increase the breadth and impact of Computing.

1.2 Scope

The contractor shall provide non-personal, A&AS for (1) Executive Support, (2) Business Management Support, (3) Civil Engineering Support, (4) Financial Management Support, (5) Program Management Support, (6) Information Technology Support and (7) Research Support to 15 SPSS at the AMOS site as described in Mission Overview.

Information technology support includes: (1) operations support: including systems integration, systems administration, network administration, cybersecurity/information assurance, and database administration; and (2) technology advancement for AMOS: such as software applications support and development, systems support and development, data analysis, technology evaluation, and customer centric outreach.

The services addressed as part of the scope are to support the AMOS Site’s management and technical support for acquisitions and Operations activities at various organizational levels such as: the squadron, branch, sections, operations, and individual projects.

2 General Requirements This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

2.1 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual Contractor employees. The Contractor shall ensure its employees understand the prohibitions imposed on the Government regarding personal services contracts, as defined in FAR 37.104(a) as “characterized by the employer-employee relationship it creates between the Government and the contractor’s personnel.” The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, the Contractor shall notify the Contracting Officer (CO) immediately.

2.2 Contractor Management

The Contractor shall integrate and coordinate all activities needed to satisfy the requirement. The Contractor shall manage the timeliness, completeness, and quality of problem identification. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors (when subcontractors are utilized). The Contractor shall seek to ensure customer satisfaction, professional behavior, and ethical behavior of all Contractor personnel.

The Contractor shall provide a Monthly Status Report (MSR) covering the Contractor’s activities of the preceding month.

Deliverable A001 – Monthly Status Report (MSR)

The Contractor shall provide an annual Fringe Report.

Deliverable A002 – Professional Employee Compensation (PEC) Report

2.2.1 Contract Administration

The Contractor shall ensure its personnel do not perform inherently Governmental activities. The Contractor shall ensure its personnel do not attempt to represent the Government of the United States (US) to any other person or entity, US, or foreign, except for delivering a Government-approved message or position. All briefings, policies, plans and other formal products the Contractor develops, reviews, and creates, will be reviewed and approved by the Government.

2.2.2 Contractor POC

The Contractor shall have a single point of contact between the Government and Contractor personnel assigned to support this contract. This lead shall coordinate with the Contracting Officer’s Representative (COR) to obtain and clarify contract requirements and shall be responsible for the daily control and supervision of the Contractor’s employees.

2.2.3 Personnel Administration

The Contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements. The Contractor shall obtain approval from the CO prior to attending Government-provided training classes. Provided there is no cost to the Government, the Contractor may be eligible to attend Government-sponsored and Government-provided training to maintain proficiency in software, administrative procedures or other areas. Additionally, provided there is no cost to the Government, the Contractor may be eligible to attend third party-provided off-site seminars and classes.

2.2.4 Contractor Identification

Contractor employees shall clearly identify themselves as “Contractors” at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other Contractor personnel, or with the public. Contractor personnel should wear a readily visible badge that clearly identifies them as Contractor employees.

2.3 Contractor Personnel, Disciplines, and Specialties

The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The Contractor shall ensure the labor categories and man-hours utilized in the performance of this PWS issued hereunder will be the minimum necessary to accomplish the task. The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

2.3.1 Personnel Turnover

The Contractor shall ensure continuity of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal. Once the Contractor knows an employee will no longer support the requirement, the Contractor shall provide written documentation to the CO and COR within three (3) business days. In this notification, the

Contractor shall include the date and time the position will be vacant, anticipated fill date, and what management actions the Contractor will take to ensure uninterrupted performance.

2.3.2 Removal of Personnel at Government Request.

The Government may request removal (permanent or temporary) of personnel for security, safety or health reasons, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person.

2.4 Location and Hours of Work

This PWS requires work at the AMOS Site and its various Government facilities (e.g. sea level & summit locations on Maui Island). Normal workdays are eight (8) hours per day, Monday through Friday, except US Federal Holidays. The Contractor shall generally support a normal work week of 40 hours per week. Core hours of work are from 0900 to 1500 daily; Contractor personnel shall generally be available during these core hours.

2.5 Building Access

The Government will provide Contractor personnel unescorted access to 550 Lipoa Pkwy Kihei, HI 96753, the Remote Maui Experimentation (RME) site located at 805 Lipoa Pkwy Kihei, HI 96753, and associated Maui Space Surveillance Complex (MSSC) located at summit of Haleakala Mountain) consistent with task requirements. Access to Government facilities, documents and systems will be in accordance with the DD Form 254.

2.6 Morale Events

There may also be occasions when Contractors are invited to participate in morale and recreational activities (e.g., holiday parties, golf outings, sports day and other various social events). Under these circumstances, Contractor employees shall comply with individual company policy in accordance with company compensation system. Because the Government does not have an employer/employee relationship with Contractor employees, it is not authorized to grant administrative leave or expend Government resources to compensate Contractor employees for hours expended on activities not included in the PWS. In addition, the attendance at morale activities does not, in any way, excuse any non-performance or delayed performance on the Contractor’s part. The Contractor is still fully responsible for its performance requirements and/or deliverables as set forth in the PWS.

2.7 Closures

For closures affecting the availability of the Government site (e.g., weather closures, a National Day of Mourning, etc.), the Government will notify the Contractor through normal means such as the Snow Call Line and local news outlets, or via email from the COR or CO. During such closures, Contractor personnel may telework if they have a COR-approved telework request in place.

2.8 Teleworking

“Teleworking” is defined as authorization for a contractor employee that normally works at the Government location, to work at an alternate location (at the employee’s residence or other Contractor location) either permanently or temporarily. “Contractor location” is defined as Contractor-approved place of performance for certain employees that is not an employee’s residence or Government location. The COR may approve Contractor personnel to telework on a case-by-case basis. The Contractor shall obtain COR approval prior to any teleworking. To obtain approval for teleworking, the Contractor shall submit a teleworking request with appropriate rationale to the COR in writing. This request shall include the Contractor’s [“lead’s”, “Project Manager’s”, “Task Lead’s”, etc.] approval, as well the primary Government customer’s approval – if different than the COR – when the request is submitted to the COR for approval. If approved for teleworking, the Contractor shall support Government core hours in the same manner they would if they were working at a Government location. Although the Government may allow the Contractor to use Government computer resources for teleworking, all other teleworking expenses for internet, telephone connectivity, and other equipment services are the responsibility of the Contractor. Classified work is not authorized under telework. Authorized teleworking does not abrogate the Contractor’s requirement to protect information IAW applicable requirements in this PWS, the DD Form 254 or other Government regulations applicable to this contract.

2.9 Travel / Temporary Duty (TDY)

Travel to other Government facilities or other Contractor facilities may be required. All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the Government (subject to local policy procedures) and are on a strictly cost reimbursable basis. Travel requests will be coordinated through the Contracting Officer Representative (COR) and authorized by the Contracting Officer (CO). Contractors may be allowed to attend Government sponsored training.

Contractors may be required by the Government to attend training to be qualified to work under this contract. The training shall be scheduled to ensure mission disruption is at a minimum. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234, and Federal Acquisition Regulation (FAR) 31.205-46 Travel Costs. All Contractor employees are subject to customs, processing procedures, Status of Forces Agreements and other agreements, duties of the country to which they are traveling, and procedures, laws, and duties of the United States upon re-entry. Travel expenses for local travel are not chargeable to the contract; local travel is defined as within 50 miles of the AMOS Site.

Estimated travel requirements are included below.

Kirtland Meetings / Training

Colorado Springs Meetings / Training

2.10 Security and Safety

All Contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable National Agency Check (NAC).

2.11 DD Form 254

DD Form 254 specifies overarching security requirements and Contractor access to classified information. All contractor personnel supporting classified work efforts must be able to obtain and maintain the applicable security clearances. All Contractor personnel shall be able to access to material up to the classification level in accordance with the DD Form 254.

2.12 Operational Security (OPSEC)

The Contractor shall adhere to OPSEC guidance as defined in Air Force Instruction (AFI) 10-701, Operations Security (OPSEC). The Contractor shall be familiar with the organization’s Critical Information and Indicator List (CIIL) and ensure indicators and vulnerabilities are protected from Unauthorized Disclosure (UD) per Mission Delta 2/15 SPSS countermeasures and measures. The Contractor shall complete OPSEC in-processing training and follow-on OPSEC training such as event- driven and annual OPSEC training, as required by the Space Delta 2 OPSEC Signature Manager/15 SpSS OPSEC Coordinator per Department of Defense (DoD) Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual (DoDM) 5205.02, DoD Operations Security (OPSEC) Program

Manual; Chairman of the Joint Chiefs of Staff (CJCS) Instruction (CJCSI) 3213.01D, Joint Operations Security; and AFI 10-701, OPSEC.

2.13 Controlled Unclassified Information (CUI)

The Contractor shall safeguard all information provided and marked as CUI via this contract IAW DoD Instruction (DoDI) 5200.48, Controlled Unclassified Information (CUI). If the Contractor generates any CUI information, it shall protect and disseminate that information by the controls required by DoDI 5200.48. The Contractor shall monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. The Contractor shall immediately report the potential classification of aggregated or compiled CUI to the CO and the COR.

2.14 Manpower Reporting

The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor shall fill in all required data fields at the data collection site. Use the following web address: www.sam.gov.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, the Contractor shall report all data no later than October 31 of each calendar year.

Contractors may direct questions to the System for Award Management (SAM) help desk.

2.15 Documentation

The Contractor shall make all information and documentation generated or maintained (to include Government-furnished documents) by this contract available for Government review upon request for the duration of the contract. The Contractor shall generate and maintain all such documentation in an electronic, editable (where appropriate) format. Contractor-generated format is acceptable, unless otherwise noted by this PWS.

The Contractor shall provide responses to requests for information. These requests are in addition to Deliverable submissions and other documentation that is available for review by request. Requests may cover the range of activities under this PWS.

2.16 Documentation Rights

The Government has unlimited rights to data for all deliverables developed under this PWS. The Contractor shall not use any materials pertaining to this contract for business development or any other Contractor purposes; however, the Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements.

All products developed and produced by the Contractor in the performance of this PWS are the property of the Government, and this could include software, electronic files, hard copy documents, etc.

2.17 Government Data

The Contractor shall request Government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract. The Government will provide the Contractor with access to information required to accomplish assigned tasks commensurate with security clearance and on a need- to-know basis. The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the Contracting Officer.

2.18 Performance Evaluation.

Contractor performance is subject to Government surveillance to ensure PWS compliance. The Contractor shall comply with the following:

Access. The Contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The Contractor shall provide support, and not interfere with the CO, Contracting Officer’s Representatives (CORs), state, federal, and other designated personnel in the performance of their official duties. The Contractor shall provide access as soon as possible, but not to exceed one (1) workday after the request.

Non-conformance. The Contractor shall identify root causes of non-conformances and shall control them through analysis, corrective actions, and preventive actions. The Contractor shall focus on eliminating the cause to prevent reoccurrence. The Contractor shall maintain records of non-conformities and actions taken. The Contractor shall correct and provide responses to all Government-identified non- conformances in accordance with (IAW) time frames specified by the CO. There are two types of non-conformances: Minor and Major.

Minor non-conformance. A Minor Non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Minor Non-conformance does not normally increase risk to the Government. Minor non-conformances are typically low risk and are communicated through a Corrective Action Request (CAR) notice. First notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non- conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan may not be required for notices.

Major non-conformance. A Major Non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Major Non-conformance may also be a significant number of recurring non- conformances, which is an indication of inadequate preventive measures or actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate Major Non-conformances using the CAR notice and will include a suspense date for the Contractor’s Corrective Action Plan. As a minimum, the Contractor’s Corrective Action Plan shall address:

· Actions taken to fix the immediate problem

· Root cause analysis of the problem to determine cause

· Corrective action on the cause of the problem

· Actions taken to prevent recurrence

2.19 Government Furnished

The Government will make available the materials, office space, communications capability and information for use by the Contractor in the performance of this contract.

2.19.1 Government Furnished Property (GFP).

The Government will not provide any GFP for Contractor use on this contract.

2.19.2 Government Furnished Resources.

The Government will furnish workspaces at 550 Lipoa Pkwy Kihei, HI 96753, associated desks, chairs, computers/laptops, internet connection, use of telephones, copier and fax machines. Any equipment is considered incidental to performance location.

2.19.3 Government Furnished Information

Government staff personnel will be available for technical exchanges with the Contractor. Government personnel will provide technical input, answer questions, review and approve completed work, and provide feedback regarding Contractor efforts. The COR is the primary source of technical guidance for this PWS.

3 Performance Requirements

3.1 Executive Support

Performance of requirements begins on 1 June 2027.

3.1.1.1 The contractor shall provide senior-leadership administrative support services for the 15th SPSS Commander.

Administrative support includes calendar management, answering telephones, greeting visitors, preparing correspondence, distribution of documents, gathering information, responding to requests for information, distributing documents, responding to queries from higher headquarters, proofread and provide edits to correspondence and recurring/non-recurring reports, and track suspense items Performance Standards

a) Standard: Knowledge of general office routine

b) Standard Proofread and edit correspondence 3-5 times per week

c) Standard: Writing IAW Tongue and Quills

d) Standard: Track 5-10 suspense actions per week

3.1.1.2 The contractor shall fulfill the functions of Functional Area Records Manager (FARM) and Records Custodian (RC) in providing records management functions for all of 15 SPSS. Includes: filing, maintaining, and disposing of Government records.

Performance Standards

a) Standard: AFI 33-322, Records Management Program

b) Standard: AFI 33-322 AFRLSUP AFRL Records management (RM) Program

c) Standard: Local Records Management Plan; as provided by the COR

d) Standard: Includes official and unofficial records

e) Standard: Includes all AMOS official files electronic and hardcopy

f) Standard: Manage records in the Air Force Records Information Management System (AFRIMS)

3.1.1.2.1 The contractor shall provide Records Management training to Government and third-party support contractors.

Training format will be slide presentation, no printed materials are necessary.

Performance Standards

a) Standard: 1 time per year

b) Standard: Approximately 25 personnel

c) Standard: AFI 33-322, Records Management Program

d) Standard: AFI 33-322 AFRLSUP AFRL Records management (RM) Program

3.2 Security Support

3.2.1 Security Support

3.2.1.1 The contractor shall serve as a CSSR, supporting all aspects of the organization's security program and shall support accountability of all Special Security Compartmented Information Facilities (SCIFs) within the Squadron.

Performance Standards

a) Standard: Must be performed by individual(s) with a TOP SECRET security clearance with SCI eligibility.

b) Standard: DoDM 5105.21 v1 Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Information and Information Systems Security, Vol 1 Enclosure 2 para 10.

c) Standard: Shall conduct monthly SCIF entry/exit inspections checking for prohibited items and tracking individuals entering and exiting the SCIF.

d) Standard: Shall coordinate the Nominations, Transfer in Status (TIS) and Transfer Out Status (TOS) of SCI for cleared personnel.

3.2.1.2 The contractor shall draft, update, and maintain local procedures and documentation for implementing and administering security programs.

a) Standard: Documentation shall be accurate, complete, and compliant with all applicable regulations and directives, including DoDM 5105.21 series.

b) Standard: DoDM 5105.21 v1 Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Information and Information Systems Security, Vol 1 Enclosure 2 para 10. Note: Para 4. PROCEDURES points to specific enclosures

c) Standard: Shall update documentation for Special Security Office (SSO) Security Standard Operating Procedures (SOP) and Emergency Action Plan (EAP) as needed.

3.2.1.2 The contractor shall draft, update, and maintain local procedures and documentation for implementing and administering security programs.

a) Standard: Documentation shall be accurate, complete, and compliant with all applicable regulations and directives, including DoDM 5105.21 series.

b) Standard: DoDM 5105.21 v1 Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Information and Information Systems Security, Vol 1 Enclosure 2 para 10. Note: Para 4. PROCEDURES points to specific enclosures

c) Standard: Shall update documentation for Special Security Office (SSO) Security Standard Operating Procedures (SOP) and Emergency Action Plan (EAP) as needed.

3.2.1.3 The contractor shall support development, and maintain a comprehensive security education, training, and awareness (SETA) program for all personnel, and maintain training records.

a) Standard: Will attend SCI Security Officials Course or other Special Security Officer approved course prior to appointment.

b) Standard: Annual training sessions for AMOS employees; can be completed via email and TEAMS.

c) Standard: DoDM 5105.21 v3 Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Personnel Security, Industrial Security, and Special Activities, Vol 3 Enclosure 6: Security Education, Training, and Awareness (SETA) Program.

d) Standard: Conduct security orientation briefings to new employees within 30 days of their start date, provide refresher briefings at least annually, and conduct debriefings for departing personnel within one week of their departure date.

3.2.1.4 The contractor shall support physical access control systems for the SCIFs and assist with personnel security administration.

Performance Standards

a) Standard: Shall support the access control system, creating and maintaining access lists for SCIFs and collateral spaces.

b) Standard: Assist with personnel security administration by verifying clearances in government systems (e.g. DISS/JADE) and preparing access rosters for government approval.

c) Standard: Shall verify security clearances for site personnel daily and monitor security org box.

3.2.1.5 The contractor shall assist with information security and asset management.

a) Standard: Shall sanitize unclassified and classified materials located throughout the Squadron's buildings monthly.

b) Standard: Shall ensure compliance with regulations for approved GSA safes and the disposal of classified material.

c) Standard: Support end-of-day closing procedures for controlled areas within 15 SPSS.

d) Standard: Update, print and post SF 701 & 702 and visitor logs for all SCIFs and secure classified areas monthly.

3.3 Civil Engineering Support

3.3.1 The contractor shall provide analysis, technical expertise, and recommendations to support the 15 SPSS Civil Engineering Requirements Section in the evaluation of third-party contractor execution of CE requirements at AMOS.

The Government will perform all COR duties with respect to the third-party contract and will be the final decision authority.

Performance Standard

a) Standard: AFI 32-1001, Civil Engineering Operations, Sections 1.6.6, 1.7.1.1, 1.7.1.3, 1.7.1.4, 1.7.3.

Reference 1.7.5

3.3.1.1 The contractor shall review real property records entered/updated in the BUILDER SMS program by third-party contractors.

Real property is limited to MSSC and RME sites.

Performance Standard

a) Standard: Provide recommendations for Government action when areas for improvement or of non- compliance are identified

b) Standard: Monitor corrective actions through successful implementation

3.3.1.2 The contractor shall evaluate outputs of BUILDER SMS program and provide recommended repair work with prioritization to the Government for work order initiation Performance Standard

a) Standard: Provide actionable recommendations for Government approval/work order to support a monthly work request review board (WRRB)

b) Standard: Manage and Facilitate monthly WRRB

3.3.1.3 The contractor shall monitor the transition from the legacy Interim Work Information Management System (IWIMS) to the NextGen IT/IBM TRIRIGA integrated workplace management system.

Note: Transition from IWIMS to NexGen IT/IBM TRIRIGA is planned for June 2022 Performance Standards

a) Standard: Provide recommendations for Government action when areas for improvement or of non- compliance are identified

b) Standard: Monitor corrective actions through successful implementation

3.4 Financial Management Support

Performance of requirements 3.4.1 – 3.4.3 begins in OY1

3.4.1 The contractor shall prepare financial funding documents for Government action.

Performance Standards

a) Standard: For funds allocation and release

b) Standard: Requests for Emergency Funds Required under Continuing Resolution Authority (CRA)

c) Standard: Requests for Lines of Accounting (LOA) establishment in the Comprehensive Cost and Requirements (CCaR) database

d) Standard: To include Requests for Purchase (AF Form 9), Military Interdepartmental Purchase Requests (MIPRs) (DD Form 448) and MIPR Acceptance (DD Form 448-2), Military Obligation Reimbursement Documents (MORDs) (AF Form 406), Government Interagency Agreements (IAAs) (FS Form 7600A/B), Government Purchase Card Form 4009 (GPC/4009), and Travel Orders (AF Form 1610)

3.4.2 The contractor shall provide analysis and recommendations to the Government on funds control, resource allocation, budget execution, cost status and funds reporting.

Performance Standards

a) Standard: For RDSM / 15 SPSS 5-year plan budget forecasts

b) Standard: Budget forecasts updated in CCaR system for obligations and expenditures at least weekly

3.4.3 The contractor shall provide analysis and recommendations for the 15 SPSS Planning, Programming, Budgeting and Execution (PPBE) processes.

The contractor shall interface with higher headquarters to coordinate resourcing expenses related to operational baseline sustainment, purchasing, and funds execution.

Performance Standards

a) Standard: For all programs in the 15 SpSS portfolio

b) Standard: Includes multiple funding appropriations (e.g. R&D, O&M, & Procurement)

3.5Program Management Support Performance of requirements 3.5 begins in OY1

3.5.1 Stakeholder Management

3.5.1.1 The contractor shall organize and coordinate high-visibility conferences, visits, and events.

Performance Standards

a) Standard: Support and coordination of distinguished visitors

b) Standard: Support and coordination of yearly AMOS Conference and Space Domain Awareness (SDA) Conference

c) Standard: Support and coordination of Senior Steer Group Meetings

d) Standard: Manage database of site stakeholders

3.5.1.2 Stakeholder Support - Provides analysis and recommendations for Government action in developing, updating, and coordinating support agreements (SA) between Suppliers/Customers and Receivers.

Performance Standards

a) Standard: Complete collaborative development and coordination of new agreements within 30 days

b) Standard: Complete review and coordination of renewed agreements within 20 days

c) Standard: Maintain SA repository and contact information

d) Standard: 3-4 SA updates annually; 2-4 new SA annually

3.5.1.3 The contractor shall provide overall cost, schedule, and performance management of resourced programs, projects, and contracts within the execution portfolio of 15 SPSS.

Desired Qualifications:

a) Minimum of 3 years of experience in, or with, a U.S. Federal Government Program Office

b) DAWIA Level III Program Management, or DAWIA Advanced Program Management, or Program Management Professional (PMP) Certification, or equivalent of 6+ years of experience in, or with, a U.S. Federal Government Program Office

3.5.1.4 The contractor shall prepare financial and status products for approximately 2-10 contracts. Contractor will prepare documentation using the Government-provided templates; Government PM will brief as needed Performance Standards

a) Standard: Development of Execution Plans annually, incorporating strategic planning, capital planning, and including transition of technology opportunities

b) Standard: Updates to obligation and execution forecasting monthly

c) Standard: Government Implementation of Operations Planning and Execution monthly

d) Standard: Program Management Reviews up to bi-monthly to Government Leadership

e) Standard: Combined Space Operations Center (CSpOC)/ National Space Defense Center (NSDC) Status Support monthly to include proposal of improvement of projects planning

f) Standard: Development of detailed cost estimates, and activity schedules

3.5.1.5 The contractor shall collect, manage repository, analyze and provide recommendations to the Government on third-party contractor deliverables.

Performance Standards

a) Standard: Program Management Review bi-monthly

b) Standard: Program Status Reports monthly

c) Standard: IPT status meetings weekly

d) Standard: IMS deliverables monthly

e) Standard: Cost reports monthly

f) Standard: Invoices biweekly

3.5.1.6 The contractor shall analyze and provide recommendations to the Government on third-party contractor deliverables.

Limited to high-level/general recommendations, work effort does not include refinement or implementation of recommendations. Contractors shall be knowledgeable of both Government’s requirements and contractor’s plan Performance Standards

a) Standard: Configuration Management process and monthly deliverables

b) Standard: Integrated Sustainment Plan, initial and quarterly updates

c) Standard: Risk & Opportunity Review Meeting support monthly

d) Standard: Integrate Master Schedule (IMS) monthly

e) Standard: Technical performance measures and monthly metrics

f) Standard: Integrated Program Management Report (IPMR) monthly

g) Standard: Technical Interchange meetings monthly

h) Standard: Systems Engineering events (e.g. PDR, CDR)

3.5.1.7 The contractor shall analyze and provide recommendations to the Government regarding third-party contract events and deliverables.

Limited to high-level/general recommendations, work effort does not include refinement or implementation of recommendations.

Performance Standards

a) Standard: Systems integration projects

b) Standard: Requests for studies and analysis, engineering design

c) Standard: Technology projects

3.5.1.8 The contractor shall provide input for recurring Boards.

Contractor will prepare documentation using the Government-provided templates; Government PM will brief, and the contractor will attend Performance Standards

a) Standard: Scientific Advisory Board quarterly

b) Standard: Distinguished Review Board quarterly

a) Standard: Complete technical requirement and detailed tasks

b) Standard: Cost and schedule estimates

c) Standard: Technical acceptance criteria

3.5.1.9 The contractor shall review and participate in 15 SPSS test and evaluation planning and program activities.

Performance Standards

a) Standard: Enclosures 4 and 5 of DoD Instruction (DoDI) 5000.02T, Operation of the Defense Acquisition System

b) Standard: New Project Test Plans quarterly

c) Standard: Test Plan execution reviews monthly

3.5.2 Workforce Management Support

3.5.2.1 In the event the contractor is unable to find fully qualified personnel as defined within their staffing approach, the contractor shall notify the Government and develop an individual training plan for less qualified personnel candidates and submit to the Government for approval of the individual training plan prior to each hiring.

Performance Standards:

a) Standard: The contractor shall develop an individual training program that will support bringing personnel up to speed using other members of and associated with the contractor performing similar jobs. (i.e., Security Specialists, Program Managers, Financial Analysts, etc.)

b) Standard: The contractor shall assume all costs of training. The training may consist of onsite (over the shoulder) and offsite (i.e., MS Teams) depending on the training topic and classification level required.

c) Standard: The training plans per individual shall be reviewed and approved by the Government prior to hire.

3.5.3 IT Support

3.5.3.1 The contractor shall provide administrative support for the preparation of funding packages for government-approved IT requirements.

Performance Standards

a) Standard: Draft required funding documentation (e.g., 7600B forms, MIPRs) using government-provided information, such as the line of accounting, cost estimate, and a description of the approved requirement.

b) Standard: Submit all draft documentation to the designated government official for final review, certification, and signature.

c) Standard: The contractor shall perform a quality control review on all prepared draft documents to ensure accuracy and completeness in accordance with Unit guidelines.

a) Standard: Assist in tracking and reporting on the execution status of approved and funded IT budget items.

b) Standard: Provide administrative support for the consolidation and formatting of government-drafted Unfunded Requirements (UFRs) and Quad Charts into standardized templates for government review and submission.

c) Standard: Fulfill government-approved requests for historical financial data from the Program Control office within 5 business days.

3.5.3.3 The contractor shall provide advisory and assistance services for IT projects. This shall include monitoring project status, tracking IT project schedules, and providing recommendations to the government project leads.

a) Standard: Project status and schedule tracking reports shall be delivered to the government project lead weekly and shall be 98% accurate.

b) Standard: Actionable recommendations for identified project risks and issues shall be provided to the government project lead within 3 business days of identification.

c) Standard: The contractor's performance is measured by the quality, accuracy, and timeliness of their analysis and deliverables, not by the overall success or failure of the project itself.

3.5.3.4 The contractor shall support the lifecycle management of IT hardware (HW) and software (SW) assets.

Performance Standards

a) Standard: Support a comprehensive inventory of IT hardware and software assets and help report on asset status to support government identification of procurement needs.”

b) Standard: Quotes from the designated third-party vendor will be obtained within 5 business days of identifying a procurement need.

c) Standard: Ongoing tracking and weekly touchpoints with procurement vendor in order to stay in sync on status of quotes, orders and delivery to the unit

3.6Research Support Performance of requirements 3.6 begins in OY1

3.6.1 The contractor shall provide technical system integration support across the Air, Space, and Cyberspace Domains. The contractor will guide the establishment of partnerships/relationships at all levels of leadership within each organization. The contractor shall possess experience with the test, analysis, and/or experimentation of space systems or military systems, including space operations or test control room experience. The essential duties include, but are not limited to: leading recurring meetings to establish cross-architecture level trade studies and developing common interoperable architectures to support the test of complex, state-of-the-art systems for space-based applications; CONOPS development, requirements definition, multi-segment interface definition, mission partner architecture integration, functional analysis, risk management, and space range design activities; support space range architect integration and interfaces with operational and training systems; and developing architecture briefings, reports, and other associated architecture documentation.

3.6.2 The contractor shall provide support in planning and managing program transitions and operational integration, to include warfighter integration and requirements generation, wargame integration support, launch and initialization planning, ground system planning and integration, operational test and evaluation, initial operations, and program transition to operational units.

4 Applicable Publications The Contractor shall comply with all documents listed below in the table of publications and referenced under paragraph 3.0, Performance Requirements. The Directive/Guidance (D/G) column indicates the extent of Contractor compliance with the publication that is prescribed by the PWS. A “D” in the column means the publication is a “directive publication,” that requires mandatory compliance by the Contractor. A “G” in the column means the publication is a “guidance publication.” Compliance with documents listed as guidance is the Contractors' option. If there is any conflict between the directive referenced in PWS paragraph 3.0 and the reference listed in the tables below, the reference in PWS paragraphs 3.0 takes precedence.

When directive chapters, paragraphs, appendices, attachments, etc. are referenced as a standard in this PWS, the standard shall be inclusive of all subordinate paragraphs unless specifically excluded. For example, if the PWS standard lists paragraph 1.2 as directive, and paragraph 1.2 has subparagraphs 1.2.1, and 1.2. those subparagraphs are directive as well.

Publications

5 Deliverables The Contractor shall provide deliverables as described in the PWS. Format and delivery schedule for deliverables shall be outlined in the table below. All Deliverable distribution shall be by an electronic method unless otherwise specified. Email documents in a Microsoft Office or Adobe Acrobat-compatible format. Submit drawings in a uniform electronic format.

Informal, recurring work products may not require a deliverable. These products are still required as described in paragraph 3 of the PWS.

If there is any conflict between the Deliverable reference in paragraph 3 of this PWS and the Deliverable specifics in the following table, paragraph 3 takes precedence. Days referenced shall be calendar days, unless otherwise noted. For recurring Deliverables, if the due date falls on a holiday or a weekend the Deliverable may be sent on the following business day. Contractor format is acceptable, unless a specific format is identified. The Contractor shall not include its name or any logos on any Deliverable except when a Contractor signatory is required by the Deliverable. The Contractor shall ensure all markings included in Deliverables are consistent with the contract’s requirements, to include copyright and proprietary markings addressed in the contract’s clauses.

Deliverable Table

the month after performance

COR

Description: (Contractor format acceptable) As a minimum, the MSR shall detail:

· Major tasks/activity status

· Quantities of tasks/meetings supported

· Contractual issues or risks requiring Government resolution/mitigation

· Contractor work efforts exceeding the requirements and providing additional benefits to the Government

· Self-identified performance deficiencies during the period; including the cause of each identified deficiency, corrective actions, the impact, and actions taken to preclude recurrence

· Current status of all issues yet to be resolved or in work

· Deliverables submitted

· Executive summary detailing a self-assessment of the Contractor’s performance during the reporting period

SAM-D/PK

Description:

PEC Report shall be delivered in a soft copy, MS Office Excel compatible format.

The Contractor's PEC Report shall include all data and supporting information required by FAR Subpart 22.1103. The PEC Report shall include the prime contractor's subcontractors / teaming partners / joint venture partners’ information (professional employee's salaries and fringe benefit package). Submission of this data by subcontractor directly to the CO is acceptable.

The PEC Report shall present actual salaries and fringe benefits used for professional employees as prescribed in the instructions below:

Provide the actual compensation for all professional employee labor…