Role 01
Business owner
Training focuses on what problem the platform solves, what the current boundary is, and when the work should move into the next phase.
Implementation & Training
Implementation & Training Notes
Implementation ScopeExecFabric does not only provide a software opening. The current delivery path also includes scoped configuration, role-based training, and handoff support within the agreed project range.
The point is not to walk through pages one by one. The point is to explain scope, onboarding, usage, acceptance, and support boundaries clearly in one place.
For most customers, four questions matter first: what the implementation steps are, which roles need training, which notes are handed over, and where ongoing support stops.
Scope alignmentDeployment setupRole-based trainingGo-live support
EXECFABRIC // IMPLEMENTATIONDOC 11
const implementationSteps = ['scope', 'deploy', 'onboard', 'accept']const trainingTargets = ['owner', 'tenant_admin', 'users', 'it_ops']const supportWindow = 'workday_support'
TRAIN THE RIGHT ROLE, NOT EVERYONE AT ONCE
Implementation Steps
Standard implementation steps
| Phase | What happens | Current focus |
|---|---|---|
| 01. Scope confirmation | Confirm the core scenario, the first capability batch, the delivery boundary, and the out-of-scope items | Keep phase one small and real instead of opening with an oversized platform story |
| 02. Environment preparation | Decide whether the project is team edition, lightweight private deployment, or standard private deployment, then prepare access entries, accounts, and deployment conditions | Clarify the deployment mode and delivery mode early instead of mixing them together |
| 03. Capability onboarding | Bring in the customer's existing scripts, flows, or result chains and configure permissions plus execution entries | Run the smallest closed loop first, then consider second-stage expansion |
| 04. Joint testing and acceptance | Test the key chains together, align the acceptance items, and close issues that are inside the agreed delivery range | Make sure the customer can say it is usable, understandable, and sustainable after go-live |
| 05. Training and go-live | Train by role, hand over notes, and explain support boundaries plus the future update path | Go-live is not the end. It is the point where sustained usage begins |
Role 02
Tenant administrator
Training focuses on how to log in, where capabilities are visible, where execution records are visible, and how to submit update or expansion requests.
Role 03
General users
Training focuses on how to trigger capabilities through pages or the intelligent assistant, view results, upload files, and download output artifacts.
Role 04
Client IT / operations
For private deployment, training focuses on the deployment form, runtime requirements, backup and recovery, and the local environment boundary.
Standard Handoff
Current standard handoff items
- Platform access entry
- Initial accounts and initialization method
- Customer delivery notes
- Customer usage notes
- Customer-facing capability notes
- Customer script hot-update notes
- If included in the project, notes for file upload and result download chains
- If included in the project, the customer notice entry or related documents
Client Preparation
What is useful to prepare before implementation
- Core scenario list
- Scripts or flows to onboard first
- The roles that should attend training
- If independent deployment is needed, server and network conditions confirmed in advance
Support Boundary
Current support boundary
Included by default
- Troubleshooting for issues inside the delivered scope
- Answers to baseline usage questions
- A small amount of script updates or configuration help
- Platform runtime assistance
Not included by default
- New feature development
- Large-scale page redesign
- Deep third-party system integration
- Resident service, high-SLA operations, or long-duration embedded support
If baseline support is included, the current default assumption is workdays `09:00-18:00` with ticket, email, or WeCom as the main channels. Higher response levels or longer support windows should be agreed separately.
Next Read
Continue with delivery boundaries, deployment options, and service packages
If you are already moving into a formal discussion, the next useful step is to review deliverables, deployment mode, and cooperation path together.