Classification: INTERNAL
March 2024
STATEMENT OF WORK
Green Financing Platform
1
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate
permission.
Classification: INTERNAL
ACRONYMS, ABBREVIATION, AND TERMS
Acronym
Description
ADB
Asian Development Bank
ADO
Azure Dev Ops
API
Application Programming Interface
CI/CD
Continuous Integration / Continuous Delivery
EA
Enterprise Architecture
EaC
Environment-as-Code
ELS
Early Life Support
AI
Artificial Intelligence
ITD
Information Technology Department
OOTB
Out of The Box
MVP
Minimum Viable Product
PSC
Project Steering Committee
SaaS
Software as a Service
SME
Subject Matter Expert
SOW
Statement of Work
SQL
Structured Query Language
SPD
Strategy, Policy, and Partnerships Department
TEC
Technical Evaluation Criteria
TSMP
Transition Support and Maintenance Plan
UI
User Interface
UX
User Experience
2
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate
permission.
Classification: INTERNAL
Contents
1
Background
5
2
Objective
5
3
Scope of Work
5
4
Overview Functional Specifications
5
Expected Deliverables 6
6
Timeline and Milestones
7
Solution Delivery and Other Non-Functional Requirement
5
6
7
7.1
Application Cloud SaaS Hosting for the MVP phase ........................................................................... 7
7.2
High-level Solution Design ...................................................................................................................... 7
7.3
Reporting and Analytics ........................................................................................................................... 7
7.4
Security and Compliance ........................................................................................................................ 8
7.5
Customization and Brand Alignment ..................................................................................................... 8
8
Non-Technical Requirements 8
8.1
Project Management and Administration .............................................................................................. 8
8.2
Resources / Team Composition ............................................................................................................. 8
8.3
Qualifications ............................................................................................................................................. 9
8.4
Development Methodology ..................................................................................................................... 9
8.5
Critical Assumptions ................................................................................................................................. 9
8.6
Training and Adoption .............................................................................................................................. 9
9
Potential Future Deployment to Production
10
Contract Details 10
10
10.1
Service Level Compliance during Project Implementation ............................................................... 10
10.2
Place of performance ............................................................................................................................. 13
10.3
Working days and business hours ....................................................................................................... 13
10.4
Identification and Conduct .................................................................................................................... 13
10.5
Intellectual Property ............................................................................................................................... 14
10.6
Milestone Payment Schedule ............................................................................................................... 14
10.7
Confidentiality Statement ...................................................................................................................... 14
11
Appendixes
15
1.1
ADB Engineering Standards ................................................................................................................. 15
1.2
High-level Solution Design .................................................................................................................... 15
1.3
ADB ITD Security Guardrails ................................................................................................................ 15
1.4
ADB Project Management Framework (PMF) .................................................................................... 15
1.5
SDLC Operations Manual ...................................................................................................................... 15
1.6
ADB Handbook of Style and Usage ..................................................................................................... 15
3
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate
permission.
Classification: INTERNAL
12
Potential Future Deployment to Production
13
SOW Acceptance 16
16
4
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate
permission.
Classification: INTERNAL
1 Background
The Asian Development Bank (ADB) is an international financial institution headquartered in
Manila, Philippines and is composed of 68 members, 49 of which are from the Asia and Pacific
region. ADB is committed to achieving a prosperous, inclusive, resilient, and sustainable Asia and
the Pacific while sustaining its efforts to eradicate extreme poverty.
The Strategy, Policy, and Partnerships Department (SPD) plays a pivotal role in shaping the
organization’s overarching goals and initiatives. This department is responsible for formulating and
implementing strategic plans that align with the ADB’s mission of fostering sustainable economic
development and reducing poverty in the Asia-Pacific region. By conducting thorough research,
analysis, and policy formulation, the department provides valuable insights to guide the bank’s
operations and decision-making processes. SPD works to strengthen ties with regional and global
institutions to promote coordinated efforts towards achieving common development objectives. In
the era of digital transformation, SPD has been spearheading the development of mechanisms to
facilitate finance mobilization and serves as a strategic hub within the ADB, contributing to the
formulation of policies that drive impactful development projects and fostering collaborative
partnerships to maximize development impact.
2 Objective
The ADB’s Strategy 20301 aims to achieve a prosperous, inclusive, resilient, and sustainable Asia
and the Pacific. Critical to the implementation of the Strategy 2030 is the digital transformation of
ADB using secure, modern information and technology (IT) systems and digital processes to
enhance effectiveness, efficiency, and resilience.
Green project funding aims to increase financial flows from public, private, and not-for-profit
sectors towards environmental initiatives and supporting sustainable development priorities.
3 Scope of Work
The specific objective of this Statement of Work (SoW) is to develop a Minimal Viable Product
(MVP) for a Green Financing Platform featuring a portfolio of green projects. The Green Financing
Platform aims at promoting and facilitating financial support to projects prioritizing sustainable
development and environmental protection. The platform will facilitate the process of raising
capital for green projects by using Artificial Intelligence (AI) in the screening and due diligence
processes of these projects.
The MVP will be developed for internal ADB use, focusing on adoption of ADB specific due
diligence guidelines and practices, user testing and feedback sessions for subsequent
development and implementation phases.
4 Overview Functional Specifications
(i)
Portfolio of projects with their owners:
1
https://www.adb.org/documents/strategy-2030-prosperous-inclusive-resilient-sustainable-asia-pacific
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
a. Registration of projects and owners' profiles;
b. AI enabled Screening and Due diligence processing: Assessment of the green
projects include financial, legal and environmental-related risks and opportunities.
The screening process typically involves an initial assessment of the project's
potential risks, while the due diligence process involves a more in-depth
investigation of these risks, liabilities and opportunities. The AI will assist and speed
up the pace of screening, due diligence and document review, providing a deeper
insight into documents and a level of discovery that can be difficult to achieve
manually.
c. Rating resulting from the screening and due diligence processing;
5 Expected Deliverables
(i)
(ii)
(iii)
(iv)
Conceptual Design: Prior to development, the Solution Provider will conduct a needs
assessment and produce a conceptual design. In overall, processes will be subject to
revisions and corrections from the stakeholders during the project lifetime . The
detailed work plan, methodology, design, functional specifications, design UI/UX,
technologies and system requirements will be reviewed and confirmed with the
stakeholders;
Development: The Solution Provider will develop, test and implement the front-office
and back-office features of the MVP. The MVP will be tested with various technical
iterations (ref. Agile methodology / sprints) and testing sessions.
Testing: The Solution Provider will conduct with the stakeholders a Test phase based
on case studies and precedents (data set).
Final Report:
a. Final report and project documentation (user and administration manual,
guidelines and technical specifications, etc.); and
b. Propose a plan to transition from MVP into Go-Live, including inventory and
recommendations of requirements for future upgrade.
All development and documentation will be in English.
6 Timeline and Milestones
Dates are subject to change due to various scheduling factors with a total period of 6
months.
MILESTONE
Contract Award
TIMELINE
-
Conceptual design completed
Week 4
Development / Sprint #1
Week 8
Development / Sprint #2
Week 12
REMARKS
First set of prioritized
front-office and backoffice features
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
Development / Sprint #3
Week 14
Sprint #4
Week 18
MVP ready for review by
the stakeholders with the
data set
Review and feedback
from stakeholders #1
Sprint #5
Week 20
Review and feedback
from stakeholders #2
Completion MVP, final review and
testing
Week 22
Final Report
Week 24
7 Solution Delivery and Other Non-Functional Requirement
7.1 Application Cloud SaaS Hosting for the MVP phase
(i) Infrastructure: The SaaS application could be hosted outside of ADB infrastructure,
leveraging a reliable and scalable cloud service (preferably Microsoft);
(ii) Cloud SaaS Solution: The selected solution must meet industry standards for cloud
security, performance, and reliability;
(iii) Scalability: The hosting environment should be designed to scale horizontally to
accommodate increased user loads and data volumes;
Customization matrix/model type: Allow ADB to define their own customizable
assessment soft matrix and/or model type to apply. Allow custom risk items and
customize confidence rating matrix. This will allow extensibility and flexibility; and
(iv) The solution must be responsive, flexible, scalable with reusable components, and agile
to address fast-changing business needs, while adhering to ADB’s design principles,
overall technical direction, architecture, and infrastructure. In particular, the Solution
Provider must demonstrate the skills, knowledge, and experience for Continuous
Integration and Deployment (CI/CD) through Azure DevOps. Refer to ADB Engineering
Standard document.
7.2 High-level Solution Design
• Upon contract award, Provider is required to complete High-Level Solution Design form.
ADB is available to provide assistance in filling out the form.
7.3 Reporting and Analytics
• Monitor the usage, performance, and impact of the platform.
• Deliver regular reports to ADB on project progress, user feedback, and further
enhancements.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
7.4 Security and Compliance
• Implement robust security measures to safeguard sensitive data and ensure ADB
compliance and in line with industry best practices.
• Provide ongoing technical support.
• Establish user support channels.
• Incorporates the integration and deployment of Information Technology Division (ITD)
Security Guardrails as an integral component of the overall scope. The ITD Security
Guardrails encompasses a comprehensive set of security measures designed to fortify
our organization's digital infrastructure against potential cyber threats and vulnerabilities.
7.5 Customization and Brand Alignment
•
Design to be implemented must adhere to industry standards, ADB’s design principles
on UX, and ADB style and usage. Refer to ADB Handbook of Style and Usage.
8 Non-Technical Requirements
8.1 Project Management and Administration
• The Solution Provider will appoint a project manager to run the day-to-day activities of
the engagement. The Provider’s project manager will work with ADB’s project manager
and project lead to manage work planning, execution, monitoring, and control to ensure
that the work is performed correctly, timely, accurately, efficiently, and in compliance with
the requirements stated in this SOW.
•
The Solution Provider should provide a Project Management Plan with the following, at a
minimum:
(i) Project organization
(ii) Roles & responsibilities
(iii) Project delivery approach
(iv) Project schedule (high level & detailed)
(v) Schedule management
(vi) Resource management
(vii) Communications plan
(viii) Project change management
•
The Solution Provider should develop a plan to transition from MVP into full roll-out
across ADB.
Upon project completion, the Solution Provider should provide an Engagement
Closure/Completion Report.
ADB SharePoint will be used to store and manage project artefacts.
The Solution Provider should follow ADB’s Project Management Framework
•
•
•
8.2 Resources / Team Composition
•
The Solution Provider must provide the resource matrix forecasted for the duration of the
services under this SOW.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
•
•
•
•
The Provider will assign a dedicated Project Team to support continuous project
management activities.
The Provider is responsible for the selection of the members for the project team. The
assignment will be subject to ADB approval.
Once resources are assigned to the project, they may not be substituted or replaced
without ADB’s approval.
On top of the Project Team, the Solution Provider will provide the name, designation and
contact details of a key executive (world or Asia Pacific responsibility) having
accountability for this engagement, who ADB may coordinate with for any project
concern or issue escalation.
8.3 Qualifications
ADB is seeking a vendor team that possesses technical expertise and the resources
necessary to design, develop, and implement the MVP while demonstrating effective
project management.
8.4 Development Methodology
The Solution Provider should use Agile methodology to deliver the MVP.
8.5 Critical Assumptions
The vendor will follow ADB templates and project artifacts as per contractor processes,
standards, and guidelines. If required, limited customization can be incorporated to align with
ADB’s requirements for reporting.
ADB will make available, upon request, all relevant information/documentation required to
facilitate consultant’s analysis and recommendations.
Refer to SDLC Operations Manual.
8.6 Training and Adoption
• Provide comprehensive training for ADB administrators and users, ensuring they are
equipped to use the platform and the AI tool effectively.
(i)
User Training: Provide comprehensive training sessions for end-users to ensure a
smooth onboarding process and efficient utilization of the SaaS application;
(ii)
Administrator Training: Conduct training sessions for system administrators to
empower them with the knowledge required for managing and maintaining the
application.;
(iii)
Knowledge Transfer: Facilitate knowledge transfer sessions to internal IT teams
for a seamless transition, including documentation, best practices, and
troubleshooting guides.; and
(iv)
Technical Support: Establish a support mechanism, including a helpdesk and
documentation repository, to address user queries and issues promptly.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
9 Potential Future Deployment to Production
A deployment to production may be considered in the future, and if materialized, the current
known requirements are documented in the attached appendix Potential Future Deployment
to Production Functional Requirements.
10 Contract Details
10.1
Service Level Compliance during Project Implementation
ADB requires that the vendor will ensure all services, features and functionalities, and other
requirements identified in this SOW are completely implemented as scheduled, tested,
signed off, and operating as designed before becoming operational and before signing the
Project Acceptance Certificate.
Any contract breaches and violations found will be handled following ADB’s institutional
procurement and contract administration processes.
Prior to MVP completion, if the vendor fails to perform the Services and/or deliver the related
goods/services within the period(s) specified in this Contract and/or according to the service
levels defined, ADB may deduct from the Contract Price, Liquidated Damages. Penalties will
be 5% of the payment for that milestone in which more than two service level requirements
(as defined in Service Level Agreement (SLA)) are exceeded.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
Metrics Criteria
Reporting
Frequency
Description
Target Metrics
Measurement Method
Response Time
Measure the time it takes for the MVP
to respond to user requests.
1 second for page loads .
Monthly
Error Rate
Rate of error based on number of
failed request over total number of
request
no more than 1%
Bugs Resolution
Time
Timely resolution of bugs reported in
the MVP, thereby maintaining a high
level of system reliability and user
satisfaction.
Critical Bugs:
Within 24 hours of reporting.
Major Bugs:
Within 3 business days of
reporting.
Minor Bugs:
Within 7 business days of reporting
Response time shall be measured
using appropriate monitoring tools at
regular intervals (e.g., every 5
minutes).
Error rate shall be calculated based
on the number of failed requests
divided by the total number of
requests made.
The time taken to resolve each
reported bug shall be measured from
the moment it is officially reported or
logged by users or the internal testing
team to the time when the resolution
is confirmed and implemented.
Scalability
MVP's performance as user traffic
and data volumes increase. Ensure
that the system can scale to
accommodate growth without
significant degradation in
performance or functionality.
The MVP shall scale
dynamically to accommodate
increased user traffic and data
volumes without significant
degradation in performance.
Scalability shall be assessed through
load testing under simulated hightraffic conditions. Real-time
monitoring shall be implemented to
track key performance indicators
related to scalability, such as CPU
utilization, memory usage, and
network throughput.
The completeness of features shall
be evaluated against a predefined
feature checklist or requirements
documentation.
Monthly
User stories shall be tracked and
monitored using PM tools, with
completion status.
Monthly
Feature
Completeness
Ensure that the MVP delivers
essential features and functionalities
as per the defined scope, meeting
user requirements and expectations.
Featured Checklist:
The MVP shall include all
essential features and
functionalities identified in the
project requirements and
specifications.
User Story Completion:
All user stories associated with
essential features shall be
implemented and marked as
completed within the agreedupon development sprints.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Monthly
Monthly
Monthly
Classification: INTERNAL
Uptime
Ensure that the MVP is available and
accessible to users for a significant
portion of the time.
Acceptance Criteria
Satisfaction:
All features and functionalities
shall meet the acceptance
criteria defined by stakeholders
and end users.
uptime of 99.9%
Acceptance criteria shall be
documented for each feature or user
story, and feature completeness
shall be evaluated based on the
satisfaction of these criteria during
user acceptance testing.
Uptime shall be calculated based on
the total available time versus the
actual downtime experienced by
users
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Monthly
Monthly
Classification: INTERNAL
10.2
Place of performance
• The services will be delivered in hybrid mode.
• Planning of onsite and offsite work needs to be done between the Solution Partner and the
ADB Project Manager. If either ADB and/or the Solution Partner deems it necessary to
work on-site in ADB Headquarters, the parties shall agree on the deployment of the
Solution Partner’s personnel. The Solution Partner shall be available for extended support
after normal working hours during critical times as needed by the project. The Solution
Partner shall be responsible in securing the necessary requirements such as appropriate
travel visas (as applicable), hotel accommodation, airline ticket, and Daily Subsistence
Allowance (DSA), which shall cover all travel related expenses such as local transportation,
airport transportation, meals, personal incidental expenses including tips, laundry, and
phone calls, among others. ADB will reimburse travel expenses incurred by the solution
provider subject to ADB’s travel ceiling rates and terms and conditions which will be
discussed during contract negotiations.
•
The Solution Partner shall ensure that its personnel are covered by appropriate travel,
health, and other related insurance to cover accidents or sickness while in transit to and
working in the ADB Headquarters. ADB is not liable to cover additional travel expenses
resulting from these incidents.
10.3
Working days and business hours
• Working hours in ADB Headquarters in Manila, Philippines, are between the hours of 9:00
AM and 6:00 PM, Mondays through Fridays, including Philippine public holidays but
excluding ADB holidays.
•
The official ADB holidays are listed below and will be strictly followed. The vendor is to be
aware of these dates and align them with scheduled meetings, tasks, and deliverables.
Refer to this link for the calendar of ADB holidays.
10.4
Identification and Conduct
• Vendor personnel working or visiting on-site at ADB facilities must display ADB-issued
identification and visitor badges in plain view above the waist at all times.
• All personnel deployed by the said vendor must identify themselves as representatives
when their status is not readily apparent.
• Vendor personnel must comply with all applicable ADB and public regulations, policies,
and procedures (e.g., fire, safety, security, sanitation) when visiting or working at ADB
facilities. They must ensure a professional appearance at all times, and their conduct must
not bring discredit upon ADB and their respective organization.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
10.5
Intellectual Property
• All developed documentation, processes, procedures, source code, configuration files,
resolutions, fixes, workarounds, training materials, and other forms of intellectual
property developed under this SOW will be considered ADB property unless otherwise
discussed and mutually agreed upon by ADB and the Provider on a case-to-case basis.
•
With ADB taking ownership of the documentation produced by the Provider, ADB
reserves the right to reproduce or distribute said documentation for official purposes.
10.6
Milestone Payment Schedule
ACTIVITY
PAYMENT PERCENTAGE
Initial Payment (Contract Award)
20% of project cost
Upon successful completion of:
• Development / Sprint #1
• Development / Sprint #2
• Development / Sprint #3
Upon Successful Completion of
• Sprint #4
• Sprint #5
• MVP, final review and testing
• Project Acceptance Certificate Sign-off
and completion of transition activities
40% of project cost
40% of project cost
10.7
Confidentiality Statement
• All data and information received from ADB for this project should be treated with
confidentiality and used only in connection with the execution of this project. The
contents of written materials obtained and used in this assignment may not be disclosed
to any third parties without the express advance written authorization of ADB.
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
11 Appendixes
1.1 ADB Engineering Standards
• ADB Integration Principles v1.0
• ADB Software Engineering Standards
• ADB Java Coding Standard
• Secure Coding Guidelines.pdf
1.2 High-level Solution Design
High-Level Solution Design Template v1.3a.docx
1.3 ADB ITD Security Guardrails
• ITD Security Guardrails.docx
• SLTO_Guardrails Template.xlsx
1.4 ADB Project Management Framework (PMF)
ADB Project Management Framework (PMF)
1.5 SDLC Operations Manual
ITD Software Development Lifecycle - Operations Manual
1.6 ADB Handbook of Style and Usage
ADB Handbook of Style and Usage
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.
Classification: INTERNAL
12 Potential Future Deployment to Production
This may be considered in the future, and if materialized, the current known requirements are documented in the attached
appendix.
Annex - Functional
Requirements FVP.docx
13 SOW Acceptance
Authorized representatives of ADB and the Solution Provider must affix their signatures below to signify their understanding and
acceptance of the details indicated in this document.
ACCEPTED BY:
ACCEPTED BY:
Asian Development Bank
Solution Provider
Name:
Name:
(Please print)
(Please print)
Title:
Title:
(Please print)
(Please print)
Signature:
Signature:
Date:
Date:
INTERNAL. This information is accessible to ADB Management and staff. It may be shared outside ADB with appropriate permission.