Equipment Lists and Technical Specifications

Equipment lists and technical specifications turn mine design decisions into identifiable supplies and verifiable obligations. The equipment list establishes what is included; the specification defines what the purchaser requires. The World Bank's June 2025 procurement guidance describes specifications as both the definition of the intended purchase and a basis for judging the supplier's contractual performance.^[1]

For a mine, the central task is to keep each equipment identity connected to its duty, supply boundary, requirements, and accepted configuration. A model number or headline capacity cannot carry that information alone.

Different records serve different purposes

The following division is a practical project convention. Organizations may combine records, but should preserve the distinctions between required, offered, purchased, and installed information.

An equipment list supports scope coordination; a procurement schedule adds timing and purchasing progress. Neither demonstrates that a delivered item meets its duty. Similarly, the proposed catalogue model in a bid should remain distinguishable from the model eventually installed.

At an early estimating stage, grouped quantities may be sufficient. Label them as groups, then resolve individual equipment and package identities as the design develops. Distinguish operating units, standby units, warehouse spares, and future provision so that quantities and supply scope remain interpretable.

IOGP's JIP33 provides an industry example of separating procurement data sheets, technical requirements, quality requirements, and information requirements. Its data sheets capture project selections; the other documents address technical requirements, inspection and testing, and supplier deliverables. JIP33 was developed for oil and gas procurement and supplements applicable standards; its document structure is an example, rather than a mandatory mining format.^[2]

Establish the duty and its operating context

Prepare a dated duty basis before requesting firm offers. Give each input an origin, revision, responsible discipline, and confidence status. An unresolved process value needs an explicit provisional basis and a decision date.

A useful mine equipment enquiry identifies:

• Duty cases: normal operation, required operating range, startup, shutdown, intermittent operation, standby service, and future stages that are actually included in the purchase.
• Handled material: the relevant ore, waste, water, slurry, air, or reagent characteristics, including expected variability.
• Site conditions: elevation, ambient temperature, exposure, dust, water ingress, corrosion environment, and installation location.
• Available services: electrical supply, control power, water, compressed air, fuel, communications, and their operating limits.
• Service expectations: operating hours, starts, maintenance access, replacement strategy, required support, and planned life.
• Physical constraints: transport route, lifting arrangements, access openings, foundations, clearances, and connections to existing works.

Keep the cases internally consistent. A future ore type, peak production rate, and unusual ambient condition may belong to different scenarios; combining every extreme requires an engineering justification. Identify which cases govern selection and which require a performance guarantee.

A slurry pump illustrates why duty information extends beyond flow. Metso Outotec's 2020 handbook identifies flow or solids tonnage, static lift, pipe-system losses, chemistry, density, concentration, and particle characteristics as relevant inputs. Its hydraulic discussion also addresses inlet conditions, atmospheric pressure, and temperature. These are application inputs, not a recommendation to select a particular manufacturer's equipment.^[3]

Make units, reference conditions, and margins explicit

Choose a project unit convention and show units beside every numerical field. Describe the quantity sufficiently to distinguish dry solids throughput from wet throughput, and mass concentration from volume concentration. The slurry handbook explicitly distinguishes concentration by mass and by volume; treating them as interchangeable changes the stated duty.^[3]

For other equipment, equally useful distinctions include gauge versus absolute pressure, actual versus reference gas volume, and absorbed power versus installed motor rating. Define the reference temperature, pressure, moisture basis, or other condition where it affects interpretation.

Record the base duty separately from any design allowance. State the purpose and origin of each margin, who authorized it, and whether it is already included in upstream inputs. This makes duplicated allowances visible. Keep operating range, design envelope, guaranteed performance, and test acceptance tolerance in separate fields: they answer different questions and should not silently substitute for one another.

Control equipment identity and package boundaries

The March 2022 CFIHOS RDL Development Guide distinguishes a functional tag from the physical equipment fulfilling that function. A physical item may have a serial number, while the functional identity can persist through replacement. CFIHOS originated in the process and energy sectors; this distinction is useful when structuring mine records without making its classification scheme a mining requirement.^[4]

Define the project's tagging rules and granularity early. Record package membership and decide which maintainable components need their own identities. An enquiry for a pumping package, for example, should identify whether the pump, motor, coupling, guard, baseplate, instruments, and local controls belong to the supply. These are illustrative boundary questions, not a universal package definition.

For each connection, state the physical boundary, required information, and responsible party. A nozzle interface needs its location and connection details; an electrical interface needs supply and termination requirements; a control interface needs the agreed signals and command responsibilities. Assign responsibility for foundation loads, anchor arrangements, lifting information, and installation services.

Check these boundaries against the layout, electrical load list, and system diagrams. A motor included in the supplier's package still needs coordination with the site's power system. Likewise, a control panel described as included does not establish who provides site cabling, software integration, or commissioning assistance.

Write requirements that can be accepted

Separate the required result from any prescribed solution. The World Bank guidance distinguishes performance specifications, which state outcomes, from conformance specifications, which prescribe characteristics. It also recommends measurable requirements and a clear basis for success or failure. Its procurement rules apply within its financing framework; the distinction is useful more broadly when drafting a mine enquiry.^[1]

For each significant requirement, record:

• The required function or performance and the operating cases to which it applies.
• Any justified construction, material, compatibility, or installation constraint.
• The proposed verification method: document review, inspection, calculation, demonstration, or test.
• The conditions, acceptance criterion, required record, and authority for accepting the result.

Avoid combining several unrelated obligations in one statement. A requirement for capacity, energy use, and wear performance needs separately defined evidence for each. Terms such as reliable, heavy duty, or suitable for mining need an engineering definition before they can guide acceptance.

Identify referenced standards by designation and edition, and identify applicable legal requirements by jurisdiction. Record project supplements and resolve conflicting requirements through the agreed contract procedure. A supplier's compliance statement should identify what it covers.

Define the test boundary

Specify what will be tested, where, under which conditions, and with which auxiliaries. Distinguish factory evidence from checks that require the installed system. Agree any witness or hold points, reporting obligations, treatment of nonconformities, and retesting arrangements in the procurement documents.

IOGP Report 795, version 1.0 of December 2022, distinguishes inspection and test-plan activities from formal submission of supplier documents. Within JIP33, purchaser intervention is chosen using risk and criticality. This is a useful reminder to specify both participation in verification activities and delivery of the resulting evidence.^[5]

ISO 9906:2012, second edition, covers hydraulic performance acceptance testing of rotodynamic pumps at test facilities for liquids behaving as clean, cold water. Its public abstract also distinguishes testing a pump alone from testing it with associated fittings. For a slurry-service purchase, therefore, identify the relationship between that test scope and the required site duty; the standard's title alone does not define acceptance of the complete slurry installation.^[6]

Do not insert an assumed percentage tolerance or guarantee duration. Select and agree the acceptance basis appropriate to the equipment and contract, using the applicable source documents and engineering assessment.

Evaluate deviations and substitutions explicitly

Use a requirement-by-requirement technical comparison when reviewing bids. Ask suppliers to distinguish compliance, qualifications, exceptions, and assumptions, with references to supporting data. Keep a deviation record identifying the original requirement, proposed alternative, technical consequences, decision, conditions, and approval authority.

A substitution deserves review even when its headline rating matches. Examine the effects on connections, dimensions, loads, utilities, controls, maintenance, spares, and the agreed performance evidence. Record any resulting changes to price or delivery through the contractual process.

Retain the purchaser's requirement alongside the accepted vendor response. Overwriting an original datasheet value can conceal a concession. After agreement, update the affected list entries, datasheets, specifications, and interface information together, using the project's revision controls.

Specify information delivery and operational handover

Define the supplier information schedule during procurement. JIP33's information requirements distinguish deliverables and their timing, while its quality requirements address inspection and purchaser involvement. This illustrates why documentation and assurance need an explicit place in the enquiry package.^[2]

For a mine package, tailor the schedule to the decisions awaiting information. Foundation and connection data may be needed before manufacture is complete; operating manuals are needed before training and commissioning. Specify each deliverable's identifier, content, format, submission milestone, review purpose, and required final status. Give the supplier an agreed way to identify superseded revisions.

At handover, reconcile the purchased scope with the installed equipment and accepted changes. Link tags and serial numbers to final datasheets, drawings, test records, certificates where applicable, maintenance instructions, spare-parts information, and commissioning records. CFIHOS's distinction between functional and physical information helps preserve this relationship when equipment is replaced during operation.^[4]

Assign ownership of the continuing records. Retain the history of removed or relocated items, and record replacement equipment against the correct function. The equipment list and specification set then remain traceable evidence for maintenance, future modifications, and eventual removal.