Orders and movements
Provide exports for the same population: order and execution identifiers, completion dates, material movements, posting dates, quantities and units. Optional grouping and values need their own agreed meaning.
METRICZ / BY VALERON
SAP maintenance analytics from Excel and CSV exports
Investigate maintenance material issues, reversals and recurring return patterns. Metricz takes uploaded exports through validation and analysis to findings you can trace, review and report.
Start with your exported data. The export structure, movement meanings and source coverage must be configured and validated for your dataset. Metricz’s current focus is material analysis and audit workflows.
START WITH A MAINTENANCE QUESTION
Which material patterns deserve a closer look?
Repeated reversals
Does the same material show high returns across several adequately sampled years?
Changing usage
Are issue and reversal quantities changing, or is one unusual period driving the result?
Evidence to investigate
Which orders and movements explain the pattern, and what needs to be checked before acting?
UPLOAD FIRST
From an export to a reviewable finding.
Manual Excel/CSV upload is a permanent core capability. Keep control of the source files, interpretation and analysis period without connecting Metricz to SAP.
01
SAP export
Prepare orders and material movements for the same population.
02
Excel/CSV upload
Load values-only XLSX or supported UTF-8 CSV files.
03
Sheet/header inspection
Select the dataset and inspect its columns and rows.
04
Mapping
Map fields and explicitly define movement and date interpretation.
05
Validation
Review errors, exceptions and record reconciliation.
06
Normalised data
Use consistent order and movement records with source references.
07
Analysis
Calculate quantities, rates and eligible historical trends.
08
Findings
Identify explainable material patterns worth reviewing.
09
Investigation
Follow contributing transactions back to their source.
10
Review/action
Record the decision, evidence, owner and next action.
11
Report
Export the scoped findings and review evidence to Excel.
Save reviewed mappings for recurring export structures. Changes to ordered headers require review. Suggestions match column names; they do not automatically interpret SAP semantics.
MATERIAL BEHAVIOUR
Read the quantities in context.
Compare issued, reversed and net quantities, annual return percentages and eligible twelve-month trailing rates. Findings retain sample context and reasons, so sparse history and incomplete periods remain visible.
The period return rate uses total reversed quantity divided by total issued quantity. A missing denominator or ineligible rolling window is shown as unavailable.
A review opportunity needs interpretation.
- Net quantities are accounting quantities, not proof of physical consumption.
- Reversals do not automatically mean unused parts or physical waste.
- Associated reversal value is not verified savings.
- Check posting corrections, date boundaries and maintenance context before recommending a change.
INVESTIGATION & EVIDENCE
Follow the finding back to its source.
Inspect the orders and material movements contributing to a finding. File, sheet and row references keep the calculation connected to the uploaded source, while the finding explains its pattern, thresholds and limitations.
Record decisions and next actions.
Retain review notes, supporting evidence, a disposition and follow-up actions with owners and dates. Closure requires the review details and completion of outstanding actions.
Reviews persist in the local workspace. Reviewer and owner names are recorded labels; they are not authenticated enterprise approvals or authority to change SAP data.
Bring an Excel review pack to the discussion.
Export the selected findings, review register, actions, historical and trailing analysis, order and movement evidence, data quality and methodology. Reports use the saved analytical results and current review scope.
PREPARING SOURCE DATA
Agree the meaning before trusting the result.
Explicit interpretation
Confirm issue and reversal codes, quantity signs, date formats, join keys and source coverage. SAP movement semantics must be configured and validated against representative examples.
Validation and reconciliation
Inspect missing, duplicate, invalid and unmatched records. Blocking errors prevent analysis; excluded records and warnings remain explained and traceable.
Practical file scope
Use values-only XLSX or supported UTF-8 CSV. Current limits are 10 MB and 100,000 data rows per file, with up to 20 sheets. Processing is bounded; formats and real data volumes are reviewed during setup.
CURRENT SCOPE & DEPLOYMENT
A guided material-audit workflow.
Metricz currently runs as a single-machine local review workspace. Real SAP export mappings and transaction interpretation require validation. A walkthrough establishes the maintenance question, available data and intended review process.
It does not connect to or write back to SAP, and is not offered here as a hosted enterprise service. Task-list effectiveness, planned-versus-actual work-order analysis and comprehensive SAP master-data auditing are outside the current scope.
Meet the company behind Metricz or explore Valeron’s operational solutions.
Questions about Metricz and SAP exports
Does Metricz connect directly to SAP?
No. Metricz analyses uploaded Excel or CSV exports. It does not provide a direct SAP connection, OData, SAP APIs, SAP authentication or SAP write-back. Manual upload is a deliberate, permanent core workflow.
Which source data do I need?
The current material audit uses maintenance orders and material movements for the same population and period. Supply explicit identifiers, dates, quantities, units and movement meanings. Export structure, relationships and interpretation must be validated for your dataset; universal SAP export compatibility is not assumed.
Can mappings be reused?
Yes. Save reviewed mappings for exports with the same ordered headers. Changed structures require explicit review. Column suggestions do not infer SAP movement semantics; issue/reversal codes, signs and date interpretation must be configured and checked.
How are return percentages and rolling trends calculated?
Return percentage is reversed quantity divided by issued quantity, multiplied by 100. Whole-period rates use summed quantities, not an average of annual percentages. A zero denominator is unavailable. Twelve-month trailing analysis requires complete window coverage and a sufficient sample; ineligible windows show gaps and reasons.
Does a high reversal value represent savings?
No. Reversals are transaction classifications, not proof of unused physical parts or waste. Net quantities are accounting quantities. Reversal values describe supplied transaction values, not verified savings. Findings need investigation of posting, timing and maintenance context.
Can I trace a finding to the original export?
Yes. Findings link to contributing orders and movements, with file, sheet and source-row references. Review decisions, selected evidence and actions can be retained alongside the finding and included in an Excel review pack.
Does Metricz analyse task-list effectiveness or planned versus actual work orders?
Not currently. The implemented scope is maintenance material analysis and audit workflows. Task-list comparisons, work-order plan-versus-actual analysis, BOM recommendations and comprehensive SAP maintenance master-data auditing are outside the current scope.
Is Metricz available as a hosted enterprise service?
The current application is a single-machine local review workspace. It does not offer multi-tenant production SaaS, SSO or authenticated enterprise approvals. We discuss intended users, data handling and deployment requirements during a guided walkthrough.
GUIDED WALKTHROUGH
Bring the maintenance question. Follow the evidence.
See the workflow with synthetic example data and discuss which exports and interpretation your review would require. Any sample-data review is arranged separately.