CMMS Profile
osapiens HUB for Maintenance
osapiens GmbH · Germany (Mannheim)
Mobile-first execution with published pricing and a SAP-certified connector; strong for SAP-centric rollouts, but “AI” is mostly rule automation today and advanced analytics are tier-gated.
- Website
- osapiens-cmms.com
- Deployment
- SaaS
- Pricing
- Per user Feature tier Usage quota
- Entry price
- 29
- Price transparency
- 4/4
- Maturity
- 3/4
- Small org fit
- Yes
- Enterprise
- Yes
Strengths
- SAP-certified connector is a credible integration path for SAP PM-centric organizations.
- Published tiered pricing (including a free starter plan) lowers procurement friction and enables low-risk pilots.
- Offline-capable native mobile execution with evidence capture (photos/redlining, signatures/approvals).
- Planner-focused scheduling cockpit with skills-based assignment and shift/capacity awareness.
Gaps
- Validate SAP connector scope in a live demo: which objects sync, how errors are handled, and what monitoring exists.
- Request API documentation (OpenAPI/Swagger) and confirm CRUD coverage for assets, WOs, inventory, and planning objects.
- Test offline mode with two technicians editing the same work order and syncing later; confirm conflict behavior.
- Validate PM trigger depth: meter/counter precedence, multi-counter logic, and exception governance.
- Ask for a clear list of AI features available today vs. planned modules (post Lucent AI acquisition) and how they’re priced.
Feature Depth
| Feature | Score | Reason |
|---|---|---|
| Asset hierarchy | | Unlimited assets/locations and practical hierarchy patterns. Deeper governance (e.g., strict component swap traceability) needs validation. |
| Asset identification | | QR/barcode scanning for fast asset lookup is core. NFC/label governance and scan-first workflows are not shown in depth. |
| Asset history/docs | | Work history, attachments, and documents can be tied to assets for a usable machine life file. Export/audit depth is unclear. |
| Work request intake | | Requests can be captured via structured forms and routed into work orders. Multi-channel intake (portal/email) needs confirmation. |
| Work order execution | | Technician execution supports templates, checklists, photos/redlining, and approvals. Sub-task depth and governance controls need a demo. |
| Failure RCA | | Issue documentation exists, but Pareto-grade problem/cause/remedy coding depth is not evidenced publicly. |
| Preventive maintenance | | Recurring PM with automatic work order generation is productized. Seasonal packages and exception handling depth should be validated. |
| Usage-based triggers | | PM can be triggered by meter readings/operating hours plus condition-based logic. Multi-counter precedence and governance are not detailed. |
| Machine downtime | | — |
| Inspections/checklists | | Checklists and step-by-step instructions standardize execution. Rich conditional logic and compliance-grade signatures need confirmation. |
| Mobile app | | Native iOS/Android with offline mode for execution and evidence capture. Sync conflict handling is not described. |
| Parts/BOM | | Spare parts can be linked to assets and consumed on work orders. BOM depth (alternates/substitutes) is not clearly shown. |
| Inventory/procurement | | Inventory supports locations and transfers with usage tracking. Purchasing/PO workflows and approvals are not clearly evidenced. |
| Planning/scheduling | | Drag-and-drop planning cockpit with skills-based assignment and shift/capacity views. Constraint-based planning depth should be validated. |
| Workforce skills | | Skill-based assignment is positioned in planning. Certification/expiry tracking and governance depth are unclear. |
| External contractors | | Contractor coordination is positioned in scheduling/dispatch. External user access and approval workflows should be validated. |
| UX adoption | | Product messaging and flows emphasize technician adoption and low training friction. Validate with a 1-day pilot on real jobs. |
| Reporting/KPIs | | Core KPI visibility exists; advanced dashboards/analytics and cost tracking are Premium-gated. Custom reporting without BI tools needs validation. |
| Integrations/API | | Integrations are positioned, but public API depth and object coverage are not explicit. Request OpenAPI/Swagger in diligence. |
| SAP ERP integration | | Enterprise tier includes a SAP-certified connector (PM/SD/MM positioning). Validate object scope, monitoring, and error handling. |
| Security/admin | | SSO (Premium) and ISO 9001/27001 + GDPR positioning support shortlist viability. Validate SCIM, audit logs, and role granularity. |
| Automation/workflows | | Rule-based automation and condition triggers reduce admin work. Workflow builder depth and change control should be confirmed. |
| Customization | | Custom fields and workflow tailoring are positioned. Boundaries of deep business logic customization are not public. |
| AI assist | | AI messaging exists, but shipped capability reads as rules/automation today. Validate what’s live vs. roadmap (Lucent AI modules). |
0: Not offered 1: Basic: usable, shallow depth 2: Standard: expected CMMS level 3: Advanced: handles real complexity 4: Best-in-class: deep, low-friction, governed
Trust & Compliance
- Certifications
- ISO 9001ISO/IEC 27001
- Confidence
- Medium
- References
-
- Coca-Cola (CONA Services)
- Nordex
- Puratos
- Boehringer Ingelheim
- Grupo Agora
- Lekkerland
- ewz
- Rollout support
- 2
Company Details
- Employees
- 500
- Customers
- 1800
- VC-backed
- Yes
- Languages
- German, English
- Adjacent areas
- eam
- Last verified
- 2026-02-08
Notes
osapiens is best known for its broader ESG platform; HUB for Maintenance is marketed as a standalone CMMS with its own signup and pricing. Treat customer-count claims as company/platform-level unless contract language specifies CMMS-only references.