Operational Process
A document describing how to operate a gateway in the field. It covers roles and sequence, not how to use the screen.
While the tutorial covers "connecting a PLC for the first time," this document covers "running multiple gateways continuously."
Roles — There is only one account
Edge has only admin one account. It's not a structure where accounts are assigned to each person.
⇒ Whoever knows the password can access the gateway. Role separation should be established through operational rules and network access control, not through product features.
| Actual roles that are separated | What they do |
|---|---|
| Installer | Sets up the gateway, creates connections and tags |
| Field Operator | Checks that values are coming in, raises alarms if they are lost |
| System Administrator | Manages upgrades, backups, and passwords |
With only one account, sharing is easy. However, once shared, it becomes impossible to know who changed the settings. Only those who need to make configuration changes should know the password.
Overall Flow
The point where the arrow crosses lanes is the handoff point.
1. Commissioning — Up to establishing a single gateway
| Order | What to do | Documentation |
|---|---|---|
| 1 | Determine deployment location and network configuration | Network Configuration |
| 2 | Finalize EDGE_ID naming convention | Install (install.sh) |
| 3 | Install | Installation Overview |
| 4 | Replace password and API key | Change Initial Password |
| 5 | Register connections + Test connection | Add New PLC Connection |
| 6 | Register tags | Register Tags |
| 7 | Verify values | View Real-time Values |
| 8 | Acceptance inspection | Production Readiness Criteria |
EDGE_ID is difficult to change laterIt will conflict with information registered on the upper platform. Establish the naming convention before deploying multiple gateways — it should match the name used on site to refer to the equipment, such as building/line/sequence number.
2. Normal Operation — Recurring Tasks
| Frequency | What to do | Owner |
|---|---|---|
| Daily | Check that values are coming in and there are no disconnected connections | Field |
| Weekly | Check disk free space | System Administrator |
| Monthly | Backup settings → Backup and Recovery | System Administrator |
| Per release | Review upgrade → Upgrade | System Administrator |
Field walk-throughs can be done on a mobile phone → Mobile Inspection.
Capacity is determined by number of tags × collection interval × retention days. If you've added tags, check the disk trend again at that point → Database Model.
3. Changes — When Adding or Replacing Equipment
| What to do | Sequence |
|---|---|
| Add PLC | connection → Test connection → tag → verify value |
| Bulk add tags | Use CSV Upload |
| Change collection interval | Calculate disk impact first |
| Replace gateway | Take a configuration backup first — after recovery, connections and tags are restored intact |
Time series data can be collected again, but connection and tag definitions are made by humans. Take a configuration backup before touching the equipment.
Common Points of Confusion
| Symptom | Likely Cause |
|---|---|
| "No data since some time" | Not doing daily inspections. Disconnections begin silently |
| "Disk is full" | Only adding tags while leaving retention days unchanged |
| "Don't know who changed the settings" | Many people using a single account — reduce access |
| "No data after the upgrade" | Upgraded without a backup. Backup before upgrade is the rule |
| "Don't know the EDGE_ID scheme after taking over" | No naming convention documentation |