Inspection Due is an operator for cranes, lifting gear, and vessels that must be examined on a statutory clock. Under LOLER, HSE's leaflet INDG422 puts thorough examination at least every 6 months for lifting accessories and equipment that lifts people, and every 12 months for other lifting equipment, unless a competent person's examination scheme says otherwise; 29 CFR 1910.179 puts periodic crane inspection at 1 to 12 month intervals.
This operator reads the asset register in IBM Maximo Manage, Limble CMMS, UpKeep, or Brightly Asset Essentials, the last examination date on each item, and the reports filed in SharePoint. It proposes the inspection work order as each item comes due, and a removal from service when an item is overdue or its report carries a defect.
This is a reference listing. It documents what Fibric would read from Inspection Due and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.
Inputs
The asset register: Maximo assets from mxapiasset with location and status, Limble assets with custom fields, UpKeep assets with statuses, or Brightly Asset Essentials assets
Each item's class and last thorough examination or periodic inspection date, in an asset custom field or a Google Sheets range you keep
Examination reports and certificates filed as documents in a SharePoint library or list, with the item they belong to
Inspection work already scheduled: Limble PM tasks, UpKeep preventive maintenance schedules, Brightly PM procedures, Maximo work orders
The ERP's fixed asset list, read through Odoo search_read, so an item on the books but missing from the register is flagged
Defects reported on the last examination, as recorded on the work order or the report
Proposed actions
Target capability: propose an inspection work order for each item due, in Maximo, UpKeep, or Brightly, or as a Limble PM task through POST /v2/tasks
Target capability: propose removing an overdue or defective item from service: a Maximo changeStatus, an UpKeep asset downtime record, or a Brightly asset status change
Target capability: propose a site schedule: items overdue, items due inside the horizon, and items with no examination date on record
Target capability: propose an appended row in the register sheet, or a list item in SharePoint, when a new report is filed against an item
Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.
What you can build
Schedule LOLER examinations from Maximo
Lifting accessories and passenger lifts are due every 6 months and other lifting equipment every 12, from the last examination date on mxapiasset. The operator proposes a work order for each and a changeStatus for any overdue item.
A Google Sheets register holds each crane's periodic inspection interval, inside the 1 to 12 month range 29 CFR 1910.179 allows. The operator proposes a Limble PM task as each comes due and appends the completion row.
When the filed report names a defect, the operator proposes an UpKeep asset downtime record and a work order for the repair or replacement, and lists the SharePoint report beside it.
Odoo's fixed asset list is read with search_read. Items on the books with no register entry are proposed as new Brightly assets with an examination date to fill in.
A CMMS holding the items as assets: IBM Maximo Manage, Limble CMMS, UpKeep on the Enterprise Plan, or Brightly Asset Essentials
A last examination date and an interval or examination scheme per item, on the asset record or in a sheet
The rule set you operate under, in the operator's configuration: LOLER intervals, 29 CFR 1910.179 intervals, or your own scheme
Optional: a SharePoint library for reports, and an ERP connector such as Odoo for the fixed asset list
Authentication
Registers, reports, and work orders are read and written through the CMMS, file, and ERP connectors you bind, using the accounts they hold; the operator keeps no login of its own.
Limits
Intervals are as you configure them. INDG422 gives 6 months for accessories and equipment lifting people, 12 months otherwise, unless a competent person's scheme differs
A thorough examination is done by a competent person; the operator schedules and records it and never judges an item fit
Removal is proposed, not done. Under LOLER a serious defect means taking equipment out of service at once, on the spot, before any proposal
An item missing from the register is found only if it appears in the ERP asset list or a sheet; gear recorded nowhere stays invisible
Access and pricing
Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.
Each work order and each removal from service. You see the item, its class, the last examination date and report, the interval applied, and the due date. Approve, change the date, or dismiss. A removal shows the defect or the overdue period that justifies it.
What record is kept?
The register row or asset read, the interval and rule applied, the work order or status change as the CMMS made it, who approved it and when, and how to reverse it. Filed reports are linked to the item they cover.
Does it examine equipment or judge it fit?
No. Thorough examinations and periodic inspections are carried out and reported by a competent person. The operator schedules the work, records the report against the item, and proposes removal when the report or the calendar says so.
Ask about Inspection Due
Ask about the capabilities and requirements in this listing.
This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy