CMS - Appendix D - Requirements Compliance Certification_TSP Enhancement Features Matrix.xlsx
XLSX spreadsheet 20 KB Posted
- Solicitation number
- 21240625164751
- Issued by
- Philadelphia County, Dale Borough, Pennsylvania
About this file
This is a Requirements Compliance Certification document for a Digital Content Management System (CMS) enhancement project for the City of Philadelphia, Department of Aviation at Philadelphia International Airport (PHL). The document outlines eighteen must-have capabilities and features that the CMS solution must satisfy, including seamless integration with various airport data sources, real-time data updates, content management across multiple media types, comprehensive security controls, integration with existing airport systems such as flight information and baggage systems, display management with offline functionality, 99.99% minimum uptime requirements, dynamic content display timing, modular and scalable design, detailed display customization and emergency override capabilities, ADA compliance with content approval workflows and audit trails, centralized system monitoring with remote administration, hardware provisioning including servers and display controllers, environmental compatibility for diverse airport installation locations, professional installation and rigorous testing phases, and support for multiple concurrent users managing content across numerous displays with customizable templating and branding.
The requirements matrix indicates that most capabilities are in a "Select from Dropdown" status for vendor response, while specific entries note that real-time updates functionality is available and content management features are not currently available. The document requires that hardware provision be addressed, with preference for compatibility with PHL's existing Windows-based mini-PC form factors where applicable. The system must undergo detailed performance verification, endurance testing, and final acceptance review before operational deployment. This comprehensive CMS solution is designed to meet the complex operational needs of a major international airport while maintaining Philadelphia's visual and operational standards across all digital display infrastructure.
View the file
Other files
Show all 24
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
Features
| Spec | ||
| ID | Criticality | Capability |
Digital CMS Additional Capability Description Vendor Comments Availability
| 1 | Must-have | CMS Capabilities | The CMS should integrate seamlessly with various data sources, automate content display based on predefined rules, and provide a user-friendly graphical interface for content management. | Select from Dropdown | Select from Dropdown |
| 2 | Must-have | Real-time Updates | The system must support real-time data updates and automatic content adjustments without manual input, especially for critical updates and emergency messaging. | Select from Dropdown | Function Available |
| 3 | Must-have | Content Management | Must handle a diverse range of content types such as text, images, videos, interactive media, including airline-specific branding ensuring appropriate display on different digital displays throughout the airport. The system should support updates via a web interface, ensuring flexibility for different users. | Select from Dropdown | Function Not Available |
| 4 | Must-have | Security and Data Integrity | Strict access controls must be enforced to present unauthorized data access, with data input through secure forms and content displayed based on user roles. | Select from Dropdown | Exception |
| 5 | Must-have | Comprehensive Integration | The CMS must integrate with existing and future airport systems like flight information, baggage systems, and more, following standard data schemas and messaging standards. | Select from Dropdown | |
| 6 | Must-have | Display Management | Should manage content across displays, capable of operating independently from the central servers to enhance reliability (i.e. cached data is displayed if the connection to central server is disrupted or backend server downtime). | Select from Dropdown | |
| 7 | Must-have | High Availability | The system should maintain operational integrity with a minimum uptime of 99.99%, with support for scheduled downtime during off-peak hours. | Select from Dropdown | |
| 8 | Must-have | Dynamic Content Display | Timing windows for content display should be adjustable dynamically to optimize the utilization of display resources. | Select from Dropdown | |
| 9 | Must-have | Modular and Scalable Design | The system should be designed for easy scalability and integration with potential future expansions and requirements. | Select from Dropdown | |
| 10 | Must-have | Display Customization | The CMS should allow detailed control over content displayed, including emergency overrides and the segmentation of display areas. Displays should be individually controllable and customizable based on various parameters like location, time of day, or external triggers. | Select from Dropdown | |
| 11 | Must-have | Compliance and Workflow | The CMS must comply with ADA standards and support a workflow for content approval, particularly for third-party content such as advertisements. A robust audit trail for content changes should be provided. | Select from Dropdown | |
| 12 | Must-have | System Monitoring | Implement centralized control and monitoring of system performance and failures with real-time alerts and logging. Remote administration capabilities for endpoint devices are required, including performance monitoring and the ability to remotely restart services. | Select from Dropdown | |
| 13 | Must-have | Hardware Provision | Necessary hardware including servers, workstations, and digital display controllers must be provided, supporting the overall system design and operational needs. It is preferred that the system can use PHL’s existing form-factor mini-PCs (Windows) if compatible. | Select from Dropdown | |
| 14 | Must-have | Environmental Compatibility | Hardware must be suitable for the specific installation environments within the airport, from controlled interiors to harsher, uncontrolled or exterior locations. | Select from Dropdown | |
| 15 | Must-have | Professional Installation | Installation must adhere to local and national standards, with all activities performed professionally and neatly. | Select from Dropdown | |
| 16 | Must-have | Rigorous Testing Phases | The system must undergo detailed performance verification and endurance testing to ensure it meets all operational and functional requirements. | Select from Dropdown | |
| 17 | Must-have | Final System Acceptance | After successful testing and resolution of any issues, the system will undergo a final review and acceptance process to ensure it meets all specifications and is ready for operational deployment. | Select from Dropdown | |
| 18 | Must-have | Multiple User and Display Management | The CMS should support concurrent access from multiple users and synchronize content across multiple displays, catering to the complex operational needs of a major airport like PHL. Templating and branding should be customizable to maintain PHL’s visual and operational standards. | Select from Dropdown |
File details come from the government source that posted it. Updated .