|
1 | | -The following work steps are required for the national implementation of the DPG carbon registry in any country. |
| 1 | +# Sample Terms of Reference |
| 2 | +The TOR can be further specified if national details are known, e.g. about the NDC management tool. |
| 3 | +These worksteps can also be intergrated with larger TORs, especially TORs covering wider NDC management / transparency. Below are sample phrases that may be used. Generally a vendor (firm) or a group of individual consultant are encouraged, as the required skills vary. |
| 4 | + |
| 5 | +## 1. Installation |
| 6 | +The following work steps are suggested for the national implementation of the DPG carbon registry in any country. |
2 | 7 |
|
3 | 8 | - Installation of a Carbon Registry from https://github.com/undp/carbon-registry |
4 | 9 |
|
| 10 | +- Technical timeline/roadmap |
| 11 | +- Fork the [Carbon Registry](https://github.com/undp/carbon-registry). Send pull requests to `staging` for added features (languages, security patchees, modules, etc.). |
| 12 | + |
5 | 13 | - Initial Setup of the Carbon Registry, including localization to national requirements: |
6 | | - - translation into relevant national languages *(Link to the .json/yaml files that need translation HERE)* |
7 | | - - adjust sectors to match the sectors specified in the nationally determined contribution *(link to file that specifies sectors HERE)* |
8 | | - - integration with existing NDC management tools (if applicable) |
| 14 | + - translation of text into relevant national languages |
| 15 | + - adjust colors, logos, maps, etc. to national standard |
| 16 | + - design graphics |
| 17 | + - purchase domain, hosting, & security certificate |
| 18 | + - register & connect supporting services (analytics, forms, etc.) |
| 19 | + - adjust sectors to match the sectors specified in the nationally determined contribution |
| 20 | + - integration with existing NDC management tools (if applicable) [API] |
9 | 21 | - adjustment of user types to national requirements |
10 | 22 | - creation of government accounts |
11 | | -*(Deliverable: Fully localized Carbon Registry running on test environment)* |
| 23 | + - status page for monitoring uptime, utlizing https://github.com/undp/carbon-registry-status |
| 24 | + - *(Deliverable: Fully localized Carbon Registry running on staging (test) environment & productive (live) environment)* |
12 | 25 |
|
13 | 26 | - Successful end-to-end test of the registry. This test needs to cover the full lifecycle of one dummy project including at least project creation, authorization, implementation, MRV, issuance and transfer. |
14 | 27 | *(Deliverable: Test Report)* |
15 | 28 | - Creation of a nationally appropriate signup proceedure for non-government accounts |
16 | 29 | - Hand over to official government use |
17 | | -*(Deliverable: Government Acceptance)* |
| 30 | +*(Deliverable: Government Acceptance. Source code submission (ideally on `GitHub`) approved.)* |
| 31 | +- Testing: Security, Privacy, Accessability. *(Deliverable: 3rd party and/or automated tests.)* |
| 32 | +- Ticketing system: For submitting, tracking, & responding to platform requests & bugs. |
| 33 | +- Warranty: Supporting long term web hosting and operation (DevOps) of the registry |
| 34 | +- Training: manual. video/screen recording walkthrough. guidebook. workshops. |
| 35 | +- Awareness: advertising. community outreach. |
18 | 36 |
|
19 | | -- Long term hosting and DevOps of the registry |
| 37 | +## 2. Scope of Work |
| 38 | +- Design |
| 39 | + - User Interface (UI) Design |
| 40 | + - Real-Time Reviewing & Commenting Mechanism |
| 41 | +- Quality Assurance (QA) & User Testing |
| 42 | + - Internal Test with SME for the MVP version |
| 43 | +- Software Development |
| 44 | + - Cloud-Based Containerized Web-Application for Desktop users |
| 45 | + - DevOps, including Hosting Page |
| 46 | + - Analytics |
| 47 | + - Accessibility |
| 48 | +- Handover & Training |
| 49 | + - Video/screen recording walkthrough |
| 50 | + - Source code to be submitted to the official UNDP GitHub repository with full source documentation, use cases, and functional requirements. |
| 51 | +- Support & Maintenance |
| 52 | + - x months of maintenance |
| 53 | + - y days per month are required |
| 54 | + - Service Level Agreement (SLA): |
20 | 55 |
|
21 | | -Sample Terms of Reference |
22 | | -The TOR can be further specified if national details are known, e.g. about the NDC management tool. |
23 | | -These worksteps can also be intergrated with larger TORs, especially TORs covering wider NDC management / transparency. Below are sample phrases that may be used. Generally a vendor (firm) or a group of individual consultant are encouraged, as the required skills vary. |
24 | 56 |
|
25 | | -1. Scope of Work |
| 57 | +|Critical Level| Response Time| Resolution Time| |
| 58 | +|---|---|---| |
| 59 | +|Critical (System down)| <10 mins| <2 hours| |
| 60 | +High| <30 mins <4 hours| |
| 61 | +Medium| <4 hours| <48 hours| |
| 62 | +Low| < 48 hours| <3 days| |
| 63 | +Planning| < 48 hours| < 5 days| |
26 | 64 |
|
27 | | -3. Deliverables |
| 65 | + |
| 66 | + |
| 67 | +## 3. Deliverables |
28 | 68 | - Deliverable 1: |
29 | 69 | - Deliverable 2: |
30 | 70 | - Deliverable 3: |
31 | 71 | - Deliverable 4: Maintenance of the registry (This is optional, however highly recommended to ensure upgrade and security checks) |
32 | 72 |
|
| 73 | +### Deliverable Requirements |
| 74 | + |
| 75 | +- AGPL-3.0 software license |
| 76 | +- UNDP Data Principles Adherence [https://data.undp.org/data-principles/](https://data.undp.org/data-principles/) |
| 77 | +- Contributor Covenant Code of Conduct Adherence |
| 78 | +- Reporting |
| 79 | +- GDPR-compliant Analytics |
| 80 | +- Notifications |
| 81 | + - Email notifications and reports |
| 82 | +- Infrastructure |
| 83 | + - Cloud-based |
| 84 | + - Regular data export and/or backups |
| 85 | + - Staging & Production environments |
| 86 | + - DevOps |
| 87 | + - Status page |
| 88 | + - Domain & security certificate management |
| 89 | + - Containerized |
| 90 | +- Accessibility Compliance (W3C) |
| 91 | +- Audit: Internal |
| 92 | +- Multi-Language Support |
| 93 | +- Ticketing system |
| 94 | +- Service level agreement (SLA) |
| 95 | +- Platform(s): Desktop Web |
| 96 | +- Integrations |
| 97 | + - UNDP ITMO Platform |
| 98 | +- Privacy & Security |
| 99 | + - Security audit: External |
| 100 | + - Privacy audit: Internal documentation of adherence to UNDP Data Principles |
| 101 | + |
33 | 102 | Other items to consider: |
34 | 103 | - Hosting / clound server: |
35 | 104 | - The ToR is based on the assumption that he government entity has or will prepare a hosting environment in a cloud server. If the government does not have a server space, consider if the vendor will need to host the registry. If so, consider if the vendor can be contracted for a long term. |
36 | | -- Server specs- |
| 105 | +- Server specifications: TBD |
37 | 106 |
|
38 | | -4. Required persons / skills |
39 | | - - Developer 1: |
40 | | - - Developer 2: |
| 107 | +## 4. Required persons / skills |
| 108 | + - Developers (x2): |
| 109 | + - At least 5 years of previous working experience in Web development with front-end and back-end is required; |
| 110 | + - Previous experience with human-centered design and agile software development and methodology is preferred; |
| 111 | + - Demonstrated experience in JavaScript, Html5, CSS3, (Angular; ReactJS; Vue.JS…) for front end development is strongly preferred |
| 112 | + - Proven previous experience in API programming (NodeJS /PHP…) is an advantage |
| 113 | + - Demonstrated experience in Database Development: e.g. MSSQL, MariaDB, MySQL, Oracle, PostgreSQL is an asset |
| 114 | + - Demonstrated proficiency in DevOps: Azure DevOps, Docker, Git, Deployment pipeline, test automation is preferred |
41 | 115 | - Project manager: |
42 | | - - Carbon or stakeholder engagement expert (optional) |
| 116 | + - Minimum of 5 years of product management experience, with at least 2 years working in a startup environment |
| 117 | + - Have shipped at least 1 digital product with proven impact. |
| 118 | + - Been working with quantitative and qualitative Data |
| 119 | + - Digitally competent and have a high drive for understanding and meeting users needs |
| 120 | + - Experience in start-ups, with Agile methodology as well as UX are a plus but not a requirement |
| 121 | + - Strong project manager and have experience in leading cross-functional project teams |
| 122 | + - Ability to solve complicated problems and understanding end-customer needs are part of your core strengths |
| 123 | + |
| 124 | + - Carbon or stakeholder engagement expert - local and/or (optional) |
| 125 | + - At least 5 years experience in climate policies, carbon markets and other green financing mechanisms are required |
| 126 | + - Knowledge of digital technology or digitalization is strongly desired |
| 127 | + - Direct experience related to mitigation outcome agreements at the national or international level is strongly desired |
| 128 | + - Direct experience in developing or overseeing digital systems related to climate or carbon reporting, accounting, measurement, verification is strongly desired |
| 129 | + - Experience in business development and entrepreneurship is an asset |
0 commit comments