AFIMSC IT-IM PWS 29 Aug 24.pdf

AIR FORCE INSTALLATION & MISSION SUPPORT CENTER (AFIMSC)

PERFORMANCE WORK STATEMENT

for

INFORMATION TECHNOLOGY - INFRASTRUCTURE MAINTENANCE (IT-IM)

DAF CABLE, ANTENNA, MICROWAVE, VOICE, LAND MOBILE RADIO, AND

GIANT VOICE SYSTEMS

23 Aug 2024

DRAFT Version 2

DRAFT

1. PURPOSE. This acquisition is to provide and maintain serviceable mission systems that meet Department of the Air Force (DAF) Technical Orders (TO) and/or commercial standards.

Systems to be maintained include Digital and Internet Protocol (IP)-based Voice Systems, Giant

Voice, Cable Infrastructure, Antenna, Microwave systems, and Land Mobile Radio (LMR) base backbone across the DAF.

2. SCOPE. The contractor shall provide services for the Information Technology -

Infrastructure Maintenance (IT-IM) system including routine maintenance, Preventative

Maintenance Inspections (PMI), sustainment, troubleshooting, repairing, replacing faulty components, and installing infrastructure, based on emerging mission requirements or capability refreshes.

3. DESCRIPTION OF SERVICES. Required services are broken down into three (3) levels of support:

I. Routine Maintenance/Sustainment Services - Support consists of routine maintenance and sustainment, including Preventive Maintenance Inspections (PMI). PMIs will be conducted on a predetermined interval based on government requirements and mission priority, IAW Original Equipment Manufacturer (OEM) directive.

II. Repair/Replace Services – Comprises of troubleshooting, repairing, and replacing faulty component(s)

III. Modernization Services - Addresses installs and modernization of systems hardware, software, and infrastructure. New installs and system upgrades address emerging mission requirements or new system capabilities

3.1. Other Services. Any associated tasks not readily identified but required for the maintenance/sustainment of systems within this PWS or specified by appropriate government representative.

4. REQUIRED SERVICES.

4.1. Antenna. The contractor shall provide routine maintenance and repairs to ensure optimal sustainment of installation antennas.

4.2. Microwave Systems. The contractor shall provide routine maintenance and repairs to ensure optimal sustainment of installation Microwave Systems.

4.3. Giant Voice. Maintenance and sustainment of Giant Voice systems encompasses PMIs on a predetermined interval based on government requirements and mission priority. The repair and replacement of the faulty component(s) result from the age of the system, extensive use, and, in most cases, the environment.

4.4. Voice Systems. Maintenance and sustainment of Voice encompasses PMIs on a predetermined interval based on government requirements and mission priority. Moves, adds and changes of end instruments. The repair and replacement of the faulty component(s) result from the age of the system, extensive use, and, in most cases, the environment.

4.5. Land Mobile Radio. Support Information Assurance (IA) Services - Risk Management

Framework (RMF) Cybersecurity Accreditation. The Government Information Systems Security

Manager (ISSM) shall facilitate the RMF cybersecurity accreditation, gather system information provided by the Contractor, and enter information into eMASS. The Contractor shall incorporate all applicable technical, procedural, and system documentation associated with DoD IA policy and requirements for non-tactical LMR systems that transmit and manage Controlled

Unclassified Information (CUI) voice and data traffic. The Contractor shall prepare and deliver

RMF support documents and artifacts (CDRL A001) to the Government in accordance with

Technical Exhibit 2. As DoD and Air Force IA policies require continuous updates, the

Government ISSM shall provide the latest templates and policy guidance references upon request to the Contractor cybersecurity team to include System Security Plans.

5. SUSTAINMENT.

5.1. Contractor shall provide certified personnel and equipment, transportation, tools, materials, supervision, and other items and services necessary to perform troubleshooting, repair, PMI, conduct operational checks/adjustments, monitor system performance, provide remote support/maintenance, dispatch technicians, and deliver on-site maintenance repair services in accordance with all manufacturer specifications, to include OEM parts and labor.

5.2. Contractor shall provide associated maintenance and services to include remote and on-site maintenance response capabilities, depot level repairs, advanced parts replacement, and emergency support to sustain system operations as specified within this document.

5.3. Contractor shall notify the appropriate base LMR POC before dispatching technical services to the site for LMR issues. Government shall provide telephone and email contact information to support required notifications upon contract award. The Government shall confirm site access and support for duty schedules that extend beyond normal business hours when major repairs are required.

5.4. Contractor shall provide infrastructure repair with advanced parts replacement to minimize downtime. Upon assessment, suspected faulty equipment items shall be sent to the field within

24 hours to ensure that a spare unit is available to expedite repair activities. Infrastructure may be repaired down to the component level, as applicable. When infrastructure is no longer supported by the OEM, or third-party Contractor, the Contractor shall replace infrastructure with similar infrastructure. The Contractor shall provide priority shipment for all required equipment.

6. PREVENTIVE MAINTENANCE INSPECTIONS (PMI).

6.1. Contractor shall provide PMIs as necessary per the equipment, scheduled with the

Government, for each installation to ensure equipment meets original manufacturer’s specifications. Preventive maintenance activities shall be documented and provided to the

COR/CO (CDRL A00X) and in the appropriate DAF System of Record. This is a maintenance service to ensure the system is operating efficiently and functioning within OEM specifications.

6.2. Contractor shall prepare and submit incident ticket notification (CDRL A00X) to the COR and in the appropriate DAF System of Record. Notifications shall include the date and time of the service call, service location by name, description of incident and affected systems, detailed repair actions completed to include descriptions for any system adjustments, software/configuration changes, or equipment that was replaced and supporting pass through warranty information.

6.3. Contractor shall provide notification, if applicable, that a particular item is on backorder, the expected lead-time to fulfill the order and complete all repair actions. Prior to implementation, the Contractor shall submit written requests (CDRL A00X) for any temporary work around configurations needed to sustain system operations to the Government for approval.

6.4. Contractor shall deliver a Quarterly Sustainment Services Report (CDRL A00X) to the

COR/CO. Sustainment Services Reports shall include a narrative summary regarding the current health of the equipment, a complete list of sustainment activities completed within the 90 days prior, assigned incident ticket tracking number, incident open and close dates/times, current status for unresolved incident tickets, initial problem identified, restoral activity description, define activities as completed remotely or onsite, and a list of replaced parts or equipment.

7. GENERAL INFORMATION.

7.1. General Information Awareness (IA) Requirements for LMR Sustainment.

7.1.2. Field upgradable operating systems and Air Force Standard Desktop Configuration

(AFSDC) compliant software configurations, Air Force Network Operations (AFNETOPS) standard desktop configured, and upgrade legacy software prior to scheduled end-of-life.

7.1.3. LMR equipment: provide Software Update Service (SUS) automated IA security patches and updates to support the system as required to maintain RMF authorizations and sustain operational capabilities (CDRL A00X). System updates must be vetted by the Contractor to ensure compatibility and supportability with P25 radio operations and shall not impact ELMR users. At a minimum, the Contractor shall provide automated anti-virus definition updates, minor release patches, and IA remediation. The Contractor shall obtain Information Assurance

Vulnerability Management (IAVM) Alerts released by the Department of Defense Computer

Emergency Response Center (DoD-CERT), and OEM Bulletins and Technical Tips (Microsoft, Oracle, Solaris, RedHat, Adobe, etc.) to identify and address new vulnerabilities identified.

Unless approved by the Government ELMR IA team, remote updates should be scheduled as follows:

7.1.4. At a minimum, apply:

7.1.4.1. Microsoft, UNIX, Linux, and Third-Party Patches: Monthly

7.1.4.2. Antivirus Patches/definition updates: Weekly

7.1.5. Communications Security (COMSEC).

7.1.5.1. Contractors may require access to COMSEC information on Air Force installations.

The contractor shall not need a COMSEC account. The sponsoring agency shall control access to all COMSEC materials.

7.1.5.2. If necessary, the COR shall provide required COMSEC training to include required courses to contractors needing COMSEC material. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.

7.2. Security Instructions.

7.2.1. Physical Security. The contractor shall safeguard all Government property, documents, and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract.

7.2.2 Quality Control Program (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are delivered in accordance with this document. The contractor’s plan should be detailed to incorporate how the contractor will ensure quality services are in line with this requirement. The QCP shall implement procedures to identify, prevent, and ensure non-recurrence of defective services. The QCP shall describe the actions

(measurements, inspections, quality checks or monitoring of process parameters) required to assure services conform to the requirements in this document. (CDRL A00X)

7.2.3. Contractor Interface and Support for Other Vendors. The contractor shall cooperate, share, and exchange routine or available technical and system equipment interface information with other approved vendors.

7.2.4. Emergency Conditions. The contractor shall report any safety hazards in writing to the site Point of Contact (POC) and immediately perform corrective actions before departing any site. The site POC shall correspond to the appointed government representative on all reported emergencies within one week. Add email language.

7.2.5. Access Control. The contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced, or used by unauthorized persons. The contractor shall not share access codes with any person(s) outside the organization. The contractor shall control access to all Government-provided lock combinations to preclude unauthorized entry. The contractor is only authorized to record lock combinations with written approval by the appointed government representative. Records with reported combinations to approved secure storage containers, secure storage rooms, or certified vaults shall be marked and safeguarded at the highest classification level. The contractor and appointed government representative shall store classified material inside the approved containers.

7.3. Weapons, Firearms, and Ammunition.

7.3.1. Contractors shall not transport weapons, firearms, or ammunition on themselves or within any vehicle while on any military facility.

7.3.2. Accident/Incident Reporting and Investigation.

7.3.3. The contractor shall record and report to the COR all available facts relating to each instance of accidental government property damage or contractor personnel injury. The contractor shall secure the scene of an accident and wreckage until released by the accident investigative authority through the Contracting Officer (CO). If the Government elects to investigate the incident, the contractor shall cooperate fully with the COR. The contractor shall provide a list of Accident/Incident Reports to the base COR and or CO. (CDRL A00X)

7.3.4. Subcontractor Compliance. The contractor shall be responsible for ensuring subcontractors satisfy the requirements outlined in the PWS and contract.

8. Base Civil Engineering Work Clearance Requests. The contractor shall obtain a Base

Civil Engineering Work Clearance Request, AF Form 103, or AF Form 332, prior to performing subterranean repair or maintenance.

9. Transition Plan In/Out. The contractor shall provide a Transition-In Plan at the Kickoff

Meeting; the plan shall facilitate a seamless transition from the incumbent contractor (if applicable) to the incoming contractor.

9.1. The contractor shall identify how it will coordinate with the incumbent Contractor and

Government personnel to transfer knowledge regarding the following:

9.1.1. Project management processes

9.1.2. Points of contact

9.1.3. Location of technical and project management documentation

9.1.4. Status of ongoing technical initiatives

9.1.5. Transition of key personnel

9.1.6. Schedules and milestones

9.1.7. Actions Required of the Government.

9.1.8. Coordination of IT-related programs, issues

9.2. The contractor shall also establish and maintain effective communication with the incumbent Contractor and Government personnel for the transition period via weekly status meetings per the COR’s direction.

9.3. Incumbent employees may be interviewed for possible employment by the incoming contractor; however, the employees will have the first right of refusal.

9.4. The contractor shall provide Transition Plan for discussion with the COR(s), Contracting

Officer, or other personnel (approved by the CORs or CO). (CDRL A00X)

10. Records Management. Records Management includes creation, use, maintenance, storage, and disposition of information as a government record, regardless of media. All records, files, documentation, working papers, and software provided by the Government or generated in performance of this contract become and remain Government property. Contractor shall maintain records, files, documentation, and working papers IAW DAFI 90-160, using (AFRIMS http://afrims.amc.af.mil) and/or other pertinent directives as supplemented. If requested by

Government, provide original record or a reproducible copy of any such record within five (5) working days of receipt of request. (CDRL A00X)

11. Meetings.

11.1. The contractor shall attend contracted review meetings as required.

11.1.1. Kick-off Meetings. Contractor shall facilitate a kick-off meeting prior to performance of this contract. In addition, prior to installation service, a kick-off meeting shall be conducted at the task order level as directed by the contracting officer and COR.

11.1.2. Workload Status Meetings. The contractor shall attend local meetings with the COR(s), Communications Squadron Plans Office, and CO to discuss the status of current and future work orders, trouble tickets, outages, PMIs, or any other work/event that may impact contractual performance as required (or may impact mission operations as determined by the installation

COR). The contractor shall provide a list of work orders and trouble tickets at meetings for reconciliation and discussion with the installation COR(s), Contracting Officer, or other personnel (approved by the CORs or CO). (CDRL A00X)

12. Work Orders. Work Orders submitted by the contractor shall specify the CLIN/PID’s directly on the form. The Contractors will be responsible for uploading any receipts associated with issued work orders into the DOD-approved database within two (2) business days of completion. The contractor shall provide Work Order report to enterprise COR(s), Contracting

Officer, or other personnel. (CDRL A001)

13. Workload Status Report. The Workload Status Report shall identify all maintenance activity performed or scheduled to include preventive maintenance and repair/fix actions for all contractor-maintained equipment. Contractor maintained items shall be identified and documented in a quarterly report. Status reporting for all completed or uncompleted and or scheduled maintenance activity are required for the given period. Additional examples include, but are not limited to, future equipment purchases, installations, removals, or relocations.

Additionally, installation or removal of cables/transmission media as required for new installations to include follow-on O&M for all items installed by the contractor. The

Government requires electronic maintenance and storage of reports, unless otherwise specified herein. The Contractor shall identify all acronyms, codes, abbreviations, signs and symbols used in each record. Format shall be approved by enterprise, or local COR (or other individuals identified in writing by the COR). (CDRL A002)

14. Outages.

14.1. Outage Restoral Priority Levels. AFIMSC requires the quarterly report on all outages with the UNCLASS impact statement on the installation's mission; Negligible, Low, Medium, High.

The contractor shall provide outage report to enterprise COR(s), Contracting Officer, or other personnel. (CDRL A003)

14.1.1. MAJOR System Outage. Loss of operational capability of the following:

14.1.1.1. Cable: cuts/outages that affect 100 users or more.

14.1.1.2. Antenna: any impairment that affects critical mission systems, as provided/defined by the COR.

14.1.1.3. Microwave: any impairment that affects critical mission systems, as provided/defined by the COR.

14.1.1.4. Voice: any outage that affects operations, command and control functions, or 100 or more routine voice users.

14.1.1.5. Giant Voice: any outage that affects thirty-three percent (33%) or more of Giant Voice poles/towers or any sites that border the flight line.

14.1.2. MINOR System Outage. Any outage that does not create a safety hazard or prevent a service from operating as designed and does not prevent subsequent work. The contractor shall acknowledge notification within eight (8) hours after a monitored detection or notification by the

COR. A minor system failure shall be corrected before any other maintenance support except for a significant system outage and within ninety-six (96) hours after response unless the COR gives further time.

14.1.2.1. Cable: any outage that does not create a safety hazard or prevent a service from operating as designed and does not prevent subsequent work.

14.1.2.2. Antenna: any outage that does not create a safety hazard or prevent a service from

14.1.2.3. Microwave. any outage that does not create a safety hazard or prevent a service from

14.1.2.4. Voice: any outage that does not create a safety hazard or prevent a service from

14.1.2.5. Giant Voice: any one site not bordering the flightline becoming inoperable, any intermittent RF interference.

14.2. Non-Emergency Outages. All non-emergency issues are defined as parts questions, intermittent problems, or presently monitored system problems. The contractor shall respond to non-emergency issues within twenty-four (24) hours after notification by the COR. The COR will determine if an on-site response technician is required at the time of trouble call receipt.

Non-emergency calls shall be corrected before any other maintenance support within ten (10) days (240 hours) after response unless more time is given by the COR.

14.3. Authorized Service Interruption (ASI). The contractor shall identify, coordinate, and schedule service outages with the COR. The notification shall include the reason for the interruption, start and stop times, duration, and the equipment, lines, circuits, and buildings affected. The contractor shall schedule such outages to minimize the impact on the mission;

scheduled outages outside regular duty hours are allowed. The user must release all affected equipment and circuits before any service disruption. The contractor shall follow established local procedures for scheduling and implementing scheduled outages.

14.4. Outage Restoration. The contractor shall acknowledge notification within the times specified by the COR. The contractor shall restore services in the priority order determined by the COR. The contractor shall work on repair actions until service is corrected based on priority.

The contractor shall work closely with the COR on all service or system outages, including trouble calls/tickets. The contractor shall provide the repair action and time of service restoral to the COR in writing.

14.5. Outage Cause Identification. The contractor shall determine if a recorded problem or system failure is attributable to IT-IM or other causes (other vendors provide services). The contractor shall immediately notify the COR if the outage is due to other causes (outside the

Contractor-maintained system/equipment). The contractor shall be liable for restoral cost if the contractor's poor maintenance practices caused the system failure.

15. Inventory of Active Equipment. Contractors shall develop and maintain a comprehensive list of all hardware, software, and components that are serviced under this contract to be submitted to the government on an annual basis. The list shall at a minimum include the following:

15.1. Hardware:

15.1.1. Giant Voice inventory equipment

15.1.2. Voice inventory equipment

15.1.3. Antennas

15.1.4. Routers

15.1.5. Switches

15.1.6. Servers

15.1.7. Power Supplies

15.1.8. Cables: Ether, coaxial, and power cables for interconnecting devices

15.1.9. Mounting Hardware: brackets, mounts and accessories for installing antennas and equipment

15.2. The contractor shall provide inventory report to enterprise COR(s), Contracting Officer, or other personnel. (CDRL A004)

15.4. Initial Assessment.

15.4.1. Initial assessment is conducted after the contractor transition in/out meeting. The contractor has 90 days to complete in association with the installation COR. The contractor shall provide initial assessment report to enterprise COR(s), Contracting Officer, or other personnel.

(CDRL A005)

16. Special Project Requirements. Special projects are negotiated projects issued under the contract over and above the O&M requirement.

Add in Regulations for how we conduct our job

Add in paragraph that says you must work off of these regulations

APPENDIX 1 - DELIVERABLES

** Installations may require additional CDRLs based upon mission need.

CDRL Ref Para Title Delivery schedule

A00X 6.a Preventative maintenance Installation determines

A00X 6.a Records management

A00X 6.b Ticket notification Installation determines

A00X 6.c Written requests Installation determines

A00X 6.d Quarterly Sustainment

Services Report

Installation determines

A00X 7.d.i Quality Control Program Installation determines

A00X 7.i.i Accident/Incident Reports Installation determines

A00X 9.d Transition Plan in & out Installation determines

A00X 10.d Meetings Installation determines

A00X 7.a.ii Provide Software Update

Service

Yearly or when changes are made

A001 11.a Workorders Quarterly

A002 12.a Workload Status Report Quarterly

A003 13.b Outages Quarterly

A004 14.c Inventory of active equipment

Within 90 days of transition in

A005 14.d Initial Assessment

A006 12 Annual Inventory Report Yearly

APPENDIX 2 - ANNUAL INVENTORY REPORT (will add after RFI) (CDRL A006)

INTENTIONALLY LEFT BLANK

APPENDIX 3 - SERVICE SUMMARY

The Government has the right to inspect and test all services called for by the contract. The

Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance, to the extent practicable at all times and places during the term of the contract.

Performance objectives will vary on the installations. At a minimum, these are required at the enterprise level:

- Annual inventory

- Accuracy of the inventory

- Review other required deliverables

- Timeliness and accuracy

- This chart also goes in the QASP

- Method in which DAF CORs are evaluating contractor performance

- Contractor Performance Reports

Service

Summary #

Performance objective

PWS

Reference

Performance

Threshold

Observation

Method

SS 1 The contractor shall maintain systems at the

Original

Equipment

Manufacturer

(OEM)

recommended specifications.

OEM

recommendation and PMI intervals met 90% of the time.

Periodic Inspections at (interval), applicable reports and customer feedback.

SS 2

The contractor shall document, respond to and restore all systems and service outages and trouble calls/tickets

Major System

Outage: respond within 1 hour;

complete resolution within 24 hours.

Minor System

Outage: respond within 8 hours;

A minimum of 20% of outage reports will be reviewed monthly. At the call level, a finalized level of surveillance will be established.

within 96 hours.

Non-emergency

Outage: respond within 24 hours;

within 240 hours

SS 3 The contractor shall perform any associated task required for the sustainment of the systems outlined in this

PWS.

Performance threshold will be determined by the appropriate government representative

Periodic Inspections at

(interval), applicable reports and customer feedback.

SS 4 The contractor will provide a

Quality

Assurance Plan

Recommendation intervals met 90% of the time.

Yearly report

SS 5 The contractor will provide an

Annual

Inventory report

Recommendation intervals met 90% of the time.

Due within 90 days of contractor initial transition and at the yearly anniversary of contractor plan in meeting.

Yearly report

APPENDIX 4 - ACRONYMS

CDR: Contract Discrepancy Report

CLIN: Contract Line-Item Number

CIPS: Cyberspace Infrastructure Planning System

CVC: CIPS Visualization Component

CO: Contracting Officer

COMSEC: Communications Security

COR: Contracting Officer Representative

COTS: Commercial Off-The-Shelf

CS/CC: Communications Squadron Commander

DoD: Department of Defense

ELMR: Enterprise Land Mobile Radio

FFP: Firm Fixed Price

IA: Information Assurance

IT-IM: Information Technology - Infrastructure Maintenance

IP: Internet Protocol

LMR: Land Mobile Radio

PMI: Preventive Maintenance Inspection

OSHA: Occupational Safety and Health Administration

PWS: Performance Work Statement

QASP: Quality Assurance Surveillance Program

WOMS: Work Order Management System

APPENDIX 5 – PUBLICATIONS

Publication Number

Date

Title

Applicable

Paragraphs

AFI 17-203 16-Mar-17 Cyber Incident Handling ALL

DAFI 10-208 11-May-23 Continuity of Operations (COOP) Program ALL

DAFI 10-2501 15-Oct-23 Emergency Management Program ALL

AFI 17-101 6-Feb-20 Risk Management Framework (RMF) for

Air Force Information Technology (IT)

ALL

AFI 17-110 23-May-18 Information Technology Portfolio

Management and Capital Planning and

Investment Control

ALL

AFI 17-130 13-Feb-20 Cybersecurity Program Management ALL

AFI 17-201 5-Mar-14 Command and Control (C2) for Cyberspace

Operations

ALL

AFI 17-210 30-Jul-23 Radio Management, Incorp Chng 1 ALL

DAFI 17-220 7-Jun-21 Spectrum Management ALL

DAFI 17-221 30-Jan- Spectrum Interference Resolution Program ALL

AFI 33-322 12-May-20 Records Management and Information

Governance Program

ALL

AFI 33-324 22-Jul-19 The Air Force Information Collections and

Reports Management Program

ALL

AFI 33-332 5-May-20 Air Force Privacy and Civil Liberties

Program

ALL

AFI 33-393 3-Jul-19 Electronic and Information Technology

Accessible to Individuals with Disabilities, Section 508

A10.5.3.

DAFI 65-601V1 22-Jun-22 Budget Guidance and Procedures ALL

AFI 65-601V2 29-Jan-21 Budget Management for Operations ALL

DAFI 17-1203 13-Sept-23 Information Technology (IT) Asset

Management (ITAM)

ALL

AFMAN 17-1301 12-Feb-20 Computer Security (COMPUSEC) ALL

AFMAN 17-1302-O 9-Apr-20 Communications Security (COMSEC)

Operations (FOUO), Incorp Corrective

Action 24-Apr-20

AFMAN 17-1402 20-Jun-18 Clinger-Cohen Act (CCA) Compliance ALL

AFMAN 17-2101 22-May-18 Long-Haul Communications Management ALL

AFMAN 33-326 31-Jul-19 Preparing Official Communications ALL

AFMAN 33-396 12-Aug-19 Knowledge Management Para 3.4.8.

AFMAN 17-1303 12-May-20 Air Force Cybersecurity Workforce

Improvement Program

ALL

AFPD 10-24 5-Nov-19 Mission Assurance ALL

AFPD 17-1 12-Apr-16 Information Dominance Governance And

Management

ALL

DAFPD 17-2 27-Oct-20 Cyberspace Operations ALL

AFPD 33-3 21-Jun-16 Information Management, Incorp Chng 1 ALL

CJCSI 6211.02D 4-Aug-15 Defense Information System Network

(DISN) Responsibilities

ALL

CJCSI 6510.01F 9-Jun-15 Information Assurance (IA) and Support

To Computer Network Defense (CND)

ALL

DoDI 5205.13 21-Aug-19 Defense Industrial Base (DIBib) Cyber

Security/Information Assurance (CS)

Activities, Incorp Chng 2

DoDI 8100.04 9-Dec-10 DoD Unified Capabilities (UC) ALL

DoDI 8320.02 5-Aug-13 Sharing Data, Information, And

Technology (IT) Services In The

Department Of Defense

DoDI 8320.05 change 1 24-Jun-20 Electromagnetic Spectrum Data Sharing, Incorp Chng 1

DoDI 8330.01 27-Sep-22 Interoperability of Information Technology

(It), Including National Security Systems

(NSS), Incorp Chng 2

DoDI 8410.01 4-Jun-21 Internet Domain Name and Internet

Protocol Address Space Use and Approval

DoDI 8410.02 8-Dec-21 NETOPS for the Global Information Grid

(GIG)

ALL

DoDI 8410.03 19-Jul-17 Network Management (NM), Incorp Chng

ALL

T.O. 00-33B-5004-WA-

1, Rev 2

23-Jul-15 Methods And Procedures -- Access Control

For Information Systems

ALL

T.O. 00-33B-5006-WA-

1, Rev 1

15-Dec-17 Methods And Procedures – Computer

Security (COMPUSEC)

ALL

T.O. 00-33D-2002-WA-

1, Rev 12

26-Oct-18 Methods And Procedures --Cyberspace

Engineering, Installation Activities

Management

T.O. 00-33D-3004-WA-

1, 16-Jul-12 Methods And Procedures -- Managing

Cable And Antenna With The Cyberspace

Infrastructure Planning System (CIPS)

Visualization Component (CVC)

T.O. 00-33D-3005-WA-

1, Rev 2

29-Mar-19 Methods Procedures -- Managing The

Cyberspace Infrastructure with the

Cyberspace Infrastructure Planning System

(CIPS) Version 5