L3Harris
Decision-making on manufacturing and supply chain forecasting
Palantir
Defence/Industry
Typical Forward Deployed model
Standard case | Useful reference with remaining gaps
Evidence level B
In production
B
Evidence level
L3 Harris: Manufacturing and supply chain forecasting decision-making
Evidence level measures whether a source can be located and reviewed; it does not mean vendor-reported claims were independently audited.
Standard case | Useful reference with remaining gaps
7 / 12
Business context1 / 2
Transformation workflow1 / 2
Technical workflow2 / 2
Human roles & governance1 / 2
Measured outcomes1 / 2
Source traceability1 / 2
Remaining gaps: Business context, Transformation workflow, Human roles & governance, Measured outcomes, Source traceability
Business problem
Managers have no shortage of “what happened” watchboards, and no system to predict risk ahead of time and to give implementable programmes.
Solution
Mapping of manufacturing, supply, cost and delivery data to Ontology and translating risks into proposals for action with prediction/optimization/AIP.
Technical architecture & production workflow
Step 01
Equipment/quality/process/maintenance/supply chain/historical events
→
Step 02
Foundry integrates real-time and historical industry data
→
Step 03
Establishment of equipment, spare parts, orders, processes and constraints
→
Step 04
AIP/project/optimal identification of risks and recommended actions
→
Step 05
Engineer/field personnel confirm and operate
→
Step 06
Implementation results and failure feedback deposition as follow-up model and rule context
Key technology & infrastructure components
FoundryOntologyAIPForecast/optimalManufacturing and supply chain data
Human roles & accountability
The Head of Operations and Engineering is responsible for high-risk decision-making and redeployment of resources.
FDE delivery actions
- Together with the manufacturing and supply chain first-line teams, complete processes to identify nodes that really require decision-making rather than presentation of data
- Collapse decentralized data sources, competencies and business terms into a single, operational Ontology
- Combine business rules, optimization models, LLM and traditional software according to a reliable boundary, instead of letting the LLM operate
- Insert recommendations directly into existing operating workstations and design approvals, rejections, upgrades and write back to Action
- Continue to modify Ontology, rules and automation with operational KPI acceptance and feedback
Reusable delivery patterns
- Let's be clear about the client, the relationship, the state and the action, and then talk about Agent.
- The recommendation must enter the executable stream, otherwise it's just another dashboard.
- High-value deployment is often a combination of data integration + rules/ optimization + AI + Human-in-the-lop
- Continuous rewriting of the results of implementation to build cumulative operational memory
Business outcomes & delivery results
Official clients cited the emphasis on retroactivity towards predictability and agility in decision-making, and public materials did not give uniform quantification of ROI.
Evidence boundaries & verification notes
- Palantir network clearly discloses client objectives and deployment directions; no single financial indicators and specific models are disclosed.
- The current link is the official aggregation entrance, and a deep link or page number that directly locates the case has yet to be added.