Version control and approvals

Every change versioned. Every version explained.

Every project keeps a full history on your server, built on Git. Your engineers never commit, branch or merge: each change is saved as a version, with who made it, when, and the request that asked for it.

PLC › Line4_CasePacker.L5X File History
Approved by Priya Shah, v7 · Today 3:58 PM · “Door 3 checked on the rig.”
  1. Today

    1. Approved by Priya Shah

      In Line 4 PLC · Sam Rivera

    2. Note: Tested on the FAT rig

  2. Yesterday

    1. Downloaded by Sam Rivera

Changes in v7 Cell_Permissives · Rung 3 changed Before in red, after in green
3 RUN PERMISSIVE The cell may run only with every guard door closed and the safety system healthy. Door1_Closed Door2_Closed Safety_OK Run_Perm 3 RUN PERMISSIVE The cell may run only with every guard door closed and the safety system healthy. Door1_Closed Door2_Closed Door3_Closed Safety_OK Run_Perm
Asked in chat by Jordan Lee Restore v7 Download

Saved without anyone saving it

A version is saved each time a request, an upload, a restore, or a rename, move or delete changes a file. Each names the request that saved it and opens the chat it was asked in.

  • Who, when and why on every version
  • The other files the same request changed
  • Restores that are versions of their own, so nothing is lost
  • Links to a version that survive renames and moves
A file’s history in Altitude: an approval asked for, a version saved with its request’s name, downloads, and a note that v4 was loaded on Line 4’s PLC

Diffs drawn the way each tool shows them

Studio 5000 changes drawn as rungs, with safety changes marked Safety. TIA Portal object by object, with its hardware. TwinCAT, Ignition and every robot brand in their own views, spreadsheets row by row, and documents as a redline.

A TIA Portal function block’s change in Altitude: a declaration added and a network drawn before and after

Approvals that follow the contents

An approval belongs to what a file holds, not to a version number: restoring, renaming or copying approved contents keeps them approved, and any edit after it needs approving again.

PLC › Line4_CasePacker.L5X Waiting on Priya Shah Changes requested Approved
  1. JL Jordan Lee asked Priya Shah to approve v6 11:24 AM Tested the infeed on the FAT rig.
  2. PS Priya Shah requested changes to v6 1:10 PM Add door 3 to the run permissive too.
  3. JL Jordan Lee sent back v7 3:45 PM Door 3 added to rung 3 of Cell_Permissives.
  4. PS Priya Shah approved v7 3:58 PM Door 3 checked on the rig.
Approval record v7 · SHA-256 4e1c 9a07 … 2bd3 Download

Know what is loaded where

The history records which version was downloaded, by whom and when, keeps your note of which version was loaded on each device, and says whether it was approved when it went out.

A Studio 5000 program’s history in Altitude: downloads, a note that v4 was loaded on Line 4’s PLC, an approval against the risk assessment, and a safety change drawn as rungs
  • Notes on any version, such as who it was sent to or what was tested
  • An approval record workbook, with each approved version’s SHA-256
  • Compare any two versions, or any version with the file as it is now

FAQ

Questions teams ask first

Do our engineers need to learn Git?
No. Git keeps the history underneath, and nobody commits, branches or merges. Every change is saved as a version on its own.
Where is the history kept?
On your Altitude server, with the project. A project’s files, their history and its chats go with it when it is exported, archived or backed up.
Which files show a visual diff?
Studio 5000 and TIA Portal programs, TwinCAT projects, Ignition resources and robot programs from every brand Altitude reads, each in its own view, with spreadsheets row by row and Word and Markdown as a redline.
Can we record which version is on each machine?
Yes. Note where a version was loaded, from the history or by asking in a chat, and the history marks that version as in the device.

Keep exploring

More ways teams use Altitude

See it on the work your team does every day

We'll walk through the workflows that matter most to your team, on the PLC, robot and HMI platforms you run, from review and troubleshooting to documents and migration.