Appendix D.PDPH.EHS.RFP.IntegratedEHregcompmgmtsystem_v3 11052026.xlsx
XLSX spreadsheet 13 KB Posted
- Solicitation number
- 21260923160156
- Issued by
- Philadelphia County, Philadelphia City, Pennsylvania
About this file
This file is a requirements specification document for the City of Philadelphia Department of Public Health (PDPH), Environmental Health Services (EHS) division, outlining functional and technical requirements for an Integrated Environmental Health and Regulatory Compliance Management System. The procurement seeks a Software-as-a-Service (SaaS) solution that consolidates multiple environmental health program areas including food safety certification, plan review permitting, special event permitting, body art permitting, pool permitting, and tobacco permitting into a centralized platform. The system must support major web browsers with responsive design, accommodate up to 100 simultaneous users without latency, and achieve 99.9% uptime. Key functionality requirements include role-based access controls with audit logging, customizable forms with CRUD capabilities, signature input functionality, secure file attachments, GIS-based reporting with Esri ArcGIS integration, real-time reporting capabilities, and public portal access for permit lookup and application status checking. The solution must migrate approximately 2 GB of existing data and 60 GB of files from the current system without data loss and support unlimited future data growth.
The system must incorporate comprehensive security measures including data encryption at rest and in transit, Azure Active Directory integration, API access with customized endpoints, and daily backup and disaster recovery protocols. Additional requirements include near-real-time data exchange capabilities with external systems and internal PDPH datasets, initial system training, a customer relationship management platform for issue reporting and change requests, and provision of up to five minor feature changes annually at no additional cost. The solution must support online payment processing through the Kubra vendor, money order submission, automated permit expiration reminders, and batch permit processing. The document does not specify pricing terms, contract duration, renewal options, set-asides, incumbent information, or funding amounts and sources.
View the file
Other files
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
Sheet1
| Requirement ID | Requirement Description | Compliance Status | Comment | Additional Cost |
| 1 | Provide a SaaS (Software-as-a-Service) customized solution to meet all requirements in this RFP (request for proposal) | |||
| 2 | Support major browsers such as Chrome and Edge | |||
| 3 | Have a responsive design for tablets, phones, and computer screeens | |||
| 4 | Requires no installation or any special changes to the browswer or device setting | |||
| 5 | Have standard password and username log-in functionality, such as password complexity and length requirements, self-serve reset and update, and automatically logging out after a period of inactivity | |||
| 6 | Have different roles, such as View, Write, Admin, for different users to access different levels of data | |||
| 7 | Allow Admin users to make changes throughout the system, such as user accounts, reports, facilities, predefined statements, etc. | |||
| 8 | Have logs of user activities, and allow Admin users to run audit reports | |||
| 9 | Allow traffic of up to 100 users simultaneously using the service without latency | |||
| 10 | Integrate with City of Philadelphia Azure Active Directory (Desired) | |||
| 11 | Have a user-friendly interface with robust search functionality such as partial address, facility name, inspection result, health district, etc. | |||
| 12 | Allow staff to export searched results as CSV (comma-separated values) or Excel format | |||
| 13 | Show searched results with different colors or indicators for predefined criteria, such as initial inspection due and reinspection due | |||
| 14 | Include basic data objects such as Facility, Inspection, Owner, License, User, Violation, Health District, Facility Type, Predefined Statement, etc. | |||
| 15 | Include necessary and customized forms with tailored data fields for creating, reading, updating, and deleting (CRUD) for the data objects mentioned above | |||
| 15.1 | Signature input is needed | |||
| 15.2 | Violation sets toggle depending on facility type | |||
| 15.3 | Allow staff to securely upload and attach various formats, such as PDF, Word, and common picture formats | |||
| 15.4 | Keep record change logs | |||
| 15.5 | Lock editing for certain user roles after a certain time | |||
| 15.6 | Allow autosaving to avoid data loss due to weak connectivity | |||
| 15.7 | Integrate with City of Philadelphia Address Information System (Desired) | |||
| 16 | Have a flexible GIS (graphic information system), Esri ArcGIS preferred, reporting capability for all facilities in the database | |||
| 17 | Provide specific and customized ad-hoc and auto-populated reports, such as the License Eligibility Report and the Radar Report | |||
| 18 | Allow staff to export inspection reports in HTML, PDF, and email with PDF formats | |||
| 18.1 | No upper limit on emails per day | |||
| 18.2 | Standard protocol for email proxy | |||
| 19 | Provide basic real-time reporting capabilities | |||
| 20 | Existing functionality – carry over all functionalities from the current system to the new system (Food Inspection, Environmental Engineering (EE) Inspection, Complaint, Self-configuration capability by internal staff (predefined statement, violation category, email message, dropdown fields, etc.) | |||
| 21 | Allow limited look-up functionality for the public to search for the most recent inspectional reports | |||
| 21.1 | Preventing web scraping | |||
| 22 | Accommodate dynamic web traffic for report lookup | |||
| 23 | API (application platforming interface) Access | |||
| 24 | API library functionality | |||
| 24.1 | GET endpoints exposure for most of the data | |||
| 24.2 | Allow customized access level | |||
| 24.3 | Allow customized endpoints | |||
| 24.4 | Encrypted and secure endpoints | |||
| 25 | Must convert all existing data (2 GB) and files (60 GB) from the current system to the new system without any data loss | |||
| 26 | No upper limitation on future data and file size growth | |||
| 27 | Have a daily backup plan without record locking | |||
| 28 | Allow Admin users to access daily backup files or provide read access to the backend data that allows advanced query | |||
| 29 | Enable data encryption at rest and in transit | |||
| 30 | Have a disaster recovery plan | |||
| 31 | The proposed solution should provide near-real-time data exchange mechanisms with other external systems. | |||
| 32 | In addition, supporting data architecture must support data sharing with internal PDPH data sets and data sets owned by EHS external partners. | |||
| 33 | Provide initial system training | |||
| 34 | Ensure 99.9% uptime | |||
| 35 | Provide a customer relationship management platform for reporting issues and submitting change requests | |||
| 36 | Provide timely and effective maintenance, updates, and changes upon request | |||
| 37 | Allow up to five (5) minor feature changes per contract year without extra charges | |||
| 38 | Create a centralized internal and public portal for the following program areas (Food Safety Certification Application, Plan Review Permitting/Inspection, Special Event Permitting/Inspection, Body Art Permitting/Inspection, Pool Permitting/Inspection, Tobacco Permitting/Inspection) | |||
| 38.1 | Create and manage a single sign-on account according to the city’s standard | |||
| 38.2 | Configure a protocol for proxy accounts (accountants representing the customer and businesses representing the client) | |||
| 38.3 | Submit application information to different program areas | |||
| 38.4 | New and renewal permits | |||
| 38.5 | Check the status of the application | |||
| 38.6 | Communicate questions through the system | |||
| 38.7 | Submit additional material required through the system | |||
| 38.8 | Support various file formats and file sizes | |||
| 38.9 | Able to generate, download, and print a permit | |||
| 38.10 | With a limitation on the number of views/printings | |||
| 38.11 | Able to pay the invoice online through the Kubra vendor | |||
| 38.12 | Able to handle money order submission | |||
| 38.13 | Search, view, edit, and process the received applications (with email notifications) | |||
| 38.14 | Communicate with the applicant through the system | |||
| 38.15 | Link existing and add new inspection records to the application | |||
| 38.16 | Link existing and add new owner/licensee records to the application | |||
| 38.17 | Link existing and add new invoice and payment information to the application | |||
| 38.18 | Able to send an automatic email reminder about the permit expiring | |||
| 38.19 | Able to batch view and print permits | |||
| 38.20 | Able to view all histories on address-based search | |||
| 38.21 | Able to void and cancel a permit |
File details come from the government source that posted it. Updated .