Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt

Use this file to discover all available pages before exploring further.

Manual observation creation interface overview

​
What is Manual Observation Creation?

The Manual Observation Creation feature allows you to supplement existing, system-detected emission events with operational observations that include specific timing, emission rates, and supporting documentation. This creates a complete, auditable story by combining automated sensor data with your on-ground operational knowledge.

50% More Accurate

Volume calculations using operational data

Complete Audit Trail

Defensible documentation for compliance

5-Minute Setup

Quick addition of operational context

​
Why Use Manual Observation Creation?

The Problem

Without manual observations:
  • Automated detections miss operational context
  • Volume calculations based on incomplete data
  • Difficult to justify reported volumes during audits
  • No way to document known operational events

The Solution

With Manual Observation Creation:
  • Combine sensor data with operational knowledge
  • Accurate volume calculations using ground-truth data
  • Complete audit trail with supporting documentation
  • Streamlined process for operational event documentation

​
Getting Started

Ready to add operational context to your emission events? Follow these quick steps to create your first manual observation and see immediate improvements in data accuracy.
1

Access an Emission Event

Navigate to any existing emission event in your dashboard. Look for events that could benefit from additional operational context, such as those detected during known maintenance activities.
2

Open the Manual Observation Form

Click the “Add Observation” button or navigate to the “CreateNew” tab within the event details panel to access the manual observation creation interface.
3

Complete Your First Observation

Fill in the observation details including start/end times, emission rate, description, and upload any supporting files like maintenance logs or operational reports. The system will validate your inputs and create a comprehensive record.

​
Common Use Cases

​
Operational Event Documentation

When you have a known operational event (like a compressor blowdown or planned venting) that coincides with an automated detection, you can document the specific operational details to provide complete context and more accurate emissions calculations.

​
Improving Volume Accuracy

Supplement sensor-based detections with precise operational data including exact timing and emission rates from your equipment specifications, leading to more accurate volume calculations for regulatory reporting.

​
Creating Audit Defense

Build a robust audit trail by combining automated detections with operational documentation, maintenance logs, and descriptive context that demonstrates due diligence and accurate reporting practices.

​
Key Features

​
Comprehensive Data Entry

  • Timing Details: Specify precise start and end times with timezone support
  • Emission Rates: Enter accurate emission rates with configurable units (kg/hr, lb/hr)
  • Descriptions: Add detailed operational context and explanations
  • File Uploads: Attach supporting documentation like maintenance logs and reports

​
Data Validation & Quality

  • Smart Validation: Automatic checks ensure data integrity and logical consistency
  • Unit Conversion: Seamless conversion between different measurement units
  • Timezone Handling: Proper timezone management for accurate temporal data
  • File Management: Support for various document types with size and format validation

​
Integration & Workflow

  • Event Association: Automatic linking to existing emission events
  • Volume Calculations: Integration with time and rate engines for accurate quantification
  • Audit Trail: Complete tracking of all additions and modifications
  • Permission Controls: Role-based access to ensure data security

​
Managing Observations

​
Correcting Errors

If you need to correct a manual observation that was added in error:
  1. Remove from Event: Use the ellipse menu to disassociate the observation from its parent event
  2. Mark as False Alarm: Navigate to the removed observation and mark it as a false alarm
  3. Maintain History: The system retains complete audit history for transparency
Important: Marking an observation as a false alarm will exclude it from all future volume calculations and reporting, but the audit trail is preserved for compliance purposes.

​
FAQ / Troubleshooting

You can upload image files (JPEG, PNG) up to 10MB per file, with a maximum of 5 files per observation. These typically include maintenance logs, operational reports, or photos documenting the emission event.
When you add a manual observation with specific timing and emission rate data, the system’s time and rate engine will use this more precise operational data for volume calculations, typically resulting in more accurate emissions quantification than sensor-only estimates.
Manual observations maintain data integrity for audit purposes. If you need to make corrections, you should remove the observation from the event and mark it as a false alarm, then create a new observation with the correct information.
You need the “create EmissionObservation” permission in your user role. Contact your system administrator if you don’t see the option to add manual observations to events.
Manual observations are integrated into the complete emission event record and their data (timing, rates, volumes) is included in regulatory reporting calculations. The operational context and supporting documentation provide audit defense for the reported values.

​
Best Practices

Do This

Document Known Events: Always add manual observations for planned operational events like blowdowns or venting Upload Support Files: Include maintenance logs, work orders, or photos as evidence Be Specific: Provide detailed descriptions with equipment IDs and operational context Review Timing: Ensure start/end times accurately reflect the operational event duration

Avoid This

Guessing Rates: Don’t estimate emission rates without operational data or specifications Incomplete Context: Don’t leave descriptions vague or without specific operational details Wrong Event Association: Don’t associate manual observations with unrelated automated detections Missing Documentation: Don’t skip uploading supporting files when they’re available

​
Feedback & Support

Found an issue or have suggestions? Contact your system administrator or submit feedback through your organization’s support channels for assistance with manual observation creation.
For additional help with emission event management and observation workflows, refer to your organization’s EmissionOps documentation or contact your technical support team.