You are on page 1of 2

Deliverables:

1. Standard template for all mentioned certificates


2. E-signature of the Priest-in-charge embedded in the certificate
3. Church logo in template
4. Repository of requested and printed certificates
5. Permission based access ***
6. Dashboard **
7. Reports ***

IV. SERVICE LEVEL AGREEMENT (SLA):


The SLA agreement is vital to the support and maintenance of the system. The SLA is provided in the
principle of the defined continuity and making maximum use of the system, continuing work
Implementation and of course ensuring maintenance of the project. The following support guidelines
shall be implemented.
1. Remote support and maintenance for the period of 1 year with the effectivity date upon turnover and
acceptance of project.
2. Remote administration, assistance, troubleshooting and technical support.
3. On site service, if needed, based on severity of issues. (not included in quotation)
4. Phone and email support from Mondays to Fridays from 0800H to 1700H.

After the period of 1 year, support and maintenance, both onsite and remote may incur additional
charges.
Support covers all items related to the existing platform. A separate document and proposal (if needed)
defining the SLA process shall be provided upon execution of the project.
All concerns outside the scope of the project shall be treated as Change Control and shall be charged
separately.
CHANGE CONTROL:
Change control is necessary for the management of the software requirements. The objective of the
change control process is to minimize disruption in software development process, reduce re-work and
defects, and effective utilization of resources. The following change control guidelines shall be
implemented:
1. Any software changes must undergo a change control process.
2. A change control board consisting of client representatives and solutions provider representatives will
decide on the acceptance of the change request.
3. Acceptance of change request will entail adjustment in timeline, or replacement or swapping of
scope of work, or adjustment in allocated resources, or adjustment in project cost.

A separate document defining the change control process shall be provided upon execution of the
project.
TERMS AND CONDITIONS:
1. Client shall provide the necessary project team members from their end.
2. Requests not approved by the change control process is out of project scope.
3. Integration of developed system and other external system is out of project scope.
4. Data migration and population is out of project scope.
5. Backup and disaster recovery plan will be treated as separate projects.

Let us know if there is anything that we can do to further satisfy your IT requirements.
Yours sincerely,
Nolan Zara
President
Makopa Inc.
CONFORME:

You might also like