Getting Started
What is RavenLI?
RavenLI is a software licence compliance analysis engine. Upload your raw export files from IBM ILMT, Microsoft SCCM, Oracle LMS, SAP LMDB, VMware vCenter, or Adobe Admin Console, and RavenLI instantly cleans the data, classifies every product, and runs 505 compliance rules to identify licensing risks, audit exposure, and cost-saving opportunities. All processing happens in your browser — your data never leaves your machine.
Supported Publishers
RavenLI supports the 6 most commonly audited software publishers, with publisher-specific licensing engines and compliance rules for each.
- ILMT Software Inventory (.csv)
- PVU Sub-Capacity Report (.csv)
- Computer List (.csv)
- Scan Status (.csv)
- SCCM / Intune export (.csv, .xlsx)
- LMS collection script output (.csv, .xlsx)
- LMDB export (.csv, .xlsx)
- vCenter export (.csv)
- Admin Console export (.csv)
Rule Coverage
80
IBM
COMP-001 to COMP-080
90
Microsoft
MS-001 to MS-090
80
Oracle
ORA-001 to ORA-080
50
SAP
SAP-001 to SAP-050
50
VMware
VMW-001 to VMW-050
30
Adobe
ADO-001 to ADO-030
How to Export Your Files
IBMILMT Export
- Log into the IBM License Metric Tool web console.
- Navigate to Reports → All Reports.
- Select Software Classification (or “All IBM Metrics”).
- Set the reporting period (recommend: last 90 days minimum).
- Click Export → CSV.
- For PVU Sub-Capacity: navigate to Reports → PVU Sub-Capacity and export similarly.
- For Computer List: navigate to Reports → Computers → All Computers and export.
- Upload all exported CSV files to RavenLI simultaneously for cross-file analysis.
MicrosoftSCCM / Intune Export
- Open the SCCM console (Configuration Manager).
- Navigate to Monitoring → Reporting → Reports.
- Under Software - Companies and Products, select a software inventory report.
- Run the report and click Export → CSV or Excel.
- Ensure the export includes: Device Name, Product Name, Product Version, Publisher, Install Date.
- For Intune: use the Discovered Apps report in the Intune admin centre.
OracleLMS Export
Run the Oracle LMS Collection Tool on each database server. The tool generates a CSV output with host details, product names, processor counts, and core counts. Upload the resulting CSV directly to RavenLI.
SAPLMDB Export
Export your SAP licence data from the License Administration Workbench (LAW) or System Measurement transaction (USMM). The export should include System ID, Product Name, License Type, Quantity, and Valid From/To dates.
VMwarevCenter Export
In the vSphere Client, navigate to Menu → Hosts and Clusters. Select the datacenter or cluster, then Export → Export List as CSV. Ensure the export includes VM Name, Host, Guest OS, CPU Count, Core Count, and Power State.
AdobeAdmin Console Export
In the Adobe Admin Console, go to Users → Users. Click the Export users list to CSV button. The export includes Email, Product Profile, Identity Type, Status, and Last Login.
Understanding Your Results
Reliability Score
The reliability score (0-100) measures the quality and trustworthiness of your data. It is calculated based on duplicate rows, missing fields, and data inconsistencies.
80-100
Reliable
Data is clean and ready for analysis. Minimal issues found.
50-79
Review Recommended
Some data quality issues found. Review the cleaning log for details.
0-49
Action Required
Significant data quality issues. The export may be incomplete or corrupted.
Compliance Score (IBM)
The compliance score (0-100) measures licensing risk based on triggered compliance rules. Each rule severity deducts from the score: Critical (-15, cap -60), High (-7, cap -35), Medium (-3, cap -15), Low (-1, cap -5). A score of 100 means all compliance rules passed.
80-100: Audit Ready
Low audit risk. Minor findings only.
50-79: At Risk
Material compliance gaps. Remediate before an audit.
0-49: Compliance Gap
Significant licence shortfalls detected. Urgent action needed.
Cleaning Log
The cleaning log shows every action taken on your data:
Compliance Rule Naming
Each compliance rule has a unique identifier with a publisher prefix:
68 rules covering PVU, sub-capacity, ILMT, product classification, Cloud Paks, virtualisation, audit evidence
80 rules covering SQL Server, Windows Server, M365, EA True-Up, Azure Hybrid Benefit, Power Platform, Defender, Teams Phone, Fabric, Intune, Windows upgrade rights
20 rules covering VMware soft partition, Core Factor, NUP minimum, SE2 limits, Java SE post-2023
20 rules covering indirect access, user requalification, Digital Access, HANA memory, ECC end-of-life
20 rules covering Broadcom transition, socket-to-core migration, Oracle/IBM/SAP cross-vendor risk
15 rules covering ghost licences, anniversary dates, CCE overlap, personal accounts, Firefly AI
5 rules detecting risks visible only when multiple publisher datasets are combined
Cross-Publisher Risks (XPUB)
XPUB rules detect licensing risks that are only visible when data from multiple publishers is analysed together. These are the highest-value insights because organisations almost never cross-reference their own licence data between publishers.
Multi-File Upload
How It Works
- Drag and drop multiple files onto the upload zone (or click to browse and select multiple).
- RavenLI auto-detects the publisher for each file from its column headers.
- Each file shows a status badge: publisher name, confidence score, and file size.
- Click “Clean N files” to process all files.
- Results show a consolidated report with combined score, per-publisher sections, and cross-publisher risks.
- Download all cleaned files as a single ZIP or individually.
What Cross-Publisher Analysis Detects
IBM PVU products on VMware hosts — ILMT sub-capacity requires VMware Scanner configuration
Oracle DB on VMware — soft partition, full ESXi host cores must be licensed
SAP indirect access via Salesforce, ServiceNow, Power BI, RPA tools detected in other datasets
SQL Server on VMware — Software Assurance required for Licence Mobility (vMotion)
Hosts appearing in 3+ datasets — licensing complexity multiplier, each publisher's rules apply independently
Recommended File Combinations
For maximum insight, upload these combinations together:
IBM Full Audit Prep
ILMT Software Inventory + PVU Sub-Capacity + Computer List + Scan Status
Complete IBM sub-capacity defence evidence with cross-file validation.
VMware + Vendor Stack
VMware vCenter + IBM ILMT + Oracle LMS + Microsoft SCCM
Detects all virtualisation licensing risks: IBM PVU, Oracle soft partition, SQL SA.
SAP Indirect Access Audit
SAP LMDB + Microsoft SCCM (shows Power BI, ServiceNow) + any CRM export
Maps indirect access vectors from integration products in other datasets.
Full Estate Review
All 6 publishers uploaded together
Maximum cross-publisher risk detection. Recommended before any licence true-up.
Frequently Asked Questions
What does RavenLI NOT do?
RavenLI does not connect to your systems, does not install agents, and does not require network access to your infrastructure. It only reads the export files you upload. It is not a SAM tool, CMDB, or discovery platform — it is a compliance analysis engine that works with data you already have.
How is my data protected?
All files are processed entirely in your browser using client-side JavaScript. No data is uploaded to RavenLI servers. The application runs on Vercel's edge network but the processing engine is 100% client-side. Your licence data never leaves your machine. For Enterprise deployments, on-premise installation is available.
Can I upload real production data?
Yes. Since all processing happens in your browser (Layer 1), your production ILMT, SCCM, LMS, LMDB, vCenter, and Admin Console exports are safe to upload. No data is transmitted to any server. The files exist only in your browser's memory during the session and are discarded when you close the tab.
How often should I run an analysis?
We recommend running an analysis quarterly at minimum, and always before any vendor audit notification. For IBM, run it whenever you generate new ILMT reports (IBM requires quarterly ILMT reporting for sub-capacity defence). For Oracle, run it before any LMS audit engagement. For SAP, run it before contract renewals or S&S negotiations.
What is the difference between reliability score and compliance score?
The reliability score (0-100) measures data quality: duplicates, missing fields, normalisation issues. A high reliability score means the data is clean and trustworthy. The compliance score (IBM only, currently) measures licensing risk: how many compliance rules were triggered and at what severity. A high compliance score means fewer audit risks. You can have clean data (high reliability) that still has compliance issues (low compliance), or messy data (low reliability) that happens to be compliant.
Ready to try it?
Upload your first file on the homepage — no account required.