Construction operating and integration layer

Active build

NOSMO Nexus.

Nexus carries shared construction context across people, projects, communication, existing software and NOSMO modules. It connects what already works instead of demanding another full system replacement.

Nexus Core

What Nexus keeps connected.

The objects stay understandable. Their relationships, permissions and source boundaries make them useful across the project lifecycle.

People / Person Cards

Identity, role, skill and controlled sharing.

Projects

Shared project context and structure.

Documents

Drawings, schedules and controlled files.

Tasks

Assignable work, readiness and evidence.

Timeline

Actions, changes, approvals and decisions.

Project Memory

Durable history with source boundaries.

Knowledge Graph

Relationships between people, objects and work.

Ask Nexus

Natural-language access to authorised context.

Integrations

Existing platforms, BIM tools, messaging and file sources.

Permissions

Private, professional and project access remain explicit.

Nexus modules

Shared core. Three different operational surfaces.

BIM and WorkSuite sit alongside each other. WorkSuite is the home for trade applications; BIM handles model and object context.

NEXUS COREConnected context, permissions and integrationsPeople · Projects · Documents · Tasks · Timeline · Memory · Graph · Ask Nexus · Integrations
MODELS AND OBJECT CONTEXT

NOSMO BIM

Models and object identities connect to the people, documents, evidence and history around them.

  • Model / object graph
  • Coordination context
  • Asset and handover history
  • BIM overview

Existing software and communication

Nexus is the connective layer, not a forced replacement.

Integration should preserve useful source systems while adding the missing relationship between the person, project, task, evidence and decision.

Construction platforms

Targets include Work Wallet, Procore, Dalux, Viewpoint, CompanyCam and other established workforce, project and evidence tools.

Communication routes

Email, WhatsApp, SMS and contacts can be connected to the correct person or project through a controlled pre-action layer.

BIM, storage and specialist tools

Model-authoring, coordination, Drive, document storage and specialist systems can remain authoritative sources connected through Nexus.

Current boundary: integration readiness differs by system. These are product directions unless a specific connector is identified as live in a released module.

Connected project memory

Context can move without collapsing every tool into one app.

Source systemPlatform, model, message or file
Nexus contextPerson, project, object and permission
Operational moduleWorkforce, BIM or WorkSuite
EvidencePhotos, tests, defects and approvals
Project memoryTraceable decision and handover history
Technical building services model illustrating connected construction objects
BIM direction

Objects with operational history

BIM is not only a visual model when objects can carry controlled evidence and lifecycle context.

Field and spatial direction

Guidance where the work happens.

Spatial interfaces, photogrammetry, AR/VR and digital twin research are explored as ways to give people the right project context in the field. They remain R&D until a practical workflow proves them.

Technology evolution