Clay's Blog

Work order acceptance can be performed by work order accepters who are customers of maintenance operations. Accepters are defined by site.  Menu path: Organization module | ACL Profiles | WO Accepter; or from EAM or Customer's site screens. An accepter can add the following info when accepting a WO:  Comments about the acceptance Wor...

Work order planners are configured by sites. They receive some work order email notifications per site.  There are cases that a user needs to be of WO Planner role for operating weekly schedules or dispatch boards by teams, but does not need to get all the emails for the planners (for given sites). There is a new flag ...

Server processes in Calem Enterprise are typically executed in the server as scheduled jobs. This feature allows users to launch he server processes after changes made to PMs or user schedules so that the work orders or user schedules can be generated and viewed right away (without waiting to see the results the following day).&...

​Duplicate work orders require resources to view and filter out. It is more efficient to avoid duplicate work orders. Calem Enterprise provides the following processes to reduce duplicate work orders: ​Work order generation from PM. The generation process uses PM and its due date to determine duplication and will skip work order generation for a PM...

We have just made available the R10d release today. R10d includes interesting enhancements based on customer feedbacks and bug fixes. Here are the highlights of the release.  Work Order duplicate check in WO creation. This feature prompts you about potential duplicate work orders and allows you to continue or cancel out the work orde...

Work order steps can be enforced by statuses. For instance, step 10 to 20 must be completed before a work order can be set to "In Process" status. The enforcement can be configured for PM and corrective work orders and by sites. Here are the steps to set up: Build out step enforcement by statuses. Menu path: Admin module | Data design | WO Sta...

This feature is designed to show different dropdowns for different sites. Here is a use case: In a multi-site deployment one site does not use work order "Detective" and "Calibration" categories while "Detective" and "Calibration" are used by other sites. Here are the steps to achieve site specific dropdowns: Define custom dropdown sets to for excl...

This feature has been enhanced to cover to use cases: When creating a work order for an asset the matching custom fields will be copied to the work order created. When generating a PM work order for an asset the matching custom fields will be copied to the PM work order. ​ A preventive maintenance (PM) object is a preventive job to be performe...

​Two new KPIs have been added to KPI-10 (the key performance indicators in "KPI-10" tab of Calem Enterprise Dashboard). WO Open for 10+ days: work orders that have been open for 10 or more days. Open WO Count: total work orders that are open. You can change the number of days that work orders are open by "Set Days" menu.​ You can switch to lis...

Iterative implementation means to implement Calem Enterprise with small, repeatable steps. Each iteration implements one one or more functions for a selective data set. It enables you to have an operational EAM/CMMS solution from the get-go, then extend it incrementally.  The Iterative Implementation was presented at WAI OPERATIONS SUMMIT &...