Conceptual, Basic and Detailed Engineering

Conceptual, basic and detailed engineering describe the progressive definition of a proposed mine and its supporting facilities. Conceptual work explores workable configurations; basic engineering develops the selected arrangement and its principal requirements; detailed engineering produces the coordinated information needed for procurement, fabrication and construction. The progression connects engineering decisions with increasingly specific evidence and deliverables.^[1][2]

Agree the Meaning of Each Phase

The phase names are useful only when their scope is clear. A project should specify which facilities are included, which decisions are to be resolved, the information supplied by each discipline, and the purpose for which each document may be used. A layout suitable for comparing alternatives may leave dimensions or interfaces unresolved that a construction package must define.

Study level, engineering phase and estimate class describe different attributes. AACE's classification guidance bases estimate class on the maturity of scope-defining information; class alone establishes neither estimating quality nor a fixed accuracy range. Consequently, a feasibility-study label or a percentage of engineering completion cannot substitute for examining the deliverables and uncertainties behind the estimate.^[3]

For a mine project, it is useful to separate approval of the overall development concept from authorization to execute a particular package. The practical question is whether the information is sufficiently resolved for the proposed commitment, including dependencies on work that remains incomplete.

Conceptual Engineering: Compare Coherent Options

Conceptual engineering establishes possible ways to meet the project requirements and identifies the investigations needed to distinguish them. The U.S. Department of Energy's 2018 design-review guidance illustrates this logic through assessment of alternatives, performance objectives, technical achievability, risks, cost and schedule. The document is non-mandatory U.S. federal guidance; its design reviews illustrate how decisions and required evidence change as a project develops.^[1]

Applied to mining, an option should describe a connected operating arrangement. Comparing access alternatives, for example, requires considering how people, ore, waste and services would move through the mine. A choice that appears attractive when judged only by access construction may create difficulties elsewhere in the production system. This is an engineering comparison to be developed from the particular deposit and site, not a universal preference for one access form.

A useful conceptual record explains why the retained options remain plausible, what could make them unsuitable, and which assumptions most affect the comparison. It should preserve the reasons for rejecting alternatives so that later changes can be judged against the original decision basis.

Basic Engineering: Establish the System Definition

Basic engineering develops the preferred concept into a coordinated basis for subsequent design. Its emphasis is the arrangement and requirements of the systems: what each must do, where it fits and what it requires from neighbouring systems. For processing facilities, the engineering documents can cover process arrangements, layouts and mechanical, structural and automation requirements. Detailed engineering subsequently develops these into information released for fabrication and construction.^[2]

Interfaces deserve explicit treatment. NASA's systems-engineering guidance identifies physical, electrical, mechanical and human interfaces and connects their definition with compatibility and integration. Applied to a mine project, the implication is that each team needs agreed information about both its own system and the systems it connects to. An interface should have identifiable responsibilities and a defined basis for checking compatibility.^[4]

Consider the following qualitative example for an underground pumping facility. The water-management assessment provides the duty conditions; mine design provides its position and access; civil and structural work provides the space and supporting works; electrical and control engineering addresses supply and operation. Basic engineering should expose the dependencies among these decisions before each team develops detailed documents independently.

The design basis should distinguish verified inputs, interpretations and provisional assumptions. Where an unresolved input could alter several disciplines, the remaining investigation and its affected documents should be visible in the work plan. Otherwise, apparent progress in drawing production can conceal an unresolved system decision.

Detailed Engineering: Make the Design Executable

Detailed engineering specifies how the approved arrangement will be implemented. The DOE guide describes final design outputs as drawings, technical specifications and contract documents for procurement and construction, together with testing requirements and acceptance criteria. These outputs support checking both what is to be supplied and how conformity will be demonstrated.^[1]

For a particular package, readiness should be judged against its intended use. Procurement information needs to define the supplier's scope and connection requirements. Installation information needs to reconcile the supplied equipment with the actual site and adjacent work. Construction information needs the applicable geometry, materials, connections and quality requirements. Document status should communicate whether these matters have been resolved and who has authorized the issue.

Constructability and maintainability also affect the design. Safe Work Australia's November 2024 model code for workplace structures considers construction methods, access for maintenance, temporary conditions and residual hazards. Its legal effect depends on adoption in the relevant Australian jurisdiction. The engineering lesson is to involve people familiar with building, operating and maintaining the facility while design changes remain practicable.^[5]

For example, a maintenance space shown on a layout should be tested against the intended task: reaching components, removing them and transferring them to a safe working position. This kind of review examines the proposed use of the design and may reveal requirements that are absent from equipment dimensions alone.

Apply the Progression to Mine Excavations

Mine excavations introduce a continuing relationship between design and observed ground behaviour. The 2019 Western Australian ground-control guideline treats design as an iterative activity supported by geological and geotechnical information, appropriate analytical methods, implementation checks and performance monitoring. It also distinguishes the needs of different mine openings and their exposure periods. Surface slopes, underground access and production excavations therefore require different design questions, even when the project uses common document-control arrangements.^[6]

Detailed plans do not remove geological uncertainty. New mapping, measurements or observed response can require reassessment of the assumptions, geometry, sequence or controls. The same guideline emphasizes understanding the limitations of the chosen design method and using site observations to check its continuing applicability.^[6]

This means that an excavation package can be sufficiently developed for a defined scope of work while still requiring specified observation and review as mining advances. The release decision should explain that relationship rather than implying that all future ground conditions have been established.

Review, Change Control and Handover

An engineering baseline is the agreed definition against which changes are assessed. Configuration management keeps the physical system and its documentation consistent by identifying the controlled information, evaluating changes and recording their implementation. Interface changes require communication to affected teams, including updates to the documents on which they rely.^[4]

As a practical review, a proposed change can be examined through three questions: what requirement or assumption has changed; which connected work is affected; and what evidence is needed before the revised package can be released? For the pumping-facility example, moving its location could require reconsidering access, supporting works, pipe routes, supply connections and installation sequence. The consequence extends beyond relocating a symbol on the layout.

Verification checks conformity with specified requirements; validation examines suitability for the intended use and operating environment. NASA's handbook distinguishes these purposes and calls for identifiable acceptance criteria and retained results. The distinction helps explain why checking drawings, testing equipment and assessing the integrated operating arrangement address related but different questions.^[4]

Handover information should preserve the design's intended use, relevant limitations, residual risks and information needed for later maintenance or modification. Safe Work Australia's model code discusses communicating design information through drawings, safety records and maintenance documents, and revisiting design risks when structures are modified. This is a useful information-transfer principle for mine infrastructure, with applicable local requirements established separately.^[5]

For a mine project, retain an agreed record of the installed configuration, accepted changes and outstanding conditions. These records give the operating team a consistent starting point for inspection, maintenance and subsequent design work.^[4]