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

develop a SSTP based on testing criteria outlined in the TSA PGDS Appendix D. The Draft SSTP will be based on the Airport’s responses to a Site Planning Checklist to be completed >120 days in advance of ISAT. The Final SSTP shall be delivered to the Airport between 60 and 30 days in advance of projected ISAT start-up. The ILDT and TSA Acceptance Testing Contractor will conduct review meetings of the Draft SSTP and Final SSTP per schedule in Table 1, Section 1.3 of this OTA prior to ISAT. Any requests for deviation from the SSTP testing requirements must be delivered in writing through a RFV to the TSA RDC and Acceptance Test Lead prior to this Final SSTP meeting for review and response. Page 22 of 39 HSTS04-13-H-CT1161 The TSA RDC and TSA Acceptance Test Lead will review/evaluate any requests for phased testing (e.g. non-consecutive testing activities requiring multiple TSA Test Team trips). Such requests must be supported by compelling justification and submitted in writing through a RFV to the TSA RDC and TSA Acceptance Test Lead during the design process and well in advance of SSTP development. Programming or mechanical changes made before ISAT (typically during Contractor pre-testing) must be documented and provided to the TSA RDC and TSA Acceptance Testing Contractor. Once a system enters TRR, no variances will be permitted to the testing criteria. 1.3.3. Integrated Site Acceptance Testing (ISAT) Scheduling and Coordination: Construction schedule including the ISAT start date(s) and duration(s) shall be shared with the TSA Site Lead Contractor, TSA RDC, TSA Acceptance Test Lead and TSA Acceptance Test Contractor through weekly and monthly meetings and reports upon submission of the SSTP checklist to ensure all stakeholders maintain schedule awareness. This schedule shall be distributed each time changes are made to the ISAT start date and/or duration. Changes made to the schedule within two weeks of the planned ISAT start date may relieve the TSA of the obligation to begin testing within three business days of the TRR. In this situation, the ISAT start date could depend on TSA’s testing workload and resource allocation. Test Results and Reports: Testing results will be shared in hard copy format with the Airport from the RDC through the local TSA Point of Contact. Test results will identify security, efficiency and safety concerns. There are four (4) possible test outcomes: e Meets PGDS Criteria — The system under test meets CBIS design and PGDS criteria. e Minor Defects Found — The system under test had no security failures and performance deficiencies would not impede system performance and staffing levels. e Major Defects Found — The system under test had no security failures but performance deficiencies would be detrimental to system performance and/or staffing levels. e Fail—The system under test produced security failures and/or deficiencies that would be excessively detrimental to system performance and staffing levels. In the event of a failed ISAT result, TSA reserves the right to defer any subsequent re-tests for a period of at least 30 days. 1.4 INTEGRATION SERVICES 1.4.1. BHS Support The EDS OEM shall assist the COUNTY’s contractor to establish digital and serial communication for the EDS units. Once communication between devices has been established, the EDS OEM shall provide the following support and integration services. « Assist the BHS contractor to obtain efficient EDS operation. « Provide on-site Integration Engineer Support Services to facilitate the entire integration effort with the BHS. « Be available to support system testing and validation conducted by internal or external organizations including the Integrated Site Acceptance Test (ISAT) and pre-ISAT Project testing and throughout the planning phases including the issuance of the ISAT TRN and TRR. Page 23 of 39 HSTS04-13-H-CT1161 " During initial Live Operations Run-In, provide system performance documentation and technical assistance as requested by TSA, TSA Acceptance Testing Contractor and/or the ILDT. 1.4.2. Software and Hardware Following SAT and throughout the integration effort, the EDS OEM shall install and test the required software and hardware to allow for digital and serial communication between the EDS and the BHS PLC if required. Functionality of the EDS BHS interface hardware and software shall be verified by the EDS OEM at the interface box prior to working with the Airport BHS contractor to ensure a proper operating PLC interface and to avoid delays. 15 SYSTEM NETWORKING 1.5.1 Network Infrastructure The EDS OEM shall provide required patch cables and miscellaneous hardware to interface between network patch panel and EDS OEM supplied networking components. 1.5.2 Network Services The EDS OEM shall provide: training for TSA staff; coordination and support for TSA and testing certification; and resources to conduct installation, testing, and initial operational support for networking. No other network may interface with the networked airport screening solution. The implemented assigned network for operation shall be an isolated, stand-alone network. 1.6. TRAINING TSA will provide training for TSA screening staff on the operation of the EDS and ETD equipment. 1.7. MAINTENANCE Upon successful completion of SAT testing for each unit, TSA will maintain and repair the EDS and ETD units throughout their lifecycles. B. COUNTY’s RESPONSIBILITIES with regard to the Project are listed below in sections 2.1 to 2.5 listed below. 2.0 DESIGN The COUNTY will undertake design of a baggage screening system in accordance with the TSA PGDS to meet the needs of the Airport and TSA FSD. The COUNTY shall submit all applicable design requirements to the TSA RDC for review and as further defined in Chapter 2 of PGDS Version 4.1. The COUNTY shall respond to TSA design review comments promptly and in writing prior to the start of the next design phase for the CBIS Project. 2.1 EDS PLACEMENT If applicable, the COUNTY shall ensure that the Project site will be ready to accommodate the installation of the EDS and associated equipment. The COUNTY shall provide adequate protection to the EDS machines and to the airport infrastructure during any and all EDS movements. The COUNTY shall coordinate with the OEM to integrate all activities regarding Page 24 of 39 HSTS04-13-H-CT1161 placement of EDS equipment. The COUNTY shall provide reasonable measures to protect the EDS and ETD equipment from damage in the screening area. 2.1.1 Site Readiness and Storage The COUNTY shall confirm site readiness to receive EDS units to the TSA Site Lead Contractor no later than 10 business days prior to requested delivery date. Site readiness shall address availability of temporary or permanent power; removal of obstacles to the rigging path; and adequacy of physical environmental conditions within the delivery area that meet EDS OEM standards for protecting the EDS units. The COUNTY shall provide secure storage for the EDS units and any ancillary screening equipment if site conditions at the time of delivery do not provide adequate protection. The COUNTY shall provide secure storage space for hardware associated with EDS integration and multiplexing until it can be installed by EDS OEM Integration Support Staff. Failure to meet these minimum requirements may result in reallocation of equipment to other sites, thus affecting the airport’s overall project schedule. 2.1.2 Rigging Services The COUNTY will be responsible for providing rigging path verification, ingress path, and/or structural analysis. If required, the Airport will remove and replace any walls, windows, glass, doors, or other physical barriers in support of rigging activities. 2.2 INSTALLATION SUPPORT 2.2.1 Power Requirements The COUNTY will provide terminations to the EDS for electrical power. The COUNTY will be responsible for providing all infrastructure power requirements including separate metering. If applicable, the COUNTY will design and install all power requirements to terminal locations within the Checked Baggage Resolution Areas and at EDS locations. The COUNTY will provide cabling from terminations to EDS equipment. The COUNTY shall attest to the availability of power supply to adequately support the EDS and associated equipment in accordance with OEM specifications and be liable for damage to this equipment resulting from intentional deviations to accepted power supply conditions. 2.2.2 Commissioning Services The COUNTY will be responsible for obtaining all other infrastructures not mentioned in Section 2.2.1 to support EDS operations and maintenance. 2.3. INTEGRATION SERVICES The COUNTY shall ensure that the BHS Contractor coordinates with EDS OEM in support of integration activities (e.g. installation and testing the required software and hardware to allow for digital and serial communication between the EDS and the BHS PLC) as needed. Terminations to the EDS for BHS PLC communication shall be performed by the COUNTY. 2.4 NETWORKING 2.4.1. Network Infrastructure The COUNTY will design and install all communication conduit, fiber, etc. as required by the EDS OEM’s design criteria for the EDS and EDS networking system, including but not limited Page 25 of 39 HSTS04-13-H-CT1161 to connectivity of Checked Baggage Resolution Areas, TSA network control room, and BHS Control Room as required. Exact parameters will be reviewed at Project start-up by TSA. The COUNTY will provide cabling and network patch panels in TSA control rooms, ETD search areas, and the TSA network room as determined by the network design conducted in conjunction with the COUNTY. The EDS OEM shall provide required patch cables and miscellaneous hardware to interface between network patch panel and EDS OEM-supplied networking components. The COUNTY will provide all electrical outlets to support installation and operation of a fully multiplexed explosive detection system. 2.4.2. Network Services No other network may interface with the networked airport screening solution. The implemented assigned network for operation shall be an isolated, stand-alone network. 2.5. ACCEPTANCE - TESTING SUPPORT The Project schedule shall allow for sufficient time to conduct mandatory testing of the EDS units after installation and integration. The Project schedule shall also factor in minimum lead times for notification of readiness for testing (7 days for SAT; 3 days for TRR; and at least 3 business days for ISAT). The COUNTY shall identify operational windows in time in which testing activities can be accomplished. Testing activities will be scheduled for normal 8-hour business days (Monday-Friday) and should not include holidays. Testing activities shall also be scheduled such that test articles shall not be comingled either physically with Live Passenger Bags on existing or new screening systems or their electronic screening images shall not appear on consoles being used for Live Passenger Bag screening. Use of temporary networks or phased testing to accommodate the separation of Live Bags and Test Articles must be approved in writing through a RFV in advance of TRR/ISAT by the TSA RDC and TSA Acceptance Test Lead. Requests for overtime or multiple shifts are discouraged and will only be considered based on compelling justification. The TSA RDC and TSA Acceptance Test Lead will review/evaluate any requests for phased testing (e.g. non-consecutive testing activities requiring multiple test team trips). Such requests must be in writing supported by compelling justification and submitted to the TSA RDC well in advance of SSTP development. Programming or mechanical changes made before ISAT (typically during Contractor pre-testing or TRR) must be documented and provided to the TSA RDC and Acceptance Test Contractor. 2.5.1 Site Specific Test Plan (SSTP) The COUNTY shall ensure that information needed to develop an accurate SSTP is provided to