Work: field to office
Work across operations, data, software and service design, with evidence and limits for each example.
All work
Filter by kind, problem or state
2 entries: field to office.
No entries match this filter yet.
Back to the complete collection| Entry | Kind / state | Where / years | Evidence | Problem families |
|---|---|---|---|---|
| A bilingual pump form and the fleet workflow behind itCase study | build running | Purchasing and operations 2026 | reported | Reporting and visibility, Field to office, Custom applications, Data management, Configuration and integration |
| A marine service business designed around a permanent per-hull recordLibrary entry | design design | independent 2026 | none | Field to office |
How this list is kept honest
Every entry carries a dated source review. A running system, evidence of use and a measured outcome are separate things. The entry states which ones the record supports.
Related and superseded repositories are grouped into the work they support. Adopting or configuring an existing tool is described as that contribution; a fork is not evidence of original authorship.
Career statements are my own account, checked against my records. Engineering checks and synthetic demonstrations establish only the behavior they actually exercise.