W91QVN-18-R-0190-0001RELEASED.pdf

PDF 401 KB Posted

Attached to
CVC Infrastructure Assessment
Solicitation number
W91QVN-18-R-0190
Issued by

About this file

Amendment

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See Continuation Page.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 35

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 31-Aug-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W91QVN18R0190

X 9B. DATED (SEE ITEM 11)

20-Aug-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

31-Aug-2018

CODE

411TH CONTRACTING SUPPORT BRIGADE, KOREA

SERVICES DIV, UNIT #15289

APO AP 96271

UNITED STATES

W91QVN 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91QVN18R0190

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES ADDENDUM

The purpose of this amendment is to record the following changes:

1. Respond to questions associated with this solicitation. The Government’s response to Offerors questions are located on attachment named Government Response to questions.

2. PWS has been revised see highlighted areas.

3. Please reference FAR Clause 52.212-1 and 52.212-1. Factor C- Past Performance 52.212-2 has been changed to remove the requirement for Past Performance Questionnaires (PPQ). Please see the strike-through. Offers still have to submit a minimum of two written references in their proposal.

4. The closing date has been changed to 13:00 hrs, 05 Sep 2018 Local Korea Time.

5. All other changes remain unchanged.

Note: All proposals shall be submitted in Federal Business Opportunities (FBO) https: //www.fbo.gov by 1300 hours 05 Sep 2018 (Local Korean Time).

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

PWS

PERFORMANCE WORK STATEMENT (PWS)

FOR

CVC SURVEY OF COMMUNICATIONS INFRASTRUCTURE

Osan Air Base, Republic of Korea

1. GENERAL INFORMATION

1.1. Description of Services/Introduction: 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 provide technical/field services necessary to locate and perform Geographic Information System (GIS) data collection of Outside Plant (OSP) cable infrastructure and communications pathways for entry of collected data into the Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC). Additionally, the Contractor shall enter into all (estimated about 770) communication "containers", to include communication Vaults, Maintenance-Holes (MH), Hand-Holes (HH), and Pedestals in order to record/document detailed container information by means of field drawings. The Geospatial survey and the field inspection/container documentation actions will be performed within the confines of Osan Air Base, Republic of Korea, as designated by the government. The contractor shall perform to the standards in this contract. This includes the planning, coordination, and surveillance of the activities necessary to ensure disciplined work performance and timely resources application to accomplish all tasking under the contract. The contractor shall be responsible for maintaining communication with the Contracting Officer (KO) and the Contracting Officer’s Representative (COR), and to immediately notify both the KO and the COR of any problems that would prevent timely performance of this contract. The contractor is responsible for and required to implement, and maintain management control systems necessary to plan, organize, direct, and control all activities under this contract.

1.2. Background: This document will identify the safety requirements, list of materials/specifications and performance work standards that shall be required by the contractor. It is the vehicle that will allow the assignment of work to a contractor when the requiring customer deems it necessary. This document is also synchronized with the Unified Facilities Criteria (UFC), which are mandated under Department of Defense (DoD) policy. The UFC system is prescribed by the Military Standards (MIL-STD) 3007, Standard Practice for Unified Facilities Criteria and Unified Facilities Guide Specifications (UFGS) and provides planning, design, sustainment, restoration, and modernization criteria. The standard applies to military departments, defense agencies, and DoD Field activities in accordance with (IAW) the Under Secretary of Defense for Acquisition Technology and Logistics (AT&L) Memorandum dated 29 May 2002. USF 3-580-01, Telecommunications Interior Infrastructure Planning and Design, dated 01 June 2016, and Chapter 3 of the Technical Criteria for the Installation Information Infrastructure Architecture (I3A) by the United States Army Information Systems Engineering Command dated February 2010, will be the governing documents for the contractor. This document establishes an implementation concept that can be used to shape architectural templates and to include the design process for the I3A. It identifies proven infrastructure construction techniques, defines common practice, and serves as an authoritative implementation criterion.

1.3. Objectives: Currently there is no accurate documentation of Osan, AB Outside Plan (OSP) 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 Geospatial 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 Additionally the contractor will be responsible for performing as-built drawings using GPS assisted survey equipment for accuracy of ± 1 foot or .5 meter

1.4. Scope of Work: The contractor shall perform telecommunications engineering and installation services for outside plant (OSP) infrastructure. To include the complete communications infrastructure footprint survey of fiber optic cables, copper cables, underground conduits, manholes, handholes, pull boxes, protected distribution systems, LAN distribution equipment, and patch panels. All Engineering and Installation (E&I) work shall meet government and industry developed standards and practices. 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.5. Period of Performance (POP): The entire period of performance shall not exceed 8 months from the date of award.

Base Period: 30 Sep 2018 – 31 May 2019 (or 8 months from the date of award)

1.6. Place of performance: The contractor shall perform the services in the PWS at Osan Air Base, Republic of Korea (ROK).

1.7. Not Used:

1.8. Requirements:

1.8.1. Geospatial Survey. The Contractor shall use Global Positioning System (GPS) technology to locate and collect data on OSP infrastructure features and communications pathways to include an estimated 510,000 feet with a variant of +/- 10 % of cable routes and associated OSP features to include containers, pedestals, direct buried splices, terminals, etcetera servicing all buildings with a variant of +/- 10 %. Outside plant features/containers include vaults, maintenance-holes, hand-holes, pedestals, underground cables, direct buried splices, terminals, etc. The communications pathways include duct routes, aerial and direct-buried cable, trench routes, communication pathway entry points on building exterior walls that lead to interior building entry terminals, etc. The Contractor shall augment the GPS survey by using conventional land surveying equipment and electronic cable locating (underground utility toning) equipment to meet requirements. The Contractor shall ensure collected/provided data is compatible with the CVC. The Government shall provide an annotated base map that identifies zones requiring survey, see attachments for reference. The Contractor is required to locate and record information for any cables residing in the communications outside plant infrastructure to include Abandoned in Place (AIP) cables. The Contractor is required to electronically trace the path of all direct buried cables and/ or ducts by plotting GPS points. The Contractor is required to locate every communication path formed by a single duct, or by a bank of ducts, including communication paths that run parallel to one another provided there is a tracer wire or metallic conductor in the path. . In the event tracer wire is not in place or non-metallic material is available to properly use GPS measurement tools, specialized tools such as a Cable Rod with tracer tips should be utilized to collect GPS data when possible. No installation is required of tracer wire but using necessary tools to properly collect necessary data for this survey.

1.8.2. GPS Accuracy Standards. The Contractor shall use GPS to determine the horizontal position of communications OSP 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/resources/download-geospatial-standards.

1.8.3. GPS Accuracy of Feature Locations. Each OSP infrastructure feature and communications pathway requiring geospatial coordinates shall be located within 1 foot or.5 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 containers shall be recorded at the center of the maintenance lid. Geospatial coordinates for the location of pedestals, marked direct buried splices and Electronic Marker System marked direct buried splices shall be recorded for the top center of the feature or marker. Geospatial coordinate data for the location of communication pathway lines shall be recorded at a minimum every 20 feet and minimum every 5 feet along 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.8.4. Shape Files. The GPS collected OSP infrastructure features and communications pathways attribute, metadata, and location information shall be converted to, stored, and submitted in an Environmental Systems Research Institute (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, .dbf, .shp, .shx and .cor) files included that specifies the parameters of the coordinate system. Shape files shall be provided as part of Survey Data Report within 10 working days of completing GPS Survey (A002).

1.8.5. 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 by Attachment B.

1.8.6. 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 Attachment A and in coordination with the government to create the data dictionary for use in the logger.

http://www.fgdc.gov/resources/download-geospatial-standards

1.8.7. 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 Survey Data Report as described below, (A002).

1.8.8. Accuracy Worksheets. Calculation worksheets showing compliance with the National Standard for Spatial Data Accuracy (NSSDA) statement at the 95% confidence level, as required by paragraph 3.4, shall be submitted as an Excel (.xls) file (A003). Examples of the Horizontal Accuracy Statistical Worksheet are given in FGDC- STD-007.3-1998, Appendix 3-B (informative) Horizontal Accuracy Computations, Tables 1 and 2. The standard can be downloaded from the FGDC website: http://www.fgdc.gov/resources/download-geospatial-standards.

1.8.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.

(A004).

• Submitted Shape files shall have:

• No erroneous overshoots, undershoots, dangles or intersections in the line work.

• Features snapped where applicable (for example, GPS Path Segment snapped to GPS Manhole)

• Continuous lines, with no pseudo-nodes

(Nodes shall only exist where the attributes of a line change)

• No sliver polygons

• All polygons completely closed and have a single unique centroid

• Digital representation of the common boundaries for all graphic features that is coincident, regardless of feature layer

1.8.10. Quality Control Plan (QCP). The contractor shall develop and maintain an effective quality control plan to ensure services performed under this contract are in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor shall provide the QCP to the Contracting Officer (KO) and Contracting Officer’s Representative (COR) within 30 days after the award of this contract. As a minimum the contractor shall develop quality control procedures that address the tasks identified in the Specific Tasks paragraph (Paragraph 4.8)

1.8.11. The contractor shall provide a quality control plan (QCP) to the COR prior to initiation of work. Any changes to the QCP must be approved through the COR. The QCP must contain at a minimum the items listed below

• An overarching project management and administrative plan

• A description of the inspection system that covers all services. The description shall include specifics as to the areas to be inspected, the frequency of inspections, and the title and organizational placement of the inspectors

• A description of the methods to be used for identifying and preventing defects in the quality of service performed

• A description of the records to be kept to document inspections and corrective or preventative actions taken

• A feedback mechanism for customer complaints and resolution of valid complaints

1.8.12. 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

1.8.13. 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 http://www.fgdc.gov/resources/download-geospatial-standards 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

1.8.14. 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).

1.8.15. Field Inspection and Documentation of Containers. The Contractor shall conduct a field inspection of communication infrastructure features, 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.

The Contractor shall document the attributes of the communications pathways and comprehensively record/document all information pertaining to an estimated 770 communication containers with a variant of +/- 10 % to include their orientation, content, and etc. (reference, Attachments A/B/C). The Contractor shall enter all containers to provide accurate information/field inspection. Some container lids may require special equipment for removal. The Contractor shall pump out water and clear containers of mud and debris as required, perform field inspection and the documentation action. The Contractor shall document and list the existing conditions and note any discrepancies. (A001)

1.8.16. Demonstration Field Survey

1.8.16.1 Demonstration Plan. The Contractor shall prepare and furnish a plan for demonstrating that information recorded for all Contractor-surveyed OSP features is accurate. The purpose of each demonstration is to use validate the quality and amount of work completed. The initial demonstration shall be presented after ten calendar days, this will ensure that the information is IAW this PWS. Demonstrations after the initial shall be performed at 28 day intervals or within 10 calendar days upon government request. The Contractor shall furnish all equipment and personnel required to conduct demonstrations. The demonstration plan shall describe the work the Contractor plans to have completed by each demonstration step and how the Contactor is going to show the work has been completed. The demonstration plan must be approved for use by the government.

1.8.16.2. Progress Demonstrations. During the progress demonstrations, the Government reserves the right to perform any duplication of the Contractor performed demonstrations to assure results conform to prescribed requirements for completeness, workmanship, and accuracy. The Contractor shall notify the 51st CS/SCXP Contracting Officer Representative (COR) at least 5 working days prior to any demonstrations and shall make available all standards and criteria used to accomplish demonstrations.

1.8.16.2.1 Initial Demonstration

Contractor shall:

a. Allow two work days to conduct the demonstration.

b. Demonstrate end to end cable connectivity. For up to ten (10) cables, selected by the COR at the time of the demonstration, the Contractor shall show that, for the selected cables, the number, type, and pair or strand count, the cable run continuously (without gaps) between the point of origin and the point of final termination. COR may select additional containers, if discrepancies are identified.

c. Provide field survey information to complete CVC generated CSIR drawings for up to ten (10) container selected by the COR, five days prior to the start of the demonstration. In order for a drawing to be complete, the container must be properly sized and shaped, geospatially oriented where placed. In addition, the container must be fully populated with appropriate cables, splices, duct bank placement and layout, and equipment and junction device information. Without editing, at the time of demonstration, of the cable or strand attributes, the container CSIR drawings must show properly aligned and spaced cables.

d. Have copies of all communication container field drawings and communications pathways available at the initial demonstration for the COR to cross check any field drawing against information contained within CVC (A002 & A005) and for the COR to field check actual conditions in the containers against information in the field container drawings.

1.8.16.2.2 Demonstration at 35 percent completion: At the 35 percent completion the

Contractor shall:

a. Allow two work days to conduct the demonstration.

b. Demonstrate end to end cable connectivity. For up to ten (10) cables, selected by the COR at the time of the demonstration, the Contractor shall show that, for the selected cables, the number, type, and pair or strand count, the cable run continuously (without gaps) between the point of origin and the point of final termination. COR may select additional containers, if discrepancies are identified.

c. Provide field survey information to complete CVC generated CSIR drawings for up to ten (10) container selected by the COR, five days prior to the start of the demonstration. In order for a drawing to be complete, the container must be properly sized and shaped, geospatially oriented where placed. In addition, the container must be fully populated with appropriate cables, splices, duct bank placement and layout, and equipment and junction device information. Without editing, at the time of demonstration, of the cable or strand attributes, the container CSIR drawings must show properly aligned and spaced cables.

d. Have copies of all communication container field drawings and communications pathways available at the 35 percent demonstration for the COR to cross check any field drawing against information contained within CVC (A002 & A005) and for the COR to field check actual conditions in the containers against information in the field container drawings.

e. Open and prepare up to ten (10) containers randomly selected by the COR for entry by the COR or designated government representative to field check actual conditions in the containers against information in the field container drawings (A005).

1.8.16.2.3 Demonstration at 65 percent completion: At the 65 percent completion the

a. Allow two work days to conduct the demonstration

b. Demonstrate end to end cable connectivity. For up to ten (10) cables, selected by the COR five days prior to the start of the demonstration, the Contractor shall show that, for the selected cables, the number, type, and pair or strand count, the cable run continuously (without gaps) between the point of origin and the point of final termination. COR may select additional containers, if discrepancies are identified.

c. Provide field survey information to complete CVC generated CSIR drawings for up to ten (10) containers selected by the COR, at the time of the demonstration. In order for a drawing to be complete, the container must be properly sized and shaped, geospatially oriented where placed. In addition, the container must be fully populated with appropriate cables, splices, duct bank placement and layout, and equipment and junction device information. Without editing, at the time of demonstration, of the cable or strand attributes, the container CSIR drawings must show properly aligned and spaced cables.

d. Have copies of all communication container field drawings and communications pathways available at the 65 percent demonstration for the COR to cross check any field drawing against information contained within CVC (A002 & A005) and for the COR to field check actual conditions in the containers against information in the field container drawings

e. Open and prepare up to (10) containers randomly selected by the COR for entry by the COR or

1.8.16.2.4 Demonstration at 100 percent completion: At the 100 percent completion the

a. Allow two days to conduct the demonstration.

b. Demonstrate end to end cable connectivity. For up to ten (10) cables, selected by the COR at the time of the demonstration, the Contractor shall show that, for the selected cables, the number, type, and pair or strand count, the cable run continuously (without gaps) between the point of origin and the point of final termination. COR may select additional containers, if discrepancies are identified.

c. Provide field survey information to complete CVC generated CSIR drawings for up to ten (10) container selected by the COR, five days prior to the start of the demonstration. In order for a drawing to be complete, the container must be properly sized and shaped, geospatially oriented where placed. In addition, the container must be fully populated with appropriate cables, splices, duct bank placement and layout, and equipment and junction device information. Without editing, at the time of demonstration, of the cable or strand attributes, the container CSIR drawings must show properly aligned and spaced cables.

d. Have copies of all communication container field drawings and communications pathways available at the 100 percent demonstration for the COR to cross check any field drawing against information contained within CVC (A002 & A005) and for the COR to field check actual conditions in the containers against information in the field container drawings

e. Open and prepare up to ten (10) containers randomly selected by the COR for entry by the COR or

1.8.16.3 Demonstration Reports. The Contractor shall record all demonstrations as they are accomplished and make all results available to the 51st CS COR for review as demonstrations are completed (A006).

1.8.16.4 Weekly Status Reports. The Contractor shall prepare a Weekly Status Report during the course of performing the work (A008). The purpose of the report is to inform the government 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. (A007)

1.8.16.5 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

1.9. Deliverables

1.9.1. Acceptance and Approval Criteria. All deliverables are subject to Government acceptance and approval.

They shall meet professional standards and the requirements set forth in the basic contract and this PWS.

Documentation shall be in accordance with the Contract Deliverables Requirements List (CDRL) declaration.

Referenced format or contractor format is acceptable as approved by the government. A Register Communications Distribution Designer (RCDD) shall be on staff. The Contractor shall provide the Government the certification documentation of the RCDD on staff in their proposal. All deliverables shall be produced using recommended software tools/versions as accepted by the Government. All deliverables shall be reviewed and stamped by the RCDD on staff.

CDRL DID Data Item Title A001 DI-MISC-80508B Technical Report – Studies/Services (List of Discrepancies and Missing Data

Issues) A002 DI-MISC-80508B Technical Report – Studies/Services (Survey Data Report) A003 DI-MISC-80508B Technical Report – Studies/Services (Accuracy Worksheet) A004 DI-MGMT-81117 Technical management and Work Plan (Quality Control Plan) A005 DI-MISC-80508B Communications-Computer Systems Installation Records (CSIRs)

(Communications Container Field Drawing) A006 DI-MISC-80508B Technical Report – Studies/Services (Demonstration Report) A007 DI-MISC-80368A Status Report (Integrated Product Team (IPT) Minutes) A008 DI-MISC-80368A Status Report (Weekly Status Report) A009 DI-MISC-80368A Status Report (Outbrief Synopsis)

1.9.1. Distribution List.

The Contractor shall deliver the required numbers and type of copies IAW the distribution list set forth below.

DOCUMENTS 51 CS / SCXP Changed to 51 CS/SCOW

CDRL A001 *1 EM *WD *1 EM *WD

CDRL A002 *1 CD *1 CD

CDRL A003 *1 CD*1PC *1 CD*1PC

CDRL A004 *1EM*WD

CDRL A005 Colored paper copies Bound of each Communications Container Field Drawing 10%, 35%, 65% and an all-inclusive 100%, and 1 CD of colored electronic copies in Adobe PDF format of each Field Drawing at 10%, 35%, 65% and an all-inclusive 100%

CDRL A006 *1 CD, *1 PC *1 CD,

CDRL A007 *1 EM per attendee *1 EM per attendee

CDRL A008 *1EM, *WD to Member on IPT *1EM, *WD to Member on IPT

CDRL A009 *EM, *WD *EM, *WD

*CD = Compact Disc *PC = Paper Copy *EM=Email WD=Word doc. Attachment

1.10. Return of Government Property and Out-brief.

1.10.1. Return of Government Property. Prior to the out-brief, the Contractor shall return all Government equipment, door keys, etc. issued to contractor personnel for the performance of this contract.

1.10.2. Out-brief. The Contractor shall conduct an out-brief with the COR or designated representative and other site personnel at the conclusion of the Field Survey The site survey out-brief shall inform the COR of results and maintenance issues. At the conclusion of the out-brief, the Contractor shall provide the site POC a written synopsis of the action issues which includes major concerns or action items and a list of attendees (A009). A copy of this synopsis shall be forwarded to the CO within two workdays of the out-brief.

1.11. Contractor Manpower Reporting Requirement:

1.11.1. 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.”

1.11.2. The Office of the Assistant Secretary of the Army Manpower & Reserve Affairs operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor Manpower (including sub-contractor manpower) required for performance of this contract.

1.11.3. The Contractor shall completely fill in all the information in the format using the following web address https://armycmra.dmdc.osd.mil/Login.aspx.

1.11.4. The required information includes:

Contracting Office, Contracting Officer, Contracting Officer’s Representative and Technical Monitor;

Contract number, including task and delivery order number;

Beginning and ending dates covered by reporting period;

Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data;

Estimated direct labor hours (including sub- Contractors);

Estimated direct labor dollars paid this reporting period (including sub-Contractors);

Total payments (including sub-Contractors);

Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different);

Estimated data collection cost;

Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing them with its UIC for the purposes of reporting this information);

Locations where Contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

Presence of deployment or contingency contract language; and Number of Contractor and subcontractor employees deployed in theater this reporting period (by country).

1.11.5. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Army via the ecru secure data collection site. The contractor is required to completely fill-in all required data fields within the ecru. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through 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.

2. CONVERSION OF CONTRACTOR COLLECTED DATA TO CVC.

2.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. It is highly preferred that the contractor or the sub-contractor meet necessary background checks as listed in paragraph 2.1.1 to request and be granted NIPRNet access The Contractor will be provided Government-http://www.ecmra.mil/ https://armycmra.dmdc.osd.mil/Login.aspx 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 navigate and use off the CVC online tool.

2.1.1. For contractors requiring Common Access Card (CAC). Required for a minimum of one member (maximum of two) for the purpose of inputting collected data into CVC. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

2.1.2. For information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to IA/IT functions.

2.2. Discrepancies/Missing Data Issues. The Contractor’s weekly Status Report (A001/A008) 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 1.9 of this PWS.) All issues shall be either resolved by the Contractor and entered into CVC or accepted by the Government for Government action.

2.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.tiner.af.mil/cips/mycips.aspx. (CIPS account required for access).

2.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.

2.5. 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.

2.6. 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.

2.7. 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 https://cipsaf.tiner.af.mil/cips/mycips.aspx https://cipsaf.tinker.af.mil/cips/mycips.aspx 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 and occur within five working days of inspecting and collection of geospatial data of selected area based on scheduled area till full completion of this contract.

2.8. 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 (access to site once contractor has been vetted and submitted necessary account documents) 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.

2.9. Warranty: All work performed under this contract shall be covered under warranty by the contractor for one

(1) year after completion of the original work. This shall include at a minimum, repair, replacement, and/or re-installation of any services performed. Warranty service work to be carried out shall be prioritized between the ACO, COR, and the contractor. The contractor shall ensure the work carried out in support of the warranty does not interfere with the COR’s overall program objectives. 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.

3. SERVICE SUMMARY (SS)

3.1. General: The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success but do not represent all contract performance requirements. All contract performance requirements in this PWS will be monitored.

3.2. Performance Evaluation.

3.2.1. Performance of a service shall be evaluated to determine whether or not it meets the performance requirements of this contract. Re-performance of unacceptable services at no additional cost is the preferred course of action when appropriate. In the case of issued Corrective Action Reports (CARs), the Contracting Officer shall take appropriate measures according to inspection of services clause in the contract, i.e., FAR 52.246-4, 52.246-5, or 52.212-4(a).

3.2.2. The contractor is advised to implement procedures to identify, prevent, and ensure non- recurrence of defective services.

3.2.3. If service is unsatisfactory, the COR will notify the assigned AFTC/PZIOAA CA. Then, AFTC/PZIOAA https://cipsaf.tinker.af.mil/cips/mycips.aspx will notify the contractor’s contract manager when the service is unsatisfactory. A written record of the problem will be issued and the contract manager will acknowledge it in writing (can be by electronic mail digitally signed), and request a corrective action.

Performance Requirements Summary

3.3 Government Quality Assurance

3.3.1 The government shall inspect and evaluate the contractors’ performance to ensure services are received in accordance with requirements set forth in this contract. The COR will use the contractor’s work schedule, or modified version thereof, to record validation results. Results of the validation then becomes the official Air Force record of the contractor’s performance. Government surveillance of tasks not listed in the PWS or by methods other than those listed in the PWS (such as provided for by the Inspection of Services clause) may occur during the performance period of this contract. Such surveillance will be done according to standard inspection procedures or other contract provisions. Any action taken by the CO as a result of surveillance will be according to the terms of this contract.

3.3.2 The government will periodically evaluate the contractor’s performance in accordance with the Quality

Assurance Surveillance Plan (QASP). The government may inspect each task as completed and increase the number of quality assurance inspections if deemed appropriate because of repeated failures discovered during

SS Performance Objective PWS Paragraph

Performance Threshold Rating Criteria

Quality 1 Progress Demonstrations--

During the progress demonstration at Initial, 35 percent, 65 percent and 100 percent work completion.

1.8.16.2.1 thru

1.8.16.2.4

a. COR accepts Initial progress demonstration within 28 calendar days of contract award

b. COR accepts 35% progress demonstration.

c. COR accepts 65% progress demonstration.

d. COR accepts 100% progress demonstration. Final demonstration must show 100% end-to-end connectivity, for all cables in the outside plant and, for (10) randomly selected containers.

Correct failures within one work day.

Schedule 2 Demonstration Report--

Reports of demonstrations of the CVC updates at the Initial/Monthly, 35 percent, 65 percent, and 100 percent completion points..

1.8.16.2 Provided to the COR within 10

calendar days of completing the demonstrations

Correct failures within one work day.

3 Contractor shall prepare a Weekly Status Report during the course of performing the work (A008) The purpose of the report is to inform the government of project progress, problems being encountered, and other topics necessary/beneficial to ensure success and timely completion of the contract requirements.

1.8.16.4 Provided to the COR on the same day

each week with requested topics addressed.

Correct failures within one work day.

surveillance inspections or because of repeated customer complaints. Likewise, the government may decrease the number of quality assurance inspections if performance dictates.

3.3.3 When an observation indicates defective performance, the COR will require the contract manager or representative at the site to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation, only acknowledgment that he or she has been made aware of the defective performance. When a performance threshold has not been met or contractor performance has not been accomplished, the COR will initiate and provide the KO a CAR for issuance to the contactor. The contractor shall respond to the CDR IAW instructions provided and return it to the KO within 10 calendar days of receipt.

3.4 Performance Assessment.

3.4.1 Monthly Surveillance. Periodic surveillance will be conducted on a scheduled basis and may be adjusted, based on quality trends. The surveillance results shall be maintained as Past Performance Information (PPI) and utilized to submit information into the annual Contractor Performance Assessment Report System (CPARS).

Surveillance results, will be used to develop metrics to track contractor’s overall compliance with contract terms and conditions. The contractor will be provided a copy of their assessment 365 days from contract award. The contractor shall have 60 days to review and submit comments for the evaluation activity’s consideration before the assessment is made final.

3.4.2 Past Performance Information (PPI). PPI can be provided to other government agencies, as requested.

3.4.3 Customer Complaints. The COR will receive and investigate all complaints. The COR shall be responsible for validating customer complaints. The CO shall make final determination of the validity of customer complaint(s) in cases of disagreement with the COR and the contractor. Validated customer complaints shall be corrected within 2 hours of notification. KO will validate corrective action.

3.4.4 Surveillance of Non-Service Summary Items.

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.