Before the first production order of a new product, a launch checklist of 100 to 300 items has to be true: material and long-lead orders, supplier and OSAT qualification, test program release, part numbers and master data.
Twelve weeks before the launch of the new controller board 7741-Y, the daily readiness scan ran at 06:00. The scorecard shows 212 of 240 items complete. Overnight Juno created the 14 sales part numbers within the naming rule and the ERP returned each item number; it found that the work definition at plant 1210 lacks a resource for the new test step, and that the long-lead flash memory order covers seven of the first twelve weeks of the ramp plan.
P. Sharma approves the master-data fix from her queue in one click, and the ERP confirms the record. D. Okafor approves the top-up order with Acme Components GmbH, drafted with the coverage gap as its basis. The test program release candidate waits for the quality engineer’s signature, with a clock of five days.
At the ramp gate review J. Ridley sees the three open exceptions with their owners and clocks, and the 25 routine items inside their clocks, on one page read from eight systems. The decision to go or hold at the gate is his and the programme manager’s. showcase estate
The ERP vendors ship readiness agents, and the descriptions are theirs. Oracle’s Production Readiness Workspace, an agentic application, checks material availability, master-data gaps, work definitions and resources, generates prioritised corrective actions, and its Product Updates Advisor watches engineering changes that hit manufacturing; a manufacturing engineer approves each correction (Oracle, 29 June 2026; Oracle documentation, 28 August 2026) 7, 8.
SAP’s Joule Production Planning and Operations Agent automates prerequisite checks on material, capacity and scheduling before releasing production orders, recommends workarounds or releases orders at once, planned for the first quarter of 2026 (SAP, 7 October 2025) 3. Oracle’s Supplier Qualification Workspace turns qualification into a guided, risk-based process, and SAP’s Supplier Onboarding Agent validates data and handles escalations (Oracle, 29 June 2026; SAP, 7 October 2025) 7, 3. Planning suites offer like-item forecasting and launch execution for products that lack sales history (o9 Solutions, checked 23 September 2026) 54. Customer results for these agents have yet to be published.
The delay pain is measured. 90% of engineering leaders delay product launches and 10% launch every product on time (CoLab, 26 July 2024, 250 respondents) 30; 75% of chip projects run behind schedule (Semiconductor Engineering, 27 March 2025) 31. Over 75% of engineering and R&D executives expect AI to deliver 20% to 50% gains in productivity, time to market and cost (Capgemini Research Institute, 13 November 2025) 47. 33% of manufacturers cite faster time to market as the challenge driving AI investment (Aras, 20 March 2025, 656 executives) 17. Gartner predicts 40% of enterprise applications will carry task-specific agents by the end of 2026 (Gartner, 26 August 2025) 51.
The readiness list itself spans eight systems: items, bills of materials and work definitions in two ERPs, the product lifecycle management (PLM) project, the planning suite, the OSAT portal, the quality system, test data management and the supplier portal. Each vendor’s agent checks its own system. The platform’s part would be one scorecard across all of them, with the routine items closed within rules and every gap owned.
A programme manager for new product introduction (NPI) keeps a launch checklist of 100 to 300 items in a spreadsheet or a PLM project and chases owners at a weekly readiness meeting. A supply planner checks material availability and long-lead orders line by line. A buyer confirms supplier qualification and OSAT capacity by e-mail. A quality engineer confirms the qualification report, the test program release and first-article approvals.
A master-data steward creates part numbers, bills of materials, work definitions, prices and classifications in each ERP by hand. Documentation releases the datasheet. Gaps surface at the first production order and cost days each. Seven roles, eight systems and readiness cycles of several weeks; in the market’s figures, 10% of companies launch every product on time (CoLab, 26 July 2024) 30.
Item, bill of materials, purchase order and supplier are objects the ontology holds already; checklist item, milestone, work definition, qualification report and test program release would extend it. The six stages below say what would be registered from eight systems, which items the rules may close on their own, and which people sign before the gate.
| Item | Source checked | Status | Owner | Clock |
|---|---|---|---|---|
| Sales part numbers (14) | SAP S/4HANA item master | Created within rules · 06:05 | P. Sharma reviews | closed |
| Work definition · plant 1210 · new test step | Oracle Fusion work definitions | Resource missing · fix drafted | Manufacturing engineer | 2 days |
| Flash memory · long-lead order | Purchase orders · supplier portal | Covers 7 of 12 weeks · top-up drafted, $118,000 | D. Okafor | 3 days |
| OSAT capacity commitment | OSAT portal | Confirmed for weeks 1 to 12 | Buyer | closed |
| Test program release | Test data management | Release candidate 3 · signature pending | Quality engineer | 5 days |
| Qualification report | Quality management system | Signed 12 September | Quality engineer | closed |
| 234 more items | eight systems | 209 complete · 25 open inside their clocks | various |
The scorecard J. Ridley would see at the ramp gate: every item with the source that proves it, the three exceptions with owners and clocks. Showcase estate; the roles are designed, yet to be built.
The market runs routine corrections within rules with exceptions surfaced to people: one ERP vendor’s agentic applications progress routine work within guardrails and the other’s agent releases orders when checks pass (2025 to 2026) 7, 3. The blueprint designs the write-back roles here at A3 with the steward and the buyer taking exceptions, and spreads the fourteen roles across the gamut: part number and SKU creation at A4, the checklist and the scorecard at A3, ramp planning, long-lead commitment and OSAT readiness at A2, the gate review at A1, and the production release decision at A0, because the release is a signature.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Every readiness item for a product in ramp is proven from its source each day, routine gaps closed within rules and every other gap owned before the ramp gate | The NPI programme manager, in a sentence | New version |
| Data scope | SAP S/4HANA and Oracle Fusion items, BOM, work definitions, purchase and production orders; the PLM checklist; quality records; the OSAT and supplier portals; test data management | A. Novak, data lead | New version |
| Rules | The readiness policy and its planning table: check daily from twelve weeks out; create part numbers within the naming rule; draft long-lead orders under the ramp plan; route the rest | The programme manager with the Planner Agent | New version, simulated first |
| Trigger | 06:00 daily from twelve weeks before launch; each gate milestone; an engineering change on a product in ramp; a work order for a new item | The programme manager | At once |
| Actions permitted | Update a checklist item with evidence · create a part number or SKU · draft a work-definition correction · draft a long-lead order · route a gap with a clock · publish the scorecard | The programme manager, owner | New version |
| Limits | Long-lead orders above $25,000 go to D. Okafor · part numbers only from the naming rule, 50 a day · a work-definition change always waits for the manufacturing engineer · confidence floor 0.90 on a coverage check | The programme manager, J. Harrison and P. Sharma | New version |
| Escalation | An item that blocks the first work order, to the programme manager at once · a clock that runs out, to the owner’s manager · a failed write-back, to P. Sharma | The programme manager | At once |
| Level | A3 Delegated with P. Sharma and D. Okafor on exceptions; go or hold at the gate stays with J. Ridley and the programme manager at A0 | J. Ridley, supply chain director | Up on evidence, down in one step |
| Feedback | Every approved correction, edited order and gap that recurred is recorded and used | Always on | Fixed |
Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.
Additional capability in Idea-to-Market lists the rest of the map for this chain.
| Measure |
|---|
| Launches on time, baseline: 10% of companies launch every product on time (CoLab, 2024) |
| Projects behind schedule, baseline 75% (Wilson Research Group 2024 study) |
| Checklist items closed before the gate |
| Master-data defects found before the first work order |
| First-pass production order release rate |
| Time from qualification complete to production release |
| Expedite spend during ramp |
Baseline checklist items closed before the gate first: the last launch’s checklist gives the number in an afternoon, and it is the one the gate review already argues about. Master-data defects found before the first work order follows, because it is what the A4 part-number role is judged on. Launches on time and expedite spend during ramp read over a year of launches.
Part numbers and SKUs that follow the naming rule, and checklist updates with their evidence, would run within the rule at A3. Work-definition changes, long-lead orders above $25,000 and every other gap wait for a named person.
The scorecard at the gate: every item with the record that proves it, the open exceptions with owners and clocks, and the coverage of the ramp plan week by week. The decision stays with J. Ridley and the programme manager.
Gaps that surface after the gate, at the first production order, are recorded against the launch. Juno proposes them as new checklist items and rules, and the programme manager approves them as a new version for the next product.
The product is released and its first orders arrive from the customers who evaluated samples. How does the same machinery carry an order from intake to cash?
Order intake, cash application, collections and disputes: the chain where the market’s evidence is deepest.
Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.