Attachment 5 FOWAN-Upgrade VCRM v1 forBidders FINAL.xlsx
XLSX spreadsheet 159 KB Posted
- Solicitation number
- W91CRB25R5014
About this file
This is a Performance Work Statement (PWS) and System Requirements Document (SRD) for the U.S. Army Communications-Electronics Command's Foreign Military Sales (FMS) project to upgrade the Royal Jordanian Air Force's (RJAF) Fiber Optic Wide Area Network (FOWAN) transmission nodes. The project involves delivering a new network platform with enhanced capabilities, including Dense Wavelength-Division Multiplexing (DWDM), Optical Transport Network (OTN) switching, and packet switching technologies to maximize network efficiency, scalability, and availability across 25 sites in Jordan's eastern region.
The solicitation (W91CRB25R5014) is a 100% small business set-aside with a Lowest Price Technically Acceptable (LPTA) evaluation methodology. The contract will be a firm-fixed-price with a performance period of 18 months, covering hardware delivery, services, training, and optional spare parts and maintenance support. Key deliverables include main platform equipment, daughter equipment, power systems, network management systems, program management, engineering, testing, logistics support, and two training sessions. Proposals are due by noon EDT on 22 April 2025, with an anticipated award focused on implementing a flexible, scalable network solution that supports various traffic protocols and can accommodate future expansions.
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
VCRM Instructions
| VCRM Instructions |
| Offeror is required to fill in COLUMNS "D" and "E" for Tab "FOWAN PWS" and "FOWAN SRD" that highlighted in "Green". |
FOWAN PWS VCRM
This document contains information sensitive to the Government of the Hashemite Kingdom of Jordan.
Distribution beyond Official US Government channels is not authorized without the express consent of the Government of the Hashemite Kingdom of Jordan.
PWS Paragraph Section Header Requirement
FOWAN UPGRADE PWS
(v1.0, dated 10 March 2025) Vendor Compliance Description Proposal Reference (Page # and Section Header)
| 1. | SCOPE | The United States Army Communications-Electronic Command (USCECOM) Security Assistance Management Directorate (SAMD) has been tasked to assist the Hashemite Kingdom of Jordan’s Armed Forces (JAF) and the Royal Jordanian Air Force (RJAF) in implementing a new solution to maximize the efficiency of the RJAF Fiber Optic Wide Area Network (FOWAN) node network and increase the flexibility, scalability, availability, and remote configurability of the network to lower operational expenses, turn up new services and enhance the network as needed. This goal will be achieved through phased transmission node upgrades applying design best practices and integrating the latest technologies into the existing capability already in-country. The scope consists of delivering equipment, services, spare parts and training. This Performance Work Statement (PWS) establishes and identifies the requirements authorized under Foreign Military Sales (FMS) Letter of Authorization (LOA) JO-B-YFG. | No VCRM input required | No VCRM input required |
| 1. | SCOPE | The Contractor shall provide materials, services, and training under a single Firm-Fixed Price (FFP) contract. | ||
| 1. | SCOPE | The word Government in this document refers to the United States Government (USG). The words End User in this document refers to the JAF and/or RJAF. | No VCRM input required | No VCRM input required |
| 1.1. | BACKGROUND | U.S. Army Communications Electronics Command (USCECOM) is responsible for developing and applying emerging technology to significantly advance the Soldier’s fighting capabilities now and in the future. USCECOM develops and integrates the critical technologies required to provide a speedy transition from research labs to the field, ensuring the long-term superiority of the U.S. Army and our Host Nation partners in the areas of communications, integrated logistics support, border security, information warfare and intelligence systems. | No VCRM input required | No VCRM input required |
| 1.1. | BACKGROUND | With the growing demand for various services and bandwidth on RJAF FOWAN nodes and simultaneous decrease in capital budgets, the onus is now on RJAF to use their existing fiber optic networks to satisfy the current and future military needs especially the high bandwidth services for the security agencies and other departments. RJAF is currently having Synchronous Transport Module, level 16 (STM-16) optical lines with few STM-64 optical lines, therefore, RJAF is looking to install a new transmission node (platform) that meets the expansion needs by providing protection and performance monitoring while supporting a flexible and transparent mix of traffic protocols including Internet Protocol (IP), Fiber Channel, Ethernet, synchronous digital hierarchy (SDH).... etc. | No VCRM input required | No VCRM input required |
| 1.1. | BACKGROUND | The sites (nodes) identified in Figure 1, are the basis of this effort. This network topology is suggested as “phase 1” upgrading the sites (nodes) shown in Annex D, which are considered the milestone for upgrading based on RJAF required traffic, fiber cable tests with the information about the fiber routes as shown in Annex A and Annex B respectively. The allocated budgets taking into account an optical margin between (5-7 dB) shall be added for each link based on the laser source and power meter test set results shown in Annex A. | ||
| 1.2. | APPLICABILITY | This effort is within the scope and adherence to the basic contract. | No VCRM input required | No VCRM input required |
| 1.3. | PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE | The period of performance (POP) shall not exceed eighteen (18) months from the date of contract award. | ||
| 1.3. | PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE | All equipment/material procurements, deliveries, installation, integration, testing, training, and final system acceptance shall be accomplished within this contract’s period of performance. | ||
| 1.3. | PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE | The performance for CONUS activities will take place at Contractor provided facilities. | ||
| 1.3. | PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE | Delivery, installation, integration, testing, training, and final system acceptance will be at various Contractor and/or End User identified locations within the Kingdom of Jordan as required to execute this contract and with approval of the government client. | ||
| 1.3. | PERIOD OF PERFORMANCE / PLACE OF PERFORMANCE | The final destination point will be the Royal Hashemite Kingdom of Jordan. | ||
| 1.4. | CONTRACT MANAGEMENT | Contractor shall designate a single Point of Contact (POC) / Project Manager (PM) for the execution of the work efforts. | ||
| 1.5. | GOVERNMENT FURNISHED EQUIPMENT (GFE) / MATERIALS / FACILITIES | The End User will be responsible for providing Contractors with the necessary in-Kingdom storage facilities (non-environmentally controlled warehouse); however, the Contractor shall be responsible for its own business and personnel facility requirements. | ||
| 1.5. | GOVERNMENT FURNISHED EQUIPMENT (GFE) / MATERIALS / FACILITIES | Pursuant to the Letter of Offer and Acceptance (LOA), JO-B-YFG, JAF will be responsible for: |
· Clearing items delivered thru Customs and exempting the taxes and custom fees imposed inside Jordan.
· Providing adequate security to protect Contractor personnel and property associated with this effort when located on purchaser military bases and military sites. JAF will be responsible to ensure the general physical security of a location while Contractor personnel and/or equipment are present. JAF is not responsible for providing the aforementioned security outside of JAF/RJAF premises.
· Providing Contractors reasonable access to all End User sites necessary to fulfill the requirements of this effort, to include any necessary facility upgrades at installation sites to allow for equipment installation.
· Optical distribution frames (ODFs) will be provided by RJAF.
| 1.6. | PROCUREMENT CONTRACTING OFFICER | The Army Contracting Command- Aberdeen Proving Ground (ACC-APG) Procurement Contracting Officer (PCO) is the single point of contact within the Government for funds, program direction or changes. Only the PCO can approve or direct changes or additions to the contract. | No VCRM input required | No VCRM input required |
| 2. | APPLICABLE DOCUMENTS | The following documents form a part of this PWS to the extent specified herein. The most recent revision of the referenced document at the time of contract award shall be used unless otherwise specified. In the event of conflict between the applicable documents and this PWS, the PWS shall take precedence. Nothing in this PWS supersedes applicable laws and regulations unless a specific exemption has been obtained. Military and Federal standards, performance specifications, and handbooks may be obtained from the Document Automation and Production Service, Building 4/D, 700 Robbins Avenue, Philadelphia, PA 19111-5094 or visit https://assist.dla.mil/online/start/. | ||
| 2.1. | MILITARY STANDARDS | AR 25-2 Information Management, Information Assurance |
AR 190-13 The Army Physical Security Program AR 380-10 Foreign Disclosure and Contacts with Foreign Representatives AR 381-12 Threat Awareness and Reporting Program AR 525-13 Antiterrorism AR 525-28 Personnel Recovery AR 530-1 Operations Security MIL-STD-129R Military Marking for Shipment and Storage MIL-STD-130N Identification Marking of U.S. Military Property MIL-STD-882E System Safety
| MIL-STD-2073-1 Standard Practice for Military Packaging | No VCRM input required | No VCRM input required | |
| 2.2. | COMMERCIAL STANDARDS | ISPM 15 Regulation of Wood Packaging Material for International Trade |
ASTM D 3951-18 Standard Practice for Commercial Packaging ANSI/ASQ-9001 Quality Assurance Program Motorola R56 Standards and Guidelines for Communications Sites ETS 300 119-X European Telecommunication Standard for Equipment Practice
| ANSI/TIA 606-D Cable Labeling Standards | No VCRM input required | No VCRM input required | |
| 2.3. | OTHER DOD DOCUMENTS | SRD System Requirements Document for Royal Jordanian Air Force Fiber Optic Wide Area Network Transmission Node Upgrades |
Annex A Fiber Tests Using FLS and FPM Test Set Annex B OTDR Test Equipment Annex C Client Interfaces – General Traffic and Details Annex D Upgrading RJAF Transmission Nodes (JBSP) Annex E Standards to be Supported
| Annex F Acronyms | No VCRM input required | No VCRM input required | |||
| 3. | REQUIREMENTS | Not Applicable | No VCRM input required | No VCRM input required | |
| 3.1. | RJAF FOWAN TRANSMISSION NODE UPGRADES | The Contractor shall provide a complete solution which meets the FOWAN Transmission Node Upgrade requirements as defined in this PWS, associated SRD and Annexes. | |||
| 3.1. | RJAF FOWAN TRANSMISSION NODE UPGRADES | The Contractor shall provide materials, articles, supplies, equipment, including any hardware and software necessary, and services to fully meet the FOWAN Transmission Node Upgrade project objectives. | |||
| 3.1. | RJAF FOWAN TRANSMISSION NODE UPGRADES | The Contractor shall provide program and engineering management, systems engineering, design, installation, integration, material procurement or manufacture (as necessary), testing, documentation, training, sustainment and integrated logistics support (ILS) services. | |||
| 3.1. | RJAF FOWAN TRANSMISSION NODE UPGRADES | The Contractor’s solution, including all equipment, software and services, must be exportable to Jordan. | |||
| 3.1. | RJAF FOWAN TRANSMISSION NODE UPGRADES | The Contractor shall also provide maintenance support and transferable Original Equipment Manufacturer (OEM) commercial warranties, all as applicable. | |||
| 3.1. | RJAF FOWAN TRANSMISSION NODE UPGRADES | The Contractor shall be responsible for the overall system design, installation, commissioning, and treat this effort as a turnkey project. | |||
| 3.1.1. | General Technical Requirements | The Contractor shall perform survey, design, installation, configuration, integration, testing & commissioning of all Systems, including Network Management System (NMS), supplied under this Contract in accordance with (IAW) the respective manufacturer’s guidelines and recommendations and applicable standards referenced in Para 2. | |||
| 3.1.1. | General Technical Requirements | The Contractor shall perform all necessary design and engineering of the proposed transmission node (platform) meeting the traffic requirements ensuring seamless performance. Such design and engineering details must be submitted for USG and/or JAF approval as high-level & low-level designs, including NMS and integration plan, and all other relevant documents based upon the details specified in the technical specifications and traffic requirements. | |||
| 3.1.1. | General Technical Requirements | As part of the network design, the Contractor shall be responsible for defining the transmission node connectivity and wavelength plan to meet the traffic requirements based on the upgrade scenario as defined herein. | |||
| 3.1.1. | General Technical Requirements | The Contractor shall provide all materials and equipment necessary to meet the requirements of this PWS. | |||
| 3.1.1. | General Technical Requirements | When required, the Contractor shall use its own test and installation equipment. | |||
| 3.1.1. | General Technical Requirements | Any purchased materials under this contract shall become the property of the Jordanian Government upon delivery, installation, and acceptance, and shall be fully accounted for, maintained, and serviceable when accepted by the Jordanian Government. | |||
| 3.1.1. | General Technical Requirements | All material shall be new. | |||
| 3.1.1. | General Technical Requirements | All commercial material warranties that run with incidental items purchased shall be submitted to the Government for review. | |||
| 3.1.1. | General Technical Requirements | The prime Contractor will be responsible for enforcing any commercial warranties during the period of performance of this contract and transfer any commercial warranties that exceeds POP to the End User. Only material required to support the services of this contract will be acquired by the Contractor. | |||
| 3.1.1. | General Technical Requirements | The Contractor shall be fully responsible for installation, configuration, testing and commissioning of the supplied new transmission node equipment (platform) in line with the low- level design. | |||
| 3.1.1. | General Technical Requirements | Upon successful completion of installation and equipment testing, the Contractor guarantees the interoperability between the old RJAF Ericsson nodes (network) and the new nodes (new network) so the old network can work transparently within the new network. | |||
| 3.1.1. | General Technical Requirements | The Contractor shall shift traffic, as detailed in Interoperability paragraph below, from the existing RJAF nodes to the newly installed equipment with minimum Service disturbance and confirm the interoperability between the old nodes and the new one. | |||
| 3.1.1. | General Technical Requirements | This traffic migration shall be carried out by the Contractor upon receiving the approval from the RJAF to the Contractor proposed migration plan. | |||
| 3.1.1. | General Technical Requirements | Throughout project execution, the Contractor shall minimize downtime and negative impact to network traffic on existing or new data links. | |||
| 3.1.1.1. | Requirement Verification Events | The Contractor shall develop Test Plan & Procedures (TPPs) and a Test Report for each Verification event in accordance with the respective CDRL, DD Form 1423, Data Item E001, DI-QCIC-80553A, Acceptance Test Plan and Procedures and CDRL, DD Form 1423, Data Item E002, DI-NDTI-80809B, Test/Inspection Reports. | |||
| 3.1.1.1. | Requirement Verification Events | There will be multiple elements of testing and verification to mitigate project risks. Below are the required elements expected from the Contractor. All testing equipment required for declaring the system Ready for Service (RFS) are the responsibility of the Contractor. | |||
| 3.1.1.1. | Requirement Verification Events [FAT] | · Factory Acceptance Test (FAT): | No VCRM input required | No VCRM input required | |
| 3.1.1.1. | Requirement Verification Events [FAT] | The Contractor shall develop and perform a detailed CONUS Factory Acceptance Test (FAT) in accordance with CDRL, DD Form 1423, Data Item E001, DI-QCIC-80553A, Acceptance Test Plan and Procedures. | |||
| 3.1.1.1. | Requirement Verification Events [FAT] | The FAT shall focus on a slice of the Contractor’s solution, demonstrating how the system will be used to meet the requirements. | |||
| 3.1.1.1. | Requirement Verification Events [FAT] | Testing results shall be documented and reported in accordance with CDRL, DD Form 1423, Data Item E002, DI-NDTI-80809B, Test/Inspection Reports. | |||
| 3.1.1.1. | Requirement Verification Events [FAT] | The Contractor will support JAF and USG attendees. The Contractor is not responsible for JAF and/or USG participant travel expenses. | |||
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | · Site Inspection & Acceptance: | No VCRM input required | No VCRM input required | |
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | The Contractor shall provide Certificates of Completion (CoC) for each site at the conclusion of installation and functional test. | |||
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | Functional testing shall be performed in accordance with a Contractor developed CDRL, DD Form 1423, Data Item E001, DI-QCIC-80553A, Acceptance Test Plan and Procedures. | |||
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | The Contractor shall provide CoC’s that encompasses how they will validate objective tasks , validate the work they performed was successful, and define a successful completion criteria per site. A checklist may be used as appropriate. | |||
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | CoC events will be conducted in Jordan and witnessed by the appropriate JAF and USG representatives, and those representatives will sign off on the CoC upon successful completion. | |||
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | The CoC document shall contain signature blocks for JAF and USG representatives to sign. | |||
| 3.1.1.1. | Requirement Verification Events [SITE I&A] | CoCs shall be submitted at site acceptance in accordance with CDRL G002; Certificate of Completion, DI-MISC-81356A. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | · System Acceptance Test (SAT): | No VCRM input required | No VCRM input required | |
| 3.1.1.1. | Requirement Verification Events [SAT] | Upon completion of system installation and site inspection & acceptance, the Contractor shall conduct a fully functional SAT of the operational system. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | Per the Contractor developed Test Plan & Procedures (TPP) in accordance with CDRL, DD Form 1423, Data Item E001, DI-QCIC-80553A, Acceptance Test Plan and Procedures, the Contractor shall perform the appropriate activities to allow the USG/JAF to verify all the system requirements have been met. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | The Contractor shall develop a detailed Acceptance Test Plan. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | The OCONUS System Acceptance Test (SAT) will be conducted in Jordan. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | This Acceptance Test Plan shall address the requirements specified in this PWS and SRD. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | Upon Government approval, the Acceptance Test Plan shall be the basis for approving all work accomplished under this contract. | |||
| 3.1.1.1. | Requirement Verification Events [SAT] | Testing results shall be documented and reported in accordance with CDRL, DD Form 1423, Data Item E002, DI-NDTI-80809B, Test/Inspection Reports. | |||
| 3.1.1.1. | Requirement Verification Events | All requirements shall be verified using the verification methods defined in the Verification Cross Reference Matrix (VCRM). The VCRM documents the incremental approach to verifying all PWS and SRD requirements. | |||
| 3.1.1.1. | Requirement Verification Events | Requirements identified as being verified by testing will be allocated to one of the three (3) test events (CONUS FAT, Site Acceptance and OCONUS SAT) which shall be recorded in the VCRM. | |||
| 3.1.1.1. | Requirement Verification Events | In the event a requirement is not fully verified at the specified verification event (i.e., solution does not comply with the requirement), the Contractor shall include within the Test Report the appropriate remediation steps, including regression procedures, necessary to fully verify the requirement. | |||
| 3.1.1.1. | Requirement Verification Events | Furthermore, any requirement may be subject to be re-verified at a future verification event based upon implicit dependencies with other requirements and test procedures. | |||
| 3.1.1.1. | Requirement Verification Events | Full System Acceptance (FSA) shall be accomplished only upon successful completion of all test activities (e.g., FAT, Site Acceptance, SAT, FAT/SAT regression testing, and USG-approval on contractor-submitted SAT Test Report CDRL). | |||
| 3.1.1.2. | System Design Description / As-Built Drawings | The Contractor shall develop and maintain a System/Subsystem Design Description (SSDD) to include detailed description of system architecture design and “As Built” drawings for all installations in accordance with CDRL, DD Form 1423, Data Item D001, DI-IPSC-81432A, System/Subsystem Design Description. | |||
| 3.1.1.2. | System Design Description / As-Built Drawings | These drawings will reflect each site/link/hardware configuration. This document and drawings are intended to be provided to host country maintenance and operator personnel to verify connectivity and to assist with any future troubleshooting, upgrading, or system modifications. | |||
| 3.1.1.2. | System Design Description / As-Built Drawings | The Low-Level Design documents must document the following: |
a) Equipment details, including name of the Site, equipment name, rack no., floor plan layout, power consumption, and IP address.
b) System assembly for each Site.
c) Inter-rack and wiring diagram (fiber patch cord, electrical/power and grounding).
d) Equipment Connectivity diagram.
e) NMS Servers and Workstations connectivity drawing with proposed IP address.
f) Optical results and calculations.
g) Topology for data communication network (DCN).
| 3.1.1.2. | System Design Description / As-Built Drawings | The As Built drawings shall be submitted after completion of site installation and test, prior to issuance of the CoC. | ||
| 3.1.1.2. | System Design Description / As-Built Drawings | The As Built drawings shall be submitted in both hard copies and electronic format. | ||
| 3.1.1.2. | System Design Description / As-Built Drawings | Electronic drawings shall be in pdf and MS Visio format. | ||
| 3.1.1.3. | Software Version Description | The Contractor shall develop and maintain a Software Version Description Document (VDD) for each delivered software in accordance with CDRL, DD Form 1423, Data Item D002, DI-IPSC-81442A, Software Version Description. | ||
| 3.1.1.4. | Interoperability | The Contractor shall develop and maintain an Interface Control Document (ICD) in accordance with CDRL, DD Form 1423, Data Item B002, DI-SESS-81248B, Interface Control Document describing the interfaces and relationship between components of the new transmission node (platform) in terms of data items and messages passed; protocols observed; and the timing and sequencing of events from the lowest mechanical and electrical elements to the highest logical levels of the system. This is to ensure current and future interoperability. | ||
| 3.1.1.4. | Interoperability | The Contractor shall preserve and ensure interoperability with existing connections/interfaces as documented in Annex C to other systems and subsystems. | ||
| 3.1.1.4. | Interoperability | The ICD shall define each input and output of all critical (platform) elements (e.g., sites, end nodes, etc.) and document how each interface can be utilized to expand the system and its subsystems. | ||
| 3.1.1.4. | Interoperability | The ICD shall be detailed enough for the USG or another party to determine how to add future inputs/outputs and allow for the ability to determine what data inputs can be accepted by the proposed (platform) and to determine what data outputs are available for export to new or external software/C2 systems. | ||
| 3.1.1.4. | Interoperability | The End User will have all rights and privileges for using the ICD as it sees fit. | ||
| 3.1.2. | General Program Execution Requirements | The project consists of the design, procurement, fielding, training and maintenance of the system for the End User. The Contractor shall manage the project in accordance with the requirements described below. | ||
| 3.1.2.1. | Contractor General Requirements | Not Applicable | No VCRM input required | No VCRM input required |
| 3.1.2.1.1. | Facilities | The Contractor shall be responsible for its own CONUS and OCONUS business and personnel facility requirements. | ||
| 3.1.2.1.2. | Work Schedule | Contractors located in Jordan will be expected to work the Jordanian work week (Sunday to Thursday) and Jordanian normal business work hours (0800-1700) local time. In some instances, the Contractor or Sub-Contractor may be required to work after normal work hours and on the weekends to resolve issues or meet program milestones. | ||
| 3.1.2.1.2. | Work Schedule | The Contractor shall consider Jordanian holidays when scheduling and performing tasks. | ||
| 3.1.2.1.2. | Work Schedule | The Contractor shall coordinate all work activities with JAF and/or the USCECOM SAMD PMO. | ||
| 3.1.2.1.3. | Past Experience, Qualifications and Personnel | The Contractor shall provide a qualified work team throughout the contract POP to guarantee fulfillment of all of the tasks identified in this PWS, within cost and schedule. | ||
| 3.1.2.1.3. | Past Experience, Qualifications and Personnel | The Contractor and/or subcontractor shall meet the following: |
a) Have at least five (5) years experience working projects in the field of optical networks.
b) Be well established and have efficient, reliable and local (Jordan) technical staff capable of supporting and supervising during the installation, commissioning, warranty and maintenance support period.
c) Provide on-site support during the installation by an expert from the OEM and local company.
d) Provide an authorized letter that shows it represents the main equipment OEM inside Jordan and they are authorized resellers of the equipment.
e) Provide documentation showing their installation technicians are OEM certified for the proposed hardware and software configuration of the systems.
| 3.1.2.2. | Program Management Requirements | Not Applicable | No VCRM input required | No VCRM input required |
| 3.1.2.2.1. | Integrated Master Schedule | The Contractor shall develop an Integrated Master Schedule (IMS) in accordance with CDRL, DD Form 1423, Data Item A001, DI-MGMT-81861C, Integrated Master Schedule. | ||
| 3.1.2.2.1. | Integrated Master Schedule | At a minimum, the Contractor-developed IMS shall include all critical milestone dates, shipping durations, installation activities, and government-furnished equipment/information (GFE/GFI) dates. | ||
| 3.1.2.2.2. | Program Milestone Events | The Contractor’s implementation program shall consist of the following milestone events (milestone dates will be based on Contractor’s proposal): | ||
| 3.1.2.2.2. | Program Milestone Events [PAC] | · Post Award Conference: | No VCRM input required | No VCRM input required |
| 3.1.2.2.2. | Program Milestone Events [PAC] | The Contractor shall host a PAC via teleconference for the Government within thirty (30) calendar days after contract award. | ||
| 3.1.2.2.2. | Program Milestone Events [PAC] | The Contractor will prepare PAC presentation material and supporting documentation in accordance with CDRL, DD Form 1423, Data Item C002, DI-ADMN-81250C, Reports, Records of Meetings/Minutes. | ||
| 3.1.2.2.2. | Program Milestone Events [TIM/SRR] | · Technical Interchange Meeting (TIM)/System Requirements Review (SRR): | No VCRM input required | No VCRM input required |
| 3.1.2.2.2. | Program Milestone Events [TIM/SRR] | The Contractor shall hold an OCONUS TIM/SRR within ninety (90) calendar days of after contract award. | ||
| 3.1.2.2.2. | Program Milestone Events [TIM/SRR] | The Contractor will prepare TIM/SRR presentation material and supporting documentation in accordance with CDRL, DD Form 1423, Data Item C002, DI-ADMN-81250C, Reports, Records of Meetings/Minutes. | ||
| 3.1.2.2.2. | Program Milestone Events [CDR] | · Critical Design Review (CDR): | No VCRM input required | No VCRM input required |
| 3.1.2.2.2. | Program Milestone Events [CDR] | The Contractor shall hold a CDR at the Contractor’s CONUS facility within six (6) months after contract award. | ||
| 3.1.2.2.2. | Program Milestone Events [CDR] | The Contractor will prepare CDR presentation material and supporting documentation in accordance with CDRL, DD Form 1423, Data Item C002, DI-ADMN-81250C, Reports, Records of Meetings/Minutes. | ||
| 3.1.2.2.2. | Program Milestone Events [CDR] | The CDR will consist of the Contractor’s final technical design and implementation approach including non-technical aspects of the project like schedule, budget, training plans and materials, and sustainment support details. | ||
| 3.1.2.2.2. | Program Milestone Events [CDR] | The Contractor will support JAF and USG attendees. The Contractor is not responsible for JAF and/or USG participant travel expenses. | ||
| 3.1.2.2.2. | Program Milestone Events | The Contractor shall order all equipment only after formal completion of the CDR. | ||
| 3.1.2.2.2. | Program Milestone Events | At the PAC or TIM/SRR, the Contractor may request USG approval to order major long-lead items prior to the CDR. | ||
| 3.1.2.2.2. | Program Milestone Events | The Contractor shall include in their proposal any dependencies between the Contractor’s proposed Integrated Master Schedule and long-lead item procurement. | ||
| 3.1.2.2.3. | Meeting Agendas and Minutes | The Contractor shall provide an agenda and briefing materials for all meetings, reviews, conferences, and teleconferences in accordance with CDRL, DD Form 1423, Data Item C001, DI-ADMN-81249B, Meeting Agendas. | ||
| 3.1.2.2.3. | Meeting Agendas and Minutes | The Contractor shall be responsible for developing meeting minutes of all meetings, reviews, conferences, teleconferences, milestone and requirements verification events in accordance with CDRL, DD Form 1423, Data Item C002, DI-ADMN-81250C, Reports, Records of Meetings/Minutes. | ||
| 3.1.2.2.4. | Site Survey / Facilities Requirement Document | The Contractor shall conduct site survey of the twenty-five (25) sites and two (2) NMS locations and develop a site survey report and Facilities Requirement Document (FRD) in accordance with CDRL, DD Form 1423, Data Item G001, DI-MISC-80508B, Technical Report – Study/Services. | ||
| 3.1.2.2.4. | Site Survey / Facilities Requirement Document | The FRD, at a minimum, shall include detailed requirements necessary for the End User to prepare sites for the Contractor-provided equipment installation (i.e., responsibility matrix) and also define the timeline for JAF to implement any FRD needs. | ||
| 3.1.2.2.4. | Site Survey / Facilities Requirement Document | The Contractor may perform fiber testing to confirm network performance parameters; this should be done before the project installation. | ||
| 3.1.2.2.5. | Contract Performance Reporting | The Contractor shall continuously monitor the cost/schedule/technical performance/risk of the contract, and all subcontracts, and deliver to the Government a Monthly Status Report (MSR) IAW CDRL, DD Form 1423, Data Item A002, DI-MGMT-80368A, Status Report. | ||
| 3.1.2.2.5. | Contract Performance Reporting | The Contractor shall conduct regular status meetings such as weekly project teleconferences, program management reviews, as well as participate in various joint working groups, technical interchanges and meetings of project stakeholders. | ||
| 3.1.2.2.6. | Quality Assurance | The Contractor shall implement, operate, and maintain a quality assurance (QA) program that meets or exceeds commercial best practices and is acceptable to the Government. | ||
| 3.1.2.2.6. | Quality Assurance | Any civil works required under this contract shall be in accordance with current Jordanian Ministry of Public Works standards and the SRD. | ||
| 3.1.2.2.7. | Configuration Management | The Contractor shall develop, implement, and maintain a Configuration Management (CM) Plan acceptable to the Government and in accordance with CDRL, DD Form 1423, Data Item B003, DI-SESS-80858C, Contractor’s Configuration Management Plan addressing all hardware, software, and system documentation. | ||
| 3.1.2.2.7. | Configuration Management | A baseline shall be established and subsequent changes captured throughout the contract. | ||
| 3.1.2.2.8. | System Safety | The Contractor shall identify and evaluate system safety and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards associated with contractual tasks. | ||
| 3.1.2.2.8. | System Safety | The Contractors shall develop a System Safety Plan (SSP) in accordance with CDRL, DD Form 1423, Data Item H001, DI-SAFT-81626, System Safety Program Plan. | ||
| 3.1.2.2.9. | Sensitive Information Control | The Contractor shall be responsible for safeguarding Jordan sensitive materials and information throughout the contract POP. Distribution of information or contract requirements beyond Official Government channels is not authorized without the express consent of the Government of the Hashemite Kingdom of Jordan and the PCO. | ||
| 3.1.2.2.9. | Sensitive Information Control | All requests for release of information shall be in writing and forwarded to the PCO or USCECOM SAMD PMO for approval. | ||
| 3.1.2.2.9. | Sensitive Information Control | The Contractor and subcontractor(s) shall sign non-disclosure agreement(s) (NDA) as required by JAF upon contract award. | ||
| 3.1.2.2.9. | Sensitive Information Control | Any/all data related to this effort shall be returned to the Government or appropriately destroyed at the conclusion of this effort or upon request of the Government. | ||
| 3.1.2.2.10. | Inventory Management | The Contractor shall develop, maintain and provide a master equipment list (MEL) / bill of materials (BOM) acceptable to the Government in accordance with CDRL, DD Form 1423, Data Item A006, DI-MGMT-81994B, Priced Bill of Materials for the purpose of material kitting, custody transfer and inventory tracking. | ||
| 3.1.2.2.10. | Inventory Management | The BOM shall list all equipment purchased under the contract and include detailed information, including but not limited to part number, serial number, manufacturer, quantity, spare quantity, unit cost, purchase order, date purchased, location, and status. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor shall develop and provide a training program to End User personnel covering the necessary system knowledge such that they can operate and maintain all aspects of the system and in turn train other operators and maintainers (i.e., Train-the-Trainer (T3)). | ||
| 3.1.2.3. | End User Training Requirements | System knowledge includes, but is not limited to fiber optic equipment, telecom transport technologies (i.e. OTN, MPLS-TP, Ethernet, etc.), network management system, interfaces into the legacy system, and troubleshooting. | No VCRM input required | No VCRM input required |
| 3.1.2.3. | End User Training Requirements | Two (2) training iterations shall be provided. | ||
| 3.1.2.3. | End User Training Requirements | Each training iteration shall be two (2) weeks in duration for ten (10) students in the following subjects: |
A. System Deployment, Commissioning, Operation, and Data/Optical Service Creation and Provision.
B. NMS & Network Administration, Maintenance, Optimization and Troubleshooting.
| 3.1.2.3. | End User Training Requirements | The Contractor shall develop and provide full training plans and training material in accordance with CDRL, DD Form 1423, Data Item F001, DI-ILSS-80872, Training Materials. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor shall provide a syllabus that, at a minimum, describes the training courses, course outlines, schedule and identifies student prerequisites. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor shall prepare and deliver to the USG for review Operator and Administration & Maintenance technical manuals which include all topics addressed in the training course. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor shall revise these manuals to incorporate any End User and/or Government changes. | ||
| 3.1.2.3. | End User Training Requirements | All hardcopy and softcopy manuals for the new system platform, including the NMS, must be provided. | ||
| 3.1.2.3. | End User Training Requirements | All Contractor conducted training and training materials shall be in English. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor shall conduct the training using a combination of formal classroom instruction and hands-on interaction with equipment that is deliverable under this project. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor shall conduct training at the Contractor’s and/or authorized subcontractor’s CONUS facility. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor is not responsible for the costs of student airfare, lodging, and meals/incidentals. | ||
| 3.1.2.3. | End User Training Requirements | The Contractor is responsible for basic student management and life support afforded international students attending training on a USG installation to include travel arrangements, lodging arrangement, dining facilities, daily transportation between student quarters, training facility, dining facility, student reporting, medical support, and general administration. | ||
| 3.1.2.3.1. | On the Job Training (OJT) | The Contractor shall provide hands on, On the Job Training (OJT) in Jordan. | ||
| 3.1.2.3.1. | On the Job Training (OJT) | The OJT shall consist of an onboarding/training session focused on the management of the network locally in Jordan for at least three (3) working days. | ||
| 3.1.2.3.1. | On the Job Training (OJT) | In addition, the Contractor shall provide additional OJT to the End User during system installation, configuration, testing, and system commissioning events. | ||
| 3.1.2.4. | Integrated Logistics, Lifecycle Sustainment, Maintenance Support and Warranty Requirements | The Contractor shall develop and implement an Integrated Logistics Support (ILS) approach (e.g., maintenance support and supply concept, warranty program, etc.) for the project in accordance with best commercial industry standards. | ||
| 3.1.2.4. | Integrated Logistics, Lifecycle Sustainment, Maintenance Support and Warranty Requirements | The Contractor logistics support shall include, but not be limited to, all material elements and ancillary items necessary for maintaining the system in an operational state of readiness. | ||
| 3.1.2.4. | Integrated Logistics, Lifecycle Sustainment, Maintenance Support and Warranty Requirements | The objective of the logistics support program is to provide to JAF the necessary resources (e.g., information, tools, training, etc.) to fully self-sustain the system beyond the Contractor-required sustainment support. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | During the period of performance, the Contractor shall provide full maintenance support and warranty to cover all materials, workmanship, and software delivered, to include but not limited to the material installed. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | If full system acceptance occurs before the end of the base POP, the Contractor shall provide full maintenance and sustainment support for the remaining duration. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | This maintenance support includes, but is not limited, to fault isolation, repair/replacement and preventative/corrective maintenance services, remote support, on-site support, warranty, software fixes and upgrades. | No VCRM input required | No VCRM input required |
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | Any commercial warranties provided shall be documented in accordance with CDRL, Data Item B001, DI-SESS-81639, Warranty Performance Report. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | The Contractor shall provide copies of all commercial warranties for material/items purchased under this contract. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | The Contractor shall develop a replace or repair program and perform actions needed to ensure that the supported items remain fully capable of being made operational. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | If items are found defective, to include but not limited to equipment or cards, the Contractor shall repair or replace these items within sixty (60) calendar days from date of defect starting upon End User or authorized delegate notifying the Contractor. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | The Contractor shall be responsible for all costs associated with any shipping of materials and equipment under this maintenance support program. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | The Contractor shall be responsible for replenishing any spares used before final system acceptance used so that the full complement of spares are available at the end of this contract’s period of performance. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | A trouble reporting (TR) process may be followed during the contract’s period of performance. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | After the base POP ends, the Contractor shall provide one (1) year of maintenance and sustainment support as described herein. | ||
| 3.1.2.4.1. | Maintenance/Sustainment Support and Warranty | Maintenance and sustainment support shall include, but not limited to: |
A. Twenty-four (24) hours a day, seven (7) days a week help desk support.
B. On-site and Remote Level 1, 2, and 3 support per the definitions below.
C. Software upgrades during this period.
D. Warranty and repair or replace any defective equipment.
E. Execute a full system inspection every six (6) months, with the report of findings submitted IAW CDRL G001 articulating the status of the system starting from FSA.
3.1.2.4.1. Maintenance/Sustainment Support and Warranty The support levels are defined as:
· Level 1 support = Local phone support, 24/7; i.e., RJAF calls local in-country partner
· Level 2 support = Local field support, 24/7; i.e., local in-country partner sends a team into field
| · Level 3 support = OEM technical support, 24/7; i.e, OEM assists local in-country partner | No VCRM input required | No VCRM input required | |||
| 3.1.2.4.2. | Option for Spare Parts | The Contractor shall propose as a separately priced OPTION for spare parts to include critical and recommended items based on Mean Time Between Failure (MTBF). | |||
| 3.1.2.4.2. | Option for Spare Parts | If MTBF information is not available per system items, the Contractor shall propose an equivalent standard to ensure system operational availability. | |||
| 3.1.2.4.2. | Option for Spare Parts | The Contractor shall indicate the MTBF and MTTR figures for each individual module and for each of the units and subunits. | |||
| 3.1.2.4.3. | Option for Maintenance Support and Warranty, Year 2 | The Contractor shall propose as a separately priced OPTION for twelve (12) months of maintenance support and warranty in accordance with the requirements of Para 3.1.2.4.1. | |||
| 3.1.2.4.3. | Option for Maintenance Support and Warranty, Year 2 | This additional support shall start upon the conclusion of the initial one (1) year maintenance support period in the thirteenth month after the base period. | |||
| 3.1.2.5. | Transportation Requirements | The Contractor shall be responsible for packaging all equipment to be shipped; packaging details are in Para 3.1.5. | |||
| 3.1.2.5. | Transportation Requirements | The Contractor shall be responsible for all shipping, transportation and related services for all equipment and material procured under this contract from the Contractor facility or point of origin to Jordan in-Kingdom point of delivery/installation. | |||
| 3.1.2.5. | Transportation Requirements | The Contractor shall be responsible for in-country shipping until Full System Acceptance, including handling movement of materials from port of debarkation (POD) to in-country destination either temporary (ie. storage facility) or permanent (ie. final installation site). | |||
| 3.1.2.5. | Transportation Requirements | The Contractor shall be responsible for maintenance support transportation as defined in Para 3.1.2.4.1 (ie. returning faulty equipment to/from OEM for repair-replace purposes). | |||
| 3.1.2.6. | Requirements for Publications | For all hardware and software procured and delivered under the contract, the Contractor shall provide any applicable commercial documentation and manuals that are normally provided to the Contractor’s English speaking commercial customers. | |||
| 3.1.2.6. | Requirements for Publications | It is preferred that the format for this documentation be provided as a hardcopy and in a digital softcopy format. | |||
| 3.1.3. | Requirements for Item Unique Identification (IUID) | The contractor shall mark all contract deliverables In Accordance With (IAW) DFARS clause 252.211-7003 in Section F of this contract and the following requirements. | |||
| 3.1.3.1. | IUID Marking | Not Applicable | No VCRM input required | No VCRM input required | |
| 3.1.3.1.1. | New Items | The contractor shall provide IUID, or DoD recognized equivalent, for all items delivered with an acquisition cost of $5000 or more and Government serial numbered items. | |||
| 3.1.3.1.1. | New Items | For long term contracts, the Contractor shall implement IUID markings IAW MIL-STD-130N w/Ch1, dated 16 Nov 12 for any item that will exceed the $5,000.00 unit price for any range quantity or contract year. This requirement is effective throughout the life of this contract. | |||
| 3.1.3.1.2. | Repair Items | The contractor shall mark those items as identified by the Government. | |||
| 3.1.3.1.2. | Repair Items | Items received for repair shall be inspected for IUID markings. | |||
| 3.1.3.1.2. | Repair Items | Those items where the marking is damaged or missing the contractor shall mark the equipment. | |||
| 3.1.3.1.2. | Repair Items | When marking requirements are not clearly specified then the contractor shall advise the PCO. | |||
| 3.1.3.1.2. | Repair Items | For previously acquired items where the IUID markings were not required the contractor shall follow the procedures as if the item was a new item. | |||
| 3.1.3.1.3. | Commercial Markings | All other items shall have acceptable commercial markings that meet the guidelines in Department of Defense (DoD) Guide to Uniquely Identifying Items http://www.acq.osd.mil/dpap/pdi/uid/index.html. | |||
| 3.1.3.1.4. | Permanency and Legibility | The IUID marking and identification plates, tags, etching, or labels when used on equipment, parts, assemblies, subassemblies, units, sets, groups, or kits shall be as permanent as the normal life expectancy of the item and be capable of withstanding the environment, test, cleaning, repair, and rebuild procedures specified for the item. | |||
| 3.1.3.1.4. | Permanency and Legibility | Legibility shall be as required and verified for ready readability per MIL-STD-130N w/Ch1, dated 16 Nov 12. | |||
| 3.1.3.1.5. | Deleterious Effect | Marking of items shall be accomplished in a manner that will not adversely affect the life and utility of the item. | |||
| 3.1.3.1.5. | Deleterious Effect | Marking materials creating hazardous conditions shall not be used. | |||
| 3.1.3.1.5. | Deleterious Effect | Placement and choice of the marking shall not create hazardous conditions. | |||
| 3.1.3.1.6. | Mandatory Information Reporting for all items requiring IUID marking | The contractor shall include the National Stock Number (NSN), if the item has a NSN, the Serial Number marked on the item, if a Serial Number is marked on the item, the original part number, the current part number (only if not the same as the original part number), the current part number effective date (only if the current part number is used) and the USARMY as the SERVICE /AGENCY/COMMAND data element in the information reported to the IUID Registry, in addition to the information required to be reported to the IUID Registry by DFARS clause 252.211-7003. | |||
| 3.1.3.1.6. | Mandatory Information Reporting for all items requiring IUID marking | Wide Area Workflow (WAWF) users shall report this mandatory information to the IUID Registry by Direct submission via an X12 Ship Notice/Shipment and Billing Notice (856/857) transaction, an IUID XML transaction, an IUID flat file transaction or a WAWF IUID Material Inspection and Receiving Report/Combo UDF through the Global Exchange (GEX) Service, or manually, via the IUID Web Entry Site at http://www.bpn.gov/iuid. For WAWF users, these methods do not replace the current WAWF interaction, but are performed in addition to it after the shipment has been accepted to provide IUID data that cannot be provided via WAWF. | |||
| 3.1.3.2. | IUID Coding | IUID markings and readability requirements shall comply with MIL-STD-130N w/Ch1, dated 16 Nov 12. | |||
| 3.1.3.2. | IUID Coding | Symbology markings and the order of priority for marking the hardware shall be in accordance with MIL-STD-130N w/Ch1, dated 16 Nov 12. First priority is the 2D data matrix symbol (machine readable) IUID is the minimum requirement when there are severe space limitations. The second priority is the human readable characters. The third priority is the Linear Bar Code. | |||
| 3.1.3.2. | IUID Coding | If the technical data has not specified the marking location, markings shall be located such that they are visible during item use, provided that sufficient space is available, and does not interfere with equipment operations. | |||
| 3.1.3.2. | IUID Coding | If items are not described by Government Product Technical Data (i.e. Commercial Items), the contractor shall maintain diagrams showing placement and description of the IUID marking and applicable installation and processing instructions for government review. | |||
| 3.1.3.2. | IUID Coding | The contractor shall maintain an accurate, current list of IUIDs for all manufactured items on this contract. | |||
| 3.1.3.2. | IUID Coding | Dates of manufacture, substitutions, shop changes, etc. shall be included on this list. | |||
| 3.1.3.2. | IUID Coding | The list shall be available for inspection by the PCO or other Government representative at any time during the life of this contract. | |||
| 3.1.3.2. | IUID Coding | The contractor shall provide this list to the government at the end of the contract. | |||
| 3.1.3.3. | Correction of Noncompliant Equipment and Technical Data | The contractor shall initiate the appropriate configuration control document to correct all affected drawings/specifications which conflict with or omit the marking requirements stipulated above. | |||
| 3.1.3.3. | Correction of Noncompliant Equipment and Technical Data | If configuration control requirements do not apply and the equipment on order is defined by technical data which conflicts with or omits the marking requirements stated above, the contractor shall advise the PCO. | |||
| 3.1.3.3. | Correction of Noncompliant Equipment and Technical Data | Such advice shall list the number of each deficient drawing/specification and a brief description of the deficiency. | |||
| 3.1.3.3. | Correction of Noncompliant Equipment and Technical Data | If the item on order is defined by existing Government technical documentation and such documentation is in conflict with the requirements of this SOW, production of equipment with revised markings shall not proceed until Government approval is received. | |||
| 3.1.3.4. | Pricing of IUID Requirements | All efforts required by this SOW and contract, including, but not limited to, the preparation of ECPs or notification of marking deficiencies, serial number data reporting at end of contract and the actual marking of hardware, will be included in the base contract price. | No VCRM input required | No VCRM input required |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .