432 SPTS-CE UMCS SA SOW.pdf

PDF 301 KB Posted

Attached to
432 SPTS/CE Utility Monitoring Control Systems (UMCS) System Administrator (SA)
Solicitation number
FA486125R0020
Issued by

About this file

This Statement of Work (SOW) details the requirements for a Utility Monitoring Control Systems (UMCS) System Administrator (SA) position at Creech Air Force Base in Indian Springs, Nevada. The primary responsibilities include maintaining, securing, and troubleshooting the UMCS infrastructure for the 432 SPTS/CE Cybersecurity Workforce, with key objectives encompassing infrastructure maintenance, cybersecurity management, policy development, and technical support.

The role requires a candidate with a bachelor's degree in Computer Science or related field, minimum 4 years of system administration and cybersecurity experience, and professional certifications such as CompTIA Security+ or higher. The System Administrator will work 160 hours per year (one 40-hour week per quarter), with potential overtime for urgent issues, and will be responsible for producing quarterly security reports, monitoring system performance, managing access controls, conducting security audits, and supporting ongoing cybersecurity efforts. The position involves close collaboration with Information System Security Officers (ISSO) and Information Systems Security Managers (ISSM) to ensure comprehensive system protection and compliance with Department of Defense and Air Force regulations.

View the file

Other files

File Type Posted
RFIs.pdf PDF
WD 2015-5593.pdf PDF
Solicitation - FA486125R0020.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

AFCEC/COOI Contract SOW 432 SPTS/CE Creech CECS

2025010311 STATEMENT OF WORK (SOW) FOR UTILITY

MONITORING CONTROL SYSTEMS (UMCS) SYSTEM ADMINISTRATOR (SA)

432 SPTS/CE CONTRACT SUPPORTING DOCUMENTATION

FOR CIVIL ENGINEER CONTROL SYSTEMS (CECS)

SUPPORT STAFF

STATEMENT OF WORK (SOW) FOR UTILITY MONITORING

CONTROL SYSTEMS (UMCS) SYSTEM ADMINISTRATOR (SA)

432 SPTS/CE

CREECH AFB

INDIAN SPRINGS, NV

Prepared By: Date Published: 20250411

SEAN P. HARRIGAN, CTR, USAF/GDIT

INFORMATION SYSTEMS SECURITY OFFICER

AFCEC/COOI / 432 SPTS/CE

Approved By:

DONALD R. HAMMOND, MSgt, USAF

INFORMATION SYSTEMS OWNER

432 SPTS/CE CREECH AFB, NV

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

DISTRIBUTION STATEMENT:

Limited distribution is releasable to United States government agencies and their contractors only. Other requests for this document shall be referred to USD (A&S) CISO Cyber Directorate, 4800 Mark Center Drive, Alexandria, VA 22311, Attn: DCI Lead, 571. 372. 7770.

DESTRUCTION NOTICE:

Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Controlled by: Air Force Civil Engineering Center (AFCEC) Controlled by: 432 SPTS/CE CUI Category(ies): OPSEC, CONTROLLED TECHNICAL INFORMATION Limited Dissemination Control: Distribution Statement C [OUSD (A&S)/CISO Cyber Directorate, 04 OCT 2021] POC: DONALD R. HAMMOND,, MSgt., USAF, Comm: (702) 404-2693 https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

THIS PAGE IS INTENTIONALLY LEFT BLANK

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

CHANGE LOG

This record shall be maintained throughout the life of the document. Each published update shall be recorded. Revisions are a complete re-issue of entire document. A revision shall be made the document’s content changes.

CHANGE / REVISION RECORD

Date Page/Paragraph Description of Change Made By:

20241220 All Creation Sean P. Harrigan

20250411 Title & Schedule Edit MSgt Hammond https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

TABLE OF CONTENTS

1. Introduction __________________________________________________________________ 6

2. OBJECTIVES: _________________________________________________________________ 6

3. SCOPE OF WORK _____________________________________________________________ 6

3.1 Scope of Work and Objectives Breakout __________________________________________ 7

4. DELIVERABLES _______________________________________________________________ 9

5. reporting ____________________________________________________________________ 10

6. SCHEDULE __________________________________________________________________ 10

7. QUALFICATIONS _____________________________________________________________ 10

8. COMPLIANCE WITH LAWS, REGULATIONS, PUBLICATIONS, CONTROLS, AND

ORDERS _________________________________________________________________________ 10

9. AUTHORITY __________________________________________________________________ 10 https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

1. INTRODUCTION

This Statement of Work (SOW) outlines the duties and responsibilities of a System Administrator (SA) for Creech’s UMCS. The UMCS SA will be responsible for ensuring the security, reliability, and performance of the UMCS infrastructure. The UMCS SA will be part of the 432 SPTS/CE Cybersecurity Workforce (CWF). The UMCS SA will follow all guidance published and/or accepted by the Department of Defense (DoD), United States Air Force (USAF), Air Force Civil Engineer Center (AFCEC), and Creech Civil Engineer Flight 432 SPTS/CE within six months of publication or acceptance.

2. OBJECTIVES:

1) Maintain UMCS Infrastructure.

2) Secure UMCS Infrastructure.

3) Troubleshoot UMCS Infrastructure.

4) Support and Training

3. SCOPE OF WORK

The System Administrator will be responsible for the installation, configuration, and maintenance of the UMCS hardware and software. This includes regularly updating and patching software to ensure optimal performance and security, as well as performing routine checks on hardware components to identify and replace any failing parts. The administrator will conduct regular system backups, ensuring they are securely stored, and the backup and recovery processes are tested to guarantee data integrity and availability. They will document and manage configurations for all UMCS components, ensuring that all configurations are up-to-date and compliant with industry standards.

In terms of security management, the System Administrator will implement and manage user access controls to prevent unauthorized access and will regularly review and update access permissions based on role changes and security policies. They will monitor security logs and alerts for any signs of suspicious activity or potential threats and will work with vendors of UMCS and AFCEC to manage and troubleshoot intrusion detection systems (IDS) and firewalls. Additionally, the administrator will develop and enforce cybersecurity policies and procedures tailored to the UMCS environment and will conduct regular security audits and vulnerability assessments.

When it comes to troubleshooting, the System Administrator will quickly respond to and resolve any security incidents or breaches, documenting incidents and creating reports to analyze their cause and impact. They will monitor system performance, identifying and resolving any issues or bottlenecks that arise. The administrator will also be responsible for responding to and repairing UMCS network outages promptly to minimize downtime, implementing measures to maintain a 90% uptime for all UMCS. They will provide technical support to end-users and other staff members and will conduct training sessions to ensure all staff are aware of best practices and security protocols.

In addition to the above, the System Administrator will be responsible for developing a System Development Life Cycle (SDLC) for hardware and software technology refresh. This involves https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064 planning, designing, testing, and implementing upgrades and replacements to ensure that the UMCS infrastructure remains current and efficient. The administrator will provide technical support to end-users and other staff members specific to the UMCS frontend, building end devices, and UMCS networks. They will serve as a Subject Matter Expert (SME) to advise the 432 SPTS/CE on UMCS upgrades, expansions, and new implementations, as well as on network design and architecture. Additionally, the administrator will aid the ISO, ISSM, and ISSO in achieving and maintaining Authority to Operate (ATO), and will develop, maintain, and update Risk Management Framework (RMF) documentation, including continuous monitoring checklists and Annual Security Reviews (ASR). The System Administrator will attend any meetings pertaining to 432 SPTS/CE UMCS with vendors, outside organizations, AFCEC, the 432 SPTS/CE Cybersecurity Workforce (CWF), or any conferences or meetings requested by the ISO or the 432 SPTS/CE commander. Furthermore, they will collaborate with stakeholders to ensure that the SDLC aligns with organizational goals and industry standards.

3.1 Scope of Work and Objectives Breakout

The following is a breakout of responsibilites for the 432 SPTS/CE UMCS SA position. The breakout is the majority of responsibilities but not all.

1) Maintain UMCS Infrastructure.

a. Hardware and Software Maintenance:

i. Regularly update and patch Level 4 device and frontend software to ensure it runs smoothly and securely.

ii. Regularly update Level 2 and 1 device firmware to ensure components run smoothly and securely.

iii. Perform routine checks on hardware components to identify and replace any failing parts.

iv. Coordinate and work with vendors of UMCS and AFCEC Community of Interest Network Enclave (COIN) helpdesk on troubleshooting, changes, installs, and patching.

v. Coordinate with AFCEC COIN helpdesk, ISSO, and ISSM to remediate any findings from compliance or vulnerability scans.

b. System Backups.

i. Conduct regular system backups and ensure they are stored securely and IAW AFCEC selected National Institute of Standards and Technology (NIST) 800-53r4 Security Controls.

ii. Applicable to all Level 4 devices of the Purdue Model.

iii. Ensure that records are kept of backup activity and uploaded to

Enterprise Mission Assurance Support Service (EMASS) package ID.

iv. Test backup and recovery processes to guarantee data integrity and availability.

c. Configuration Management.

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

i. Document and manage configurations for all UMCS components IAW the UMCS Configuration Management Plan (CMP) and Change Control Board (CCB) charter.

ii. Ensure all configurations are up to date and compliant with Industry Standards and AFCEC selected NIST 800-53r4 Security Controls.

iii. Update and Maintain UMCS network documentation such as topologies, network IP schemas, IP address assignments with the Information System Security Officer (ISSO), Information Systems Security Manager (ISSM), Information System Owner (ISO) and the 432 SPTS/CS Communication Squadron Infrastructure Team.

2) Secure UMCS Infrastructure:

a. Access Controls:

i. Implement and manage user access controls to prevent unauthorized access IAW UMCS System Policy Document(s) (SPD).

ii. Regularly review and update access permissions to the Purdue Model Level 4 devices based on role changes and security policies.

iii. Coordinate and work with AFCEC COIN helpdesk, ISSO, ISSM, and Unit Security Manager (USM) to process accounts IAW UMCS SPD.

iv. Regularly review and update access permissions to the UMCS Frontend Applications based on role change and security policies.

v. Maintain account documentation IAW UMCS SPD to include Transfer and Termination Checklists.

vi. Coordinate and work with ISSO and ISSM to document an Authorized User and Maintainer List IAW UMCS SPD.

b. Security Monitoring:

i. Collect and Review security logs with ISSO and ISSM to detect any signs of suspicious activity or potential threats.

ii. Coordinate and work with ISSO and ISSM to conduct compliance and vulnerability scans.

iii. Coordinate and work with ISSO and ISSM to conduct regular

Security Control Audits and vulnerability assessments.

3) UMCS Cybersecurity Policies:

a. Coordinate and work with ISSO and ISSM to review, update, disseminate, and make changes to cybersecurity policies.

b. Participate in UMCS exercises, After Action Reports (AAR) and Lessons Learned.

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

4) Troubleshoot UMCS Infrastructure:

a. System Performance

i. Monitor system performance and identify any issues.

ii. Troubleshoot and resolve any hardware or software issues affecting system performance.

iii. Troubleshoot network connectivity on the UMCS network at Levels

4, 2, and 1 of the Purdue Model and Layers 1, 2, and 3 of the OSI Model.

iv. Maintain UMCS up time of 90%.

v. Coordinate with UMCS vendors and AFCEC helpdesk to resolve identified issues.

vi. Ensure Purdue Model Level 1 and 2 devices have current and accurate logic programed.

5) Support and Training:

a. Provide Technical support to end-users and other staff members specific to the UMCS frontend, building end devices, and UMCS networks.

b. Provide Subject Matter Expert (SME) advise on 432 SPTS/CE on UMCS upgrades, UMCS expansions, and new UMCS. Advise the 432 SPTS/CE on UMCS network design and architecture.

c. Aid the ISO, ISSM, and ISSO to achieve and maintain Authority to Operate (ATO), develop, maintain, and update Risk Management Framework (RMF) documentation to include continuous monitoring checklists and Annual Security Reviews (ASR).

d. Attend any meetings pertaining to 432 SPTS/CE UMCS with vendors, outside organizations, AFCEC, 432 SPTS/CE Cybersecurity Workforce (CWF), or any conferences or meetings requested by the ISO or 432 SPTS/CE commander.

4. DELIVERABLES

The System Administrator is responsible for producing quarterly security reports and performance metrics to monitor the effectiveness and security of the UMCS infrastructure.

They will provide regular updates on system status and maintenance activities to keep stakeholders informed. Additionally, the System Administrator will document all changes and updates to the UMCS infrastructure to ensure that accurate records are maintained IAW SPD, CMP, and CCB Charter. Training materials and records of cybersecurity training sessions will also be prepared and maintained to support continuous improvement in staff cybersecurity awareness.

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

5. REPORTING

The System Administrator will be part of the 432 SPTS/CE Cybersecurity Workforce (CWF).

Daily reporting during quarterly visits shall be directed to the ISSO and/or the ISSM. The System Administrator shall submit all deliverables to the Contracting Officer Representative (COR) and the CWF staff. Any changes to the Statement of Work (SOW) shall only be made by the COR IAW the signed contract between the SA or the SA contracted organization and the 432d Contracting Squadron.

6. SCHEDULE

The System Administrator will work one standard 40-hour week per quarter, total 160 hours per year, with the possibility of occasional overtime as needed and approved by either the CECS ISO or the Base Civil Engineer (BCE)/432 SPTS/CE Commander, to respond to security incidents, UMCS outages, or planned maintenance. This schedule ensures that the UMCS infrastructure is consistently monitored and maintained, while also allowing for flexibility to respond to urgent issues as they arise.

7. QUALFICATIONS

The ideal candidate for this role will possess a bachelor's degree in Computer Science, Information Technology, or a related field, along with a minimum of 4 years of experience in system administration and cybersecurity. The candidate must have the ability to obtain a DoD Common Access Card (CAC), Non-Classified Internet Protocol Router Network (NIPR) account, Secure Internet Protocol Router (SIPR) account, and Privileged Access Account (PAA). The candidate must meet the qualifications as outlined in DoD Manual 8140.03, “Cyberspace Workforce Qualification and Management Program,” dated February 15, 2023, specifically for the job role (451) System Administrator Intermediate. Additionally, the candidate must have a minimum of CompTIA Security+ certification, or higher certifications such as CompTIA CASP+, Cisco CCNP Security, (ISC)2 CISSP, or ISACA CISM. All professional certifications need to be enrolled in Continuing Education programs to ensure ongoing professional development and compliance with industry standards. This combination of education, experience, and certification ensures that the System Administrator has the necessary skills and knowledge to effectively manage and secure the UMCS infrastructure.

8. COMPLIANCE WITH LAWS, REGULATIONS, PUBLICATIONS, CONTROLS,

AND ORDERS

In performing work under this contract, the contractor shall comply with all applicable federal, state, and local laws. As well as all applicable DoD and USAF regulations, publications orders, and 432 SPTS policies and procedures. A six month waiver could be granted for compliance if any DoD and USAF regulations, publications orders, and 432 SPTS policies and procedures is published after award of the contract. The waiver process will be a case by case basis.

9. AUTHORITY

The contracting officer (CO) must be the only person authorized to approve changes in this contract and notwithstanding any provision contained elsewhere in this contract, said authority remains solely with the CO. In the event the contractor effects any such change at the direction of any person other than the CO, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in cost incurred as a result thereof.

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=imgres&cd=&cad=rja&uact=8&ved=2ahUKEwjuhsDRt9bcAhWGk1kKHf-zDFwQjRx6BAgBEAU&url=https://scrollmedia.deviantart.com/art/Shield-AFCEC-Air-Force-Civil-Engineer-Center-537471853&psig=AOvVaw1dKPLJ6_vRf4xVfcT5mJTq&ust=1533576456796064

1. Introduction
2. OBJECTIVES:
1) Maintain UMCS Infrastructure.
2) Secure UMCS Infrastructure.
3) Troubleshoot UMCS Infrastructure.
4) Support and Training
3. SCOPE OF WORK
3.1 Scope of Work and Objectives Breakout
1) Maintain UMCS Infrastructure.
a. Hardware and Software Maintenance:
i. Regularly update and patch Level 4 device and frontend software to ensure it runs smoothly and securely.
ii. Regularly update Level 2 and 1 device firmware to ensure components run smoothly and securely.
iii. Perform routine checks on hardware components to identify and replace any failing parts.
iv. Coordinate and work with vendors of UMCS and AFCEC Community of Interest Network Enclave (COIN) helpdesk on troubleshooting, changes, installs, and patching.
v. Coordinate with AFCEC COIN helpdesk, ISSO, and ISSM to remediate any findings from compliance or vulnerability scans.
b. System Backups.
i. Conduct regular system backups and ensure they are stored securely and IAW AFCEC selected National Institute of Standards and Technology (NIST) 800-53r4 Security Controls.
ii. Applicable to all Level 4 devices of the Purdue Model.
iii. Ensure that records are kept of backup activity and uploaded to Enterprise Mission Assurance Support Service (EMASS) package ID.
iv. Test backup and recovery processes to guarantee data integrity and availability.
c. Configuration Management.
i. Document and manage configurations for all UMCS components IAW the UMCS Configuration Management Plan (CMP) and Change Control Board (CCB) charter.
ii. Ensure all configurations are up to date and compliant with Industry Standards and AFCEC selected NIST 800-53r4 Security Controls.
iii. Update and Maintain UMCS network documentation such as topologies, network IP schemas, IP address assignments with the Information System Security Officer (ISSO), Information Systems Security Manager (ISSM), Information System Owner (ISO) and the...
2) Secure UMCS Infrastructure:
a. Access Controls:
i. Implement and manage user access controls to prevent unauthorized access IAW UMCS System Policy Document(s) (SPD).
ii. Regularly review and update access permissions to the Purdue Model Level 4 devices based on role changes and security policies.
iii. Coordinate and work with AFCEC COIN helpdesk, ISSO, ISSM, and Unit Security Manager (USM) to process accounts IAW UMCS SPD.
iv. Regularly review and update access permissions to the UMCS Frontend Applications based on role change and security policies.
v. Maintain account documentation IAW UMCS SPD to include Transfer and Termination Checklists.
vi. Coordinate and work with ISSO and ISSM to document an Authorized User and Maintainer List IAW UMCS SPD.
b. Security Monitoring:
i. Collect and Review security logs with ISSO and ISSM to detect any signs of suspicious activity or potential threats.
ii. Coordinate and work with ISSO and ISSM to conduct compliance and vulnerability scans.
iii. Coordinate and work with ISSO and ISSM to conduct regular Security Control Audits and vulnerability assessments.
3) UMCS Cybersecurity Policies:
a. Coordinate and work with ISSO and ISSM to review, update, disseminate, and make changes to cybersecurity policies.
b. Participate in UMCS exercises, After Action Reports (AAR) and Lessons Learned.
4) Troubleshoot UMCS Infrastructure:
a. System Performance
i. Monitor system performance and identify any issues.
ii. Troubleshoot and resolve any hardware or software issues affecting system performance.
iii. Troubleshoot network connectivity on the UMCS network at Levels 4, 2, and 1 of the Purdue Model and Layers 1, 2, and 3 of the OSI Model.
iv. Maintain UMCS up time of 90%.
v. Coordinate with UMCS vendors and AFCEC helpdesk to resolve identified issues.
vi. Ensure Purdue Model Level 1 and 2 devices have current and accurate logic programed.
5) Support and Training:
a. Provide Technical support to end-users and other staff members specific to the UMCS frontend, building end devices, and UMCS networks.
b. Provide Subject Matter Expert (SME) advise on 432 SPTS/CE on UMCS upgrades, UMCS expansions, and new UMCS. Advise the 432 SPTS/CE on UMCS network design and architecture.
c. Aid the ISO, ISSM, and ISSO to achieve and maintain Authority to Operate (ATO), develop, maintain, and update Risk Management Framework (RMF) documentation to include continuous monitoring checklists and Annual Security Reviews (ASR).
d. Attend any meetings pertaining to 432 SPTS/CE UMCS with vendors, outside organizations, AFCEC, 432 SPTS/CE Cybersecurity Workforce (CWF), or any conferences or meetings requested by the ISO or 432 SPTS/CE commander.
4. DELIVERABLES
5. reporting
6. SCHEDULE
7. QUALFICATIONS
8. COMPLIANCE WITH LAWS, REGULATIONS, PUBLICATIONS, CONTROLS, AND ORDERS
9. AUTHORITY

File details come from the government source that posted it. Updated .