Properties and room register In development
Site, building, unit and room in one hierarchy, plus the staff records. This module is part of every package.
NCS-Facility brings together the room register of your properties, the scheduling of your teams and the time recorded on site. Every company works under its own address. Whoever uses SAP Business One connects it through an agent inside their own network, without opening a port to the outside.
NCS-Facility is being built. The platform already carries tenant separation, sign-in with multi-factor authentication and the subscription model. The functional modules are being written; we will tell you on request which one will be usable when. A test environment we set up today.
The modules work on the same properties and the same staff records. A building is entered once, and the roster, the proof of service and the invoice all refer to it.
Site, building, unit and room in one hierarchy, plus the staff records. This module is part of every package.
Recurring maintenance cleaning and one-off special jobs on one plan, with cover when somebody is out.
Times are recorded on site, not in the evening on a slip of paper. Only approved entries leave the system.
Inspections with check points per room type, documented and tied to the property.
Assignments driven by the weather, with proof per area. The proof is what counts when liability is questioned.
For companies running SAP Business One. Booked separately and part of no package.
Permissions hang on five roles. Who holds them is your administration's own decision.
Their own assignment and their own time recording, on the device they have on site.
The properties of their own district, the plan for the coming days and the cover when somebody is out.
Master data, approval of recorded times and the proofs that belong to an invoice. This role signs in with multi-factor authentication.
Users, booked modules and the billing figures of the month. With multi-factor authentication as well.
Your company gets a subdomain of its own. The address decides which data is loaded, not the sign-in. A user therefore cannot help themselves to another tenant.
For example ihrname.demo.ncs-facility.cloud.
Every row carries its tenant, and PostgreSQL enforces the separation through row level security. It therefore does not rest on application code alone: without a tenant set, a query returns no rows.
For administration and office the second factor is mandatory, as a one-time code or as a passkey. For the team on site it explicitly is not.
An agent in your network collects the jobs from the cloud and reports the result back. It only connects outwards, so your IT department does not have to open a port. A proof of service becomes a draft document in SAP; posting it stays a manual step.
You pick a package, settle on your address and get an environment of your own. After that we talk about what your company really needs.