This blog is a tutorial of implementing PM Checklist in Calem.  The process diagram is shown below. 

Click How to Implement PM Checklist (PDF file link) to view the tutorial.

Appendix A and B are shown below.


Appendix A. Steps by Maintenance Manuals

If steps to perform a PM Plan is defined in a maintenance manual, you may upload the relevant sections of the maintenance manual as a document in Calem and reference that doc in the steps of a PM Plan. Here are steps to do it.

  • Prepare a document based on maintenance manual to upload to Document module in Calem.
    • The document should include the sections of maintenance instructions from a manufacturer's maintenance manual.
    • If the maintenance manual is in paper format, scan the relevant sections into a PDF document.
  • Create a document in Calem for the document prepared above.
    • Create a new document in Document | Document List
    • Upload your document to Calem
  • Reference the doc in a PM Plan
    • Go to your PM Plan (PM module | PM Home | PM Plan)
    • Create a document row to reference the doc uploaded above.
    • Write down the Seq (10) of the document row.
  •  The last action is to reference the doc in a step description of the PM Plan.
    • Create a new step in the step list.
    • Use "#10" to reference the document row just added. 
  • The document reference will show as a link. Clicking the link from Calem Mobile or web will open the PDF document. 
  • Your techs can view the maintenance doc from Calem Mobile in a tablet or phone, or from Calem Web in a browser.


Appendix B. PM Uniqueness

A PM is uniquely identified by its PM Plan (plan_id), Asset (asset_id, or location_id if asset is not defined) and sequence (seq) in addition to its PM number which is unique by itself. The default sequence number is set to 1 to prevent creation of PMs for the same plan and asset. 

  • Creating a PM for the same PM Plan and asset will raise a duplicate key error.
  • If there is a need to create PMs for the same PM Plan and asset, populating seq field to prevent the duplicate key error.