# Overview

Process Logbook™ is a modern electronic operator notebook, integrated with Wonderware/AVEVA Application Server (or System Platform).

Process Logbook captures and preserves the operational knowledge that lives in your team's heads—tied directly to your equipment, accessible from anywhere.

# The Problem

# Knowledge Walks Out the Door

Every shift change, every retirement, every resignation takes irreplaceable knowledge with it.

  • That pump that needs a special startup sequence
  • The valve that sticks when temperatures drop below 40°F
  • The workaround discovered at 2 AM that nobody documented

Your SCADA system tracks data. But who tracks the wisdom?


# The Solution

# Institutional Memory for Industrial Operations

Process Logbook is a knowledge continuity system purpose-built for AVEVA System Platform SCADA environments. It connects operational notes, observations, and lessons learned directly to your equipment—and keeps them synchronized across your entire operation.

Three environments. One source of truth.

graph TB
    SCADA(SCADA<br/>AVEVA System Platform) -->|One way connection<br/>Bidirectional data exchange| OnPrem(On-Premise Web GUI)
    OnPrem -->|One way connection<br/>Bidirectional data exchange| Cloud(Cloud/Mobile Access)
    

# Key Features

# Equipment-Centric Organization

Notes aren't buried in folders or lost in email chains. Every observation, every tip, every lesson learned is attached to the equipment it relates to. Equipment model is directly imported from Application Server's object model.

"Show me everything we know about Pump 4A" — answered in seconds.


# Notes & Observations

Capture what matters when it matters:

  • Regular Notes — Routine observations, maintenance tips, operational guidance
  • Abnormal Condition Notes — Flag issues that need attention, visible across the organization
  • Comments — Collaborative discussions on any note
  • Attachments — Photos, documents, wiring diagrams, P&IDs—anything that helps

# Activities & Reminders

Not everything is urgent, but nothing should be forgotten:

  • Schedule follow-up tasks tied to equipment
  • Set reminders for periodic checks
  • Track completion across shifts

# Seamless Synchronization

Create a note in the control room. Read it on your phone. Update it from the office.

Process Logbook keeps everything in sync:

  • SCADA Zone → Control room operators review and enter notes in SCADA environment
  • On-Premise Web GUI → Central repository on your corporate network
  • Cloud → Mobile access from anywhere, anytime

No manual exports. No version conflicts. Just one truth.


# Mobile Access

Your team isn't always at a desk. Process Logbook Cloud puts operational knowledge in their pocket:

  • Review equipment history before walking into the field
  • Add photos and notes on the spot
  • Get notified about abnormal conditions in real-time

# Use Cases

# Shift Handover

"The night shift figured out why the boiler trips on cold mornings. Instead of a sticky note that disappears, they documented it in Process Logbook. Now every operator knows—forever."


# Troubleshooting

"We've seen this alarm before. Process Logbook shows us exactly what the team did last time—and what NOT to do."


# Knowledge Preservation

"Our best operator retired last year. Thanks to Process Logbook, his 30 years of experience didn't walk out with him."


# Compliance & Audits

"Auditors asked about our abnormal condition tracking. We pulled up 18 months of equipment-specific logs in minutes."


# How It Works

# 1. Operators Create Notes

From the control room interface or mobile app, operators document observations, attach photos, and flag abnormal conditions.

# 2. Notes Sync Automatically

Whether created in the SCADA zone, corporate network, or mobile device—everything synchronizes bidirectionally.

# 3. Knowledge Accumulates

Over time, each piece of equipment builds a living history of operational wisdom that serves current and future teams.

# 4. Anyone Can Access

Control room operators, maintenance technicians, engineers, and management all see the same information—appropriate to their role and location.


# Architecture

# Built for Industrial Reality

Process Logbook understands that SCADA networks are different:

  • Air-Gap Friendly — Works in isolated control system environments
  • One-Way Security — Data flows outbound; no inbound connections to SCADA
  • Offline Capable — Environments (SCADA, On-Premise, Cloud) continue working when networks are down
  • Cloud Optional — Full functionality on-premise; cloud enhances but isn't required

# Integration with ProcessAlert

Process Logbook is designed to work seamlessly with ProcessAlert alarm notification:

  • Same equipment hierarchy
  • Same user accounts
  • Shared infrastructure
  • Single pane of glass for alarms AND knowledge

Already using ProcessAlert? Adding Process Logbook is seamless.


# Pricing

# On-Premise

One-time license fee + annual maintenance. Full functionality within your network.

# Cloud Add-On

Annual subscription based on user count. Mobile access and cloud synchronization.


# FAQ

# Is Process Logbook a CMMS?

No. CMMS systems track work orders and maintenance schedules. Process Logbook captures operational knowledge—the tips, observations, and lessons learned that make your team effective. They complement each other.

# Do we need Process Alert to use Process Logbook?

Process Logbook is designed as an add-on to Process Alert (our alarm notifications product integrated with Application Server) and shares its infrastructure. Contact us about standalone options.

# Can we use it without the cloud?

Absolutely. Process Logbook On-Premise provides full functionality within your network. Cloud is an optional enhancement for mobile access.

# How is data secured?

  • On-premise data stays on-premise
  • Cloud data encrypted in transit and at rest
  • No inbound connections to SCADA networks
  • Role-based access controls

# What about existing documentation?

Process Logbook doesn't replace your document management system. It captures the living knowledge that doesn't fit in formal documents—and links to your existing docs when needed.