Attachment 3H - ATSS ITSS RFQ Attachment ITSS-4 - Statement of Work A0002 Clean.1623193518404.pdf

Attachment ITSS-4

Statement of Work

1.0 Overview

This Statement of Work (SOW) defines the requirements for Integrated Testing Support Services (ITSS). As provided for in Orders issued under this BPA, the Contractor shall provide ITSS, including, but not limited to the following:

a. Program management activities, resource allocation, reporting, scheduling, planning, data management, test coordination and test logistics.

b. All activities that enable test execution.

c. Integrated Site Acceptance Test (ISAT) execution including the execution, assessing and reporting of all acceptance testing activities.

d. Personnel and experience to support the BPA and any subsequent Orders.

e. Coordinating, scheduling, executing, and reporting on ITSS activities.

The Transportation Security Administration (TSA) is charged with the mission of protecting the nation’s transportation systems to ensure freedom of movement for people and commerce. The mission of TSA’s Acquisition Program Management (APM) office is to develop and implement the best procedures and technologies that deter, prevent, and/or render ineffective any attempt to sabotage commerce and transportation. APM’s Test and Evaluation Division (TED) provides test, evaluation and lifecycle matrix support services to APM program offices, TSA field elements and other TSA and Department of Homeland Security (DHS) stakeholders. TED is the primary liaison with DHS Science & Technology (S&T) on Test & Evaluation (T&E) matters, to include T&E policy level coordination. TED is also responsible for the following:

Management of all technical and logistic activities associated with the TSA Systems Integration Facility (TSIF);

Serving as the Independent Operational Test Agent (OTA) for acquisition systems and Investment Review Board (IRB) decisions; and

Developing and maintaining a T&E capability to support all testing within TSA to include acquisition support, Concept of Operations (CONOPS), process development/refinement, and threat mitigation.

Additionally, the TED Director is responsible for executing and maintaining the APM/Component Acquisition Executive (CAE) T&E Policy document, as well as the APM T&E Evaluation Guidebook.

The Acceptance Test and System Assessment (ATSA) Branch is responsible for conducting design reviews for Checked Baggage Inspection Systems (CBIS), drafting policies and procedures for Checked Baggage and Checkpoint designs, evaluating Checked Baggage screening systems, providing Subject Matter Expertise (SME), performing all Factory Acceptance Testing (FAT), Site Acceptance Testing (SAT), Operational Readiness Testing (ORT) and ISAT testing for

Checkpoint and Checked Baggage equipment, and the development, integration and performance of all Test Article tests.

1.1 Applicable Documents and Government Documents

The documents listed below describe the policy and methodology for the conduct of ITSS and other field data collection activities by TSA. Current versions of these documents are available upon request.

A. Department of Homeland Security Directive Number 102-01, Acquisition Management

Directive, with appendices.

B. Department of Homeland Security Directive Number 026-06, Test and Evaluation.

C. TSA Test and Evaluation Policy.

D. DHS Operational Test and Evaluation Acquisition guidelines for Operational Test Agent

Risk Assessment Level of Test (RALOT) Process, DOT&E Procedure 10, Rev. 1, Enclosure (2).

E. Memo: DHS Procedures for Operational Test and Evaluation of Cybersecurity.

F. Transportation Security Administration Management Directive 300.21.

G. Transportation Security Administration Acquisition Reform Act.

H. Transportation Security Administration Test and Evaluation Guidebook.

I. Transportation Security Administration Office of Security Capabilities Test and Evaluation

Process Guide.

J. Transportation Security Administration Office of Security Capabilities Test and Evaluation

Verification, Validation and Accreditation (VV&A) Policy.

K. Transportation Security Administration Office of Security Capabilities Test and Evaluation

Statistical Methodology Policy Memorandum.

L. Transportation Security Administration Office of Security Capabilities Third Party Testing

Strategy.

M. DHS Memorandum, Release of Test and Evaluation Master Plan Guide.

N. Planning Guidelines and Design Standards (PGDS) for Checked Baggage Inspection, most recent version.

1.2 General Requirements

Communication Standards

The Contractor shall promptly (within 1 business day) communicate issues and conflicts that arise during performance of this BPA and its Orders to the TSA Contracting Officer’s Representative (COR), or Technical Monitor (TM) for TSA involvement and resolution.

Key Personnel shall respond to all normal (non-Urgent) emails within twenty-four (24) hours after receipt (excluding weekends and holidays). If an email is marked as “Urgent”, Key Personnel receiving the email shall respond within four (4) hours (including weekends and holidays).

The Contractor shall provide accurate and correct data/responses to TSA’s inquiries at all times.

Data and responses provided by the Contractor shall be free of typographic errors and formatting issues.

Due to the high volume of correspondence and documents anticipated under this BPA and its Orders, the Contractor must have in place standards to facilitate communication, information sharing, and data archiving. A sample list of these standards is provided below:

File Names Structure / Format.

Data Archive Structure (folders and subfolders).

Email Subject and Email Body Structure.

Passwords Structure.

Document formats.

Acronyms/Nomenclature Use.

The Government will provide further details regarding these standards during the kickoff meeting.

Security Clearance and Security Sensitive Information

The BPA and Orders require access to Sensitive Security Information (SSI). All Contractor personnel are required to receive a favorable TSA suitability determination prior to commencing work on the BPA. Contractor personnel shall handle and mark SSI in accordance with applicable TSA requirements.

The TM and/or COR will determine if individual Contractor personnel will require access to classified material and a SECRET clearance. TSA will direct the Contractor to initiate a security clearance investigation based on that determination via a formal notification from the COR.

TSA does not anticipate that the Contractor will be required to handle and store classified information at the Contractor’s facility. TSA will provide access to classified processing and storage facilities to the Contractor on an as needed basis.

Quality Control

The Contractor shall maintain high levels of quality and implement a quality control plan/program to meet all the performance requirements. Orders may include additional performance requirements.

Off Hour Communication

Different tasks completed under this contract may need to be performed after the normal government business hours of Monday through Friday between 8am and 5pm (EST). As a result of work being performed outside of the normal workday communication with the Government shall be coordinated on a case by case basis prior to the test event. For example, if there is a safety issue, personnel injury, or items of a security concern then the TM/COR shall be notified immediately via email, phone, and/or text.

Archiving of Test Data and Reports Data Retention

All test generated data must be retained by the Contractor until the expiration of the BPA. This data shall back up the official TSA database and also house all of the test notes and data sheets.

Upon BPA closeout all test data (reports, test data sheets, analysis data, and all other final testing documents collected or generated) shall be provided to TSA in a format and medium outlined by the TM/COR or CO.

Data Accessibility

Final reports prepared for this BPA and any Orders shall be stored at a location determined by the TM or COR. New Test Reports shall be made available within twenty-four (24) hours after they are approved by the TM or COR.

Data Storage

The following is an overview of the types of data that the Contractor will be excepted to retain and store:

All deliverables of the BPA and Orders.

All test plans, procedures, and reports.

All as built airport drawing packages.

All Test Readiness Notifications (TRN) and Test Readiness Reports (TRR).

All Programming Language Code (PLC) codes.

All Request for Variances (RFVs).

All Configuration Change Requests (CCRs).

All documents relating to the airport project (e.g. schedule, procedures, integration, and phasing documentation).

This list is not all inclusive and there are other documents that will be generated that the Government will request that the Contractor store and retain. The Government will provide direction on storage, handling, safeguarding, as well as access to this data.

On average, it is estimated that the Contractor will be expected to retain and store approximately 5 TB of data per year.

The Contractor shall obtain approval from the COR or TM prior to implementing any data storage solution.

2.0 Annual Program Management Support Services and Key Personnel (CLIN 0001) (Task

A-1)

2.1 Task A-1 Program Management and Key Personnel

The Contractor shall provide all necessary labor, travel, and materials to provide monthly Program Management and core support services in accordance with the Statement of Work. This includes providing the Key Personnel - ISAT Program Manager. As part of the Program Management support services the Contractor shall establish and maintain a formal organizational structure to manage the BPA and all Orders under it.

The Contractor shall perform Program Management activities, including, but not limited to:

Provide day-to-day assignments of personnel to functions in this BPA. Manage workload, deliverable due dates, requirements, and interface with Government stakeholders.

Report on the technical progress of the BPA and Orders in the Progress Reports. Progress Reports shall detail the technical progress of work activities, future scheduled project and current BPA activities, and any other activities assigned and managed under this BPA.

Manage all Orders to include finances, schedules, and resources.

Develop a Planning of Actions and Milestones (POA&M) for each individual Order.

Schedule and conduct a monthly in-person BPA Status Review with the Government COR and/or TM. This review will provide a current snap shot of activities to include current schedule, financial situation, resource allocations, status of all projects/tasks assigned, and any issues identified that need resolution or government input.

In addition, the Contractor shall participate in meetings and provide the following plans and reports as outlined below:

Kickoff Meetings

The Contractor shall participate in a kickoff meeting with the TSA to be scheduled 15-30 calendar day’s following the award of the BPA. Kickoff meetings may also be required for all Orders.

The BPA kickoff meeting will take place at the TSIF and will last three days. All key personnel, Task Leads, and other Contractor personnel designated by the Government are required to attend.

The COR or TM will provide an agenda for this meeting five (5) business days in advance.

Kickoff meetings for all Orders will take place at the location designated by TSA. All Contractor personnel designated by the Government are required to attend Order kickoff meetings.

The Contractor shall provide Kickoff Meeting Minutes (Deliverable D-1) within fifteen (15) business days following the kickoff meeting.

At the kickoff meeting, the Contractor shall present their plan for fulfilling the BPA requirements, not limited to approach, schedule, milestones, deliverables, risks, staffing approach, and other requirements of the BPA. The Contractor shall prepare kickoff meeting minutes, including a summary of action items and any issues requiring resolution.

Fully Loaded Integrated Master Schedule (Deliverable D-2)

The Contractor shall develop and maintain a Fully Loaded Integrated Master Schedule for all test events. Additional tasks(s) may be added to this schedule depending on the scope and complexity of Orders. The Contractor shall provide TSA with an updated version of the Fully Loaded Integrated Master Schedule weekly by Close of Business (COB) on Thursday of each week.

This schedule shall capture all activities of the BPA and Orders, Order expirations, Program Management events, test events, and all logistical and personnel resources.

The Contractor shall work with TSA to establish a Concept of Operations (CONOPS) on how the data is entered and how data will be validated as well as a procedure for schedule change tracking.

Planning of Actions and Milestones (POA&M) (Deliverable D-3)

The Contractor shall develop and maintain a POA&M for each task.

The Contractor shall prepare and submit a draft POA&M at the Order’s kickoff meeting. Updated POA&M shall be submitted to TSA monthly within five (5) business days after the last business day of the month.

Program Management Plan (PMP) (Deliverable D-4)

The Contractor shall develop and maintain a Program Management Plan (PMP) and shall keep the PMP up-to-date throughout the period of performance. This document will be provided to TSA as requested.

The PMP shall include the following information: relevant strategic information such as cost management, schedule management, technical management strategy, risk management, metric reviews, and quality management and control, Conflict Resolution/Escalation Process, Risk Management Plan, Monthly Test Surge Plan, Employee Turnover Management, Training Management.

The Contractor shall submit a draft PMP at the BPA kickoff meeting and provide an updated PMP within thirty (30) calendar days following the BPA kickoff meeting.

As Orders are placed, the Contractor shall update the PMP to reflect these Orders.

Program Management Review (PMR) and PMR Minutes (Deliverable D-5)

The Contractor shall conduct and coordinate quarterly in-person PMRs at locations agreed to by the Contactor and TSA. The Government’s intention is to hold 50% of the PMRS at a TSA designated location and 50% at the Contractor’s facility.

At the PMRs, the Contractor shall present their progress in supporting the BPA and any Orders awarded, provide status on technical requirements, identify any issues requiring TSA intervention or response, identify proposed activities for the next quarter, and present programmatic data including, but not limited to scope, funding, and schedule. The Contractor shall provide PMR minutes, including a summary of action items and highlighting any issues requiring resolution.

The Contractor also shall deliver a written PMR report as part of the PMR. The report shall include an overall summary, to include status on funding, resources, data, and equipment, as well as other items requested by TSA. In addition, the PMR report shall include summaries of the other reports provided by the Contractor during the PMR period. The Contractor shall prepare PMR minutes and deliver them to TSA within five (5) business days after completion of the PMR.

Management Reports

The Contractor shall develop and update management reports as requested by TSA, including:

Progress Reports (Deliverable D-6): Daily and/or weekly depending on tasks and surges Staffing Report (Deliverable D-7): A report that contains, but is not limited, to all hiring activities, and Contractor staff supporting the BPA. The staffing report shall list all Key Personnel, all core support personnel, and all staff supporting the BPA/Orders.

The specific outline, formats, delivery method, as well as previous examples will be provided and discussed during the BPA kickoff meeting.

The Contractor shall propose templates, ideas or examples of similar reports completed in similar contracts during the BPA kickoff meeting.

Contract Status Report (Deliverable D-8)

The Contractor shall provide a Monthly Contract Status Report (CSR) that highlights major accomplishments, all issues in each functional area of the BPA/Orders that need resolution/decisions, and a summary of all active and closed Orders. The summary of the Orders shall include obligations and expenditures to date, award value, summary of awarded modifications, Periods of Performance, as well as other relevant information that shows the status of the BPA and Orders. The content of this report will be discussed during the kickoff meeting.

This Contract Status Report shall be provided within five (5) business days after last business day of the month.

This Contract Status Report shall complement the POA&Ms and any other reports.

Organizational Chart (Deliverable D-9)

The Contractor shall provide an organizational chart that shows the lines of authority and clear roles and responsibilities for each position within the Contractor’s organization which supports the

BPA.

The Contractor shall provide TSA with an updated organizational within five business days after the Contractor makes changes to the personnel listed in the organizational chart.

The Contractor shall provide TSA an updated organizational chart if organizational changes impacting the lines of authority or roles and responsibilities for each position shown on the organizational chart are made.

The following personnel are designated as Key Personnel:

Key Personnel Title Roles and Responsibilities Required Education /

Experience ISAT Program Manager Responsible for managing all

Orders awarded, staffing, and overall operation of the BPA for the Contractor.

Minimum of twelve (12) years of Program Management experience and 10 years specializing in managing similar Federal programs of the size and complexity as this

BPA.

Bachelor’s degree is required.

A Master’s degree is preferred.

Ability to obtain a SECRET clearance is required.

ISAT Task Lead

See SOW Section 3.2 See SOW Section 3.2

Systems Assessment, Engineering, and Innovation Team Lead

See SOW Section 3.8 See SOW Section 3.8

Systems Assessment, Engineering, and Innovation Subject Matter Experts (SME) – 2 Positions

See SOW Section 3.9, 3.10, 3.11, 3.12

See SOW Section 3.9, 3.10, 3.11, 3.12

As part of task A-1, the Contractor shall provide an ISAT Program Manager. Please note that the ISAT Task Lead is covered by task A-2 and the Systems Assessment Engineering and Innovation Task Lead is covered by task A-8.

As part of task A-1, the Contractor shall also provide Core Staff to conduct the following “core” functions of the BPA:

Core Staff Functions Function Description Contracting Manage all contract activities for the BPA and Orders.

Administration Provide administrative support functions for the BPA and Orders.

Finance Provide financial management for the BPA and Orders.

Travel Manage travel under the BPA and Orders.

Technical Manage all technical activities under the BPA and Orders.

Resource / Schedule Management

Manage Contractor resources and scheduling activities for the BPA and Orders.

Logistics Manage the daily coordination of arranging test article delivery to test sites.

As requested by TSA, Key Personnel / Core Staff Function personnel shall attend all scheduled weekly, monthly, and quarterly meetings. Key Personnel / Core Staff Function personnel shall also attend ad-hoc meetings so long as TSA provides at least 24-hours advance notice of the meeting.

If designated Contractor personnel cannot attend, a substitute may be used. However, the substitute personnel must have the necessary knowledge to participate, respond to questions, and provide any information requested by TSA.

Before removing or replacing any of the Core Staff, the Contactor shall notify the Contracting Officer, COR and TM in writing before the change becomes effective. The Contractor shall submit sufficient information to support the proposed action to enable the Government to evaluate the potential impact of the change to this BPA. The Contactor shall not remove or replace Core Staff until the Contracting Officer approves the change.

3.0 ISAT Testing Support Services (CLIN 0002) (Tasks A-2 – A-13)

3.1 ISAT Description

An ISAT is required to be performed after each major phase of a multi-phase project or at the end of construction for a completely new Checked Baggage Inspection System (CBIS).

The PGDS for Checked Baggage Inspection Systems provides an overview of the ISAT testing process and also the tests used to evaluate the systems. At the time of release of this SOW, the current version of the PGDS is version 7. The PGDS document is updated approximately each year. Unless otherwise specified by the Government, the Contactor shall use the most recent version of the PGDS.

The ISAT process consists of three (3) phases: (i) Pre-ISAT Coordination, (ii) Testing, and (iii) Analysis. The following process flowchart provides the tasks and a high level overview of the ISAT Process through all three phases. There are instances where steps are combined within a phase but the functions will not transfer between phases.

Figure 1: ISAT Flow Phases Process flow

Based on prior experience, the following resources have been required to perform ISATs:

Resource Team Composition ISAT Task Lead N/A ISAT Testing Lead N/A Pre-ISAT Coordination Team 1 team lead, 3 analysts ISAT Testing Team 1 Onsite Test Team Lead, 1 Deputy Onsite Test

Team Lead, and 6 Test Team Members Data Analysis Team 1 team lead, 2 analysts

The above estimate is provided for informational purposes only.

3.2 Task A-2 ISAT Task Lead

The Contractor shall provide an ISAT Task Lead with the following responsibilities and education / experience:

Title Roles and Responsibilities Required Education /

Experience

The ISAT Task Lead is the technical point of contact for all ISAT activities (Pre-ISAT Coordination, Testing, and Data Analysis). The ISAT

Minimum of ten (10) years’ experience in Baggage Handling System Testing/Reporting.

Task Lead will need to lead and manage the testing and reporting effort to ensure that the process is correctly completed according to all applicable time lines.

The ISAT Task Lead shall perform the following activities including but not limited to:

• Coordinate and manage all Pre-Testing activities and ensure a Project Portfolio is generated for all ISAT Testing phases.

• Coordinate and manage all ISAT Testing activities and ensure that all data outlined is collected.

• Coordinate and manage all Data Analysis activities.

• Coordinate and manage the drafting, review, and submission of test reports.

Bachelor’s degree is required.

3.3 Task A-3 Pre-ISAT Coordination

The Contractor shall provide all necessary labor and materials to execute all of the Pre-ISAT Coordination activities and deliver the Project Portfolio (internal Contractor document using Contractor’s desired format) and Test Cards (TSA provided) to the Testing Team thirty (30) days prior to the commencement of an ISAT. Please note that labor also includes “travel labor”.

The Test Cards used for testing are provided by TSA for use during testing. The Test Cards used for each individual ISAT shall align with the ISAT Task Lead test strategy for the particular site.

Based on prior experience, the following resources and level of support have been needed to perform the Pre-ISAT Coordination activities on an annual basis:

Pre-ISAT Coordination Resource Level of Support Description Pre-ISAT Coordination Team (1 team lead, 3 analysts)

52 weeks

Responsible for all pre-ISAT Coordination activities as determined by the ISAT Task Lead.

The Pre-ISAT Coordination phase is designed to get the test team involved with the Integrated Local Design Team (ILDT)/Airport Team early in the project to ensure there is a continuous dialog within the team as it relates to the scheduling, conduct, and expectations of testing. At the discretion of the Deployment Logistics Division (DLD) Regional Deployment Coordinator (RDC), the Pre-ISAT Coordination team shall be invited to attend the normal ILDT/Airport meetings to begin the discussions about testing logistics and coordination. The Pre-ISAT team shall be involved in these early planning meetings which will greatly enhance the successful completion of the overall project.

The Pre-ISAT Coordination Team shall provide a Pre-ISAT checklist of required CBIS information to the ILDT/Airport Team. The ILDT/Airport Team will review this checklist and, through a designated Point of Contact (POC), provide feedback to the team. This checklist and the subsequent feedback will be used to generate a Project Portfolio which includes, but is not limited to, test objective, an overall project contact list, system descriptions, drawings, equipment serial numbers, expected throughput, and any approved Request for Variances (RFVs) and/or Check Baggage Integrates System Change Requests (CCRs). From the data collected, the Contactor shall develop (and obtain TSA ATSA approval of) a testing strategy which will enable the Pre-ISAT Coordination Team to develop the Project Portfolio.

For ISATs or Airport projects that require multiple phases, a Project Portfolio shall be made for each phase of the project.

The Project Portfolio and Test Cards should be provided to the onsite Testing Team at least 30 days prior to the commencement of the ISAT.

The designated Contractor Pre-ISAT Coordination POC (a member of the Pre-ISAT Team) will be the primary contact between the ILDT/Airport Team and the Testing Team throughout the completion of the project to ensure continuity of communication and a smooth testing transition throughout.

The Contractor Pre-ISAT Coordination Team will have regular interactions with the airport, programming, and construction teams which will require strong interpersonal/written communication and team building skills. The individuals working on this team must have a strong understanding of the PGDS for CBIS, Project Planning, CBIS Operations, and Testing

Methodologies. They will be representing TSA Acceptance Testing at numerous meetings and must be familiar with all TSA testing directives and practices.

The Contractor Pre-ISAT Coordination Team may be required to participate in the System Factory Acceptance Testing performed by the Baggage Handling System Programmer. The TM/COR will provide tasking as needed for this task.

Pre-ISAT Outcome:

The Contractor shall produce a Project Portfolio with the correct Test Cards at the end of the Pre- ISAT Coordination phase.

The Project Portfolio and Test Cards will be provided to the onsite ISAT Testing Team at least 30 days prior to the commencement of the ISAT. Please note that the Project Portfolio is an internal document that is approved/reviewed by the Government and will direct the Testing Team in performing the ISAT test.

3.4 Task A-4 ISAT Testing Lead

The ISAT Testing Lead is the individual responsible to the ISAT Task Lead for managing the testing onsite and ensuring that all testing is accomplished using the appropriate procedures and test methodologies. This individual shall manage all test teams and ensure that all testing protocols and reporting requirements are met. This individual will prepare a daily test report outlining all testing activities accomplished during testing (Deliverable D-10).

The ISAT Testing Team Lead is not expected to regularly travel to testing sites, rather, their role is to administer the entire testing process.

3.5 Task A-5 ISAT Testing Team - Home Support

This task is intended to be utilized when the ISAT Testing Team is not performing onsite testing activities (for example, when they are preparing for upcoming tests). Task A-6 ISAT Testing – Onsite shall be used for onsite testing activities.

3.6 Task A-6 ISAT Testing - Onsite

The Contractor shall provide all necessary labor and materials to execute all ISAT Testing activities. Please note that labor also includes “travel labor”.

The Contractor shall have sufficient staff to support up to two (2) ISATs at different sites per week. After the first year, the Contractor shall have a surge capacity to support three (3) ISATs at different sites per week as required by TSA. Please note that this CLIN is should be priced on a “per ISAT” basis. TSA anticipates that there will be a maximum of sixty (60) ISAT test events in the base year of this contract.

perform ISAT Testing on a per site basis:

ISAT Testing Resource Level of Support Description Onsite ISAT Testing Team Lead

1 week Supervise On-site ISAT Testing

ISAT Testing Team (7 testers) 1 week Conduct On-site ISAT Testing

The ISAT Testing Team will perform the test functions during test events. They perform the following functions on the test team: bag unpacking/repacking, bag induction, Checked Baggage Resolution Area (CBRA) operation, On Screen Resolution (OSR) operation, data collection, matrix operations, and system observation.

The ISAT Test Team is comprised of eight (8) team members (Onsite ISAT Testing Team Lead, Deputy Onsite ISAT Testing Team Lead, and six (6) test team members. The Onsite ISAT Testing Team Lead is the individual responsible for the overall management of the test onsite. They will coordinate with all internal and external entities to ensure that the testing is accomplished correctly and in accordance with TSA guidelines. They will be the central point of contact for all testing while onsite. This person will be responsible for the following: test execution, job assignments, test reporting, data collection, report collection, and TSO training for the test. The Deputy Onsite ISAT Testing Team Lead will be responsible for ensuring that all operations in the matrix are performed per the test plan and test procedures. In most instances they will be the individual that will perform any test manipulations or conditions. They will assist the Onsite ISAT Testing Team Lead in the duties above.

TSA may request that Contractor personnel participate in the Test Readiness Review (TRR). The Contractor shall support the site Deployment Site Lead (separate TSA contact) during the TRR process by witnessing or any other means to facilitate test readiness test completion as directed by the Technical Monitor. This testing proceeds the ISAT testing and is an opportunity for the Onsite ISAT Test Team Lead and/or Deputy Onsite ISAT Test Team Lead to gain familiarity with the system under test and also collect test data that can be used for ISAT efficiency and security determinations.

Testing is performed to determine system certification of the CBIS. Thirty (30) days prior to commencement of the ISAT, the Independent Acceptance Team (IAT), Onsite ISAT Test Team Lead, and Deputy Onsite ISAT Test Team Lead will take over the coordination of the ISAT from the Contractor’s Pre-ISAT Coordination Team. From this point forward, they will participate in the ILDT/Airport Team meetings, will coordinate with the ILDT/Airport Team to monitor and potentially participate in the testing phase of the TRR. The actual execution of the ISAT will normally take place over a one-week period (Monday: the test team travels to the site; Tuesday – Thursday: conduct the ISAT; Friday: used as a backup testing day if necessary, or the test team departs the site) per phase. The duration of the ISAT is dependent on the amount of testing time available each day. If there are at least six (6) hours available each day, then testing can be completed in two test days baring any issues. A shorter available testing time may extend the overall testing window past the planned duration. Upon completion of testing if there are subsequent testing phases the Contractor Pre-ISAT Coordination Team will again take over communicating with the site and coordinate the next ISAT testing phase.

During the ISAT various test protocols will be utilized to determine if the system is “suitable” and “efficient” for TSA Operations. All tests performed will be based on the tests included in Appendix G of the PGDS current that the time of testing. Based on the findings of Suitability and Efficiency, TSA will provide a recommendation to the RDC as to whether the system is efficient and secure enough to be utilized in live screening operations. The RDC will provide the “Go Live” notification at their discretion.

The Onsite Testing team will be responsible for drafting and reviewing the Quick Look Reports (QLR) (Deliverable D-12) and ISAT Test Summary Reports (TSR) (Deliverable D-13). They should receive an analysis package from the Analysis Team to be used in the reports. These QLR reports shall be submitted to TSA within seven (7) calendar days after completion of testing or in the case of TSRs within seven (7) days after collection of data during the data run-in period.

Individuals supporting the Testing process must have a strong understanding of the test protocols outlined in the PGDS Appendix D. An Onsite ISAT Test Team Lead and Deputy Onsite ISAT Test Team Lead will be identified by the Contractor Team. They are responsible for the on-site management of the testing team. The Onsite ISAT Test Team Lead must have mastery knowledge of the test protocols outlined in Appendix D of the PGDS and data analysis techniques used to evaluate Baggage Handling Systems (BHS) and Explosive Detection System (EDS) reports. The Deputy Onsite ISAT Test Team Lead shall have a mastery knowledge of the test protocols outlined in Appendix D of the PGDS. The Deputy Onsite ISAT Test Team Lead is considered a training position for the Onsite ISAT Test Team Lead, who may not have a mastery knowledge of the data analysis techniques used to evaluate the system.

Prior to commencing an ISAT, Owner’s (i.e. airport authority, airlines, local authorities) Testing, and the Test Readiness Review (TRR) must be successfully completed and documented. A Test Readiness Notification (TRN) must be provided to the Acceptance Test Team at least five (5) days prior to the commencement of the ISAT. The ISAT must be completed and successfully passed prior to screening of live operational baggage/passengers.

Test Scheduling and Blackout Dates

TSA requires the Deployment Logistics Division (DLD) Site Integration Test Team to provide a TRN or results of the TRR, five (5) business days in advance of the required test event. Upon receipt the Contractor shall review the TRN to ensure that all anomalies discovered are understood and that there is sufficient information available to determine if additional testing is required.

There will be instances that the TRN will not be submitted on the respective timelines and/or at Government direction a test needs to conducted in short time frame, such as 24 – 48 hours. For these test events, a TRN may not be available, however this events shall be only conducted per TSA COR, Technical Monitor, or Designee direction. The designee will have to have a written notification from TSA COR or technical monitor.

No testing will be executed during the following weeks (i.e. Monday through Friday):

Thanksgiving week, Christmas week, and the week between Christmas and New Year’s Day.

These three (3) one (1) week periods are black-outs for any on-site testing activities. If commissioning activities cannot be completed prior or post to black-out periods, then test execution will not begin. The only exception to these blackout periods is if there is prior approval from the COR or TM for testing to occur during the blackout periods.

Test Results

The Contractor shall deliver the QLR and/or TSR. A QLR is required after each phase of ISAT testing unless directed by the TM/COR. This report is a formal synopsis of the testing results and provides a recommendation to TSA as to the status if the system. A TSR is provided upon completion of all testing phases and after completion of the data analysis period. This report is generally provided with forty-five (45) days after the system has actively started screening checked luggage. This report outlines the status of deficiencies that have been found during testing and also provides efficiency and suitability determinations based on actual live operations.

QLR and TSR shall provide recommendations from the Contractor on the following:

Proceed to Live Screening Operations System Suitability System Efficiency

These recommendations are based on the information collected during the testing of the system.

System Suitability is defined as does the system properly track bags and sort them to the appropriate destination (clear bags – makeup and alarmed bags to CBRA correctly. System Efficiency is how well the system operates in relation to the standards outlined in the PGDS.

If a system is found to be “suitable” and “efficient” it will be recommended that it proceed to Live Screening Operations. Once a system “passes” ISAT the Technical Monitor in coordination/consultation with the RDC will determine the next steps in the process and reporting requirements for multi-phased projects. For systems found to be not secure the system will be deemed an ISAT failure and will require a retest once all deficiencies have been addressed and corrected. A retest will not be permitted for at least seven (7) calendar days after the failure. A retest will not be performed without a written corrective action report from the airport team. A retest and its timeline will be coordinated between the RDC and the Acceptance Test Lead, Technical Monitor, or COR. The retest is treated just like another phase of testing. If a system fails ISAT, then a major programming change would be required to correct the deficiencies. As a result of that a complete test would be performed to collect both suitability and efficiency data to ensure the system is operating correctly in this case another Task A-6 would be used.

3.7 Task A-7 Data Analysis

The Contractor shall provide all necessary labor and materials to execute all ISAT Data Analysis activities. Please note that labor also includes “travel labor”.

perform ISAT Data Analysis for each ISAT:

ISAT Data Analysis Resource Level of Support Description Data Analysis Team (1 team lead, 2 analysts)

1 weeks Conduct data analysis activities as directed by the

The Contractor shall deliver an Analysis Plan to the airport/ILDT at least fourteen (14) calendar days prior to the requested data collection. This plan is a step by step guide developed by the Contractor on what reports are needed from the airport to accurately assess the operation of the system. Additionally, this plan outlines how the contractor expects to receive the reports from the airport. This plan is generated by the Contractor and is not considered a deliverable to TSA and the format is entirely up to the Contractor. TSA can provide a sample of the document currently used.

The Data Analysis Team will be responsible for all data analysis of the testing data for all phases of the project. The Data Analysis Team members must have a mastery of current analytical processes and procedures. During the ISAT testing, the Onsite ISAT Testing Team Lead or Deputy will forward daily the test data collected during the tests to the Data Analysis Team for analysis.

The Data Analysis Team shall provide analysis of the test data for the QLRTSR to the Onsite ISAT Testing Team Lead in a timely manner to allow the delivery of the reports within seven (7) calendar days upon completion of testing or operational run-in. The Operational Run-in will commence two (2) weeks after the completion of the ISAT or when designated by the Technical Monitor/COR. The Operational Run-in will normally last for two (2) weeks but may extend if conditions warrant it.

During the run-in period, TSA expects that the airport and the BHS and EDS teams will provide the requested reports to support the data analysis effort. If the system is shown to be performing adequately and within established efficiency requirements, the run-in will stop and the Test Summary Report (TSR) will be drafted. If performance is not within the established efficiency requirements, or at the discretion of the RDC, another two weeks of data collection and run-in will be performed prior to the drafting of the TSR.

Upon completion of the two week (or as prescribed) run-in period, the Data Analysis team will perform an analysis of the submitted reports. Upon completion of their analysis, the data will be forwarded to the Onsite ISAT Testing Team for incorporation into the TSR. The TSR upon being finalized/approved by the Technical Monitor/COR will them be forwarded to the RDC and the distribution list provided by the Technical Monitor/COR. The RDC will then provide the TSR to the ILDT/Airport Team.

The TSR will include the results from all testing (TRR and ISAT) as well as data from the Operational Run-in. Additionally, it will include a running list of all items discovered during testing and the status of those items. The TSR should also detail any new findings.

Individuals supporting this process shall have a thorough understanding of the BHS and EDS reports and the data that is contained within them. This includes any error codes or system generated data.

3.8 Task A-8 Systems Assessment, Engineering and Innovation Task Lead

The Contractor shall provide a single Systems Assessment, Engineering and Innovation Task Lead with the following responsibilities and education / experience:

Title Roles and Responsibilities Required Education /

Experience Systems Assessment, Team Lead

The System Assessment, Task Lead is the technical point of contact for all System Assessment, Engineering, and Innovation activities.

They will lead and manage the activities assigned under the System Assessment, Engineering, and Innovation

CLIN.

They are the subject matter expert in system design, programming, system utilization, and engineering processes for Checked Baggage systems (Conveyor, Explosives Detection Systems (EDS), Programming Language Code (PLC), etc.).

They will manage and monitor all innovation activities developed to enhance all ISAT testing and assessment processes.

Minimum of ten (10) years’ experience in Baggage Handling System Design, Programming, Engineering, and Testing is required.

This individual will be lead the System Assessment, Engineering, and Innovation Team’s activities. The activities under this task are unique in nature and require a team of specialized individuals that have a variety of knowledge in BHS and EDS system design, programming, and system optimization, as well as process improvement.

3.9 Task A-9 System Assessment and Innovation (Basic Support)

The Contractor shall provide a single full-time Subject Matter Expert (SME) to support the System Assessment and Innovation activities and, together with the Systems Assessment, Engineering and Innovation Task Lead, will constitute the System Assessment, Engineering, and Innovation Team.

System Assessment(s) are critical to ensure systems are screening baggage and passengers securely and efficiently. To perform these services, specialized technical experience is needed.

The System Assessment and Innovation SMEs are considered key personnel and will be responsible for numerous technical tasks including, but not limited to:

Providing technical support for updates to the Planning Guidelines and Design

Standards (PGDS).

Reviewing system design documentation and identifying potential issues or failures to comply with TSA policies.

Conducting site meetings with local TSA and airport operational personnel.

Providing day-to-day technical support on subject areas such as: BHS electrical infrastructure, mechanical design, software programming and vulnerabilities, systems analysis, system design, system installation, and operational interfaces.

Providing oversight for implementation and testing of changes to equipment, processes and/or procedures to mitigate or eliminate deficiencies/issues.

Providing engineering support through the Post Implementation Review (PIR) process.

Providing technical support during failed ISATs.

Reviewing and analyzing PSP or EBSP equipment reports (e.g., BHS, EDS, ASL) to determine what area of the systems are experiencing functional issues.

Conducting airport assessments to observe systems operations from both a detailed mechanical/controls perspective and identifying modifications and improvements to existing systems.

Evaluating checked baggage screening systems to identify the source of screening inefficiencies, safety, or security issues and recommending approaches for resolving these issues.

Conducting data analysis to establish passenger flow and screening needs for airports.

Reviewing and providing a recommendation for Request for Variance(RFVs) for all screening equipment within 24hrs of receipt.

Reviewing CCRs for all screening equipment within 24hrs of receipt.

Generating BASE Team reports (refer to template) within 10 business days after completion of a site visit.

Conducting aviation studies to further enhance TSA operations or systems performance.

Responding to emerging technical issues.

Historically, the level of effort required to support these Task was performed by one Full Time Employee (FTE). Offeror’s are encouraged to propose efficiencies. Historic FTE information will be removed from the PWS at award.

For planning purposes, a typical month would include, but not be limited to, the following tasks:

One site-visit with a resultant Baggage Assessment and System Evaluation (BASE) Report (15 days).

One Technical Study with a resultant Report (10 days).

One Screening Demand Analysis (3 days).

20 CCRs.

5 RFVs.

One Design documentation review (3 days).

One ISAT Support (2 days).

Note: The above is only a subset of activities that can be quantified based on historical knowledge.

In addition, the Contractor shall propose at least one test innovation per Order, per year. The Government reserves the right to decide to pursue that innovation. The Government will formally provide the funding at the Order level for these innovations using CLIN 0004. Test innovation refers to any improvements in the process or technology which have a final goal of improving testing methods/methodology and of ensuring that all systems are tested adequately using the latest techniques.

The Contractor shall provide expertise and support that allows TSA utilize current technology traits in the field. This will allow TSA to support continuous improvement of operational security technology solutions. This includes assisting with specific industry oriented conferences. Efforts include application development, data capture systems creation, and any other effort that would increase productivity or capability in supporting BASE initiatives.

An example of previous innovations includes:

Bag Tags Printer – Enables TSA to create International Air Transport Association (IATA) tags that are compliant with the current IATA standard.

Bag Measurement Device – Enables TSA capture the number of bags, their dimensions, and also a picture of the bags.

Any improvements in the process or technology have a final goal of improving testing methods/methodology and ensuring all systems are tested adequately using the latest techniques.

The Contractor shall develop a final report inclusive of the activities outlined above at the conclusion of each innovation.

Daily status Updates- Projects and Initiatives: The contractor shall provide Daily Status updates for Projects and Initiatives as required (D- 16)

3.10 Task A-10 System Assessment and Innovation (Complex Support)

The activities for this task are identical to the ones in Task A-9 but the complexity and level of effort are greater than the ones outlined in that task. An example of this would be a major study of large airport BHS systems that are not performing in accordance with the PGDS guidelines or there is a major problem with its operation that is impacting TSA.

Historically, the level of effort required to support these Task was performed by three (3) FTEs and generally are accomplished in one month. Offeror’s are encouraged to propose efficiencies.

Historic FTE information will be removed from the PWS at award.

3.11 Task A-11 Engineering and Programming (Basic Support)

The Contractor shall provide a single full-time Subject Matter Expert (SME) that is available to support the Engineering and Programming activities.

Engineering and Programming support is considered critical to the overall assessment and design of BHS systems. Individuals supporting this task will be responsible for numerous technical tasks including, but not limited to:

System Design Review Cyber Security with a focus on Industrial Control systems vulnerabilities and protections Programming Language Code reviews and optimizations BHS System Troubleshooting and Remediation Coordination with BHS and EDS manufacturers to discuss

The Cyber Security technical task is an emerging requirement for all TSA BHS systems. As a result, the focus of this is to ensure that there is expertise in hardening and securing Industrial Control Systems. So the individual supporting this task shall have a background in Cyber Security and an understanding of Industrial Control Systems.

3.12 Task A-12 Engineering and Programming (Complex Support)

The activities for this task are identical as the ones in Task A-11 but the complexity and level of effort are greater than the ones outline in that task.

This task would be accomplished by two (2) Subject Matter Experts and generally be completed within one month. An example would be the redesign of the TSIF BHS Testing environment.

3.13 Task A-13 ISAT Logistics

The Contractor shall provide support for coordinating the shipping, delivery, and return shipping to the storage facility of all test articles for ISAT. The actual development, maintenance, and storage of test articles is being performed under another contract and is outside of the scope of this BPA.

4.0 ISAT Testing Support Services (CLIN 0003) (Task A-14)

4.1 Task A-14 Travel and ODCs

The Contractor shall provide all travel necessary for tasks A-1 – A-13.

Travel is required within the Contiguous United States (CONUS) and U.S. Territories in support of this SOW. All travel shall be in accordance with Federal Travel Regulations (FTR). The Contractor shall be responsible for coordinating and tracking of all travel expenses necessary to accomplish each task.

The Government will reimburse all reasonable travel expenses in accordance…