Assets & lifecycle
An asset record is designed to combine master data, technical assignment, condition, faults, costs and history. End-of-life and replacement planning will make the coming years visible.
OS Facility is designed to connect assets, medical technology, work orders, maintenance, cleaning, staff, space and tenants. On a shared data foundation with OS Board. From the event to confirmed completion.
Planned for 2027. OSF is in the concept phase. The following views show the target concept; scope and rollout will be defined step by step.

Select an image to enlarge
Three examples show how OSF is intended to turn events into tasks and status updates.
A discharge should trigger bed reprocessing. OSF is designed to take room rules and the next expected admission into account. Only confirmed cleaning releases the bed again.
OS Board receives the discharge from the HIS or the digital checkout.
Step 1 of 4 · Discharge reported
Technical, infrastructural and commercial facility management. The modules are designed to be introduced individually, according to your priorities.
An asset record is designed to combine master data, technical assignment, condition, faults, costs and history. End-of-life and replacement planning will make the coming years visible.
Device records, inspection intervals, user training, location and lending are planned as a separate module. Medical devices are to use the same work order, document and compliance logic as technical assets.
Reports are to become work orders with priority, responsibility and deadline. Check-in, working time and materials are to be recorded on the work order; assignees and requesters confirm completion.
Existing contract management is to be linked with assets, rooms and service providers. Maintenance plans will trigger work orders; contract deadlines, documents and reminders remain visible together.
A catalog of obligations, defined together with facility management, is designed to bring inspections, due dates and records together. Defects will generate follow-up work orders.
Planned cleaning zones and rounds are to work together with events such as discharges or special cleaning. Checklists and time recording are planned for mobile use.
Teams, qualifications, presence, on-call duty and deputies are to control how work orders are distributed. The existing duty roster remains the master system; OSF is designed to show capacity and working time on the work order.
Rooms, space, usage, rental units and contract deadlines are to use the same structure. Planned exports will link this information with your existing ERP.
On the ward, room 204 is a patient room with beds. In OSF, the same record is also designed to link floor space, assets, contracts and cleaning zone.
Patient, case, bed and ward status. OSF is designed to build on the existing structure, roles and events of OS Board.
Explore OS Board ↗Additional levels are planned for buildings and floors, all room types, technical assets and the related tasks.
Coming 2027Report in three steps: where, what, photo. Role-based views are planned on the OS Panel, in the OSF app and on handsets. Badge or NFC will identify the person and the location.
The concept provides for operation in the customer network, with separate tenants, roles and SSO. Existing systems remain connected via interfaces.
A planned alarm adapter will connect work orders, escalations and confirmations with your existing alarm system. OS Alarming, Ascom handsets, DECT, pagers and the app are planned as channels; the integration is implemented system by system.
Accounting, purchasing, HR and payroll remain in your existing systems. OSF is designed to plan assignments and record working time on the work order. BIM modeling stays in the specialist system; CAD import is planned for a later expansion stage.
Further CAFM areas are planned as extensions that can be introduced individually. Scope, sequence and integrations are defined in the joint project.
The planned path leads from a joint workshop to pilot operation. Your existing CAFM remains the master system for areas not yet migrated. Sequence and scope are defined in the project.
Define use cases, data foundation and boundaries together.
Start with cleaning and fault reports; test the processes in daily use.
Add assets, medical technology, staff and obligations, as well as space, tenants and extension modules, step by step.
Coming 2027: OS Facility is planned as a platform for systems, medical technology, orders, maintenance, cleaning, personnel as well as space and tenants. Eight core modules are intended to connect events from OS Board with tasks and feedback. Anlagen, Aufträge, Wartung und Betreiberpflichten sollen zusammenlaufen. Geplante Touren und Ereignisse sollen dieselbe Auftragslogik nutzen. For use in a hospital, functions, responsibilities and interfaces are planned around your existing systems. Neutronix provides consulting and integration. Together, we clarify which components fit your processes and how they work with the OS Board product family.
Coming 2027: OS Facility is planned as a platform for systems, medical technology, orders, maintenance, cleaning, personnel as well as space and tenants. Eight core modules are intended to connect events from OS Board with tasks and feedback.
For use in a hospital, functions, responsibilities and interfaces are planned around your existing systems. Neutronix provides consulting and integration. Together, we clarify which components fit your processes and how they work with the OS Board product family.
Contact Neutronix to discuss your requirements. The contact form lets you request a product demo or a consultation. We discuss the concept planned for 2027.
An idea, a challenge, a specific project.
We listen – and think it through with you.