Bulk Documentation
Product referenceInsights and visual managementAtlas

Beta

Review cross-plant performance in Atlas

Use Atlas to compare every plant side by side: build a saved pivot of sites against metrics, read it by period, drill into any cell, and share it.

Last updated

Atlas is the cross-plant executive dashboard in Bulk. It lays out your sites down the rows and your chosen metrics across the columns, so you can scan how every plant is performing against the same measures at a glance. Instead of opening each plant's dashboards one at a time, you read the whole organisation in a single grid — hence the tagline you see under the page title, "Every site, side by side."

Use Atlas when you need an operations-wide picture rather than the detail of one plant: a morning review across the group, a weekly performance call, or a quick check on which site is falling behind on a shared target. Each layout you build is saved as a named view (a tab), so different audiences can keep their own scorecards.

Atlas is in beta

Atlas is a beta feature. In the left navigation it appears under Modules with a Beta badge. The capabilities described here are live in the product, but the feature is still evolving, so expect refinements to the layout and controls over time. This page describes the behaviour as it exists in the current build.

Before you start

To open Atlas you need the atlas.view permission. In a standard Bulk role setup this permission is granted to the Entity admin, Manager, and Dashboards roles. If Atlas is missing from your navigation, ask an administrator to add a role that grants it.

Two further capabilities are gated separately:

  • Setting monthly targets requires the atlas.manage permission (granted to Entity admin in the standard setup). Anyone with atlas.view can still read views that use targets; they simply cannot edit the target numbers.
  • Editing a specific view depends on that view's own access. The person who creates a view is its owner and can always edit it. Other people can edit only if the owner shares it with edit rights.

Atlas compares the sites (legal entities) that exist in your organisation. If your Bulk account has a single site, Atlas still works, but the cross-plant comparison is most useful once you operate more than one plant.

Open Atlas

Select Atlas in the left navigation, under the Modules group. The page opens full width. The heading reads Atlas, and a row of saved-view tabs sits below it.

The first time you open Atlas — before any view exists — you see a Welcome to Atlas panel with a Create your first view button. Selecting it starts a blank view that you can shape with the fields rail described below.

Saved Atlas view comparing buffer value, completed jobs, OEE and training across three Wayne plants.
A saved Atlas view compares every plant and its totals. These actual values have no target shading because no targets are set.

How an Atlas view is built

Every Atlas view is a pivot with three moving parts.

Rows are your sites. Atlas groups the rows by legal entity. An optional All sites total row sits at the top and rolls the metrics up across every plant; each plant then appears as its own row beneath its group.

Columns are metrics. You choose which measures to compare. Atlas ships a catalogue of around thirty built-in metrics tagged by category — Inventory, Production, Safety, Training, Tasks, People, Audits, Quality, and OEE — covering measures such as OEE, Completed jobs value, Stock on hand value, Incidents open, Audits overdue, Training compliance, and Active headcount. You can also add any KPI you have defined in the KPIs module as a column, so custom measures sit next to the built-ins.

The Cells picker reformats the whole sheet. Choose Actual for the number, Plan / Act / Δ for the target and gap, or Δ to target for only the difference. Rollup methods belong to each metric; there is no global Rollup or Period picker.

Each metric starts expanded into Day, WTD, MTD and QTD. Use its minus control to collapse it to Day, or its plus control to expand it again. Expansion is temporary and is not saved with the view.

All four periods use completed site-local calendar days and exclude today's partial activity. Day is the previous complete local day. WTD, MTD and QTD end at yesterday's close. Snapshot metrics reconstruct each day-end, averaging the completed closes for to-date periods. Missing reliable history shows #N/A rather than an invented zero.

Shape the layout

To change which metrics and filters a view uses, right-click an editable view tab and select Edit layout, or use the add-metric control in the sheet. The fields rail opens alongside the pivot.

The rail has two parts:

  • A Catalogue of everything you can add — metrics, KPIs, and the Sites dimension — with a search box ("Search metrics, KPIs, source..."). Each catalogue row is tagged with its category and source, where Live metrics read current data and Analytics metrics come from the analytics snapshots.
  • The Layout zones — drop into area, with a Metrics zone (the columns) and a Filters zone. Drag a catalogue row into a zone, or select it to add it without dragging. Add the Sites field to the Filters zone to narrow the view to specific plants; the site picker then lets you choose All sites or a subset.

Each metric column has a settings menu where you can give it a custom Label and, for built-in metrics, open Monthly targets.

Atlas Fields catalogue with all four selected Metrics and Sites All sites in the complete Filters zone.
Add metrics to the Metrics zone and Sites to Filters. This unsaved draft keeps All sites selected.

Save it as a view

Layout changes stay local until you save them. While a view has unsaved edits its tab is marked Unsaved changes, and a Save view button (with Discard beside it) appears in the header. Selecting Save view persists the layout; Discard reverts it. If you try to switch tabs with unsaved changes, Atlas asks whether to Stay here, Discard & switch, or Save & switch.

Create additional views from the New view control at the end of the tab strip: Duplicate current view copies the active layout, or Blank view starts empty. A view's own tab menu also lets you rename, duplicate, delete, share, and set it as your default.

Read the cells and drill in

The status colour of each cell — good, mid, or bad — reflects how the value compares to its target, taking into account whether higher or lower is better for that metric. Cells without a target show their actual value without target shading. Targets come from the metric's monthly targets (see below) or, for KPI columns, from the KPI's own target.

Select any cell to open a drilldown panel for that plant, metric, and period. The panel shows widgets that explain the number, such as recorded running and downtime hours for OEE or a trend for completed jobs, along with a note field for team context. A widget may show no data when that period has no matching records. If you can edit the view, an edit control lets you add, reorder, or reset the panel's charts, and those choices save with the view like any other layout change.

Set monthly targets

Monthly targets drive the heat shading and the plan-versus-actual cell modes. For a built-in metric, open its column settings and choose Set targets… under Monthly targets. The targets editor shows your sites against a three-month window, with arrows to move quarter by quarter, and you enter a target per site per month.

Editing targets requires the atlas.manage permission. If you have atlas.view but not atlas.manage, Atlas hides the Set targets… action so you are not offered inputs that would fail to save.

Atlas targets and KPI targets are separate

The monthly targets you set here belong to Atlas built-in metrics. KPI columns bring their own targets from the KPIs module. See the related links below for managing KPI targets.

Share a view

Open the Share action from a view's tab menu (available to the owner and to anyone the owner has given edit rights). The Access picker offers three modes:

  • Private — only the owner can see the view.
  • Everyone — everyone with Atlas access can see it.
  • Restricted — only the chosen Roles and People can see it. Saving replaces the current restricted list.

When someone without access opens a restricted view they see a No access to this view panel with a Request access button; the request notifies the owner. The owner then approves or denies pending requests from the same share dialog, under Access requests.

Example: Wayne's operations review

Bruce opens Wayne Site Review, which compares Blüdhaven Fabrication, Gotham Applied Sciences and Wayne Aerospace. Its four columns are Buffer on hand value, Completed jobs value, OEE and Training compliance, with group and all-sites totals above the plants.

Gotham's OEE WTD value is 100%. Opening that cell shows 60.7 running hours and zero downtime. There are no downtime reason bars for this period. Bruce can read the complete recorded-time breakdown and weekly note controls without inventing an explanation for missing downtime.

When adjusting his own layout, Bruce can add Sites to Filters and leave All sites selected. That change stays a draft until Save view. Discard restores the saved view. Sharing and monthly targets can be set separately when needed; this example changes neither.

Gotham OEE WTD drilldown showing100% efficiency,60.7 running hours and zero downtime with weekly note controls.
The OEE drilldown shows the recorded time behind the value. Gotham has 60.7 running hours and zero downtime in WTD, so there are no downtime category bars.

What you can expect

After building and saving a view, you have a reusable scorecard that any permitted teammate can open. The readbar reformats every cell together, so changing cell mode is consistent across plants; period expansion is controlled per metric. Targets you set turn the grid into a status board, and any cell drills down to the detail behind it. Views persist as tabs until you delete them; deleting a view removes it for everyone it was shared with, but never changes the underlying production data.

Limitations and feature state

  • Beta feature. Atlas is in beta and carries a Beta badge in the navigation. Controls and layout may change as the module matures; treat this article as current rather than final.
  • Permission gating is enforced by the server. The atlas.view and atlas.manage permissions, and each view's own sharing, are enforced in the backend, not only hidden in the interface. Missing a permission means the corresponding action is unavailable, not merely invisible.
  • Rollups belong to the metric. Atlas combines totals, rates and OEE using each metric's own method; the current sheet has no global Rollup picker.
  • Closed periods exclude today. Snapshot metrics reconstruct completed day-ends. Current partial activity is excluded, so new records from today may not appear in the displayed periods.
  • Freshness is explicit. These captures use a saved view with fully rendered live-preview values while its snapshot is being prepared. Snapshot completion was not verified. None of the captured cells have monthly targets, so no target heat shading is shown.

Troubleshooting

  • Atlas is not in my navigation. Your roles do not grant atlas.view. Ask an administrator to assign a role that includes it (for example Manager or Dashboards).
  • A view shows "No access to this view". The view is Restricted and you are not on its list. Select Request access to notify the owner, or ask them to add you.
  • I cannot set targets. Setting monthly targets needs atlas.manage. If Set targets… is not offered, you have view access but not manage access; ask an Entity admin to set the targets or grant the permission.
  • I cannot find the old Rollup or Period picker. The current readbar only has Cells. Use the plus/minus control on each metric to expand or collapse its four fixed periods.
  • An OEE breakdown has no downtime bars. Check its recorded running and downtime hours. Zero downtime in a closed period does not produce reason bars; do not assume today's activity belongs to that period.