Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

CIRCUIT COMPLETION by Mind Map: CIRCUIT COMPLETION
5.0 stars - 1 reviews range from 0 to 5

CIRCUIT COMPLETION

CLR

MAIN PAGE

PAGE SPECIFIC INFORMATION, IS SYNC INFORMATION IDENTIFIED ON MAIN PAGE, IS THE LATEST TSO NUMBER IDENTIFIED ON THE MAIN PAGE, IS THE BIT RATE IDENTIFIED ON THE MAIN PAGE, IS A DETAILED SOURCE OF TIMING IDENTIFIED ON THE MAIN PAGE OR REFERENCE TO TIMING LAYOUT; I.E. EQUIPMENT TYPE, SIGNAL TYPE, STRATUM REFERENCE, PHYSICAL CONNECTIONS, IS THE CCO IDENTIFIED ON THE MAIN PAGE WITH VALID CONTACT INFORMATION OR REFERENCE, IS THE FULL CCSD LISTED ON THE MAIN PAGE, IS THE LATEST TSP NUMBER ON THE MAIN PAGE, IS SYNC INFORMATION IDENTIFIED ON MAIN PAGE

RESPONSIBILITY SPECIFIC INFORMATION, IF NOT SERVICING TCF OVER CIRCUIT OR TRUNK AND IT MAKES A PHYSICAL APPERANCE IN FACILITY ARE ALL APPLICABLE AND NECESSARY ITEMS OF SERVICE DEPICTED ON MAIN PAGE, IF NOT SERVICING TCF OVER CIRCUIT OR TRUNK AND IT MAKES NO PHYSICAL APPERANCE IN FACILITY ARE ALL APPLICABLE AND NECESSARY ITEMS OF SERVICE DEPICTED ON MAIN PAGE, IF SERVICING TCF OVER CIRCUIT OR TRUNK AND IT MAKES NO PHYSICAL APPERANCE IN FACILITY ARE ALL APPLICABLE AND NECESSARY ITEMS OF SERVICE DEPICTED ON MAIN PAGE, IF SERVICING TCF OVER CIRCUIT OR TRUNK AND IT MAKES A PHYSICAL APPERANCE IN FACILITY ARE ALL IN-HOUSE ITEMS DEPICTED ON MAIN PAGE AS WELL AS ALL EXTERNAL APPLICABLE AND NECESSARY ITEMS

LOCATION SPECIFIC INFORMATION, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITHIN A ROOM NUMBER OR NAME, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITHIN A COUNTRY IF NECCESSARY OR APPLICABLE, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITH SHELF NUMBER OR IF MULTIPLE OF LIKE EQUIPMENT WHICH NUMBER IN SERIES, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITHIN A SITE, IF CIRCUIT IS WITHIN FACILITY ARE ALL APPLICABLE ITEMS DEPICTIED IN DIAGRAM, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITH RACK NUMBER, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITHIN A BUILDING NUMBER OR NAME

EQUIPMENT SPECIFIC INFORMATION, IS EACH APPLICABLE EQUIPMENT ITEM'S OUTPUT/INPUT PORT DEPICTED IN THE MAIN PAGE, IS EACH APPLICABLE EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITH EQUIPMENT TYPE; MANUFACTURER, MODEL, ETC, IS EACH EQUIPMENT ITEM LABELED IN THE MAIN PAGE WITH EQUIPMENT NOMENCLAUTRE; DISA ID, LOCAL ID, ETC.

CONNECTION SPECIFIC INFORMATION, IS EACH ELECTRICAL INTERFACE IDENTIFIED WITH APPLICABLE STANDARD; IF NON-STANDARD IS IT IDENTIFIED WITH A REFERENCE, IS EACH PHYSICAL MEDUIM IDENTIFED IN ACCORDANCE WITH THE CURRENT COLOR LABELING REFERENCE, IS EACH PHYSICAL INTERFACE IDENTIFIED WITH APPLICABLE STANDARD, PINOUT, OR ROUTING; IF NON-STANDARD IS IT IDENTIFIED WITH A REFERENCE

FORMATING SPECIFIC INFORMATION, ARE ALL APPLICABLE FACILITES/ROOMS/SITES IDENTIFIED BY A CLEAR FORM OF SEPERATION, ARE ALL DEMARKS IDENTIFIED IN MAIN CLR BY CURRENT VERSION'S FORMATTING TECHNIQUE, IF A CLOUD OR OTHER GENERAL ROUTING FORMAT IS USED TO DEPICT IN HOUSE ROUTING IS IT REFERENCED TO A DETAILED DIAGRAM, ARE ALL APPLICABLE TRANSMISSION LINES LABLED WITH SIGNAL DIRECTIONS, IS THE CURRENT VERSION TEMPLATE BEING USED

Policy Requirement Documentation

CLRs for digital circuits must include timing and sync information (e.g., synchronous, asynchronous or isochronous), data rate, electrical and mechanical interface type (i.e., RS-232, RS-449, MIL-STD-188-114A, etc.), signal type (i.e., NRZ, Bipolar/AMI, B8ZS, etc.), protocol (i.e., Bisync, HDLC, SDLC, etc.), and source of timing.

CLRs for analog circuits must include audio signal levels, type signaling, and signaling frequency for each transmission level point (TLP).

In-facility circuit layout records (CLRs) must be completed for all trunks and circuits that have a physical patch panel appearance in the TCF/PTF, and for all trunks and circuits for which the TCF/PTF is the servicing TCF/PTF. The CLR must depict "infacility" equipment and cross-connect information. The reverse side of DD Form 1441 may be used to satisfy this requirement. Other methods, including automated, may also be used. TCF/PTFs with numerous circuits of the same configuration (e.g., DSN IST's) may use one CLR that depicts the common configuration as long as specific cross-connect, conditioning equipment, and other pertinent information is maintained for each individual circuit.

FACIT

Front Page

Is the correct category identified

Is the current rate identified

If HIT/SI is it identified

Is the current Purpose/Use identified

Is the current TSP identified

Is the correct circuit identifier declared

Is the mission impact identified in the mission statement section

Is the current service availability identified

Other Tabs

Affected Circuits, If circuit has lower level circuits are they identified in this section

Affected By Circuits, Is circuit rides higher level trunk is it identified

Equipment

Circuit Actions, Is the current TSO# identified, Is the status of the action current

Interested Parties, Are any applicable interested parties identified

QC, No longer used. CAD replaces

Path, Is the current CCO identified

Diagrams, Is there a updated diagram in accordance with CLR checklist and attached as a link

Reportable, If circuit is designated to be reported to a facility/organization are they identified, MOC, CFP

Alternate Designator, If circuit is identified by other name by any other organization is it entered into fields, TRUNK ID, ALLA, MDA circuit number, Mission Id, Phone number

PHYSICAL

Has all equipment been properly labeled?

Equipment, Promina Cards, Circuit Identification, Font Size, 18, Label Size, Layout, Top facing right, Node Identification, Label Size, Font Size, Software, Broadmore, Ports, PVC Table, CCSD ONLY, CTC, OPTICAL, INTER NODAL TRUNK #, ALL EQUIPMENT CHASSIS, POC NAME, POC ORGANIZATION, POC PHONE NUMBER, POC EMAIL ADDRESS

Patch Panel, Types, Circuit Identification, Font Size, 18, Label Size, Policy Requirement Documentation, Labels all patch bays, test boards, or other circuit access points normally used by technical control personnel. As a minimum, labeling must include the last four characters of the circuit Command Communications Service Designator (CCSD) and the NCS TSP restoration priority. If a NCS TSP is not assigned, then the letters "NA" (none assigned) must be entered with the CCSD to indicate that the circuit has no assigned restoration priority.

Cable, Font Size, 6, Label Size, Required Information, CCSD, From Location, Rack, Shelf, From Equipment, Model, Nomenclature, From Equipment Specifics, Shelf, Slot, Port

Rack, Rack Identification, Rack Identification Number in Series, Layout, Center Top, Format, LABEL SIZE, FONT SIZE, LABEL COLOR

NOTES, Labeling Devices, Brother PT-2400/2410, TZ-251, 1 inch /24 mm, Dymo, ID Expert, Colors Thoughts, BACKGROUND COLOR, TEXT, RED LETTERS, TSP, ENCRYPTED, BLACK LETTERS

Has all equipment been properly installed?

Cable, DONT, Lay cable across racks, Use longer cable than required, thereby making it neccessary to wrap cable in trough, Use zipties, DO, Tie cable to one side of rack, Use exacting measurements from and to equipment, Use pre-existing main cable One Trunk out of rack

Equipment, DO, Ground Properly, Leave space between adjoining equipment, Allow for air circulation, Label with POC contact information, DONT

MISCELLANEOUS

If applicable has the CLR been sent to all persons?

If applicable have the CSIRS records been updated?

Description, The CSIR is a collection of records associated with the installation of a communications and information system in a facility, building or location. The CSIR is comprised of three parts; (1) an administrative record, (2) drawing record, and (3) maintenance record. These records provide both a historical record of communications system and equipment installation and a living document that reflects how the system/equipment is modified over time. It is used for planning, programming, and supporting communications systems/equipment operations, maintenance, integration, and Engineering and Installation (EI) efforts. The record documents the locations and physical configuration of communications systems/ equipment in a facility, building or location.

Policy Requirement Documentation, AFI 33-101, Develop and maintain CSIR drawing records in the CIPS Visualization Component (CVC) or installation supported systems or facilities, MPTO 00-33A-1001, They are required for all AF-owned fixed communications and information systems regardless of who maintains or operates the systems.

Unsure, Was any equipment removed or installed?, Yes, Update the associated Bldg/Room/Rack CSIR record, No, Dont worry about it

If applicable has the network diagram been updated?

Optical Cloud

Node Site Coordinator

If applicable have historical records been updates?

Unsure, Was any equipment or equipment items that would be inventoried in IMDS installed?, Yes, Update the historical record for the equipment, No, Dont worry about it, Unsure, Policy Requirement Documentation, Units will develop master inventories based on shipping, acceptance, catalog, and other applicable documents for AF, MAJCOM or locally procured Commercial-Off-The-Shelf (COTS)/Government-Off-The-Shelf (GOTS) equipment., Policy Requirement Documentation, All equipment/systems tracked in IMDS must utilize the IMDS history files and record all significant maintenance actions, especially Time Change Items (TCIs), Time Compliance Technical Orders (TCTOs), Time Compliance Network Orders (TCNOs), etc.

Description, Work center facility, systems installation, and equipment records are historical documentation that constitute a permanent record of significant maintenance actions or significant changes to the facility or system. Historical records must remain with each equipment or system throughout its life cycle. They are designed to provide technicians and item managers with an accurate portrayal of significant actions, modifications, issues, and overhauls.

Policy Requirement Documentation, Historical records, AFTO Form 95, Significant Historical Data, Integrated Maintenance Data System (IMDS) history files or other records, are required on all Mission Capable (MICAP) reportable equipment, command supported equipment, and other equipment as designated by the Item Manager/System Manager/Program Manager (IM/SM/PM).

Has the circuit configuration been properly documented?

Has the user letter been sent to all applicable persons and is there proof of it properly stored on the shared drive?

Policy Requirement Documentation, Sends DII user notification letters to each user upon activation of a new circuit, and annually thereafter. An updated letter should also be sent any time information contained in the letter affects the users ability to contact appropriate personnel (i.e., phone number, point of contact, etc.).

CIRCUIT HISTORY FOLDER

Policy Requirement Documentation

Each history file must contain a copy of:, In-effect, exception, and delayed service reports applicable to the latest TSO., Status Acquisition Message (SAM)., Copies of quality control waiver requests and approvals., The initial test and acceptance data (DD Form 1697 or 1697-1), Copies of the latest TSO that reflects the current end-to-end configuration, control office assignment, etc., Copies of any appropriate documentation (i.e., QC results, letters, etc.) resulting from action(s) taken to resolve degradations when a trunk or circuit fails management threshold for two consecutive months or more. Documentation must be kept on file for 1 year.

Automation, The ADP system must provide for adequate backup capability so that computer failure will not prevent the maintenance of required records or the retrieval of information, If ADP systems are used to maintain TCF/PTF records, all personnel must also be trained to use the paper forms required by this chapter. A 90-day supply of paper forms must be maintained and accessible to personnel on duty. Contingency procedures must be developed to include instructions on how and when to revert to manual recordkeeping., The ADP system must be redundant with a second computer immediately available to replace a failed unit, The backup process should be an automated procedure, or should at least prompt the operator to perform the required actions

Each TCF/PTF must establish and maintain permanent history files for, all trunks and circuits for which the TCF/PTF is the CCO/CMO or servicing TCF/PTF, all trunks and circuits that have physical patching capabilities within the TCF/PTF, all links that terminate at their facility

Circuit history files are not required for through facility trunks and circuits that do not have physical patch appearances, unless the TCF/PTF is the CCO/CMO or servicing TCF/PTF.

If applicable have copies of any appropriate documentation (i.e., QC results, letters, etc.) resulting from action(s) taken to resolve degradations when a trunk or circuit fails management threshold for two consecutive months or more. Documentation must be kept on file for 1 year.

Have copies of quality control waiver requests and approvals been properly stored?

Have the latest TSO and applicable related messages been properly stored?

If applicable has the SAM been properly stored?

Has the Test And Acceptance Document been properly completed and stored?