Approved document in, work out
A plugin reads the approved document it is for, such as the maintenance program or the audit programme, and runs it: tasks, schedules, checklists, records.
Plugins read what your approved documents say and run it, day to day: at one site, in a sandbox, with only the access you consent to. Written by us, and by anyone who builds to IMS Creator's requirements.
Part one of IMS Creator writes your management system. Plugins are part two: they keep it operating, and show your auditors that it is.
A plugin reads the approved document it is for, such as the maintenance program or the audit programme, and runs it: tasks, schedules, checklists, records.
When a document is approved again, its plugins propose what follows ("3 new PM tasks, 1 interval changed") and a person accepts or declines, as everywhere else.
Each plugin lists what it asks for in plain words. A company admin installs it (anyone can request one), its records stay at that site, and they export to CSV and JSON whenever you like.


Fifteen are available today, from us: what each needs is stated, and it is installed per site. Any publisher can build more.
The promise that each company's data is its own holds for plugins too.
Functions run as WebAssembly with no file system and no network: only IMS Creator's own requests, within limits on memory, processing and time.
Every request is checked against the permissions your admin granted. A plugin runs inside one site and can never name another company.
Automated checks, then a person's review against a published policy. IMS Creator runs only plugins signed with the platform's key.
Installs, updates and removals go to your company's audit log; every record change and run is in the plugin's activity at the site.
If a plugin breaks the rules, we can suspend it at every site in one step. It stops running; your records stay yours.
Plugins cannot send data off the platform. When they can, it will be only to hosts named in advance, each one consented to by your admin.
Know a process that should run from an approved document? Build it once, and every company on IMS Creator can install it. Sign-up is open, and publishing is free.
id: controls-tracker name: Controls tracker version: 0.1.0 summary: "Checks the controls in the approved risk register." clause: "8" requirements: [operational-control] permissions: - documents:read:risk_register # shown to admins in plain words functions: functions/main.wasm models: check: label: Control check fields: control: {type: text, required: true} owner: {type: text} due: {type: date} workflows: check: initial: due states: due: {label: Due} done: {label: Done, closed: true} transitions: - {key: done, from: [due], to: done, requires: [owner]} events: - {when: document.approved, kind: risk_register, function: propose_checks}
Records, workflows, pages, permissions, scheduling, audit and export come with the platform. Write only what is specific to your plugin.
Each plugin names the requirements it helps meet and sits under its clause, so companies find it where they look for it.
The Publisher Agreement and the Plugin Review Policy say what we check and why, before you write a line. Paid plugins are on the way.
See the PM scheduler and Audit manager working from your kind of documents, or tell us the plugin you would like to see next.