Platform capabilities
How the repository covers each architecture domain the City listed, and whether each capability is native to the platform, a third-party product, or a separately licensed add-on. "In this repository" names the screen that shows it working.
| Domain | Capability | Provided | In this repository |
|---|---|---|---|
| Data ingestion and integration | SQL Server, PostgreSQL, APIs, flat files, SharePoint, ArcGIS, SaaS; Tyler Munis, Cityworks, EnerGov, ArcGIS | Native connectors; third party only for niche SaaS | Sources and connectors |
| Batch, incremental, change data capture, API and near real time ingestion | Native | Run steps (method per dataset) | |
| Schema change detection and versioned source mappings with replay | Native (pipeline framework) | Run R-20261106-0200 | |
| ETL and ELT | Orchestration, scheduling, pipeline monitoring, logging, error handling, alerting | Native within the CDR platform; no separate ETL product | Pipeline runs, Alerts |
| Data storage and organization | Structured, semi-structured (JSON) and geospatial types; storage scales separately from compute | Native | Raw layer, spatial parcels |
| Development, test and production; encryption at rest; backup and recovery; raw, cleansed and curated layers serving department views from one source | Native | Operations, Catalog | |
| Transformation and processing | SQL for cleansing and curation; Python for orchestration and extraction; Spark available for large workloads; low-code available for analysts | Native (SQL, Python); Spark and low-code native on the recommended platforms | Metric SQL |
| Data modeling | Dimensional facts and dimensions; documented business rules and a shared semantic layer for metric definitions; City data standards applied | Native; semantic model in Power BI | Metric migration, Data standards |
| Analytics and reporting | Power BI integration; spatial data and ArcGIS integration | Native connector; Power BI licenses already held by the City | Department views (map) |
| Security and access | RBAC, SSO, MFA, encryption, network isolation, private endpoints, auditing, row and column security, dynamic masking, sensitive data classification; government cloud deployment options | Native; SSO and MFA through the City identity provider | Access and roles |
| Metadata and documentation | Catalog, lineage, classification, ownership, metadata management | Native catalog; a separately licensed enterprise catalog is optional | Catalog entry with lineage |
| Data quality and validation | Automated rules, alerts, reconciliation checks, exception handling (quarantine) | Native (rules as code) | Data quality, Quarantine |
| Scalability and expansion | Compute per workload class, multi-cluster for BI peaks, new sources added from documented patterns | Native | Cost and consumption |
| Monitoring and support | Pipelines, failures, performance, usage and cost | Native | Operations, Cost |
| Disaster recovery | RPO 15 minutes, RTO 4 hours, nightly snapshots plus log backup, paired region copy, quarterly restore tests, 99.9% availability for department views | Native | Recovery tests |
This repository runs on stand-ins for the production services (PostgreSQL with PostGIS for the warehouse, a Python orchestrator for the pipeline service). Platform selection against the City's criteria happens in Phase 0; the patterns shown here carry to each recommended platform.
Data as of run R-20261111-0200, finished 11/11/2026 02:13 Central. Curated layer: curated schema.