A useful procurement dashboard connects a public record to a practical decision: identify relevant work, understand its stage, locate it when the evidence permits, and verify the opportunity at its source.
Counts describe the November 10, 2026 snapshot. Forecast counts include City departments and partner agencies; the demo defaults to City departments. These figures are not a verified count of every City contract.
01 / THE DECISION
One Explorer, Several Procurement Stages.
The Command Center is designed for public-sector leaders, procurement teams, and prospective suppliers. Its central question is: What work is available or anticipated, which public records describe the contract portfolio, and what can location add to the decision?
Multi-select contract-type controls allow Professional Services to be viewed alongside Public Works, Services, Supplies & Equipment, Concessions, and records awaiting a reliable classification. A contract category with no loaded records remains a valid filter; the interface does not invent examples to fill the category.
The Opportunity Pipeline begins with open solicitations and forecast opportunities. Contract Portfolio brings together executed vendor / term listings, notices of intent, and an explicitly historical commodities snapshot. All Records makes the loaded records searchable together. Stage labels remain visible in every view.
02 / THE EVIDENCE
Public Sources With Visible Coverage.
The application draws from public City listings rather than private vendor accounts. Direct eContractPhilly and PHLContracts records support the current opportunity and professional-services views. The Contracts Hub feed supplies additional fields only when its bid identifier matches a directly collected PHLContracts record.
| Source | Role | Interpretation |
|---|---|---|
| eContractPhilly Opportunities | Professional-services pipeline | Includes open, closed, and cancelled records returned by the list. |
| eContractPhilly Executed Listings | Vendor and contract-term evidence | One row is a vendor / opportunity / term listing; values are not provided in every row. |
| eContractPhilly Notices of Intent | Procurement-stage visibility | A notice of intent does not by itself establish contract execution. |
| PHLContracts Open Bids | Competitive opportunity listings | All returned pages are reconciled against the reported result count. |
| Fall 2026 Procurement Forecast | Anticipated work and estimated timing | Includes City departments and partner agencies. Plans, timing, and values may change. |
| Commodities Contracts · FY2016 Q1 | Historical contract analysis | A quarter-specific published snapshot; not a current active-contract register. |
| Capital Projects Finder | Location and project context | Context projects are separate from open procurement opportunities. |
| Council Districts · 2024 | Official geographic boundaries | District assignment uses published City polygons. |
03 / THE DATA MODEL
Keep the Record’s Meaning Intact.
Records retain their source identifier, source URL, procurement stage, department, contract type, available dates, published value, and reporting period. Vendor names are carried only when the source supplies them. Missing values remain unknown; a zero amount is retained as a reported zero.
Bid IDs reconcile overlapping PHLContracts and Contracts Hub information. Executed listings keep their vendor and term grain. Forecast rows are retained separately because similar project names can represent different trades or solicitations. A forecast is linked to an open bid only when a dependable identifier relationship is available.
A single opportunity can lead to several vendors or contract terms. A notice, a forecast, and a historical contract row can concern related work. Adding all rows together would not produce an accurate citywide contract count or spending total.
Amounts retain their basis: solicitation estimate, forecast range, or historical contract amount. The demo does not combine those bases into a City spending total. Value-band filters use overlap: a published $250,000–$1 million range can match any selected band that overlaps it. Anticipated solicitation months are distinct from response deadlines.
04 / THE GEOGRAPHY
Map Only What the Evidence Supports.
The map uses official 2024 Council district polygons. Procurement locations are conservative named-facility associations between record text and the City’s public project-location data. The initial associations identify the Dell Music Center and Simons Recreation Center. A pin represents the named facility, not a surveyed construction footprint.
District filtering applies to records with a linked facility. Records without a dependable location remain in the explorer under All Locations or Location Not Identified. Supplier office addresses, billing addresses, and department headquarters are not substituted for work locations.
The Capital Project Context layer displays published project-location rows separately. It helps explain the broader municipal project environment. Its points are not claims that a project is seeking bids, that it has an awarded contract in the dataset, or that it matches the selected procurement type.
05 / THE INTELLIGENCE
Explain Why a Record Deserves Attention.
Decision-support signals are calculated from the filtered evidence. The first version identifies open opportunities due within 14 days, anticipated solicitations from the snapshot month onward, departments with the largest matching record counts, and the share of records with an identified facility.
These signals are transparent rules. A high listing count does not establish supplier risk, market concentration, noncompliance, or excessive spending. Such conclusions require additional award, payment, performance, and participation evidence.
- Select Professional Services and Public Works together.
- Choose a department, value band, or procurement stage.
- Inspect an opportunity and confirm its dates at the official source.
- Use the map for records with an identified facility; switch layers for capital-project context.
- Export the filtered records with source links for further review.
06 / THE CONTROLS
Reconcile, Trace, and Disclose.
Collection validates expected source-table structure and reconciles PHLContracts pagination. Normalized record IDs are unique. Geography requires all ten district features. Required-source collection failures stop a refresh so the last published snapshot is retained. Source counts and limitations are available inside the dashboard.
Deadlines are assessed against the snapshot date in America/New_York. The interface does not promise continuous updates. A source’s historical coverage and retrieval date do not prove that every City contract has been published or ingested.
Exports preserve source links, stage, dates, value basis, and period. Text fields that could be interpreted as spreadsheet formulas are escaped. The public app uses no City credentials, vendor logins, client data, or fabricated procurement records.
07 / THE NEXT EXPANSION
Build Toward Verified Citywide Coverage.
The next data expansion is the current PHLContracts executed / blanket contract register, followed by special-process RFP/RFI postings and relevant PennDOT ECMS opportunities. Each source must be checked for result limits, update patterns, identifier relationships, and contract grain before it is added to the combined portfolio.
Further location work can add verified site addresses and multi-site project areas. Supplier participation, spending concentration, payments, and contract-performance analytics should follow only when appropriate, current records are available and the measures reconcile.
This proof of concept demonstrates how Quant Strata connects data engineering, business intelligence, geospatial analysis, and executive decision support. It does not imply a City engagement, endorsement, or verified procurement outcome.
Bring the Decision Into View.
Explore the public-data demonstration or discuss a procurement analytics engagement.