104 lines
4.8 KiB
Markdown
104 lines
4.8 KiB
Markdown
# Project Charter Report
|
||
|
||
| Document field | Value |
|
||
|---|---|
|
||
| Document | Project Charter Report |
|
||
| Project | BRN WMS |
|
||
| Project code | 200-WMS-26-001-00 |
|
||
| Title | Project Charter |
|
||
| 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 |
|
||
|
||
## Project information
|
||
|
||
| No. | Topic | Details |
|
||
|---:|---|---|
|
||
| 1 | Project name | BRN WMS — Warehouse Management System Development Project |
|
||
| 2 | Project code | 200-WMS-26-001-00 |
|
||
| 3 | Start date | 05/01/26 (formal project period start) |
|
||
| 4 | Project duration | 05/01/26–24/08/26 (232 days) |
|
||
|
||
## Project objectives
|
||
|
||
| Objective | Description |
|
||
|---|---|
|
||
| Centralize warehouse management | Replace manual/fragmented tracking with a single system for inventory accuracy, transaction control, and visibility |
|
||
| Support multi-company, multi-warehouse operation | Restrict each user to authorized company and warehouse data |
|
||
| Integrate operational and financial workflows | Connect sales, purchasing, and inventory movements to accounting and reporting |
|
||
| Strengthen control and auditability | Controlled document numbering, status lifecycles, and traceable transaction history |
|
||
| Enable maintainable deployment | Repeatable installation, configuration, and (per Product Operation Guide) backup/recovery procedures |
|
||
|
||
## Scope of Work (SOW)
|
||
|
||
| No. | System | System name |
|
||
|---:|---|---|
|
||
| 1 | User, Permission, and System Access Management System | Identity, Role, and Application-Access Management |
|
||
| 2 | Master Data System (Warehouse, Product, Contact) | Master Data Management (Warehouse, Product, Contact) |
|
||
| 3 | Warehouse and Stock Operations System | Inventory and Warehouse Operations (stock in/out/transfer, lot/serial/expiry, barcode) |
|
||
| 4 | Sales System | Sales (Quotation, Order, Invoice, Return, Credit Note) |
|
||
| 5 | Purchasing System | Purchasing (Request, Order, Invoice, Supplier Return) |
|
||
| 6 | Finance System | Finance (Receipt Billing/Receipts, Payment Billing/Payments) |
|
||
| 7 | Accounting System | Accounting (Chart of Accounts, Departments, Journals, General Ledger) |
|
||
| 8 | Reporting System | Reporting and Dashboards |
|
||
| 9 | Document Numbering and Status System | Controlled Document Numbering and Lifecycle |
|
||
| 10 | Notification and Scheduled Task System | Node.js/Socket.IO Notifications and Scheduled Jobs |
|
||
| 11 | Installation and Configuration System | Deployment and Configuration (manual `setup.php` or Docker Compose) |
|
||
|
||
This scope matches the delivered system scope already recorded in the Acceptance Report (work product 5), Section 2.
|
||
|
||
## Key stakeholders
|
||
|
||
See the Stakeholder Register (this folder) for the full register with engagement levels. Summary:
|
||
|
||
| No. | Name | Role | Main responsibility |
|
||
|---:|---|---|---|
|
||
| 1 | Seri Viriyasakultorn | Project Sponsor | Approve project documents and budget |
|
||
| 2 | Apirach Supattaratpateep | Project Manager | Manage the project plan and control quality |
|
||
| 3 | Noppong Chareunsook | System Analyst | Analyze requirements and define system behavior |
|
||
| 4 | Thanakorn Sathitwitayakul | Developer | Design and develop the system |
|
||
| 5 | Parin Ngamkham | QA / Tester | Test the system and verify quality |
|
||
| 6 | Yaowalak Bangchomphoo | Document Control | Control identifiers, versions, approvals, and evidence |
|
||
|
||
## Project timeline
|
||
|
||
| Phase | Period | Notes |
|
||
|---|---|---|
|
||
| Initiation / planning | 05/01/26–18/02/26 | Project planning and preparation |
|
||
| Development | 19/02/26–29/05/26 | Application development |
|
||
| Stabilization | 30/05/26–03/08/26 | Stabilization evidence `b2c4374` (03/08/26) |
|
||
| Test, validation and demonstration data | 04/08/26–14/08/26 | Test and validation execution 10/08/26–14/08/26; demo data population `dd48a8b` (14/08/26) |
|
||
| Delivery preparation | 15/08/26–17/08/26 | Rebranding, Docker Compose deployment stack, and SDLC documentation completion, and the recorded acceptance decision; see Change Report CH-003 |
|
||
| Closure | 18/08/26–24/08/26 | Final work-product review and Project Sponsor signature capture; acceptance decision recorded 17/08/26 |
|
||
|
||
## Project budget
|
||
|
||
Not separately tracked for this project.
|
||
|
||
## 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: ___________________________________________________
|