Appendix D.PDPH.EHS.RFP.IntegratedEHregcompmgmtsystem_v3 11052026.xlsx

XLSX spreadsheet 13 KB Posted

Attached to
Integrated Environmental Health and Regulatory Compliance Management System.
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 IDRequirement DescriptionCompliance StatusCommentAdditional Cost
1Provide a SaaS (Software-as-a-Service) customized solution to meet all requirements in this RFP (request for proposal)
2Support major browsers such as Chrome and Edge
3Have a responsive design for tablets, phones, and computer screeens
4Requires no installation or any special changes to the browswer or device setting
5Have 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
6Have different roles, such as View, Write, Admin, for different users to access different levels of data
7Allow Admin users to make changes throughout the system, such as user accounts, reports, facilities, predefined statements, etc.
8Have logs of user activities, and allow Admin users to run audit reports
9Allow traffic of up to 100 users simultaneously using the service without latency
10Integrate with City of Philadelphia Azure Active Directory (Desired)
11Have a user-friendly interface with robust search functionality such as partial address, facility name, inspection result, health district, etc.
12Allow staff to export searched results as CSV (comma-separated values) or Excel format
13Show searched results with different colors or indicators for predefined criteria, such as initial inspection due and reinspection due
14Include basic data objects such as Facility, Inspection, Owner, License, User, Violation, Health District, Facility Type, Predefined Statement, etc.
15Include necessary and customized forms with tailored data fields for creating, reading, updating, and deleting (CRUD) for the data objects mentioned above
15.1Signature input is needed
15.2Violation sets toggle depending on facility type
15.3Allow staff to securely upload and attach various formats, such as PDF, Word, and common picture formats
15.4Keep record change logs
15.5Lock editing for certain user roles after a certain time
15.6Allow autosaving to avoid data loss due to weak connectivity
15.7Integrate with City of Philadelphia Address Information System (Desired)
16Have a flexible GIS (graphic information system), Esri ArcGIS preferred, reporting capability for all facilities in the database
17Provide specific and customized ad-hoc and auto-populated reports, such as the License Eligibility Report and the Radar Report
18Allow staff to export inspection reports in HTML, PDF, and email with PDF formats
18.1No upper limit on emails per day
18.2Standard protocol for email proxy
19Provide basic real-time reporting capabilities
20Existing 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.)
21Allow limited look-up functionality for the public to search for the most recent inspectional reports
21.1Preventing web scraping
22Accommodate dynamic web traffic for report lookup
23API (application platforming interface) Access
24API library functionality
24.1GET endpoints exposure for most of the data
24.2Allow customized access level
24.3Allow customized endpoints
24.4Encrypted and secure endpoints
25Must convert all existing data (2 GB) and files (60 GB) from the current system to the new system without any data loss
26No upper limitation on future data and file size growth
27Have a daily backup plan without record locking
28Allow Admin users to access daily backup files or provide read access to the backend data that allows advanced query
29Enable data encryption at rest and in transit
30Have a disaster recovery plan
31The proposed solution should provide near-real-time data exchange mechanisms with other external systems.
32In addition, supporting data architecture must support data sharing with internal PDPH data sets and data sets owned by EHS external partners.
33Provide initial system training
34Ensure 99.9% uptime
35Provide a customer relationship management platform for reporting issues and submitting change requests
36Provide timely and effective maintenance, updates, and changes upon request
37Allow up to five (5) minor feature changes per contract year without extra charges
38Create 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.1Create and manage a single sign-on account according to the city’s standard
38.2Configure a protocol for proxy accounts (accountants representing the customer and businesses representing the client)
38.3Submit application information to different program areas
38.4New and renewal permits
38.5Check the status of the application
38.6Communicate questions through the system
38.7Submit additional material required through the system
38.8Support various file formats and file sizes
38.9Able to generate, download, and print a permit
38.10With a limitation on the number of views/printings
38.11Able to pay the invoice online through the Kubra vendor
38.12Able to handle money order submission
38.13Search, view, edit, and process the received applications (with email notifications)
38.14Communicate with the applicant through the system
38.15Link existing and add new inspection records to the application
38.16Link existing and add new owner/licensee records to the application
38.17Link existing and add new invoice and payment information to the application
38.18Able to send an automatic email reminder about the permit expiring
38.19Able to batch view and print permits
38.20Able to view all histories on address-based search
38.21Able to void and cancel a permit

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