Features

What your teams use in the field, and what you control from the office

A production workshop that turns a video into a document, a governance layer that decides what gets published, and your systems that receive the result.

The production workshop

Where video becomes a document

What the writer and the technical reviewer work with, starting from a clip shot on a phone.

01

From clip to draft

Someone films the task on a phone. Prism transcribes the speech, recognizes actions and objects, splits the clip into distinct steps and turns out a structured draft. No manual writing required.

  • Upload .mp4, .mov, .avi, .mkv, batch processing
  • Audio transcription aligned to timecodes
  • Action and object detection (vision engine)
  • Automatic splitting into distinct steps
  • Extraction of the PPE detected on screen
  • Source language and starting template chosen when queued

02

A draft you adjust, not a document you write

Each step keeps its original video segment. The writer fixes a word, picks the right image, adds the tool and the safety warning. The work is correcting, not writing.

  • Video window for each step (time segment of the source)
  • Candidate images extracted, manual capture available
  • Tools used and estimated duration for each step
  • Metadata: title, equipment/area, category, CMMS code
  • Lockout step type for LOTO procedures
  • Safety warnings and PPE callout for each step

03

Configured once, inherited everywhere

The site admin sets the logo, the accent color, the page structure and the format. Every procedure on the site inherits the same look, without anyone having to think about it.

  • Site accent color and logo (PNG, SVG)
  • Logo position: left, right, centered
  • Layouts: photo beside, photo above, two or three columns, text only
  • Format and density (A4 or Letter)
  • Choice of included blocks
  • Automatic inheritance by every procedure on the site
  • Configuration restricted to site or Prism admins

04

One procedure, many teams

The procedure is captured in the language of the person doing the work, and distributed in each team's language. Each language has its own status: nothing counts as translated until it has been reviewed.

  • Source language declared per procedure (e.g. fr-CA)
  • Translations generated on demand
  • Status per language: not generated, to review, generated
  • Regional variants (e.g. es-MX)
  • Generation permission-controlled and logged

Governance

Where the document becomes official

Who is allowed to do what, who has to approve, what gets logged and what goes out to your systems.

01

Granular access control, not file sharing

Six roles, explicit permissions, and a simulated role to check a configuration before deploying it. Every blocked action says exactly which permission is missing.

  • Writer: draft, step content, metadata
  • Technical reviewer: technical validation
  • Document owner: signature and publishing
  • Site admin: template, users and roles for the site
  • Prism admin: cross-site administration
  • Field reader: view only
  • Simulated role to preview a configuration
  • Every blocked action shows the missing permission

02

Named owners, not an inbox

Writing, technical validation, OHS approval, publishing. At any moment, you can see who needs to act and for how long. A return to the writer stays in the workflow, not in an email.

  • Statuses: writing, in validation, published
  • Technical review, then OHS approval where applicable
  • Shows who needs to act, and since when
  • Return to the writer with comments
  • Dashboard focused on tasks and urgent files
  • Every action logged with actor and timestamp

03

The attributes expected of a controlled document

Version, date, owner, reviewer, signature and revision table. The signed PDF passes inspection because it was produced as a controlled document, not formatted after the fact.

  • Version number and revision date
  • Standard owner and named reviewer
  • Document owner's signature
  • Detailed revision table
  • Quality-standard document numbering
  • QR code to the source video
  • Signed PDF export

04

Timestamp, event, object, actor, site

Anything that touches a procedure or a permission leaves a trace. When the auditor asks who approved what and when, the answer is on screen, not in someone's memory.

  • Step edit and technical review approved
  • Return to the writer
  • Permission revoked or granted
  • Publication to SharePoint
  • Translation generated
  • SSO sign-in and signed PDF export

05

Prism feeds your systems rather than replacing them

The published document goes to SharePoint and your maintenance systems. The right to distribute is separate from the right to publish: a document can be official without having been distributed yet.

  • SharePoint: automatic distribution of published documents
  • CMMS / ERP: SAP PM, Maximo, MP2
  • Azure AD SSO
  • Distribution right separate from the publishing right
  • Multi-tenant: active site selection
  • Statistics per site and role matrix per site

In real-world conditions

Built for field conditions

Capture on a phone, review on a tablet, approval at the office. Each role works with the tool it already has.

Two workers in safety gear inspecting a rock face at a mine site.

We don't replace your systems. We give them what they're missing

Your CMMS, your ERP, your SharePoint and your OHS systems stay in place. What they're missing isn't one more feature: it's up-to-date documentation, in the right template, approved by the right people.

Prism captures the hands-on technique once, at the source, and turns it into a controlled document. Nothing goes to your systems without clearing technical review, OHS approval where it applies, and the document owner's signature.

You keep your processes and your rules. What changes is the quality and freshness of what feeds them.

A technical demo, with your integrations and your role matrix