74 lines
2.6 KiB
Markdown
74 lines
2.6 KiB
Markdown
# Training Report
|
||
|
||
| Document field | Value |
|
||
|---|---|
|
||
| Document | Training Report |
|
||
| Project | BRN WMS |
|
||
| Project code | 200-WMS-26-001-00 |
|
||
| Title | Training Report |
|
||
| Project period | 05/01/26–24/08/26 |
|
||
| Release | 17/08/26 V1.0 |
|
||
| Standard | ISO/IEC 29110 Basic Profile |
|
||
| Prepared by | Apirach Supattaratpateep — Project Manager |
|
||
| Status | Final as a status report — **no training session has been conducted**; see Section 1 |
|
||
|
||
## 1. Training information
|
||
|
||
| Topic | Details |
|
||
|---|---|
|
||
| Training date | Not yet scheduled |
|
||
| Location | Not yet determined |
|
||
| Trainer | Thanakorn Sathitwitayakul (Developer); no dedicated trainer role is currently assigned |
|
||
| Training organizer | Apirach Supattaratpateep (Project Manager) |
|
||
| Expected attendees | Not yet determined — expected to include Owner/Admin, Staff, and Viewer role representatives per company |
|
||
|
||
## 3. Planned curriculum
|
||
|
||
Derived from the Software User Documentation (work product 18):
|
||
|
||
| No. | Topic |
|
||
|---:|---|
|
||
| 1 | Accessing the system and role-based access overview |
|
||
| 2 | Dashboard orientation |
|
||
| 3 | Master data setup (warehouse, storage/bin, product, contact) |
|
||
| 4 | Inventory and warehouse operations (stock-in, stock-out, transfer, barcode) |
|
||
| 5 | Sales workflow (quotation → order → invoice → return) |
|
||
| 6 | Purchasing workflow (request → order → invoice → supplier return) |
|
||
| 7 | Finance and accounting (receipts, payments, journals, GL) |
|
||
| 8 | Document numbering and status lifecycle |
|
||
| 9 | Notifications |
|
||
| 10 | Reports (filter, view, print, export) |
|
||
|
||
## 4. Result
|
||
|
||
No result to report — training has not yet occurred. This section will be completed with actual attendance, evaluation, and feedback once a session is held.
|
||
|
||
## 5. Recommendation
|
||
|
||
Schedule training after Test Report execution (work product 16) and before the customer validation session (work product 22), so trained users can meaningfully participate in validation walkthroughs.
|
||
|
||
## 6. Approval
|
||
|
||
### Prepared by
|
||
|
||
Name: Apirach Supattaratpateep
|
||
Role: Project Manager
|
||
Signature: ______________________________________________
|
||
Date: ___________________________________________________
|
||
|
||
### Reviewed by
|
||
|
||
Name: Thanakorn Sathitwitayakul
|
||
Role: Developer
|
||
Signature: ______________________________________________
|
||
Date: ___________________________________________________
|
||
|
||
### Reviewed and authorized by
|
||
|
||
Name: Seri Viriyasakultorn
|
||
Project roles: Project Sponsor / Customer Representative / Authorized Approver
|
||
Position: Managing Director
|
||
Company: B.R.N. Enterprise Co., Ltd.
|
||
Signature: ______________________________________________
|
||
Date: ___________________________________________________
|