ArcnexusOS
Operations platform
WorkPlatform · ArcnexusOS
One connected record for physical operations.
ArcnexusOS is an operations platform MVP for multi-site businesses with physical assets, shaped through internal and pilot use. It connects operational workflows, assets, inventory, teams and site-level information within a coherent platform.
MVP · shaped through internal and pilot use
Real screens from the MVP
Browse the modules as they are today. On desktop, the view tilts gently with your cursor.
Unified dashboard: open tickets, active assets, critical stock, and alerts per site — one picture of what needs attention.
Operational work that doesn't get lost.
Visibility
- Every request becomes a record with an owner, priority and status.
- One view of open work across sites and teams.
- A history of what happened, by whom and when.
Connected work
- Tickets linked to the assets, locations and parts involved.
- Stock and suppliers alongside the work that uses them.
- Fewer hand-offs through email and spreadsheets.
Multi-site structure
- Permissions by role and module.
- Operations per location with central oversight.
- Modules activated as each site needs them.
From request to resolution, in one flow
ArcnexusOS connects operational work rather than adding isolated tools: every ticket, asset, part and order stays linked from report to resolution.
1
A request comes in
Customer request, staff report, maintenance need, or sensor alert — captured in one place, not lost in a call or inbox thread.
2
A ticket is created and classified
Unique record: who reported it, what is needed, priority, type (incident or service request), site, and when it opened.
3
Assigned to the right owner
Operations, maintenance, F&B, or facilities — assigned to the right team with SLA, due date, and clear responsibility.
4
Work is tracked in one thread
Status updates, notes, photos, time spent, and every action logged — reopen if the issue returns.
5
Linked to operational context
Site, area, asset, device, floorplan, or supplier connected to the ticket when it matters.
6
Resources coordinated
Parts, purchases, approvals, or external vendors — without switching to Excel or scattered email.
7
Resolved and communicated
Solution documented, requester informed, managers see closure — nothing left hanging.
8
History builds over time
Repeat issues, response times, cost per asset, and patterns across sites — data, not memory.
In the MVP today
The core modules available now, working from one shared operational record and activated per site.
Stock Management
Parts and spares linked to assets. Suppliers, orders, and invoices in one place, with low or critical stock alerts.
MVP
Ticket System
Register, organize, assign, and track every operational request. Each ticket captures who reported it, what is needed, priority, owner, status, actions taken, and how it was resolved — incidents, maintenance jobs, service requests, or operational tasks.
MVP
Asset Management
Equipment catalog per site with detail, maintenance history, calendar, and QR/NFC scanner.
MVP
Site Control
Central asset view, operational floorplan, device status, and real-time alerts per site.
MVP
User Management
Roles (owner, admin, manager, staff, viewer), module access, and multi-site team management.
MVP
Notification Center
Inbox, preferences, and real-time operational alerts: low stock, new ticket, thresholds, critical incidents.
MVP
Configuration
Locations and sites, essential integrations (Gmail, Slack, DHL, OpenAI), branding, and cron tasks.
MVP
In development
Modules being built and refined. Available to explore in a demo, not yet part of the MVP.
Workflow Automation
Event-driven workflows: a new ticket can raise an order and send an alert. Automate repetitive operational flows across modules.
Planned
Planner
Projects, boards, cycles, and calendar for site expansion, refurbishments, audits, or rollouts.
Planned
BMS
Sites, devices, snapshots, analytics, thresholds, and reports for large venues, hospitality properties, or malls.
Planned
One platform, six layers
Every module reads and writes the same operational record, from a single site to many.
- 01
Interfaces
A view for every role
Dashboards and module views for each role — managers see the full picture, staff see the work assigned to them.
- 02
Automation (in development)
Workflows that react across modules
Rules that listen to the operational record — a stock threshold, a missed deadline, an asset alert — and prepare tickets, orders and notifications.
- 03
Capability modules
Activated per site
Tickets, assets, inventory, site control, users and notifications today; planner and BMS in development — switched on per site as needed.
- 04
Shared operational record
One record, not siloed apps
Sites, assets, work, stock and suppliers linked in one data model, so modules share information rather than copying it.
- 05
Sites & spaces
Floorplans, zones, devices
Locations mapped to floorplans, zones and devices, with configuration, permissions and modules set per site.
- 06
Organisation & access
Role-based access
Owner, admin, manager, staff and viewer roles, with access controlled across sites and modules.
From MVP to platform
What is available today, what we are building next and what we are exploring.
- 1
Now The MVP
Tickets, assets, inventory, site control, users and notifications working together as one connected operational record.
- Core modules
- Multi-site structure
- Role-based access
- 2
In development Automation and planning
Event-driven workflows across modules, a planner for projects and roll-outs, and building management for larger sites.
- Workflow automation
- Planner
- BMS
- 3
Exploring Deeper intelligence
Reporting across sites and AI assistance drawn from the operational history, shaped by what pilot use shows is valuable.
- Cross-site reporting
- AI assistance
- Integrations
See ArcnexusOS on your own workflow.
In a demo we walk through a real flow — request, ticket, asset, parts, resolution — and discuss whether the platform fits your operation.
