Partner Onboarding and Integration

English | 中文

Applies to DecisioWorks v1.4.0

Partner Onboarding and Integration

DecisioWorks gives manufacturers, consultants, integrators, industrial platforms, software partners, and AI Agent developers a shared production-decision capability language. Partners retain customer ownership, domain knowledge, and delivery responsibility; the toolkit supplies reusable capabilities.

Roles

Role	Primary contribution	Relevant capabilities
Manufacturer	scenario, data, rules, objectives, execution review	Scenario Lab, analysis, objectives and rules
Consultant	diagnosis, option comparison, improvement path	templates, baseline/rerun, evidence report
Integrator	ERP/MES/WMS access, deployment, operations	mapping, APIs, standard actions, licensing
Industry software partner	domain UI, workflow, customer application	registry, recipes, adapters
Industrial park/platform	scenario organization, manufacturer outreach, and pilot coordination	Research Edition demonstrations, scenario list, validation framework
AI Agent developer	assisted mapping, configuration, invocation, explanation	AI-oriented docs, standard actions, run evidence

Intake checklist

1. Define the scenario scope, decision frequency, and responsible person.
2. Identify data sources, update methods, confidentiality requirements, and sample data.
3. Describe current planning methods, manual adjustments, and known problems.
4. Specify objectives, structural constraints, shop-floor rules, and evaluation metrics.
5. Record existing systems, deployment conditions, interfaces, and licensing needs.
6. Agree on the validation period, delivery responsibilities, support arrangements, and exit criteria.

Four stages

1. Scenario discovery

Reduce a broad requirement to a decision problem that can be reviewed. Define its business objects, inputs, outputs, and responsibility for evaluating the result.

2. Data and capability preparation

Complete source-data mapping, standard-interface validation, and SolverReady checks. Select existing capabilities or identify the extension points that the scenario needs.

3. Baseline and adjusted validation

Run a baseline, then adjust objectives, rules, or resource settings. Retain the before-and-after comparison and the business review record.

4. Integration and operation

Connect stable capabilities to business systems or partner applications. Establish versioning, access control, monitoring, support, and a process for continued iteration.

Recommended deliverables

Provide a scenario description, mapping table, configuration list, run evidence, result interpretation, known limitations, integration guide, test records, training material, and an iteration backlog. These deliverables should help the manufacturer understand, use, and maintain its decision knowledge.

Continue with Ecosystem Overview and ERP/MES Data Mapping Guide.