Okaloosa County BOCC — October 15, 2013 — OTA_Internal Coordination_Email Comments — reading text

TSA Test Acceptance Lead at the earliest opportunity, but no later than 120 days prior to the requested testing date. Required documentation includes: Page 26 of 39 HSTS04-13-H-CT1161 e Completed Site Survey Data Collection Checklist Any and All Approved Request for Variance (RFV) Basis of Design Report Sample BHS & CBIS Reports for all PGDS required Reports BHS & EDS Network Diagrams and Server Architecture Local Procedures for Fail-Safe, E-Stop, Jam Clearing and IQ Test Conduct Airport/Airline Bag Induction/Hygiene Procedures BHS Specifications Controls Description and/or Description of Operation (if both exist then provide both) Fail-safe and/or E-Stop Zone Drawings BHS Mechanical Plan and Elevation Drawings from Natural Induction Locations to & through the CBIS, CBRA and Make-up Locations with Conveyors labeled Plan View Drawings and Electrical Drawings of the BHS/CBIS with Control Station & Photoeye Locations and labeling. All drawings will be “Approved for Construction” by the Airport and not Pre-Bid or Bid Use Only versions. At least 1 Plan/Overview Drawing that shows the entire CBIS in a single view e Conveyor Motor Manifest to include not less than (Conveyor Name, Phase, Conveyor Type, Degree of Turn, Degree of Incline/Decline, Length, Speed in FPM, Motor HP, Control Type (VFD yes/no), Brake Type, Motor Type, drive Type, FLA Rating). e Installation & Commissioning Phasing Plan Narrative and Phasing Plan Drawings Construction and Testing Schedules provided through weekly and monthly meetings and reports prior to ISAT. All drawings shall be clearly visible and readable when plotted on Arch D Size Stock. All documents shall be submitted electronically (e.g. text documents in MS Word or PDF and drawings in AutoCAD [.dwg] or PDF.) Any system constraints that will prevent compliance with TSA testing and performance criteria must be disclosed in writing to TSA as far in advance as possible to allow for evaluation of applicable waivers. Any restrictions on system availability and accessibility for testing shall be disclosed. Cutover plans including any phasing plans that will affect the TSA Acceptance Test Contractor’s ability to test the full system from ticket counters and curbside inductions (if applicable) through the outbound/sortation system shall also be disclosed to allow for the development of an accurate SSTP. Cutover plans that will result in multiple testing phases shall also be presented to the TSA RDC in writing for review and approval prior to the Test Coordination Meeting and no later than 30 days prior to ISAT. The COUNTY will have the opportunity to review and comment on SSTP in advance of testing. Comments and/or questions should be directed to the TSA RDC and the TSA Site Lead Contractor. 2.5.2. Test Readiness Report (TRR) This pre-ISAT activity is conducted by TSA Site Lead Contractor in coordination with the COUNTY (typically the BHS Contractor.) The purpose of this testing activity is to assure TSA of site readiness for ISAT and is a precursor for TSA authorization for TSA Acceptance Test Contractor to deploy. The COUNTY will be provided TRR data sheets by the TSA Site Lead Page 27 of 39 HSTS04-13-H-CT1161 Contractor. BHS/CBIS configuration and operation shall be in final form intended for bag screening operations. Unless mutually agreed to, changes/improvements to BHS/CBIS between TRR and ISAT are not authorized. The COUNTY must address security and efficiency defects found during TRR and be prepared to implement mutually agreed upon corrective actions prior to ISAT. Required input from the Project Team will include: Functional Testing Documentation: Testing authentication must be clearly reported and show every test with bag ID and declared status on printed EDS FDRS (Field Data Reports) and on the printed Critical Tracking PEC Report (as required in PGDS Section 7.2.14) resulting bag destination. Ledger forms should show test date, type of test, identification of bag destination location, and ID number of the bags arriving at that location. These reports should be organized and indexed in an electronic media/file or loose-leaf binder(s) "Each test shall conclude with an indication of successfully passing the required criteria of BHS specification and testing criteria and if conflict or failure exists, then so indicate with an explanation. = Presentation of completed testing and TRR required documentation to TSA Site Lead not less than 7 business days prior to anticipated Pre-ISAT date is required. System Mixed Bag Test and System Throughput Test Observation: Sufficient numbers of test bags (no less than 100 test bags per EDS) will be utilized to “stress” the BHS/CBIS as would occur during peak operating times. Test bag set profile should be similar to the TSA Acceptance Test Contractor’s test bag profile. « A real-time observation by TSA Site Lead Contractor of a global BHS/CBIS System Mixed Bag Test and System Throughput Test using clear and suspect bags is required. » All EDS equipment must be operational. « All baggage entry points must be utilized. The TSA Site Lead Contractor or Acceptance Testing Contractor performs the TRR. If successful, a Test Readiness Notice is issued to the TSA RDC and the TSA Acceptance Test Contractor for ISAT deployment. If delivered by COB Monday through Wednesday (5:00 p.m. EST), ISAT deployment will occur the following Monday. If delivered any time Thursday through Sunday, ISAT deployment will occur on the second Monday. If changes are made to the system following TRR without prior coordination with TSA, ISAT testing shall be postponed pending submission of documentation for review and evaluation by TSA and its Acceptance Test Contractor (see paragraph 2.5.7) 2.5.3. Logistical Support Needs: The COUNTY shall identify and provide any logistical or support needs that will impact TRR and ISAT testing, to include: any process needed to obtain sufficient baggage tags should the system use IATA baggage tracking mechanisms, pier tags should the system use pier tags, or blank bag tags if the system does not use IATA baggage tracking mechanisms; Quantities of tags needed will be coordinated during the Site Survey Meeting and the SSTP review Meetings " any process needed to obtain sufficient baggage tubs/totes (typically 20 per installed EDS) Page 28 of 39 HSTS04-13-H-CT1161 = any process needed to obtain sufficient bag transportation devices (tugs, totes, carts, etc.) needed to move test articles in and around the CBIS, CBRA, laydown area and sort/claim devices " any process needed to obtain safety training and/or General Contractor access for TSA Acceptance Test Contractor, as required” " any process needed to obtain airport badges/access for TSA Acceptance Test Contractor personnel; and/or personnel escorts. Airport SIDA Badging Process shall not require more than 2 trips of test team personnel to the site, 1 work week maximum duration each, to obtain SIDA badges including fingerprinting, SIDA Training, testing, issuing and pickup. * availability of BHSC and BHS Programmer to operate BHS during ISAT and provide support for ISAT Testing and diagnostic activities (BHS reports, investigations, and explanations to questions from the TSA Acceptance Test Contractor) " provide baggage handling support for testing activities including bag loading, unloading, transport, fault recovery, during ISAT and TRR including movement between test and laydown/storage areas; and «availability of support for delivery and secure and weather protected storage of TSA Acceptance Contractor test bags for ISAT (100 bags per EDS contained in 2 LD3s per 100 bags.) 2.5.4. ISAT Testing: The TSA Acceptance Test Contractor will meet with the COUNTY between 30 and 45 days prior to testing to coordinate the conduct of ISAT testing. The TSA Acceptance Test Lead and the COUNTY will finalize details relating to the scheduling and duration of the testing. (Generally allow one day of travel for ISAT Testing Team in and out; one day for Site Mobilization; one day per EDS Spur Line; one day per System Level Test (Dieback, Mixed Bag Sortation and Throughput; one day for demobilization and cleanup). It is recommended to schedule one to two additional days for unforeseen testing delays or contingences. 2.5.5. Test Results and Reports The Airport shall report corrective actions to be applied and the timeline associated with deficiency corrections. Corrective actions shall address all defects identified in the TRR/TRN (pre-ISAT) or QLR (ISAT). TSA is not obligated to accept or operate a baggage screening system that does not meet the minimum test standards. 2.5.6. 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 85% or greater of its normal (not peak) operational daily load of “checked bags or luggage” for the time period at hand (i.e. not based on future dates of operation). 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 Airport or their authorized representatives shall forward electronic versions of all CBIS Reports required by PGDS Chapter 7, Section 7.2.14. to the TSA Acceptance Testing Contractor. After receipt, review and analysis of at least 21 days of Page 29 of 39 HSTS04-13-H-CT1161 performance data, TSA and their Acceptance Test Contractor will deploy to the site in either the 4" or 5" week of Substantial Live Operations to physically verify closure of open deficiencies, and assess observe system operation against the data reported. The ILDT or their Contractors will also pull and provide the PLC Code for the same PLCs as provided at ISAT start. 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. 2.5.7. Post Commissioning Activities: The TSA Site Lead Contractor will conduct 30-day operational run-in observations of the system following successful ISAT testing. The Airport shall provide the TSA RDC a written response outlining corrective actions that will be taken due to outstanding deficiencies, issues, and action items identified in the Quick Look Report (QLR) and Test Summary Report within two (2) weeks of receipt of the QLR or TSR. For the continued and secure operation of the CBIS, all changes to the BHS system that impact the CBIS operation during and after its initial commissioning must be reviewed, evaluated, and endorsed by TSA before they are implemented by the Airport. The Post-ISAT changes procedure must be provided in accordance with PGDS Appendix D. The procedure is to be followed for all changes to CBIS systems other than those required for normal routine and periodic maintenance/repairs to the BHS system. The Airport responsible for the BHS system shall assemble an information package for submittal to TSA RDC which includes the following minimum information. e Written description of all proposed physical and programming changes to the BHS and CBIS system(s) e Reason for proposed change(s) e Anticipated impact to system operation (e.g. increased throughput, lowered tracking losses, elimination of bag jams) e Drawings showing affected areas e Any potential security, tracking or efficiency impacts, including impacts on TSA manpower or operations e Testing procedures e Proposed date of changes A CBIS Configuration Change Request Form will be provided by TSA. This package shall be delivered to the local TSA FSD who shall review the package. The local TSA FSD shall add any comments