Empire Teas Managed Cloud Infrastructure & Hosting — Statement of Work (ET-002)
SUPERSEDED 29 September 2026 — not signed, and not the arrangement in force. Empire Teas declined this SOW and opened the AWS account themselves: the account is held by Kavindu Anthony (Empire Teas IT), paid by Empire Teas’ own card, and billed to Empire Teas directly by AWS. Empire Teas created an administrator IAM identity for Shyamin Ayesh (Altrium DevOps), who builds the environments in that account. Altrium bills only the USD 360/month application support fee under SOW ET-001; the USD 650/month fee below does not apply. The text below is kept unchanged as the record of what was proposed. What replaces it: the proposal header’s 29 September 2026 post-issue note,
sow-cost-annexe.md(now an estimate of Empire Teas’ own AWS bill), and.forge/design/environments-and-identity.md§3.
Status: drafted (v1.2, 5 September 2026). This is a searchable, diffable mirror of the issued Word document; the issued draft
.docxis the authoritative text on any disagreement. Source:Altrium-Empire-Teas-Managed-Cloud-Infrastructure-SOW-v1.2.docx. Trust: a Statement of Work is a highest-trust commercial artifact (.claude/rules/source-trust.md) — it outranks internal design docs on scope, price, ownership and infrastructure.Why this SOW exists (context, not part of the issued text). Empire Teas is a non-technical business; their AWS/Azure billing is normally handled by their outsourced IT provider (Dialog). For the CRM project Empire asked Altrium to own and run the AWS infrastructure rather than Empire or Dialog, with Altrium invoicing Empire a fixed monthly fee. This SOW (ET-002) is the vehicle for that arrangement: Altrium owns the AWS organisation and accounts, operates the environments, and bills Empire USD 650/month for managed infrastructure & hosting — separate from the USD 360/month CRM application support fee under SOW ET-001.
This changes the earlier working assumption. The pre-SOW assumption (AD-O-10) was that Empire would open and hand over the AWS management account. Under this SOW, Altrium owns the AWS organisation and accounts and they are not transferred to Empire on exit (§2.1, §2.3, §12). Per §14, this SOW expressly supersedes any inconsistent provision of SOW ET-001 or the proposal on AWS account creation/ownership, infrastructure operations, infrastructure pricing, and account transfer on exit. The harness docs that described the old assumption are reconciled to this model.
Statement of Work [ET-002] — Empire Teas Managed Cloud Infrastructure and Hosting
This Statement of Work (the “SOW”) is entered into between Altrium Pvt Limited (the “Supplier”) and Empire Teas Pvt Limited (the “Client”) under the Master Services Agreement dated [TO BE COMPLETED] (the “MSA”). It defines the recurring managed cloud infrastructure and hosting services supporting the Client’s CRM solution delivered under SOW ET-001.
| Item | Details |
|---|---|
| SOW reference | ET-002 |
| Service | Managed cloud infrastructure, hosting, security and operations for the Empire Teas CRM |
| Service commencement | Production Go-Live under SOW ET-001, or another date agreed in writing |
| Initial term | Twelve (12) months from Service Commencement |
| Supplier service representative | [NAME / TITLE / EMAIL / TELEPHONE] |
| Client service representative | [NAME / TITLE / EMAIL / TELEPHONE] |
1. Purpose and Objectives
The Supplier will provision, host, supervise and maintain the cloud environment required to operate the CRM. The intended outcomes are:
- secure and logically isolated development and production environments;
- continuous automated monitoring with timely operational response during the agreed service window;
- controlled patching, backups, restoration testing, capacity management and cost oversight;
- transparent monthly service, environment-health and usage reporting; and
- continued Client ownership and portability of Client Data and applicable Deliverables.
2. Service Environment and Ownership
2.1 Account and billing ownership
The AWS organisation, AWS accounts, subscriptions and direct cloud-vendor billing relationships used for the Services will be owned and administered by the Supplier. The Supplier will provide dedicated, logically isolated development and production accounts for the Client solution. The Supplier may use consolidated billing and central security tooling, provided Client Data and workloads remain segregated from those of other customers.
2.2 Planned hosting architecture
The primary hosting region will be AWS US East (N. Virginia) (us-east-1), with CloudFront used for content delivery where applicable. The planned service baseline includes Amazon ECS/Fargate, ECR, Application Load Balancer, Amazon RDS for PostgreSQL, S3, SQS/EventBridge, Secrets Manager, CloudWatch, AWS Budgets/SNS, VPC and IAM services, GuardDuty, CloudTrail, KMS, IAM Identity Center and Shield Standard. The production baseline is planned to include Multi-AZ RDS and AWS WAF. The Supplier may right-size or substitute equivalent managed services without materially reducing security, availability or functionality.
2.3 Ownership of data and resources
The Client retains all right, title and interest in Client Data and in Deliverables owned by the Client under the MSA or SOW ET-001. The Supplier retains ownership and control of its AWS organisation, accounts, shared tooling, operating methods and billing relationships. Cloud accounts are not transferred to the Client on expiry or termination; data, applicable build artefacts and agreed configuration information will be exported as described in Section 12.
3. Included Services
| Service area | Included activities |
|---|---|
| Provisioning and configuration | Initial creation and configuration of the development and production environments; infrastructure-as-code; network, access, logging and deployment foundations. |
| Monitoring and incident operations | Continuous automated health, availability, resource and security monitoring; alert triage; incident coordination; escalation and operational remediation. |
| Platform maintenance | Maintenance and patching of supported operating components, container base images, managed database configuration, certificates, secrets and related cloud services. |
| Security administration | Least-privilege access, MFA controls, security logging, threat-detection review, vulnerability remediation and security configuration updates. |
| Backup and recovery | Database point-in-time recovery, scheduled snapshots, S3 versioning, retention management, restoration support and quarterly restore testing. |
| Capacity and cost management | Usage review, right-sizing, budget alerts, capacity adjustments and reasonable cost optimisation. |
| Reporting and vendor coordination | Monthly environment-health and usage summary and coordination with AWS or other approved service providers. |
The initial infrastructure foundation required for the CRM is included within the implementation activities under SOW ET-001 and will not attract a separate setup fee, unless the Client requests additional environments, migrations, redesign or work outside that agreed baseline.
4. Service Window and Response Targets
Automated monitoring and alert generation operate continuously. Human support, triage and remediation are provided from 9:00 a.m. to 5:00 p.m. Sri Lanka time on Business Days, excluding Sri Lankan public and mercantile holidays (“Business Hours”). Targets are measured only during Business Hours from the time the Supplier receives an actionable alert or report.
| Priority | Illustrative impact | Initial response | Workaround target | Resolution target |
|---|---|---|---|---|
| S1 – Critical | Production unavailable, material security incident or severe data-integrity risk | 1 business hour | 2 business hours | 4 business hours |
| S2 – High | Major degradation or material feature unavailable; no reasonable alternative | 2 business hours | 4 business hours | 1 Business Day |
| S3 – Medium | Limited degradation with workaround available | 4 business hours | 1 Business Day | 3 Business Days |
| S4 – Low | Minor operational request, advisory matter or planned improvement | 1 Business Day | Not applicable | Planned maintenance release |
These are service targets, not guaranteed resolution commitments or service-credit entitlements. Time awaiting Client information, access, approval, third-party action or resolution of an external-provider fault is excluded. After-hours human intervention is separately chargeable at rates agreed in advance, except where the incident was directly caused by the Supplier’s breach, negligence or failed infrastructure change.
5. Maintenance and Patching
- Routine maintenance will normally be performed outside Business Hours with at least three (3) Business Days’ notice where service impact is expected.
- Emergency maintenance may be performed when reasonably necessary to address an active threat, material vulnerability or service instability; notice will be provided as soon as practicable.
- Applicable critical or actively exploited vulnerabilities will be targeted for remediation within one (1) Business Day; high-risk vulnerabilities within five (5) Business Days; and routine updates through a monthly maintenance cycle.
- Changes will use controlled deployment, validation and rollback procedures appropriate to the risk and urgency.
6. Backup, Restoration and Resilience
| Control | Baseline |
|---|---|
| Database recovery | Point-in-time recovery with approximately five-minute granularity; fourteen (14) days’ production retention and three (3) days’ development retention. |
| Snapshots and object storage | Daily database snapshots and S3 versioning, subject to lifecycle and retention controls. |
| Restore testing | Quarterly restore test with outcome included in the monthly or quarterly service report. |
| Recovery objectives | Target database RPO: 5 minutes. Target restore-based RTO: 1–2 hours. Where Multi-AZ is enabled, target automated failover: under 5 minutes. |
| Disaster recovery boundary | Cross-region replication, warm standby and full disaster-recovery orchestration are excluded unless added through Change Control. |
Recovery objectives are targets dependent on AWS service availability, dataset size, failure mode and dependencies. They do not constitute a guarantee of uninterrupted service or zero data loss.
7. Responsibilities
7.1 Supplier responsibilities
- operate the included services with appropriately skilled personnel and reasonable care;
- maintain administrative access controls and prevent unauthorised direct changes;
- manage alerts, incidents, maintenance, backups, security updates and usage reporting;
- maintain reasonable operational records and provide evidence or read-only reports upon reasonable request; and
- notify the Client of material incidents and known service risks in accordance with the MSA.
7.2 Client responsibilities
- nominate authorised business and technical contacts and provide timely decisions, information and approvals;
- maintain accurate, lawful Client Data and comply with acceptable-use and applicable-law requirements;
- manage Client-controlled dependencies such as corporate domains, DNS approvals, Microsoft 365 configuration and end-user devices, unless expressly included;
- promptly report suspected incidents or material service issues and cooperate with investigation and recovery;
- not attempt or permit unauthorised direct modification of the Supplier-owned cloud environment; and
- pay the fixed monthly fee, taxes and other charges approved through Change Control when due.
8. Fees, Usage and Invoicing
| Charge | Amount and billing basis |
|---|---|
| Managed cloud infrastructure and hosting service | USD 650.00 per month, invoiced monthly in advance from Service Commencement. The first partial month, if any, will be prorated. |
The monthly fee is all-inclusive for the approved service baseline and covers the managed infrastructure services in this SOW together with the associated AWS and approved third-party platform usage required to operate the solution, including applicable cloud administration and billing-management activities. No separate usage recharge or administration percentage will apply within that baseline.
The USD 360.00 monthly CRM application support and maintenance fee under SOW ET-001 remains separate and is not included in the USD 650.00 fee. Material additions or changes outside the approved architecture, usage assumptions or service scope—including additional environments, regions or third-party services—require prior written approval through Change Control and may result in an agreed fee adjustment. Taxes, payment timing and USD/LKR conversion are governed by the MSA.
9. Exclusions and Additional Services
Unless added through Change Control, the Services exclude:
- CRM application defect correction, functional support, training, enhancements and new features, which remain governed by SOW ET-001;
- 24x7 human on-call coverage or guaranteed after-hours response;
- additional staging, testing or regional environments; major re-platforming or architecture redesign;
- cross-region disaster recovery, warm standby, dedicated NAT gateways or other optional resilience controls not in the approved baseline;
- penetration testing, formal compliance certification, legal or regulatory advisory services;
- outages or degradation caused by AWS or another third party beyond the Supplier’s reasonable control; and
- Client-requested after-hours planned work, migration to another provider, or services outside the stated baseline.
10. Security, Data and Subprocessors
The security, confidentiality, data-protection and incident-notification provisions of the MSA apply. The Supplier will act as a processor/service provider for Client Data hosted in the environment and may use AWS and other approved providers as subprocessors. The baseline includes encryption in transit and at rest where supported, least-privilege access, MFA for privileged access, central logging, threat detection, secrets management and controlled administrative access.
The Client authorises the subprocessors and hosting location described in this SOW, subject to any notice or objection procedure in the MSA. The Supplier will not use Client Data for its own independent purposes and will maintain logical separation of Client workloads and data.
11. Term and Renewal
This SOW begins on the date of last signature. The recurring Services begin on Service Commencement and continue for an initial term of twelve (12) months. Thereafter, the SOW renews month-to-month unless either Party gives at least thirty (30) days’ written notice. Termination for cause and suspension rights are governed by the MSA. If the CRM application services under SOW ET-001 terminate, either Party may align termination of this SOW with the agreed transition plan.
12. Exit and Transition
On expiry or termination, all accrued fixed monthly fees and other approved charges remain payable. Subject to payment of undisputed amounts, the Supplier will within ten (10) Business Days provide a standard export of Client Data, current infrastructure/configuration documentation reasonably required for migration, and Client-owned source or build artefacts due under the MSA or SOW ET-001. The Supplier-owned AWS organisation and accounts will not be transferred.
Additional migration, re-platforming or transition assistance will be charged at rates agreed in writing. Unless otherwise required by law or agreed in writing, the Supplier may delete active Client Data thirty (30) days after completing the agreed export, subject to normal backup-expiry cycles, and will confirm deletion upon request.
13. Assumptions and Change Control
- The service is sized initially for approximately 10–20 users and data volumes in the low tens of thousands of records.
- The baseline comprises development and production environments in us-east-1.
- The fixed monthly fee is based on the approved architecture, service scope and usage assumptions in this SOW.
- Optional controls and environments identified in the proposal are not included unless expressly approved.
- The Supplier may undertake routine right-sizing and operational changes that do not materially reduce agreed security, availability or functionality.
- A change to scope, architecture, service window, service targets or included controls will follow the Change Control procedure in the MSA.
14. Documents, Precedence and Supersession
This SOW incorporates the MSA. SOW ET-001 is incorporated only to the extent necessary to identify the CRM solution, Production Go-Live, application-support boundary and Client-owned Deliverables. Appendix A of the CRM proposal is incorporated for architecture and indicative cost context only.
For the managed cloud infrastructure covered here, this SOW expressly supersedes any inconsistent provision of SOW ET-001 or the proposal concerning (a) AWS account creation or ownership, (b) responsibility for infrastructure-level monitoring, patching, backups and cloud operations, © infrastructure pricing and responsibility for AWS and approved third-party platform costs, and (d) transfer of cloud accounts or resources on exit. The application support scope and USD 360.00 monthly fee under SOW ET-001 remain unchanged. If there is any conflict, the order of precedence is: this SOW for its subject matter; the MSA; SOW ET-001; and the proposal.
15. Acceptance and Signatures
By signing below, each Party confirms that it has authority to enter into this SOW and agrees to be bound by its terms and the MSA.
| For Altrium Pvt Limited | For Empire Teas Pvt Limited |
|---|---|
| Name: [TO BE COMPLETED] | Name: [TO BE COMPLETED] |
| Title: [TO BE COMPLETED] | Title: [TO BE COMPLETED] |
| Signature: __________________________ | Signature: __________________________ |
| Date: ______________________________ | Date: ______________________________ |
| Company registration no.: [TO BE COMPLETED] | Company registration no.: [TO BE COMPLETED] |
| Registered address: [TO BE COMPLETED] | Registered address: [TO BE COMPLETED] |