Identity Management System

The vendor required to provide identity management system (IDMS) for include:
•    To enforce business rules for badge issuance; comply with the transportation security administration (TSA) regulations and security directives (SD) 
•    To reduce manual, time consuming, error prone, and duplicate data entry in multiple standalone systems 
•    To improve customer service 
•    To achieve paperless process.
- Platform:
•    Propose system architectures (on premise or a hybrid on premise cloud solution (azure(preferred), AWS, other)) that provide cost effective and operationally efficient IDMS without losing any functionality
•    The IDMS shall utilize communication links between the tiers of the application, which shall be encrypted using at least transport layer security (TLS)
•    Provide server requirements, network requirements, database, storage, back-up server and other as needed to operate the IDMS.
•    IDMS must support the use of firewalls, intrusion detection systems, virtual private networks, virus protection, encryption, access controls, password expiration, identity management, and other technologies to ensure that IDMS complies with all TSA security requirements. 
•    IDMS shall provide system level tools (or protocols) to support network intrusion and performance monitoring by airport IT applications.
- Environment:
•    The airport highly recommends the IDMS vendor to provide the most suitable system architecture (cloud solution or on-premises solution) based
- Implementation approach
•    Project schedule
•    Communications plan should address at a minimum the following topics:
o    Weekly and monthly project status meetings followed by minutes.
o    Forms and templates to track ongoing open items, issues, actions, decisions, and statuses.
•    Change management plan should include at a minimum:
o    Process, form templates, and method to document resolutions.
o    Change control process for raising change requests, review and approval methods, form templates, and cost analysis impacts.
•    Plan to conduct workshop to document and review process workflows, system design and functional requirements as per the contract.
•    Infrastructure specifications
•    System software and hardware requirements (if applicable): server, OS, database, network, firewalls,
•    Badging equipment includes quantities for workstations and badging peripherals.
•    External systems interface control documents
•    Data migration plan
o    The contractor will perform data migration into the test environment such that the system is test ready. 
o    Impact analysis of certain data fields that are mandatory for the normal performance of the IDMS.
o    Contractor will submit reports of preliminary analysis from the data repositories identifying missing or incorrect data elements.
- The contractor will first install and configure the system in the testing and training environment (pre-production) and perform the system acceptance testing and training in this environment.
- Provide for the system acceptance testing the following:
•    Test plan to include test timeline, staff and equipment resources required. 
•    Test scripts and test cases: scenario based and mapped to the functional specification’s requirements established.
•    Online issue tracking system: method to log, identify issues and track testing results for actions.
- System acceptance approval in the testing and training environment from the airport after all requirements are demonstrated and tested, there are no open items, and the airport has provided explicit acceptance of the system.
- Provide user manuals – electronic copies (pdfs) and hard copy, bound user manuals for all training sessions.
- Required to perform the implementation and roll out of the system into the production environment. 
- The installation in the production environment must take place after the airport has approved the system acceptance testing.
- Provide an implementation plan or run book for the airport’s review and approval which will include – step-by-step guide for installation, configuration, database migration, 3rd party integration sequence and production sanity testing details.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: December 12, 2025