SYSE.2:5.2 - Manufacturer’s ERP-enabled planning change

The manufacturer keeps PlanningSystem-P1 as an intended System referent in its project decision; actual System identity remains unestablished. Actual person Systems Planner-A and Planner-B perform PlanningWork-PW1. They use actual deployed software runtime ERP-Runtime-E3 and demand, capacity, material, and production-order records as resources and evidence. The records are epistemes; PlanningAPI-PA2 and the user interface are separately identified interfaces.

The linked use claim says that Planner-A and Planner-B would revise production commitments during PlanningWork-PW1 using current records and ERP-Runtime-E3. The system-concept claim describes a possible future organization in which these actual Systems, records, interfaces, and planning Methods could satisfy a separately tested A.1 System criterion. Data currentness and interface latency are the main uncertainties. The ERP vendor’s product project can instead select ERP-Runtime-E3 or its product referent for its own decision. Installation completion, an organization chart, and user acceptance establish neither the manufacturer’s production effect nor the intended composite PlanningSystem-P1.