| 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": 31554, "fields": {"project": 8780, "organisation": 4, "amount": 48763, "start_date": "2022-11-01", "end_date": "2023-04-29", "raw_data": 45612}}]
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
41
|
[{"model": "core.projectorganisation", "pk": 89793, "fields": {"project": 8780, "organisation": 10576, "role": "PARTICIPANT_ORG"}}]
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
41
|
[{"model": "core.projectorganisation", "pk": 89792, "fields": {"project": 8780, "organisation": 10576, "role": "LEAD_ORG"}}]
|
|
| Jan. 28, 2023, 11:09 a.m. |
Created
40
|
[{"model": "core.projectperson", "pk": 56356, "fields": {"project": 8780, "person": 12552, "role": "PM_PER"}}]
|
|
| Jan. 28, 2023, 10:52 a.m. |
Updated
35
|
{"title": ["", "AI enabled carbon footprint calculator"], "description": ["", "\nIncreasingly government legislation and companies are focused heavily on how they can significantly reduce the carbon footprint of emission intensive operations, the project **AI enabled carbon footprint calculator** will provide the ability to make decisions in real time to ensure we can achieve the best possible outcomes in relation to the environment and business sustainability and help with the pursuit of net-zero operations.\n\nThe project involves building a Business Intelligence reporting tool which will identify the amount of carbon different highway repair treatments use. Cost of the repair will also be considered, giving the Local Authority (LA) the information required to make informed decisions when choosing carbon saving over cost.\n\nThe report will take ordering data directly from the Authorities' Asset management system (Confirm/Symology etc) and by altering the proposed treatment type in the report give data on both monetary cost and the amount of carbon consumed.\n\nOnce the job has been completed the report will show the difference between the cost and the amount of carbon used, benchmarked against a traditional hot-lay patch, the proposed treatment and the final treatment, if different.\n\nThere will be a simple way for Local Authorities to be able to calculate the carbon cost for each type of treatment they use/propose to use which will be bespoke to them, ensuring local factors and methodology is considered in the calculations. This methodology will be independently verified to ensure it can be scrutinised by external parties.\n\nOnce set up it will need minimal management with only actual repair types entered into the data set. It is envisaged that all other data will be automatically retrieved from the LA's Asset Management system.\n\nThe resulting data will be presented in a number of visual reports giving clear information for both LA Officers and Elected Members.\n\n"], "extra_text": ["", "\n\n\n\n"], "status": ["", "Active"]}
|
|
| Jan. 28, 2023, 10:52 a.m. |
Added
35
|
{"external_links": [35922]}
|
|
| Jan. 28, 2023, 10:52 a.m. |
Created
35
|
[{"model": "core.project", "pk": 8780, "fields": {"owner": null, "is_locked": false, "coped_id": "e8df6eeb-c47e-47e0-afbe-81857d53091c", "title": "", "description": "", "extra_text": "", "status": "", "start": null, "end": null, "raw_data": 45596, "created": "2023-01-28T10:50:26.398Z", "modified": "2023-01-28T10:50:26.398Z", "external_links": []}}]
|
|