|
Engineering × TechnologyIn DevelopmentCASE // 01

Facility Management Platform

A digital platform I am developing to bring asset management, work orders, preventive maintenance, technicians, inventory, and operational workflows into one environment.

Discipline
Systems Engineering & Software
Role
System Architect & Lead Developer
Status
In Development
Architecture Focus
Relational Asset Registry & Operations
SYSTEM_MAP // FACILITY_TOPOLOGY
Conceptual Explanatory Flow
01
FACILITYFacility
02
SYSTEMSSystems
03
SPACESSpaces
04
ASSETSAssets
Core Anchor
05
MAINTENANCEMaintenance
06
WORK_ORDERSWork Orders
07
TECHNICIANSTechnicians
STATUS: IN_DEVELOPMENT // SYSTEM_LAYER: RELATIONAL_COREENTITY_GRAPH // CONNECTED_STRUCTURE
Conceptual explanatory diagram reflecting relationship flow from facility to field technician — not claiming final technical production deployment.
The Problem

What happens when facility operations are spread across different systems and tools?

Facility management involves an interconnected environment of assets, systems, spaces, maintenance activities, work orders, technicians, inventory, and operational data.

When this information and these workflows are fragmented, maintaining a clear picture of facility conditions, ongoing work, and operational decisions becomes more difficult.

Engineering Observation

The challenge in facility operations is rarely a lack of software, but rather fragmentation across siloed tools, dispersing equipment history and operational context across disconnected channels.

FRAGMENTED_STATE // ISOLATION
FRICTION
01
Asset records in disconnected spreadsheetsStale data without spatial grounding
02
Work orders via chat apps & callsLost trails & delayed field responses
03
Preventive maintenance schedules isolatedRoutines unlinked to spare parts logs
04
Dispersed inventory & reportingNo unified picture of real-time readiness
Operational friction & fragmented decisions
Conceptual illustration of data and workflow fragmentation in siloed operational setups.
The Idea

What if the elements of a facility could become part of one connected system?

The idea began with creating a digital environment that connects a facility with its systems, spaces, assets, and maintenance operations, allowing information, relationships, and tasks to become part of one structure that can evolve over time.

01 // PARADIGM

Connected context over scattered logs

Every asset links directly to its space, engineering system, and maintenance history.

RELATIONAL_SYSTEM_PRIMITIVE
02 // PARADIGM

Cohesive operational loops

Linking work orders to technicians, parts, and real-time field logging seamlessly.

RELATIONAL_SYSTEM_PRIMITIVE
03 // PARADIGM

Progressive extensible architecture

An architecture starting from clean fundamentals, built to scale toward BMS telemetry.

RELATIONAL_SYSTEM_PRIMITIVE
Structuring the Facility

From Portfolio and Facility to the Atomic Operational Asset

A conceptual information hierarchy reorganizing operational elements into a logical sequence linking every asset to its spatial and functional context.

SCHEMA_TREE // FACILITY_TO_ASSETCONCEPTUAL_LEVELS: 06
L1
Portfolio / OrganizationOverarching organizational entity
portfolioId
L2
FacilityDistinct building or physical site
facilityId
L3
SystemsMajor engineering systems (HVAC, Electrical, Plumbing)
systemId
L4
SubsystemsDistribution circuits and specific functional loops
subsystemId
L5
SpacesPhysical rooms, zones, and usable spaces
spaceId
L6
AssetsMaintainable equipment and physical apparatus
assetId
Conceptual sequence illustrating the operational placement of an asset within its physical and engineering context.
RELATIONAL_BINDING // NOT_ISOLATED

The Asset Within a Wider Facility Context

Rather than storing equipment as a detached flat record, the schema utilizes relational identifiers anchoring every operational transaction to its precise location, energy loop, and host system.

facilityIdFacility Identifier

Anchors the asset within its physical site

systemIdSystem Identifier

Links the asset to its engineering discipline

subsystemIdSubsystem Identifier

Specifies the distribution circuit or subsystem

spaceIdSpace Identifier

Documents precise room/zone location for technicians

Architectural Note:This hierarchy represents the logical information schema, engineered to accommodate future system expansions without refactoring foundational root entities.
Global Asset Registry

An asset is more than a name in a list.

The architecture treats an asset as an active entity embedded within its engineering and spatial context and operational history, rather than an isolated entry in a spreadsheet.

Direct relational linkage to Facility, Engineering System, Subsystem, and Physical Space.

Rapid discoverability by engineering classification, spatial location, or operational state.

Data structure prepared to attach maintenance history and technical logs without data duplication.

Current project focus: Global Asset Registry architecture in active development.
RELATIONAL_TOPOLOGYASSET_IN_CONTEXT
PARENT_CONTEXTFACILITYfacilityId: "FAC-01"
ENGINEERING_DOMAINENGINEERING SYSTEMsystemId: "SYS-HVAC"
FUNCTIONAL_CIRCUITSUBSYSTEMsubsystemId: "CHW-LOOP"
PHYSICAL_ZONEPHYSICAL SPACEspaceId: "RM-B102"
TARGET // ENTITY
OPERATIONAL_ASSETOPERATIONAL ASSETassetId: "AST-AHU-04"
Schematic diagram showing the convergence of engineering and spatial vectors upon the asset.
Operational Ecosystem

From asset to operation.

How operational work areas connect within the platform across a cohesive system architecture.

In Development (Active Phase)
Future Direction (Planned)
In Development
MOD_ASSETS

Asset Management

Asset structuring, global registry, technical specifications, and metadata.

ACTIVE_WORKSTREAMassets
In Development
MOD_WO

Work Orders

Task creation, assignment, and dispatch for corrective maintenance.

ACTIVE_WORKSTREAMwork-orders
In Development
MOD_PM

Preventive Maintenance

Inspection schedules and periodic maintenance plans for critical assets.

ACTIVE_WORKSTREAMpreventive-maintenance
In Development
MOD_TECH

Technicians & Teams

Trade-based work allocation and field maintenance mobility workflows.

ACTIVE_WORKSTREAMtechnicians
Future Direction
MOD_INV

Inventory & Spare Parts

Tracking spare parts consumption and maintenance stock availability.

PLANNED_PHASEinventory
Future Direction
MOD_OPS

Operations & Insights

Centralized operational views for facility health and system readiness.

PLANNED_PHASEoperations
Note: Modules designated (In Development) represent current engineering focus, while (Future Direction) modules follow in subsequent phases.
Scalability

From home maintenance to larger facility environments.

Designing an adaptable data architecture that avoids unnecessary overhead for simple cases, while scaling smoothly to accommodate multi-system facility environments.

This progression represents design ambition and architectural direction, not past deployment history.

Home

01
Individual assets and direct spaces

Tracking HVAC units, pumps, and basic fixtures without unnecessary hierarchical overhead.

Building

02
Multi-floor structures and shared systems

Managing utility rooms, main distribution panels, and standard maintenance loops.

Commercial Facility

03
Centralized plants and continuous operations

Central air handlers, chillers, elevators, and specialized technical teams.

Campus / Complex Environment

04
Multi-facility portfolio and interconnected sites

Unified asset governance across multiple buildings sharing operational resources.

System Principles

Principles Shaping the System

Guiding principles I adhere to while architecting the platform, designing workflows, and structuring data relationships.

PRINCIPLE // 01Connected Data

Connected Data

Data points are not isolated islands; every record links contextually to its engineering, spatial, and operational environment.

ARCHITECTURAL_GUIDELINE
PRINCIPLE // 02Operational Clarity

Operational Clarity

Minimizing visual noise and surfacing exactly what the operator or technician needs to make decisions and act.

ARCHITECTURAL_GUIDELINE
PRINCIPLE // 03Scalability

Scalability

An architecture capable of handling a modest setup or a complex facility without restructuring foundational primitives.

ARCHITECTURAL_GUIDELINE
PRINCIPLE // 04Usability

Usability

Designing pragmatic workflows that accommodate field technicians on mobile as naturally as engineers on desktop.

ARCHITECTURAL_GUIDELINE
PRINCIPLE // 05Extensibility

Extensibility

A modular codebase allowing clean integration of future extensions, including Building Management Systems (BMS).

ARCHITECTURAL_GUIDELINE
Building the Experience

Interfaces Designed for Real Operational Perspectives

Facility operations involve diverse roles with distinct informational needs. The experience is structured to give each perspective the right tools without clutter.

Operational System Perspectives:
ROLE // 01

Facility & Operations Management

High-level overview, system readiness, and priority dispatch

Key Workflows
Monitoring preventive maintenance cycles
Tracking critical work orders and response times
Governance over asset hierarchy and site data
ROLE // 02

Maintenance Team & Supervisors

Task scheduling, technician assignment, and execution quality

Key Workflows
Configuring periodic inspection routines
Dispatching work orders based on trade
Reviewing completion logs and field remarks
ROLE // 03

Field Technicians

Fast asset lookup and mobile execution logging on site

Key Workflows
Locating asset, its exact space, and recent logs
Updating job progress and recorded parts
Submitting technical observations and telemetry notes
ROLE // 04

Project & Administrative Views

General governance and overarching project coordination

Key Workflows
Portfolio-level structure management
Aligning maintenance with asset renewal phases

Architectural Interface Views Under Development

Interface Architecture
Abstract Representation
GLOBAL_ASSET_REGISTRY // ARCHITECTURE
Search: "AHU", "Chiller", "RM-B102"...
Filter
Asset ID / Name
System / Circuit
Location / Space
Operational State
AST-AHU-01Main Air Handling Unit
SYS-HVAC // LOOP-A
ROOF-ZONE-01
Operational
AST-CHW-02Secondary Chilled Water Pump
SYS-HVAC // CHW-DIST
MECH-ROOM-B1
PM Scheduled
AST-MDP-04Main Electrical Dist Panel
SYS-ELEC // FEED-02
ELEC-ROOM-GF
Verified Ready
RELATIONAL_RESOLVER: FACILITY_CTX_LOADEDSHOWING: 3 ENTITIES // SCHEMA: PROGRESSIVE

Global Asset Registry view: hierarchical structuring and instant search linked to spatial and system context.

Abstract UI system representation of the asset registry architecture under development

Workflow Flow
Abstract Representation
WO-1042 // PREVENTIVE_MAINTENANCE_TICKET
PRIORITY: HIGH
Target AssetAST-AHU-01 (Air Handler)ROOF-ZONE-01
Assigned TradeHVAC Specialist TeamTECH_ID: TC-409
Cadence LoopQuarterly Routine Q3DUE: CYCLE_72H
01Inspect drive belts and tension
COMPLETED
02Verify motor operating amps
COMPLETED
03Replace air intake filters & log delta-P
PENDING

Work Order interaction flow: linking dispatch to asset, room, and technician with clear temporal tracking.

Abstract UI system representation of the work order dispatch flow

Development Journey

System Engineering Milestones

System development follows structured milestones prioritizing data architecture maturity over superficial surface expansion.

Engineering progression arranged sequentially without artificial target dates.
01

Foundation

Completed

Defining baseline domain primitives, software entities, and data models.

STAGE_ID: STAGE-FOUNDATION
02

Design System

Completed

Building interface components and establishing a technical design system supporting bilingual RTL/LTR.

STAGE_ID: STAGE-DESIGN-SYSTEM
03

Core Facility Structure

Completed

Developing facilities, spaces, systems logic, and hierarchical relational trees.

STAGE_ID: STAGE-CORE-STRUCTURE
04

Asset Architecture

Completed

Formulating the relational asset schema linking spatial and subsystem identifiers.

STAGE_ID: STAGE-ASSET-ARCHITECTURE
05

Global Asset Registry

Active / In Development

Developing the asset discovery engine, search filters, and technical specification views.

STAGE_ID: STAGE-ASSET-REGISTRY
06

Operational Modules

Next Phase

Engineering work orders, preventive maintenance engines, technician dispatch, and inventory.

STAGE_ID: STAGE-OPERATIONAL-MODULES
07

Future Integrations

Next Phase

Exploring Building Management Systems (BMS) telemetry, sensor monitoring, and project governance.

STAGE_ID: STAGE-FUTURE-INTEGRATIONS
Engineering Notes

Challenges & Decisions

Architectural observations and design dilemmas encountered during development, along with the engineering decisions adopted.

DECISION_LOG // 01CD-RELATIONAL-ASSETS

Relational Asset Architecture vs Isolated Records

Architectural Challenge:

In many tools, an asset is treated as a flat row in a table unaware of its engineering system or physical site, leading to duplicated data and tracking friction.

Engineering Decision:

Designed an entity schema enforcing asset linkage to facility, system, and space identifiers (facilityId, systemId, spaceId), ensuring the asset always lives in context.

DECISION_LOG // 02CD-SCALE-BALANCE

Balancing Small and Large Facility Use Cases

Architectural Challenge:

Large enterprise FM systems are overwhelmingly complex for smaller setups, while lightweight tools quickly break when facility scale and system counts expand.

Engineering Decision:

Adopted progressive structural depth: allowing direct asset-to-space mapping for simple cases, while unlocking deep multi-level subsystem hierarchies when required.

DECISION_LOG // 03CD-REUSABLE-WORKFLOWS

Designing Reusable Operational Workflows

Architectural Challenge:

Handling distinct operational dynamics between emergency corrective repairs, scheduled preventive maintenance, and regulatory inspections.

Engineering Decision:

Standardized the core work order as a flexible primitive with auditable state transitions, triggered either manually or automatically via preventive schedules.

DECISION_LOG // 04CD-SCALABLE-GOVERNANCE

Maintaining System Scalability Without UI Cognitive Overload

Architectural Challenge:

Surfacing rich technical parameters and telemetry across thousands of assets risks creating cluttered screens that impede field execution.

Engineering Decision:

Structured views through progressive disclosure: surfacing primary operational telemetry upfront, while organizing in-depth engineering data into clean focused tabs.

What I'm Learning

“Building a facility-management system does not begin with screens alone; it begins with understanding the relationships between facilities, systems, spaces, assets, and operations.”

Software serving the physical built world demands deep alignment between digital architecture and field reality—where every data schema ultimately maps to operating equipment and occupied spaces.

Zakaria Al-ShuailiSystem Architect & Developer
Future Direction

Architectural Horizons & Research

Future research and development trajectories being planned to explore platform integration with smart systems and broader engineering project governance.

Future Direction — Planned & Under Exploration

BMS / Building Systems Integration

Future Integration Model

Exploring connectivity with Building Management Systems to ingest telemetry, temperature profiles, and operating hours in support of predictive workflows.

BMS / Building Systems01
Integration Layer02
Facility Platform03
Monitoring / Operations04
Technical Boundary: Conceptual future direction — direct building automation control is not currently active.

Project Management Expansion

Proposed Horizon

Expanding the platform to support capital renewal projects and major maintenance overhauls through multi-level work breakdown structures.

Projects01
Project Manager02
Levels / Work Packages03
Progress / Tasks / Operations04
HORIZON_01

Advanced asset dossiers with end-to-end lifecycle costing and depreciation profiles.

HORIZON_02

Multi-site telemetry dashboards for large institutional facility portfolios.

HORIZON_03

Long-term interoperability pathways connecting maintenance logs with Building Information Modeling (BIM).

Current Status

Current Status: In Development

The platform is under active development focused on asset registry architecture and operational modules.

The platform is being engineered as an integrated solution prioritizing architectural integrity and coherent data relationships.

SYSTEM_STATEIN_ACTIVE_DEVSTAGE: REGISTRY_CORE
Engineering Discussion

Have an idea or challenge that needs a solution?

I'm open to discussing projects and ideas at the intersection of engineering, technology, and solution building.