Work: configuration and integration
Work across operations, data, software and service design, with evidence and limits for each example.
All work
Filter by kind, problem or state
4 entries: configuration and integration.
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 personal workspace that answers from my own records and links to the sourceCase study | build running | independent April 2026 to present | measured | Business knowledge, Custom applications, Data management, Configuration and integration |
| Order logistics and AP/AR across a distribution order bookLibrary entry | career career | Distribution logistics January 2024 to December 2025 | reported | Purchasing, Reporting and visibility, Operations and audits, Data management, Configuration and integration |
| Operations, billing and staffing for a service business with 500 active membersLibrary entry | career career | Service operations January 2022 to January 2024 | reported | Purchasing, Reporting and visibility, Operations and audits, Configuration and integration, Ongoing improvement |
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.