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

he/she may have and forward the form to the following email address: OSTCBD@dhs. gov. The TSA will review and analyze the efficacy and impact of these changes to determine if it may be necessary for TSA to re-certify the CBIS system(s). Once the review has been completed, TSA shall notify the local TSA FSD and the Airport with the TSA recommendation and testing requirements for the system changes, Page 30 of 39 HSTS04-13-H-CT1161 APPENDIX C Construction Milestone Schedule Design & Construction Services Milestones [Dates to be included] Project Validated / Notice to Proceed (NTP) Design OTA Awarded Facility Modification OTA Awarded Pre-Design Deliverables Submitted Pre-Design Deliverables Approved Schematic Design Deliverables Submitted Schematic Design Deliverables Approved 30% TSA Design Deliverables Submitted. 30% TSA Design Deliverables Approved 70% TSA Design Deliverables Submitted 70% TSA Design Deliverables Approved 100% TSA Design Deliverables Submitted Final Construction Drawings Approved Facility Modification NTP (if applicable) Facility Modification Progress Meetings (reoccurring) Facility Modification Substantially Complete (if applicable) Site Assessment and Survey Report Submitted Site Installation Plan (SIP) Submitted SIP Approved EDS Delivered and Placed Site Acceptance Test (SAT) Passed Integrated Site Acceptance Test (SAT) Test Readiness Review Complete (if applicable) iSAT Passed (if applicable) EDS Installation/Networking Start EDS Installation/Networking Finish EDS Decommissioned (if applicable) EDS Removal Start (if applicable) EDS Removal Finish (if applicable) Live Bag Screening (LBS) Start Record Dwgs / CAD As-Built Submitted | TSA Final Sign-off of Project Final Invoice Submitted Project Completion Notification Submitted Project Finish / Contract Closeout Page 31 of 39 HSTS04-13-H-CT1161 APPENDIX D, SCHEDULE OF CONSTRUCTION DELIVERABLES The following deliverables are required to be submitted by the COUNTY: Item Submitted To: Frequency or Due Date Design: pre-design, schematic, |} TSA Regional Deployment In accordance with the TSA 30%, 100% to include detailed | Coordinator PGDS. construction cost estimate EDS Delivery Schedule TSA Regional Deployment NLT 30 Days after Coordinator Construction Contract Award Schedule of Values (Design, TSA Regional Deployment Within 30 days after execution Construction, Baggage Coordinator of the TSA Agreement or Handling Contracts) TSA Contracting Officer upon issuing Notice to Proceed to Contractor. To be updated on a monthly basis and submitted with the monthly report. Copies of the Design and” related Construction Contracts and Change Orders TSA Regional Deployment Coordinator TSA Contracting Officer Upon contract award. Change Orders affecting the CBIS Project require advance TSA approval. Monthly Milestone and TSA Regional Deployment By the 10" of each month. Project Status Report Coordinator Electronic submission is TSA Contracting Officer requested if feasible. TSA Site Lead Contractor Quarterly Project Financial TSA Regional Deployment Quarterly upon execution of Statement Coordinator the OTA. TSA Contracting Officer FinanceConfirm@tsa.dhs.gov Summary report of Small Business/Disadvantage Business Enterprises utilization Report TSA Contracting Officer By September 30" each year and upon completion of the Project via email CONSTRUCTION PHASE Mechanical and Electrical TSA Regional Deployment Upon completion by the Shop Drawings Coordinator COUNTY. TSA Site Lead Contractor Close Out Process Close Out Process — Correction of testing deficiencies Close Out Report submitted to TSA Regional Deployment Coordinator and TSA Site Lead Contractor Airport responses within (2) weeks of receipt of QLR and TSR to address noted CBIS Final Copy of PLC program and software disaster recovery TSA Regional Deployment Coordinator No later than 30 days after commissioning of system(s) Page 32 of 39 HSTS04-13-H-CT1161 procedure in electronic format. As Built Drawings in TSA Regional Deployment No later than 30 days after 30- electronic format, .dwg Coordinator day operational run-in period (AutoCAD) or comparable format to include final description of operations; mechanical layouts, including belt speeds in CAD and PDF file format. Overview of drawings of the | TSA Regional Deployment 30 days after 30-day Matrix/Node, Resolution Coordinator operational run-in period Room, OSR Room as applicable. dwg (AutoCAD) or comparable format Final Invoice TSA Regional Deployment No later than 90 days after Coordinator final sign-off of system by TSA CO ' | TSA Deployment Manager, following successful operational run-in period and start of live bag screening POST COMMISSIONING CHANGES CBIS Changes after OSTCBD@dhs.gov See Post Commissioning Commissioning Requirements, Appendix A, paragraph 2.5.7 The Monthly Milestone and Project Report-are to be submitted by the 10" of each month. A draft Monthly report template will be submitted via separate correspondence. The Monthly Milestone and Project Report shall address the following: a. b. = Actual start and/or finish dates for updated/completed activities. Remaining duration, required to complete each activity started, or scheduled to start, but not completed The Project’s progress to include Project Percent Completion; cost incurred and invoiced to date; a forecast the Project completion date and final costs; as well as monthly schedule and budget variances throughout the Project. Percentage for completed and partially completed activities. Any CO approved changes including but not limited to new activities, deleted activities, activity duration changes, and change in logic relationships between activities. Status date for the schedule update. A statement that identifies and describes any current or anticipated delays that includes the following information: identification of the delayed activity by description and activity code; type of delay; cause of the delay; effect of the delay on other activities, milestones, and completion dates; identification of actions needed to avoid or mitigate the delay. Summary of cost incurred and invoiced to date. Page 33 of 39 HSTS04-13-H-CT1161 i. Description of lessons learned j. Construction Schedule in both PDF and “‘live’/usable format to depict the critical path, baseline and actual date information; predecessors/successors and shall be broken down to a minimum of three (3) WBS levels where applicable. The construction schedule will be used for all planned TSA activities (delivery of equipment, scheduling of testing, etc). Page 34 of 39 HSTS04-13-H-CT1161 APPENDIX E STIP DATA REQUIREMENTS FOR CHECKED BAGGAGE SYSTEMS The TSA HQ Office of Information Technology (OIT) and Security Technology Integrated Program (STIP) require STIP-enabled transportation security equipment (TSE) to have specific connections to securely and reliably network the equipment. Multiple parties play a role in this portion of Checked Baggage Inspection System (CBIS) specification and execution. Roles and Responsibilities for Implementing STIP As CBISs are recapitalized or optimized, the project owner’s contractor will provide new telecommunications outlets and cables as needed to support new technology. If a CBIS reconfiguration is initiated as part of a recapitalization/optimization, safety effort, new technology deployment or any other CBIS redesign initiative, the CBIS contractor will be responsible for restoring the previous state of connectivity (“make whole”), including development of the scope of work (SOW). Implementation in the field will occur via the CBIS contractor. A working group, or Integrated Local Design Team (ILDT) must be formed consisting of representatives from the Airport Authority, FSD staff, OSC, OIT and STIP. The group should meet immediately via conference call once it has been determined that a CBIS is going to be recapitalized or optimized. This action will ensure that ALL aspects of the CBIS redesign have been identified and assigned to a specific group for action and funding. The ILDT will organize the working group members, develop, review and approve the SOW. The OIT Field Regional Manager (FRM) shall always be consulted when a CBIS redesign is initiated and will provide the necessary routing information to ensure the checked baggage systems are appropriately cabled to a networked TSA IT cabinet. The IMAC Process The IMAC Process is the mechanism by which TSA OIT will procure and install IT hardware (e.g. network switch) following the IT infrastructure build-out of a CBIS contractor. The OSC Regional Deployment Manager (RDM) shall be responsible for engaging OIT at project initiation and including the respective regional Field Relations Manager (FRM) throughout the construction process. The IMAC process takes between 30 and 45 days and needs to be initiated to complete the following tasks: ¢ Procurement, configuration and shipment of IT hardware e Installation of IT hardware ¢ Patch cabling of checked baggage equipment ¢ Validation of network connectivity for checked baggage equipment e Validations of STIP EM sever registration for checked baggage equipment. Page 35 of 39 HSTS04-13-H-CT1161 It is imperative to engage each team member as early as possible in order to avoid any gaps in IT Services. Specific Design Standards and Requirements Two modular jacks consisting of a flush-mounted telecommunications outlet box plus/minus 10 feet from the equipment are required. Even though one is redundant, both terminations should be connected using Cat5e or Cat6 4-pair 100 ohm unshielded twisted pair (UTP) or screened twisted pair (ScTP) cable and terminated on the patch panel in the closest TSA IT cabinet. The data cable type should be based on the existing conditions at the Checked Baggage Inspection System (CBIS). The purpose of this connectivity is so that TSA HQ can review statistical data over the network from screening equipment for a particular airport and time period without having to go to the site. Installation and/or relocation of Cat5e/Cat6 data cabling will meet or exceed the specifications listed in the TSA Structured Cabling System Guidelines dated July 2012 [Attached]. This document will be provided by the TSA to the ILDT. In addition, the following requirements should be met: > All ETDs and stand-alone EDSs will have 1 “dual telecommunications outlet”. > Itis assumed that when a multiplex server is present, connectivity to TSANet will terminate at the multiplex server cabinet, therefore connectivity to TSANet for each EDS is not required. > All core drilling will support a minimum of 4 “modular jacks”. > All new fiber installations will be multimode fibers, either multimode fiber, either 50/125 ot 62.5/125 micron fibers r 50/125 or 62.5/125 micron fibers, six-strand bundles enclosed in inner duct. > All cabinet installations require 2 110v 20A service. > All cabinet installations will meet the local seismic rating requirements and can be floor/bracket mounted. > All cabling outside of TSA controlled space must be in Rigid Metal Tubing (RMT) conduit. Any deviance will must be approved through existing RFV procedures. > All newly installed and existing data jacks and associated patch panels must comply with TSA’s approved scheme [see provided TSA Structured Cabling System Guidelines dated July 2012]. > Provide TSA completed Data Capture Sheet [Attached] and cable certification paperwork prior to established I-Sat date. Page 36 of 39 HSTS04-13-H-CT1161 Figure 1 illustrates all of the equipment that must be connected to the Main Distribution Frame (MDF)/Intermediate Distribution Frame (IDF) IT cabinet for a stand-alone CBIS configuration. When the EDS are in a stand-alone configuration, each EDS must be connected to the patch panel. Figure 1 STAND-ALONE CBIS CONFIGURATION TSA IT Cabinet (Existing) | CAT Se or er es