SpOC EIS IV PWS v0_2.pdf

UNCLASSIFIED

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

FOR

UNITED STATES SPACE FORCE (USSF)

HEADQUARTERS SPACE OPERATIONS COMMAND (HQ SPOC)

ENTERPRISE INFORMATION SERVICES (EIS) IV

7 April 2025

REVISION HISTORY

Revision Description of Change Author Effective Date

A Initial Revision S. Sanders, SAIO/PMA 7 Apr 25

TABLE OF CONTENTS

1.0 DESCRIPTION OF SERVICES

2.0 PROGRAM MANAGEMENT

3.0 SPECIFIC REQUIREMENTS

4.0 GENERAL REQUIREMENTS

5.0 SERVICE SUMMARY

6.0 SECURITY REQUIREMENTS

7.0 DELIVERABLES

8.0 MANPOWER REPORTING

9.0 CONTRACTOR PURCHASING

APPENDIX A – ACRONYMS

APPENDIX B - APPLICABLE STANDARDS AND REFERENCES

APPENDIX C – SpOC EIS DELIVERABLES

1.0 DESCRIPTION OF SERVICES

This Task Order (TO) is for non‐personal services. The Contractor shall provide United States Space Force (USSF) Enterprise Information Services (EIS) support for SpOC SharePoint sites, EIS Training for HQ SpOC users, and Enterprise Task Management Software Solution (ETMS2) license management and team names/workflow support for USSF units. USSF is defined as US Space Force Field Commands and Centers: Space Operations Command (SpOC); Space Systems Command (SSC); and Space Training and Readiness Command (STARCOM) and their units. EIS is defined as collaboration tools e.g., SharePoint, MS Power Platform (Apps/BI), ETMS2, and MS Teams. All performance shall be in accordance with this Performance Work Statement (PWS).

2.0 PROGRAM MANAGEMENT

2.1 The Contractor shall appoint a Program Manager (PM) in writing, including the name, telephone number (to include mobile telephone) and email address, to the Contracting Officer (CO) and the Contracting Officer Representative (COR) within 3 days of award and any changes thereafter. The PM shall oversee all aspects of the contract. The Contractor shall monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, support management and recommendations, and facilitate communications. The Contractor shall institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting. The Contractor shall maintain the SpOC’s EIS Status Page and administer this integrated data management system for weekly collection and status. See Appendix C, Item 8, SpOC EIS Status Page. The PM shall ensure that Contractor employees understand the prohibitions imposed on the United States (US) Government regarding personal services contracts and shall report instances where the Government attempts to control or supervise Contractors' employees to the COR and CO immediately.

2.2 The Contractor shall provide recommended inputs and statistics for a monthly Performance Assessment Report (PAR) NLT the 5th calendar day of the month after the reporting month, detailing monthly tasks/activity status, meetings supported, issues or risks requiring Government resolution or mitigation, highlighting the benefits to the Government, and provide an annual overall self-assessment of the Contractor’s performance during the reporting period as it relates to requirements and activities identified in this PWS. See Appendix C, Item 1, SpOC EIS Monthly Performance Assessment Report (PAR).

3.0 SPECIFIC REQUIREMENTS

3.1 Task 1, SpOC EIS Solutions Team.

The Contractor shall provide SpOC EIS Solutions Team services support for approximately 8,000 end users to ensure continuity of day-to-day operations. Users may be from HQ SpOC, Deltas, Geographically Separated Units (GSUs) or Detachments (Dets). The Contractor shall provide support for SpOC SharePoint sites, permissions, service desk support, application management and business data analysis of SpOC business processes support, data gathering for efforts out of the box (OOTB), short-term development, training, and general application support. The Contractor shall manage ETMS2 users for all Field Commands (FLDCOMs), their teams and members and assist with issues that arise. The Contractor will interface with ETMS2 Tier III support for issues.

The Contractor shall ensure the SpOC Headquarter staff in Bldg 1 have on-site SpOC EIS Solutions Team support for SpOC NIPRNet and SIPRNet SharePoint sites, permissions, business data analysis data gathering for application development, with and without Power Platform, training on new sites created, and general application management support, as applicable. This is primarily for the Headquarter Staff but shall extend to all organizations within SpOC.

3.1.1 SharePoint Site Collection Management. The Contractor shall work the SpOC Site

Collection Administrators (SCAs) and Site Owners with SharePoint business analysis application development, permissions and support, when SharePoint Site Owners request assistance or are unavailable.

a. SharePoint Applications. The Contractor shall develop SpOC SharePoint applications for end-users with a level of effort of 4 to 80 hours each, and hand them off to the user upon user-acceptance is obtained. Contractor shall not continually maintain previous developments or new requirements unless developed for the Contractor’s team to support sites like the Support Center.

b. SharePoint Site Permissions Management. The Contractor shall ensure all Site Owners and Site Collection Administrators (SCA) have received the SpOC SharePoint training prior to giving them permissions. The Knowledge Management Centers (KMCs) at each SpOC location shall obtain SharePoint Online (SPO) SCA permissions for their Units complying with SpOC SharePoint Governance on their authority role, business rules, and training.

c. SpOC SharePoint Governance Plan Enforcement. The Contractor shall ensure the enforcement of the SpOC SharePoint Governance Plan for SpOC SharePoint sites and manage routine maintenance of the SharePoint environments. The documented plan is located in the SpOC EIS Support Center (EISSC). The Contractor shall ensure SharePoint permissions are not being abused and police sites for units not following the governance. If the Contractor identifies any governance policy not being followed, actions to revoke permissions shall be taken. Reference 3.1.3 below.

3.1.2 Enterprise Task Management Software Solution (ETMS2). The Contractor shall provide US Space Force (USSF) Field Command (FLDCOM) ETMS2 support for help desk, training, and license management. for all USSF Field Command users.

The ETMS2 site collections hosts the USSF Field Commands (SSC, STARCOM and SpOC) and are available on NIPRNet/SIPRNet with the site collection called FLDCOM on both NIPRNet and SIPRNet.

The Contractor shall:

a. Provide support to create, activate, or deactivate ETMS2 License holders, as applicable (Approx. 400 a month).

b. Provide license management for 3,500 FLDCOM ETMS2 licenses and the Unit

ETMS2 POCs.

c. Provide a bi-monthly report of SpOC ETMS2 active user licenses and organization license allocations. The Contractor shall provide the report the 1st and 3rd Friday of each month to the COR. See APPENDIX C, Item 3, FLDCOM ETMS2 Licenses Report.

d. Provide a quarterly scrubbing of inactive users and report of FLDCOM inactive/underutilized ETMS2 Licenses/Accounts. See APPENDIX C, Item 4, FLDCOM Inactive/Underutilized ETMS2 Accents/Teams Report.

e. Provide ETMS2 Organizational team name maintenance by creating, renaming, or deactivating ETMS2 Teams, as requested. (Approx. 15 a month).

f. Oversee the SpOC ETMS2 Records Archive Delivery System (RADS) modules for both NIPRNet and SIPRNet ETMS2 taskers, as required.

Contractor shall provide Tier 1 SpOC EIS Solutions Team support for the RADS module and support ETMS2 end-users with RADS features.

g. Provide FLDCOM ETMS2 template name scrub annually. The SpOC/CoS will send out a ETMS2 tasker for all units to review and rename their current templates in ETMS2 by renaming the template with the current Calendar Year (CY). Example: HQ FLDCOM eSSS Template 2024. The Contractor shall review templates NLT 30-days after tasker close-out templates not showing the current CY and disable these templates. (Approx. 15 a year) See Appendix C, Item 5, SpOC Annual ETMS2 Template Review.

3.1.3 SpOC SharePoint Governance.

The Contractor shall provide an annual review of SpOC SharePoint Governance to ensure SharePoint controls, structure, methods and permissions are current and accurate for the SpOC NIPRNet and SIPRNet SharePoint On-line (SPO) sites. See Appendix C, Item 6, SpOC SharePoint Governance Review.

a. The Contractor shall complete annual review of the SpOC SharePoint

Governance and provide comments to the COR with tracked changes on a MS Word document no later than 1 September of each year.

b. Coordinate comments and revisions made with the COR within 30 days after initial change submission to the COR.

c. Upload the final approved version of the SpOC SharePoint Governance no later than 1 November of each year to the SpOC EIS SharePoint Support Center.

3.1.4 SpOC EIS Support Center.

The Contractor shall maintain the SpOC Support Center on the SPO NIPR SharePoint to ensure updated information, support, and training are available for end-users, (e.g., EIS updates, issues, training, ETMS2 and SharePoint assistance, contact info, etc.) The Contractor shall apply updates as necessary. (Approx. 4 per quarter).

3.1.5 SharePoint Online (SPO).

The Contractor will provide NIPRNet and SIPRNet SPO Tier 1 and II support through the SpOC EIS Solutions Team. See paragraph 3.2.2 for Tier 1 level definition for the SPO Tier level support.

a. The Contractor shall submit ServiceNow tickets, as necessary, for the SPO hosted SharePoint environments for Tier 3 support.

b. The Contractor SpOC EIS Solutions Team shall help in identifying and fixing broken permissions, help with web parts, Power Platform, Power Apps Power BI, business processes, custom solutions, workflows, calendars and other solutions in the SpOC environments.

3.1.6 SpOC SharePoint Section 508 Compliancy.

The Contractor shall support the Government in its compliance with Section 508 throughout the development, implementation, and management of the SpOC SharePoint sites. Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) requires that when Federal agencies develop, procure, maintain, or use electronic information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who do not have disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

Applicable standards of the SpOC SharePoint sites shall be compliant with Section 508, Americans with Disabilities Act as defined in Section 508 (29 U.S.C. 794d), Technical Standards (Subpart B), Web based Intranet and Internet Information and Applications (1194.22). The SpOC SharePoint sites will follow, at a minimum, the Priority 1 Checkpoints of the Web Content Accessibility Guidelines 2.0 (WCAG 2.0) (January 2018) published by the Web Accessibility Initiative of the World Wide Web Consortium (W3C)."

The Contractor should review the following websites for additional 508 information:

https://www.section508.gov/index.php; https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards The Contractor shall attend Section 508 Compliant telecons/meeting hosted by SAF/CNZA and will provide SpOC NIPRNet SharePoint audits annually (Approx 10 audits). See Appendix C, Item 9, SpOC NIPRNet SharePoint Section 508 Compliance Audit.

3.2 Task 2, AF Portal Responsibilities.

The Contractor shall coordinate with the COR on actions to provide management and support for the SpOC area of responsibility for the AF Portal IAW the following requirements:

3.2.1 Content Manager: Provide SpOC AF Portal Content Manager (CM) support to site and sub-sites. The Contractor shall:

a. Track all lower-level SpOC AF Portal sub-site CMs who have elevated permissions to maintain the organizations on the SpOC AF Portal pages.

There are approximately 45 current SpOC AF Portal sites and 125 current trained and assigned CMs. The Contractor shall manage the system administration oversight for the SpOC pages on the Air Force portal and assigned CMs with negative or positive differentials of +- 6 sites or +-8 CMs.

b. Provide AF Portal training link to CMs.

c. Maintain overall responsibility of SpOC content management.

d. Manage publishing permissions to all subordinate unit CMs.

e. Troubleshoot and coordinate all SpOC AF Portal-related problems and issues (Approx. 10 calls a year) between CMs and AF Portal Help Desk.

f. Attend bi-monthly AF Portal CM technical interface meetings.

3.3 Task 3, EIS Solutions Team.

The Contractor shall provide SpOC application management, customer training, and help desk support for SpOC EIS applications and collaboration tools, and systems in accordance with DAFMAN 17-1305, Cybersecurity Operations, and DODD 8140.01, Cyberspace Workforce Management.

3.3.1 SpOC EIS Customer Training (see SpOC EIS Training Table below)

The Contractor shall coordinate with the COR to provide SpOC EIS collaboration training to customers in accordance with the Table 3.2 below.

Table 3.2, SpOC EIS Training

The Contractor shall:

1. Curriculum: Develop or update existing training guides to reflect the environment versions and collaboration tools, e.g., MS Teams. SpOC EIS Training encompassing SharePoint, ETMS2, Power Apps, Automate, BI, and other collaboration tools the government identifies.

2. SpOC SharePoint Training: The Contractor shall conduct SharePoint Training for designated SharePoint Collection Administrators (SCAs), Site Owners and end-users. SharePoint training shall be announced in the SpOC Support Center.

3. Location: The Contractor shall schedule and provide SharePoint, ETMS2 and other collaboration tool training via on-line screen sharing (e.g., MS Teams), one-on-one (on-line or in person), and classroom for the Training for Space Base Delta 1 (SBD1) On-site training at Peterson SFB, CO, and Site Visit Training to SDB2 at Buckley SFB, CO.

Self-Help Training (Support Center)

On-line Screen Sharing Training

Level of Training

How Often Duration One-on-One

Training Level of Training How Often Duration

Site Visit Training

Level of Training How Often Duration

O365 Beginner (Teams &

SharePoint)

End User

15xmo (Remote) 1 hr ea End User 5xmo (By Request) End User

1xyr

O365 Advanced (Teams & Power

Platform)

End User

5xmo (Remote) 3 Hrs ea x N/A . N/A End User 1xyr

SpOC EIS Training

Site Owner 1xyr

ETMS2 End User 2xmo (By Request) 1 hr eaOPR/OCR 2xmo (Remote) 1.5 hr ea End User

1-4 days combined with all the training available

1xyr

SharePoint Site Owner 2xmo (Remote) 2 days ea Site Owner 2xmo (By Request) 1 hr ea

a. The Contractor shall schedule a training facility at Peterson SFB necessary for hands-on training or appropriate off-site facility within close proximity to Peterson SFB for local training. The Contractor shall test computers, support equipment and connectivity are in good working order prior to each training session. For Classroom Training (Hands-On) at Buckley SFB, the Contractor will identify their POC to schedule classroom training once a year, for one week or less. Those local to Peterson SFB (e.g., Schriever SFB) can receive training at or near Peterson SFB.

b. The Contractor shall accomplish the training for FLDCOM ETMS2 users using the FLDCOM NIPRNet ETMS2 production environment. The Contractor shall ensure all FLDCOM individuals signed up for ETMS2 training have an active ETMS2 account assigned to them prior to training session.

c. The Contractor shall accomplish SpOC EIS online training to end-users using online screen sharing capability that end-users can access on the NIPRNet Air Force Network (AFNet) (e.g., MS Teams, etc.).

4. SpOC EIS Training Surveys: The Contractor shall have all participants who complete SpOC EIS Training submit survey inputs at the end of each course. For online courses, an email with a survey will be sent to training attendees to complete. The Contractor shall track all surveys submitted to ensure customer training needs were met based on the results. The SpOC EIS Training curriculum shall be adjusted based on customer feedback and versions released. See APPENDIX C, Item 7, SpOC EIS Training Survey.

5. Advertisement/Enrollment: The Contractor shall use the SpOC Support Center site for EIS training classes advertisement and scheduling, ensuring the customers can enroll through the training page on the SpOC SharePoint Support Center page.

3.3.2 SpOC Service Desk Support.

The Contractor shall provide on-site SpOC EIS NIPRNet and SIPRNet service desk support for approximately 8,000 end-users for SpOC EIS application issues, sites and permissions between 0730 and 1630, Monday through Friday, excluding all Federal Holidays.

1. Availability: The Contractor shall support Service Desk functions to all SpOC EIS end-users for SharePoint and MS Team; and all FLDCOM end-users for ETMS2, as requested.

a. The Contractors shall support NIPRNet and SIPRNet customers via email, telephone, instant message, and/or in person. The average calls/tickets logged are approx. 450 a month.

b. During duty hours, to exclude weekends and Federal Holidays, 98% of the time the Contractor shall respond to EIS telephone calls, voicemails, instant messages, and/or emails on both NIPRNet and SIPRNet; NIPRNet response shall be within a half hour and SIPRNet responses shall be within 1 hours. For the remaining 2% of the time, response shall be made within 1.5 hours.

c. If the SpOC Service Desk voicemail or email are received after duty hours, the Contractor shall respond within 1 hour of the beginning of the next duty day if appropriate information is left by the customer for a call back.

d. If point of contact is unreachable by phone, the Contractor shall leave a voicemail and follow-up with an email if contact information was provided.

The below table and paragraphs depict the SpOC Service Desk and SpOC EIS Solutions Support Levels for Customers.

Table 3.2.2, SpOC EIS Tiered-Level Service Desk and Support Teams

2. SpOC EIS Tier Level Definitions:

a. Tier 0 Support: Consists of end-user self-help services and support resolution of issues and education at the lowest level:

SpOC Support Center - User Guides, Governance, and Service Desk contact info

b. Tier 1 Support: For SpOC SharePoint, the SpOC Service Desk will provide support to end-users for application issues, sites, permissions, and questions via email, voice mail, instant messaging and hands-on support, as applicable.

Microsoft Clouds TIER 0 TIER 1 TIER 2 TIER 3 SharePoint (NIPRNet and SIPRNet)

Hosted by the Army TIER 0 TIER 1 TIER 2 TIER 3 NIPRNet/SIPRNet FLDCOM ETMS2

SpOC EIS Tiered-Level Service Desk and Support Teams

c. Tier 2 Support: SpOC EIS Solutions Team

Provide support for SpOC SharePoint content on SpOC sites.

d. Tier 3 Support: SharePoint SPO Support

The Contractor shall escalate SpOC SIPRNet SharePoint issues through ServiceNow.

3.4 TASK 4, SPOC SHAREPOINT CHANGE ADVISORY BOARD (CAB).

The Contractor shall coordinate with the COR prior to providing input to the CAB.

The SpOC SharePoint Configuration Control CAB is established under the authority of HQ SpOC/S64 and is tasked with configuration control and change management responsibilities within the SpOC CAB Charter located at the SpOC Support Center.

a. The SpOC SharePoint Configuration Control CAB reviews and analyzes change proposals (i.e., Change Requests, deviations, or waivers) affecting the SpOC environments. This CAB is the official forum for review, approval and/or disapproval, and documentation of all requested changes to the established SpOC environment baseline.

b. The Contractor shall not engineer changes but shall perform sufficient analysis and technical review to ensure that the proposed change is suitable for incorporation into the SpOC environments. Refer to the SpOC SharePoint CAB Charter for further details. The CAB meets monthly to review proposed changes and requests, as necessary.

4.0 GENERAL REQUIREMENTS

4.1 PLACE OF PERFORMANCE.

The Contractor shall perform all on-site performance and activities in Building 1, 150 Vandenberg Street, Hartinger Building, Peterson SFB, CO, 80914 (hereinafter referred as Building 1). Contractor shall use Zero Clients or Thick Clients for SIPRNet connectivity provided in Building 1. The Government will provide (3) three cubicle spaces in Building 1 for Contractor support. The Contractor shall perform the remaining activities remotely or at a Contractor hosted Facility.

4.2 NORMAL HOURS OF OPERATION.

The Contractor shall have access to Building 1, to perform daily work hours, Monday through Friday, excluding all Federal Holidays. The Contractor shall provide SpOC EIS Service Desk support from 0730 through 1630 Mountain Standard/Daylight Time, for SpOC SharePoint and the FLDCOM ETMS2 users. If an Executive Order is declared, and

Government facilities are closed, at the Contractors discretion, may treat the Executive order the same as the holidays listed below or if applicable, perform duties at Contractor Facility or alternate location. See Table 4.1 for observed Federal Holidays.

Table 4.1, Federal Holidays Observed

4.2.1. The Contractor employees shall contact his/her supervisor for direction concerning late reporting, early release, or base closure due to inclement weather or incidents.

Government officials are not authorized to grant “administrative leave” or expend Government resources to compensate Contractor personnel to attend Government-sanctioned off-site events, morale building activities (e.g., picnics, golf outings, holiday parties, sports day events, fitness time). Military down days or Family Days are not considered Government holidays.

4.3 GOVERNMENT-FURNISHED EQUIPMENT (GFE) AND SERVICES:

The Government will provide the equipment necessary to perform duties, e.g., laptop, telephone, headsets, monitors, etc. IAW FAR 52.245-1. This will remain the property of the Government and shall be returned to the responsible Government Quality Assurance Personnel (QAP) upon request or at the end of the contract period of performance.

a. The Government will provide the Contractors supporting this PWS residing in a

Contractor hosted Facility with GFE computer equipment, to include monitors, keyboards, mice, CAC readers, etc., as applicable.

b. The Government will provide 3 (three) cubicle spaces and furniture to include

NIPRNet clients, SIPRNet Zero Clients, network printer/scanner/fax, and desk telephones. This equipment and office space is located at HQ SpOC, Building 1, on Peterson SFB, Colorado Springs, Colorado, 80914. All Contractor issued items will be tracked and managed by the Government.

4.4 OTHER REQUIREMENTS.

The Contractor shall provide to the Government all developed training curriculum and other official documents created.

All physical records, files, documents, and work papers provided and/or generated by the Government in preparation for or to assist the Contractor in performance of this contract, and all those generated for the Government by the Contractor in performance of this PWS shall become and remain solely the property of the Government. The Contractor shall transfer records, files, documents and work product to the Government or the successor Contractor at the direction of the Government at the end of the performance period. Nothing in this section alters the rights of the Government or the Contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS.

4.5 TRANSITION PHASE-IN/PHASE-OUT.

4.5.1 PHASE-IN: The Contractor shall accomplish Phase-in during the Government-defined phase-in period. The Contractor shall cooperate with the incumbent and the COR to ensure a smooth and orderly transition of Government services and knowledge transfer.

The Contractor personnel shall complete the below actions within 15 (fifteen) calendar days of contract award for overlap, permissions, access and accounts setup, and knowledge transfer.

a. The Contractor shall ensure all employees obtain a DoD Common Access Card (CAC) identification badge (ID badge) though their COR Integrated Computer-Aided Manufacturing (ICAM) Mission Partner Affiliation Sponsor (MPAS), formally known as Trusted Agent (TA).

b. The Contractor employees required to perform support in Building 1 and those Contractors who visit three (3) times a week or more shall submit information required for an AF Form 2586, Unescorted Entry Authorization Certificate, to the HQ SpOC/ESX, Security Office, for Building 1 to obtain a badge for unescorted access.

c. The Contractor shall provide a System Authorization Access Report (SAAR), DD Form 2875 to the HQ SpOC Field Services Technicians (formally known as a CST or CSL) for a Network Accounts (NIPRNet and SIPRNet). A DD Form 2875 shall be submitted for each Contractor employee for each network access required. The Contractor shall request a SIPRNet Token to obtain access to the SIPRNet when the account has been created.

4.5.2 PHASE-OUT: In the event the Contract ends or is no longer needed, the current Contractor personnel shall complete the below actions within 15 (fifteen) calendar days of contract end date and/or to accommodate the Phase-In Contract personnel, as stated below or necessary:

a. The Contractor shall ensure all employees turn in their DoD Common Access

Card (CAC) identification badge (ID badge) to the COR or HQ SpOC/ESX Security Office on the last day of their contract, or sooner if not needed.

b. For Contractor personnel who have a Restricted Area Badge for access to

Building 1, shall be escorted to and from the HQ SpOC/ESX Security Office in the Building 1 for Badge turn-in. In the event the Contractor needs access after badge turn-in, they can request to be escorted by the COR.

c. The Contractor shall request from the HQ SpOC Field Service Technicians (formally known as CST or CSL) to de-provision each Contractor employee’s NIPRNet and/or SIPRNet Network accounts on the last day of the contract, or sooner if no longer needed. The Contractor shall turn in all SIPRNet tokens issued to the COR.

d. The Contractor shall provide names of individuals who shall no longer need elevated permissions for NIPRNet and SIPRNet SpOC EIS applications, and work with incumbent Contractor in place to transfer permissions for these applications. (e.g., SharePoint, ETMS2), as necessary.

4.6 CONTRACTOR TELEPHONES

The Government will provide the already established SpOC EIS Service Desk Phone Number to the Contractor SpOC EIS Service Desk: Commercial 719-554-5363.

4.7 PRODUCT OWNERSHIP

1. IAW the data rights clauses of the contract, all products produced by the Contractor in the performance of this PWS shall be property of the Government.

2. The Government has unlimited rights to all deliverables developed under this PWS.

The Contractor shall not use any materials pertaining to this contract for business development or any other vendor strategic purposes.

3. The Contractor shall provide to the Government any developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, and/or documentation used to perform their duties.

4.8 TRAVEL

1. The Contractor shall travel to Buckley SFB to perform hands-on Collaboration Tools training for their users. Travel to Buckley SFB will be once a year, approx. 3-5 days long to include travel time.

2. The Contractor shall obtain written COR approval 14 business days prior to trip for travel in support of the mission requirements. The Government will only pay for travel expenses outside the normal commuting distance (50 miles). Travel expenses shall be billed in accordance with the Joint Federal Travel Regulations (JFTR).

4.9 SPOC EIS ENVIRONMENTS:

Environments of the SpOC EIS include:

1. SharePoint Online (SPO): Consists of a NIPRNet and SIPRNet SharePoint instance hosting numerous AF/SF Organizations in the Microsoft Cloud. SpOC will have site collections and shall provide Tier 1 and 2 by the SpOC EIS Solutions Team support, as needed. The Contractor shall utilize ServiceNow to submit Tier 3 requests for support in these environments, as needed.

2. FLDCOM NIPRNet and SIPRNet ETMS2: Consists of FLDCOM ETMS2 instances hosted by the Army and ETMS2 Support Desk provides Tiers 2 and 3 support and all O&M. The Contractor shall provide Tier 1 SpOC EIS Service Desk and SpOC Solutions Team support.

4.10 USSF COMMUNITY:

USSF Community is defined as SpOC, STARCOM, SSC and SWAC (until SWAC stands up fully), their Deltas, Geographically Separated Units (GSUs), and Detachments (Dets).

SharePoint sites will be managed by the organization Field Commands, their Deltas, GSUs/Dets and SWAC. FLDCOM ETMS2 site collections will be shared amongst these organizations and HQ SpOC will provide Service Desk support, license manage, ETMS2 Teams Management, and training.

4.11 SPOC SUPPORT CENTER SITE:

The SpOC Support Center is the primary location and authoritative source for Tier 0 "Self- Help" support documentation (i.e., checklists, users guides, Frequently Asked Questions, etc.) This Support Center shall provide support information for SharePoint, ETMS2, and other collaboration tools, along with training registration sign-ups, ETMS2 license requests, and CAB submission area.

4.12 TRAINING

The Contractor shall provide employees with the proper training and /or certificates to meet the minimum requirements of this PWS.

4.12.1 Other Government-Provided Training.

The Contractor’s employees may participate in other Government-provided training under the following circumstances:

1. The Contractor employees’ participation is on a space-available basis;

2. The Contractor employees’ participation does not negatively impact performance of this contract;

3. The Government incurs no additional cost in providing the training due to the Contractor employees’ participation; and

4. Man-hours spent due to the Contractor employees’ participation in such training identified in this Section 4.12 are not invoiced to the Contract.

4.13 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. 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 Procuring Contracting Officer (PCO) immediately. If any action(s) constitute or are perceived to create personal services, it shall be the Contractor’s responsibility to notify the Task Order (TO) Contracting Officer (CO) or Contracting Officer Representative (COR) within 24 hours of perceived action/direction.

4.14 DATA RIGHTS AND NON-COMMERCIAL SOFTWARE

In order to implement the provisions at DFARS 252.227-7013(b) and (e) and DFARS 252.227-7014(b) and (e) and DFARS 252.227-7017, the Contractor shall disclose to the ordering CO and ordering office in any proposal for a contract, or after award of a contract if not previously disclosed in the proposal, any technical data or non-commercial computer software and computer software/source code documentation developed exclusively at Government expense in performance of the contract. This disclosure shall be made whether an express requirement for the disclosure is included or not included in the PWS or solicitation for the order. The disclosure shall indicate the rights asserted in the technical data and non-commercial computer software by the Contractor and rights that would be acquired by the Government if the data or non-commercial software was required to be delivered under the contract and its deliverables requirements and any cost/price associated with delivery. This disclosure requirement also applies to segregable software routines of non-commercial software that may be developed exclusively at Government expense to integrate

Commercial Software components or applications provided under a commercial software license or developed to enable Commercial Software to meet requirements of this contract.

Performance of this disclosure requirement shall be considered a material performance requirement of any contract under which such technical data or non-commercial computer software is developed exclusively at Government expense.

4.14.1 Software Support and Data Rights.

Unless specified otherwise in the contract, the Contractor shall fully support all unique software developed to support integrated solutions on this contract. The Contractor shall be able to support all software revisions deployed or resident on the system, and sub-systems.

4.15 Manuals and Supplemental Data. The Contractor shall provide documentation for all systems services delivered under this contract. The Contractor shall provide commercial manuals, supplemental data for commercial manuals, and documentation IAW best commercial practices (i.e., CD-ROM, etc.). This documentation shall include users’ manuals, operators’ manuals, maintenance manuals, and network and application interfaces if specified in the contract.

5.0 SERVICE SUMMARY

Performance Objective

PWS

Paragraph

Performance Threshold

(PO-01) Customer Training 3.3.1

98% of the time, the Contractor shall:

- Schedule monthly EIS training

- Ensuring facility and computers are in good working order

- Ensure training curriculum is complete and updated

- Update any accounts needed (ETMS2) prior to training

- Track survey results from each training session to ensure customer training needs are met.

(PO-02) Service Desk Support 3.3.2

- Respond 98% of the time to telephone calls, voicemails, instant messages, and/or emails within 1 hour for NIPRNet and within 2 hours for SIPRNet

- Respond within 3 hours for the remaining 2% of the time

(PO-03) Engineering Services 3.4

99% of the time, deliver technical solutions within 30 calendar days of assignment from the COR or Change Advisory Board.

6.0 SECURITY REQUIREMENTS

6.1 The Contractor personnel shall all have at a minimum, an active SECRET Clearance at contract start.

6.2 Individuals performing work under this contract shall comply with applicable program security requirements as stated in the contract. The Contractor shall support the following levels of security: Unclassified; Controlled Unclassified Information (CUI).

Visitor Group Security Agreement (VGSA): The Contractor shall enter into a long-term visitor group security agreement for contract performance on base. This agreement shall outline how the Contractor integrates security requirements for contract operations with the Space Force to ensure effective and economical operation on the installation.

6.3 The Contractor shall ensure SpOC EIS applications comply with Operation Security

(OPSEC), Privacy Act (PA)/Freedom of Information Act (FOIA), contracting, Legal, and Foreign Disclosure requirements, and Section 508 (as amended) of the Rehabilitation Act of 1973 (20 U.S.C. 794d).

6.4 CONTRACTOR IDENTIFICATION.

6.4.1 The Contractors shall wear company identification badges to easily distinguish themselves from Government employees (e.g., corporate identification badges, Government-issued identification that reflects Contractor status, etc.) These badges must be conspicuously always displayed when working with Government personnel. Identification badges must be displayed above the waist at all times to allow for easy identification as a contractor employee or authorized sub-Contractor performing work for the Contractor. Badges shall be worn at all times when Contractor employees are co-located on a Government installation or when on temporary duty (TDY) working with other Government personnel. Sub-Contractor employees’ identification badges shall identify their respective prime Contractor.

6.4.2 The Contractors shall, when conversing with Government personnel during business meetings, over the telephone or via electronic mail, identify themselves as Contractor employees. Electronic mail signature blocks and business cards shall identify Contractor/company affiliation.

6.4.3 When collocated in space in a government facility, such as offices, separate rooms, or cubicles, work area must be clearly identified with Contractor-supplied signs, name plates or other identification, showing that these are work areas for Contractor or sub-Contractor personnel.

6.5 SYSTEM AND NETWORK AUTHORIZATION ACCESS REQUESTS.

For Contractor personnel who require access to DOD, DISA, or Air Force computing equipment or networks, the Contractor shall have the employee, prime or subcontracted, sign and submit a SAAR, DD Form 2875.

6.6 UNESCORTED ENTRY TO SECURE ROOMS.

Contractor personnel requiring unescorted entry to secure rooms designated by the installation commander shall comply with base access requirements. Contractor personnel shall be the subject of an adjudicated National Agency Check with Local Agency Check (NACLC) investigation to qualify for unescorted entry to a secure room. Contractor personnel shall contact their COR and the appropriate secure room monitor for permission.

6.7 REPORTING REQUIREMENTS.

Contractor personnel shall report to an appropriate authority (COR or CO) any information or circumstances of which they are aware may pose a threat to the security of DOD personnel, Contractor personnel, resources, and classified or unclassified defense information.

Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment and as required thereafter.

6.8 SECURITY.

6.8.1 Contractor employees shall comply with Force Protection Conditions (FPCON) procedures, Random Antiterrorism Measures (RAMS) per AFI 10-245, Antiterrorism (AT)Program Implementation,) per AFI 10-701, Operations Security (OPSEC), and local Emergency Management (EM) procedures. The Contractor shall safeguard all Government property including controlled forms provided for Contractor use. At the close of each work period, the Contractor shall secure Government training equipment, facilities, support equipment, and other valuable materials.

6.8.2 Operations Security (OPSEC). The contractor shall adhere to OPSEC guidance:

Be familiar with the organization’s Critical Information and Indicator List (CIIL) and ensure indicators & vulnerabilities are protected from disclosure per HQ SpOC countermeasures/measures. The contractor shall complete OPSEC in-processing training to include complete follow on OPSEC training such as event-driven and annual OPSEC training as required provided by the SpOC OPSEC Program Manager/Planner per DoDD 5205.02E, DoD OPSEC; DoD 5205.02, DoD OPSEC Manual; CJCSI 3213.01D, Joint OPSEC; and

AFI 10-701, OPSEC.

6.8.3 Compliance with DD Form 254, Contract Security Classification Specification, to include proper handling, storage, transmission, and destruction of classified materials to ensure no security violations or infractions to include OPSEC disclosures.

6.9 When necessary, assist the OPSEC PM/Signature Manager in conducting OPSEC internal assessments to ensure sufficient protection measures are in place to protect critical and sensitive information.

6.10 WIRELESS ELECTRONIC DEVICES.

Contract employees shall adhere to Prohibition of Mobile Wireless Devices within Building 1 (Hartinger Building) IAW Memorandum, dated 8 Feb 2023. Mobile devices with cellular or wireless transmit capabilities are prohibited anywhere within the Hartinger Building (Building 1). The prohibition includes, but is not limited to, laptops, tablets, cell phones, pagers, Global Positioning system transceivers, smart watches, fitness trackers equipped with wireless or cellular capability, Wi-Fi capable music players, wireless keyboards or mice, pointing devices, wireless headphones, wireless printers, and any other commercial wireless device, service, or technology. This policy does not apply to mobile devices having minimal storage and transmission capabilities such as key fobs used for medical alert, motor vehicles, or home security systems. This policy does not apply to fitness trackers or smart watches that do not contain camera, microphone, cellular, or Wi-Fi technology. Note that devices with such capabilities, even if not activated, are subject to the restrictions of this policy.

Additionally, Sensitive Compartmented Information Facilities and Special Access Program Facilities within Building 1 may apply more stringent controls to ban all fitness trackers and smart watches.

6.11 GOVERNMENT AUTHORIZATION.

The Contractor shall ensure its employees do not allow Government-issued keys to be used by personnel other than current authorized Contractor employees. Contractor employees shall not use keys to open work areas for personnel other than Contractor employees engaged in performance of duties.

6.12 ACCESS LOCK COMBINATIONS.

Access lock combinations are “For Official Use Only” and shall be protected from disclosure to unauthorized personnel. The Contractor shall adhere to the Air Force-activity operating instructions ensuring lock combinations are not revealed to un-cleared /unauthorized persons and ensure the safeguard procedures are implemented. The Contractor is not authorized to record lock combinations without written approval by the Government functional director.

6.13 SECURITY COMBINATIONS.

Combinations to security containers, secure rooms, or vaults are classified information and must be properly safeguarded. Only Contractor employees, who have the proper security clearance and the need-to-know, shall be given combinations to security containers, secure rooms, or vaults. Contractor employees shall properly safeguard combinations. Contractor employees shall not record security containers, secure rooms, or vaults combinations without written approval by the Government functional director. Contractors shall not change combinations to security containers, secure rooms, or vaults without written approval by the security officer and the Government functional director.

6.14 SECURITY EDUCATION AND TRAINING.

The Contractors are required to participate in the Government’s in-house and web-based security training program under the terms of the contract. The COR will provide the contacts for all training required to gain access to the on-line system/network(s). All Contractor employees shall complete all required security training by the deadline announced, annually.

7.0 DELIVERABLES

All deliverables and reports for this requirement are listed in the body of the PWS and in Appendix C – SpOC EIS Deliverables.

The Government reserves the right to review all deliverables for a period of ten (10) working days prior to acceptance. The Contractor shall not assume any data deliverable to be accepted by the Government until the 10-day period has passed, unless the Government explicitly states otherwise in this PWS of the applicable contract.

8.0 MANPOWER REPORTING

8.1 The Contractor shall report ALL Contractor labor hours (including sub-Contractor labor hours) required for performance of services provided under this contract for the HQ SpOC/SAIO via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://SAM.gov. See Appendix C, Item 2, SAM Manpower Reporting.

8.2 Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, the Contractor shall report all data no later than 31 October of each calendar year. The Contractor may direct questions to at https://sam.gov and search the “HELP” section. Should contractor have issues using SAM, they should contact the Federal Service Desk at https://www.fsd.gov.

9.0 CONTRACTOR PURCHASING

9.1 Other Direct Costs (ODC). There are no ODCs associated with this PWS.

http://sam.gov/ https://sam.gov/

APPENDIX A – ACRONYMS

AF Air Force DAFMAN Department of the Air Force Manual AFNet Air Force Network AT Anti-Terrorism CAB Change Advisory Board CAC Common Access Card CM Content Manager CMRA Contractor Manpower Reporting Application CO Colorado CO Contracting Officer COA Course of Action COR Contracting Officer Representative DD Department of Defense DISA Defense Information Systems Agency DOD Department of Defense DSN Defense Switched Network e.g. “for example” -- abbreviation for the Latin phrase exempli gratia EIS Enterprise Information Services EISSC Enterprise Information Services Support Center ETMS2 Enterprise Task Management Software Solution FLDCOM Field Command FOIA Freedom of Information Act FPCON Force Protection Condition FY Fiscal Year GSU Geographically Separated Unit HQ Headquarters IAW In Accordance With ICAM Integrated Computer-Aided Manufacturing ID Identification IT Information Technology ITE Information Technology Equipment JFTR Joint Federal Travel Regulation KMC Knowledge Management Center MPAS Mission Partner Affiliation Sponsor NIPRNet Nonsecure Internet Protocol (IP) Router Network OOTB Out-Of-The-Box OPSEC Operational Security OCONUS Outside Continental United States PA Privacy Act PAR Performance Assessment Report

PM Program Manager PWS Performance Work Statement RADS Records Archive Delivery System SBD Space Base Delta SCA Site Collection Administrator SFB Space Force Base SIPRNet Secret Internet Protocol (IP) Router Network SPO SharePoint Online URL Uniform Resource Locator US United States

APPENDIX B - APPLICABLE STANDARDS AND REFERENCES

The Contractor shall notify the CO within 30 days of receipt of revisions, changes, supplements, and notifications of rescission (including referenced publications in the PWS), if there is a cost impact is/are information for the Contractor as they apply to the original directive publication unless the referenced document is also included in this appendix as a directive publication. Supplements to that portion of a directive publication contained in the PWS are also a directive.

Documentation URL Paragraph Referenced Description

DoDI 8170.01, Online Information Management and Electronic Messaging, dated 2 Jan 19, change 1 24 Aug 21 https://www.esd.whs.

mil/Portals/54/Docu ments/DD/issuances/ dodi/817001p.pdf?ver =2019-05-24-092843-

All

Purpose: In accordance with the authority in DoD Directive (DoDD) 5144.02, this issuance:

• Establishes policy, assigns responsibilities, and prescribes procedures for:

o Conducting, establishing, operating, and maintaining electronic messaging services (including, but not limited to, e-mail) to collect, distribute, store, and otherwise process official DoD information, both unclassified and classified, as applicable.

o Managing official DoD information on the DoD Information Network and other networks, i.e., online.

AFI 10-701,

Operation https://static.e-publishing.af.mil/pr

Para 6.8

1.3.2. OPSEC is a process of

identifying, analyzing and controlling critical https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/817001p.pdf?ver=2019-05-24-092843-007 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/817001p.pdf?ver=2019-05-24-092843-007 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/817001p.pdf?ver=2019-05-24-092843-007 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/817001p.pdf?ver=2019-05-24-092843-007 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/817001p.pdf?ver=2019-05-24-092843-007 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/817001p.pdf?ver=2019-05-24-092843-007

Security

(OPSEC)

oduction/1/af_a3/pu blication/afi10-

701/afi10-701.pdf information indicating friendly actions associated with military operations and other activities to:

1.3.2.1. Identify those actions

that can be observed by adversary intelligence systems.

1.3.2.2. Determine what

specific indications could be collected, analyzed, and interpreted to derive critical information in time to be useful to adversaries.

1.3.2.3. Select and execute

measures that eliminate or reduce to an acceptable level the vulnerabilities of friendly actions to adversary exploitation.

APPENDIX C – SpOC EIS DELIVERABLES

Name PWS Para # Due Date Distribution Remarks

1. SpOC EIS Monthly

Performance Assessment Report

(PAR)

Para 2.1

Monthly activities/require ments documented, proposed contractor inputs due NLT 5th of the month after performance.

COR will provide formal PAR to

Contractor NLT 5th of the month.

Contractor will provide approve/ sign PAR NLT than the 10th of the month.

• COR & Alt COR

PAR Form provided by

SAIO

Requirement: (Contractor inputs format acceptable) As a minimum, the PAR inputs shall detail Monthly Tasks/Activity Status for each Task area, meetings supported, issues or risks requiring Government resolution or mitigation, benefits to the Government, and provide an overall self-assessment of the Contractor’s performance during the reporting period.

2. SAM Manpower Reporting

Application Para 8, 2 - Annually, NLT 31 Oct

N/A Electronic

Requirement: Report Contractor direct labor hours and dollars (to include Subcontractor hours and dollars) required for performance of services provided under this contract. Fill in in all required data fields.

Information provided is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars.

3. FLDCOM ETMS2

License Report

Para 3.1.2, iii

Bi-Monthly Report of how many

ETMS2 license holders assigned and track organizational

•…