Skip to main content

Create the RAMS each package needs, with a due date

Category: Safety

Screens every package for whether it needs a RAMS and works back from its start date, so high-risk work is approved well in advance.

Input Parameters​

ParameterTypeRequiredDescription
Additional Review InformationTextNoOptional context, assumptions or focus areas for the screening (e.g. known high-risk works, site ...
Baseline RAMS Lead Time (days)NumberNoHow many days before a package starts on site a routine RAMS should be approved. The task adjusts...
Create RAMS RecordsBooleanNoIf enabled, creates a RAMS record for each package identified as needing one — linked to its pack...
Create Summary ReportBooleanNoIf enabled, creates a markdown report summarising the RAMS screening and the records created.

Outputs​

Summary​

Type: Text/Markdown

Summary

Outputs​

Type: Array

Outputs

Completion Time​

Type: Text/Markdown

Completion Time

Report Id​

Type: Text/Markdown

Report ID

Rams Created​

Type: Number

RAMS Created

Packages Reviewed​

Type: Number

Packages Reviewed

Disclaimer​

Type: Array

Disclaimer

Example Use Cases​

Create RAMS for all packages needing one​

Screen every work package and create the RAMS records that are required.

Configuration:

  • Create Rams Records: True
  • Create Report: True
  • Default Lead Time Days: 14

Preview without creating records​

Screen the packages and produce the report only — no RAMS records are created.

Configuration:

  • Create Rams Records: False
  • Create Report: True

Tags: rams · packages · cdm · risk-screening · workspace-items · planops-report

Last updated: 2026-08-31