SeqCarbon - Demo

Agriculture is a fundamental and global human operation, unfortunately its current form focuses on financial profitability, not sustainability. The first step of changing this is reliable and viable data collection. This is a complex task: our models are partial and should improve along the process of data collection and evaluation, while different actors with different motivations already use the system.

This prototype demonstrates a working approach to this data collection, local footprint calculation and communication over the value chain. If this is your first time here, please familiarise yourself with the system architecture, then follow the links on this page to the Static, Dynamic and Technical sections of the demo. You can read a bit more about the project in the about section.

As you will see, all pages have the same structure:

Please be aware that this is a public portal and you may not be the only one interacting with the Dynamic part, the data may change due to someone else’s activity.

You can reload all data to return to the original state (login with "SeqCarbon"" entity, "trusted" user).

Static Demo

This first section was used to verify the technical components and some of the core architecture concepts in a “snapshot”. The values are calculated manually, there is no UsedResource collection, only Assets, Jobs, Products and Footprints.

However, you can see the activities of its three entities:

Dynamic Demo

The dynamic part has access control, but for your convenience, the login page is pre-loaded with the test user and its password. You only should check the Entity and click Login. If you want to check all Entities without security issues, please select the SeqCarbon entity and use the “trusted” user with the same password. The three entities are similar (LabFarm2, LabMerchant2, LabProcessor2), but you should complete actions here.

  1. LabFarm2 is an empty placeholder, but the demo contains the LabFarm2_2024.xlsx file with a complete configuration.
  2. Use this import link to load the content of the file, then check the LabFarm2 page again, you will see all items loaded.
  3. Scroll down to the Job list, where initially all Jobs are in Planned state, and you have an Execute button. Clicking it executes the selected one together with all the previous ones in date order, they modify various data items and switch to Done state, the Execute button disappears.
  4. The first two Buy Jobs fill the StockMaterial inventory, the next ones prepare the Parcel, Sowing creates the Plantation, further Cultivation Jobs treat it with StockMaterials, Harvesting creates the Crop and Straw Products, etc. You can execute the Jobs in blocks or go down and execute the last Sell job to see all changes at once.
  5. While executing the Jobs, you can follow the UsedResources collection growing for the target items.
    1. First everything is added to the Parcel.
    2. Sowing creates the Plantation that inherits the collection from the Parcel and after this, it starts growing.
    3. Harvesting creates the Crop Product that inherits its attributes and resource collection from the Plantation.
  6. Then you can switch to LabMerchant2, and follow a similar roadmap, here you can see how various local Jobs work with UsedResources, Total and Scope3 Footprint (updated after executing Sell). You will also see some “Test” Jobs that simulate some taking some locally defined measurements by creating ExtItem instances filled with random values. After you executed the Sell Job, you can switch to LabProcessor2 and execute Buy to see the Product data loaded from the source at LabMerchant2.
  7. The top line of the Footprint property sheet contains an XBRL button that generates an XBRL instance following the VSME standard. This could be the primary form of sending Footprint information to an external buyer, utilising the extensible nature and the mature infrastructure behind the established XBRL standard. However, you can also save a CSV export of the same data to demonstrate that the system can fulfil other requirements as well.

Technical Notes