Six modules on one set of properties
A building is entered once. The duty roster, the recorded time and the proof of service refer to it, and no detail is typed twice.
On the current state: the platform is in place with tenant separation, sign-in and the subscription model. The functional modules described here are in development. What you get today is an environment of your own and a firm answer on when which module will be usable.
Properties and room register In development
The property records are the foundation of everything else: site, building, unit and room, plus the district a property sits in. A room type carries what has to be done there, and an area carries how large it is. The plan and the costing are built from these details.
- Site, building, unit and room in one hierarchy
- Districts as the assignment of properties to site supervisors
- Staff records, shared with the other NCS cloud products
- Service contracts per property as the basis for billing
- Part of every package and never sold on its own
Duty rosters and scheduling In development
Maintenance cleaning repeats, special jobs do not. Both belong on the same plan, because otherwise the same person is scheduled twice and nobody sees it. When somebody is out, the plan shows who knows the property and has the time.
- Recurring assignments and one-off jobs in one plan
- Cover for sickness and holidays, with the property in view
- Absences the scheduling knows about, instead of the calendar in the hallway
- Planning per district, so a site supervisor can run their own area
Mobile time recording In development
Recording happens on site, not in the evening from memory. What matters is the step after it: only an approved entry leaves the system towards payroll and invoice. That boundary is already part of the contract between the cloud and the sync agent, not of a report.
- Recording at the property, tied to the planned assignment
- Approval by the site supervisor before a time travels on
- Only approved times go to SAP Business One or into billing
- No multi-factor sign-in for the team, because a shared device cannot carry it
Quality inspections In development
An inspection is worth only as much as its documentation. The check points hang on the room type, so a sanitary room is checked differently from a stairwell, and the result stays with the property. When a complaint arrives, that is the answer.
- Check points per room type instead of one list for everything
- Inspections documented at the property and findable again
- Complaint and rework tied to the inspection
Winter service In development
In winter service the proof is what counts. Who cleared or gritted which area and when is the detail needed when liability is questioned, and it has to hold up afterwards. The assignment depends on the weather, the duty on the area.
- Areas with their clearing and gritting duty
- Assignments driven by the weather, not by a fixed plan
- Proof per area with its time, as the answer to a liability question
Connect SAP Business One In development
For companies running SAP Business One. An agent runs in your network and collects its jobs from the cloud; it only connects outwards, so your IT department does not have to release a port. The cloud can never reach it on its own, and that is the design rather than a shortcoming.
A proof of service becomes a draft document in SAP. Posting a customer invoice is your clerk's decision and not that of a service checking back every minute.
- Reconcile properties and staff between SAP and the cloud
- Hand approved times over to SAP
- Proof of service as a draft document; posting stays manual
- Outgoing connections only, out of your network
- Part of no package, because an agent at the customer brings its own support effort
Create an environment and look around
You pick a package and an address. We set up the access and get back to you.