Shift handover
Handovers built from the shift’s own entries, then signed off.
Find out more ↗
Opralog: the operational record behind every shift.
Record what happens, keep the context and make it available to the people taking over. Opralog is our web-based logbook and shift handover system. Logbooks, instructions, registers, tasks and reports all live in one place, so control-room and shift teams work from the same record.
Use Opralog on its own, or extend it into the field with the optional Mobilog app.
Opralog is used on sites that run around the clock, where the next shift needs a clear picture of what happened, what changed and what still needs doing. Here’s how it helps.
01 / HANDOVER
A consistent shift handover, every shift
Entries from any logbook can be shared into the handover, automatically or by hand, so most of it is ready before anyone sits down to write it. It’s the same entry wherever it appears, not a copy.
Anything still open is carried forward and keeps the time it was first recorded. Shifts can be locked and signed off with names recorded, and if you want, the next shift can be held until it has accepted the handover.
02 / VISIBILITY
A clear view of your operation, without chasing anyone
Everything your teams record sits in one place, so earlier shifts are easy to search and filter. Reports run across several logbooks and can be emailed on a schedule, or as soon as a shift is signed off.
When something needs doing, it becomes a task for a person or a role, with a due date. Opralog can email people when a task is assigned or overdue, and you can see what was done and when.
03 / CONFIGURATION
Configured around the way your site works
When we first install Opralog, it’s like a blank sheet of paper. We set it up with you and train your superusers, who can keep shaping it with point-and-click tools and no programming.
Your trained superusers can configure Opralog around the way your site works. Build a generating-unit handover, a lab-results form, a valve register or a workflow for following up defects. Whether you run a power plant, refinery or manufacturing site, you can keep common standards across sites while giving each team the detail it needs.
04 / RECORDING
More accurate records, with less typing
Operators pick what happened from a list set up for your site, and Opralog adds the time and who logged it. Forms use drop-downs and short tables, do the sums as you go and highlight a value that looks out of range.
Connect Opralog with your plant historian, maintenance and permit-to-work systems, so teams can see relevant plant data alongside their operational records. Standard interfaces and APIs let these systems read data from and write data to Opralog, reducing manual entry and helping keep information accurate and consistent.
Clearer communication between shifts
Follow-up that doesn’t slip
Less paperwork and retyping
One record you can trust
05 / Applications
Where teams use Opralog
One system, used across the operation. Each of these is set up for your site.
Operational logbooks
Control room, maintenance, safety and other logbooks in one place.
Find out more ↗Inhibits and overrides
Keep long-term inhibits and overrides in a register that every shift sees.
Find out more ↗Registers
Registers set up for your site, with change approval if you need it.
Find out more ↗Tasks and follow-up
Turn an entry into a task with an owner and a due date.
Plant status
Plant data from PI and equipment status kept up to date from logged events.
Find out more ↗Work instructions
Daily instructions and standing orders where the next shift will see them.
Operator rounds
Rounds and inspections in the field with Mobilog, in the same record.
Find out more ↗06 / Features
Feature overview
A summary of what’s in Opralog today, grouped by area.
Logbooks and entries
- Chronological logbooks for any area: control room, maintenance, safety and more
- Entries picked from your own list of events, with time and user added
- Forms with drop-downs, tables, calculations and range warnings
- Entries can be back-timed, or scheduled for the start or end of a shift
- Attach files, photos and links to other systems
- Flags, such as safety-critical, plus search and filters
Handover
- Handover logbooks with your own sections
- Entries shared in automatically or by hand, linked rather than copied
- Carry forward, keeping the original time, or until a set date
- Lock and sign-off, with names recorded
- Option to hold the next shift until the handover is accepted
- Printed or emailed automatically as a PDF
Tasks and follow-up
- Tasks for a person or a role, with due dates
- Scheduled, repeating tasks
- Task dashboard showing what’s open
- Email when a task is assigned or overdue
- Reports on what was done and when
Registers
- Register logbooks set up in the configuration wizards
- Approval for changes, switched on or off as needed
- A clear list of current register items
Plant data and integrations
- Two-way PI interface: read, write and create entries from PI data
- OPC and a generic API
- Standard interfaces for historians, maintenance, permit and other systems
- Equipment status kept up to date from logged events
Reporting
- Summary, detail, handover, tabular and status reports
- Reports across several logbooks, saved for reuse
- Scheduled to email or file
- Sent automatically when a shift is signed off
- Export for use elsewhere
Configuration and administration
- Point-and-click wizards, no programming
- Your own logbooks, event lists, forms and reference lists
- Templates and locations
- Notifications on chosen conditions
- Users and roles managed by your superusers
Security and audit
- Full audit trail for entries and logbooks
- Access set by role
- Installed on your own servers or private Azure or AWS
Mobilog (optional)
- Our mobile app for iOS and Android
- Rounds, inspections and field entries
- Works offline and syncs when back in range
- Field entries marked in the same record
- Forms set up once, in Opralog
07 / At a glance
Why sites choose Opralog
- Handover templates and forms set up for your site
- Full audit trail and access set by role
- Every logbook and handover searchable in one place
- Less paper and fewer spreadsheets
- Two-way PI interface, plus OPC and a generic API
- Installed on your own servers or private Azure or AWS
Where it runs
Opralog is installed on your own servers or in your own private Azure or AWS environment. Infotechnics does not host it, and it is not supplied as SaaS.
Set-up and training
When we first install Opralog, it’s like a blank sheet of paper. We work with you to set it up around how your site runs, and train your superusers so they can keep shaping it themselves.
Support
You deal directly with the people who build, configure and support it.
08 / Your questions
Questions about Opralog
Straight answers about the product, set-up and getting started.
Discuss your requirements ↗What is an electronic logbook?
An electronic logbook replaces paper logbooks and spreadsheets with one structured record that teams can search. Opralog is an electronic logbook and shift handover system: teams record what happens during the shift, and that record feeds handovers, tasks, registers and reports.
Is Opralog a web application?
Yes. This page describes Opralog Web. If you use an older Windows installation, talk to us about upgrading. Mobilog needs Opralog Web.
Can we start with Opralog and add Mobilog later?
Yes. Opralog works on its own. Mobilog is an optional, separately licensed app you can add when you want to take rounds and inspections into the field.
Can Opralog match our handover forms and registers?
Yes. Logbooks, handovers, forms and registers are all set up around the way your site works, and shifts can be locked and signed off if needed. Bring examples of what you use today and we’ll show you how they could look.
What happens to issues that aren’t finished at the end of a shift?
They can be carried forward to the next shift, keeping the time they were first recorded. Tasks stay with whoever they’re assigned to until they’re done, and Opralog can email them if a task goes overdue.
Can Opralog connect to our other systems?
Yes. Opralog has standard interfaces and APIs, so historians such as PI, maintenance, permit-to-work and other systems can share data with it. What’s connected, and how, is agreed for each project.
Does Opralog include reporting?
Yes. Reports come from the same record your teams use every day, including Mobilog data where you use it. They can be saved, scheduled and emailed automatically.
Where is Opralog installed?
Opralog is installed on your own servers or in your own private Azure or AWS environment. Infotechnics does not host it, and it is not supplied as SaaS.
We’ll agree the set-up, access and security with your IT or OT team early on, and who looks after what.
What should we prepare for a demonstration?
Nothing formal. A current logbook or handover form and an example of an issue that ran across a few shifts is plenty. We’ll use them to show how Opralog could work for you.
09 / See it in context
See Opralog using one of your current records
Follow an entry from the original event through to review, follow-up and the next shift. We can explore the configuration and implementation needed for your operation.
Book a demo