What the product does.
WexaMaintain is an independent product for equipment maintenance, fault response and field service across companies and sites. Technician completion and the operating team’s acceptance remain separate steps.
Native-auth source edition and local verification are prepared. Customer readiness and live vendor integration are not confirmed.
Product capabilities
Keep the equipment and its history together
Review equipment hierarchy, maintenance history, preventive plans, faults and technician assignments. Ownership, physical location and maintenance responsibility are distinct.
- Equipment records and maintenance history
- Preventive plans and fault response
- Technician assignment and work orders
Separate work completion from acceptance
A technician’s completion report does not finalize operating acceptance. Work evidence, acceptance responsibility and parts reservation, consumption or return need their own review.
- Work evidence and operational acceptance
- Company and location access
- Distinct parts and stock outcomes
Evaluate the relevant tasks.
Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.
- Select sample equipment, its location and maintenance responsibility.
- Review a fault, technician assignment and work-order evidence.
- Inspect the separate completion and acceptance decisions.
- Agree customer setup, parts ownership and any ERP connection.
Workflow walkthroughs
Follow a fault through operational acceptance
Describe one equipment or service workflow, your sites and team responsibilities. Use anonymized equipment examples.
- Select sample equipment, its location and maintenance responsibility.
- Review a fault, technician assignment and work-order evidence.
- Inspect the separate completion and acceptance decisions.
- Agree customer setup, parts ownership and any ERP connection.
Prepare a useful support request.
Include the exact WexaMaintain package or preview, environment and workflow. Confirm whether the issue concerns a local evaluation or an accepted customer installation.
- Describe one equipment or service workflow, your sites and team responsibilities. Use anonymized equipment examples.
- Describe expected behaviour, what happened and any steps already tried. Do not send passwords, tokens, private files or production records.
- Remaining acceptance scope: Customer installation and operating acceptance; Live ERP/WexaStock/vendor connections; Production deployment and external activation.
Your questions, answered.
Is Keycloak required for the current source edition?
The current native-auth edition uses its own username/password setup and removes the active OpenID/Keycloak dependency. Confirm the exact edition before installation.
Does closing a technician task complete acceptance?
No. Technician completion and operating acceptance are separate product decisions.