Journal6 articles3 topicsUpdated
How operational software is designed, connected and replaced: which system owns which record, how a process becomes dependable automation, and what to decide before anything is built. Written for operations leaders and the people who answer for their systems.
§ 01Front page
ERP stands for enterprise resource planning, but the useful definition is narrower: one shared set of business records that sales, purchasing, inventory and finance all read and write. Everything else follows from that.
§ 02Subjects
Three subjects, chosen from the questions buyers and operators actually search for. Each one answers a different kind of question.
§ T1
What an ERP is, what it owns, and where specialist systems take over
02 articles
§ T2
Mapping, automating and governing the work that moves between people
02 articles
§ T3
Integration patterns, data ownership and replacing systems without stopping work
02 articles
§ 03Systems architecture & integration
Integration patterns, data ownership and modernization, written for the people who answer for the whole landscape rather than one application.
All articles on systems architectureHow to design ERP integrations that hold up: system-of-record decisions, integration patterns, sync versus async, idempotent messages, retries, reconciliation.
A decision framework for legacy system modernization: assess each capability, choose keep, wrap, replace or rebuild, then migrate data and cut over in phases.
§ 04Process automation guides
Practical material for operations leads: how to describe the work precisely, then decide which parts a system should run.
Step 01 · Explainer
Business process automation explained: its building blocks, examples by department, how it differs from RPA and workflow tools, and what it cannot fix.
7 min read
Step 02 · Implementation guide
A swimlane map, a state list, an exception register and a rules table that a developer or automation tool can build from.
7 min read
§ 05Decisions
For the choices that are expensive to reverse: which system should own a job, and whether an old system should be rebuilt, replaced or kept.
ERP, MRP and MES compared: the question each system answers, its time horizon, the records it owns, and how to decide which ones a manufacturer actually needs.
A per-capability decision (keep, wrap, replace or rebuild), a migration sequence and cutover criteria you can defend to a board.
§ 06Learning paths
Short sequences that build on each other. Each path is complete: every article in it is published.
Understand what the core system owns, connect the systems around it deliberately, then replace what no longer fits without stopping operations.
3 articles · 24 min in total
Learn what automation can and cannot do, describe the work precisely enough to automate it, then connect the systems the process runs through.
3 articles · 22 min in total
§ 07Index
| Published | Format | Article | Topic | Reading |
|---|---|---|---|---|
| ARC Architecture deep dive | ERP integration architecture: patterns, data ownership and failure handling | Systems architecture & integration | 8 min | |
| CMP Comparison | ERP vs MRP vs MES: which system runs which part of manufacturing | ERP & core systems | 7 min | |
| GDE Implementation guide | How to map a business process before you automate it | Process automation & workflow | 7 min | |
| DEC Decision framework | How to modernize a legacy business system without stopping operations | Systems architecture & integration | 7 min | |
| EXP Explainer | What is an ERP system? Meaning, modules and how it works | ERP & core systems | 9 min | |
| EXP Explainer | What is business process automation? Definition, examples and limits | Process automation & workflow | 7 min |
§ 08Topic directory
§ 09Services
The journal explains; these pages describe what Comtau builds and how a project is scoped.
