Question 1

What does Struktive for Mining actually do?

Accepted Answer

Struktive for Mining takes a messy equipment register CSV or Excel export from a mine site and returns a clean, structured, scored version of that data — ready to import into IBM Maximo, SAP PM, Pronto Xi, Infor EAM, or Ellipse. It resolves OEM names (e.g. 'CAT', 'Caterpillar Inc.', 'Cat' → 'Caterpillar'), parses free-text location strings into a structured mine hierarchy (Site → Area/Pit → Level → Functional Area), classifies every equipment item into one of 12 mining-specific categories, scores each record 0–100 on EAM import readiness, and generates platform-native export files with suggested Functional Location (FLOC) codes.

Question 2

What file formats does Struktive for Mining accept?

Accepted Answer

Struktive accepts CSV and Excel (.xlsx / .xls) files. It handles real-world equipment register exports — files with metadata preamble rows, inconsistent quoting, mixed delimiters, and empty rows are all handled gracefully. Maximum file size is 50 MB per upload.

Question 3

Do I need to format my equipment register before uploading?

Accepted Answer

No. Struktive auto-detects column mappings using a library of 300+ mining-specific header aliases (e.g. 'Asset No', 'Equipment Tag', 'Fleet No', 'OEM', 'Manufacturer', 'Make', 'Mine Area', 'Location', 'Level'). You do not need to rename columns or reformat your file before uploading.

Question 4

How does the 7-stage pipeline work?

Accepted Answer

Stage 1: OEM Name Resolution — resolves 1,200+ raw OEM name variants to canonical names. Stage 2: Mine Hierarchy Parsing — extracts site, pit/area, level, and functional area from free-text location strings. Stage 3: Equipment Classification — assigns one of 12 mining categories using keyword rules and LLM fallback. Stage 4: EAM Enrichment — matches equipment to 1,200+ model records and suggests Maximo FLOC / SAP FL codes. Stage 5: Duplicate Detection — flags exact and fuzzy duplicates by equipment tag, serial, and location. Stage 6: Quality Scoring — scores each record 0–100 on EAM import readiness. Stage 7: Export Generation — renders platform-native export files for your target EAM.

Question 5

What is the quality score for mining equipment?

Accepted Answer

Each equipment record receives a 0–100 quality score. The mining scoring formula weights OEM resolution (+15), serial number (+15), and mine hierarchy resolution (+10) heavily, reflecting EAM import requirements. Records scoring 70 or above are considered EAM import-ready. Records below 50 typically have missing equipment tags, unresolved OEM names, or no location data — these require manual review before EAM import.

Question 6

Can Struktive handle underground mine equipment registers?

Accepted Answer

Yes. The mine hierarchy parser handles both open-cut and underground location structures. For underground sites, it extracts level designations (e.g. 'L850', 'L920', '850 Level'), portal references, and underground area codes. The Maximo FLOC and SAP FL suggestions reflect the underground hierarchy structure.

Question 7

Which EAM platforms does Struktive export to?

Accepted Answer

Struktive currently supports six export profiles: IBM Maximo (Equipment, Functional Location, and Classification records), SAP PM / S/4HANA (Equipment master data mapped to EQUNR, EQTYP, HEQUI, IWERK fields), NI 43-101 QP Equipment Schedule (18-column CSV with ISO 14224:2016 class codes, FLOC hierarchy, and QP sign-off fields for National Instrument 43-101 technical reports), Pronto Xi (Equipment register CSV), Infor EAM (Equipment and location hierarchy CSV), and Ellipse (Equipment register CSV). The platform selector appears at download time.

Question 8

How does the Maximo export work?

Accepted Answer

The Maximo export generates three linked CSV files: Equipment (ASSETNUM, DESCRIPTION, MANUFACTURER, MODEL, SERIALNUM, SITEID, LOCATION, ASSETTYPE, STATUS), Functional Location (LOCATION, DESCRIPTION, SITEID, TYPE, PARENT), and Classification (ASSETNUM, CLASSSTRUCTUREID, CLASSIFICATIONID). Suggested FLOC codes are derived from the mine hierarchy parsed from your location data. The pre-flight summary panel shows any FLOC codes that need to be created in Maximo before the equipment import.

Question 9

How does the SAP PM export work?

Accepted Answer

The SAP PM export generates an equipment master data CSV mapped to SAP PM field names: EQUNR (equipment number), EQTYP (equipment category), HEQUI (superior equipment), IWERK (maintenance plant), SWERK (planning plant), BRGEW (gross weight), GEWEI (weight unit), HERST (manufacturer), TYPBZ (model number), SERGE (serial number). Functional Location codes follow SAP's hierarchical structure (e.g. SITE-AREA-LEVEL-SYSTEM).

Question 10

What are Functional Location (FLOC) codes and how are they generated?

Accepted Answer

Functional Location codes are the hierarchical identifiers used by Maximo and SAP PM to represent the physical and functional structure of a mine site. Struktive generates FLOC suggestions by parsing the mine hierarchy from your location data: site code + area/pit code + level code + discipline code. For example, 'North Pit, Level 850, Mechanical' becomes 'NORTHSTAR-PIT-NORTH-L850-MECH'. These are suggestions — your EAM administrator should review and adjust them to match your existing FLOC structure before import.

Question 11

Can Struktive push data directly into Maximo or SAP PM?

Accepted Answer

Not yet. The current workflow is: normalise in Struktive → download the platform-specific export file → import into your EAM using the platform's native import tool or your implementation partner's migration scripts. Direct API push is on the roadmap.

Question 12

What is ISO 14224:2016 and how does Struktive use it?

Accepted Answer

ISO 14224:2016 is the international standard for the collection and exchange of reliability and maintenance data for equipment in the petroleum, petrochemical, and natural gas industries. It defines a hierarchical taxonomy of equipment class codes (e.g. Class 41 — Pumps, Class 42 — Compressors, Class 61 — Electrical generators) that is increasingly referenced in mining for equipment classification and reliability data alignment. Struktive maps every normalised mining asset to its ISO 14224:2016 class code and reports a conformance rate — the percentage of records that map to a direct ISO 14224 code. For mobile mining equipment not covered by ISO 14224:2016 (haul trucks, excavators, drill rigs), Struktive applies MINING-EXT extension codes with the closest applicable ISO 14224 reference noted. The conformance rate and class code breakdown appear in the Provenance Pack PDF certificate and in the results table for every mining job.

Question 13

What does Struktive do for MRO parts catalogues?

Accepted Answer

Struktive normalises MRO parts catalogues for SAP MM, Maximo Item Master, and Pronto Xi. It standardises free-text part descriptions to structured noun-modifier format, resolves UOM variants (e.g. 'EA', 'EACH', 'Each', 'ea' → 'EA'), detects duplicate part numbers and descriptions, assigns UNSPSC commodity codes, and generates platform-native export files for SAP MM Material Master and Maximo Item Master bulk import.

Question 14

What is noun-modifier format and why does it matter?

Accepted Answer

Noun-modifier format is the standard parts description structure used in EAM and procurement systems: NOUN, MODIFIER — ATTRIBUTE 1; ATTRIBUTE 2. For example: 'BEARING, ROLLER — TYPE: CYLINDRICAL; BORE: 50MM; OD: 90MM; WIDTH: 20MM'. This format enables consistent searching, deduplication, and UNSPSC code assignment. Without it, the same bearing might appear as 'cylindrical roller bearing 50mm', 'bearing 50x90x20', and 'SKF NU210' — three separate catalogue entries for the same part.

Question 15

How does duplicate detection work for parts?

Accepted Answer

Struktive uses a three-tier duplicate detection approach: exact part number match (after normalisation), fuzzy description match (noun-modifier similarity above 0.85 threshold), and manufacturer + part number match. Detected duplicates are flagged with a duplicate type (Exact, Fuzzy, or Cross-Reference) and the row index of the master record. The EAM Migration Audit Pack includes a dedicated Duplicates worksheet.

Question 16

What is UNSPSC and why is it assigned?

Accepted Answer

UNSPSC (United Nations Standard Products and Services Code) is the global commodity classification standard used in procurement, EAM, and spend analytics. Assigning UNSPSC codes to your parts catalogue enables spend analysis by category, supplier rationalisation, and integration with procurement platforms. Struktive assigns 8-digit UNSPSC codes based on the normalised noun-modifier description and equipment category.

Question 17

Where is my equipment register data stored?

Accepted Answer

Uploaded files and generated exports are stored in an S3-compatible object store with non-enumerable keys. Metadata is stored in a MySQL-compatible database. No data is shared with third parties. Equipment register data is not used to train any models.

Question 18

Does Struktive use my equipment data to train models?

Accepted Answer

No. Your equipment register data is never used to train machine learning models. The LLM receives only the equipment description and category options — it does not receive your equipment tags, serial numbers, or location data.

Question 19

Is my data encrypted in transit and at rest?

Accepted Answer

Yes. All data is encrypted in transit via TLS 1.2+. Data at rest is encrypted using AES-256 at the storage layer.

Question 20

What is equipment provenance and why does it matter for mine operators?

Accepted Answer

Equipment provenance is the documented record of where each item in your mine site equipment register was manufactured — the OEM identity, country of manufacture, applicable free trade agreement status, and relevant compliance frameworks. It matters because regulators (NRCan, CEAA-2012), lenders (ESG-linked facilities), and acquirers increasingly require this documentation as part of RFI submissions, environmental assessments, and due diligence processes. A structured provenance pack generated from your normalised register provides that documentation in a submission-ready format.

Question 21

What does a Struktive provenance pack contain?

Accepted Answer

A Struktive provenance pack contains five components: (1) an equipment origin summary — a breakdown of the register by country of manufacture; (2) a manufacturer breakdown — every OEM in the register with their canonical name, country of manufacture, and equipment count; (3) a compliance framework attestation — a list of the applicable regulatory frameworks for the mine's jurisdiction (e.g., NI 43-101, CEAA-2012, CUSMA, CPTPP, CETA for Canadian mines) with official document links; (4) an ISO 14224:2016 classification summary — the conformance rate (percentage of records with a direct ISO 14224 class code), MINING-EXT extension count, and unclassified count, with the standard citation; and (5) chain-of-custody metadata — the source file hash, processing timestamp, normaliser version, and record count that make the pack tamper-evident.

Question 22

Which jurisdictions does Struktive support for provenance documentation?

Accepted Answer

Struktive currently supports four jurisdiction configurations: Canada (CA) — NI 43-101, CEAA-2012, MSHA-CA, CUSMA, CPTPP, CETA, EFTA; Australia (AU) — JORC-2012, EPBC Act, MSHA-AU, AUSFTA, AUKFTA, CPTPP; South Africa (ZA) — MPRDA, SAMREC-2016, MHSA, BBBEE, SADC-FTA; and Global Standard — ISO 55001, GHG Protocol, TCFD, SASB Metals & Mining. Additional jurisdictions can be configured for enterprise accounts.

Question 23

How does Struktive handle NRCan's critical minerals RFI requirements?

Accepted Answer

NRCan's Request for Information processes for critical minerals projects increasingly ask proponents to demonstrate supply chain transparency, including the origin of major capital equipment. A Struktive provenance pack — generated from the normalised equipment register — provides a structured, submission-ready document showing manufacturer breakdown by jurisdiction, FTA partner status, and compliance framework attestation. The CA jurisdiction configuration covers all eight frameworks relevant to NRCan submissions: NI 43-101, CEAA-2012, MSHA-CA, SEMA, CUSMA, CETA, CPTPP, and EFTA.

Question 24

Does the provenance pack cover CUSMA and CPTPP tariff eligibility?

Accepted Answer

Yes. The provenance pack flags each manufacturer as a CUSMA, CPTPP, or CETA partner country where applicable. This provides the documentation foundation for customs compliance and FTA tariff claims. For a Canadian mine importing equipment from the United States, CUSMA preferential tariff rates on qualifying mining equipment can be 0% versus the MFN rate of 2.5-6.5% — but only if the country-of-manufacture documentation supports the eligibility claim. The provenance pack creates that documentation record.

Question 25

Can the provenance pack be used for CEAA-2012 environmental assessment submissions?

Accepted Answer

Yes. The Canadian Environmental Assessment Act 2012 requires project descriptions to include a description of the supply chain, including the origin of major equipment and materials. A Struktive provenance pack provides a structured, citable document that satisfies this requirement. The pack includes the equipment origin summary and manufacturer breakdown in a format that can be attached directly to a CEAA-2012 project description submission.

Question 26

How does provenance documentation support ESG financing?

Accepted Answer

ESG-linked loan facilities and green bonds increasingly include supply chain transparency covenants requiring borrowers to demonstrate that major capital equipment is not sourced from sanctioned jurisdictions or high-risk supply chains. A Struktive provenance pack — updated with each major procurement cycle — provides the documentation that satisfies these covenants without requiring a bespoke audit for each financing event. The pack's sanctions screening component flags any equipment from jurisdictions on current OFAC, UK OFSI, or EU consolidated sanctions lists.

Question 27

Is provenance documentation available on the free tier?

Accepted Answer

Provenance pack generation is available on paid tiers. The free tier (50 records) includes OEM name resolution, country-of-manufacture mapping, and FTA partner flagging in the normalised output, but does not generate the full PDF attestation certificate with compliance framework attestation and chain-of-custody metadata. Enterprise accounts include provenance packs as a standard output for all jobs.

Question 28

How does pricing work for mining equipment registers?

Accepted Answer

Struktive uses a credit-based model. Credits are purchased in packs and consumed per record processed. One record = one row in your equipment register CSV. There is a free tier that allows you to normalise up to 50 records without purchasing credits — no login required. See the Pricing page for current pack sizes and rates.

Question 29

Are the pricing rates the same for equipment registers and MRO parts catalogues?

Accepted Answer

Yes. The per-record rate is the same for both equipment registers and MRO parts catalogues. Credits are interchangeable — you can use the same credit balance to process both equipment and parts data.

Question 30

Do credits expire?

Accepted Answer

Credits do not expire. Once purchased, they remain in your account until used.

Question 31

Is there an enterprise plan for large EAM migration programmes?

Accepted Answer

Yes. Enterprise plans include volume pricing (from $0.60/record), a dedicated account manager, custom FLOC generation rules, and SLA commitments. Contact us to discuss enterprise pricing for your programme.

Question 32

What happens to my uploaded file after processing?

Accepted Answer

Your original uploaded file is automatically deleted from our storage servers when your job completes. This happens without any action from you. We keep the normalised results — not your raw file. The fileUrl field in your job record is cleared at the same time.

Question 33

How long is my data retained?

Accepted Answer

Free-tier jobs (no account) are retained for 90 days from the date of processing. Paid jobs are retained for 12 months. Compliance Audit Packs are retained for 12 months regardless of tier. At the end of the retention period, job records and all associated asset data are automatically purged by a nightly cleanup job.

Question 34

Is my data used to train AI models?

Accepted Answer

No. Your inventory data is never used to train, fine-tune, or build datasets for any machine learning model. The LLM classification stage receives only the asset description and category options for each record — it does not receive your hostnames, serial numbers, IP addresses, location data, or any other identifying information.

Question 35

Can other users see my data?

Accepted Answer

No. Every job is isolated to your account or session. Authenticated jobs are accessible only to the account that created them. Anonymous jobs are accessible only via the unique job ID — this ID is not guessable or enumerable.

Question 36

What security controls are in place?

Accepted Answer

All connections use TLS 1.2+. Security headers are applied to every response (HSTS, X-Frame-Options: DENY, X-Content-Type-Options: nosniff). Rate limiting is applied at three tiers: 120 req/min general, 5 attempts/15min auth, 10 uploads/hour anonymous. Passwords are hashed with bcrypt. API keys are stored as SHA-256 hashes — the raw key is shown once at creation and never stored.

Question 37

How are Compliance Audit Packs protected against tampering?

Accepted Answer

Every Compliance Audit Pack receives a SHA-256 hash at generation time. This hash is stored in a tamper-evident audit pack registry with WORM semantics — records cannot be modified after creation. You can verify the integrity of any pack at any time via struktive.io/verify.

Question 38

Where can I read the full security documentation?

Accepted Answer

The full security page at struktive.io/security covers the complete data lifecycle, all technical controls, data handling commitments, and responsible disclosure contact. A machine-readable security.txt is available at /.well-known/security.txt.

Everything you need to know about Struktive for Mining

Mining EAM

Ready to migrate your equipment register?