Facilities requests
No cataloged capability or published implementation claim. Start with a bounded outcome and operating context.
Start in Open Flow →Industrial & Field
Prevent work orders from becoming downtime.
These are operational problems Forklift is willing to scope. One flagship has a detailed page; the others enter Open Flow as candidate engagements without implying catalog support.
Maintenance coordination
Design goal: reduce preventable downtime through visible priority, ownership, parts readiness, and verified closeout.
This is a candidate engagement, not a cataloged capability. Scope, evidence, and commercial terms are agreed before work begins.
Review capability →Field workforce planning
No cataloged capability or published implementation claim. Start with a bounded outcome and operating context.
Start in Open Flow →Fleet and dispatch
No cataloged capability or published implementation claim. Start with a bounded outcome and operating context.
Start in Open Flow →Inventory visibility
No cataloged capability or published implementation claim. Start with a bounded outcome and operating context.
Start in Open Flow →1 detailed flagship
A page is published only when its buyer, scope, evidence, data boundary, and engagement mode can be stated specifically.
Existing systems stay authoritative
Assessment and design begin with process evidence or controlled exports. Connectors require separate review and approval.
No authority from marketing copy
A landing-page request creates no production access, budget, approval, or execution authority.