Attachment 3 - Configuration Management Plan for OAPMFinalns.pdf

This is a Configuration Management Plan (CMP) for the Transportation Security Administration's Office of Acquisition Program Management (OAPM), outlining the processes and procedures for managing Transportation Security Equipment (TSE) throughout its entire life cycle.

The plan establishes the CM framework for TSE hardware, firmware, software, documentation, testing, and design artifacts developed, integrated, acquired, deployed, and maintained by TSA-OAPM. Key processes include Configuration Management Planning, Configuration Identification, Configuration Change Management, Configuration Status Accounting, and Configuration Verification and Audits. The plan defines roles and responsibilities for multiple stakeholders: the Configuration Control Board (CCB) oversees change approvals; the CM Functional Lead chairs the CCB and manages baseline control; the Configuration Management Specialist maintains developmental baselines; the Contracting Officer implements approved changes; Product Contracting Officers' Representatives conduct technical reviews; and Original Equipment Manufacturers (OEMs) implement CM requirements in their contracts. The plan details four types of change requests—Engineering Change Proposals (ECPs), Requests for Deviation (RFDs), Requests for Waiver (RFWs), and Developmental Deviations (DEPs)—each with specific classification levels (Minor, Major, Critical). Configuration baselines include Certification or Developmental Product Baselines established during development and testing phases, with the Production Baseline established post-contract award following functional and physical configuration audits. Implementation procedures include a Configuration Audit Procedure, CCB Charter, CCB Procedure, and Configuration Status Accounting Procedure. OEMs must deliver CM documentation as contract data requirements including a CM Plan, Master Configuration Item List, change requests, deviation requests, waivers, and configuration audit reports. The plan emphasizes use of a TSA-approved electronic database for information management, compliance with federal records retention guidelines, and coordination across multiple testing entities including the Transportation Security Laboratory (TSL) and Transportation Security Integration Facility (TSIF).