PWS_13_June_2014.docx

DOCX document 2 MB Posted

Attached to
45SW Comm-GIMS
Solicitation number
FA2521-14-Q-B103
Issued by

View the file

Other files

File Type Posted
Atch_1 _MOB_ _GSU_Comm-Facilities_List.xlsx XLSX spreadsheet
Atch_5 _QASP_45SW_Com-GIMS.docx DOCX document
Atch_4 _Executive_Pkg.pdf PDF
Atch_3 _Geobase_Policy.pdf PDF
Atch_2 _TO_00-33A-1001.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

45SW Comm-GIMS Phase 12, Replicate existing MOB Inside Cable Plant (ICP) Comm Layer Tool to GSUs, Replicate existing GSU Telephone Records Tool to MOB and GSUs, Add Legacy CSIRs, Non-standard Drawing Floor Plans & Equipment, Communications Rooms & Data Centers Performance Work Statement (PWS) Dated 13 Jun 14

Name:
45th Space Wing
Organization:
45th Space Communications Squadron (45 SCS)
Address:
Patrick Air Force Base, FL

Executive Summary

Replicate existing 45th Space Wing (45SW) Communications Geographical Information Management System (Comm-GIMS – aka GIMS) Inside Cable Plant (ICP) Tool from MOB (Patrick AFB - PAFB) to GSUs (Cape Canaveral AFS (CCAFS), Antigua AS (ANT), Ascension AAS (ASC)), replicate existing GSU Telephone Records Tool to MOB and GSUs, add legacy CSIR (Communications System Installation Records), Non-standard Floor Plans Comm-Drawing of Equipment, Communications Rooms & Data Centers.

CIPS Requirement: SXHT-07-00017

45SW Comm-GIMS Phase 12, Replicate existing MOB Inside Cable Plant (ICP) Comm Layer Tool to GSUs, Replicate existing GSU Telephone Records Tool to MOB and GSUs, Add Legacy CSIRs, Non-standard Drawing Floor Plans & Equipment, Communications Rooms & Data Centers

1. PURPOSE

This requirement is established for the purpose of delivering GIMS toolsets uniformity between MOB and GSUs. Instituting uniformity thru replication of existing GSU telephone records tool and by adding legacy CSIRs, Non-standard Drawing Floor Plans & Equipment, Communications Rooms & Data Centers at MOB & each GSU into GIMS. This effort will allow communication system maintainers of the geospatial relational communications databases employed across the Eastern Range the ability to troubleshoot and repair communication infrastructures.

2. SCOPE

CIPS requirement SXHT-07-00017, GIMS, states that the infrastructure mapping and planning tool is to provide rapid reconfiguration information management reporting tools for the 45SW Comm-Infrastructure for management of existing and planned communications assets IAW AF Policy directives: AFTO 00-33A-1001, see attachment 2, and HAF Policy Memorandum, 7 Oct 02, USAF GeoBase Policy Memo, see attachment 3 & 4. Currently the basic ICP tool is installed at MOB. Currently the Telephone Records Tool is installed at GSU (CCAFS).

3. REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

This requirement is established for the purpose of delivering GIMS toolsets uniformity between MOB and GSUs. Instituting uniformity thru replication of existing GSU telephone records tool and by adding legacy CSIRs, Non-standard Drawing Floor Plans & Equipment, Communications Rooms & Data Centers at MOB & each GSU into GIMS as follows:

3.1. Replicate MOB Inside Cable Plant (ICP), GSU Telephone Records Tool and apply MOB and GSU data products with integrations to standardize GIMS applications by surveying each sites ICP data and replicating telephone records & ICP Comm layer tools into each MOB/GSU. Apply ICP-data Layers (i.e., telephone records, comm-paths, floor plan infrastructure, circuit and cable records, buildings’ comm-room data and data centers) thru Civil Engineering’s (CE) Base Visualization Tool (BVT) Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) of CE’s Common Installation Picture (CIP) on each GSU.

3.2. Provide the following abilities to each GSU as replicated from the MOB ICP & GSU Telephone Records tools: View, edit and analyze circuits routing from Comm-facility (see 2.1.3) ICP demarc to com-room hub(s), cable types, cable circuits’ paths, cable routing to applicable equipment elevation racks, equipment & interconnects, floor plan equipment location, cable record (CR) diagrams, telephone records and Circuit Line Record Cards (CLRC). Contractor’s cost proposal should be based on the use of government-provided floor plans. See attachment one for MOB & GSU Comm-Facilities List.

3.3. Provide tools as replicated from the MOB ICP to each GSU to display, search, insert symbols from libraries; query and edit Cable Record, and Cable Plant data reporting tools; and integrate existing GIMS communications infrastructure to increase capacity and speed and enhance configuration management.

3.4. Provide gathered MOB ICP Comm-Room and Data Center equipment, racks and cable records, circuit line record card (CLRC) circuit data into ICP. Automated cut-sheet population shall be accurately shown as they relate to building floor plan locations. Interior cable run lengths will be calculable automation from geospatial relational data sets perspective location.

3.5. Provide as replicated from the MOP ICP to each GSU ICP: faster search, query and data gathering abilities severed to system users, one web application accessible by Common Access Card (CAC enabled) in format for joining all of GSUs and MOB geospatial relational data sets.

3.6. Provide data compression integration to GSUs and MOB Comm-GIMS products to increase speed for greater configuration management, including faster search and query tools for surveying communication circuit records and enhanced “end to end” tracing and re-configuration management tools.

3.7. All deliverables must meet professional GCMDS (Geobase Communications Model Data Standards) mapping and ANSI (American National Standards Institute) standards along with the requirements set forth in contract documents. The contractor shall be responsible for delivering all items specified within the tasks of each objective.

3.8. The contractor shall deliver a GCMDS-compliant dataset of COMM data in 45SW Comm-GIMS multi-user geo-database format that is storable and servable in Oracle for MOB and GSUs.

3.9. Provide a minimum of four (4) days of hands-on training for total sixty (60) 45SW Comm-GIMS Editors

4. CONTRACTUAL REQUIREMENTS

4.1 Place of Performance: Patrick Air Force Base, FL

4.2 Normal Hours of Operation

The average workweek is 40 hours. The normal work hours 7:00 AM and 5:00 PM, Monday through Friday or as specified in this TO, except for days listed in Clause G021, Contract Holidays, in the overarching ID/IQ contract. Work in excess of the standard 40 hour work week requires prior written approval by the Contracting Officer

4.3 Government Furnished Property: Not Applicable

4.4 Billable Hours: Not Applicable

4.5 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the Award Contracting Officers (CO) immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government. These operating procedures may be superseded by Theater Commander’s direction during deployments.

4.6 Contractor Identification

All contractor/subcontractor personnel shall be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation. Refer to Clause H063 of the overarching ID/IQ contract.

4.7 Performance Reporting

The contractor’s award performance will be monitored by the Government and reported in Contractor Performance Assessment Reports (CPARs) or a Customer Survey, depending on the dollar amount of the award. Performance standards shall include the contractor’s ability to provide or satisfy the following:

· Provide satisfactory solutions to requirements with the necessary customer support

· Provide solutions and services that meet or exceed specified performance parameters

· Deliver timely and quality deliverables to include accurate reports and responsive proposals

· Ensure solutions to requirements are in compliance with applicable policy and regulation

4.8 Program Management / Project Management

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

5.1 Services Delivery Summary

See Quality Assurance Surveillance Plan (QASP); attachment 4

5.1.2 Award Management

The contractor shall establish and provide a qualified workforce capable of performing the required tasks. The workforce may include a project/task order manager who will oversee all aspects of the award. The contractor shall use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, 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 shall 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 efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness, and consistently high-quality delivery. The contractor shall provide transition plans as required.

5.1.3 Documentation 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 Award Proposals. The contractor shall provide the Government with electronic access to this data, including access to printable reports.

5.1.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 Application Services contract of which this PWS is a part (including all clauses that are or shall be included or incorporated by reference into that contract).

5.1.5 Personnel Security

Individuals performing work under this award shall comply with applicable program security requirements as stated in the award.

This award may require personnel security clearances up to and including Top Secret, and may require all employees to be United States citizens. The security clearance requirements will depend on the security level required by the proposed award. The award may also require access to sensitive compartmented information (SCI) for which SCI eligibility will be required. Contractors shall be able to obtain adequate security clearances prior to performing services under the award. The Contract Security Classification Specification (DD Form 254) will be at the basic contract and will encompass all security requirements. All contractors located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10-701, Operations Security. In accordance with DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants, and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries (NACI).

The types of Personnel Security Investigations (PSI) required for the contractor vary in scope of investigative effort depending upon requirements of the Government and/or conditions of the award. In cases where access to systems such as e-mail is a requirement of the Government, application/cost for the PSI shall be the responsibility of the Government. In cases where access to systems is as a condition of the Award, application/cost for the appropriate PSI shall be the responsibility of the contractor. In such instances, the contractor shall diligently pursue obtaining the appropriate PSI for its employees prior to assigning them to work any active award. Acquisition planning must consider Anti-Terrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in-transit forces), information systems and communications systems IAW DoD Instructions 2000.16 Anti-Terrorism Standards.

5.1.5.1 Transmission of Classified Material

The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operating Manual (DoD 5220.22-M). These requirements shall be accomplished as specified in this award.

5.1.5.2 Protection of System Data

Unless otherwise stated in the award, the contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DoD Regulation 5400.7-R and DoD Manual 5200.01(v1-v4) to include latest changes, and applicable service/agency/ combatant command policies and procedures. The contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or user ID/password-based access controls. In either case, the certificates used by the Contractor for these protections shall be DoD or IC approved Public Key Infrastructure (PKI) certificates issued by a DoD or IC approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

5.1.5.3 System and Network Authorization Access Requests

For Contractor personnel who require access to DoD, DISA, or Air Force computing equipment or networks, the Contractor shall have the employee, prime or subcontracted, sign and submit a System Authorization Access Report (SAAR), DD Form 2875.

5.2 Training

Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the Government or charged to TOs by contractors.

5.3 Data Rights and Non-Commercial Computer Software

In order to implement the provisions at DFARS 252.227-7013(b) and (e) and DFARS 252.227-7014(b) and (e) and DFARS 252.227-7017, the Contractor shall disclose to the ordering Contracting Officer and ordering office in any proposal for n award, or after award if not previously disclosed in the proposal, any technical data or non-commercial computer software and computer software/source code documentation developed exclusively at government expense in performance of the award. This disclosure shall be made whether or not an express requirement for the disclosure is included or not included in the PWS or solicitation for the order. The disclosure shall indicate the rights asserted in the technical data and non-commercial computer software by the Contractor and rights that would be acquired by the government if the data or non-commercial software was required to be delivered under the award and its CDRL requirements and any cost/price associated with delivery. This disclosure requirement also applies to segregable routines of non-commercial software that may be developed exclusively at Government expense to integrate Commercial Software components or applications provided under a commercial software license or developed to enable Commercial Software to meet requirements of this Award. Performance of this disclosure requirement shall be considered a material performance requirement of any award under which such technical data or non-commercial computer software is developed exclusively at Government expense.

5.4 Software Support and Data Rights

Unless specified otherwise in the Award, the contractor shall fully support all unique software developed to support integrated solutions on this contract. The contractor shall be able to support all software revisions deployed or resident on the system, and sub-systems. The data rights ownership/licensing guidance is specified in Section I, Clause 252.227-7013 and 252.227-7015.

5.5 COTS Manuals and Supplemental Data

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

5.6 Enterprise Software Initiative: Not Applicable

5.7 Software License Management

If developing and/or sustaining a system that requires and/or contains COTS, the contractor shall provide maintenance and support of that software license to manage its relationship to the overall system life-cycle in accordance with AFI 33-114, Software Management, which would include applications, license agreements, and software upgrades. The contractor shall provide asset inventory and services that track the financial aspects of an asset to include cost and depreciation, contract management, leases, maintenance agreements and service contracts. The contractor shall provide support summary information to include the general terms and conditions, benefits, strategic and tactical directions, license ordering information, internal billing process, pricing and deployment and support of the products included in the agreement. The contractor shall support common practices for ordering assets, tracking orders and assets, and tagging the assets. The contractor shall support application installation, operations, customer support, training, maintenance, sustainment and configuration control, to include the procurement of supporting software licenses.

5.8 Transition and Decommissioning Plans

The contractor shall create transition and decommissioning plans that accommodate all of the non-authoritative data sources (non-ADS) interfaces and ensure that necessary capabilities are delivered using approved ADSs.

5.9 Section 508 of the Rehabilitation Act

The Contractor shall meet the requirements of the Access Board’s regulations at 36 CFR Part 1194, particularly 1194.22, which implements Section 508 of the Rehabilitation Act of 1973, as amended. Section 508 (as amended) of the Rehabilitation Act of 1973 (20 U.S.C. 794d) established comprehensive requirements to ensure: (1) Federal employees with disabilities are able to use information technology to do their jobs, and (2) members of the public with disabilities who are seeking information from Federal sources will be able to use information technology to access the information on an equal footing with people who do not have disabilities.

6. DATA DELIVERABLES

The Government requires all deliverables that include Scientific and Technical Information (STINFO), as determined by the Government, be properly marked IAW DoD Directive 5230.24 and AFI 61-204 prior to initial coordination or final delivery. Failure to mark deliverables as instructed by the Government will result in non-compliance and non-acceptance of the deliverable. The contractor shall include the proper markings on any deliverable deemed STINFO regardless of media type, stage of completeness, or method of distribution. Therefore, even draft documents containing STINFO and STINFO sent via e-mail require correct markings. Additionally, as required by the award, the contractor shall formally deliver as a CDRL all intellectual property, software, licensing, physical records, files, documents, working papers, and other data for which the Government shall treat as deliverable.

7. ATTACHMENTS

1 MOB & GSU Comm-Facilities Listing

2. AFTO 00-33A-1001, Technical Manual, Methods and Procedures, General Communications Activities Management Procedures and Practice Requirements dated Oct 11

3. USAF Geobase Policy Memo dated Oct 02

4. GeoBase Executive Package ATO ID1824

5. Quality Assurance Surveillance Plan image2.emf

TO 00-33A-1001.pdf

TO 00-33A-1001

TECHNICAL MANUAL

METHODS AND PROCEDURES

GENERAL COMMUNICATIONS ACTIVITIES

MANAGEMENT PROCEDURES AND PRACTICE

REQUIREMENTS

THIS PUBLICATION SUPERSEDES TO 00-33A-1001 DATED 1 October 2011.

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD contractors only for administrative or operational use, 23 April 2009. Refer other requests for this document to AFNIC/ESPP Policy Branch. Submit recommended changes to Air Force Network Integration Center (AFNIC/ESPP), 203 West Losey Street, Room 1200, Scott AFB IL 62225-5222, or afnic.espp@us.af.mil, through appropriate channels, using Air Force Technical Order (AFTO) Form 22, Technical Manual (TM) Change Recommendation and Reply, according to TO 00-5-1.

Published under authority of the Secretary of the Air Force

9 JANUARY 2012

T.O. 00-33A-1001

INSERT LATEST CHANGED PAGES. DESTROY SUPERSEDED PAGES.

A USAF

NOTE: The portion of the text affected by the changes is indicated by a vertical line in the outer margins of the page. Changes to illustrations are indicated by shaded or screened areas, or by miniature pointing hands.

Dates of issue for original and changed pages are:

Original.................... 0 ............9 January 2012

TOTAL NUMBER OF PAGES IN THIS MANUAL IS 188, CONSISTING OF THE FOLLOWING:

Page *Change Page *Change Page *Change

No. No. No. No. No. No.

Title

A i - xxiii xxiv Blank

1-1 - 1-3

2-1 - 2-17

3-1 - 3-15

4-1 - 4-4

5-1 - 5-9

6-1 - 6-2

7-1 - 7-10

8-1 - 8-8

9-1 - 9-4

10-1 - 10-7

11-1 - 11-3

12-1 - 12-3

13-1 - 13-3

14-1 - 14-5

15-1 - 15-2

16-1 - 16-2

17-1 - 17-8

18-1 - 18-2

A-1 - A-5

B-1

C-1 – C2

D-1 - D-2

E-1 - E-4

F-1 - F-25

Index 1 – Index 4

*Zero in this column indicates an original page

LIST OF EFFECTIVE PAGES

i

Table of Contents INTRODUCTION ..................................................................................................................................................................xv

1. PURPOSE. ..................................................................................................................................................................xv

2. USE OF THIS MANUAL. ..............................................................................................................................................xv

3. DEFINITIONS. .............................................................................................................................................................xv

4. NOTES........................................................................................................................................................................xv

5. ABBREVIATIONS. .......................................................................................................................................................xv

6. LIST OF RELATED PUBLICATIONS.............................................................................................................................. xxi

7. LIST OF APPLICABLE TIME COMPLIANCE TECHNICAL ORDERS (TCTO). ................................................................. xxiii

8. IMPROVEMENT REPORTS. ..................................................................................................................................... xxiii

CHAPTER 1

OVERVIEW

1.1 PURPOSE

1.2 SCOPE

1.3 DEFINITIONS

1.3.1 Qualified Personnel

1.3.2 Communications Equipment/System

1.3.3 Test Equipment

1.4 RESPONSIBILITIES

1.4.1 Applicability for Deployable Units

1.4.2 Training Tracking and Documentation

1.5 CONTRACT MAINTENANCE

1.5.1 Contract Surveillance Programs/Quality Assurance Evaluators (QAE)

1.5.2 Contract Rules and Assistance

1.5.3 PWS Requirements for Maintenance Management

1.5.4 Impact on Wartime Capabilities

CHAPTER 2

QUALITY ASSURANCE PROGRAM

2.1 INTRODUCTION

2.1.1 Applicability and Authority

2.1.2 Purpose

2.1.3 Scope of Program

2.2 KEY TERMS

2.2.1 Voice/Video/Data Transport

2.2.2 Transmission Systems

2.2.3 Air Traffic Control and Landing Systems (ATCALS)

2.2.4 Radar Systems

2.2.5 Personal Devices

2.2.6 Internal Assessments

2.2.7 External Assessments

2.2.8 In Compliance (C)

2.2.9 In Compliance With Comments (CWC)

2.2.10 Not in Compliance (NIC)

2.2.11 Core Equipment/Systems

2.2.12 Other/Ancillary Equipment/Systems

2.2.13 Trend Analysis

2.2.14 Deficiency

2.2.15 Corrected During Evaluation (CDE)

ii

2.2.16 Deficiency Code

2.2.17 Unit Type Code (UTC)-Based Organization

2.3 PERSONNEL SELECTION AND TRAINING REQUIREMENTS

2.3.1 QA Personnel

2.3.2 Quality Assurance Representative (QAR)

2.3.3 Training Requirements

2.4 OTHER DUTIES AND RESPONSIBILITIES OF QA WORK CENTER

2.4.1 Technical Order Distribution Offices (TODO)

2.4.2 Corrosion Control Lead

2.4.3 Electrostatic Discharge (ESD) Monitor

2.4.4 Statement of Work (SOW) Reviewer

2.4.5 Operational Change Management Focal Point

2.4.6 Local Workcard (LWC) Validator

2.5 QUALITY ASSURANCE EVALUATION REQUIREMENTS

2.5.1 Self Inspection (SI) Evaluations (DELETED)

2.5.2 Managerial Evaluations (ME)

2.5.3 Personnel Evaluations (PE)

2.5.4 Equipment Evaluations (EE)

2.5.5 Managerial Schedule

CHAPTER 3

CONTROL OF PRODUCTION

3.1 INTRODUCTION

3.2 KEY TERMS

3.2.1 AF-Approved Automated Information System

3.2.2 Record Copy

3.2.3 Standard Reporting Designator (SRD)

3.2.4 Trouble Tickets

3.2.5 Jobs

3.2.6 Control Number (CN)

3.2.7 Owning Work Center (OWC)

3.2.8 Production Work Center (PWC)

3.2.9 Situational Report (SITREP)

3.2.10 Time Compliance Network Order (TCNO)

3.2.11 Restoral Priorities

3.2.12 Fully Mission Capable (FMC)

3.2.13 Partial Mission Capable (PMC)

3.2.14 Not Mission Capable (NMC)

3.2.15 Equipment Status Report (ESR)

3.2.16 Service Catalog

3.2.17 Operational Report (OPREP)

3.2.18 Maintenance Tasking Order (MTO)

3.2.19 Field Change Order (FCO)

3.2.20 Notice to Airman (NOTAM)

3.3 KEY CONCEPTS

3.3.1 Customer Service

3.3.2 Use of CNs

3.3.3 Routing SITREPs

3.3.4 Processing TCNOs

iii

3.3.5 Processing TCTOs

3.3.6 Utilizing Restoral Priorities

3.4 COMMUNICATIONS FOCAL POINT (CFP) FUNCTION

3.4.1 CFP Overview

3.4.2 Command and Control - Internal vs. External

3.4.3 Interaction With ESD

3.5 CFP PERSONNEL SELECTION AND TRAINING

3.5.1 Requirements

3.6 CFP FUNCTION RESPONSIBILITIES AND DUTIES

3.6.1 Responsibilities and Duties

3.7 CFP PROCESSES AND PROCEDURES

3.7.1 CFP Interaction With Production Work Center

3.7.2 Shift Continuity

3.7.3 Data Review and Trend Analysis

3.7.4 Depot Maintenance Processes

3.7.5 Equipment Inventory List (EIL)

3.7.6 Master PMI Schedule

3.7.7 Time Change Item Management

3.7.8 AIS Focal Point

3.7.9 Status Updates

3.8 PRODUCTION WORK CENTERS RESPONSIBILITIES/FUNCTIONS

3.8.1 Work Center Responsibilities/Functions

CHAPTER 4

AIR TRAFFIC CONTROL AND LANDING SYSTEMS (ATCALS)

REQUIREMENTS

4.1 INTRODUCTION

4.1.1 General

4.2 CFP RESPONSIBILITIES AND DUTIES RELATING TO SUPPORTING ATCALS/DATCALS

4.2.1 Outage Reporting

4.2.2 Data Reporting

4.2.3 CFP Functions and Duties

4.3 QUALITY ASSURANCE PROGRAM

4.3.1 ATSEP Evaluations

4.3.2 ATSEP Checklist Items

4.3.3 Post-upgrade Personnel Evaluations

4.4 ATCALS FACILITY REQUIREMENTS

4.5 ATCALS MAINTENANCE SPECIAL CONSIDERATIONS FOR REMOVING NAVAID IDENTIFICATION SIGNALS

CHAPTER 5

COMMUNICATIONS INSPECTION POLICY

5.1 INTRODUCTION

5.2 DESCRIPTION AND MAINTENANCE OF INSPECTION WORKCARDS

5.2.1 Inspection Requirements

5.2.2 AFTO Form 26D, Inspection Work Document

5.2.3 Changes

5.2.4 System Component/Subsystem Requirements

5.2.5 Additional Inspection Requirements

5.3 SCHEDULED MAINTENANCE INSPECTIONS

5.3.1 Scheduling

iv

5.3.2 Use of Modified Inspection Workcards

5.3.3 Changes to Inspection Requirements

5.3.4 Equipment Condition and Documentation

5.3.5 Use of Local Checklists/Workcards

5.3.6 Not Mission Capable (NMC) Status

5.3.7 Periodic Inspection (PI)

5.3.8 Servicing Inspection

5.3.9 Operator Inspection

5.3.10 Special Inspection

5.3.11 Scheduled Lubrication

5.4 PROGRAMMED DEPOT MAINTENANCE (PDM)

5.5 EQUIPMENT TRANSFER INSPECTION REQUIREMENTS

5.5.1 In-Process Inspections

5.5.2 Acceptance Inspections

5.5.3 Transfer Inspection

5.6 INSPECTING EQUIPMENT NOT IN USE (MOBILITY EQUIPMENT AND/OR EQUIPMENT IN STORAGE)

5.6.1 Additional Guidance for Depot-Procured Equipment Items

5.6.2 Additional Guidance for AF-Procured Equipment Items

5.6.3 Other Guidance

5.7 CONDITIONS FOR ACCEPTABLE INSPECTION DEVIATIONS

5.7.1 Conditions

5.7.2 Cancelling PMIs

5.7.3 Early/Late PMI Accomplishment

5.7.4 Limit on PMI Waivers

5.8 APPLICABILITY OF CONTRACTOR’S ACCEPTANCE MARKINGS AND DECALS

5.9 INSPECTION RESPONSIBILITY FOR WORK ACCOMPLISHED AT OPERATING LOCATIONS OR STATIONS BY DEPOT

OR CONTRACTOR TEAMS

5.9.1 Depot Field Team

5.9.2 Contractor Field Team

5.10 FUNCTIONAL CHECK INSPECTION

5.10.1 Unit Requirements

5.11 ANTENNA PREVENTIVE MAINTENANCE INSPECTION (PMI)/INSPECTION PROCEDURES

5.11.1 Antenna PMI Intervals

5.11.2 Depot Maintenance and Maintenance Assistance Requests

5.11.3 Inventory Listings

5.11.4 AIS

5.11.5 Antenna Identification

5.11.6 Leadership Notification

CHAPTER 6

CORROSION PREVENTION AND CONTROL PROGRAM (CPCP)

6.1 INTRODUCTION

6.2 PROGRAM RESPONSIBILITIES

6.2.1 Flight Commander/Chief

6.2.2 CPCP Manager’s Responsibilities

6.2.3 Production Work Centers

CHAPTER 7

HISTORICAL RECORD MANAGEMENT

7.1 INTRODUCTION

v

7.1.1 Overview

7.1.2 Master Inventories

7.1.3 Historical Records

7.2 KEY TERMS

7.2.1 Communications and Information Systems Installation Records (CSIR)

7.2.2 Administrative Records, Part 1

7.2.3 Drawing Records, Part 2

7.2.4 Maintenance Records, Part 3

7.2.5 Interim Installation Records (IIRs)

7.2.6 Existing Installation Records (EIR)

7.2.7 Standard Drawings (Non-CSIR)

7.3 REQUIRED FORMS

7.4 WORK CENTER RESPONSIBILITIES

7.4.1 Collect Data

7.4.2 Use AFTO Forms

7.4.3 Create Data

7.4.4 Maintain Permanent History and Historical Files

7.4.5 Maintain Current Drawings

7.4.6 Document Facility Grounding and Lightning Protection Checks

7.4.7 Transfer Documents With Equipment Transfers

7.4.8 Use and Maintain TCTO/TCNO/FCO Information

7.4.9 Make Entries on Communications Support and Historical Documents

7.4.10 Resolve Missing/Incomplete Historical Documents

7.4.11 Maintain Historical Documents on Equipment in Extended Storage

7.4.12 Record Dates in Proper Format

7.4.13 Use Electronic Signatures

7.4.14 Process Documents During Depot Maintenance

7.4.15 Follow AFTO Form 470-Series Procedures

7.4.16 Develop Master Inventories for COTS/GOTS Equipment

7.4.17 Ship Historical Documents

7.5 BASE CSIR MANAGER RESPONSIBILITIES

7.5.1 Duties

7.6 HISTORICAL RECORDS

7.6.1 Contents

CHAPTER 8

LIFE CYCLE MANAGEMENT

8.1 INTRODUCTION

8.1.1 Keys to Success

8.1.2 Critical Functions

8.1.3 Downward-Generated Enterprise-Level Acquisitions

8.1.4 Upward-Generated Acquisitions

8.1.5 References

8.2 ROLES AND RESPONSIBILITIES

8.2.1 AFMC-Supported Systems/Equipment

8.2.2 Non-AFMC-Supported Systems/Equipment

8.2.3 Standard Reporting Designator (SRD) Assignment

8.2.4 Degree of Usage

8.2.5 Major Command (MAJCOM) Responsibilities

vi

8.2.6 Base/Unit Responsibilities

8.2.7 Production Work Center Supervisor Responsibilities

8.2.8 Project Coordinator Responsibilities

8.2.9 Planning & Implementation (P&I) Responsibilities

8.3 LIFE CYCLE MANAGEMENT PLANS (LCMP)

8.3.1 Support Planning for Spares and Repairs

8.3.2 Minimum LCMP Sustainment Elements

8.4 MODIFICATION MANAGEMENT

8.4.1 AF Form 1067 Process

8.5 ENGINEERING AND INSTALLATION PROJECT DOCUMENTATION

8.6 JOINT TACTICAL RADIO SYSTEM (JTRS)

8.6.1 Waiver Requirement for Non-JTRS Radios

8.6.2 Waiver Process/Information

CHAPTER 9

MATERIAL MANAGEMENT

9.1 INTRODUCTION

9.1.1 Supply Discipline

9.2 LOGISTICS READINESS SQUADRON (LRS) LIAISON

9.2.1 LRS Liaison Responsibilities

9.3 WORK CENTER MATERIAL MANAGEMENT

9.3.1 Supervisor Responsibilities

CHAPTER 10

PUBLICATIONS PROGRAMS

10.1 INTRODUCTION

10.2 WORK CENTER/SECTION/UTC PUBLICATION MANAGEMENT

10.2.1 Supervisors Responsibilities

10.3 TECHNICAL MANUAL (TM) DISTRIBUTION AND CONTROL

10.3.1 TODO Responsibilities

10.3.2 TO Waiver Requests

10.4 LOCAL WORKCARDS (LWCS)

10.4.1 General Requirements

10.4.2 Commercial Off-The-Shelf (COTS) Items

10.4.3 AFMC-Supported Equipment/Systems

10.4.4 Non-AFMC-Supported Equipment/Systems

10.5 TIME CHANGE ITEM (TCI) MANAGEMENT

10.5.1 Overview

10.5.2 Considerations

10.5.3 Applicable Guidance

10.5.4 PMO-Managed Systems

10.5.5 General Management of TCIs

10.5.6 TCTO Processing

10.5.7 Preplanned and Time Change Procedures

10.6 AIR FORCE COMMUNICATIONS QUALITY CONTROL CHECKLISTS (AFCQCC)

10.6.1 Policy

10.6.2 AFCQCC Categories and Numbering

10.6.3 Air Force Network Integration Center (AFNIC) Responsibilities

10.6.4 AFCQCC OPR Responsibilities

10.6.5 Changes to AFCQCCs

vii

10.6.6 Proposed AFCQCCs

10.6.7 Local Communications Quality Control Checklists (LCQCC)

10.6.7.1 Use, Approval, and Processing

10.6.7.2 Local CQCC Requirements

10.6.8 Checklist Format

10.7 AIR FORCE COMMUNICATIONS SPECIAL INSTRUCTIONS (AFCSI)

10.7.1 General Information

10.7.2 HQ AFNIC Responsibilities

10.7.3 Format

10.7.4 New, Revised or Changed AFCSI

10.7.5 Numbering and Indexing

10.7.6 Obtaining AFCSIs

10.7.7 Implementation

10.7.8 Documentation

10.7.9 Rescission of AFCSI

CHAPTER 11

ANTENNA IDENTIFICATION

11.1 INTRODUCTION

11.1.1 Objective

11.1.2 Applicability

11.2 MATERIAL REQUIRED

11.2.1 11.2.2 11.2.3

11.3 PROCEDURES

11.3.1 Antenna Numbering

11.3.2 Open Wire Transmission Lines

11.3.3 Other Than Open Wire Transmission Lines

11.3.4 Special Instructions

ANTENNA DATA CHART

FREQUENCY TOLERANCE

CHAPTER 12

TOOL MANAGEMENT

12.1 INTRODUCTION

12.1.1 Objectives

12.1.2 Applicability and References

12.2 GENERAL REQUIREMENTS/INFORMATION

12.2.1 Tool Definition

12.2.2 Requirements

12.3 UNIT/WORK CENTER TOOL MANAGEMENT

12.3.1 Operating Instruction/Management Procedures

CHAPTER 13

PERFORMANCE METRICS AND ALGORITHMS FOR COMMUNICATIONS

13.1 INTRODUCTION

13.2 COMMUNICATION PERFORMANCE METRICS AND MEASURES

13.2.1 Maintenance Performance

13.2.2 Types of Metrics

CHAPTER 14

viii

CENTRALIZED REPAIR ACTIVITIES (CRA)

14.1 INTRODUCTION

14.2 BASIC CONCEPT OF CENTRALIZED REPAIR

14.2.1 Purpose

14.2.2 Source of Repair (SOR)

14.3 C-I CENTRALIZED REPAIR GUIDANCE

14.3.1 Procedures

14.4 REQUESTS TO ESTABLISH A CRA

14.4.1 Overview

14.4.2 Required Information

14.5 AUTHORITY TO ESTABLISH CRA

14.5.1 HQ USAF Direction

14.5.2 Acquisition Process

14.5.3 MAJCOM Approval

14.6 CRA ALIGNMENT

14.7 CRA OVERSIGHT AND MANAGEMENT

14.7.1 Owning MAJCOMs

14.7.2 Supported MAJCOMs

14.7.3 HQ AFMC System Program Office (SPO)/Program Manager (PM) and Lead Command LCMP Responsibilities.4

14.7.4 Parent Unit Operations Flight Commander/Chief

14.8 CENTRALIZED REPAIR ACTIVITY (CRA) RESPONSIBILITIES

14.8.1 Maintenance Production

14.8.2 Quality Assurance

14.9 REQUESTS FOR CRA ASSISTANCE

14.10 CRA AND SOURCE OF REPAIR (SOR) WORKLOAD REPORTING

CHAPTER 15

SYSTEM MANAGERS

15.1 INTRODUCTION

15.2 DUTIES AND RESPONSIBILITIES

15.2.1 MSM Duties and Responsibilities

CHAPTER 16

SPECIALIZED COMMUNICATIONS TEAMS (SCT)

16.1 INTRODUCTION

16.2 MISSION

16.3 USE OF SCTS

16.4 MANNING

16.5 RESPONSIBILITIES

16.5.1 MAJCOMs, AFNIC, AFFSA, and Direct Reporting Units (DRUs)

16.5.2 MAJCOM/AFNIC/AFFSA SCT Office of Primary Responsibility (OPRs)

16.6 RELATIONSHIP TO OTHER PROGRAMS

16.6.1 Air Force Engineering and Technical Services (ETS) Program

16.6.2 Operational Test and Evaluation (OT&E) and Defense Information System Agency (DISA) Technical Evaluation Program (TEP)

16.6.3 Acceptance of New Communications Facilities

16.6.4 Performance Evaluation Program (PEP) of Defense Information Infrastructure (DII)

16.6.5 Radar Evaluation Program

16.6.6 Defense Switched Network (DSN) Evaluation Program

CHAPTER 17

ix

HOW TO …

17.1 INTRODUCTION

17.2 PROCESSING TIME COMPLIANCE TECHNICAL ORDERS (TCTOS)

17.2.1 TCTO Processing Procedure

17.3 DOCUMENTATION OF NOT-REPAIRABLE THIS STATION (NRTS) TRANSACTION WITHIN IMDS

17.4 NRTS TRANSACTION REPORT FROM IMDS

17.5 REPAIR CODE CHANGE REQUESTS

17.5.1 General

17.5.2 Submitting SMR Code Change Requests

17.5.3 Considerations

17.6 COMPLETION OF AFTO FORM 95, SIGNIFICANT HISTORICAL DATA

17.6.1 Purpose

17.6.2 Minimum Documentation Requirements

17.7 MAINTAINING COMMUNICATIONS AND INFORMATION SYSTEMS INSTALLATION RECORDS (CSIR)

17.7.1 Filing Requirements

17.8 INSPECT CSIRS

17.8.1 Inspection Scheduling and Processes

17.8.2 Formula

17.9 SUBMITTING A WAIVER

CHAPTER 18

CLIMBING TRAINING REQUIREMENTS

18.1 INTRODUCTION

18.2 SCOPE

18.3 PERSONNEL PROFICIENCY

18.4 INITIAL CERTIFICATION PROCEDURES

18.4.1 Guidance for Training Course Graduates With Climbing Training

18.4.2 Climbing Authorizations

18.4.3

18.5 RECERTIFICATION PROCEDURES

18.5.1 Timelines and Requirements

18.5.2 Decertification and Recertification

18.6 CERTIFICATION RESOURCES

18.7 TRAINING DOCUMENTATION

18.8 CLIMBING CERTIFIER REQUIREMENTS

18.9 REFERENCES

APPENDIX A

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

A.1 REFERENCES

A.2 FORMS

A.3 ABBREVIATIONS AND ACRONYMS

A.4 TERMS

APPENDIX B

TOPICS REFERENCES

B.1 LIST OF SUBJECT AREAS AND REFERENCES

APPENDIX C

SAMPLING PLAN

C.1 COMMON TERMS

C.1.1 Population x

C.1.2 Like Items C.1.3 Sample Size

C.2 USING A SAMPLING PLAN FOR EQUIPMENT EVALUATIONS

C.3 RANDOM SAMPLING

C.4 USE OF A RANDOM NUMBER TABLE

APPENDIX D

COMMUNICATIONS PLAN

D.1 OVERVIEW

D.2 MANDATORY ITEMS

D.3 OPTIONAL AREAS

D.4 COMMUNICATIONS PLAN - SAMPLE PLAN

APPENDIX E

ADDITIONAL TOOL MANAGEMENT INFORMATION

E.1 STORAGE AND TRACKING CONSIDERATIONS

E.1.1 Accountability and Shift Inventory E.1.2 Utility Tool Kits E.1.3 Tool Storage E.1.4 Unit Ty

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 .