Skip to main content
GullySystem
Manufacturing

Quality Control for Aluminium die casting companies

Record specified inspections and the disposition of checked goods.

Manufacturing

Does this function belong in your operation?

Use when goods or production stages require documented checks before release.

Material or output reaches an agreed inspection stage.

Porosity checks, X-ray sampling and leak tests are recorded per casting lot with the die and shift. Rejects carry a defect code. Customers see the same data on a test certificate.

Bring the records the workflow depends on.

  • Inspection specifications
  • Sampling and acceptance rules
  • Authorised reviewers

Outputs to check

  • Inspection readings and evidence
  • Hold, release or rejection record
  • Nonconformance follow-up list

Follow the quality control workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Select the inspection

    Identify the receipt, job or output and applicable specification.

  2. 2. Record measurements

    Capture required readings, sample details and evidence.

  3. 3. Review nonconformance

    Hold failures and assign the authorised disposition.

  4. 4. Release or reject

    Record the responsible decision and affected quantity.

  5. 5. Follow rework

    Link corrective work and reinspection without overwriting the original results.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Quality checker

Fills the check at the station and holds what fails. Simple.

Production in-charge

Sees rejection by stage and by operator, and knows which machine is drifting before the customer says so.

Purchase

Takes the gate rejections to the supplier with dates and readings attached.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Reading outside tolerance

Hold the affected quantity and route the disposition to the authorised reviewer.

Inspection incomplete

Keep release pending and show the missing measurement or evidence.

Reworked goods returned

Create a linked reinspection rather than replacing the original failure record.

Can this work independently?

Quality records can be maintained independently against identifiable receipts or jobs. Inventory and production connections must enforce any hold or release decision. The module records authorised checks; it does not select a regulatory standard or replace a qualified inspector's judgement.

Systems and records it connects with

  • Work orders: Released production jobs, material issues and output records.
  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Purchase returns: Approved supplier-return quantities and adjustment references.
  • Batch and serial tracking: Lot or unit identifiers carried through stock movements.

Configure, test and introduce the workflow.

  • Show us where checks happen now. A note names the checkpoints and the parameters to record.
  • Provide limits and your list of rejection reasons. A test lot can then be checked on the trial screen. Checkers use it at a station for a trial run. Their remarks return as changes.
  • Checkers, production and purchase each practise their part. Each group gets a printed card. Other stations join as the trial station settles. The team reviews rejection reasons together.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Failed items follow the agreed hold rule.
  • Results retain the specification version.
  • Release decisions identify the reviewer.
Aluminium die casting companies

How the business operates.

A die casting cell is fast and unforgiving. A furnace holds molten alloy, a machine fires it into a steel die in seconds, and a trim press removes runners and overflows. A hundred castings an hour leave the cell. Small shifts in die temperature, spray or metal quality show up as porosity or cold shuts.

Alloy lot and melt record

Record ingot lots, returned scrap, degassing and the chemistry sample for each melt, and tie them to the shots cast.

Die register and shot counts

Count shots per die, log cleans, polishing and repairs, and flag a die before it passes its limit.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Part list and call-offs. Hold each casting with its drawing revision, alloy grade such as A380 or ADC12, die and route. Load call-offs and revisions by week.
  • Alloy and ingot stock. Receive ingot by heat lot, issue it to melts, and keep returned gates and dross on separate accounts.
  • Melt and chemistry record. Record each melt, its charge, degassing time and spectrometer sample, then release it to the holding furnace once the chemistry passes.
  • Machine and die planning. Plan machines by clamping tonnage and dies by availability and shot count, and show which die change comes next to the setters.

Operational bottlenecks to check

Alloy lots mix in the furnace

Fresh ingot and returned runners are charged together into one furnace. When a casting fails chemistry, the lot that fed that melt is unclear, and every casting from the shift comes under doubt.

Die life is counted on a tag

Shots run on a die decide when it needs a clean, a polish or a repair. The tag is updated at changeover, but a die pulled off the machine in a hurry keeps yesterday’s count and nobody notices until it cracks.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Call-off and plan

    Call-offs are loaded by part and week. The planner assigns a machine, a die and an ingot lot, then checks the die’s shot total against its cleaning limit before the setter is told.

  2. 2. Melt

    Ingot and returned gates are charged, degassed with a rotary impeller and sampled for the spectrometer. A passing chemistry result releases the melt to the holding furnace.

  3. 3. Casting run

    The operator records the die, the plunger speed settings, the intensification pressure and the shots. Good and rejected counts are entered when the run closes.

  4. 4. Trim and remelt

    Castings go to the trim press while biscuits, runners and overflow wells are weighed back for remelt. Yield per part updates on the spot.

  5. 5. Test and machine

    Samples go for X-ray, density index or helium leak checks. Passed lots follow the route card to machining, deburring or impregnation.

  6. 6. Dispatch

    Crates are counted, labelled and loaded. Once the truck leaves, the invoice and the dispatch record close the call-off.

Industry reports to connect with

  • Call-offs against shipments by part and week
  • Melts with chemistry results and castings made
  • Shots and rejects by die
  • Metal yield by part and by melt

Questions before implementation.

When should aluminium die casting companies consider quality control?

Use when goods or production stages require documented checks before release. Material or output reaches an agreed inspection stage.

What should we bring to the requirements discussion?

Bring anonymised examples of Inspection specifications; Sampling and acceptance rules; Authorised reviewers. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record specified inspections and the disposition of checked goods. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The software records your inspection process and does not certify product safety or regulatory conformity.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Failed items follow the agreed hold rule. Use this check when reviewing the first working version.

Talk to us

Discuss quality control for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements