Project Assumptions
This document contains a list of assumptions and expectations for any professional services agreement between TurnKey Lender Pte. Ltd. (the “Company”) and the Client.
1. General Assumptions
Any factors that are considered to be true and will be assumed to be true during the planning of the project:
Client will provide a dedicated Project Manager, who shall serve as the primary point of contact for the project. The Project Manager will be available to TurnKey Lender’s personnel during commercially reasonable business hours at all stages of the project.
Client shall always be able to provide or make available to TurnKey Lender clear, complete, and explicit information, such as data flow diagrams, API descriptions, technical specifications, integration examples, and any other project-related relevant information and the access to systems required for the performance of the services.
Client is responsible for the purchase of any third-party products, services, licenses, and SSL certificates required for the project.
Client is responsible for the setup of any non-TurnKey Lender development environments, or any other third-party software required for the project.
Unless agreed otherwise, TurnKey Lender will conduct manual testing of the solution on the latest versions of the following browsers: Chrome, and Microsoft Edge.
Unless agreed otherwise, TurnKey Lender will conduct manual testing with browser zoom settings set to 100%.
The budget is supported with the list of estimates if applicable and the timeline will be established upon clarifications provided by Client during the pre-sale stage. The timeline and the budget might be subject to change depending on the requirements provided during the requirements gathering phase and further development stage.
Any change to the original scope of work for the project might cause changes to the completion date of the project. Therefore, any changes and their impact must be reviewed and agreed upon by both parties.
During the project development stage, one (1) additional environment (Test or Staging environment) will be provided to Client for non-production use, required for the development, testing, and training activities. The additional environment shall not be used for production operations or any performance or stress testing. TurnKey Lender does not guarantee the high availability of this environment. Upon the project completion and Client’s project acceptance, the additional environment with all the related data shall be permanently removed from the server.
As the result of requirements gathering, a Detailed Functional Specifications document will be created and used as a single point of truth when it is needed to get the most actual requirements.
Unless agreed otherwise, no additional documents besides the Detailed Functional Specifications and User Acceptance Testing (UAT) Test Plan will be needed.
The final solution assumes the following limitations for production instances:
- Up to 50 concurrent users.
- Maximum individual API request size = 2MB.
- A maximum number of API requests per minute = 15.
- A maximum number of API requests per day = 2500.
- Maximum API traffic per day = 2 GB.
- Maximum Traffic per hour period = 100 MB.
- Database size up to 200 GB.
2. Meetings
The following outlines the various meetings incorporated into the project scope:
Requirements Gathering sessions will be conducted to align expectations and acquire all necessary details crucial for the implementation phase.
Three times a week, brief 15-minute internal standup meetings will be held to facilitate communication and project coordination.
A weekly 60-minute call with the client is scheduled to delve into project details, address concerns, and ensure alignment with client expectations.
There will be five demo sessions, each lasting 60 minutes, showcasing the features of the web application. These sessions aim to train client users on the functionalities.
3. System Integration Testing (SIT)
The following outlines the components included in the System Integration Testing phase:
Test scripts and test scenarios preparation to ensure thorough testing coverage.
Manual testing of changes implemented within the project scope.
Integration Testing of the functionality implemented within the project scope.
User Acceptance Testing (UAT) test plan preparation.
4. User Acceptance Testing (UAT)
UAT will be conducted by Client.
One round of UAT will be performed.
Within 5 days of UAT commencement, the client shall provide written notice of any deficiencies, specifying non-conformance to outlined specifications in the Detailed Functional Specification.
If no notice of deficiency is issued within 5 days after UAT initiation, delivered features will be deemed accepted by the client.
If deficiencies are identified, TurnKey Lender will promptly address and resubmit the applicable items for client review.
Within 5 days of fixes submission, the client will test the fixed features, issuing a notice of deficiency if necessary. If no notice is provided, the fixes are deemed accepted.
TurnKey Lender’s team will be available for up to 32 hours during UAT to address client questions.
5. Deployment
Upon completion of UAT, one deployment to the production server is included in the scope.
Production is set up in one instance on TurnKey Lender Cloud in Singapore unless otherwise explicitly agreed with the Client.
6. Project Management
TurnKey Lender Project Manager’s scope of work is limited to meetings arrangement, support during the requirements gathering, activity and resource coordination, document review, deployment support, and providing a regular status report to Client for up to 5 hour a week.
7. Post-delivery Support
The project delivery team will provide post-delivery support for two weeks after deployment, during which the client can report issues for resolution.
After the initial two weeks, support transitions to the Support Team, as per the terms and conditions of the maintenance agreement. Clients can submit issues, requests, and questions to the support desk.
8. Document Assumptions
Each document template has an allowance of up to 50 fields with up to 5 derived fields that can be extracted from the solution.
Files produced are only in .pdf and can be merged with other templates to form one document.
Templates are to be provided by the Client before the development.
For files that require extraction or reading, a sample of the files together with a clear, complete, and unambiguous description for each field is provided by the Client before the development.
File uploads are limited to the below.
- Microsoft Word files (*.doc, *.docx, *.rtf)
- Microsoft Excel files (*.xls, *.xlsx)
- Microsoft PowerPoint files (*.ppt, *.pptx)
- PDF files (*.pdf)
- Text files (*.txt)
9. Integration Assumptions
The third-party system has REST or SOAP API endpoint available for integration.
The API endpoint has clear, complete, and unambiguous documentation with examples of API methods usage. Documentation is to be provided by the Client before the development, during the presale and requirements gathering phases.
Allowance of no more than 1 method of third-party API can be implemented in the integration.
A method is defined as a message containing data beyond the response codes(https://developer.mozilla.org/en-US/docs/Web/HTTP/Status).
Unless otherwise stated each method has a limit of up to 20 data points.
There is no authentication or simple authentication (basic authentication (id and pass), API key authentication (the fixed secret key that is long value), or similar) needed to connect to the API.
10. E-Signing Assumptions
In addition to the below, the integration is to follow API-based integration assumptions.
- Allowance of up to 4 signatures per document.
- Integration options are via 1 type only (e.g., the provider has a choice of URL or email).
- Multiple signatures per document will not have the option to specify the signing order.
- Fields in each signature request per document will consist of an allowance of 1 signature and 4 fields of a combination of types (text, number, date) only.
TurnKey Lender can provide DocuSign out of the box; other providers will require additional efforts.
11. Rule Assumptions
This covers all automated rules that can trigger an action by the system:
- An example is Sending notification to Borrower when 5 days from the due date of payment.
- Each rule is a straightforward rule that has a standard pattern (e.g., if-else, or nested if-then-else condition) and there is no need to implement Artificial Intelligence or Machine Learning algorithms.
- Rules will be developed using TurnKey Lender tools and no 3rd party software or platform is required to develop rules.
- TurnKey Lender tools will be used for rules management and no dedicated management page is required in the web application.
12. Notifications
Notifications are to be sent via SMS, Email, or using the internal notification interface of the solution.
1 simple triggers for per notification of simple IF..THEN..ELSE from data in the solution.
Each notification template has an allowance of up to 20 fields.
13. Reports
All source values for report fields exist in the database, for the avoidance of doubt, reports should not contain fields that require new (previously unspecified) integrations and/or additional fields that are not available in the solution without extra configuration that was not explicitly requested.
Each report to be implemented in chart, statistic, or table form and will not contain dynamically generated/configured reports (like Excel pivot tables or charts).
Reports are available in web application only and there is no need to automatically export the report data.
14. Data Migration
Unless agreed otherwise only data from excel or CSV formats will be migrated.
There is no need to implement a conversion of existing data to another format.
The client will provide a sample of the data together with an explanation of each field before the development (during the presale, requirement gathering, etc.)
Clean-up and validation of existing data is not a part of the scope.
15. Others
The following items are assumed/defined as below unless explicitly stated and mutually agreed upon by both parties:
Manual Decision Flow Stage
- At each decision stage, the user can decide to approve, reject, or rework.
- Approving the application would move the application to the next approver stage. If the approver is at the highest stage, the application status would be updated as approved.
- Rejecting the application would be to update the status of the application as a rejection.
- Rework would move the application to the earliest stage.
Fields
- Simple fields refer to one of the types below:
- Numeric
- Word(s)
- Date
- Time
- Derived fields refer to taking in simple fields and applying some form of logic such as a formula.
- Unless stated otherwise, elements or fields, refer to simple fields.
16. General Exclusions
The following items are excluded from the project’s scope unless explicitly stated and mutually agreed upon by both parties:
Any activities related to the setup and configuration of other infrastructure provided by Client to host TurnKey Lender’s solution if the setup and configuration are required to be performed on the infrastructure provided by Client.
Any third-party software development which might be required in the course of the project.