CAMPUS & BUILDING OPERATIONS

Different systems.
A shared view of operations.

Connect buildings, areas, equipment and events. Give operations, maintenance and integration teams an information path suited to their work.

Explore the role perspectives Discuss project scope

BEFORE YOU START

Clarify the conditions.
Bring the material you have.

For operations across buildings, subsystems and teams. First confirm available data and access scope.

01Buildings and subsystem inventory
02Space, equipment and event identifiers
03Team tasks and permissions

01 / WORKING ACROSS ROLES

One set of objects.
Different paths for each role.

SPACE, EQUIPMENT & EVENTS

Choose your reading perspective

OperationsMaintenanceIntegration

Your selection changes the blue emphasis and explanation below. Use arrow keys to select with a keyboard.

Area → related event → equipment

Event → AHU-01 → Building A, Level 2

Object identifier ↔ spatial ownership ↔ event reference

Building ABUILDING_A

LOCATED IN

Level 2 · HVAC room

AREA_A_02

EQUIPMENT IN THIS AREA

Air handling unit AHU-01

AHU-01

EVENT REFERS TO EQUIPMENT

RELATED EVENTEVENT_01

Equipment state to review

Related objectAHU-01

Locate through the object’s ownershipBuilding A → Level 2 HVAC room

Area → related event → equipment

Start with the area, then find the equipment to review.

The event in Building A, Level 2 refers to AHU-01. An operating view groups the area and related events to clarify who should review them.

Event → AHU-01 → Building A, Level 2

Follow the event to its equipment and location.

Relate events, equipment and plant-room locations so maintainers can move from an issue to the relevant object.

Object identifier ↔ spatial ownership ↔ event reference

Check identifiers, ownership and interface permissions.

Organize relationships between space, equipment and events in a shared integration and operations view.

Read the preparation points for all perspectives

Operations

The event in Building A, Level 2 refers to AHU-01. An operating view groups the area and related events to clarify who should review them.

Maintenance

Relate events, equipment and plant-room locations so maintainers can move from an issue to the relevant object.

Integration

Organize relationships between space, equipment and events in a shared integration and operations view.

Product demo · Select operations, maintenance or integration to inspect the objects and information each role needs.

THREE QUESTIONS IN THE SETTING

Organize system information around daily work.

Which system holds the information?

Equipment and events are dispersed. Start with objects, identifiers and available interfaces.

Where is the issue?

Relate buildings, areas, devices and events to reduce repeated searches across interfaces.

Who assesses and handles it?

Organize views around the daily work of operations, property and technical teams.

A PROPOSED DELIVERY PATH

Clarify the scope before connecting information.

Inventory buildings and systems
List buildings, managed areas, equipment objects, interface owners and permissions.
Define consistent object relationships
Align identifiers, point meanings and spatial ownership. Select the data needed by upper-layer views.
Organize views around users’ work
Arrange overviews, area states and event information around operational tasks, rather than copying every subsystem function onto one screen.
Verify using real scenarios
Use event inspection, device location or handover scenarios to verify data, permissions and responsibilities.

PRODUCT ROLES

Integration, operations and space each have a role.

IoT data layer

PsIOT: connect data across subsystem suppliers.

PsIOT

Operational information

PsCMS: organize daily views of equipment, energy and events.

PsCMS

Spatial views

P.C.I: locate devices and states within building spaces.

P.C.I

RELATED PROJECT EXPERIENCE

Review similar settings, then discuss your scope.

Returnee town project image — Returnee town · multi-system integration

Mixed-use buildings and supplier integration have different priorities.

The cybersecurity center spans offices, retail, hotel and conference settings; the returnee town connects multiple subsystems and vendor interfaces. Explore their operating contexts and integration scope.

CAMPUS & BUILDINGSNational Cybersecurity Center integration and middleware project, Hubei CAMPUS IoTReturnee Town IoT platform, Jiangsu

CONDITIONS

Clarify what existing systems can provide.

For campuses with multiple buildings and subsystems, organize overviews, event views and equipment locations.

Use the integration checklist Review integration responsibilities

NEXT STEP

Bring a specific question.
Discuss the delivery scope.