Integrated case: preparing a company to operate coherently

A coherent ERP setup begins with the business model. The organisation needs to know what it sells, how it obtains supply, who makes decisions, how work is measured and which records explain the financial result. Configuring isolated screens without those relationships can produce individually valid settings that do not work together sensibly.

This case concerns the fictional Northstar Services. It sells equipment and installation services, manages projects and sometimes produces an assembled item. The purpose is to connect the Academy's concepts into a controlled operating model, not prescribe a universal configuration.

Responsibility before configuration

Emily owns commercial agreements, Daniel coordinates operations and Oliver reviews finance. Their responsibilities should inform user roles, company access, approval rules and reporting needs. No one needs every permission simply because they participate in the same process.

In DNA, company access, action permissions, report grants and industry-module activation have distinct configuration paths. Manufacturing visibility does not establish that the production masters are ready, and a role name does not prove the exact authority granted.

Connect operational and financial definitions

A product needs a clear identity and unit. A project needs an accountable scope. A financial account needs a defined purpose. A cost centre and its budget explain responsibility and funding, while a task plan explains work and timing.

DNA's task project choices use active project-type cost centres. This provides a shared reference, but task completion is not automatically a financial posting. The team should agree how operational evidence and financial records will be reviewed together.

Verify a representative scenario

Before relying on the setup widely, use a small authorised scenario with known expected relationships. Verify the saved values, relevant permissions and resulting records. Distinguish a setting that saved from a business process whose outcome was checked.

A useful readiness record identifies what was tested, its result and what still needs attention. Check the resulting records to confirm that the process worked as intended.