GenOps Cloud Documentation

What GenOps Cloud does

GenOps Cloud is an operations workspace for generator fleets and other runtime-based equipment. It combines asset records, runtime, fuel, maintenance, incidents, telemetry, reports, and team access in one system.

Every operational record belongs to a workspace. A workspace can contain one or more sites, assets, people, connected GenBox devices, and integrations. Data from one workspace is isolated from every other workspace.

The core data model

• Workspace: the organization and security boundary for your team.
• Site: a physical location, contact, and operational grouping.
• Asset: a generator or other tracked machine with its own meter and service history.
• Runtime entry: a start and stop interval, either timed, entered manually, imported, or received through an integration.
• GenBox: a connected field device that sends telemetry and device health.
• Work order, fuel event, incident, and alert: the operational records linked to an asset and site.

Try the product before signing in

Open Detailed demo from the public site to explore a read-only example workspace. The demo never modifies production records and clearly labels simulated values.

When you are ready to use your own data, select Sign in or Get started and create a workspace.

Create an account

1. 1Open Sign in from the public site.
2. 2Select Register and enter your email address, first name, last name, and a strong unique password.
3. 3Submit the form and open the verification message sent to your email address.
4. 4Follow the link in that message, then return to GenOps Cloud and sign in.

Sign in and stay signed in

Use the email address associated with your account. The Remember me option extends the session on the current trusted device. Do not enable it on shared computers.

After sign-in, users with one workspace go directly to it. Users with several workspaces see the workspace chooser.

Recover a password

1. 1Select Forgot password on the sign-in screen.
2. 2Enter your account email address.
3. 3Open the newest recovery message and follow its link before it expires.
4. 4Set a new password and sign in again.

Sign out

Inside a workspace, open the profile button in the top-right corner and select Sign out. On the workspace chooser, open the email profile control and select Sign out.

Create a workspace

1. 1Open the workspace chooser and select New workspace.
2. 2Enter the organization name and a short URL slug using lowercase letters, numbers, and dashes.
3. 3Choose the use case, time zone, and reporting currency.
4. 4Select Create workspace. The creator becomes the workspace owner.

Complete guided setup

1. 1Confirm the workspace and use-case settings.
2. 2Add the first site with a recognizable name and address.
3. 3Add the first generator or asset and enter the current opening meter.
4. 4Create a starter maintenance interval and checklist.
5. 5Connect a GenBox now or skip the hardware step until the device is available.
6. 6Invite team members and choose notification channels.
7. 7Finish setup and open the Overview.

Return to setup later

The setup flow saves completed steps. Owners and administrators can return to the Onboarding route from the workspace when additional information or hardware becomes available.

Use the application shell

• The left navigation groups operations, connections, analytics, and administration.
• On small screens, the bottom bar keeps the five most frequently used operational destinations within reach.
• The workspace name at the top of the navigation opens the workspace chooser.
• Navigation items are permission-aware. A missing section usually means the current role does not grant access.

Search the workspace

Select the search bar or press Command/Control + K. Search can find assets, sites, devices, incidents, work orders, and members that your role is allowed to read.

Choose a result to open its relevant workspace section. Search results never bypass role permissions.

Personal controls

• Language changes the product interface. This documentation remains English-only.
• Theme supports light, dark, and system appearance.
• Notifications opens the latest operational and maintenance events.
• Help opens product documentation, legal documents, and API documentation when API docs are enabled.
• Profile provides workspace settings, all workspaces, and Sign out.

Read the overview

• Fleet metrics summarize equipment, runtime, fuel, open incidents, maintenance exposure, and device connectivity.
• Attention panels prioritize disconnected or degraded devices, overdue maintenance, and open incidents.
• Recent activity provides a chronological view of operational changes.
• Cards and table rows link to the underlying asset, site, incident, or work order.

Check data freshness

A metric is only as current as its latest source record. For connected equipment, confirm the last telemetry time and device status. For manually managed equipment, confirm the most recent runtime and fuel entries.

Create a site

1. 1Open Sites and select Add site.
2. 2Enter a clear name and address.
3. 3Add the responsible contact, phone number, and operational notes when available.
4. 4Save the site, then assign equipment to it from Fleet.

Use site views

• Switch between cards and list view based on the number of locations.
• Use site-level counts to compare connected equipment, open incidents, and overdue maintenance.
• Select a site to focus the operational summary on that location.
• The location scheme is derived from addresses; it is not a precision GIS map unless exact coordinates are configured.

Archive a site

Archive a site only after moving or retiring its active equipment. Archived records remain part of historical reporting and audit history.

Add equipment

1. 1Open Fleet and select Add asset.
2. 2Enter the equipment name and optional manufacturer, model, and serial number.
3. 3Choose its site and enter the current opening runtime meter.
4. 4Add fuel or power specifications when they are known.
5. 5Save and open the asset detail page.

Find and filter equipment

• Search by equipment name, model, serial number, or site.
• Filter by operational state, maintenance exposure, or device connectivity.
• Use the attention state to find records with overdue work, incidents, or degraded telemetry.

Use an asset detail page

The asset page consolidates identity, site, runtime, fuel, maintenance, incidents, and connected device information. Use its telemetry link for historical measurements and its action controls to edit or archive the record when your role permits.

Start and stop a timer

1. 1Open Runtime and select the target equipment.
2. 2Select Start when the generator begins operating.
3. 3Leave the timer active while the run is in progress.
4. 4Select Stop when operation ends and confirm the final record.

Add or correct a record

Use Add entry manually for historical runs or when a timer was not started. Enter the actual start, stop, equipment, and optional fuel usage. Use the row action menu to edit or archive a record if your role allows it.

Work without connectivity

Supported timer actions are stored in the browser when the network is unavailable and are sent after connectivity returns. Keep the same browser profile open until synchronization completes.

Prepare the source file

• Keep an untouched backup of the original export.
• Confirm that dates, durations, equipment identity, meter readings, and fuel units are consistent.
• Use the supported JSON structure and keep the file within the upload limits shown in the interface.
• Do not hand-edit identifiers unless you understand how the source links entries to equipment.

Validate before committing

1. 1Open Data import and select the file.
2. 2Review the validation summary, rejected records, warnings, and proposed equipment mapping.
3. 3Correct blocking errors in a copy of the source file.
4. 4Run validation again, then commit the import only when the preview matches the source.
5. 5Open Fleet and Runtime to reconcile record counts and totals.

Choose the correct event type

• Purchase adds fuel acquired from a supplier and can include price and receipt details.
• Refueling moves fuel into a specific asset and links the event to its operational history.
• Consumption records measured or reconciled usage.
• Adjustment corrects a verified inventory difference and should include a reason.

Record a fuel event

1. 1Open Fuel and choose the event type.
2. 2Select the date, equipment or stock location, and volume.
3. 3Enter price, supplier, odometer or runtime context, and notes when available.
4. 4Save, then confirm the balance and event row.

Reconcile balances

Compare GenOps balances with physical measurements on a regular schedule. Investigate unexplained negative balances, duplicate events, missing refueling records, and unit mismatches before using the data for financial reporting.

Understand the maintenance workspace

• Rules define the service interval and target equipment.
• Work orders turn planned or unplanned work into an assignable record.
• Calendar places upcoming and overdue work on a time line.
• Templates provide reusable checklists and service definitions.
• History preserves completed and archived maintenance activity.

Create a runtime-based rule

1. 1Open Maintenance and select Rules.
2. 2Create a rule, choose the equipment, and define the interval in runtime hours.
3. 3Set the starting meter or next due threshold.
4. 4Attach a checklist template and save.
5. 5Confirm that the due status appears against the correct asset.

Execute a work order

1. 1Open or create the work order.
2. 2Assign an owner, priority, due date, and the correct equipment.
3. 3Complete each checklist item and record parts, notes, and meter values.
4. 4Attach supporting files when required.
5. 5Mark the order complete only after verifying the result.

Complete supported work offline

Supported checklist and status changes are queued in the browser when offline. After reconnecting, wait for synchronization and verify the final work-order state before leaving the record.

Alert versus incident

An alert is generated from telemetry or a configured condition and represents a signal that needs review. An incident is the operational record used to track impact, ownership, investigation, and resolution.

A confirmed alert can be acknowledged, assigned, snoozed, resolved, or converted into a work order. Create an incident when the event has operational impact that needs a durable record.

Handle an alert

1. 1Open Alert center and review severity, equipment, site, metric, and last update.
2. 2Acknowledge the alert so other responders know it is being handled.
3. 3Assign an owner or snooze only when there is a documented reason.
4. 4Create a work order when physical inspection or repair is required.
5. 5Resolve the alert after confirming that the underlying condition is normal.

Manage an incident

1. 1Create the incident with a precise title, severity, site, equipment, and start time.
2. 2Describe the observed impact and add response notes as facts become available.
3. 3Track the owner and status until service is restored.
4. 4Resolve the incident with an end time and resolution summary.

Configure escalation policies

Alert center can store escalation policies and notification targets. Test the chosen channel before relying on it for urgent response, and keep at least one in-app path available if external delivery fails.

Choose and review a reporting period

1. 1Open Reports.
2. 2Set From and To dates using the workspace time zone.
3. 3Apply the range and review runtime, fuel, cost, maintenance, and incident totals.
4. 4Compare the daily trend and equipment table with source records before sharing.

Export data

• CSV is best for simple tabular review and downstream imports.
• XLSX is best for spreadsheet analysis with structured columns.
• PDF is best for a fixed presentation snapshot.
• Full data export produces a broader workspace dataset for portability and backup workflows.

Before pairing

• Create the target asset first if the device should be bound immediately.
• Confirm that the GenBox hardware and measurement module are wired according to the approved hardware guide.
• Prepare a 2.4 GHz Wi-Fi network with internet access and the correct credentials.
• Keep the GenOps pairing page open until you have copied the one-time code.

Create the pairing code

1. 1Open Devices and select Connect GenBox.
2. 2Enter a recognizable device name and optionally choose an asset.
3. 3Choose an expiry window that is long enough for the field procedure.
4. 4Select Create code and copy the one-time code immediately.

Provision and verify the device

1. 1Power the GenBox and open its local Wi-Fi provisioning portal.
2. 2Enter the site Wi-Fi credentials and the GenOps pairing code.
3. 3Wait for the device to verify its identity and establish a secure connection.
4. 4Return to Devices. The new device should appear automatically.
5. 5Open the device and confirm status, firmware version, measurement module health, and first sample time.

Use the live view

• Filter devices by search text and connection status.
• Read voltage, active power, frequency, power factor, generator state, and data quality.
• Pause automatic screen updates when you need to compare a stable set of values.
• Open the device record for measurement history and technical health.

Interpret device health

• Online means recent data and a working real-time connection.
• Degraded means data is arriving but quality or health checks need attention.
• Offline means the server has not received a recent device signal.
• Buffered telemetry is the number of samples waiting on the device for later upload.
• PZEM availability, free memory, restart reason, configuration revision, and credential revision help isolate failures.

Run diagnostics safely

1. 1Open Devices, select the device, and review its last sample and health values.
2. 2Use Check connectivity for a low-impact reachability test.
3. 3Use Collect diagnostics when support needs a current device snapshot.
4. 4Rotate the device key if credentials may be exposed.
5. 5Revoke the device only when it must permanently lose access.

Use the safe OTA pipeline

• Artifact upload validates file type and size, calculates SHA-256, and signs the binary with Ed25519.
• A release links a verified artifact to a channel, hardware revision, initial cohort, and failure threshold.
• Canary and beta cohorts should be used before broad stable deployment.
• Release monitoring shows per-device deployment outcomes.

Upload and verify an artifact

1. 1Open Firmware and select a .bin file produced by the approved build pipeline.
2. 2Enter the immutable firmware version, channel, compatible hardware revision, and release notes.
3. 3Upload the file and wait for server validation and signing.
4. 4Confirm the SHA-256 value, signature state, size, and hardware compatibility.

Create and monitor a release

1. 1Choose a verified artifact.
2. 2Set a small initial cohort and a conservative failure threshold.
3. 3Create the release, review its scope, then activate it.
4. 4Monitor success, failure, pending, and device health values.
5. 5Pause immediately if failures or post-update health checks exceed the accepted risk.

Prepare a rollback

Keep the last known-good signed artifact available. Create a rollback release for the same hardware revision, start with a small cohort, and confirm device recovery before widening the rollout.

There are two offline layers

• The web application queues supported runtime and maintenance actions in the current browser.
• GenBox stores telemetry locally when network delivery is unavailable and sends buffered samples after reconnecting.
• The two queues are independent. Browser synchronization does not prove that device telemetry has uploaded, and device upload does not prove that browser actions have synchronized.

Verify recovery after connectivity returns

1. 1Wait for the application reconnected message.
2. 2Refresh Runtime and Maintenance and confirm each queued action appears exactly once.
3. 3Open the GenBox device and confirm the last sample time advances.
4. 4Watch Buffered telemetry fall toward zero.
5. 5Compare the recovered telemetry interval with the asset runtime record.

Battery and idle operation

When the generator is stopped, the device should use the configured idle power profile while preserving wake-up, measurement, local buffering, and secure reconnect behavior. Actual runtime depends on the board revision, sensors, radio signal, sampling policy, and battery capacity.

Choose a built-in role

• Administrator manages most workspace configuration and operations.
• Operations manager runs day-to-day fleet workflows.
• Technician works with maintenance and equipment records.
• Operator records routine operational activity.
• Viewer has read-oriented access.
• Billing manager handles subscription information without broad operational control.

Invite a member

1. 1Open Team and enter the person’s email address.
2. 2Open the Role dropdown and choose a built-in or custom role.
3. 3Select Create invitation.
4. 4Check the delivery state. If email delivery fails, copy the backup invitation link and send it through a trusted channel.
5. 5Revoke unused or exposed invitations.

Create a custom role

1. 1Open Custom roles and select the add action.
2. 2Enter a clear job-based role name.
3. 3Select only the required read, create, update, manage, and export permissions.
4. 4Save and test the role with a non-owner account before assigning it broadly.

Manage member access

Suspend a member to block workspace use without deleting the historical identity. Reactivate access after review. The workspace owner is protected from routine removal so the organization cannot be left without an owner.

Create an API key

1. 1Open API & webhooks and select Create API key.
2. 2Give the key a name that identifies its system and environment.
3. 3Select only the permissions required by that integration.
4. 4Create the key and copy the secret immediately.
5. 5Store it in a secrets manager and test the narrowest required endpoint.

Create a webhook

1. 1Choose a stable HTTPS endpoint controlled by your organization.
2. 2Select the event types the receiver actually processes.
3. 3Create the webhook and store its signing secret securely.
4. 4Verify the HMAC signature before parsing or acting on a payload.
5. 5Return a successful response quickly and process heavier work asynchronously.

Use the delivery log

Review status, attempts, response code, and the most recent delivery time. Make receivers idempotent because retries can deliver the same event more than once.

Open technical API documentation

When the deployment enables API documentation, open Help and select API documentation. The interactive schema is separate from this operator guide and should be treated as environment-specific.

Workspace settings

• Keep the organization name and operational profile current.
• Set the time zone used to interpret and display operational dates.
• Set the reporting currency before creating financial records.
• Review organization identifiers before connecting external integrations.

Notification preferences

Choose in-app, email, and webhook channels, then select which operational event groups should notify the workspace. Save changes and test external channels before depending on them.

Plan and billing

Open Plan to review the current subscription, usage limits, and available tiers. A plan-change button redirects to the configured billing provider only when payments are enabled for the deployment.

Review connection security

• Production device connections use MQTT over TLS.
• Every device receives a separate identity and credentials.
• Replay protection rejects reused telemetry packets.
• Credential and configuration revisions are visible in device diagnostics.

Create a telemetry alert rule

1. 1Open Settings, then IoT and telemetry.
2. 2Select New rule and give it an operationally specific name.
3. 3Apply it to one device or all devices.
4. 4Choose the metric, comparison operator, threshold, duration, cooldown, and severity.
5. 5Save, then test the rule with controlled input before enabling urgent escalation.

Use the simulator

The local simulator creates temporary demonstration telemetry for validating the UI and alert pipeline. Keep simulated data separate from production evidence and do not use it to certify physical hardware.

Security model

• Authentication is handled by the configured identity service and protected browser sessions.
• Workspace membership and permissions restrict every application route and API action.
• Database tenant policies provide an additional organization isolation boundary.
• Sensitive application secrets are encrypted or stored as hashes where recovery is not required.
• Security-relevant administrative changes are recorded for audit.

Required operator practices

• Use a unique password and enable MFA when the identity provider offers it.
• Do not share accounts, API keys, webhook secrets, pairing codes, or device credentials.
• Revoke exposed credentials immediately and review recent activity.
• Review workspace members, custom roles, and active invitations regularly.
• Keep server, database, identity, and device-signing backups under tested restore procedures.

Data handling

Exports and downloaded attachments can contain operationally sensitive information. Apply access controls and retention rules outside GenOps after a file leaves the platform.

Access the console

The Platform console is available only to accounts explicitly marked as platform administrators. Workspace Owner or Administrator roles do not grant platform access.

Monitor platform health

• Overview metrics summarize organizations, assets, users, subscriptions, failed jobs, and failed webhooks.
• Organization health shows tenant status, owner, plan, and asset count.
• Failed job and webhook panels identify background work that needs investigation.
• Security events show high-risk activity that should be reviewed promptly.
• Announcements publish controlled platform messages to users.

Suspend an organization

Suspension is a high-impact administrative action. Confirm the tenant, document the reason, communicate with the owner, and preserve audit evidence. Reactivate only after the reason has been resolved.

Sign-in or email link does not work

• Use the newest verification, recovery, or invitation email; older links may be invalidated.
• Check spam and confirm that the email address was entered correctly.
• Request a fresh link if the message or OAuth state expired.
• If email delivery is marked failed, ask a workspace administrator for the backup invitation link.

A section or action is missing

• Confirm that you opened the correct workspace.
• Ask an owner or administrator to check your assigned role and custom-role permissions.
• Some functions also require server-side configuration, such as payments or interactive API documentation.
• Sign out and back in after a role change if the session still shows the old access.

Offline actions did not synchronize

1. 1Keep the original browser profile open and restore connectivity.
2. 2Wait for the reconnected message and refresh the affected section.
3. 3Check whether the action appears exactly once.
4. 4Do not repeatedly recreate a missing action until you have confirmed the queue did not deliver it.
5. 5Record the time, workspace, equipment, action, and browser details before contacting support.

A GenBox is offline or degraded

1. 1Check power, battery voltage, wiring, and measurement-module health.
2. 2Confirm local Wi-Fi signal and internet access.
3. 3Open device diagnostics and note the last signal, restart reason, free memory, and buffered telemetry.
4. 4Run Check connectivity, then Collect diagnostics.
5. 5Rotate credentials only if authentication is suspected; revoke only with a re-pairing plan.

A report or export fails

• Use a smaller date range and confirm your role includes report access.
• Allow browser downloads for the site.
• Retry only after the first request has completed or failed.
• For a full data export, verify there is enough local storage for the download.

Before requesting support

• State the workspace slug and affected section, but never send passwords or secret keys.
• Provide the affected asset or device ID and the approximate time with time zone.
• Describe the expected result, actual result, and exact sequence that produced it.
• Include the visible error message and a screenshot with secrets and personal data removed.
• For device issues, include firmware version, hardware revision, connection state, and diagnostics.

Glossary

• Runtime meter: accumulated operating time for an asset.
• Telemetry: time-stamped measurements and device-health data.
• Buffered telemetry: samples stored by a device while delivery is unavailable.
• Pairing code: a single-use credential that authorizes the first device connection.
• Artifact: a verified and signed firmware binary.
• Release: a controlled plan for delivering one firmware artifact to a device cohort.
• Idempotency: protection that allows a request to be retried without creating a duplicate result.
• Webhook: an outbound signed event delivered to an external HTTPS endpoint.
• Workspace slug: the stable URL-safe identifier for an organization.