Know the site.
Follow the issue.

Site atlas — identifying labels masked
Site atlas
THE PROJECT

We used a site atlas and schematic array to give the energy assets a location and a readable structure.

The report then brings the recorded observations into a view that can support follow-up.

PROJECT TYPE
Interface design & front-end development
DOMAIN
Asset and service reporting
DESIGN FOCUS
Connecting energy site records to service follow-up
THE DESIGN DECISION

The asset view leads to a service record.

A site-level summary needs a route into the service evidence behind it. A reported issue should retain its place in the wider asset context.

We gave the issue its own page rather than relying on a coloured marker in the atlas. The site, service report and next action remain connected.

THE BUILD

The pages we designed.

The build brings site atlas, service report and issue follow-up into one workspace.

Screen

Site atlas

We used a site atlas and schematic array to give the energy assets a location and a readable structure.

View the screen ↓
Screen

Service report

Keeps “Record”, “Owner”, “Recorded” and “Review state” together for comparison and review.

View the screen ↓
Screen

Issue follow-up

The completeness check identified one absent interval record.

View the screen ↓

Expanded project screenshot
FROM THIS PROJECT TO YOURS

Have a similar project?
Let’s discuss the work.

Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.

Discuss your project Explore custom software development

Search Anteomnio

A few places to start

↑ ↓ to explore · Enter to openFull search page