FA521526N0001 Supplemental IT PWS_Appendix X.pdf

Performance Work Statement for

Maui Base Support Services Information Technology (MBSS-IT) Services

XX Month 2025

Table of Contents

Chapter 1

1.0 Scope

1.2 Overview of Principle Systems

1.2.1 Network Infrastructure

1.2.2 Network Operations (NetOps)

1.2.3 Client Systems Team (CST)

1.2.4 Base Equipment Control Office (BECO)

1.2.5. Cybersecurity Office

1.2.6. Communications Focal Point

1.2.7. Local Registration Authority (LRA)

1.2.8. Communications Security (COMSEC)

Chapter 2

2.0 Program Management

2.1 Government Management Team (GMT)

2.2 Coverage Hours

2.3 Mission-Essential Contractor Services

2.4 Contractor Manpower Reporting

2.5 Personnel Management

2.5.1 Staffing

2.5.2 Contractor Employees

2.6 Contractor Reimbursable Travel

2.7 Quality Control Plan (QCP)

2.8 Training

2.8.1 Contractor Specialized Training

2.8.2 Ancillary Training

2.8.3 Training Records

2.8.4 Training and Education Costs

2.9 Program Management Support

2.9.1 Self Inspection/ Management Program

2.9.2 Meeting Support

2.9.3 Monthly Activity Report (MAR)

2.9.4 Administrative Support

2.9.5 Publications Support

2.9.6 Records Management / Privacy Act Programs

2.10 Phase-In/Phase-Out

2.10.1 Phase-In Plan

2.10.2 Phase-Out Plan

2.11 Maintenance and Equipment Accountability

2.11.1 Property Custodian (PC)

2.11.2 Preventative Maintenance Inspections (PMIs)

2.11.3 Supplies and Materials

Chapter 3

3.0 Network Infrastructure

3.1. Maintenance Management

3.2 System Outages

3.3 System Notices

3.4 Voice over Internet Protocol (VoIP)

3.5 Security/Patch Configuration Administration

3.6 Compliance Tracking and Reporting

3.7 Support Services/Maintenance Contracts

3.8 Asset Management

3.9 Sustainment and Equipment Technical Refresh

3.10 Base Communications

3.10.1 Operate and Maintain (O&M) Requirements

3.10.2 Work Order Requirements

Chapter 4

4.0 Network Operations

4.1 Network and Server Equipment Management

4.2 Operations and System Administration Services

4.3 Network Monitoring, Performance and Trend Analysis Services

4.4 Software Configuration Management

4.5 Management of Connectivity to External Networks

4.6 Network Integrity

4.7 Computer Systems Security

4.8 Time Compliance Network Order (TCNO)

4.9 Notice to Airman (NOTAM) and Maintenance Tasking Order (MTO)

4.9.1 NOTAM

4.9.2 MTO

4.10 Sustainment and Equipment Technical Refresh

4.11 System Outages

4.12 Trouble Ticket Management

Chapter 5

5.0 Client Systems Technicians (CST)

5.1 Scope of Work

5.2 General Duties

5.2.1 Client Service Technicians (CSTs)

5.2.2 User Account Management

5.2.3 Ticket Management

5.2.4 Partnership Collaboration

5.2.5 Priority and Dedicated Services

5.2.7 Projects

5.2.8 Contractor Program Management

Chapter 6

6.0 Information Technology Asset Management (ITAM)

6.1 Equipment Control Officer (ECO) Responsibilities

6.2 Property Custodian Assistance/Management

6.3 Maintain Property Custodians for the ITAM warehouse account

6.4 Base Software License Management

6.5 General Responsibilities

6.5.2 Certification of Special Equipment

6.5.3 Personnel Management

6.5.4 Account Maintenance

Chapter 7

7.0 Cybersecurity Office and Information/Communication Systems Support

7.1 Cybersecurity Office

7.1.2 Computer Security

7.1.3 Cybersecurity Awareness

7.2 TEMPEST

7.3 Risk Management Framework (RMF) Authorization Service

7.4 Cyber Readiness (CR) Support:

7.4.1 Vulnerability Management

7.4.2 Program Documentation

7.5 COMSEC/SVRO Requirements

7.6 Travel

Chapter 8

8.0 Communications Focal Point (CFP)

8.1 Scope of Work

8.1.1 On-Site Requirements

8.1.2 Required Qualifications

8.2 General Duties

8.2.1 Comm Focal Point Technicians

8.2.2 CFP Contact Methods

8.2.3 Request Prioritization

8.2.4 On-Call/After Hour Support

8.2.5 Initial Contact Support

8.2.6 NIPRNET Email Organization Box

8.2.7 SIPRNET Email Organization Box

8.2.8 JWICS Email Organization Box

8.2.9 Network Notifications

8.3 User Account Management

8.3.1 User Account Management Tools

8.4 Ticket Management

8.4.1 Prioritization

8.5 Partnership Collaboration

8.5.1 Special Notices

8.5.2 Anomalies

8.5.3 Notification of Bad Actors or Malicious Intent

8.6 Priority and Dedicated Services

8.7 Projects

8.8 Contractor Program Management

8.8.1 COR Duties

8.8.3 Problems of Performance

8.8.4 New or Revised Process Data

8.9 Negligent Discharge of Classified Information (NDCI)

8.9.1 Responsibilities for Classified Incidents

8.9.2 NDCI Actions

8.10 Approved Service Interruption (ASI)

8.10.1 CFP Standard Operating Procedures (SOP) for ASIs

8.11 Personl Wireless Communication Systems

8.11.1 Land Mobile Radios (LMRs)

8.11.2 Mobile Cellular Devices

Chapter 9

9.0 Local Registration Authority (LRA)

9.1 Scope of Work

9.2 Required Qualifications

9.3 General Duties

9.3.1 Additional General Duties

9.3.2 After Hours

9.3.3 Coordination

9.4. Records

9.5 Reporting

Chapter 10

10.0 Service Summary Items

10.1 Performance Objectives/Thresholds

Appendix A – Deliverables (Contractor Provided / Government Approved)

Appendix C

APPENDIX D – PUBLICATIONS

Chapter 1

Contract Scope

1.0 Scope: The scope of this contract encompasses all core communications services, CE industrial controls systems, and security forces electronic security systems to support the operation, maintenance, logistics, research and development (R&D) of 15th Space Surveillance Squadron (15th

SSS).

1.2 Overview of Principle Systems

1.2.1 Network Infrastructure: The 15th SpSS network infrastructure is comprised of approximately

45 switches, 5 routers, 66 servers and approximately 10 cryptographic devices providing core communications network services to 15th SpSS. Provide installation, operation and maintenance of cabling infrastructure at 15th SpSS regardless of network (Chapter 3).

1.2.2 Network Operations (NetOps): The 15th SpSS NetOps manages approximately 66 servers located on Maui supporting multiple users across the island (Chapter 4).

1.2.3 Client Systems Team (CST): The CSTs provide core communications client-level support to approximately 250 users within 15th SpSS (Chapter 5).

1.2.4 Base Equipment Control Office (BECO): BECO oversees and directs Information Technology

Equipment Custodian (ITEC) account (FU2350) at 15th SpSS (Chapter 6).

1.2.5. Cybersecurity Office: Provide cybersecurity support to 15th SpSS personnel accessing core communications information systems (Chapter 7).

1.2.6. Communications Focal Point: Provide communication focal point duties supporting 15th SpSS personnel accessing core communications information systems (Chapter 8).

1.2.7. Local Registration Authority (LRA): Provide LRA services supporting 15th SpSS (Chapters 9).

1.2.8. Communications Security (COMSEC): Provide CRO, SVRO and CAP services for 15th SpSS. The

Maui Site has approximately 105 cryptographic devices (Chapter 7).

Chapter 2

Program Management

2.0 Program Management

Provide all personnel necessary to perform MBSS PWS requirements. The contractor’s furnished materials and equipment shall include all other direct costs (ODCs) which the contractor believes necessary to perform these requirements. Core Communications ODCs shall be accountable in CLIN XXXX.

2.1 Government Management Team (GMT)

Notify the GMT of any problems affecting the contractor’s performance impacting mission accomplishment or any issues the contractor considers not within the scope of this contract. The GMT consists of the

Contracting Officer (CO), the Government Functional SME, the Contracting Specialist (CS) and the

Contracting Officer’s Representative (COR).

2.1.1 Provide a Program Management Plan (reference Appendix A), which includes:

a) Organization and management structure

b) Communication plan

c) Risk management plan

d) Quality control plan

e) Training plan

2.2 Coverage Hours

Contractor shall follow coverage requirements outlined in MBSS main PWS section 1.1.2. Coverage time may be changed at request of the COR per as needed operations.

2.3 Mission-Essential Contractor Services

Ensure continued support of all locations identified in this PWS during crises, as required by DoDI 1100.22, policy and procedures for determining workforce mix, and unless otherwise directed by the COR. Provide

Mission-Essential Contractor Services IAW Defense Federal Acquisition Regulation Supplement (DFARS)

252.237-7023, Continuation of Essential Contractor Services, for providing assurance of continuation of mission essential services during crises conditions (reference Appendix A). SIPRNet services for all facilities and VoIP at MSSC are to be considered Mission Essential. Refer to MBSS main PWS section 1.3.5 for overtime hours accounting.

2.4 Contractor Manpower Reporting

2.4.1 For performing work under CLIN XXXX, projects shall provide a SOW including all labor, materials, equipment and any other information necessary to complete the SOW to ensure a complete and usable product. Over and above projects for Core Communications functional work shall be mirrored in regards to management, execution, and closeout to how performed to the civil engineering functional area. Reference

MBSS main PWS section 6.

2.5 Personnel Management

2.5.1 Staffing. Personnel management shall include:

a) Staffing with qualified workforce, where employees have a strong foundation of experience and skills. A bachelor’s degree is not a prerequisite for qualification, as employees with significant relevant experience and a proven track record of success can also be considered qualified.

b) Full staffing to ensure coverage by qualified employees who have the required security clearance at the beginning of the period(s) of performance and throughout the life of the contract. Also, all employees who will require elevated privileges, such as administrator or root access, to perform specialized functions or maintenance tasks on an information system, shall have the appropriate and current certifications and security clearance at the beginning of the period(s) of performance and throughout the life of the contract.

c) The employee shall maintain their certifications through continuing education and professional development, as required by the certification vendor.

d) Recruiting and retaining qualified individuals and only requesting waiver/substitutions to required qualifications in exceptional situations.

e) At the direction of the government, realignment of contractor priorities to accommodate for workload surges and for technical orders (TOs) with short Deadlines for compliance.

2.5.2 Contractor Employees

2.5.2.1 All contractor employees who interface with the Government, either electronically or in person shall be able to read, write, speak, and understand English.

2.5.2.2 Select personnel who are fully qualified and have the necessary security clearances to provide the

Government the services required by this PWS.

2.5.3 The Installation Commander may direct the contractor, in writing, to remove any employee from the installation when retention of such employee endangers life, property, security, or where such an employee violates reasonable and necessary base regulations or displays improper behavior.

2.5.4 When a mishap occurs or an employee displays improper behavior, the Government reserves the right to immediately remove an individual from the installation.

2.6 Contractor Reimbursable Travel The contractor may be required to travel for this contract outside the

Maui Island. The contractor shall follow the Government’s travel regulations and procedures (Joint Travel

Regulations). Travel under this section shall be covered under CLIN XXXX.

2.7 Quality Control Plan (QCP)

IT Manager, in coordination with the MBSS Quality Control Manager shall develop a highly effective QCP for all services provided under this PWS. The QCP shall remain in effect during the term of the contract

(including any option periods if exercised). The IT Manager shall: maintain the QCP; retain a copy on site;

and ensure availability at all times to all members of their on-site staff, as well as the GMT. The

Contractor’s QCP shall reflect, centralized maintenance and remote monitoring from 15th SpSS and refrain from relying on GMT to ensure their own quality control. The Contractor shall notify the parties specified in this paragraph of any changes to the QCP at least 10 workdays prior to implementation of those changes.

The QCP shall also include procedures for training, qualification and any required certification of employees prior to performance of assigned duties under this contract. Procedures shall include assignment of management responsibility for employee task qualification to specific positions/individuals within the

Contractor’s organization, as well as the quality control process that will be utilized to ensure compliance and a description of the records to be kept to document inspections and corrective or preventive actions taken. The records of inspections shall be kept and made available to the Government throughout the contract performance period and for the period after contract completion until final settlement of any claims under this contract.

2.8 Training

2.8.1 Contractor Specialized Training

2.8.1.1 Ensure personnel are properly trained and have appropriate DoD approved cybersecurity baseline certification(s) before performing any network operations tasks. Provide the GMT copies of the appropriate certification(s) prior to being given privileged access to the network and/or assuming cybersecurity responsibilities and ensure they remain in good standing. All contractor personnel shall complete and sign a formal statement of assigned cybersecurity responsibilities. Immediately remove personnel not in good standing from cybersecurity tasks. Maintain the currency of employees by providing initial and refresher training as required to meet the PWS requirements.

2.8.1.2.2 Contractor personnel administratively working on any network shall be certified at the DoD-approved cybersecurity workforce certification(s) appropriate for each technical or managerial level as listed in DoD and DAF regulations.

2.8.1.2.3 The certification/qualification program is to be contractor self-contained, requiring no technical or materiel support from the Government and is subject to Government review.

2.8.1.3 The contractor is responsible for training on any new technology recommended to the government for implementation.

2.8.2 Ancillary Training

2.8.2.1 Participate in ancillary training IAW applicable documentation (instructions, standards, etc.).

2.8.2.2 At a minimum, the following Government provided courses via the MY TRAINING application, Computer Based Training (CBT), or classroom attendance shall be completed within thirty (30) days after contract award (Table 2-1 – Ancillary Training). Other training may be required at the request of the COR.

The training records shall contain, at a minimum, the completed/signed formal statement of assigned cybersecurity responsibilities and copies of the appropriate certifications.

Table 2-1 – Ancillary Training

Ancillary Training Course Frequency Method/Platform Completion

Date

Initial Security Briefing One-Time Brief Within 3 days

Initial Information Security Training Annual Security SharePoint Within 3 days

Cyber Awareness Challenge Annual myLearning Within 3 days

Force Protection Annual myLearning Within 60 days

PRS Annual OPSEC and OSI Training Annual Security SharePoint Within 60 days

DAF Operations Security Awareness Annual myLearning Within 60 days

Records Management – User Annual myLearning Within 60 days

Controlled Unclassified Information

(CUI)

Annual myLearning Within 60 days

PRS Continuity of Operations Plan

(COOP)

Annual myLearning Within 60 days

PRS AFRL Initial-Annual Fire

Extinguisher

Annual JKO Within 60 days

2.8.3 Training Records

2.8.3.1 The contractor shall maintain training records on all their personnel and make these records available for Government review within four (4) hours of request. The contractor shall be properly trained and certified before performing any network operations tasks.

2.8.3.2 The contractor shall submit any requests with estimated costs for Government sponsored training, conferences, seminars and workshops that are in areas related to technology used in Cyber to the COR for recommendation and the CO for approval.

2.8.3.3 The contractor shall keep current on commercial applications and provide training to their employees to maintain a well-trained workforce.

https://play.apps.appsplatform.us/play/e/default-8331b18d-2d87-48ef-a35f-ac8818ebf9b4/a/933428bb-4dba-44a8-99be-a20e6ca4cfe4?tenantId=8331b18d-2d87-48ef-a35f-ac8818ebf9b4 https://play.apps.appsplatform.us/play/e/default-8331b18d-2d87-48ef-a35f-ac8818ebf9b4/a/933428bb-4dba-44a8-99be-a20e6ca4cfe4?tenantId=8331b18d-2d87-48ef-a35f-ac8818ebf9b4 https://lms-jets.cce.af.mil/moodle/course/view.php?id=12955 https://lms-jets.cce.af.mil/moodle/course/view.php?id=12955 https://lms-jets.cce.af.mil/moodle/course/view.php?id=13624 https://lms-jets.cce.af.mil/moodle/course/view.php?id=13624

2.8.4 Training and Education Costs

The Government will provide training and materials as new or modified systems come online. Specialized

Government provided training (e.g., not commercially available) may be required as directed and equitable adjustment will be negotiated as required. Training that is Government specific will be reimbursed to the contractor utilizing standards set forth by the Joint Travel Regulation via CLIN XXXX. Training that is required for development of skills, conferences, and required general certifications are not accountable for reimbursement from the Government. The GMT reserves the right to pre-determine accounting on a case-by-case basis per training event.

2.9 Program Management Support

2.9.1 Self Inspection/ Management Program

Utilize the current Government self-inspection/management program, i.e., Management Internal Control

Toolset (MICT) or its follow-on system. The contractor shall establish MICT accounts and maintain up-to-date compliance checklists for use during assessments. Applicable check lists/sheets shall be utilized, and pertinent data shall be entered into the MICT system. Training will be provided by the Government, as needed.

2.9.2 Meeting Support

Support the Government during reviews and meetings. Meetings include, but are not limited to, teleconferences, MAJCOM Meetings, Engineering Change Requests (ECR), Configuration Control Boards

(CCB), Communications Sync-Up, Cybersecurity and Cyber Readiness (CR).

Participate in and/or, support conferences, technical and operational meetings, working groups and reviews with coordination with the Government Functional SME. Some meetings are scheduled weekly or monthly, others are ad hoc meetings to discuss immediate emergencies. Provide the appropriate personnel as required by the agenda to clarify technical details, determine solutions or recommendations, or for other technical expertise. Examples of these meetings are CCB, and/or ECR meetings to review, discuss and receive approval for new requirements.

2.9.3 Monthly Activity Report (MAR)

The contractor will provide a monthly activity report capturing all work center activities (See Appendix A).

2.9.4 Administrative Support

2.9.4.1 Documentation

2.9.4.1.1 Responsible for creating, maintaining, and delivering Government-required documents, records, and reports used for accomplishment of MBSS-IT requirements. Deliverables will be provided to the

Contracting Officer in a contractor developed, government approved format.

2.9.4.1.2 Provide the original record or a reproducible copy of record within five working days of receipt of request from the CO or GPM.

2.9.4.1.3 All documentation, products, and data developed in support of the MBSS contract are the property of the US Government.

2.9.5 Publications Support

2.9.5.1 Contract/Work Center Operating Instructions (OIs)/Standard Operating Procedures (SOPs)

The contractor shall develop their own OIs/ SOPs (See Appendix A). The OIs/SOPs shall be implemented, maintained, and complied with. All OIs/SOPs required for compliance will be accepted by and accessible to the GMT. Contract OIs will address contract wide direction/policy. Work center OIs/SOPs will address work center specific direction/policy/ procedures. All OIs/SOPs, once accepted by the GMT, will become directive in nature. Annually review all OIs/SOPs to ensure they are accurate and update when necessary.

All OIs/SOPs become the property of the Government, will be maintained by the contractor and will be stored in the Government approved location.

2.9.5.2 New Directive Publications

Review new/updated publications (draft and final) to assess technical content and impact to the MBSS contract. Notify the Government Functional SME within 30 days of receipt if there are potential risks or costs to the MBSS contract.

2.9.6 Records Management / Privacy Act Programs

2.9.6.1. Contractor shall comply with all applicable records management laws and regulations, as well as

National Archives and Records Administration (NARA) records policies, https://www.archives.gov/records-mgmt/policy/records-mgmt-language including but not limited to the Federal Records Act (44 U.S.C. chs.

21, 29, 31, 33), NARA regulations at 36 CFR Chapter XII Subchapter B, and the AFI 33-322, Records

Management and Information Governance Program, those policies associated with the safeguarding of records covered by the Privacy Act of 1974 (5 U.S.C. 552a). These policies include the preservation and unauthorized disposing of all records, regardless of form or characteristics, mode of transmission, or state of completion.

2.9.6.2 All contractor employees assigned to this contract who create, work with, or otherwise handle records are required to take Agency-provided records management training. The contractor is responsible for confirming training has been completed according to agency policies, including initial training and any annual or refresher training and provide their completion of training to the COR and/or Unit RM POCs.

2.9.6.3 Contractor functions should identify personnel to be trained. When no records professional is assigned or identified, the contractor quality assurance evaluator is responsible for all lifecycle record management and all duties assigned to the records professional as IAW AFI33-322, paragraph 1.3.6.

2.9.6.4 Contractors shall comply with the Privacy Act of 1974, Title 5, U.S.C. Section 552a, and the agency rules and regulations issued under the Act., Privacy Act Notification, and 52.224-2, Privacy Act and AFI33-

332, Air Force Privacy Act and Civil Liberties Program. These policies, includes operation of any system of records on individuals to accomplish agency functions, performing activities associated with maintaining system of records to include personally identifiable information (PII) collection, maintenance, use, dissemination of records of. Comply with the requirements in protecting PII as IAW the OMB Memo 17-

12, Preparing for and Responding to a Breach of Personally Identifiable Information. The contractor shall ensure that initial privacy training and annual privacy training, thereafter, is completed and provide their completion of training to the COR. No contractors shall be allowed to access the system of records, unless the employee has completed the privacy training.

2.10 Phase-In/Phase-Out

2.10.1 Phase-In Plan

The successful contractor shall deliver a phase-in plan (See Appendix A) within 15 days of contract award.

The GMT will meet with the contractor to review implementation of the phase-in plan.

2.10.2 Phase-Out Plan

Develop and implement a transition plan for phase-out (See Appendix A). Establish procedures with the successors to ensure a smooth transition of all requirements. Maintain overall contract responsibility until the completion of the contract PoP. Ensure all responsibilities are transferred ensuring no degradation in service.

2.11 Maintenance and Equipment Accountability

2.11.1 Property Custodian (PC)

Appoint a work center alternate property custodian and maintain IT assets and Defense Property

Accountability System (DPAS) accounts for all Government-owned hardware and software under the

Network Infrastructure, Network Operations, Client System Technicians, and the Base Equipment Control

Office AOR IAW AFMAN 17-1203 Para 2.3.8.

https://www.archives.gov/records-mgmt/policy/records-mgmt-language https://www.archives.gov/records-mgmt/policy/records-mgmt-language

2.11.2 Preventative Maintenance Inspections (PMIs)

The contractor shall perform PMIs according to applicable technical manuals and use Government approved non-proprietary commercial practices to schedule and track all maintenance actions in both the Network

Operations and Network Infrastructure work centers (similar to NextGen Chapter 7, Civil Engineering –

Facility Operations and Maintenance). The contractor shall coordinate with the Government and will ensure

PMI intervals are established if no intervals are specified in the technical manuals.

2.11.3 Supplies and Materials

The contractor shall be responsible for acquiring IT consumables via CLIN XXXX. The contractor shall report the status of total purchases quarterly to the COR.

Consumables means items meant for single use and/or items requiring regular reoccurring purchases as they are quickly used and need to be replaced often (e.g. cables, discs, SD cards, printer ink, IT cleaning items).

Additionally, auxiliary items to support the functionality of devices such as computers, servers, printers etc.

(e.g. mouse, keyboard, headset, surge protectors) are consumables.

The contractor shall acquire project materials for core communications networks in support of reoccurring maintenance and Direct Scheduled Work (as defined under PWS 7.3.4, Table 7.2) under CLIN XXXX, with prior approval from the Government. Project materials for core communications networks in support of

Facility Projects (as defined under PWS 7.3.4, Table 7.2) shall be acquired by the contractor under CLIN

XXXX, with prior approval from the Contracting Officer via written Notice to Proceed (NTP).

The contractor shall acquire IT Tools under CLIN XXXX when and as directed by the Contracting Officer via written Notice to Proceed (NTP). Ownership of all IT Tools shall be transferred to the government upon delivery.

IT Tools means items meant for multiple uses and/or long-term use (usually more than a year), and which are irregularly purchased or replaced (e.g. IT toolkits, label makers, IT workbench).

Chapter 3

Network Infrastructure

3.0 Network Infrastructure

Perform on-site operations and maintenance activities as defined in MBSS main PWS section 1.1.2, with on-call/after hour support 24 hours a day, 7 days a week including holidays. Plan, schedule, direct, organize, coordinate, and execute all actions necessary to conduct continuous operations and sustainment of the Core

Communications networks and Base Communications (BC). The BC consists of the inside plant (ISP) cabling, outside plant (OSP) cabling, handholes, manholes, Antenna transmission systems, Preventative

Maintenance Inspections (PMI), and all associated equipment, which may include other systems (e.g. radio, etc). The Contractor is solely responsible for ensuring sufficient personnel are assigned to this contract and all personnel are qualified and certified to perform the requirements listed herein, including those qualifications and certifications required by the OEM requirements to maintain, install, or operate the equipment covered by this contract including current certifications for all voice switching systems.

3.1. Maintenance Management

3.1.1 Assign and track communication system outages and repair actions, and coordinate with internal and external maintenance agencies (i.e., Mission IT, third-party vendors, host base, program management offices, etc.) to isolate faults, restore service and make repairs and document within Government Provided ticketing system.

3.1.2 Maintain maintenance management continuity documentation (maintenance processes, contact phone numbers, circuit outage procedures, etc.). Update and maintain architectural network infrastructure diagrams within MS Visio and store within the Government approved location as each change occurs.

3.1.3 Oversee daily scheduled and unscheduled maintenance. The contractor shall track all customer submitted trouble tickets in government provided ticketing system. The contractor shall track all customer submitted new installs using government provided system. The contractor shall respond to all customer submitted trouble tickets within the timeframe specified in appendix C. The contractor shall open trouble tickets for all required maintenance actions that they discover, or that are identified to them by the

Government Functional SME.

3.1.4 Prepare and modifying job schedules depending on mission priorities.

3.1.5 Track equipment and circuit outages through restore and reactivation of services.

3.1.6 Identify system process improvements to the Government Functional SME for review prior to implementation.

3.1.7 Notify and provide written corrective recommendations to the Government Functional SME of any equipment or service that is failing or degrading the network performance and may require corrective action within five business days of discovery.

3.1.8 Perform Infrastructure enterprise-wide network administrative activities. These activities may include remote administration/access, 802.1x, network monitoring/traffic analysis, Internet Protocol (IP) management, system setup, Dynamic Host Configuration Protocol (DHCP) Scope management, Information Technology (IT) device configuration and installation, troubleshooting, monitoring, security, infrastructure installation, network protocols, and network encryption systems.

3.1.9 Perform configuration changes, including configuration, installation and management of IT devices, as required. Comply with Department of the Air Force (DAF) regulations and local change/configuration procedures.

3.1.10 Developing Maintenance Operating Instructions (MOI) and Standard Operating Procedures (SOP), as applicable.

3.1.11 Upon discovery of any security system problems/incidents on core communications networks, report them to the 15th SpSS Cybersecurity Office and notify the Government Functional SME within four (4) hours

(next duty day if after hours).

3.2 System Outages

The contractor shall notify the Government Functional SME and/or the Chief Information Officer (or equivalent, or their designee) verbally and in writing as soon as system outages are discovered. (Note:

Exceptions to time limits may be allowed with written approval from the Chief Information Officer. In such cases, the contactor shall make this work high priority until remedied. The contractor shall provide updates to the Chief Information Officer (or equivalent, or their designee) and the Communications Focal Point in writing hourly until the outage is remedied. For outages beyond the scope of responsibility for the contractor

(i.e., higher level outages), the contractor shall coordinate with the appropriate higher-level organization to provide a solution to the outage or issue. Once the outage has been resolved, the contractor shall document the issue, document the fix action, and provide an update to the Chief Information Officer (or equivalent, or their designee) and the Communications Focal Point.

3.3 System Notices

The contractor shall implement advisories such as Notices to Airmen (NOTAM), Time Compliance

Network Orders (TCNO), Field Engineering Notices (FEN), System Advisory Notices, Heads Up Messages

(HUM), Air Force Computer Emergency Response Team (AFCERT), Time Compliance Technical Order

(TCTO), Task Order (TASKORD), Major Command Communications Control Center (MCCC) Email taskers, service packs and security patches as directed by the Government. The contractor shall perform bi-monthly reboot of backup/file servers to ensure TCNO compliance. The contractor shall respond to system notices in accordance with notice instructions. The contractor shall implement countermeasures identified by the advisory within the timeframe specified by the advisory or by the Chief Information Officer (or equivalent, or their designee). If the countermeasures cannot be implemented by the date noted within the

TCTO, TCNO or MTO, the contractor shall document the inability thru approved government methods, e.g.

POA&M, and receive approval from the Designated Approving Authority (DAA) and the Chief Information

Officer (or equivalent, or their designee) to either take an alternative corrective action or to continue operations without the countermeasures.

3.4 Voice over Internet Protocol (VoIP)

The contractor shall support VoIP initiatives: Manage, monitor, sustain, and employ VoIP processing systems and infrastructure. Provide technical guidance and comprehensive solutions for VoIP requirements.

Implement VoIP solutions and manage resources to ensure services are available to meet the mission requirements. For new VoIP phones, the contractor shall test the cabling and map the port for E-911 location services before connecting it to the network. Once connected, the contractor provisions the phone in the call manager. NOTE: VoIP infrastructure hardware, i.e., gateways & call managers, E-911, Sensaphone, paging system and any associated equipment, shall be maintained by the contractor. VoIP instruments shall be maintained by the contractor technicians to include troubleshooting, and repair.

3.4.1 Participate in the planning, testing and execution of software, equipment, network management devices, application and database integration prior to deployment on the operational networks. This includes firmware and/or software updates to routers, switches, and Cryptographic devices as required due to End-of-

Life equipment or Defense Information System Agency (DISA), Security Technical Implementation Guide

(STIG)s/NOTAM’s.

3.4.2 Poll all nodes daily to confirm system status and analyze any trends that indicate degradation of equipment or data links to meet performance thresholds.

3.4.3 Document in MS Visio, all changes to the network systems configurations within ten (10) days after they occur to ensure network architecture documentation/drawings are up to date and stored in Government approved location. The drawings shall be made available upon Government Functional SME request.

3.5 Security/Patch Configuration Administration Ensure all patches are accomplished IAW government directives. Create, update and maintain login/logout scripts to check for patch compliancy daily.

3.6 Compliance Tracking and Reporting Comply with all applicable NOTAMs, Time Compliance

Network Orders, MCCC Email Taskers, Network Task Orders released by the Government within the specified timeframe. Compliance status and reporting shall be accomplished IAW MPTO 00-33A-1109 para 3.2.10 (or current regulation).

3.7 Support Services/Maintenance Contracts

3.7.1 Review and track Infrastructure Hardware (HW)/Software (SW) warranty maintenance coverage in the

MAR and notify the Government Functional SME on the status of the warranties. (See Appendix A)

3.7.2 Assess HW & SW of the Infrastructure systems and deliver a plan for technical refresh on an annual basis (See Appendix A). The plan shall include End of Life/End of Service (EOL/EOS) dates and recommended equipment replacements that integrates with existing equipment.

3.8 Asset Management

3.8.1 Perform Government asset management activities (i.e., IT Control Officer, Government provided spares, etc.) in the management of HW/SW lifecycles, including all activities related to asset management.

See section 1.2.1 for approximate number of network devices.

3.8.2 Track and maintain software license documentation IAW AFMAN 17-1203 para 1.2.3.5 (or current regulation) and inform the Government Functional SME when license require renewal. Report software status in the MAR those licenses within four (4) months of expiration. (See Appendix A)

3.8.3 Oversee a spare inventory at sufficient levels to maintain system operations. Notify the Government

Functional SME of low spare supplies within ten (10) business days of identification for Government to coordinate purchases.

3.8.4 Any software, equipment, parts, and materials purchased for or by the Government shall be added to the appropriate inventories.

3.8.6 Maintain and manage Government Furnished Equipment (GFE) and critical/non-critical spare equipment IAW MBSS main PWS Section 3-Logistics.

3.8.7 Maintain all local hand receipts for equipment issued to other sections. Ensure that all local obsolete equipment is properly sanitized and prepared for disposal through proper USAF channels. Notify the

Government Functional SME, Accountable Property Officer (APO), and BECO within one week of discovery of any missing equipment. The contractor shall have 24/7 access to the spare equipment.

3.9 Sustainment and Equipment Technical Refresh

3.9.1 Perform lifecycle management, sustainment and coordinate technical refresh installations and equipment replacements of core communications networks. The equipment includes, but is not limited to, network routers, switches, and other network equipment. Perform site surveys, configuration of equipment, accreditation, and installation of equipment, testing of equipment, and cutovers & integration of the equipment into the operational networks. Additionally, process warranty repair requests as applicable.

3.9.2 Recommend to the Government Functional SME, the priority of equipment replacement also considering EOL/EOS of equipment, equipment failure rates and best use of available funds. Report

EOL/EOS equipment status in the MAR for equipment within one (1) year of expiration. (See Appendix A)

3.10 Base Communications

3.10.1 Operate and Maintain (O&M) Requirements

Overall responsibility to properly operate and maintain the BC shall rest with Contractor as described by the maintenance support plan (MSP) (see section 3.8.1.8, BC Work Center Records) and the OEM’s recommended procedures. O&M actions include all actions taken by the Contractor to operate and maintain equipment and systems in a serviceable condition or to restore it to a serviceable condition to include purchasing of commercially available parts, inspection, periodic testing, adjustment, and repair. O&M responsibilities include all pre-existing cabling infrastructure as is, to include ISP and OSP, all terminals, building terminals, pedestals, and copper and fiber optic splices. The effort may include the replacement of defective circuit packs and Customer Premise Equipment (CPE), preventive maintenance IAW applicable publications and other routine work to optimize the life expectancy of the equipment and cable systems.

Work orders will be accomplished IAW PWS Section 3.10.2.1. The Contractor shall not postpone or otherwise delay O&M efforts to accomplish work orders. The Contractor will assess each work order and volume of work orders. As the workload increases to a point at which O&M support may be affected, the

Contractor will notify the Government and will work collaboratively to develop a schedule that allows for completion of both O&M support and workorders in the timeliest manner possible. The contractor will provide EITSM and Priority ticket metrics within the MAR (See Appendix A). The Contractor has equipment for maintaining the copper infrastructure, but fiber related tools, material and equipment required for O&M will be procured through CLIN X006.

3.10.1.1 Perform Inside Plant (ISP) & Outside Plant (OSP) O&M. Contractor shall maintain ISP & OSP cable and equipment. Upon request by the Government Functional SME, the contractor will perform end to end testing on existing ISP/OSP cabling. Applicable commercial standards apply to all testing and test results will be delivered to the Government Functional SME for acceptance. Preexisting cable infrastructure will be the responsibility of the contractor, as well as all repairs to include all demarcation points and faulty wiring to include horizontal cabling and cross connects. Any additional installation/new locations are limited to 400 feet in maximum length of each run, be less than 10 feet high and have a clear path/conduit identified.

Fiber-related tools, materials, equipment and any specialized skills required to perform this work will be procured through CLIN X006.

3.10.1.2 Preventive Maintenance Inspections (PMIs). Contractor shall perform PMIs as required on all systems covered by this contract IAW OEM recommended or established schedules and/or manuals.

Contractor shall elevate any problems and identify any trends to the Government Functional SME in writing within one workday. Manhole/Handhole PMIs are completed on a 5-year period and all Antennas are performed annually according to TO-33A-1001 (or current regulation).

3.10.1.2.1 Manholes and/or Handholes. The Contractor shall inspect 20% Government-accepted manholes/handholes (which will not be the same manholes/handholes) per year under the O&M portion of this contract. If the Contractor is working in a manhole/handhole not scheduled for a PMI, the Contractor must correct any discrepancies before the job is considered complete. Then, the manhole/handhole will be counted in the monthly PMI schedule. If the following requires specialized training, equipment, materials or skills, it will be accomplished/procured through CLIN 006. It should also be noted that for safety, this work requires the Contractor to work in teams. The Contractor shall ensure a safe working environment for all technicians performing manhole and handhole work. No work shall commence or continue if conditions present an unacceptable risk to the technician's safety, as determined by the site Safety Officer or Safety

Manager. The Contractor shall inspect each manhole/handhole for the following discrepancies and correct/open work order as needed:

3.10.1.2.1.1 All cables will be identified and tagged. At each splice, tags will be placed on each side of the splice identifying each cable. In manholes/handholes with pull through cables, each cable will be identified with a tag.

3.10.1.2.1.2 All cables will be racked to the manhole/handhole cable supports.

3.10.1.2.1.3 All ducts (vacant or occupied) will be sealed.

3.10.1.2.1.4 All manholes or handholes will be cleaned of mud, water, and any other debris.

3.10.1.2.1.5 Enable updates to the CVC database - for the manhole or handhole and record all descriptive information for splices, cables, ducts, and other communication features in the manhole or handhole.

3.10.1.2.1.6 Check Locking lids/identify and place work order with Government Functional SME for new locks.

3.10.1.3 Cable Location, Staking, and Marking. Marking shall be within one foot of the actual location at ten-foot intervals and at direction changes. The marking shall begin two feet outside the point of entry into the work area and shall continue two feet past the point of exit from the work area. Contractor shall complete location, staking and marking within the specified time listed below from the time the Government

Functional SME advises the Contractor of the requirement unless additional time is permitted by the

Government Functional SME. Tools, materials, equipment and any specialized skills or training required to perform this work will be procured through CLIN 006. The Contractor shall comply with the following timelines for location, staking, and marking:

• Emergency: Within 1 hour of notification during duty hours & 2 hours for off duty and weekends.

• Priority: Within 6 Hours of notification.

• Routine: Within 3 business days of notification.

3.10.1.4 Contractor Support Services

The Contractor shall comply with FAR 9.505, Conflict of Interest, IAW support services.

3.10.1.4.1 Contractor Support for Government Engineering and Installations. The Contractor shall provide technical support to include an interchange of information on technical parameters and capabilities of the BC; location and identification of building terminals and communication rooms; and verification of cable record information as directed by the Government Functional SME, COR or CO. These efforts include setting of equipment options to determine proper operational conditions; restoration of service only to existing equipment; establishment of NIPRnet and SIPRNet service to new facilities; establishment of

NIPRnet and SIPRNet service for existing facilities under renovation; transfer from one system to another system; and support of hardware and software upgrades on NIPRnet and SIPRNet. For networks beyond

NIPRnet and SIPRnet, the contractor shall work up to point of disembarkation, which is classified as the network owner’s switch.

3.10.1.5 Contractor Interface and Support for Other Entities. The Contractor shall cooperate, share, and exchange routine or available technical and system equipment interface information with other entities as directed by the Government Functional SME, COR or CO.

3.10.1.6 Design Review Meetings. The Contractor shall review program or project drawings and provide comments concerning communications requirements within ten working days from receipt when requested by the Government Functional SME. The Contractor shall participate in designated design review meetings identified by the Government Functional SME. Any specialized skills or training required to perform this work will be procured through CLIN 006.

3.10.1.7 Technical Solutions. Contractor shall perform detailed technical solutions for work intended to be performed under this contract upon receipt of a written request for the Functional Government SME. The technical solution includes a listing of those efforts/items required to complete the job and shall be provided to the Functional Government SME using the work order format specified in PWS Section 3.8.4. The

Contractor shall provide the proposed solution to the Government Functional SME within 10 working days from receipt of requirement unless a longer period is agreed to by the Government Functional SME and documented on the requirement. Solutions are limited to NIPR/SIPR/JWICs. For networks beyond NIPRnet and SIPRnet, the contractor shall work up to point of disembarkation, which is classified as the network owner’s switch.

3.10.1.8 BC Work Center Records

The Contractor will use EITSM to document all work performed. Contractor may develop and maintain separate BC work center records. The Contractor shall update work center records within 2 duty days after completion of the associated task(s) unless specified differently within this section. All BC records and documents established and maintained by the Contractor are Government property and shall remain at the site and be turned over to the COR for disposition upon contract completion. Failure to do so may result in withholding of final payment until all records are recovered or in a reduction in final payment for records lost or misplaced. The Government requires electronic maintenance and storage of records, unless otherwise specified herein. The Contractor shall identify all acronyms, codes, abbreviations, signs, and symbols used in each record. The Contractor shall use the same format for initial and all subsequent submissions of the same record unless otherwise approved by the CO. All records shall be readily available for review by the

COR and CA, and other personnel (authorized in writing by the CO). The Contractor shall update all errors found or identified during review of the work center records. Contractor shall develop, update and/or maintain accurate, complete, and readable work center records as listed below:

3.10.1.8.1 Maintenance Support Plan (MSP)

The MSP shall enable the scheduling and tracking of preventive maintenance actions on Contractor-maintained equipment. This record shall be available within 30 calendar days after period of performance begins. When changes occur that affect the MSP, revisions shall be submitted within 10 workdays after the effective change (e.g. modification adding equipment) unless otherwise requested by the CO (e.g., with the proposal to add new equipment to maintenance). The Government will review and approve or provide the

Contractor with required corrections. Changes may be implemented only after CO approval. The MSP shall contain as a minimum: a schedule of PMIs due on each piece of equipment being maintained for the life of the contract IAW equipment manufacturer’s recommendations; alarm notification procedures; and specific maintenance tasks to be performed on each system.

3.10.1.8.2 PMI Inspection Records and Malfunction Record

PMI Inspection records shall, at a minimum, contain: the date and time inspections were performed; a short description of inspection conducted; malfunctions or problems annotated on record with equipment data, serial number, etc.; the corrective action taken by the Contractor; and the initials of the technician performing the inspection. The Contractor shall use Government-approved platform for tracking purposes.

3.10.1.8.3 Maintenance/ Repair Logs (e.g. maintenance actions, trouble tickets). Contractor shall use

EITSM to maintain an accurate and legible BC Maintenance/Repair Log to show all maintenance and inspections (other than PMIs) performed during each 24-hour period because of trouble report actions or scheduled or unscheduled outages.

3.10.1.8.4 Manhole, Handhole, and Building Terminal Inspection/ Maintenance/ Repair

Contractor shall maintain manhole, handhole, distribution pedestal terminal, and building terminal inspection records as defined in PWS Section 3.8.1.8.2, 3.8.1.8.3, and 3.8.1.9. The Contractor shall provide updates to Main Operating Base charge with updating the CVC database with pertinent cable feature data

(CFD) information gathered during the inspections. The record shall be available for inspection and analysis by the Government. If other electronic documentation is implemented, the Contractor shall grant the

Government access to those records.

3.10.1.8.5 Cable Installation/Repair Test Results. Contractor shall develop and maintain a cable installation repair test results record after the installation or repair of an outside plant cables. Graphics and pictorials may be used to illustrate. The record shall, at a minimum, contain the purpose of test/inspection;

complete identification of item tested/inspected, and test equipment used; complete…