Modules · 3 of 16

Facilities & operations

Work orders raised against real equipment, supply ordered against real stock levels, and the projects that are bigger than either.

The fifth repair on the same rooftop unit looks like five unrelated tickets when the equipment has no record of its own. And the supply closet nobody counted is the supply closet somebody reorders.

Facilities

Work orders, building queues, equipment history, preventive maintenance, vendors.

Building and room decide who picks a request up, so the queue routes itself. Equipment carries its own service history, which is what turns the fifth repair on one unit from five unrelated tickets into a visible pattern.

module key: facilities · independently toggled per district

What it does

  • Work order submission with building/room routing and an approval queue
  • My tickets, building queue, all tickets, and a cross-building emergency queue
  • Facilities asset register with service history and a capital chain
  • QR scan on the equipment itself to open its record while standing in front of it
  • Preventive maintenance schedules and inventory management
  • Floorplan viewer and a vendor portal for external contractors
  • AI-assisted triage, escalation engine, SLA enforcement, custom workflows

Custodial supply

Catalogue, ordering, warehouse inventory, cycle counts, forecasting, purchase orders.

Custodial and maintenance supply from catalogue to shelf. The reorder queue proposes what stock levels suggest is needed; a person reviews it, because a forecast is a suggestion.

module key: supply_orders · independently toggled per district

What it does

  • Product catalogue with vendor pricing and unit sizes
  • Multi-site order pipeline with a reorder queue and recurring orders
  • Warehouse and building inventory, receiving, and cycle counts
  • 90-day demand forecast, purchase orders and vendor quotes
  • Fiscal year and budget code management
  • Code 39 shelf and bin labels, pick-list PDFs, CSV import/export

Projects

Kanban and Gantt for work that is bigger than a ticket.

A ticket is one thing being fixed; a board is many related things with an order and an end date. If the work has phases, or people from more than one department, or a date the district has committed to, it wants a board.

module key: projects · independently toggled per district

What it does

  • Department and cross-functional Kanban boards
  • Tasks with a single owner, dependencies and milestones
  • Gantt view for phased work with committed dates
  • Task comments, so the thread is readable by someone who joins in month three
  • Records from other modules linked onto the board

Walk through Facilities & operations on your own data

We load a copy of your buildings and roles, turn on the modules you asked about, and show you the queues your staff would actually see.