Osan_Air_Base_CVC_Infrastructure_Assessment_PWS__16_July_18.docx
DOCX document 384 KB Posted
- Attached to
- CVC Communication Infrastructure Survey
- Solicitation number
- W91QVN-18-R-0190
About this file
DRAFT PWS- Subject to Change
View the file
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
Survey of Communications Infrastructure
And
Updating Data in the CVC
Osan AB, Republic Of Korea
Performance Work Statement (PWS)
1.0 DESCRIPTION OF SERVICES.
1.1 Scope of Work. The Contractor shall provide all personnel, labor, tools, equipment, materials, supervision, transportation, and necessary facilities for this scope of work, except those listed in section 3.0 Government Furnished Property, Equipment, Services (GFP/GFE/GFS) and Standards. The Contractor shall survey, collect, and document approximately 770 communication containers, manholes, hand-holes, pedestals, and vaults in the CVC database. Account for each copper, fiber, splice point, manhole, hand hole, pedestal and vault at Osan AB, Republic Of Korea. The Contractor shall provide professional services necessary to update the Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC) with Outside Plant telecommunications infrastructure information for Osan AB. The Contractor shall accomplish this work by collecting and recording the location of outside plant features using Global Positioning System (GPS) surveys; by entering and inspecting manholes (MH), hand-holes (HH), pedestals, and vaults; and by entering enclosure attributes and cable data into the CVC. The Contractor shall demonstrate that updated information entered into the CVC is accurate and complete by conducting progress demonstrations that include producing CVC-generated reports and drawings.
1.2 Requirements. Currently there is no accurate documentation of Osan, AB Outside Plant that includes building entrance terminals, cable tracing, tag cables, butterfly drawings, splice cases, communication pathway to include ducts, inner-ducts, connecting from one manhole to the next. This survey will provide GPS coordinates location of each manholes, cables, ducts, and inner-ducts. This project will all provide survey data (manholes, cables, ducts, inner-ducts, splices, location, GPS coordinates) into the web-based CVC tool.
1.2.1 Conversion of Contractor Collected Data to CVC.
1.2.1.1 Access to the CVC. The Contractor shall use the CVC available through the Air Force Portal at the CIPS website, to enter outside plant infrastructure information gathered from the Contractor’s GPS Surveys and Field Inspections. The Contractor or the sub-contractor must have a US Secret Security Clearance to receive a Government Common Access Card (CAC) prior to start of work. The Contractor will be provided Government-provided computer connected to the NIPRNet and access to CIPS with CVC editor privileges by submitting the necessary network account documentation upon receipt of CAC. It is preferable that the contractor already have CVC knowledge and experience to enter data into the CVC.
1.2.1.2 Discrepancies/Missing Data Issues. The Contractor’s Daily Status Report (A002) shall include a running list of discrepancies and missing data issues either discovered by the Contractor or reported by the Government throughout the life of the project (see para 4.1.2 of this PWS.) All issues shall be either resolved by the Contractor and entered into CVC, or accepted by the Government for Government action.
1.2.1.3 Preliminary Processing of Data. The Contractor may use their choice of intermediate methods to gather and to preliminarily edit, process and record information prior to transferring the data to the CVC Viewer/Editor web-browser application, accessible at https://cipsaf.tinker.af.mil/cips/mycips.aspx (CIPS account required for access).
1.2.1.4 CVC Editing Standards. CVC Editor, Workspaces and drawings shall have annotation, line editing and graphic representation and layout comparable to the manhole and cable record drawings maintained in Micro-station format by 51 CS, and shall comply with Geographic Information System and Cartographic industries professional standards. Containers shall be properly sized, shaped, geospatially oriented, and placed. In addition, manholes shall be fully populated with appropriate cables and splices; show accurate duct bank placement/layout and equipment/junction device information; show properly aligned and spaced cables.
1.2.2 GPS Survey. The Contractor shall use GPS technology to locate and collect data on outside plant infrastructure features and communications pathways in accordance with the Geological Survey Circular 895-A. Outside plant features include manholes, hand holes, pedestals, and vaults. The Contractor shall ensure collected data is compatible with the CVC database, make the data available through the AF Portal at the CIPS website, convert the GPS data to an Environmental Systems Research Institute (ESRI) Shape file, and transcribe the Shape file information into the CVC database. The Contractor is required to GPS Survey all communication manholes and commercial comm. Paths on Osan AB.
1.2.2.1 GPS Accuracy Standards. The Contractor shall use GPS to determine the horizontal position of communications outside plant infrastructure and communications pathways features in accordance with the Federal Geographic Data Committee (FGDC)-STD-007.4-2002. FGDC publications are downloadable from the website: http://www.fgdc.gov/.
1.2.2.2 GPS Accuracy of Feature Locations. Each outside plant infrastructure feature and communications pathway requiring geospatial coordinates shall be located within one (1) meter of its true ground position in the horizontal plane. Spatial accuracy confidence level as defined in FGDC-STD-007.3-1998. Geospatial coordinates for the location of manholes and cable vaults shall be recorded at the center of the manhole lid. Geospatial coordinates for the location of manholes, hand holes, pedestals, and vaults. Geospatial coordinate data for the location of communication pathway lines shall be recorded at a minimum every 50 feet and each turn or bend in a cable installation pathway must also be recorded so that the coordinates for any point along the turn pathway shall fall within the allowable accuracy.
1.2.2.3 Shape Files. The GPS collected outside plant infrastructure features and communications pathways attribute, metadata, and location information shall be converted to, stored, and submitted in an ESRI Shape File format. The shape files must be compatible with the current CVC web-based application. The shape files shall have a geospatial reference (.prj) file included that specifies the parameters of the coordinate system. The Contractor shall provide the Shape files as part of the Survey Data Report (A003).
1.2.2.4 GPS Data Format. The Contractor shall use GPS to determine horizontal position of communication features and shall format outside plant infrastructure features and communications pathways data for entry into CVC using the entity naming convention attribute fields and domain values as specified in Appendix C.
1.2.2.5 Data Dictionary. The Contractor shall collect geospatial coordinates and attribute information on the outside plant infrastructure features and communications pathways with GPS data loggers and shall use Appendix C to create the data dictionary for use in the logger.
1.2.2.6 Metadata. For each set of outside plant infrastructure features and communications pathways data using GPS, the Contractor shall complete all metadata elements marked mandatory or mandatory if applicable as defined by the FGDC–STD-001-1998. Metadata shall be formatted and stored as an XML document that is compatible with the submitted shape files Metadata shall be provided as part of the Survey Data Report (A003).
1.2.2.7 Accuracy Worksheets. The Contractor shall submit calculation excel worksheets (A004) showing compliance with the National Standard for Spatial Data Accuracy (NSSDA) statement at the 95% confidence level, as required by FGDC-STD-007.3-1998. Examples of the Horizontal Accuracy Statistical Worksheet are given in the FGDC, Appendix 3-B (informative) Horizontal Accuracy Computations, Tables 1 and 2. The standard can be downloaded from the FGDC website: http://www.fgdc.gov/.
1.2.2.8 Geospatial data. Geospatial data shall overlay on the installation’s current GeoBase Common Installation Picture (CIP) provided in the Air Force Porta1 accessible CVC. The collected data shall incorporate the datum and the coordinate and projection system of the Osan CIP.
1.2.2.9 Quality Control. The Contractor shall use a topology build and clean routine, and shall use professional standards to ensure the outside plant infrastructure features and communications pathways data are identified and correctly documented in CVC. The contractor shall provide a quality control plan within 30 days of contract award.
1.2.2.9.1 Shape Files. Submitted Shape files have:
a. no erroneous overshoots, undershoots, dangles or intersections in the line work;
b. features snapped where applicable (for example, GPS_Path_Segment snapped to GPS_Manhole);
c. continuous lines, with no pseudo-nodes (Nodes should only exist where the attributes of a line change);
d. no sliver polygons;
e. all polygons completely closed and have a single unique centroid;
f. digital representation of the common boundaries for all graphic features that is coincident, regardless of feature layer.
1.2.2.10 Updating GPS Data in CVC. The Contractor shall enter into CVC all field collected data, and shall precisely and accurately transfer into CVC geospatial coordinates of GPS shape files for the communications infrastructure. The Contractor shall store the collected outside plant infrastructure features and communications pathways shape files in the local Government-provided computer workstation, and shall use the editing “snapping ” features to transcribe information from the local workstation shape file into the CVC database using the CVC Viewer/Editor web-browser application, accessible at https://cipsaf.tinker.af.mil/cips/mycips.aspx or search for CIPS at the Air Force Portal.
1.2.3 Field Inspection and Documentation of Outside Plant Facilities.
The Contractor shall conduct a field inspection of communication infrastructure features in the outside plant, along the communication pathways, to and from the cable demarcation terminal in each facility for the purpose of updating the CVC with current, complete, and accurate information. Features to be physically inspected and documented include outside plant communication cable and the interior of communication containers such as Manholes, Hand holes, Vaults, and Pedestals. The Contractor shall inspect and document the attributes of communication pathways and cables including the size of manholes and hand holes, orientation of manholes, hand holes, pedestals, and vaults including cables, splices, terminal blocks, duct banks, MH/HH knockouts or holes, ducts, and inner duct that are accessible by removing covers or by opening lids or doors in buildings or in communication enclosures. Some manhole/hand hole lids may require special equipment for removal. The Contractor will submit a AF form 103 (work clearance request) through 51 CES when its required to pump out water and clear manholes/hand holes of mud and debris to perform field inspection (see also para 4.4.2). The Contractor shall note cable tags and record cable attributes including size, number, count, and type. The Contractor shall retag cable when tags are missing, inaccurate, or illegible. The Contractor shall coordinate with 51 CS/SCXP at least 72 hours in advance for access to these MH/HH.
1.2.3.1 Documentation of Field Inspections. 51 CS/SCXP shall provide the Contractor with electronic copies of all legacy drawings in Micro-station format, to be used for reference only. The Contractor shall prepare legible field drawings to record the features for each communications container including manholes, hand holes, pedestals and vaults. The Contractor shall use colored pencils to edit the field drawings, denoting which color is used for additions, deletions, remarks, notes to the CVC editor, and inspector reminder notes. The Contractor shall submit legible, colored paper and color electronic copies of each edited field drawing as part of the Communication Container Field Drawings (A006). The Contractor shall provide these datasheets as part of the Communication Container Field Drawings (A006).
1.2.3.2 Identification and Tagging of Cables during Field Inspection. The Contractor shall replace missing, inaccurate and illegible cable identification tags in all Contractor-surveyed communications containers. To ensure the accuracy and completeness of cable tags, the Contactor shall be required to return to a communications container or building to tag unknown or correct erroneously tagged cable. In containers with relatively few cables that are easily traced, cable shall be tagged within two feet of the cable entry and exit. In densely populated containers, cable shall also be tagged on each side of splices. Cable known to be AIP shall be tagged “AIP” with the cable size and type if tags are missing and shall be noted as AIP in the CVC. At Dial Central Office Vaults, the Contractor is required to tag cables on both sides of the TIP splice (one cable runs between the TIP splice and the vertical side of the main frame. The cable on the other side of the TIP splice is the feeder cable). No tagging or data collecting is required for cable at the Main Distribution Frame. Example B shows examples of cable tags that are acceptable for Osan AB. As an alternate labeling method, it is permissible to use Brothers P-Touch Extra-Strength Adhesive Laminate Tape to prepare labels. The tape shall be 1-inch wide white tape with black lettering. The lettering shall be minimum of 12 points, normal spacing. Tags for a single cable sheath with multiple cables shall be constructed so that labels are placed one under another until all cables within the single cable sheath are described on one tag. All tag backing for labels shall be as described in Example B. Labeling/tagging methods shall be consistent throughout.
1.2.3.3 Updating the CVC with Field Inspection Information. The Contractor shall use field inspection information to update the CVC database using the CVC Viewer/Editor web-browser application, accessible at https://cipsaf.tinker.af.mil/cips/mycips.aspx or search for CIPS at the Air Force Portal. The Contractor may delete or edit existing communication infrastructure data contained within CVC in order to accomplish the work. All communications infrastructure features placed and modified within CVC by the Contractor shall be properly and accurately attributed, positioned, sized, shaped, orientated and labeled. Contractor personnel shall be granted CVC Editor and CVC CSIR Editor roles. The CVC QC Editor role is reserved for the Contacting Officer’s Representative (COR) and other designated Government personnel.
1.2.4 Demonstration of CVC Update.
1.2.4.1 Progress Demonstrations. The Contractor shall conduct progress demonstrations at approximately 35% of project duration, approximately 65% of project duration, and at project completion (100%).
1.2.4.1.1 General. The Government reserves the right to duplicate any Contractor-performed demonstrations or to perform any CVC editing or printing actions to assure results conform to prescribed requirements for completeness, workmanship, and accuracy. The Contractor shall notify the Contracting Officer’s Representative (COR) at least five (5) working days prior to any demonstrations and shall make available all standards and criteria used to accomplish demonstrations. The Contractor shall allow at least three (3) working days for the 100% demonstration.
1.2.4.1.2 Demonstration at 100% completion. The Contractor shall conduct the 100% demonstration, with some additional requirements:
a. As part of the demonstration, the COR shall select up to 10% of features for demonstration of CVC accuracy, and the selected features may include cable counts. For each cable count selected, the Contractor shall show that the pairs/strands run continuously (without gaps) between the point of origin and the point of final termination.
b. As part of the demonstration, the COR shall select up to 10% of containers for demonstration of survey accuracy, and may request CVC-generated CSIR drawings for selected containers. The Contractor shall demonstrate that the CSIR drawings show containers properly sized, shaped, geospatially oriented, and placed. In addition, manholes shall be fully populated with appropriate cables and splices; show accurate duct bank placement/layout and equipment/junction device information; show properly aligned and spaced cables; and show all dead pairs or strands on cables.
c. The Contractor shall have paper copies of current CVC reports for No connection on Splice, Sheath Disconnect, and Sheath Overload at the demonstration for the COR to review.
d. The Contractor shall have corrected all errors shown in the most current CVC reports within 10 working days.
1.2.4.2 Demonstration Reports. The Contractor shall record all demonstrations as they are accomplished and include products generated during the demo (e.g. CVC-produced manhole and cable diagrams, cable reports and results) in the Demonstration Report (A005).
1.2.4.3 Warranty Criteria. The contractor is responsible for submitting corrected information/data found incorrect within 1-year post survey. Due to limited network account access, the corrected information/data must be submitted in the correct Shape file format to have imported into CIPS/CVC. Acceptable methods to provide data will be CD, DVD-R, or secure file sharing such as AMRDEC. The QA work center will conduct a 10% acceptance sampling of CVC inputs to ensure data is sufficiently inputted into CIPS/CVC.
1.3 Performance
1.3.1 Period of Performance. The period of performance for this contract shall be 18 months from date of award or notice to proceed.
1.3.2 Place of Performance. All work shall be performed on site at Osan AB, ROK.
1.3.3 Hours of Work. Contractor shall work during normal operating hours of 7:00 AM – 4:30 PM, Monday through Friday, excluding Federal holidays. The Contractor shall be allowed to work after hours and on weekends if the work being performed does not require an escort. When no other scheduling option is available due to mission impact, the Contractor shall be allowed to work after hours and weekends in areas that require an escort. In cases where after hours or weekend work is required by the Government and an escort is required, the Contractor shall notify 51 CS/SCXP five (5) days prior to the date that the work shall be accomplished.
2.0 CVC PERFORMANCE REQUIREMENTS SUMMARY (PRS). The PRS lists the PWS performance objectives the Government will monitor. The absence of any PWS requirements from the PRS shall not detract from its enforceability nor limit the rights or remedies of the government. The PRS sets forth the maximum allowable deviation from the standard of performance for that service.
| Performance Objective |
| Performance Standard |
| Acceptable Quality Threshold |
| Method of Surveillance |
| Remedy of Failure |
GPS Point Accuracy PWS Para 1.2.2.2
| Within one meter of their true ground position. Confidence level IAW FGDC-STD-007.3-1998 |
| No more than one (1) outside plant infrastructure features and communications pathways per Inspection |
| Random, Customer Complaints |
| Correct within five (5) days of Contractor notification of discrepancy. |
Geospatial Data Accuracy PWS Para 1.2.2.4, 1.2.2.5, 1.2.2.8 GPS format and data dictionary in compliance with Appendix C
| No more than two (2) instances where geospatial data does not conform to Appendix C. |
| Periodic, Customer Complaints |
| Discrepancies resolved within three (3) days of Contractor notification of discrepancy |
Cable Tag Accuracy PWS Para 1.2.3.2
| According to the guidelines set forth in Example B of this PWS. |
| No more than two (2) instances where Contractor fails to accurately and legibly tag cable in containers |
| Random, Customer Complaints |
| Discrepancies resolved within three (3) days of Contractor notification of discrepancy |
CVC Entry Completeness/Accuracy PWS Para 1.2.2 CVC entry in compliance with Geographic Information System and Cartographic industries professional standards IAW Geological Survey Circular 895-A
| No more than two (2) incidents where CVC entry is incorrect. |
| Random schedule, Customer Complaints |
| Discrepancies resolved within three (3) business days of Contractor notification of discrepancy |
Progress Demonstrations PWS Para 1.2.4.1
| The Contractor shall conduct progress demonstrations at approximately 35% of project duration, approximately 65% of project duration, and at project completion (100%). |
| No more than two (2) reschedules. |
| Percentage timeline outlined. |
| Correct within five (5) days of Contractor notification of discrepancy. |
3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, SERVICES (GFP/GFE/GFS) AND STANDARDS.
3.1 Government-Furnished Property (GFP).
3.1.1 Government Provided Office Workspace and Computer Workstation. The Government shall provide office workspace and a Government-configured computer, with a CAC reader, and access to the CVC over the NIPRNet for the duration of the contract period.
3.1.2 Government Provided Color Printer. The Government will provide access to a color printer, but the Contractor must supply the paper and toner/ink.
3.1.3 Government Provided Storage Space. The contractor shall request storage space upon award.
3.1.4 Manhole Lid Removal Equipment. In the event that a manhole lid is sealed or difficult to open the contractor shall submit a work order to the 51 CS/ SCOW work center for assistance.
3.2 Government Provided Escorts. The Contractor will require Government escorts in the nuclear and conventional weapons storage areas (WSAs), the flight line area, all flight facilities, and all major communication nodes (telephone central office, network control center, and local area network information transfer nodes). For access to the WSAs, the Contractor shall coordinate with 51 CS/SCX for escort arrangements at ten 10 days in advance. For access to all other listed areas, the Contractor shall coordinate with 51 CS/SCX at least five (5) duty days in advance. The government will unlock all communication rooms and cable/fiber patch panels & cabinets to provide access for Contractor.
4.0 GENERAL INFORMATION.
4.1 Administrative.
4.1.1 Schedule. The Contractor shall submit a completion timeline to the 51 CS/SCXP work center for approval.
4.1.2 Integrated Product Team (IPT). The Contractor shall chair weekly IPT meetings that include Contractor representatives, the Contracting Officer (KO), the CSI-B, the CSI-E, the 38 CEG Project Manager, the 51 CS/SCX Project Manager, COR, and other base personnel as required. The purpose of this meeting is to discuss project progress, problems being encountered, and other discussions necessary/beneficial to ensure success and timely completion of the contract requirements. The Contractor shall record and distribute meeting minutes NLT 2 days after conclusion of the meeting. (A001).
4.1.3 Daily Status Reports. The Contractor shall prepare a Daily Status Report during the course of performing the work (A002). The purpose of the report is to inform IPT members of project progress, problems being encountered, and other topics necessary/beneficial to ensure success and timely completion of the contract requirements. The Status Report and meeting minutes may be combined as long as the resulting report contains all the required elements and contains sufficient detail to serve as a project record. The DSR shall be available NLT 0900 KST the following day.
4.1.4 Outbrief. The Contractor shall conduct an out brief with the COR or designated representative and other site personnel 5 days prior to the period of performance end date. The out brief shall inform the COR of CVC update results and maintenance issues. At the conclusion of the out brief, the Contractor shall provide a written synopsis of the CVC Update which includes major issues or action items and a list of attendees (A007). Prior to the out brief, the Contractor shall return all Government equipment, door keys, and Government ID cards issued to Contractor personnel for the performance of this contract.
4.2 Contractor Personnel.
4.2.1 Project Manager. The Contractor shall provide a Project Manager (PM) responsible for contract performance and continuity. The Contractor shall identify the Project Manager’s or his/her alternate's range of authority to act for the Contractor relating to daily contract operation.
4.2.2 Site Point of Contact (POC). A designated Site POC or alternate(s) shall be on site during duty hours until project completion. The Site POC shall be the interface for all work site communications with the Government, including quality, safety, and discrepancy matters. The Project Manager and Site POC can be the same person.
4.2.3 General Personnel Requirements. The Project Manager, Site POC, and respective alternate(s) shall be able to read, write, speak, and understand English. The Site Visit Request Letter shall be submitted to the Contracting Office Representative (COR) no later than two weeks prior to base visit. The Visit Request Letter shall be IAW AFFARS 5352.242-9000.
4.2.4. Contractor Identification. Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.
4.3 Security. The Contractor must coordinate with appropriate base personnel and comply with all required security measures for gaining entry and working in all buildings. The Contractor may require Government escorts with proper building entry authorization and identification while in all buildings. Some areas in those buildings may require prior coordination through base personnel in specified work areas before entering and work can be accomplished. See paragraph 3.2 of this PWS for escort information.
4.3.1 ID Card/Key Control/Combinations. The Contractor shall establish and implement methods of assuring control and safeguard of all Government keys or lock combinations issued to the Contractor. GOVERNMENT KEYS SHALL NOT BE DUPLICATED. See FAR 52.245-2(e) (2).
4.3.2 Contractor Badges. The Contractor shall acquire all necessary base passes for Contractor personnel. The Contractor is required to provide identification badges to their employees, and all Contractor personnel shall wear these badges while on duty on the Government site. Badges are required to identify the individual, company name, and be clearly and distinctly marked as Contractor. Size, color, style.
4.3.3 Signs on Contractor Vehicles. The Contractor shall have signs displaying the Contractor’s company name on all company and employee vehicles operated on the base.
4.3.4 Base Passes/Common Access Cards (CACs).
4.3.4.1 Base access: In order to obtain base passes, the Contractor shall provide, the names, social security numbers, driver’s license numbers and state of issue (or equivalent), and birth date of all personnel who shall be performing work on Osan AB, ROK, under this contract or task order to the 51 CS/SCXP office. This information is required to grant access on Osan AB, ROK. Vehicle information (make, model, year, color, VIN, license plate number and state) must also be provided for all personal and company vehicles that shall be used on Osan AB, ROK, during performance of this contract or task order.
4.3.4.2 Computer Access: Contractor employees must meet requirements to obtain a CAC and access to NIPRNet. The Government will provide Common Access Cards (CAC) to Contractor personnel who require access to a Government computer. Contractor personnel who require access to a Government computer must complete an access application, an AF Form 4344, a DD form 2875, and DOD Security Awareness training prior to gaining computer access. The 51 CS/SCX POC can provide additional information and forms, if required.
4.3.4.3 Background Checks: The Contractor is advised that background checks are run for personnel requiring unescorted access, long term access, or Government computer access, and that it takes a MINIMUM of two weeks to process access requests. In order to expedite base passes and CACs, the Contractor may submit required information and forms to 51 CS/SCX before arrival on site.
4.4 Safety.
4.4.1 General Safety. The Contractor shall comply with all local, state and federal safety guidelines, including OSHA practices and procedures to protect employees from the hazards of entry into permit-required confined spaces, and this includes all Republic of Korea (ROK) requirements.
4.4.2 Manhole Conditions and Safety. Permits are required for access to manholes, and part of the permit process is to complete local confined spaces training. Contractor personnel shall coordinate with 51 CS to obtain the required training.
4.5 Mission Essential Services. Under the terms of this PWS, the Contractor is not required to perform any mission essential services or functions IAW DFARS 237.7600 during time of crisis.
4.6 Quality Control.
4.6.1 Quality Control Program. The Contractor shall develop and maintain an effective Quality Control Plan (QCP) for all services provided under this PWS. The QCP shall remain in effect during the term of the contract. Contractor shall retain the QCP on site and make it available for Government review upon request. Contractor shall provide any changes to the QCP to the KO at least ten (10) working days prior to implementation for review and approval.
4.6.2 Contracting Officer’s Representative (COR). The Government will periodically evaluate the Contractor’s performance by appointing COR(s) to monitor performance to ensure services are received. The Government representative shall evaluate the Contractor’s performance through intermittent on-site inspections of the Contractor's quality control program. The Government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections. Likewise, the Government may decrease the number of quality control inspections if merited by performance.
4.6.2.1 The COR shall inform the contractor in person when discrepancies occur and shall request corrective action. The COR shall make a notation of the discrepancy on their assessment checklist with the date and time the discrepancy was noted and shall request the contract manager (or authorized representative) to initial the entry on the checklist. Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the KO and not to the COR.
4.6.2.2 The services to be performed by the Contractor during the period of this contract shall at all times and places be subject to review by the Contracting Officer or authorized representative(s).
4.7 Deliverable Summary. All deliverables are subject to Government acceptance and approval. They shall meet professional standards and the requirements set forth in the Task Order. All deliverables shall be produced using recommended software tools/versions as accepted by the Government. A summary of deliverables is as follows:
| CDRL Number |
| CDRL Title |
| A001 |
| Minutes |
| A002 |
| Daily Status Report |
| A003 |
| Survey Data Report |
| A004 |
| Accuracy Worksheets |
| A006 |
| Communications Container Field Drawings |
| A007 |
| Out-brief Synopsis |
| A008 |
| Contractor Manpower Reporting |
Deliverables
| Deliverable |
| Frequency |
| Acceptable Quality Threshold |
| # Of Copies /Medium /Formant / Submit To |
| Correction /Remedy |
Meeting Minutes
PWS 4.1.2
(A001)
| Weekly, within three (3) working days after conclusion of the meeting. |
| Minuets accurately reflect the topics discussed. All action items are captures. |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within two (2) days. |
Status Report
PWS 1.2.1.2
(A002)
| Daily, by end of business day. |
| No more than two (2) instances of a deliverable being more than two (2) days late. |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within two (2) days. |
Survey Data Report (A003) PWS Para 1.2.2.3
| Daily, by end of business day. |
| This project will provide survey data (manholes, cables, ducts, inner-ducts, splices, location, GPS coordinates) into the web-based CVC tool. |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within three (3) days. |
Accuracy Worksheets (A004) PSW Para 1.2.2.7
| Daily, by end of business day. |
| The Contractor shall submit calculation worksheets (A004) showing compliance with the National Standard for Spatial Data Accuracy (NSSDA) statement at the 95% confidence level, as required by FGDC-STD-007.3-1998 |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within three (3) days. |
Demonstration Report (A005) PWS Para 1.2.4.2
| The Contractor shall record all demonstrations as they are accomplished and include products generated during the demo (e.g. CVC-produced manhole and cable diagrams, cable reports and results) in the Demonstration Report |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within three (3) days. |
Communications Container Field Drawings (A006) PWS Para 1.2.3.1
| The Contractor shall prepare legible field drawings to record the features for each communications container including manholes, hand holes, pedestals and vaults |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within three (3) days. |
Out-brief Synopsis (A007) PWS Para 4.1.4
| The Contractor shall conduct an out brief with the COR or designated representative and other site personnel 5 days prior to the period of performance end date. |
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within three (3) days. |
Contractor Manpower Reporting (A008) PWS Para 5.0
| Weekly, within three (3) working days after conclusion of the meeting |
| The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for |
performance of services provided under this contract at Osan AB
| 1 / Electronic / Contractor Formant /Submit to COR |
| Resubmit within three (3) days. |
5.0 Contractor Manpower Reporting (CMR) Requirement:
The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract at Osan AB. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on "Department of the Army CMRA" or the icon of the DoD organization that is receiving or benefitting from the contracted services. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2015. Contractors may direct questions to the help desk by clicking on "Send an email" which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s CMR website.”
6.0 APPENDICES.
A. Workload Data B. Applicable Documents and Standards C. Entities, Attributes, and Domain Values for Recording Required Communication Feature Data (BASIC COMM PATH TEMPLATE)
APPENDIX A
Workload Data Estimated Quantities of Outside Plant Features and CSIR Drawings.
Quantities of Outside Plant Features. Estimated quantities of features in the telecommunications outside plant infrastructure for Osan AB, ROK, are:
| Manholes | 462 each | ||||
| Handholes | 308 each | ||||
| General Containers | 60 each | ||||
| Information Transfer Node (ITN) | 9 each | ||||
| Building Entry Terminals | 462 each | ||||
| Cable Vaults | 3 each | ||||
| Ductbanks and duct | Unknown | ||||
| Direct-Buried Cable | Unknown | ||||
| Direct Buried Splice Cases | Unknown | ||||
| Missing, or to change Cable Tags | Unknown |
NOTE: Quantities of CSIR Drawings and Other Records. The Government will provide all legacy drawings in Micro-station format, to be used for reference purposes only; the Contractor may use these drawings to help resolve questions during field inspection, but shall not use the drawings as a basis for CVC entry.
APPENDIX B
Applicable Documents and Standards
The following documents are hereby incorporated by reference. The Contractor shall comply with these documents/standards during the performance of the contract requirements.
| ANSI/TIA/EIA-606-A Administration Standard for Commercial Telecommunication Standard |
| FGDC-STD-001-1998 - Content Standard for Digital Geospatial Metadata |
FGDC-STD-007.3-1998 - Geospatial Positioning Accuracy Standards Part 3: National Standard for Spatial Data Accuracy
FGDC-STD-007.4-2002 - Geospatial Positioning Accuracy Standards Part 4: Standards for Architecture, Engineering, Construction (A/E/C) and Facilities Management
OSHA CFR 29 Part 1910.146 – Permit-Required Confined Spaces
The Contractor shall obtain and comply with any other applicable manuals not identified above that would be required to meet industry standards.
APPENDIX C
Entities, Attributes, and Domain Values for Recording Required Communication Feature Data (BASIC COMM PATH TEMPLATE)
C.1 Feature Attributes for Comm-Path Entities.
C.1.1 GPS_MANHOLE
C.1.1.1 Definition. An enclosed structure (manhole, hand hole). A butterfly layout is used that shows the floor and walls flattened out so that duct openings can be drawn on the walls. This must be represented as one polygon (one row in the table). The point is used to show the center of the manhole/hand hole cover.
C.1.1.2 Geometry type. Site (Point).
C.1.1.3 Attributes.
| Column Name |
| SDSFIE Common Name |
| Description |
| Data Type |
| Use |
| Domain Table |
| NAME |
| Identifier Name |
| The standard identifier name (e.g. MH-19). |
| Char(20) |
| Required |
MH_TYPE_D
| A description for the type of manhole. |
| Char(16 |
| Required |
| D_MHTYP |
| MAPSRC_D |
| Map Source Discriminator |
| DISCRIMINATOR - Used to indicate the source of data for the spatial position of this graphic. |
| Char(16) |
| Required |
| D_DATSRC |
| MAPACU |
| Spatial Accuracy in Meters |
| Describes the spatial accuracy of mapsrc_d. in meters, +/- of where the feature may actually be. For example, if you are using GPS and it’s only accurate to 1 meter, put a 1 in this field. |
| Real |
| Required |
C1.2 GPS_VAULT
C.1.2.1 Definition. An enclosed structure in a facility, in which the outside plant cables are spliced to the tipping cables
C.1.2.2 Geometry type. Site (Point).
C.1.2.3 Attributes.
| Column Name |
| SDSFIE Common Name |
| Description |
| Data Type |
| Use |
| Domain Table |
| NAME |
| Identifier Name |
| The standard identifier name |
(i.e. V-19).
| Char(20) |
| Required |
| VLT_MAT_D |
| Vault Material Code |
| Discriminator References D_COSTRM table. Used to describe the material composition of the vault. |
| Char(16) |
| Required |
| D_COSTRM |
| MAPSRC_D |
| Map Source Discriminator |
| DISCRIMINATOR - Used to indicate the source of data for the spatial position of this graphic. |
| Char(16) |
| Required |
| D_DATSRC |
| MAPACU |
| Spatial Accuracy in Meters |
| Describes the spatial accuracy of mapsrc_d. in meters, +/- of where the feature may actually be. For example, if you are using GPS and it’s only accurate to 1 meter, put a 1 in this field. |
| Real |
| Required |
C.1.3 GPS_GENERAL_CONTAINER
C.1.3.1 Definition. An aboveground, enclosed structure that provides access to buried plant and a place to house splices, terminals.
C.1.3.2 Geometry type. Site (Point).
C.1.3.3 Attributes.
| Column Name |
| SDSFIE Common Name |
| Description |
| Data Type |
| Use |
| Domain Table |
| NAME |
| Identifier Name |
| The standard identifier name (i.e. PED-19). |
| Char(20) |
| Required |
| TYPE_D |
| Type Code |
| A description for the type of General Container. |
| Char(16) |
| Required |
| D_COPED |
MODEL_NO
| The model number of the General Container. |
| Char(16) |
| Required |
| TERMINAL_D |
| Terminal Existence Code |
| A Boolean indicating the presence of a terminal (Y/N). |
| Char(16) |
| Recommended |
| D_BOOLEN |
| BONDED_D |
| Bonded Code |
| A Boolean indicating whether the General Container is bonded. (Y/N). |
| Char(16) |
| Recommended |
| D_BOOLEN |
| MAPSRC_D |
| Map Source Discriminator |
| DISCRIMINATOR - Used to indicate the source of data for the spatial position of this graphic. |
| Char(16) |
| Required |
| D_DATSRC |
| MAPACU |
| Spatial Accuracy in Meters |
| Describes the spatial accuracy of mapsrc_d. in meters, +/- of where the feature may actually be. For example, if you are using GPS and it’s only accurate to 1 meter, put a 1 in this field. |
| Real |
| Required |
C.1.4 GPS_DBSPLICE
C.1.4.1 Definition. An enclosed capsule that represents a splice case (aerial or buried).
C.1.4.2 Geometry type. Site (Point).
C.1.4.3 Attributes.
| Column Name |
| SDSFIE Common Name |
| Description |
| Data Type |
| Use |
| Domain Table |
| NAME |
| Identifier Name |
| The standard identifier name (e.g. DBS01.1-1200_1-900). |
| Char(20) |
| Required |
| CAS_MAT_D |
| Case Material Code |
| Used to describe the material composition of the splice case. |
| Char(16) |
| Required for aerial splices and exposed DB splices |
| D_SPCMAT |
| CAS_TYP_D |
| Case Type Code |
| Used to describe the type of splice case. |
| Char(16) |
| Required for aerial splices and exposed DB splices |
| D_SPCCAS |
| MAPSRC_D |
| Map Source Discriminator |
| DISCRIMINATOR - Used to indicate the source of data for the spatial position of this graphic. |
| Char(16) |
| Required |
| D_DATSRC |
| MAPACU |
| Spatial Accuracy in Meters |
| Describes the spatial accuracy of mapsrc_d. in meters, +/- of where the feature may actually be. For example, if you are using GPS and it’s only accurate to 1 meter, put a 1 in this field. |
| Real |
| Required |
C.1.5 GPS_PATH_SEGMENT
C.1.5.1 Definition. Link that represents an enclosure path of comm items outside of a building, manhole, General Container, or other enclosed structure. For duct banks, comm-path segment can represent the virtual path, duct bank, duct, and inner ducts. For ducts, comm-path segment can represent the virtual path, duct, and inner ducts. For direct-buried cables at road-crossings, comm-path segment can represent the virtual path, road-crossing duct, and direct-buried cables. It can also represent the path of aerial cable, cable-bridges, and cable-troughs.
C.1.5.2 Geometry type. Polyline.
C.1.5.3 Attributes.
| ‘Column Name |
| SDSFIE Common Name |
| Description |
| Data Type |
| Use |
| Domain Table |
| PATH_TYP_D |
| Comm-Path Type Code |
| A discriminator field that describes what type of communications path this segment is representing. |
| Char(16) |
| Required |
| D_COPTHT |
COVERDEPTH
| The minimum depth of this part of the path from grade, in inches. This is mainly used for digging permits |
| Real |
| Recommended |
| MAPSRC_D |
| Map Source Discriminator |
| DISCRIMINATOR - Used to indicate the source of data for the spatial position of this graphic. |
| Char(16) |
| Required |
| D_DATSRC |
| MAPACU |
| Spatial Accuracy in Meters |
| Describes the spatial accuracy of mapsrc_d. in meters, +/- of where the feature may actually be. For example, if you are using GPS and it’s only accurate to 1 meter, put a 1 in this field. |
| Real |
| Required |
C.2 Domain Values for Attributes of Comm-Path Feature Entities.
C.2.1 D_BOOLEN: type list.
C.2.1.1 What it does. A table of Boolean data types YES and NO. Use for selecting the existence or non-existence of a value, condition, or feature.
C.2.1.2 Referenced by: GPS_GENERAL_CONTAINER
C.2.1.3 Attributes.
| Lookup Value |
| Long Description |
| YES |
| The condition is true or the feature does exist |
| NO |
| The condition is not true or the feature does not exist |
C.2.2 D_COPED: communications – General Container type.
C.2.2.1 What it does. This table contains information about various communications pedestal types.
C.2.2.2 Referenced by: GPS_GENERAL_CONTAINER.
C.2.2.3 Attributes.
| Lookup Value |
| Long Description |
| BD |
| BD - Buried Distribution Closure, size unknown |
| BOX |
| BOX - Rectangular box type enclosure, accessed by removing a cover panel |
| CAB |
| CAB - Cabinet enclosure, accessed through a hinged door |
| CAD |
| CAD - Controlled Access Distribution Closure |
| PED4 |
| 4 inch pedestal |
| PED6 |
| 6 inch pedestal |
| PED8 |
| 8 inch pedestal |
| PED12 |
| 12 inch pedestal |
| OTHER |
| Other |
| TBD |
| To Be Determined |
| UNKNOWN |
| Unknown |
C.2.3 D_COPTHT: communications - comm path type.
C.2.3.1 What it does. This table contains information about various communications path types.
C.2.3.2 Referenced by: GPS_PATH_SEGMENT.
C.2.3.3 Attributes.
| Lookup Value |
| Long Description |
| AERIAL |
| Above ground path between, poles, towers or buildings |
| CABLE_BRIDGE |
| Bridge only used for cables |
| CABLE_TROUGH |
| Pathway on top of ground for cables |
| DIRECT_BURIED |
| Below ground path where soil has direct contact with cable |
| DUCT |
| Single communications duct |
| DUCTBANK |
| A container for multiple ducts |
| STUB-OUT |
| Short duct used with manholes and vaults |
| SURFACE |
| Path directly on the surface |
| UNDER_ROAD |
| A duct for cables, usually under a road |
| UNKNOWN |
| Faulty Source Data |
C.2.4 D_COSTRM: structure – material.
C.2.4.1 What it does. This table contains information about various structure materials.
C.2.4.2 Referenced by: GPS_MANHOLE, GPS_VAULT.
C.2.4.3 Attributes.
| Lookup Value |
| Long Description |
| AL |
| Aluminum |
| CIS |
| Concrete Cast inSitu/Cast in Place |
| COMBINATION |
| Combination of materials |
| FIBERGLASS |
| Fiberglass |
| PLASTIC |
| Plastic |
| PRECAST |
| Pre-Cast Concrete |
| STEEL |
| Steel |
| UNKNOWN |
| Unknown |
| MASONRY |
| Made from bricks, clay tiles, or block. |
C.2.5 D_DATSRC: source list – data.
C.2.5.1 What it does. Allowable input values for data sources.
C.2.5.2 Referenced by: GPS_DBSPLICE, GPS_MANHOLE, GPS_PATH_SEGMENT, GPS_GENERAL_CONTAINER, GPS_VAULT.
C.2.5.3. Attributes.
| Lookup Value |
| Long Description |
| AS_BUILT |
| As-built drawings |
| FLDLOC_SURVEY |
| Field location survey |
| GPS_FLDLOC |
| GPS field located and verified data |
| UNKNOWN |
| Unknown |
C.2.6 D_MHTYP: type list - comm manhole.
C.2.6.1 What it does. The type of manhole.
C.2.6.2 Referenced by: GPS_MANHOLE.
C.2.6.3 Attributes.
| Lookup Value |
| Long Description |
| 1T1 |
| 1T1 |
| 4T1 |
| 4T1 |
| 5T1 |
| 5T1 |
| 6T1 |
| 6T1 |
| 6T2 |
| 6T2 |
| 8T1 |
| 8T1 |
| A |
| A Type |
| CEMH |
| Controlled Environment Manhole |
| HH_Type_A |
| Handhole Type A |
| J3 |
| J3 Manhole |
| J4 |
| J4 Manhole |
| JC9C |
| JC9C (2450mm x 1750mm x 1450mm) |
| L |
| L Manhole |
| R2A |
| R2A Manhole |
| T |
| T Manhole |
| V |
| V Manhole |
| OTHER |
| Other |
| UNKNOWN |
| Unknown |
C.2.7 D_SPCCAS: communications - splice case type
C.2.7.1 What it does. Allowable values for the type of splice case
C.2.7.2 Referenced by: GPS_DBSPLICE
C.2.7.3 Attributes.
| Lookup Value |
| Long Description |
| 12.5x28SS |
| 12.5 Inch Stainless Steel |
| 12.5x38SS |
| 12.5 Inch Stainless Steel |
| 12.5x45SS |
| 12.5 Inch Stainless Steel |
| 12.5x65SS |
| 12.5 Inch Stainless Steel |
| 2 TYPE |
| 2 Type |
| 2BB |
| 2 Inch Better Buried |
| 3BB |
| 3 Inch Better Buried |
| 4BB |
| 4 Inch Better Buried |
| 4x25.8RS |
| 4 Inch ReddiSeal |
| 4x25SS |
| 4 Inch Stainless Steel |
| 6BB |
| 6 Inch Better Buried |
| 5BB |
| 5 Inch Better Buried |
| 6BB |
| 5 Inch Better Buried |
| 7BB |
| 7 Inch Better Buried |
| 6.5x28.4RS |
| 6.5 Inch ReddiSeal |
| 6.5x38.5RS |
| 6.5 Inch ReddiSeal |
| 6.5x22SS |
| 6.5 Inch Stainless Steel |
| 6.5x28SS |
| 6.5 Inch Stainless Steel |
| 9BB |
| 9 Inch Better Buried |
| 9.5x28.4RS |
| 9.5 Inch ReddiSeal |
| 9.5x38.5RS |
| 9.5 Inch ReddiSeal |
| 9.5x28SS |
| 9.5 Inch Stainless Steel |
| 9.5x38SS |
| 9.5 Inch Stainless Steel |
| 9.5x45SS |
| 9.5 Inch Stainless Steel |
| 9.5x53SS |
| 9.5 Inch Stainless Steel |
| 2178-LS |
| 3M™ Series 2178-LS FO-Splice case |
| 2179-CS |
| 3M™ Series 2179-CS FO-Splice case |
| COR |
| Corning Fiber optic splice closure |
| FOSC_100_B_H |
| Raychem FOSC-100 B/H |
| HS |
| Heat Shrink |
| KBV |
| K&B Vault |
| LEAD |
| Lead |
| OTHER |
| Other |
| READY_ACCESS |
| Ready Access |
| UC_6_9 |
| Siemens UC 6-9 |
| UCN_7_10 |
| Siemens UCN 7-10 |
| UNKNOWN |
| Unknown |
C.2.8 D_SPCMAT: communications - splice case mat
C.2.8.1 What it does. Allowable input values for the material of the communications splice case
C.2.8.2 Referenced by: GPS_DBSPLICE
C.2.8.3 Attributes.
| Lookup Value |
| Long Description |
| AL |
| Aluminum |
| EVA |
| Ethylene Vinyl Acetate (Heat Shrinkable Tubing) |
| FIBER |
| Fiberglass |
| LEAD |
| LEAD |
| PE |
| PE - Polyethylene |
| PP |
| PP - Polypropylene |
| PVC |
| PVC - Polyvinyl Chloride |
| SS |
| SS - Stainless Steel |
| OTHER |
| Other |
| UNKNOWN |
| Unknown |
REMAINDER OF PAGE INTENTIONALLY LEFT BLANK
EXAMPLE A – COMMUNICATIONS CONTAINER FIELD DRAWING
Container Name MH-3 Bonded Yes_X__No______Alarm Yes___No X Size L 12 ft 6 ft D 6ft Grd.Rod Yes X No___Lid RND X___RET_____ Drainage Type None Duct Plugs Yes___No X Lid Size 30 Inch X Round Lock Present Yes___No X Ladder Yes___No X Lid Material: ( ) Concrete ( X ) Steel Lid Removal Requires Power Equipment Yes__ No X Container Material: Concrete Disposition ( X ) In Service,( ) Abandoned, ( ) Collapsed, ( ) Temporary,( ) Blocked,( ) Plugged, ( ) To Be Determined (TBD), ( ) Unknown Notes__Manhole buried, difficult to find.
EXAMPLE B – SPECIFICATIONS AND DETAILS FOR CABLE IDENTIFICATION TAGS
TWISTED PAIR CABLE
TAGS
DESCRIPTION OF TAG NOMENCLATURE
CVC EDITOR
ADD NEW CABLE SHEATH SELECTION
Goto TAB DESIGNATION
CVC CABLE TAG DESIGNATION
SEE NOTES BELOW FOR DESIGNATION
OF TWISTED PAIR CABLE TYPES
1Type
TYPE OF OUTER PROTECTION
FOR CABLE.
NUMBER OF CABLE PAIRS IN CABLE,
FOR 100 PAIR CABLES AND UP, DO
NOT INCLUDE “00’S” WHEN LABELING
CABLES.
FOR 24 PAIR CABLES AND LESS USE
AN “X” FOR 25 PAIR CABLES AND UP
USE A “-“.
CABLE GAUGE
TYPE OF CONDUCTOR PROTECTION
CABLE NUMBER
CABLE COUNT
A “+ ALPHA” TO IDENTIFY DEAD
PAIRS
9 NOMENCLATURE CVC CABLE TAG
TWISTED PAIR CABLE NOMENCLATURE DESCRIPTION OF TAG NOMENCLATURE
DEAD PAIR COUNT
TWISTED PAIR
FIBER OPTIC CABLE
TAG
DESCRIPTION OF TAG NOMENCLATURE
ADD NEW CABLE SHEATH SELECTION
Goto TAB CABLE DESIGNATION
OR
SEE NOTES BELOW FOR DESIGNATION
OF FIBER OPTIC CABLE TYPES
1Type
“A” IF ARMORED, “F” IF FLAME RETARDANT
NUMBER OF FIBERS IN CABLE SHEATH 2
SHEATH STRUCTURE/TYPE DESIGNATORS
“C” CENTER SUPPORT
“L” LOOSE TUBE
“T” TIGHT TUBE
“B” BLOWN FIBER
“R” RIBBON
CORE OR CLADDING DIAMETER MICRONS)
8.3 CORE FOR SINGLE MODE*
50 OR 62.5 CORE FOR MULTIMODE**
200 CORE
125 CLADDING
140 CLADDING
FILLED, OTHERWISE BLANK
LOCALLY ASSIGNED CABLE NUMBER
“1242/678” FROM/TO BUILDING NUMBERS
COMPLEMENT COUNT
FIBER OPTIC
FO1242/678,1-12
FO1242/688,1-12
FO1242/702,1-12
FO1242/744,1-12
COAXIAL CABLE (SERVICE TO ATCALS EQUIPMENT) TAG
DESCRIPTION OF TAG NOMENCLATURE
CVC EDITOR
ADD NEW CABLE SHEATH SELECTION
CVC Goto TAB DESIGNATION
CVC CABLE TAG
DESIGNATION
SEE NOTES BELOW FOR DESIGNATION
OF COAXIAL CABLE TYPES
1Type
COXIAL CABLE
“-AIR”, AIR DIELECTRIC
“-FF” FOAM DIELECTRIC
“-FIGURE 8”, FOAM SELF-SUPPORT/FIGURE 8
“-QUAD” , QUAD FOAM DIELECTRIC
“-SOLID” , SOLID DIELECTRIC
“-TWINAX” , TWINAX DIELECTRIC
DESIGNATOR OF METEROROLOGICAL OR ATC
EQUIPMENT TRANMITTING SIGNAL.
COMMON NAME OF COAXIAL CABLE TYPE
CABLE NUMBER4
COAXIAL
AN GPN-20 [RG216, #4]
FIBER OPTIC/TWISTED PAIR CABLE TAG
DESCRIPTION OF TAG NOMENCLATURE
CVC EDITOR
ADD NEW CABLE SHEATH SELECTION
Goto TAB CABLE DESIGNATION
SEE NOTES BELOW FOR DESIGNATION
OF FIBER OPTIC/TWISTED PAIR CABLE TYPES. (ALSO, REFER TO INDIVIDUAL DESCRIPTIONS FOR FIBER OPTIC AND TWISTED PAIR CABLES)
NUMBER OF FIBERS IN CABLE SHEATH
SHEATH STRUCTURE/TYPE DESIGNATORS
CORE OR CLADDING DIAMETER (MICRONS)
NUMBER OF TWP IN CABLE SHEATH4
TWP GAUGE
FIBER OPTIC CABLE DESIGNATOR
LOCALLY ASSIGNED CABLE NUMBER
NUMBER OF FIBERS IN CABLE SHEATH8
COMPLEMENT COUNT
TWP DESIGNATOR AND CABLE…
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.