3.4 KiB
Stakeholder Register
| Document field | Value |
|---|---|
| Document | Stakeholder Register |
| Project | BRN WMS |
| Project code | 200-WMS-26-001-00 |
| Title | Stakeholder Register |
| 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 — consistent with Customer Requirements Section 3 |
Basis
This register identifies project stakeholders, their roles, responsibilities, and engagement levels.
Key stakeholders
| No. | Name | Initials | Role | Main responsibility | Engagement level |
|---|---|---|---|---|---|
| 1 | Seri Viriyasakultorn | SeV | Project Sponsor / Customer Representative / Authorized Approver | Represent customer needs; approve scope, strategic decisions, requirement baseline, acceptance, and closure | A (Approve), I (Inform) |
| 2 | Apirach Supattaratpateep | ApS | Project Manager | Plan and coordinate activities, resolve issues, control changes, maintain the approved baseline | A (Accountable), R (Responsible) |
| 3 | Noppong Chareunsook | NoC | System Analyst | Analyze requirements, specify system behavior, and maintain technical traceability | R (Responsible), C (Consult) |
| 4 | Thanakorn Sathitwitayakul | ThS | Developer | Design and implement the solution | R (Responsible), C (Consult) |
| 5 | Parin Ngamkham | PaNg | QA / Tester | Execute tests, verify quality, and facilitate validation, independent of the Developer — added to the project 17/08/26 | R (Responsible), C (Consult) |
| 6 | Yaowalak Bangchomphoo | YaB | Document Control | Control identifiers, versions, approvals, distribution, repository content, and evidence — added to the project 17/08/26, same role as the example reference project for the same company | R (Responsible) |
| 7 | Warehouse Manager and Staff | — | Operational users | Perform and review warehouse, stock, barcode, and reporting operations | C (Consult), R (Review) |
| 8 | Sales and Purchasing Users | — | Business users | Perform quotation, order, purchase, invoice, and return workflows | C (Consult) |
| 9 | Finance and Accounting Users | — | Business users | Perform billing, receipt, payment, journal, ledger, and financial reporting activities | C (Consult) |
| 9 | System Administrator | — | Supporting user | Configure environment, company, users, services, monitoring, backup, and recovery | C (Consult), I (Inform) |
| 10 | Management / Auditor | — | Information consumer | Review controlled records, transaction history, exceptions, and management information | I (Inform) |
Note: The Engagement Level codes used are as follows — A: Approve, R: Responsible, C: Consult, I: Inform, following the RACI Matrix approach
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: ___________________________________________________