Skip to content
MAX4METS

One auditable source of truth

Every measurement, assay and adjustment lives in a secure relational database with a full audit trail, not in a spreadsheet on someone's desktop.

Metallurgical accounting kept in spreadsheets can become a chain of workbooks: a daily workbook per circuit, a monthly workbook that copies from them, and a report pack that copies from that. Each copy loses a little of the link back to the source, and it can be hard to say who changed a figure or why. MAX holds the same data in a single relational database (Microsoft SQL Server or Azure SQL) that every user works from, so there is one set of numbers and a record of how each one got there.

Every value has a history

Each value in MAX carries the user who created it and the user who last updated it, with the date and time of each. Values are also tied to the data input session that produced them: a particular file import, worksheet entry or calculation run. Each session keeps its own log of what was read, what was written and any warnings raised, so a figure on a report can be traced back to the file or the person it came from.

Changes made through the application are written to a user activity log that records the property changed with its previous and new values. Creating and deleting records is logged too, as are logins and commands, and logging of record reads can be switched on where a site needs it. What is logged, and for how long the logs are kept, is configurable per type of data.

Imported files can be retained alongside the data they produced, either for a fixed number of days or indefinitely, so the original laboratory or plant file is still available when an auditor asks for it.

Adjustments never overwrite the measurement

Metal accounting needs adjustments: a moisture correction, a survey-based stock change, a reconciliation to a final assay. In MAX a numerical value keeps its original measured value and its adjusted value side by side, with a comment explaining the change. Users can show or hide adjustments in a view, so it is always possible to see both what was measured and what was reported.

Protecting reported periods

Once a month has been reported, its figures should not move. Administrators set a lock date, and values on or before it cannot be edited until the period is deliberately unlocked. Period reports move from Draft to Approved, recording who approved them and when, and an approved report keeps the values it was approved with.

Many users, one database

Operators, metallurgists, technical services and management all work in the same system through a web browser, at the same time. MAX uses optimistic concurrency, so if two people edit the same record the second save is detected and stopped rather than silently overwriting the first.

Why it matters for AMIRA P754

The AMIRA P754 code of practice asks for a metal accounting system that is transparent, with clear sources for every input, controls and audit trails. A central database with per-value history, logged changes and protected periods is the foundation for that, and it removes the risk of the month-end depending on one person’s workbook.

More MAX4METS features

Ready to elevate your metallurgical accounting?

Book a demonstration and see how MAX fits your plant, your data sources and your reporting cycle.