Operational Run-In Clause Samples

Operational Run-In. The Run-In period will extend for a minimum of 30 days from the start of substantial operations with cutover of substantial input and output lines. This period of time shall be discussed and agreed to by all parties during the SSTP development process, and reconfirmed at the completion of the ISAT. Substantial Operations shall normally be defined as when the CBIS is processing 80% or greater of its normal (not peak) operational daily load of “checked bags or luggage”. This period shall also be dependent on resolution of deficiencies found during testing and Run-In. Once a week during the Run- In period, the PROJECT SPONSOR or their authorized representatives shall forward electronic versions of all CBIS Reports required by PGDS. to the TSA RMD and Acceptance Test Contractor. After receipt, review and analysis of at least 21 days of performance data, TSA and their Acceptance Test Contractor will deploy to the site to physically verify closure of open deficiencies, and observe system operation against the data reported. During this time, measurements of belt speeds for security tracking zone conveyors will be performed. These Run-In period measurements will be recorded and reported together with similar measurements made during mobilization for ISAT testing. Based on the data analysis and physical observations, a recommendation will be made to TSA via a Test Summary Report (TSR) to end the Run-In period, extend the Run-In period, and/or change the operational status of the CBIS.