WexaMaintain / Maintenance & field service
Plan maintenance. Close the work with evidence.
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.
Evaluation scope and delivery confirmed with the team
Discuss an evaluationReview product scope, licensing and implementation during evaluation.
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
Choose the source edition and connector scope
The current native username/password source edition removes the active OpenID/Keycloak dependency. Local setup and verification evidence is separate from a customer install. ERP, WexaStock and vendor connections require their own accepted scope; the similarly named maintenance pilot in the catalogue is a separate offer.
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.