Skip to main content

Release Notes 26.21

Released October 14th 2026

Written by Roy Abery

Ensure you have the correct version running!
If you don't see 26.21 in the bottom left corner, please clear your browser cache.
​
​


​Note: If a new feature is not visible, you may not have the correct access permissions, the option (menu item) may not be enabled on the project, or the feature is otherwise not enabled in e.g. the entity settings.
Please contact your O3 System Admin or Project Admin, or use your organization's O3 support process, if you require access to a new feature.
​
​Highlights: Please check out the 'What If?' section for some awesome IWP sequencing functionality being added to the O3 platform in 26.21.
​

Timesheets

Lock It In

Reviewers can now make changes to a timesheet in place, whatever its status, without the reject and resubmit cycle. Once the data has been passed on to payroll or payment systems, timesheets can be locked so nothing drifts out of sync.
​
​Where and How:
Edit directly from the Timesheets grid view (via Overview/Cross Project or Project navigation).
​
To lock or unlock, open the 'Overview' module (bottom left), select Timesheets, multi-select the timesheets in the grid (e.g. using the Shift key) and choose Lock or Unlock from the Action menu.
​
Or via the Project Navigation menu -> Project Management -> Timesheets (grid view).
​
​Overview (Cross Project) Timesheets – use the Action button (top right) and select Lock/Unlock for the selected rows:


​
​Grid with 'Lock' status column:


​
​Details:

  • Users with the new edit permission can edit an unlocked timesheet in any status (for example Submitted or Approved) from both the detail form and the line items grid; the change saves without a reject/resubmit.

  • Separate new permissions control who can lock and who can unlock timesheets.

  • One or more timesheets can be locked or unlocked at once from the cross-project timesheets grid.

  • A locked timesheet shows a lock icon, all edit controls are disabled, and its status cannot be changed until it is unlocked.

  • Locking and unlocking apply to both Crew and Individual timesheets, and are manual actions.

  • Editing hours on an approved timesheet updates the Actual Hours on the affected IWPs, including both the old and new IWP when an entry is moved.


Know Your Fleet

A new Construction Equipment settings entity lets administrators configure the equipment used on a project, in the same way Employees are configured for personnel.
​
​Where and How:
Project Setup menu -> 'Construction Equipment'. Records can be added manually or loaded in bulk via import.
​


​Details:

  • Each record holds Asset Number, Serial Number, Construction Equipment Type, Make, Model, Construction Equipment Shift and Construction Equipment Status.

  • Construction Equipment Shift and Construction Equipment Status are project-configurable lookups, so values can be maintained per project.

  • Records can be created manually or via bulk import from a spreadsheet.

  • New role permissions cover the entity, including import.


Clocking the Machines

Forepersons can now log equipment hours on Crew timesheets alongside their crew's hours, in the same daily submission.
​
​Where and How:
Enable the new Construction Equipment option in the Timesheet settings (Project Setup -> Project Settings -> Timesheets). A Construction Equipment Hours section then appears below Employee Hours on crew timesheets.
​
​Enabling Construction Equipment Hours on Timesheets:


​Remember to Save Changes!
​
​Construction Equipment Hours section enabled.
​Add entries from the Construction Equipment list – see Know Your Fleet:


​Details:

  • Configured construction equipment can be selected on a crew timesheet and hours entered across four categories: Operating Hours, Non-Operating Hours, Maintenance Hours and Hours Out-of-Service.

  • With the project setting turned off, the Construction Equipment Hours section is not shown.

  • Timesheet imports can write to both employee line items and construction equipment line items. A row containing both employee and equipment fields is rejected with an error.

  • Available on Crew timesheets only.
    ​

Mobile (ONField)

Pack Before You Go

When going offline, ONField now suggests the IWPs a foreperson is likely to need and downloads them in one step, so nobody arrives in the field without their packages.
​
​Where and How:
Tap the cloud toggle on the Home screen while online. The 'Entering Offline Mode' prompt lists your active IWPs.
​

​Details:

  • Suggested IWPs are those assigned to you that are not complete, and are either in progress (actual start set) or scheduled (planned start on or before today).

  • Each IWP shows its number, description, status (In Progress or Scheduled) and an 'Already downloaded' marker where applicable. Nothing is selected by default, and a Select All row is available.

  • Download and Go Offline shows progress for each IWP and overall, then switches to offline mode. Selected IWPs that were already downloaded are refreshed.

  • If no active IWPs are found, or you tap Skip, the existing 'Switch to Offline Mode?' confirmation is shown.

  • If some downloads fail, a summary lists the failed IWPs; successful downloads remain available offline.

  • Canceling during a download keeps you online. An interrupted first download is not marked as downloaded, and an interrupted refresh keeps the previous copy.

  • If the active-IWP check could not be completed, the offline confirmation message says so.


Locked Means Locked

Timesheets locked in the web app are now locked in ONField too, so field edits cannot change data that has already been handed off.
​
See Lock It In for lock/unlock functionality.


​Details:

  • A timesheet's locked state syncs to ONField and shows a lock indicator matching the web app.

  • Locked timesheets are read-only in ONField; detail and line item edit controls are disabled.

  • Unlocking a timesheet on the web makes it editable again in ONField after sync.

  • If a timesheet is locked before the device syncs, any offline edits to it are rejected at sync; the locked values are kept and the user is informed.

  • Timesheets cannot be locked or unlocked from ONField.

Workface Planning

What's Left to Build?

IWPs now have a Forecast Remaining Quantity field on the header, so planners can record the crew's own forecast of remaining work in quantity terms.
​


​Details:

  • Planners can enter a non-negative decimal value; negative or non-numeric entries are rejected.

  • The value is saved and retained on reload.

  • The field is standalone: it does not feed rollups, calculations or reporting.


Right Task, Right Contract

Execution Task Types can now be limited to one or more contracts, so planners adding tasks manually to an IWP only see the task types that belong to that IWP's contract.
​
​Where and How:
Project Setup -> Project Settings -> Entity Settings -> IWPs -> Execution Task Types. Use the new 'Available Contract for Manual Task' field.
​
​Open an IWP Execution Task Type from the grid (or add one):


Open an Execution Task Type and click the 'Available Contract for Manual Task' option, then choose the applicable contract(s).
For example, if the work is electrical, you may only want those task types to be available on the electrical contractor's contract.
​
​Editing the Task Type – add the applicable contract(s) to 'Available Contract for Manual Task':
​


​Details:

  • When adding an execution task manually to an IWP, only task types matching the IWP's Contract, or with no contract set, are offered.

  • Existing task types have no contract set, so they remain visible to everyone until assigned.

  • The Execution Task Types import accepts a Contract column with multiple values per row.

  • This only affects manual task creation on a work package; component filter rules are unchanged.


Scoped and Accounted For

User-Defined Entities can now be added as scope on an IWP, with a color-coded status showing which records are already packaged and which are still available.
​
​Where and How:
Enable 'Allow UDET Scope Children' in the IWP entity settings and choose the UDET types. A Scope tab then appears on the IWP detail form.
​
​Setup:


​With the option enabled, select the entity:


​Remember to Save Changes!
​
​Scope tab on the IWP detail form layout:


​When adding new scope, select the entity:


Then click the OK button to proceed.
​
​Packaging Status indicates where the UDET record is allocated (see Details below for a guide). The first record in this example is already in the scope of this IWP:

Packaging Status:
​


​Details:

  • Each UDET record shows one of three states: Available for packaging (green), On a different package (blue), On this package (purple).

  • The status is informational only and does not block association.

  • Only scope links count as packaged. A UDET with a general association to the IWP is converted to a scope link when added from the Scope tab, without duplicating it.

  • Removing a UDET from the Scope tab removes the association.

  • Copy Components to Associated IWPs, Copy Drawings to Associated IWPs and Include Attachments in Associated IWP Reports continue to work as before.
    ​


Only What You Need

The IWP Components table in report templates can now be filtered to a specific Object Type, so reports show only the items the site team needs, such as spools.
​
​From the Report Templates – Template Fields documentation, select a Report Type (entity) that supports Construction Components. The wording is generic, so the same applies to IWPs, EWPs and CWPs. The new 'Construction Components:Object Type' table will be listed with its available placeholders (fields):
​


​In this example, a Construction Components – Spool table has been set up in an IWP report template. The table uses the 'construction-components' keyword followed by ':' and the Object Type name used on the project (example, 'Spool'). This could be set up for a specific team that manages that object type, such as a piping discipline or contractor working on spool components:
​


​Details:

  • A Components table filtered to an Object Type (for example Construction-Components:Spool) lists only components of that type.

  • Templates without a filter produce the same output as before.

Scheduling

What If?

Sequencing IWPs from the IWP Lookahead now opens a full Sequencing Results report that explains what moved and why, and lets planners test staffing changes before committing to them.
​
​Where and How:
Workface Planning menu -> 'IWP Lookahead' -> 'Sequence IWPs'.
The Optimize dialog now includes a scenario builder; after the run you land on the Sequencing Results page.
​
​Getting there: Workface Planning -> IWP Lookahead -> Sequence IWPs:


​In the 'Optimize IWP Sequence' dialog, select the 'O3 Sequencer' option to enable What If scenarios, then click '+ Add Scenario':


Add one or more scenarios, e.g. to see what would happen to the project finish date if more crews were added.
​
​Choosing a basis for the scenario:


​Applying to all IWPs, or to a specific discipline or purpose:


​Sequencing Results – an overview of the impact of the applied scenario(s):


​Results for a single scenario:


​Scroll down to see the impact on headcount:


​Detailed 'What Shifted' report:
​


​Details:

What If scenarios

  • Scenarios can adjust additional crews (by discipline or purpose), crew size, productivity factor, hours per day and standard duration.

  • Each scenario is compared against the baseline run, labeled Current Optimized Sequence.

  • If an adjustment matches nothing (for example extra crews for a discipline with no crews), a warning is shown.

  • Nothing is staged on the Gantt until you apply a run.

Sequencing Results page

  • Summary tab: Key Measures (projected finish, peak headcount, crew utilization and projected manhours), each scored against the plan and the baseline, plus a score radar, weekly headcount charts by discipline or purpose, outliers, and a narrative explaining the run.

  • The narrative offers suggestion chips for changes that have been tested to move the finish, and explains why other changes would not help.

  • Scenarios tab: a scenario matrix marking the best run(s), with Apply on each run.

  • What Shifted tab: a per-IWP comparison of previous and new dates, with moved rows listed first.

  • Apply stages the chosen run on the Gantt; View Results reopens it.

  • Export creates a PDF management report.

Notes

  • Results are calculated for each run and are not saved.

  • Capacity delays are counted in working days and charged to the crew pool that actually blocked the IWP.
    ​

Team Boards and Actions

RFIs on Board

RFI is now available as an entity type on entity Team Boards, so RFI workflow and throughput can be tracked on a board.
​


​Details:

  • RFI appears as a selectable entity type when creating or editing a Team Board.

  • The RFI import accepts Team Board Name and Section columns to place imported RFIs on a board and section.


Who's On It?

The Actions Timeline (dashboard widget) can now be filtered by one or more 'Assigned To' users.
​
Open an existing dashboard (optionally add the 'Actions Timeline' widget), then click the widget's action button (three dots):


​From the action button, click the Settings option:


​Add a filter with 'Assigned To Users' and multi-select entries:
​


​Details:

  • Selecting users limits the timeline to actions assigned to them; clearing the filter restores the full timeline.


Which Project Was That?

The cross-project Actions grid now includes a Project Description column, making it easier to tell projects apart.
​
​Cross Project Actions grid with 'Project Description' added as a column:


​Details:

  • The description shown matches the description on the project.

Dashboards

Looking Ahead on the Curve

The Progress Curve widget now forecasts cumulative earned hours beyond today, instead of running a flat line, so you can see when scope is expected to finish.
​


​Details:

  • Cumulative Earned Hours shows actuals up to today, then continues as a dashed forecast line in the same color, with its own legend entry.

  • Each incomplete IWP's remaining hours are spread evenly across the working days between today and its end date; non-working days are skipped.

  • All incomplete IWPs in the widget's scope are included, including those not yet started. The forecast reaches 100% of estimated hours (Earned + Remaining = Estimated).

  • Overdue IWPs, and IWPs with no end date, add all of their remaining hours at today's date, showing late backlog as a step.

  • The incremental series and the planned curve are unchanged.

  • Changing widget filters or scope recalculates the forecast.
    ​

Project Setup

Areas Within Areas

Areas now support one level of sub-areas, in the same way Systems support SubSystems.
​
​Where and How:
Project Setup -> Project Settings -> Areas.
Open a top-level area to find the new Sub-areas tab alongside the General tab.
​
​Accessing the Areas grid:


​Select an area to open the Area form dialog (e.g. Area 10):
​


​Then choose the 'Sub-areas' tab. To add a sub-area, click the '+' button, or move an existing top-level area under this area (provided it has no sub-areas of its own):

When adding a new sub-area, enter the General details:


​Remember to Save!
​
Back in the Areas grid, sub-areas are identified by a value in the Parent Area column.


​Details:

  • From the Sub-areas tab you can create a sub-area (Unit defaults to the parent's), add an existing area as a sub-area, or edit and delete sub-areas.

  • Only top-level areas with no sub-areas that are not used by any other record can be added as a sub-area.

  • Only one level is supported: a sub-area cannot have its own sub-areas.

  • Area names must be unique across the project, whatever their level.

  • The Areas grid lists all areas with a Parent Area column. Existing Area dropdowns, filters and imports on other entities continue to list top-level areas only.

  • The Area import accepts a Parent Area column to load sub-areas in bulk.

  • A top-level area that still has sub-areas cannot be deleted.

  • Sub-areas use the existing Areas permissions.


Know the Requirements

System administrators can now look up the field names for system-level imports, using the same Data Requirements view already available for project-level imports.
​
​Where and How:
System Admin -> System -> 'Data Requirements'.
​


​Details:

  • The page lists every system-level import and behaves the same way as the project-level Data Requirements view.

  • Only users with system-level access can see and open the page.
    ​

Model

Credit Where It's Due

Parent components created by a sub-component parser rule now show the Model Parser Configuration and Parser Configuration Rule Name that created them, instead of appearing blank.
​


​Details:

  • Where a top-level rule produces the same parent, the top-level rule's name is kept.

  • Existing blank parents are updated on the next model refresh, without being deleted and recreated.


Did this answer your question?