City Hall planning unit
1825 Strand Way · 17,924 SF · 2006 construction year in the working baseline. Confirm the physical boundary, subsequent renewals and GIS linkage.
RECOMMENDED ASSET MODEL · CONSULTANT REVIEW DRAFT 0.3
See the whole site.
Understand every layer.
A connected structure for capital planning today, with a clear path to operational asset intelligence.
City Hall first. One model for all three types.
Scope confirmation and GIS mapping remain open.
Review the proposed structure and fields, then work through City Hall, recreation and bulkhead samples in sequence. Source evidence stays linked to the existing master keys.
Source baseline: October 23, 2026Scope confirmation and GIS mapping remain open.
CITY HALL · PROPOSED OUTPUT FOR APPROVAL
One complete specification. Review before rollout.
Approve the structure, every proposed field, GIS handoff and capture depth before we apply this model across the remaining assets.
Approval requested: the proposed output format and capture approach. Historical values remain subject to technical review. Approval does not adopt replacement estimates or authorize additional services. Return the workbook with decisions and comments; this page does not record official approval.
19 source observations
Five legacy component/system observations and 14 HVAC entries. Proposed physical groupings are review overlays. They do not change source keys or establish a complete inventory.
AHU-4 air handler
Use one source-linked equipment entry to review the full recommended operating fields. Blank nameplate, maintenance and lifecycle values remain visible.
Review the 12 decisions and City Hall source questions
The workbook provides editable decision, comment, reviewer and date columns. Resolve or explicitly defer open decisions when returning the review.
Review proposed system groupings and replacement logic
Classification describes an asset. Physical parentage defines the replacement boundary. These proposed system labels have no adopted system IDs or classification codes yet.
Whole-building replacement uses a reviewed full-replacement basis, reconciled against a complete elemental inventory. Individual renewal events have their own timing and access costs. The 2015 foundation observation contains $3,000,000 and needs a boundary check. Historical HVAC system costs may overlap individual equipment. No cost rollup or replacement life is adopted here.
All proposed fields
One row per table and field. City Hall values illustrate the site/building; component examples use AHU-4. All 19 observations and their blank fields are retained in the workbook’s Source record values sheet.
Yellow = blank / unadopted example valueTemplate = proposed fields with no linked recordProduct support ≠ populated data or agreed scope
Complete tables and source linkage
Each table can be exported with all columns. Empty tables export header-only templates. No source records are created for the approval example.
The owner filter selects the recommended maintenance authority. GIS can still contain shared summaries of IWMS-owned records. Use GIS handoff to review the complete proposed GIS content for one asset.
Current deliverable / supporting recordRecommended structure, capture depth to agreeClick a node for fields and evidence. Expand groups with +.
Hierarchy illustrates recommended relationships. Classification branches are not verified physical assets. Blank values remain unadopted.
90
Proposed whole-asset planning rows
City scope confirmation pending
371
Historical component records
Observations may overlap; not a verified unique count
Recommended field definitions
GIS and operational destinations identified
ONE ASSET · PROPOSED GIS STRUCTURE
A mapped asset, with clear data ownership
The current asset selection drives this example. Our proposal places the spatial feature and adopted planning attributes in GIS. The asset register maintains the detailed asset and lifecycle records.
GIS
Site and asset geometry, coordinate system, feature identifiers and spatial relationships.
Stable master keys
Selected attributes & references
One authority per field
Selected attributes & references
One authority per field
IWMS / asset register
Asset inventory, condition evidence, lifecycle forecasts and operational history.
Recommendation for agreement: “Owner” means the system where a record or field is maintained, not the owner of the physical property. IWMS denotes the recommended operating asset register; it does not assume a long-term software purchase or ongoing FMiQ-One hosting commitment. The current contract can deliver GIS features and associated attribute tables before a long-term system is selected.
Proposed records and linkages
Whole-asset fields proposed for GIS
The required / preferred contract fields remain in the GIS handoff even where the asset register is their recommended maintenance authority. Supporting governance fields travel with them.
Proposed exchange rule: maintain GIS-owned fields in GIS. Publish reviewed asset-register values into GIS summaries with assessment date and source references. The draft does not implement synchronization. Confirm field names, identifiers, refresh frequency and responsibilities with the City.
THE PROPOSED DATA CONTRACT
Fields for each level
Our recommended structure leads the design. Existing City GIS fields and FMiQ-One mappings will be retained or reconciled where practical.
Product support (LIVE / EXPAND / NEW) comes from the supplied FMiQ-One field document. It does not indicate Coronado data completeness or current capture scope. Mappings distinguish documented paths, review transformations and proposed additions. Empty related tables are templates.
SAME KEYS. COMPLETE DETAIL.
Review the records behind the visual
Exports include every column, including fields not highlighted in the explorer. Empty tables export their complete recommended headers.
TRANSPARENT ASSUMPTIONS
How replacement decisions connect
Each asset class has its own life and cost basis. A site aggregates defined assets; it does not receive a single artificial replacement life.
01 · EvidenceSources, dates, quantities, condition
02 · Technical judgmentLife references and documented adjustments
03 · Estimate & eventCost basis, timing and confidence
04 · Controlled rollupDefined boundaries, each cost counted once
METHOD ILLUSTRATION
Installed replacement estimate
Enter your own assumptions. This calculator does not populate or adopt Coronado asset costs.
Additional taxes, location factors and escalation require their own documented basis. Allowances below are absolute dollar amounts.Two complementary views: Whole-asset replacement value uses a consistent full-replacement basis. Capital renewal events price work at its own timing and access conditions. Individual occupied-building renewals need not sum to a new-building estimate. Maintenance can support a life adjustment only with evidence; it does not automatically reset life.
CONNECTED RECORDS · ONE AUTHORITY PER FIELD
Physical parents, locations and classifications
The physical hierarchy defines the replacement boundary. Location and classification describe the asset through separate links. Operational records attach to the persistent asset identity.
Physical hierarchySite→Whole planning asset→System / assembly→Component / equipment
ClassificationAsset reference→UNIFORMAT code & labelsSeparate classification reference, not physical parentage
LocationGIS feature / lat-longFacility / floor / spaceZone / area servedDrawing / pin x-y
Related activityAssessments & evidencePM tasks & schedulesDeficiencies & work ordersCosts & capital events
Coordinates: latitude/longitude describe geographic location. Floor-plan spatial_pin x/y describe a position on a referenced drawing. FMiQ-One geographic mapping capability is reported; its exact latitude/longitude API paths, storage level and coordinate conventions remain to be confirmed.
Stable identity across systems
External master keysCOR-S site · COR-A asset · T1 planning row
FMiQ-One UUIDsid · facility_id · client_id
City GIS referencesFeature identifier · geometry · CRS
The crosswalk preserves these as separate identifiers. Work-order asset_id references the product asset UUID. No product UUIDs or GIS coordinates have been invented.
Sample sequence
Remaining mapping decisions
This is a client-review model and export specification. It does not create product records, schedule maintenance or synchronize GIS. The three samples will establish reviewed mappings and calculation assumptions before portfolio-wide application.