Before reviewing Foundry ERP, choose a representative order and follow how your team handles it today. The aim is to identify the records, responsibilities and reports that matter to your operation. This makes it easier to assess an agreed software scope.
Use anonymized examples when sharing material for an initial discussion. The checklist below helps organize the review. It does not imply that every workflow or connection is included in a standard configuration.
Start with one production order
Record the order reference, casting or product information, quantities, dates and customer requirements your team uses. Identify the stages through which the work passes and the people responsible for each handover. Include one common exception, such as a schedule change or a record correction.
An alloy foundry and a cast iron foundry may need different records and review points. Describe the process used in your operation rather than relying on a generic ERP module list.
Map materials and inventory records
Bring examples of material references, receipts, stock movements and the units used for each record. Identify which team owns the reference data and how changes are approved. Note where duplicate names, inconsistent units or incomplete records need attention before data preparation.
For each stock or material report, explain the decision it supports. A report used to plan purchases may need a different view from a report used to review production availability.
Describe production planning and progress
List the planning periods, production stages and progress records your team currently reviews. Show how an order is scheduled and how users learn that a stage is complete. Include subcontract or other supporting handovers where these are part of the operation.
Ask the software team to review these requirements against the available workflow. Confirm which statuses, quantities and reports are needed before deciding how the process will be configured.
Prepare quality and supporting documents
Gather blank or anonymized quality records, laboratory references, certification formats and other documents relevant to the sample order. Explain how each document relates to the order, product, material or production stage.
Identify the people who prepare, review and approve the records. If traceability is required, define the references that must remain connected and how corrections should be handled. Do not assume an existing document template will transfer unchanged without review.
Agree reports, users and acceptance criteria
Choose the reports needed for daily operations and management review. For each, list the fields, filters, time period and owner. Define who will enter data, who can correct it and who needs a read-only view.
Prepare an acceptance scenario using the sample order. The review should show the required records and outputs at each agreed stage, with open questions recorded for follow-up.
Plan implementation around the agreed scope
Separate software configuration from data preparation, imports, integrations, training and support. Confirm the source data, project contacts, responsibilities and readiness criteria before rollout. Timelines depend on those requirements and the work agreed.
Explore Velotech Foundry ERP and software implementation planning, then share your foundry workflow to discuss the next step.
