Requirements_Matrix_Codification_(1)_(2).xlsx
XLSX spreadsheet 29 KB Posted
- Solicitation number
- 2023-RFP-279
- Issued by
- Allegheny County, Philadelphia City, Pennsylvania
About this file
The file is a Requirements Matrix for the City of Pittsburgh's municipal code codification and publication project. The city is seeking a Software-as-a-Service (SaaS) provider to perform comprehensive code analysis, review, electronic publishing, and web hosting services for municipal codes, with potential future expansion to GIS integration. The requirements matrix details 36 mandatory functional requirements spanning general features such as paper supplementation, robust search capabilities, online hosting, language translation, ADA compliance, system integration, and data migration. Key technical specifications include the ability to confirm legislation receipt, create cross-references, maintain legislative integrity, impose standard style conventions, and codify new legislation within two weeks.
The pricing section of the requirements matrix indicates a comprehensive cost structure covering application costs, training, implementation, module pricing, integration expenses, and data conversion. The matrix suggests a five-year total cost model with detailed breakdowns for one-time and ongoing expenses, including potential hardware costs. The project emphasizes configurability, with options for vendor and city staff configuration, and potential customization. The solution must interface with existing systems like Legistar and support features such as quarterly zoning code downloads in PDF, text document exports, and dedicated account management. The matrix underscores the city's need for a flexible, technologically advanced solution that can efficiently manage and publish municipal code documentation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Pittsburgh_Municipal_Code_Codification_and_Publication_(Addendum_#2_Revision).pdf | ||
| Technical_Requirements_2023-2024.xlsx | XLSX spreadsheet |
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
Functional Requirements
| Requirement ID | Requirements | |
| (All of the items apply to any subcontractors that work on the solution. ) | Must Have or Nice to Have | System Capability |
(select from dropdown)
| Comments: | |||
| 1 | General Features (Required) | ||
| 1.1 | City Clerk's office to receive paper supplement by EOY | Must | |
| 1.2 | ability to confirm receipt and completion of legislation with live links to take you to the current updates. Text and email notification to multiple recipients | Must | |
| 1.3 | robust search feature: ablity to search standard language, code,ordinances, munidocs | Must | |
| 1.4 | Enhanced Graphics | Must | |
| 1.5 | online hosting and maintenance | Must | |
| 1.9 | language translation | Must | |
| 1.10 | ADA Compliance | Must | |
| 1.11 | ability to interface or intergrate with existing systems or platforms: |
Legistar
| GIS | Must | ||
| 1.12 | system or solution must be able to migrate existing city data related code | Must | |
| 1.13 | Acknowledge receipt of all materials | Must | |
| 1.14 | Verify adoption of all legislation, including date of action by governing body | Must | |
| 1.15 | Review legislation and distinguish between code and non-code material | Must | |
| 1.16 | update record of legislation received and it's disposition (Disposition list) | Must | |
| 1.17 | request any missing legislation/missing pages | Must | |
| 1.18 | impose or utilize the adopted flexible section numbering system that allows for later changes | Must | |
| 1.19 | determine proper placement of legislation within code | Must | |
| 1.20 | create/modify chapter, article and/or section titles | Must | |
| 1.21 | add historial annotations | Must | |
| 1.22 | add any necessary cross references | Must | |
| 1.23 | include editorial notes to sections that require additional explanation | Must | |
| 1.24 | correct any misspellings so that searchability is not compromised | Must | |
| 1.25 | impose a distinctive style for defintions, to aid code user in quickly finding the meaning of a particular term | Must | |
| 1.26 | maintain legislative integrity by following the orignial tables and graphics and, where necessary, improving the presentation so that the information contained therein is easily accessible | Must | |
| 1.27 | impose standard internal section organizational hierarchy | Must | |
| 1.28 | impose standard style conventions | Must | |
| 1.29 | confirm accurary of internal references; correct as necessary and appropriate | Must | |
| 1.30 | Zoning code to be accessible quarterly via download in PDF format and printed | Must | |
| 1.31 | Download code sections in plain text into word document | Must | |
| 1.32 | Code comparative table and supplement history table | Must | |
| 1.33 | update code index | Must | |
| 1.34 | dedicated account manager | Must | |
| 1.35 | codify new legislation within 2 weeks and receive notification if more time is needed | Must | |
| 1.36 | Robust linking to all scales of the code - Titles, Chapters, Sections, Sub-sections, etc - to specific information to be sent as an email link. | Must |
Cost & Pricing Requirement ID Requirements (All of the items apply to any subcontractors that work on the solution. )
| General Features (Required) | |
| 1 | Cost and Pricing |
| 1.1 | Application Costs |
| 1.2 | Trainng Costs |
| 1.3 | Implementation Costs |
| 1.4 | Price by Module |
| 1.5 | Intergration Costs |
| 1.6 | Data Conversion |
| 1.7 | 2022 Priorities |
| 1.8 | Complete solution implementation |
| 1.9 | Time, Attendance, Tax Modules 5 year costs |
| 1.1 | Detail One time costs |
| 1.11 | Detail ongoing costs |
| 1.12 | Hardware Costs |
Index
| Core Capability |
| Configurable by Vendor |
| Configurable by City Staff |
| Requires Customization |
| Provided in Conjunction with a 3rd Party |
| Not Applicable |
Data Validation
| Core Capability |
| Configurable by Vendor |
| Configurable by City Staff |
| Requires Customization |
| Not Applicable |
File details come from the government source that posted it. Updated .