SYSTEM INTEGRATION TESTING FOR ADVANCED TRAFFIC MANAGEMENT SYSTEM WORK - Item No.
Special Provision No. 681F19 September 2007
1. SCOPE
This Special Provision covers the requirements for System Integration Testing (SIT) of all ATMS subsystems associated with the Work.
2. REFERENCES - Not Used
3. DEFINITIONS - Not Used
4. DESIGN AND SUBMISSION REQUIREMENTS
4.1 Submission Requirements
The Contractor shall submit documentation of the Systems Integration Testing Procedures and Systems Integration Testing Report for approval. All documentation shall meet the requirements stipulated elsewhere in the Contract.
The Contractor shall submit a 14-day burn-in test plan to the CA for approval two weeks prior to commencing the 14-day burn-in.
The Contractor shall submit documentation of the successful completion of PIT, POP and Stage 1 of SIT, along with notification of the schedule date of the 14-day burn-in to the Contract Administrator a minimum of five business days prior to scheduled commencement of Stage 2 SIT.
5. MATERIALS - Not Used
6. EQUIPMENT
The Contractor shall provide all test equipment for the System Integration Tests. The Owner will provide 120 volt power at the field cabinets and at the TOC.
7. CONSTRUCTION
7.1 Liability
The Contractor is responsible for the proper and harmonious operation of all subsystems, which the Contractor installs. Where connection to existing subsystems or components of existing subsystems are required, the Contractor is responsible for connection of equipment specified in the Contract and for elementary system integration tests. Such Work will be carried out under the direction of the Contract Administrator.
7.2 STAGE 1
The Contractor shall carry out tests in the following chronological order:
September 2007 Pg. 1 of 4 SSP681F19 a) Complete all equipment and subsystem tests required in the Contract; b) Test each subsystem independently on the communications subsystem; c) Test each subsystem independently through the communications subsystem with the head end control device in the TOC; d) Add subsystems one at a time and monitor the head end performance at the TOC; e) Fail safe testing of all subsystems one at the time and monitor the head end performance at the TOC.
The Contractor shall not be permitted to commence Stage 2 until Stage 1 has been performed and successfully completed and all documentation of the successful completion of PIT, POP and Stage 1 of SIT, along with notification of the schedule date of the 14-day burn-in is provided to the Contract Administrator in accordance with the requirements of this Special Provision. Commencement of Stage 2 will be conditional on the Contract Administrator verifying that PIT, POP and Stage 1 of SIT were successfully completed and the Contractor receiving a written notification of Owner’s readiness to proceed to Stage 2.
7.2.1 Integration Tests Required
The integration tests shall be carried out between the following subsystems: a) Loops in pavement with Controller Units and Controller Cabinets; b) Controller Units with the Communications Subsystem head ended by the data node modules and VDS computer; c) CCTV cameras, pan / tilt units, digital video encoders, and/or controller units with the Communications Subsystem head ended by the digital video decoders, video receiver modules, camera control transmitter (CCT), the video switcher and/or the video display system; d) VMS and VMS Controller Unit with the Communications Subsystem head ended by the data node modules and VMS computer; e) Communications subsystem including all Ethernet switches, modems, node modules, multiplexer/de- multiplexers, digital video encoders/decoders, modulators/demodulators, port servers, transmitters and receivers, and auxiliary equipment with all other exterior subsystems; f) ______g) ______h) ______
System integration testing required for each applicable Contract item is to be carried out as specifically addressed under the heading "SIT" in the testing requirements table for that item.
In addition, the Contractor shall perform the following tests:
Loopback in the Field
For serial communications:
A data test set shall be connected to the appropriate Data Channel Port at the TOC CDIN. At each field modem, isolated channels shall be used for testing the receive data (RD) line shall be looped to the transmit data (TD) line using an appropriate test connector. A random or pseudo- random sequence of data bits shall be transmitted to the field at an asynchronous data rate of 9600 bps. Return data from the field shall be recorded and compared with that transmitted to determine the bit error rate. Data shall be burst and continuous.
The bit error rate shall not exceed 10-7 for each loopback test.
September 2007 Pg. 2 of 4 SSP681F19 Loopback at Central
At the appropriate Data Channel Port at the TOC CDIN the receive data (RD) line shall be looped to the transmit data (TD) line using an appropriate test connector. At each field modem a data test set shall be connected. A random or pseudo- random sequence of data bits shall be transmitted to Central at an asynchronous data rate of 9600 BPS. Return data from Central shall be recorded and compared with that transmitted to determine the bit error rate. Data shall be burst and continuous.
The bit error rate shall not exceed 10-7 for each loopback test.
7.3 STAGE 2
The Contractor shall submit the schedule for this stage to the Contract Administrator 5 Working days before the scheduled start date. The Contract Administrator shall modify the schedule if necessary to avoid conflict with other MTO activities.
The Contractor shall conduct a 14-day burn-in test for all equipment. The burn-in period for all equipment shall begin when all subsystems are added to the system and with the permission of the Contract Administrator. 7.4 Failure of Tests
Where equipment supplied by the Contractor fails during the burn-in period, the Contractor shall restart the test at Day 0 (zero) following appropriate corrective measures. No compensation will be made for repeat testing under these circumstances.
If a utility power failure is proved to be the cause of testing failure, then the Contractor shall restart the Stage 2 test at the day the failure occurred. If a subsystem failure is proved to be the cause of testing failure, then the Contractor shall start the test over at Day 0 (zero).
Where tests or burn-in indicate that an existing subsystem or component is defective, the Contractor shall immediately report the deficiency to the Contract Administrator. The Contract Administrator may assign corrective repairs, retesting and repeat of burn-in to the Contractor, in accordance with Change Order provisions of the MTO General Conditions of Contract.
The Contractor shall be suitably prepared for Stage 2 prior to the Stage 2 start date. Repeated failure of Stage 2 may be considered a major deviation by the Contractor Administrator.
The Contractor shall provide the Contract Administrator with a contact name and phone number(s) for a designated emergency contact person during Stage 2. The emergency contact person shall be accessible 24 hour a day, for each day of Stage 2 testing.
8. QUALITY ASSURANCE - Not Used
9. MEASUREMENT FOR PAYMENT – Not Used
10. BASIS OF PAYMENT
Payment at the Contract price shall be full compensation for all labour, Equipment and Materials required to do the work.
September 2007 Pg. 3 of 4 SSP681F19 Where defects in the performance of the Owner’s existing subsystems or components are found, the existing systems shall be repaired as directed by the Contract Administrator and shall be administered under the Change Order provisions of the MTO General Conditions of Contract.
The Contract price for this item shall not be less than *______% of the total tender value of ATMS items as defined below:
ITEM DESCRIPTION ITEM SPEC. CODE
NOTES TO DESIGNER:
1. Add to or delete from Section 7.2.1 as required.
2. Choose applicable items from Chapter B of the ATMS CDED Manual and any other items as may be requested by the ATMS project manager for filling in Section 10. Fill-in table size is reduced. Add rows as required.
* Fill-in percentage of minimum % of selected items.
WARRANTS: 1. Any Contract where more than one subsystem is constructed. 2. Any Contract where equipment is added to an existing subsystem.
September 2007 Pg. 4 of 4 SSP681F19