| Nov. 27, 2023, 2:14 p.m. |
Added
35
|
{"external_links": []}
|
|
| Nov. 20, 2023, 2:04 p.m. |
Added
35
|
{"external_links": []}
|
|
| Nov. 13, 2023, 1:34 p.m. |
Added
35
|
{"external_links": []}
|
|
| Nov. 6, 2023, 1:32 p.m. |
Added
35
|
{"external_links": []}
|
|
| Aug. 14, 2023, 1:31 p.m. |
Added
35
|
{"external_links": []}
|
|
| Aug. 7, 2023, 1:32 p.m. |
Added
35
|
{"external_links": []}
|
|
| July 31, 2023, 1:35 p.m. |
Added
35
|
{"external_links": []}
|
|
| July 24, 2023, 1:36 p.m. |
Added
35
|
{"external_links": []}
|
|
| July 17, 2023, 1:35 p.m. |
Added
35
|
{"external_links": []}
|
|
| July 10, 2023, 1:26 p.m. |
Added
35
|
{"external_links": []}
|
|
| July 3, 2023, 1:27 p.m. |
Added
35
|
{"external_links": []}
|
|
| June 26, 2023, 1:26 p.m. |
Added
35
|
{"external_links": []}
|
|
| June 19, 2023, 1:27 p.m. |
Added
35
|
{"external_links": []}
|
|
| June 12, 2023, 1:30 p.m. |
Added
35
|
{"external_links": []}
|
|
| June 5, 2023, 1:34 p.m. |
Added
35
|
{"external_links": []}
|
|
| May 29, 2023, 1:28 p.m. |
Added
35
|
{"external_links": []}
|
|
| May 22, 2023, 1:30 p.m. |
Added
35
|
{"external_links": []}
|
|
| May 15, 2023, 1:32 p.m. |
Added
35
|
{"external_links": []}
|
|
| May 8, 2023, 1:38 p.m. |
Added
35
|
{"external_links": []}
|
|
| May 1, 2023, 1:28 p.m. |
Added
35
|
{"external_links": []}
|
|
| April 24, 2023, 1:35 p.m. |
Added
35
|
{"external_links": []}
|
|
| April 17, 2023, 1:29 p.m. |
Added
35
|
{"external_links": []}
|
|
| April 10, 2023, 1:25 p.m. |
Added
35
|
{"external_links": []}
|
|
| April 3, 2023, 1:27 p.m. |
Added
35
|
{"external_links": []}
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
43
|
[{"model": "core.projectfund", "pk": 31293, "fields": {"project": 8519, "organisation": 4, "amount": 49448, "start_date": "2022-11-01", "end_date": "2023-04-29", "raw_data": 43011}}]
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
41
|
[{"model": "core.projectorganisation", "pk": 88995, "fields": {"project": 8519, "organisation": 10265, "role": "PARTICIPANT_ORG"}}]
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
41
|
[{"model": "core.projectorganisation", "pk": 88994, "fields": {"project": 8519, "organisation": 10265, "role": "LEAD_ORG"}}]
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
40
|
[{"model": "core.projectperson", "pk": 55741, "fields": {"project": 8519, "person": 12007, "role": "PM_PER"}}]
|
|
| Jan. 28, 2023, 10:52 a.m. |
Updated
35
|
{"title": ["", "Carbon Accounting as a Service"], "description": ["", "\nThe concept behind the project is to provide a sensible and robust carbon accounting system as a core service to the carbon reporting markets. The differentiator of our product is that the system enables an entire auditing trail of carbon entries per line of data.\n\nWe have direct experience with carbon reporting systems that provide a reporting platform with good graphics. Such systems tend to be individual stand-alone systems, where the reporting teams tend to be environmentally based core teams. The methods generally do not interface well with corporate management business reporting platforms. This results in many of the current systems requiring excel based data dump to then be imported into the business accounting formats and media. Even then, the data sets tend not to be fully accounting systems.\n\nDuring 3rd party audits, there is a need to access external file directories to show proof of energy, fuel or material supply invoices. Probably with a set of hard or soft compy invoices required to be at hand to demonstrate accuracy.\n\nWe aim to provide a software tool that enables a complete audit trail showing the supply invoice number, transaction date, carbon conversion factors, either location or market based, the associated component values, and the associated asset which consumes the materials and/or fuels, whilst splitting our the carbon flows into the correct allocations, Scope, 1,2, 3 and Out of Scope categories under the Green House Protocol.\n\nBut we would also like to go one stage further, providing a carbon accounting tool that simply integrates with the corporate reporting platform. Many small and midsized clients use Microsoft Dynamic Business Central or Google G suite platforms. While larger clients use enterprise suite-level platforms of such systems. Our carbon reporting platform will be adopted to mesh with these systems to enable joined-up and smooth reporting without the need to provide excel based data dumps and importing steps as currently required.\n\nMaking the task of sustainability and carbon reporting more straightforward, more accessible and less costly for businesses. Our platform will be configured to the UK business model's reporting requirements, meeting the Energy Savings Opportunity Scheme (ESOS) needs. But within the ability to be adapted to the needs of the UK ETS system and Climate Change Agreement (CCA) schemes and Streamline Carbon and Energy Reporting (SECR) as needed.\n\nIn other words, the system will be flexible to meet the needs of the total UK market.\n\n"], "extra_text": ["", "\n\n\n\n"], "status": ["", "Active"]}
|
|
| Jan. 28, 2023, 10:52 a.m. |
Added
35
|
{"external_links": [34820]}
|
|
| Jan. 28, 2023, 10:52 a.m. |
Created
35
|
[{"model": "core.project", "pk": 8519, "fields": {"owner": null, "is_locked": false, "coped_id": "78d8e8c0-cca6-4ff0-b563-211480e135ea", "title": "", "description": "", "extra_text": "", "status": "", "start": null, "end": null, "raw_data": 42997, "created": "2023-01-28T10:49:17.077Z", "modified": "2023-01-28T10:49:17.077Z", "external_links": []}}]
|
|