Executive Summary
The Long Lead Item Pump as an Example
Creating a new complex material, such as a long-lead engineered pump, is not simply about entering data in an ERP like SAP in an asset-intensive industry. It is a multi-month, collaborative engineering and procurement process.
Traditional ERPs such as SAP work well once the material master is created; however, they do not provide a significant amount of support during the early, messy, uncertain, and ambiguous “0 → 1” phase before the material exists anywhere.
A MIMS Platform addresses this need by serving as an intelligence or governance layer that:
- Proactively manages uncertainty
- Captures technical knowledge
- Prevents duplication of work
- Ensures compliance with governance
- before a material reaches any ERP system.
ERPs are the trusted systems of records for transactional information related to materials.
MIMS provides the intelligence necessary for material creation.
This post is intended to provide factual evidence supporting why MIMS technology is complementary to but not redundant with a traditional ERP system; the long-lead pump example will provide practical context.
The Business Problem – Long Lead Material Complexity
Modern Facilities rely on thousands of complicated assets. A pump used in a new processing line is a lot more than just an item in the catalog.
A pump has the following requirements:
- Detailed engineering specifications
- Vendor evaluations and certifications
- Long manufacturing lead times (3-18 months)
- High risk of operational performance being impaired if the pump is improperly specified.
When fragmented, the creation of material presents serious challenges to the organization.
Ambiguous Definitions
Engineering has all the information it needs on flow rates and pressures, service conditions, but does not have the final seal type, metallurgy, or vendor. ERP systems require a completed Master Data record before it can be used. Inputting incomplete or inaccurate data into an ERP system results in:
- Rework
- Incorrect masters
- Bad downstream decisions
Scattered Technical Content
All of the critical documentation (i.e., datasheets, 3D models, O&M manuals, and certified documentation) that goes into a project tends to be scattered between:
- File shares
- PLM systems
- ERP Material Screens—For the most part, material screens only contain basic attributes of the item, while the technical details are usually found in either the datasheet or instruction manuals.
Duplicate Material Masters
Without a strong pre-creation check process in place:
- Equivalent pumps are created with different Master Codes
- The value of inventory is hidden in duplicate items
- Studies have shown that up to 15 – 20% of your inventory value remains tied up in duplicated or incorrectly classified parts.
Slow, Opaque Processes
Requests move through the email or spreadsheet system:
- No common view to see where the request for a component is at in the process
- No ability to track all of the decisions that have been made
- No record of the reasons for the design decision to be approved
The ERP system is not set up to accommodate this phase of the design process.
Why ERP Alone Is Not Enough
An ERP System is optimized for a “1 → N” scenario:
- Purchasing
- Inventory
- BOMs
- Financial Control
However, it is not designed for use and optimization in a “0 → 1” method.
- Exploring
- Comparing
- Capturing Knowledge
- Managing Incomplete Data
Most industry articles and publications state that a best practice is to use your ERP as a system of record and to have some form of intelligence around the ERP that will help with early phase complexities.
MIMS is an example of intelligence for materials.
Case Study: Long lead pump for Plant A
Scenario
Plant A has a new cooling-water loop that requires a custom centrifugal pump.
- Flow: 450 m³/hr
- Head: 9 bar
- Temperature: 80°C
- Standards: API compliant
- Lead time: 9–12 months
- Financial risk of downtime: $20k–$100k per hour
It will take at least 6 months from the time of the initial request to create an ERP entry for this new pump.
The Material Lifecycle: 0 → 1 → N
- Initial request (0) – Engineering logs a need for a “9 bar pump required for Unit X,” but does not haveall ofthe details fully defined yet, as they are still preliminary.
- Enrichment (0 → 1)
Teams use MIMS to:
- Search for existing pumps from past and current projects
- Attach vendor datasheets, drawings, and manuals to the pump record
- Use AI to extract data about the existing pump (flow curves, materials of construction, power ratings, etc.)
- Compare the found pumps to previous examples from the history of the company; not just the ERP masters
- Governance Review
Engineering, procurement, and reliability teams will approve:
- Review specifications
- The equivalent customers for existing pumps
- Standardization of the naming convention and classifications
- The duplicate determination with all company locations
An example of the duplicate determination query would be to “find all pumps with a flow between 450 m³/hr and 8 – 10 bar using only stainless steel as an example of the material of construction.”
- Approval Gate (1)
The master data stewards will approve:
- A confirmation that no near-duplicate pumps exist
- Confirmation that all mandatory attributes for the new pump are complete
- All associated documents have been attached to the new material
- The proper classification and criticality have been assigned to the new pump
Only after this is complete is the new pump considered ERP-ready.
- ERP Creation (N)
MIMS will provide the approved payload to ERP.
The ERP will establish the Official Material Number (e.g., 100123).
The ERP now owns:
- Inventory
- Transactions
- Usage of the BOM.
MIMS retains:
- Knowledge
- Documentation
- Audit trails,
- A rationale
Reason the separation is important
The ERP system holds the final “what”. The MIMS system holds the final “why” and “how”. This distinction prevents unnecessary failure modes and reductions in costs.
The Real Cost of Duplication
The example of failure
Two plants independently create the same pump:
- Same specs
- Same vendor
- Different ERP codes
What happens as a result?
- Duplicate inventory
- Separate RFS
- No volume discounts
Worse:
One pump has a critical status, while the other does not. If either of these two pumps fails, it will cost the company 3 days of downtime on one, versus 3 weeks on the other; thus, losing over $3 million in production costs. ($25,000/hour).
MIMS vs ERP capability Comparison
| Capability
|
MIMS | ERP |
| Primary Role | Materials intake, enrichment, governance | System Of Record, Transactions |
| Data Ownership | Candidate Records, Docs, AI Metadata | Final Master Data, Inventory |
| Data Model | Flexible, Evolving | Fixed, Finalized |
| Technical Documents | Complete Repository, Indexed | Minimal Attachments |
| Search | Semantic, A.I. Driven | Keyword Based |
| Governance | Multi-stage, content-aware | Validation only |
| Duplication control | Proactive detection | Reactive cleanup |
| Auditability | Full lifecycle history | Final state only |
MIMS Is Intelligence, ERP is Execution.
Architecture: How MIMS and ERP Function Together
Fundamental Concepts
- All 0→1 tasks in MIMS take place before integration with ERP
- Approval must occur before data can be added to ERP; only approved data will be sent to ERP
- Definitive Ownership:
- Technical Knowledge belongs with MIMS
- Transactions belong with ERP
Synchronization
- MIMS sends all approved data to ERP
- ERP sends back an official material number
- MIMS locks the fields to the master data and records a history of each field being updated
This maintains the ERP’s ability to be lean and reliable by reducing excess activity across systems.
Governance Policies That Make It Stick
This should include the following:
- Approval gates for Engineering, Procurement, MDM, and Maintenance.
- Change Controls through the Management internal Standards (MIMS), even after ERP creation.
- Duplicate rulesestablishedon a similarity in specifications as opposed to just name comparison.
- Clear boundaries for ownership of data.
- Standard taxonomies used for classification and search.
Enforcement of Governance occurs before ERP, and NOT after.
Effect of Business Using MIMS
Businesses that are using MIMS see:
- 10% to 20% in reducing excess inventory
- Faster manufacturing of long lead materials
- Reducing the necessity to backorder
- Improved uptime and operating reliability
- Reduced duplication of business masters within an ERP System
- Increased productivity through AI search engines
In the example of the pump:
- Prevented duplicate pump codes
- Maintaining accurate criticality ranking
- Retaining all technical context for the product line
- Allowing for the reuse of products in other manufacturing facilities.
Final Thoughts
A Material Intelligence and Governance platform is not an ERP.
It is the missing layer that:
- Simplifies complexity
- Gathers engineering information
- Stamps out duplication
- Keeps the ERP intact
ERP remains the system of record.
MIMS becomes the system of intelligence.
With nearly two decades of experience in engineering, I bring deep expertise across both EPC (Engineering, Procurement, and Construction) and product-based OEM environments. My core strengths lie in engineering standardization, process optimization, and technical leadership. I have consistently driven excellence through the development and implementation of robust engineering frameworks, delivering value across global industrial projects and complex product lifecycles.
