1.10 Engineering Deliverables & Design Management

Engineering deliverables communicate a mine's design basis, decisions and physical requirements through reports, drawings, models, specifications and records. Design management coordinates how these outputs are developed, checked, issued and revised. Its purpose is to keep the information used for a decision consistent with the design being evaluated and the work being authorised.

The engineering problem extends beyond document production. A mine plan, equipment specification and infrastructure drawing can each appear reasonable while referring to different production rates, layouts or operating stages. Managing their relationships is necessary for an implementable design and for understanding what must be reconsidered when conditions change.

Start with the decision and the intended use

Define who needs each deliverable, what decision or activity it supports, and what evidence makes it suitable for that use. Information adequate for comparing access options may be insufficient for fixing a shaft position, ordering equipment or releasing excavation. The required maturity follows the consequences of the decision and the unresolved conditions, rather than the appearance of a finished document.

UK BIM Framework Guidance Part A, edition 2, treats information management as responsibilities for defining, producing, checking and delivering information. It includes geometric information, data and documents, with responsibilities distributed across the project team. This UK guidance for implementing ISO 19650 offers an information-management precedent; it does not prescribe a mandatory mine documentation system.^[1]

For a mine project, a deliverable register can record purpose, responsible discipline, required inputs, recipient, issue date and permitted use. Identify who accepts the technical content and who authorises the next activity. A document controller can manage distribution without becoming responsible for the underlying engineering judgement.

Establish a common design basis

The design basis identifies the conditions to which the design applies: geological and survey information, ground and water models, production objectives, material properties, service availability, site constraints and applicable requirements. Each important input needs an identifiable source, revision or date, units and qualifications. An assumption should remain distinguishable from a measured condition or an externally imposed requirement.

Site conditions must influence the technical content. The World Bank Group's 2007 mining EHS guidance calls for recommendations to be assessed against project-specific hazards and circumstances. It also connects the mine and process-plant water balance with infrastructure design.^[2] A water-management drawing therefore needs an agreed flow basis and receiving-system assumptions; drawing detail alone cannot establish that its capacity matches the mine plan.

Separate the final arrangement from intermediate operating states. An extension may rely on temporary pumping, a restricted haulage route or a future power connection. Record when each condition applies and which activities depend on it. Otherwise a design can inadvertently combine the geometry of an early stage with the services of a later one.

Keep different representations consistent

Different deliverables answer different engineering questions. A report explains the basis and reasoning for a choice. A spatial drawing establishes positions and relationships. A system diagram explains connections or functions. An equipment specification defines the required duty and interfaces. A record of completed work retains evidence of what was observed, installed or tested. One form cannot automatically substitute for the others.

Consider an underground pumping installation as a qualitative coordination example. Its design explanation needs the inflow assumptions and operating duty; its arrangement needs location, access and installation space; its equipment documents need service conditions and connection requirements. Electrical and control information must refer to the same operating configuration. These relationships should be checked before the package is released, including the responsibility for each boundary.

For a crushing station or haul-road diversion, shared identities and compatible assumptions matter more than uniform file formats. Identify the controlled source of repeated values and update dependent outputs when that source changes.^[3]

Distinguish revision, status and technical maturity

Revision identifies a version; issue status identifies permitted use. Neither establishes technical adequacy. A preliminary equipment outline may support option comparison while leaving foundation details unresolved.

NASA's 2017 handbook links configuration control with consistency between an approved product and its technical information.^[3] For a mine project, define the baseline as the agreed reference for assessing changes. New geological evidence can require reassessment and controlled revision. Release limitations should identify the affected item and evidence needed before further commitment.

Review interfaces and control changes

A design review should test the reasoning behind a proposal as well as the consistency of its outputs. Ask whether inputs represent the relevant area and stage, whether the selected method suits the conditions, and whether interfaces preserve the required system function. Match review expertise to the issue: a survey discrepancy, uncertain rock-mass interpretation and incompatible control response require different evidence.

An approved change needs to be carried through its consequences. Moving a chamber may alter development quantities, service routes, equipment access and construction timing. The decision record should identify affected outputs, responsibilities, residual assumptions and conditions for implementation. Closure of an action means that the required correction and its consequences have been addressed, not merely that a meeting has occurred.^[3]

Keep technical acceptance, commercial agreement and permission to undertake work distinguishable. A supplier's alternative may meet a performance requirement while changing maintenance access or supply boundaries. Its commercial attractiveness does not resolve those engineering interfaces, and approval of a revised drawing does not by itself demonstrate that the physical change has been completed.

Retain evidence through construction and operation

Construction produces information that the design team did not possess initially: exposed ground, measured positions, installed configurations and test results. Reconcile this evidence with the approved basis. Record a deviation before deciding whether it requires correction, redesign or an accepted restriction. Updating a drawing to show a departure records the condition; it does not establish its acceptability.

Handover should preserve the relationship between the accepted configuration and the information needed to operate and maintain it. Users need to distinguish intended design, actual condition and verified performance. Unmeasured or inaccessible features should retain their qualification rather than acquire apparent certainty through a polished model.

The information also serves decisions beyond active production. ICMM's third-edition closure guide, updated in February 2025, describes a site-specific knowledge base that is collected, checked and revised throughout the mine life. It connects monitoring, uncertainty and new studies with subsequent planning.^[4] Retaining the basis for material placement, water arrangements and completed rehabilitation allows later assessments to use evidence instead of reconstructing undocumented assumptions.