FieldengPlace, thing, record
Location is where. Asset is what. Record is what you measured or observed.
Fieldeng files work on a project. Under that project, three optional objects give context:
- Location — where something physically is
- Asset — a physical thing you work on
- Record — something observed, measured, or calculated
A location is a place. An asset is a thing. A record is an observation about a thing, a place, or both.
Why not Site
A CP test point felt like a site: a place, an object, and a folder for readings. That mix does not hold for Fieldeng as a general field toolbox.
Site can still be a word on a CP job. The stored object is a location. A test point is usually an asset at that location.
Flat, not a tree
Locations and assets sit next to each other on the project. Assets are not children of locations.
Equipment moves. You change location on the asset. You do not recreate the asset.
Do not add a deep hierarchy (site → facility → area → equipment → component). Fieldeng is a field toolbox, not an asset-management system.
GPS
Put coordinates on the location when the place has a point.
Put coordinates on the record when the observation happened at a GPS position.
Do not require GPS on every asset. The router in the house can inherit the house location. A warehouse survey can stamp a different GPS on each RSSI reading.
Optional context
A record does not require a location or an asset.
| Job | Project | Location | Asset | Record GPS |
|---|---|---|---|---|
| Ohm's law at a desk | optional | none | none | none |
| Soil resistivity in a yard | My House | Yard | none | optional |
| Wi-Fi at the router | My House | House | Wi-Fi Router | optional |
| Walking warehouse survey | Wi-Fi Survey | Warehouse | Access Point #1 | each reading |
| Rectifier check | Pipeline Survey | Station 14 | Rectifier 7 | optional |
Same measurement engine. Same calculators. Richer context when you have it.