A.2.2:6.2 Software service in operations (structural, cyber-physical)

Preface node heading:a-2-2-6-2-software-service-in-operations-structural-cyber-physical:2565

What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

Content

  • Holder: PlannerService_v4 (deployed system).
  • Task family: job‑shop schedule generation per JS_Schedule_v4 MethodDescription.
  • WorkScope: 50–500 jobs; 5–40 machines; hard deadlines only; network latency ≤ 20 ms.
  • Measures: schedule completion within 0.95 of theoretical optimum (benchmark set), 98 % on‑time delivery in simulation.
  • Context: PlantScheduling_2025.
  • Use: Steps that “require ScheduleGeneration capability ≥ 0.90 optimality” will only pass if the holder’s capability meets or exceeds that bound.

Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)