Client Implementation — Al Faisal¶
Client Profile¶
| Field | Value |
|---|---|
| Client Name | Al Faisal |
| Type | School |
| Location | |
| Number of Students | |
| Number of Campuses | Multiple |
| Current Systems | Central (SIS) |
| Contract Start | |
| Go-Live Target | |
| Project Manager | |
| Solution Architect |
Solutions in Scope¶
| Solution | In Scope | Notes |
|---|---|---|
| ERP | ❌ | |
| ARM | ✅ | Multi-campus, 4-term billing, CSV-based billing instructions |
| EPM | ❌ |
Implementation Notes¶
Al Faisal follows the same ARM billing concepts as other clients but uses a CSV-based approach for billing instructions rather than the automated configurator. This is an interim arrangement while the Central SIS integration is being stabilized. Manual campus reconciliation with the school is required before each billing cycle. The school bills per term (4 terms per year).
Configurator Usage¶
Al Faisal does not use the automated billing configurator suitelet. The configurator exists in the account but is unused. Billing instructions are managed via CSV import:
- Export student data from NetSuite (with year level, item assignments)
- Filter and map items to students in CSV (e.g., year 7-10 → laptop hire fee)
- Import billing instruction applied-to records via CSV — the parent billing instruction records already exist in the account
- Generate invoices from the imported instructions
Al Faisal has its own version of the billing codebase, different from both Saint Edwards and the newer accounts. The billing instruction + billing instruction applied-to record pattern is used (same as Saint Edwards), but item assignment is done manually rather than through the configurator.
Project Timeline¶
| Phase | Start | End | Status |
|---|---|---|---|
| Discovery & Requirements | |||
| Solution Design | |||
| Configuration & Customization | |||
| Data Migration | |||
| Testing (SIT) | |||
| User Acceptance Testing (UAT) | |||
| Training | |||
| Go-Live | Completed | ||
| Hypercare / Post Go-Live | Completed |