PlatformImplementation Factory
Implementation Factory
CourageMFG implements itself. Then it continues to improve your processes and the software. Each change has a target, and each result is measured.
- LiveImprovement projects and product changes
- NextImplementation projects
- PlannedTemplates and best practices
Seven steps, from an issue to a measured result.
Each project goes through the same seven steps. Step 7 starts the next project.
- 01
Identify
Find issues in live data, KPIs, chat and user reports.
- 02
Define
Write the request: the measure, the current value and the target.
A person approves the request.
- 03
Design
Design the process, the setup and the data. List the tasks.
A person approves the design.
- 04
Build
AI and people do the tasks in a test copy.
- 05
Test
Test with past transactions.
A person approves each change.
- 06
Deploy
Put the approved changes live. Keep a rollback point.
A person approves the deployment.
- 07
Measure
Measure the result at 7, 30 and 90 days after go-live.
Step 7 starts the next project
One company database. All seven steps use it.
- Business Central records
- CourageMFG records
- Event log
- Projects and results
AI prepares the work. People make the decisions.
Each project has work for AI and decisions for people. The product keeps the two apart.
AI
Prepares the work
- Finds issues in live data, KPIs, chat and user reports.
- Writes the request and the design.
- Does tasks in a test copy.
- Runs the tests.
People
Make the decisions
- Approve the request.
- Approve the design.
- Approve each change. The change type sets who approves.
- Approve the deployment.
- The AI never approves its own work.
- The person who did a task cannot approve it.
Three types of project.
All three use the same seven steps.
Implementation project
NextA new customer starts to use CourageMFG. CourageMFG connects to Business Central and is set up in a test copy. The first area goes live in week one.
Improvement project
LiveA company that uses CourageMFG improves a process. The request has a measure, a current value and a target.
Product change
LiveA change to the CourageMFG software. It needs a code review and passed tests before deployment.
Each project makes the next one better.
- The go-live values of an implementation project become the start values for improvement.Next
- A change that works at one customer goes into the template for the next customer, when the customers agree.Planned
Safe by design.
The rules are part of the product. They are not a policy document.
- Use a test copy
All work starts in a copy of the database or the code. It never starts in the live system.
- Test with past transactions
Each change is tested with past transactions. The test compares the result with what really happened.
- Approvals by change type
The change type sets who approves.
Change type Approval Report No approval. A report changes no data. Data correction One owner: the owner of the record. Setup change One owner: the owner of the area. Document change Document control. Automation The area owner and an administrator. Software change A code review and passed tests. Change to Business Central records Always a person. AI can only propose the change. - Record each change
The approval, the test report and the revision go into document control. This is the change record that ISO 9001 requires.
- Set limits
You set a monthly limit for AI cost. Each area has a switch that stops all changes in that area.
Example
MRB wait time, from 9 days to 4.
One improvement project through the seven steps. The numbers in this example are for illustration only.
- Current value
- 9 days
- Target
- 3 days
- Result after 30 days
- 4 days
| Step | What happens |
|---|---|
| 01 Identify | NCRs wait 9 days for an MRB decision. |
| 02 Define | Measure: MRB wait time. Current value: 9 days. Target: 3 days. |
| 03 Design | Send supplier NCRs to engineering. Draft the SCAR in the supplier portal. Escalate after 48 hours. |
| 04 Build | AI and people do the tasks in a test copy. |
| 05 Test | Tested on the last 60 days of NCRs: 7 of 10 are routed correctly the first time. The quality manager approves. |
| 06 Deploy | The changes go live, with a rollback point. |
| 07 Measure | After 30 days, the wait is 4 days. This is better, but the target is 3 days. Decision: change again. |
Your data stays yours.
Requests, designs, tasks, tests and results are records in your own database. All project data stays there. Your company selects the AI model and can change it.
Bring one process you want to improve.
We will connect CourageMFG to a copy of your Business Central. Then we will show you the seven steps on your own data.