IFS Cloud end-to-end process flow

SEAM AS · Project ORIGO · Draft, September 2026 · Internal use only

The whole chain from enquiry to service, one step per row, in the phases of the SIS project flow P04.02. Click a step for its IFS objects, statuses, rules and open issues. Where a process diagram has more detail, the step links straight to it.

The same chain as a swimlane diagram. Each column is a department, each dashed band a phase, and the arrows show where work is handed from one department to the next. HR, HSEQ and Finance run down the right and connect to the steps they touch. Click a step, a department, a phase or a touchpoint.

Solid = main chain. Dashed = side path or parallel step.

100%
hand-over side path or loop touches open issue Outside IFS no IFS work in this box dashed box = side path

Drag to pan. Details open in a panel on the right.

The same product at seven levels across SIS, E3 and IFS, laid out like Product structure lifecycle rev05. Each coloured stripe is one level and each dashed frame one system, so a stripe read left to right follows one thing through every system. Click a box for its record and what it connects to, a level to follow it across, or a system name to see it on its own.

100%
contains rolls up to references future

Drag the diagram to pan. Details open in a panel on the right.

The simplified table from rev05. Click a cell to open its records in the detailed diagram.

How a structure moves from E3 design to purchasing, from BOM workflow rev02. Click any box for the notes on the diagram. Red marks are changes made in rev02.

Where structures come from and where they go over the life of a vessel, from Product lifecycle management rev03. Two tracks: selling from templates, and delivering from E3. Every delivery context ends in the same service object structure. Click any box for details.

Example on the diagram: Installation Site (vessel ID) 10236, Package ID (system ID) 11.

Use the flow as an end-to-end tracker. Mark any block OK, In progress or Not OK and leave comments, from here or from the block itself in any tab. Changes are shared with everyone automatically — through this site when you open it from the ORIGO web address, or through a shared OneDrive folder when you open the file from your PC (below).

Shared tracker for everyone

Keep this HTML and the tracker files in the same OneDrive or SharePoint folder, and open the HTML from that folder in File Explorer (not from the Teams or browser preview). Click "Connect to the OneDrive folder…" once and pick that folder. After that it syncs by itself every 30 seconds: your changes go into your own file, and everyone else's are merged in. Windows asks to confirm the folder once per session; the first click anywhere on the page answers it.

The folder isn't on my PC yet
  1. Open the folder in SharePoint: End-to-End testing
  2. Click Add shortcut to OneDrive in the toolbar (or Sync for the whole library).
  3. Come back, press Connect to the OneDrive folder… and paste the path: %OneDriveCommercial%\End-to-End testing after a shortcut, or %OneDriveCommercial%\Project Origo - SEAM ERP (external) - Documents\0. Project office\06 - Test Management\End-to-End testing after a sync.

No shortcut and no sync? You can still test: use Export status (JSON) and send the file to whoever collects the results, and they use Import / merge JSON.

Folder in Teams or the browser: open the SharePoint folder — use Sync or Add shortcut to OneDrive there, then open this file from File Explorer.

–
Test values Fill these in once and the test steps everywhere show your real IDs instead of «placeholders».

Without the shared folder, saving happens in this browser on this computer only. To move your status to another PC by hand, use "Download copy with my status" (a new HTML file with everything built in) or export the JSON. Importing merges: for each block, the most recently updated version wins, so colleagues' files can be combined.

Process steps