Attachment 5 - TRN Letter Template.docx

DOCX document 68 KB Posted

Attached to
Credential Authentication Technology (CAT)
Solicitation number
HSTS04-14-R-ST4000
Issued by

About this file

Not Listed

View the file

Other files

Show all 21

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

U.S. Department of Homeland Security TSA Systems Integration Facility (TSIF) Ronald Reagan Washington National Airport One Post Office Road Washington D.C. 20001-6000

Test Readiness Notification (TRN) Memorandum

Date: __________ (Day/Month/Year)

I ___________________________ (installation personnel) have completed the installation of the system ___________________________________ (machine model and Serial Number identifier) in accordance with manufacturer’s instructions, in the ___________________________ (Test Lab/ Area) of the TSA Systems Integration Facility (TSIF).

The system installation technician(s) certify and validate system performance upon its installation at the TSA Systems Integration Facility (TSIF), system performance meets the expectations of ____________________ (system vendor), and that the system is ready for record testing expected to take place __________ (Month/Year) to __________ (Month/Year).

SAT (or equivalent) Title and Version: ________________________________________________.

For the associated date above, this TRN serves as an acknowledgement between the TSA and the Transportation Security Equipment (TSE) vendor that the identified system is ready for record testing for the test period scheduled to occur after the system is certified as ready by this TRN. This TRN applies only to the identified system and by signing this notice, both parties agree that the vendor understands the following:

Test Area Access

· Test Team is the primary responsible organization for testing. Due to test integrity, safety, and security concerns, Test Area access is limited for the equipment vendor.

· The vendor must obtain access to the machine through established maintenance procedures.

· All Non-Test related entities must coordinate observational activities with Test POCs.

· Only granted on non-interference basis.

· Participation subject to Test POC authority and discretion.

Test Team Disclaimer

· TSIF Test Team members are not Contracting Officers (CO), Contracting Officer’s Representatives (COR), or Task Order Technical Monitors (TM); TSIF Test Team members cannot obligate the government.

· Any vendor actions taken because of conversations with the TSIF Test Team are undertaken at the vendor’s own risk.

· At no time will the conversations be construed as direction from the government unless coordination and concurrence is obtained from the designated CO or COR.

· The intent is not to inhibit normal interactions during the course of testing, training, installation, and maintenance but to protect the government from inadvertent obligations and the vendor from additional costs.

Test Results

· The Test Team will not release test results without the project designated Program Management Officer’s, CO’s, or COR’s approval.

· Test Team Members will not communicate test status reports, system performance results, FDRS data, etc. to vendors or others without express CO/COR approval.

· System data (FDRS or logs) required for troubleshooting malfunctions must be coordinated with Test Team POCs who will obtain project authorization prior to access.

Vendor Participation

· Training: Vendor provides equipment training.

· Configuration Audit Support: Vendor on-site with DHS, TSA, and/or ILS Teams. (Testing will not start without CM audit.)

· Equipment Installation: Vendor on-site with TSIF Test Teams.

· Site Acceptance Test and Integrated Site Acceptance Testing: Vendor on-site with TSA Test Team.

· Preventive Maintenance: Vendor to coordinate with TSIF Test Team.

· During Testing, the equipment vendor will not have unescorted routine access to the test equipment.

System Maintenance

· Perform corrective maintenance as requested.

· Provide requested information about maintenance actions completed.

· Provide assistance with FDRS download procedures.

· Provide software if necessary for data download and analysis.

· Contact the TSIF Test Team when Preventative or Scheduled Maintenance is needed in accordance with maintenance plan.

· Log vendor maintenance actions with Maintenance Service Report or Test Incident Reports.

· Certify System is ready to test upon completion of maintenance.

Test Integrity Safeguard

· Unauthorized vendor access may terminate testing and further acquisition consideration.

· System Configuration is not to change without undergoing TSA Developmental Change Process review and approval.

Test Ending Events

· TSIF Testing will terminate when data collection is complete.

· Other Events that could halt testing:

· Safety Evaluation discovers critical deficiency.

· Equipment demonstrates lack of maturity.

· Equipment limitations or failures prevent data collection or cause data corruption.

· Vendor inappropriately interferes with Test or System Configuration or Software Settings.

Other Notes

· No photography/videos. TSIF Test Team will provide photos/video as requested if mission permits.

Vendor Representative :

Date:

TSIF Representative:

Date:

Contract Number (TSA contract # or RFD version number for System Under Test (SUT)):

image1.png

File details come from the government source that posted it. Updated .