Bldg. 954 Combined PWS 11 Oct 22 (V1).docx

DOCX document 528 KB Posted

Attached to
Eglin LAN DROP
Solicitation number
FA2823-23-Q-A004
Issued by

View the file

Other files

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

COMM SOLUTION

Building 954 New NIPR Drops Task Order Performance Work Statement (PWS)

96TW-2022-00129
Organization:
96 TSSQ/RNXCO RT&T EOMS Contract
Address:
Bldg. 954 (Combined Projects)

Eglin AFB, FL 32542

1.0 Purpose

1.1 Install 10-total Plenum UTP Non-secure Internet Protocol Router (NIPR) white CAT 6 data cabling and jacks from Comm Room 126 to Rooms 165, 186, 119 and 112.

1.2 Specific Task Objectives

Contractor shall perform and/or adhere to the following:

1.3The contractor shall provide all materials and perform all work in strict adherence to the attached PWS, and the above applicable standards listed in section 6 and reference drawing attachment 1.
1.4In Comm Room 126 reuse existing Patch Panel and available ports in Rack 1.

1.5 Contractor shall create 5-each 2.5-inch wall penetrations and install 2-inch sleeves from the Comm Room 126 through the walls of rooms 124,161,165, and 186. Approx. 185 feet of J-hooks shall be installed using pathway illustrated in drawing T-001. Sleeves or slots shall not be left open except during cable installation and shall be properly fire stopped. Reference drawing T-001.

1.6 Install 6-total Plenum UTP Non-secure Internet Protocol Router (NIPR) white CAT 6 data cabling and jacks from Comm Room 126 to rooms 165 and 186. 4 port downward angled faceplates with upper and lower label windows shall be mounted flush in the drywall.

1.7 Install J-hooks from comm room 126 through room 116 and in the hallway to route to rooms 112 and 119. In room 116, core drywall and install a 2-inch fire rated sleeve into the hallway

1.8 Install 2-total Plenum UTP Non-secure Internet Protocol Router (NIPR) white CAT 6 data cabling and jacks from comm room 126 to room 112. 4 port downward angled faceplates with upper and lower label windows shall be mounted flush in the drywall

1.9 Install 2-total Plenum UTP Non-secure Internet Protocol Router (NIPR) white CAT 6 data cabling and jacks from comm room 126 to room 119. 4 port downward angled faceplates with upper and lower label windows shall be mounted flush in the drywall. Refer to drawing T-001

1.10 The contractor shall provide all materials and perform all work in strict adherence to the attached PWS, and the above applicable standards

1.11 Contractor shall provide fiber and copper cable slack within the cable tray or J-hooks for maintenance within the horizontal cabling system configuration as follows in Telecommunications room cable ladder - UTP/ScTP 10-feet and SM/MM 10-feet, Work area outlet - UTP/ScTP 1-foot and SM/MM 3.5-Feet above ceiling. Do not put slack or service loops in communications cabinets or racks

1.12 Category 6 network wiring shall be tested per industry standards, such as DB loss, head room, wire map, attenuation and length of the cable between the telecommunications room and the work area outlet or connection point. The test results shall be documented with equipment having a current calibration date

1.13 Telecommunications Rooms Grounding and Bonding: Contractor shall install telecommunications copper Primary Busbar (PBB) and conductors suitable for indoor installation in accordance with ANSI/TIA-607. Busbar(s) and conductor(s) must be made of copper or copper alloys having a minimum of 95% conductivity. Install ground conductor of appropriate sizing (#6 AWG up to #750 MCM) from the telecommunication room busbar location to the main building or servicing floor electrical panel in EMT conduit. Conduit shall be identified, tagged or labeled from point-to-point as Telecommunications Bonding Conductor (TBC). Connections of the TBC and the Telecommunications Bonding Backbone (TBB) shall utilize UL listed compression two-hole lugs or two-hole irreversible crimp connector. If two or more TBB are used in a multistory facility the TBB shall be bonded together with a Grounding Equalizer (GE) between telecommunication spaces. The GE shall be, as a minimum, the same size as the largest TBB. The following items shall be attached to the PBB…cable tray, cable ladder, racks, cabinets, metal conduits and PETs.

The government reserves the right to refuse final acceptance until all discrepancies have been resolved to the satisfaction of the government.

1.14 Plan illustrates our customers’ preliminary requirement. (See Attachment 1)

2.0 General Technical Requirement

The following design criteria provides additional requirements and guidance for Eglin AFB installations. These specific requirements are to be implemented by means of all applicable publications and documents referenced within this guide:

2.1.1 Inside Plant:

Common Patch Panel configuration with Modular style terminations. Site survey will be used to determine best arrangement to fit customer needs and system standards. Ladder rack and cable tray will be included in the TR design to properly facilitate cable routing. All cabinets, racks, ladder rack and cable tray will be grounded per Industry Standard, ANSI 607.

2.1.2 Telecomm Outlets/Jacks:

Single Gang Outlet Box - Flush Mount. (Single Gang Faceplate Mounting Bracket for Low Voltage Applications, 1-1/4" Maximum Wall Thickness, Finish: Pre-galvanized.)

Single Gang Outlet Box - Surface Mount. (Single gang two-piece screw together outlet box. Box accepts Pan-Way® Screw-On Faceplates or any NEMA standard single gang faceplate. For use with Pan-Way® LD profile raceway. 5.19in L x 3.45in W x 1.75in H (131.9mm x 87.7mm x 44.4mm). Breakouts for 1/2in, 3/4in, or 1in diameter conduit, International White) Single Gang 4 Port Faceplate. (4 port minimum. Mini Com Classic series single gang downward sloped faceplate that accepts four modular jacks, Off White) Data Jack. (The Category 6, RJ45, 8-position, 8-wire, UTP Mini-Com® universal jack module has TG-style termination. Off white) Blank Inserts. (Mini-Com® 1-port blank module, reserves space for future use, White) Surface Mount Raceway System. Tamper resistant two-piece latching surface raceway. Supplied with pre-punched mounting holes and factory applied adhesive tape. Available in 6', 8', and 10' lengths, Off White. Compatible with surface mount outlet box. Additionally, all surface mounted raceway systems shall be screwed to the wall to prevent adhesive from detaching from mounted surface.

2.1.3 Telecommunications Cabling:

Riser CAT 6. (CAT6+ (600MHz), 4-Pair, U/UTP-Unshielded, Riser-CMR, Premise Horizontal Cable, 23 AWG Solid Bare Copper Conductors, Polyolefin Insulation, X Spline, Ripcord, PVC Jacket) Plenum CAT 6. Copper Cable, Giga SPEED XL 2071E, 23 AWG, 4 Pair, Unshielded, UTP, Solid Bare Copper Conductor, FEP/PVC, CMP, (White jacket) Plenum CAT 6. Copper Cable, Giga SPEED, 23 AWG, 4 Pair, Shielded, ScTP, Solid Bare Copper Conductor, FEP/PVC, CMP, (Red jacket)

2.1.4 Cat 6 Connector Block (Patch Panel):

24/48 Port. Constructed for maximum strength and durability. Supports both T568A and T568B wiring configurations using an easy to read color-coded wiring label. Rack-mount modular panels shall include an integrated cable management requirement for cable routing and strain relief. Provide a complete modular system from patch panel to work area outlet.

Strain Relief Requirements. All Strain relief bars shall consist of a metal bar that mounts to the rear of a standard EIA 19" rack to support a minimum of 24 cables exiting from the back of a patch panel with a 2-inch to 5-inch inward mounted offset. Cables shall be secured with integrated adjustable clips, hook and loop strips or cable ties. Optional quick release brackets shall provide an easy way to remove the strain relief bar without the use of tools.

3.0Singularly Managed Infrastructure with Enterprise Level Security (SMI-ELS)
3.1Infrastructure Implementation and Operation
3.2Network Services and Solutions
3.2.1Site Preparation and Installation Services

The contractor shall perform site preparation and installation activities to support implementation of required services and solutions under this contract at any AF, DoD or other Federal Agency location.

3.2.2.Requirements Analysis and Conceptual Design
3.2.3Site Survey

The contractor shall perform site surveys at required locations. The findings of the site survey and any actions required in preparation for system installation shall be documented.

3.2.4 Installation

The contractor shall engineer, install, configure, modify, relocate or remove Communication and Information (C&I) systems for operational use. The systems and equipment installations or modifications must comply with established architectures. The contractor shall perform validation and verification testing on the system, assist users in configuring the system to meet their system requirements and provide all applicable operating manuals/system management guides. Further, the contractor shall provide pre-cutover and post-cutover on-site training IAW with TOs. The government will identify personnel who will receive this training. The training shall provide for in-depth hands-on maintenance, operations and database administration.

3.2.5 Inside Plant

The contractor shall, (as required by each TO), install and configure all the components for inside the plant (e.g., power, groundings, racks, fiber optic distribution panels, equipment, internal cabling, comm. closet, etc.). The contractor shall install and test all cable and components IAW accepted industry standards, unless superseded by a Government approved IS indicated within the TO. Electrical and communications cable, conduits, and circuits shall be installed IAW the National Electric Code (NEC). The contractor shall clearly label each end of every individual cable in accordance with the floor plans or engineering drawings. The contractor shall provide attached labels that are durable and legible. For any deviations to the specific installation specification, the contractor shall submit a proposal to the CO for approval.

3.2.6 Tools and Testing Support

The contractor shall provide all tools, installation materials and test equipment required to perform any required product installation and maintenance as called for by the TO. All tools and test equipment shall remain the property of the contractor. Any damage caused by the contractor to existing site facilities or equipment which might occur during site preparation, installation, testing or cutover of the system will be repaired at the expense of the contractor unless otherwise directed by the government. The site shall be restored to the original condition which existed prior to the event unless otherwise directed. The TO will specify testing and inspection requirements. The contractor shall demonstrate that the system design meets the reliability/availability/maintainability requirements of the TO.

4.0. DELIVERABLES

As-Built Documentation. Contractor format for deliverables is subject to Government acceptance. The installer shall provide accurate As-Built documentation of the entire install (i.e. rack elevations, cable route drawings, etc.) with type of cable path variations identified clearly. All deliverables shall be produced using recommended software tools/versions as accepted by the

Attachment 1

Government.

Standard Air Force NIPR/SIPR Data/Voice Wall-Mount Rack Elevation

Standard Air Force NIPR/SIPR Data/Voice Rack Elevation

5.0 Test and Acceptance Documentation.

The Contractor shall submit test reports within 3 duty days prior to final test and acceptance. The test reports shall show the tests performed to verify compliance with the specified performance criteria. Test reports shall include record of the physical parameters verified during testing. The contractor shall correct any errors or performance deficiencies detected by testing. The government reserves the right to refuse final acceptance until all discrepancies have been resolved to the satisfaction of the government.

6.0 APPLICABLE DOCUMENTS

APPLICABLE STANDARDS CONTRACTORS & INSTALLERS SHALL ADHEAR TO:

National Electrical Code (NEC) and National Electrical Manufacturers Association (NEMA) Standards: NFPA 70

Unified Facilities Criteria: (UFC) 3-520-1, 3-580-1, 4-010-06 dated most recent.

American National Standards Institute/Telecommunications Industry Association (ANSI/TIA) Standards: 568, 569, 606, 607 dated most recent.

National Electrical Contractors Association/Fiber Optic Association: (NECA/FOA) 301-2016 Installing and Testing Fiber Optics

96th Communications Squadron Cyber Infrastructure Design Guide, to include Applicable Publications and Standards referenced in Attachment G, dated FEB 2020

All DoD and Industry standards/guidelines shall be used to provide a complete system, from end to end.

Note: Since Standards are continually being revised, contractors and installers should refer to the latest version of any relevant standard for compliance.

7.Contractual Requirements
7.1Performance Reporting

The contractor’s performance will be monitored by the Government and reported in Contractor Performance Assessment Reporting (CPARs). Performance standards shall include the contractor’s ability to:

1. Provide quality products, incidentals and customer support.

2. Meet customer’s agreed-upon timelines for scheduled delivery of items, warranty, and/or incidental services: Emergency/critical, Maintenance/Warranty – 24 x 7 x 365, and remote OCONUS, OCONUS vs. CONUS response times.

3. Provide satisfactory product repairs or advance replacement, as appropriate.

4. Provide timely and accurate reports.

5. Respond to the customer’s requests for proposals and configuration assistance as identified in each delivery order.

6. Meet subcontracting goals.

7.2 Program Management

The contractor shall identify a Program Manager who shall be the primary representative responsible for all work awarded under this contract, participating in Program Management Reviews and ensuring all standards referenced herein are adhered to.

7.2.1 Services Delivery Summary

The Services Delivery Summary (SDS) will be in accordance with AFI 63-101, Acquisition and Sustainment Life Cycle Management and FAR Subpart 37.6, Performance-Based Acquisition. SLAs will be defined in each TO.

Desired Outcome
Performance Objective
Performance Threshold
Overall Outcome
Specific Outcomes
Target
Tolerance

Compliance with Infrastructure Solutions support requirements (delivery, quality)

Ensure compliance with Infrastructure Solutions deliverables requirements
Deliver the Infrastructure Solutions w/ predetermined outcomes and on time

Documentation submitted IAW CDRL A001 verifies the TO was completed on time

98% of the time

6.2.2 TO Management

The contractor shall establish and provide a qualified workforce capable of performing the required tasks. The workforce may include a project/TO manager who will oversee all aspects of the TO. The contractor shall use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and services, support management and decision-making and facilitate communications. The contractor shall identify risks, resolve problems and verify effectiveness of corrective actions. The contractor shall institute and maintain a process that ensures problems and action items discussed with the government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance should be tracked and lessons learned incorporated into applicable processes. The contractor shall establish and maintain a documented set of disciplined, mature and continuously improving processes for administering all contract and TO efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness and consistently high-quality delivery.

6.2.3 Configuration and Data Management

The contractor shall establish, maintain and administer an integrated data management system for collection, control, publishing and delivery of all program documents. The data management system shall include but not be limited to the following types of documents: CDRLs, White Papers, Status Reports, Audit Reports, Agendas, Presentation Materials, Minutes, Contract Letters and TO Proposals. The contractor shall provide the government with electronic access to this data, including access to printable reports. The contractor shall have an approved property control system IAW FAR 45, DFARS 245 and approved procedures to document and track all GFM and GFE. The contractor shall provide as-built documentation including, but not limited to, drawings and diagrams of the solution provided under each TO identifying specific cards in a chassis/shelf. The as-built documentation shall also include layout drawings, power drawings/specifications, floor plans and engineering specifications generated in support of the installation of the system. Documentation shall also include equipment listing with serial/model numbers and manufacturer specifications.

6.2.4 Records, Files and Documents

All physical records, files, documents and work papers, provided and/or generated by the government and/or generated for the government in performance of this PWS, maintained by the contractor which are to be transferred or released to the government or successor contractor, shall become and remain government property and shall be maintained and disposed of IAW AFMAN 33-363, Management of Records; AFI 33-364, Records Disposition – Procedures and Responsibilities; the Federal Acquisition Regulation, and/or the Defense Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the government or the contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS or the NetOps and Infrastructure Solutions contract of which this PWS is a part (including all clauses that are or shall be included or incorporated by reference into that contract).

6.3 Security Management

6.3.1 Safeguarding Classified Information

The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operations Manual (NISPOM) and the National Industrial Security Program Operating Manual (DoD 5220.22-M). These requirements shall be accomplished as specified in the TO. All Classified Contracts must have at a minimum, the Clause 52.204-2 Security Requirement, incorporated into the contract.

Each base will follow its own classified process IAW with the proscribed Federal guidance of the NISPOM and FAR “Subpart 4.4 along with DD Form 254. When transmitting classified information ensure all classified information is properly sanitized and/or degaussed of all sensitive/classified information IAW AFSSI 5020.

6.3.2 Personnel Security

Individuals performing work under these TOs shall comply with applicable program security requirements as stated in the TO. NETCENTS-2 will support the following levels of security: Unclassified; Unclassified, But Sensitive; Secret (S); Secret Sensitive Compartmented Information (S/SCI); Top Secret (TS) and Top Secret Sensitive Compartmented Information (TS/SCI).

6.3.5 Travel Requirements

The contractor shall coordinate specific travel arrangements with the individual CO or COR to obtain advance, written approval for the travel about to be conducted. The contractor’s request for travel shall be in writing and contain the dates, locations and estimated costs of the travel in accordance with the basic contract clause H047.

If any travel arrangements cause additional costs to the TO that exceed those previously negotiated, written approval by CO is required, prior to undertaking such travel. Costs associated with contractor travel shall be in accordance with FAR Part 31.205-46, Travel Costs. The contractor shall travel using the lower cost mode transportation commensurate with the mission requirements. When necessary to use air travel, the contractor shall use the tourist class, economy class or similar accommodations to the extent they are available and commensurate with the mission requirements. Travel will be reimbursed on a cost reimbursable basis; no profit or fee will be paid.

6.3.6 Other Direct Cost (ODC)

The contractor shall identify ODC and miscellaneous items as specified in each TO. No profit or fee will be added; however, DCAA approved burdened rates are authorized.

Appendix A1 – NetOps Standards & References

Instruction: This document serves as a one-stop-shop for easy reference of applicable certifications, specifications, standards, policies and procedures that may be placed on individual contract task orders. Tailor the list as needed when individual TOs may impose additional standards to those required at the contract level. The list is not all-inclusive and the most current version of the document at the time of TO issuance will take precedence. Web links are provided wherever possible. Include your tailored list in Section 7 of the Performance Work Statement, Applicable Standards and References.

NETWORK OPERATIONS AND INFRASTRUCTURE SOLUTIONS

(COMPLIANCE)

Standard
URL
Description
1.
AFI 10-206 Operational Reporting
http://static.e-publishing.af.mil/production/1/af_a3_5/publication/afi10-206/afi10-206.pdf
This instruction implements Air Force Policy Directive (AFPD) 10-2, Readiness. It applies to all US Air Force Major Commands (MAJCOM), Air National Guard (ANG), Air Force Reserve Command (AFRC), Field Operating Agencies (FOA), and Direct Reporting Units (DRU). Prior to mobilization/activation AF, ANG, and AFRC units will address the HQ AF Service Watch Cell (AFSWC) on all applicable record copy Air Force Operational Reports (AF OPREP-3). It establishes and describes the Air Force Operational Reporting System. It explains the purpose and gives instructions for preparing and submitting these reports. Refer recommended changes and questions about this publication to AF/A3O, 1480 Air Force Pentagon, Washington, D.C. 20330-1480, Office of Primary Responsibility (OPR) using the AF Form 847, Recommendation for Change of Publication. MAJCOMs are authorized to supplement this Air Force Instruction (AFI) instead of repeating instructions in separate directives.
2.
AFI 10-208 Air Force Continuity of Operations (COOP) Program.
http://static.e-publishing.af.mil/production/1/af_a3_5/publication/afi10-208/afi10-208.pdf
This Instruction implements Air Force Policy Directive (AFPD) 10-2, Readiness, and is consistent with AFPD 10-8, Homeland Security. It describes policy and requirements for implementing DODI 3020.42, Defense Continuity Plan Development, and DODI O-3020.43, Emergency Management and Incident Command of the Pentagon Facilities; DODI O-3000.08 Balanced Survivability Assessments (BSAs);and O-DODI 5110.11, Raven Rock Mountain Complex (RRMC).
3.
AFI 10-601 Operational Capability Requirements Development
http://static.e-publishing.af.mil/production/1/af_a3_5/publication/afi10-601/afi10-601.pdf
The primary intent of this instruction is to facilitate timely development and fielding of affordable and sustainable operational systems needed by the combatant commander. The primary goal is to fulfill stated defense strategy needs with effects based, capabilities-focused materiel and non-materiel solutions. These solutions must be well integrated to provide suitable, safe, and interoperable increments of capability that are affordable throughout the life cycle.
4.
AFI 10-701 Operations Security (OPSEC)
http://static.e-publishing.af.mil/production/1/af_a3_5/publication/afi10-701/afi10-701.pdf
This publication provides guidance for all Air Force personnel (military and civilian) and supporting contractors in implementing, maintaining and executing OPSEC programs. It describes the OPSEC process and discusses integration of OPSEC into Air Force plans, operations and support activities.
5.
AFI-1604 Air Force Information Security Program
http://static.e-publishing.af.mil/production/1/saf_aa/publication/afi16-1404/afi16-1404.pdf
This publication implements Air Force Policy Directive (AFPD) 16-14, Security Enterprise Governance; Department of Defense (DoD) Directive 5210.50, Management of Serious Security Incidents Involving Classfied Information, DoD Instruction (DoDI) 5210.02, Access and Dissemination of RD and FRD, DoDI 5210.83, DoD Unclassified Controlled Nuclear Information (UCNI), DoD Manual (DoDM) 5200.01, DoD Information Security Program, Volume 1, Volume 2, Volume 3, and Volume 4; and DoDm 5200.45, Instructions for Developing Security Classification Guides.
6.
AFI 31-501 Personnel Security Program Management
http://static.e-publishing.af.mil/production/1/af_a4_7/publication/afi31-501/afi31-501.pdf
Use this instruction with the DOD Regulation 5200.2-R and AFPD 31-5 to implement the personnel security program. This instruction requires collecting and maintaining information protected by the Privacy Act of 1974 authorized by Executive Orders 9397, 9838, 10450, 11652, and 12968; and 5 United States Code (U.S.C.) 7513, 7532, 7533; 10 U.S.C. 8013.
7.
AFI 32-10112 Installation Geospatial Information and Services (Installation GI&S)
http://static.e-publishing.af.mil/production/1/af_a4_7/publication/afi32-10112/afi32-10112.pdf
This instructions convey guidance and procedures allowing commanders and Air Force professionals to maintain a flow of timely geospatial information with due regard for national security, accuracy, and privacy. Describe Geospatial Information and Services (GI&S) support for the installation and facilities mission, hereafter referred to as the GeoBase Program or GeoBase. Explain the organization and execution of the GeoBase Program for all levels of command. GI&S is the key platform for cross functional integration, and to that end this AFI provides guidance for those organizations seeking to integrate with the Geo-Base Service. Provide guidance and procedures for all Air Force military and civilian personnel that perform or utilize GeoBase functions, products or systems, including those in the Air National Guard and U.S. Air Force Reserve. This instruction is not intended to overlap or supersede GI&S guidance found in AFI 14-205, Geospatial Information and Services, 4 May 2004. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with AFMAN 37-123, Management of Records and disposed of in accordance with the Air Force Records Disposition Schedule (RDS) located at https://afrims.amc.af.mil/. The use of the name or mark of any specific manufacturer, commercial product, commodity, or service in this publication does not imply endorsement by the Air Force.
8.
AFI 33-332 Air Force Privacy And Civil Liberties Program
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-332/afi33-332.pdf
Records that are retrieved by name or other personal identifier of a U.S. citizen or alien lawfully admitted for permanent residence are subject to Privacy Act requirements and are referred to as a Privacy Act system of records. The Air Force must publish SORNs in the Federal Register, describing the collection of information for new, changed or deleted systems to inform the public and give them a 30 day opportunity to comment before implementing or changing the system.
9.
AFI 33-364 Records Disposition Procedures and Responsibilities
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-364/afi33-364.pdf
Records Disposition Procedures
10.
AFI 33-401 Air Force Architecting
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-401/afi33-401.pdf
This Air Force Instruction (AFI) implements Air Force Policy Directive (AFPD) 33-4, Enterprise Architecting. This instruction describes the federation of Air Force architectures and its concept for federated architecture development, its associated business rules, governance, and the roles and responsibilities for appropriate Air Force organizations.
11.
AFI 33-580 Spectrum Management
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-580/afi33-580.pdf
This instruction establishes guidance and procedures for Air Force-wide management and use of the electromagnetic spectrum and implements Department of Defense Instruction (DoDI) 4650.01, Policy and Procedures for Management and Use of the Electromagnetic Spectrum; DoDI 8320.05, Electromagnetic Spectrum Data Sharing; National Telecommunications and Information Administration (NTIA) Manual of Regulations and Procedures for Federal Radio Frequency Management; Air Force Policy Directive (AFPD) 33-5, Warfighting Integration; and the procedures established by the Joint Staff J65A United States Military Communications-Electronics Board (USMCEB).
12.
AFI 33-590 Radio Management
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-590/afi33-590.pdf
This standard specifies requirements for types of land mobile radios, frequency ranges and encryption standards. It provides requirements processing, validation, and handling procedures for classified and unclassified Personal Wireless Communication Systems (PWCS), and training. It provides procedures for the management, operation, and procurement of commercial wireless service for all PWCS.
13.
AFI 36-2201 Air Force Training Program
http://static.e-publishing.af.mil/production/1/af_a1/publication/afi36-2201/afi36-2201.pdf
This Air Force Instruction (AFI) applies to Total Force – Active Duty, Air Force Reserve, Air National Guard (ANG), and Department of Air Force Civilian. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with AFMAN 33-363, Management of Records, and disposed of in accordance with the Air Force Records Disposition Schedule (RDS) located at https://www.my.af.mil/afrims/afrims/afrims/rims.cfm. Refer recommended changes and questions about this publication to the Office of Primary Responsibility (OPR) using the AF IMT 847, Recommendation for Change of Publication; route AF IMT 847s from the field through Major Commands (MAJCOMS) publications/forms managers.
14.
AFI 61-204 Disseminating Scientific And Technical Information
http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi61-204/afi61-204.pdf
This instruction updates the procedures for identifying export-controlled technical data and releasing export-controlled technical data to certified recipients and clarifies the use of the Militarily Critical Technologies List. It establishes procedures for the disposal of technical documents.
15.
AFI 99-103 Capabilities-Based Test And Evaluation
http://static.e-publishing.af.mil/production/1/af_te/publication/afi99-103/afi99-103.pdf
It describes the planning, conduct, and reporting of cost effective test and evaluation (T&E) programs as an efficient continuum of integrated testing known as seamless verification. The overarching functions of T&E are to mature sys-tem designs, manage risks, identify and help resolve deficiencies as early as possible, and ensure systems are operationally mission capable (i.e., effective and suitable). The Air Force T&E community plans for and conducts integrated testing as an efficient continuum known as seamless verification in collaboration with the requirements and acquisition communities.
16.
AFMAN 33-152 User Responsibilities and Guidance for information Systems
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afman33-152/afman33-152.pdf
This instruction implements Air Force Policy Directive (AFPD) 33-1, Information Resources Management, AFPD 33-2, Information Assurance (IA) Program, and identifies policies and procedures for the use of cyberspace support systems/services and compliance requirements of Secretary of the Air Force, Chief of Warfighting Integration and Chief Information Officer (SAF/CIO A6) managed programs. These programs ensure availability, interoperability, and maintainability of cyberspace support systems/services in support of Air Force mission readiness and warfighting capabilities. This manual applies to all Air Force military, civilians, contractor personnel under contract by the Department of Defense (DOD), and other individuals or organizations as required by binding agreement or obligation with the Department of the Air Force. This manual applies to the Air National Guard (ANG) and the Air Force Reserve Command (AFRC).
17.
AFMAN 33-153 Information Technology (IT) Asset Management (ITAM)
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afman33-153/afman33-153.pdf
This Air Force Manual (AFMAN) implements Executive Order (E.O.) 13103, Computer Software Piracy and Air Force Policy Directives (AFPD) 33-1, Cyberspace Support and supports AFPD 33-2, Information Assurance (IA) Program; AFPD 63-1/20-1, Integrated Life Cycle Management; and AFPD 10-6, Capabilities-Based Planning & Requirements Development. This AFMAN provides the overarching guidance and direction for managing IT hardware and software. The hardware management guidance identifies responsibilities for supporting Air Force (AF) IT hardware (IT assets) and maintaining accountability of Personal Wireless Communications Systems (PWCS) including cellular telephones and pagers. The software management guidance identifies responsibilities for management of commercial off-the-shelf (COTS) and AF-unique software acquired/developed by the AF (other than software internal to a weapon system; see AFPD 63-1/20-1, Integrated Life Cycle Management).
18.
AFMAN 33-282 Computer Security (COMPUSEC)
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afman33-282/afman33-282.pdf
This AFMAN implements Computer Security in support of AFPD 33-2, Information Assurance Program and AFI 33-200, IA Management Computer Security (COMPUSEC) is defined within the IA Portion of AFI 33-200.
19.
AFMAN 33-363 Management of Records
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afman33-363/afman33-363.pdf
This manual implements Department of Defense (DoD) Directive (DoDD) 5015.2, DoD Records Management Program, and Air Force Policy Directive (AFPD) 33-3, Information Management. It establishes the requirement to use the Air Force Records Information Management System (AFRIMS); establishes

guidelines for managing all records (regardless of media); and defines methods and the format for record storage, file procedures, converting paper records to other media or vice versa, and outlines the minimum to comply with records management legal and policy requirements.

20.
AFPD 33-3 Information Management
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-3/afpd33-3.pdf
This policy directive establishes Air Force policy for the management of information assets (all forms of data and content), across all AF information sources, as both a strategic resource and corporate asset supporting the warfighter during mission and support operations.
21.
AFPD 33-4 Information Technology Governance
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-4/afpd33-4.pdf
This directive establishes the AF policy for IT Governance to fulfill the AF CIO responsibilities established in federal laws and DoD issuances and the AF IT Governance Executive Board, which will oversee existing IT investment councils, boards, and working groups throughout the IT lifecycle to effectively and efficiently deliver capabilities to users. This directive focuses on aligning IT policy, CIO policy, and capabilities management with doctrine, statutory, and regulatory guidelines that govern accountability and oversight over IT requirements to resource allocation, program development, test, and deployment and operations under the direction and authority of the AF IT Governance Executive Board chaired by the AF CIO.
22.
DoDI 8510.01 - DoD Risk Management Framework (RMF) for DoD Information Technology
http://www.dtic.mil/whs/directives/corres/pdf/851001_2014.pdf
Provides procedural guidance for the reciprocal acceptance of authorization decisions and artifacts within DoD, and between DoD and other federal agencies, for the authorization and connection of information systems (ISs).

Revised from 2007 version on 12 March 2014.

23.
DoDI 8500.01 – Cyber Security (CS)
http://www.dtic.mil/whs/directives/corres/pdf/850001_2014.pdf
The purpose of the Defense Cybersecurity program is to ensure that IT can be used in a way that allows mission owners and operators to have confidence in the confidentiality, integrity, and availability of IT and DoD information, and to make choices based on that confidence
24.
DoDI 8551.01 – Ports, Protocols and Services Management
http://www.dtic.mil/whs/directives/corres/pdf/855101p.pdf
25.
CJCSI 6211.02D – Defense Information Systems Network (DISN) Responsibilities
http://www.dtic.mil/cjcs_directives/cdata/unlimit/6211_02.pdf
This instruction establishes policy and responsibilities for the connection of information systems (ISs) (e.g., applications, enclaves, or outsourced processes) and unified capabilities (UC) products to the DISN provided transport (including data, voice, and video) and access to information services transmitted over the DISN (including data, voice, video, and cross-domain).
26.
DFARS 252.227-7013 Rights in Technical Data Non-Commercial Items
http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/dfars/Dfars252_227.htm#P696_47162
Provides guidelines for rights in technical data on non-commercial items
27.
Department of Defense Architecture Framework (DoDAF) Ver2.02 Aug 2010
http://dodcio.defense.gov/dodaf20.aspx
The Department of Defense Architecture Framework (DoDAF), Version 2.0 is the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of Department of Defense (DoD) managers at all levels to make key decisions more effectively through organized information sharing across the Department, Joint Capability Areas (JCAs), Mission, Component, and Program boundaries. The DoDAF serves as one of the principal pillars supporting the DoD Chief Information Officer (CIO) in his responsibilities for development and maintenance of architectures required under the Clinger-Cohen Act. DoDAF is prescribed for the use and development of Architectural Descriptions in the Department. It also provides extensive guidance on the development of architectures supporting the adoption and execution of Net-centric services within the Department.
28.
DFARS 252.227-7014 Rights in Non-commercial Computer Software
http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/dfars/Dfars252_227.htm#P696_47162
Guidance on rights in technical data and computer software small business innovation research (SBIR) program.
29.
DFARS 252.227-7015 Technical Data Commercial Items
http://www.acq.osd.mil/dpap/dars/dfars/html/current/227_71.htm#227.7102-2
Provides the Government specific license rights in technical data pertaining to commercial items or processes. DoD may use, modify, reproduce, release, perform, display, or disclose data only within the Government. The data may not be used to manufacture additional quantities of the commercial items and, except for emergency repair or overhaul and for covered Government support contractors, may not be released or disclosed to, or used by, third parties without the contractor's written permission.
30.
DFARS 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions
http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/dfars/Dfars252_227.htm#P1182_92447
Provides requirements for the identification and assertion of technical data.
31.
DoD 5220.22-M, National Industrial Security Program Operating Manual
http://www.dtic.mil/whs/directives/corres/pdf/522022m.pdf
Provides baseline standards for the protection of classified information released or disclosed to industry in connections with classified contracts under the National Industrial Security Program.
32.
DoD Discovery Metadata Specification (DDMS)
https://metadata.ces.mil/dse/irs/DDMS/
Visibility, accessibility, and understandability are the high priority goals of the DoD Net-Centric Data Strategy. Of these goals, visibility and discovery are intimately linked. Visibility of a resource is, in a practical sense, useless, if the resource is not easily discoverable. With the express purpose of supporting the visibility goal of the DoD Net-Centric Data Strategy, the DDMS specifies a set of information fields that are to be used to describe any data or service asset, i.e., resource, that is to be made discoverable to the Enterprise, and it serves as a reference for developers, architects, and engineers by laying a foundation for Discovery Services.
33.
DoD Manual 5200.01, DoD Information Security Program: Overview, Classification, and Declassification, V1-V4
http://www.dtic.mil/whs/directives/corres/pdf/520001_vol1.pdf
The purpose of this manual is to implement policy, assign responsibilities, and provide procedures for the designation, marking, protection, and dissemination of controlled unclassified information (CUI) and classified information, including information categorized as collateral, sensitive compartmented information (SCI), and Special Access Program (SAP).
34.
TIA/EIA-TSB-72, Centralized Optical Fiber Cabling Guidelines
http://www.tiaonline.org/
Must be purchased.

ANSI/TIA/EIA-568-B series standard incorporates and refines the technical content of TSB67, TSB72, TSB75, TSB95 and TIA/EIA-568-A-1, A-2, A-3, A-4 and A-5.

35.
DoD Mobile Application Strategy
http://archive.defense.gov/news/dodmobilitystrategy.pdf
It is intended to align the progress of various mobile device pilots and initiatives across DoD under common objectives, ensuring that the warfighter benefits from such activities and aligns with efforts composing the Joint Information Environment.
36.
DoD CIO Net-Centric Data Strategy
http://dodcio.defense.gov/Portals/0/Documents/Net-Centric-Data-Strategy-2003-05-092.pdf
This Strategy lays the foundation for realizing the benefits of net centricity by identifying data goals and approaches for achieving those goals. To realize the vision for net-centric data, two primary objectives must be emphasized: (1) increasing the data that is available to communities or the Enterprise and (2) ensuring that data is usable by both anticipated and unanticipated users and applications. (Source: Department of Defense Net-Centric Data Strategy, DoD CIO, 9 May 2003
37.
DoD CIO Net-Centric Services Strategy
http://dodcio.defense.gov/Portals/0/documents/DoD_NetCentricServicesStrategy.pdf
The DoD Net-Centric Services Strategy (NCSS) [R1313] builds upon the DoD Net-Centric Data Strategy's (May 2003) goals of making data assets visible, accessible, and understandable. The NCSS establishes services as the preferred means by which data producers and capability providers can make their data assets and capabilities available across the DoD and beyond. It also establishes services as the preferred means by which consumers can access and use these data assets and capabilities.
38.
DoDD 5205.02E, Operations Security (OPSEC) Program
http://www.dtic.mil/whs/directives/corres/pdf/520502e.pdf
Underscores the importance of OPSEC and how it is integrated as a core military capability within Information Operations (IO) that must be followed in daily application of military operations.
39.
DoDD 8000.01 Management of the Department of Defense Information Enterprise
http://www.dtic.mil/whs/directives/corres/pdf/800001p.pdf
Provides direction on creating an information advantage for DoD personnel and mission partners, and establishing and defining roles for CIOs at various levels within the Department of Defense
40.
DoDD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the DoD Global Information Grid (GIG)
http://www.dtic.mil/whs/directives/corres/pdf/810002p.pdf
Establishes policy and assigns responsibilities for the use of commercial wireless devices, services, and technologies in the DoD Global Information Grid (GIG) (DoD Directive 8100.1, "Global Information Grid (GIG) Overarching Policy," September 19, 2002). Directs the development and use of a Knowledge Management (KM) process to promote the sharing of wireless technology capabilities, vulnerabilities, and vulnerability mitigation strategies throughout the Department of Defense. Promotes joint interoperability using open standards throughout the Department of Defense for commercial wireless services, devices, and technological implementations.
41.
DoDI 1100.22 Policy and Procedures For Determining Workforce Mix
http://www.dtic.mil/whs/directives/corres/pdf/110022p.pdf
Provides manpower mix criteria and guidance for risk assessments to be used to identify and justify activities that are inherently governmental (IG); commercial (exempt from private sector performance); and commercial (subject to private sector performance).
42.
AFI 63-101/20-101, Integrated Life Cycle Management
http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-101_20-101/afi63-101_20-101.pdf
It identifies elements of Air Force systems engineering (SE) practice and management required to provide and sustain, in a timely manner, cost-effective products and systems that are operationally safe, suitable, and effective.
43.
DoDI 3222.03, DoD Electromagnetic Environmental Effects (E3) Program
http://www.dtic.mil/whs/directives/corres/pdf/322203p.pdf
Reissue DoD Directive (DoDD) 3222.3 (Reference (a) as a DoD instruction (DoDI) in accordance with the authority in DoDD 5144.02 (Reference (b)).

The mission of the DoD E3 IPT is to promote communication, coordination, commonality, and synergy among the DoD Components for E3-related matters.

44.
DoDD 5230.24, Distribution Statements on Technical Documents
http://www.dtic.mil/whs/directives/corres/pdf/523024p.pdf
This instruction updates policies and procedures for marking technical documents, including production, engineering, and logistics information, to denote the extent to which they are available for distribution, release, and dissemination without additional approvals or authorizations.
45.
AFI 33-200, Air Force Cybersecurity Program Management
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-200/afi33-200.pdf
This AFI provides general direction for implementation of IA and management of IA programs according to AFPD 33-2. Compliance ensures appropriate measures are taken to ensure the availability, integrity, and confidentiality of Air Force ISs and the information they process. Using appropriate levels of protection against threats and vulnerabilities help prevent denial of service, corruption, compromise, fraud, waste, and abuse.
46.
AFI 33-210, AF Certification and Accreditation (C&A) Program (AFCAP)
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-210/afi33-210.pdf
AF C&A program guidance
47.
DODI 8330.01 Interoperability of Information Technology (IT), Including National Security Systems (NSS)
http://www.dtic.mil/whs/directives/corres/pdf/833001p.pdf
Establishes policy, assigns responsibilities, and provides direction for certifying the interoperability of IT and NSS pursuant to sections 2222, 2223, and 2224 of Title 10, United States Code (Reference (c)). Establishes a capability-focused, architecture-based approach for interoperability analysis. Establishes the governing policy and responsibilities for interoperability requirements development, test, certification and prerequisite for connection of IT, including NSS (referred to in this instruction as “IT”). Defines a doctrine, organization, training, materiel, leadership and education, personnel, facilities, and policy (DOTMLPF-P) approach to enhance life-cycle interoperability of IT. Establishes the requirement for enterprise services to be certified for interoperability. Incorporates and cancels DoDD 4630.05, DoDI 4630.8, and DoD Chief Information Officer (CIO) memorandum (References (d), (e), and (f)).
48.
NetCentric Enterprise Solutions for

Interoperability (NESI)

https://nesix.spawar.navy.mil/home.html
NESI is a body of architectural and engineering knowledge that guides the design, implementation, maintenance, evolution, and use of the Information Technology (IT) portion of net-centric solutions for defense application.
49.
AFMAN 33-145 Collaboration Services and Voice Systems Management
http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afman33-145/afman33-145.pdf
It establishes procedures and guidance for Collaboration Services including electronic collaboration and management of Video Teleconferencing (VTC) resources to include systems, equipment, personnel, time, and money and provides the directive guidance for Air Force VTC and voice systems management activities.
50.
DoDI 8520.02 Public Key Infrastructure (PKI) and Public Key (PK) Enabling
http://www.dtic.mil/whs/directives/corres/pdf/852002p.pdf
This instruction establishes and implements policy, assign responsibilities, and prescribe procedures for developing and implementing a DoD-wide PKI and enhancing the security of DoD information systems by enabling these systems to use PKI for authentication, digital signatures, and encryption.
51.
Installation Energy Management
http://www.dtic.mil/whs/directives/corres/pdf/417011p.pdf
ENERGY STAR is a joint program of the U.S. Environmental Protection Agency and the U.S. Department of Energy helping us all save money and protect the environment through energy efficient products and practices. It was enacted by Executive Order 13423 and governed by FAR 23.704.
52.
Federal Information Security Management Act (FISMA) 2002
http://www.dhs.gov/federal-information-security-management-act-fisma
FISMA was enacted as part of the E-Government Act of 2002 to “provide a comprehensive framework for ensuring the effectiveness of information security controls over information resources that support Federal operations and assets,” and also to “provide for development and maintenance of minimum controls required to protect Federal information and information systems.”

FISMA requires Federal agencies to:

•designate a Chief Information Officer (CIO), •delegate to the CIO authority to ensure compliance with the requirements imposed by…

This is the start of the file's text. The full file is on GovTribe.

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