A tenant reports a building-service issue with its location.
FACILITIES, SECURITY & PROPERTY / THE OPERATING DAY
Automate the SOPs
behind facilities.
Connect the teams, records and handoffs behind facilities, with the right people at each decision.
EXAMPLE OPERATION · FACILITIESAll industries
daffyOS Example operation · Facilities / One connected enterpriseField Service & Installation / Example record
A service request reaches the right site team
Supporting recordLinked to the original instruction
ATTACHEDDaffyI have linked the record and prepared the next step for Security guard. Approve assignment to the responsible site technician?
DECISION OWNER / SECURITY GUARD
Approve assignment to the responsible site technician?The source record, responsible team and proposed next step are linked. This example waits for the decision owner.
Security guard · Approval requiredTARGET OUTCOME
Approve assignment to the responsible site technician?
Approve assignment to the responsible site technician? The approval and follow-up stay attached to the original record.
RECORD IN FOCUSExample recordField Service & Installation SOP / Example
EXECUTION / SIMULATED
- Operating record DaffyEvidence captured
- 2Daffy Security guardAwaiting approval
- 3Security guard Operation recordAction pending
- 4Operation record Follow-upFollow-up waiting
DECISION OWNER / SECURITY GUARD
Approve assignment to the responsible site technician?The source record, responsible team and proposed next step are linked. This example waits for the decision owner.
Security guard · Approval requiredWORKING NOTES
- No working notes yet.
ONE CONNECTED OPERATING DAY
What needs your attention?
Context follows this operation.
THE WORKSPACES BEHIND THE THREADS
Where your work
comes together.
Each workspace holds its part of the operation. Daffy coordinates the handoffs under the permissions you set.
Field Service & InstallationVision AI GridAttendance & ShiftsMaintenance & Asset HealthIoT, Sensors & MachinesCustomer Support DeskEnergy & UtilitiesSafety, EHS & IncidentsFleet, Transport & RouteWorkforce CorePayroll & StatutoryBilling & CollectionsCompliance & AuditInventory & StoresClient PortalCosting & ProfitabilityCommand CentreDAFFY Chat & Authority
ONE SOP TO START WITH
A service request reaches the right site team.
A representative scoping example. Integrations, actions and approval rules are agreed for your deployment.
01 / THE TRIGGER
A tenant reports a building-service issue with its location.
02 / THE HUMAN DECISION
Approve assignment to the responsible site technician?
03 / THE CONNECTED OUTCOME
The helpdesk, site team and client contact share the work-order status.
THE PEOPLE BEHIND THE PROCESS
Different teams.
One operating context.
01Soft Services
02Technical Services
03Security Operations
04Energy Management
05Helpdesk
06Client Relationship
07Procurement & Stores
08Compliance & Statutory
09Quality & Audit
10HR & Deployment
11Training
12Finance
THE OPERATING CYCLE
The handoffs that
make the business work.
Use this operating map to decide where a record is created, who takes responsibility and what must be checked before work moves.
- 01 / START THE RECORD
Deployment & muster
Capture the source instruction, evidence and responsible owner.
- 02 / CARRY THE CONTEXT
Scheduled tasks
Link the scheduled tasks record to the previous stage and the team responsible for the next handoff.
- 03 / CARRY THE CONTEXT
Access & security
Link the access & security record to the previous stage and the team responsible for the next handoff.
- 04 / CARRY THE CONTEXT
Technical services
Link the technical services record to the previous stage and the team responsible for the next handoff.
- 05 / CARRY THE CONTEXT
Helpdesk
Link the helpdesk record to the previous stage and the team responsible for the next handoff.
- 06 / CARRY THE CONTEXT
Energy
Link the energy record to the previous stage and the team responsible for the next handoff.
- 07 / CLOSE THE LOOP
Client review
Retain the outcome, outstanding exceptions and decision history.
THE WORKSPACE MAP
The same brain.
Your industry’s vocabulary.
A workspace is shaped around the people and records it serves. These are starting points, with connected workflows between them.
Field Service & Installation
Task & Round Management
Which tasks are overdue at my site?
Explore workspace Vision AI GridVision AI Grid
Was the 02:00 patrol round actually completed?
Explore workspace Attendance & ShiftsDeployment & Attendance
Which sites are under-deployed today?
Explore workspace Maintenance & Asset HealthTechnical Services & AMC
Which equipment missed its scheduled test run?
Explore workspace IoT, Sensors & MachinesBuilding Sensors
Which sensors have stopped reporting?
Explore workspace Customer Support DeskOccupant Helpdesk
What requests are breaching SLA right now?
Explore workspace Energy & UtilitiesEnergy Management
Where is energy being consumed overnight?
Explore workspace Safety, EHS & IncidentsSecurity & Incidents
What security incidents occurred this week?
Explore workspace Fleet, Transport & RouteGate & Vehicle Access
Which vehicles entered outside authorised hours?
Explore workspace Workforce CoreWorkforce & Deployment
Which sites are short on trained technicians?
Explore workspace Payroll & StatutoryPayroll & Statutory
Are we compliant on minimum wage at every site?
Explore workspace Billing & CollectionsContract Billing
Which invoices are disputed and on what?
Explore workspace Compliance & AuditStatutory & Licences
Which site licences expire this quarter?
Explore workspace Inventory & StoresConsumables & Stores
Which sites are over-consuming consumables?
Explore workspace Client PortalClient Portal
Which clients have open SLA queries?
Explore workspace Costing & ProfitabilityContract Profitability
Which contracts are running below margin?
Explore workspace Command CentreOperations Command Centre
Which sites need attention this morning?
Explore workspace DAFFY Chat & AuthorityDAFFY Chat & Authority
Are we meeting SLA at this client?
Explore workspaceAUTHORITY, IN CONTEXT
The right answer.
For the right person.
Agree access and action permissions before connecting operational data. The same question can require a different scope for each role.
“What are my tasks for this shift?”
Own tasks, own area, own shift.
“Which rounds are still pending on my shift?”
Own post, own rounds, own incidents.
“Which tasks are overdue at my site?”
Their site, staffing, tasks, complaints, equipment.
“Which equipment missed its scheduled test run?”
All equipment, AMCs and breakdowns across sites.
“Are we meeting SLA at this client this month?”
Their client portfolio, SLA, complaints, billing.
“Which contracts are running below margin?”
All sites, margin per contract, statutory exposure.
START WITH ONE WORKFLOW
One SOP today.
A more connected company tomorrow.
Bring us the process, the people and the exceptions. We’ll map the first proof of value.