Data flow diagrams and system-of-record mapping for manufacturing data
Key Takeaway
Decide the system of record for each kind of data before you design any flow. The system of record table lists each data type's location, system of record and change frequency, and it is the artifact you use for maintenance planning. Where orders are created decides the sales agreement "Actuals Calculation Mode".
A system of record is the system that holds the official version of a type of data. A data flow diagram shows how that data moves between applications and transfer points. In an Agentforce Manufacturing design, these two artifacts show which data lives in Salesforce, which data comes from outside systems such as an ERP or an external inventory system, and how often it moves.
Why data flow design matters
Data architecture is the design of how data flows across systems so the data stays accessible, consistent and secure. Inconsistent data across systems costs time, because analysts may spend days reconciling it. Inconsistent data also erodes user trust, which can lead to adoption issues.