Two kinds of partner appear on this page. Delivery partners, the systems integrators who put Lima into production inside their supply-chain and data programs. And technology partners, the planning, ERP and cloud vendors whose systems Lima connects to, with the status of each program stated plainly and dated. Buyers use this page to answer one question: who will deliver this, and does the vendor whose system we depend on know about it?
A global systems integrator has packaged Lima inside its agentic supply-chain offer: the Data Fabric and the Backbone as the data layer, the control tower and governed agents as the delivery. Joint offers cover the 22-day control tower pilot and planning integration into Kinaxis, o9 and Blue Yonder.
The partner's name, logo and the joint offer descriptions appear here with its co-approval.
Mid-tier planning integrators. The firms that implement Kinaxis, o9 and Blue Yonder deliver the data work today as services. The Backbone gives them software to deliver it with: fixed-scope first loads, the nine checks, the reconciliation report and the return to the ERP. The first program cohort is three firms; conversations are under way with two.
Lima's own team. Where no partner is engaged, Lima delivers the fixed-scope offers itself. The software price is the same either way; delivery is quoted as services by whoever delivers.
Built for planning and data integrators with ten to two hundred consultants.
The showcase estate with SAP, Oracle, a warehouse, a WMS and 3PL feeds, ready for demonstrations and training.
Runbooks for each fixed-scope offer: first load, migration conversion, archive and decommission, the 22-day pilot. Checklists, templates, the reconciliation report format.
Two levels: delivery consultant and architect. Certification is by a delivered engagement reviewed by Lima, with the badge dated.
A published margin on the subscription for partner-sourced customers; joint proposals; the partner named on the customer's outcomes page when the customer agrees.
A partner page on this site, joint webinars, and the partner's case tiles on the outcomes page with the customer's approval.
A roadmap briefing each quarter, early access to connectors, and a named contact in engineering.
Governed agents expand what a partner delivers: an agent proposes, a person approves, and the partner configures and tunes both. The agents take work off the customer's team; the partner's services grow with the estate.
A badge appears when a program grants it. Until then the status is written here, with the date it is expected to change.
Lima feeds a planning system; it does not replace one. Each technology page describes the data model the system expects and how Lima loads it.
| System | What Lima does beside it | Page |
|---|---|---|
| Kinaxis Maestro | Builds the linked tables from the ERP, loads them in referential order, returns planned orders to the ERP. | Kinaxis |
| o9 | Validates hierarchies, loads members before measures, returns the agreed forecast as planned independent requirements. | o9 |
| Blue Yonder | Builds SKUs and DFUs from a governed rule, one zero-filled history stream, aligned buckets; reads execution systems live for the control tower. | Blue Yonder |
| SAP IBP | Derives combinations, checks planning-level completeness, loads through the area's channel; states when SAP's own integration is enough. | SAP IBP |
| OMP | Builds recipes, conversions and characteristics from the ERP; keeps changeover matrices as governed master data. | OMP |
| Snowflake · Databricks · Fabric | Lands SAP and Oracle correctly typed, keeps it current, and reads the lakehouse when it feeds planning. | Snowflake · Databricks · Fabric |
Lima's team delivers the fixed-scope offers, at the same software price.
Yes. The program is open; the first engagement is the certification.
A badge appears only when a program grants it. Until then the page says applied, planned or decision pending, with a date.
A demonstration estate, delivery kits, training and a published margin. Three questions, then a call.
