Project

Questions for AKFI

What your answers of 22 October leave open — and what we took from the answers you already gave, so nothing is asked twice.

Still open

Nine questions, each with the answer we go with until you say otherwise.

Your answers of 22 October settle most of the demo. These nine are what they leave open, or what the thread did not touch. Each has the answer we go with until you say otherwise; a yes, a no or a change is all we need.

One chain of three suppliers in one industry — or three companies from different industries?

Until you answer, we go with: One chain, mine → refiner → carrier, so the label visibly travels with one container; the second prepared industry shows that the label changes with the customer’s choice. You wrote “3 suppliers” on 22 October and sent a linear chain, but on 20 October “three companies from different industries”.
Why it matters: It shapes the data, the screens and the roll-up; the two readings make two different demos.

Is a second customer shown by renaming the example enough — or do you want two or three customers side by side?

Until you answer, we go with: One customer; a second one is the example renamed at setup, which takes seconds and no AI. You wrote that 2–3 customers would be better “if the design effort is minimal”.
Why it matters: Each customer side by side is one more chain to prepare, rehearse and show in the same sitting.

Who runs the demo — a presenter in front of the working group, or members trying it themselves from a link?

Until you answer, we go with: A presenter-led walkthrough, one presenter playing every party; a link to this site can go to members after the session. The notes say the demo should be “shareable with STS working group members”; how is not said.
Why it matters: Self-service needs hosting, access for each member and an AI part that holds up without a presenter beside it.

When is the working-group session the demo is for, and who presents — you or us?

Until you answer, we go with: We build in one to two days and rehearse before the session, with the presenter of your choice.
Why it matters: It sets when the build and the rehearsal happen, and whom we rehearse with.

Which name should the demo carry — “STS Exchange Platform” from our design concept, or a neutral STS or AKFI name?

Until you answer, we go with: “STS Exchange Platform”, the name of the concept you saw on 15 October, with a mark of synthetic data on every screen and no company’s logo.
Why it matters: STS is a standard of the whole industry; a product name may read as one vendor’s before the working group.

Should each supplier allocate its own site emissions to the material in this container, and say how?

Until you answer, we go with: Yes: each document states its basis and share — by mass here, 1 % of the quarter’s output — and the demo computes no allocation or yield. You said one container; how a supplier’s quarter becomes one container’s figure is not said.
Why it matters: It is the first question a supply-chain expert asks.

Is it acceptable that a supplier sees the previous party’s total — the refiner the mine’s 23.3 tCO2e, the carrier the refiner’s 35.7?

Until you answer, we go with: Yes, in the demo: the figure travels with the material, as in your STS Flow example; no supplier ever sees another’s document. You ruled out the customer seeing a supplier’s file; figures passed down the chain were not discussed.
Why it matters: It is what makes the label travel — and it shares a figure with a party further down the chain.

Keep your Category 11 example query, or replace it with one this chain can answer?

Until you answer, we go with: Kept, answered “not in this chain yet”: the buyers of the batteries would report it, downstream of the customer.
Why it matters: It is the one query of the five the chain cannot answer with a figure.

May the five example queries follow the example — for food packaging, “PET recycling” and “Category 12, end-of-life treatment”?

Until you answer, we go with: Yes: your wording is kept where it fits; lithium extraction and Category 11 make no sense for food trays.
Why it matters: Without it the second industry speaks batteries from the first query on.

Already answered

Your own words, and what the demo does with them.

What we took from the answers you already gave — not asked again. Tell us only where we misread you.

You wrote

“3 suppliers, use an example you have already data in Apiko.” · “For the demo use one container.”

So the demo

Three suppliers and one container. We have no client data we may show, so the example is synthetic, built on your STS Flow example.

You wrote

“For the demo, just show how the STS ‘label’ tracks the movement of product along the supply chain.”

So the demo

One label for one container; each step names the material it handled, and the figure travels with it to the customer.

You wrote

“Created dynamically based on the customer input (they should select the industry and the companies involved).” · “Allow the customer to change the industries and companies names.”

So the demo

The customer picks one of two prepared industries or renames the companies, and the label follows; live generation for any other industry if time allows.

You wrote

“The STS must be developed by the industry, not by us.”

So the demo

No STS dictionary exists, so the label’s names and definitions are the demo’s own, borrowing PACT’s where they fit, and the screen says so.

You wrote

“Originating company ID, Units of measurement, source of data, verification …, Scope 3 emissions, how the Scope 3 were produced (calculated from Scope 1‑2 internal and Scope 3 from supplier listed in the supply chain).”

So the demo

Your six fields and eight questions, as listed. Each party’s Scope 3 is its own Scope 1–2 plus what arrived with the material; the customer’s Scope 3 is the last supplier’s total, split into Category 1 and Category 4 as the GHG Protocol reads it.

You wrote

“I would use a simple text document e.g. PDF.”

So the demo

Each supplier uploads its own PDF in its own layout; collecting data automatically from systems such as an MMS stays beyond the demo.

You wrote

“Unavailable should produce an error.” · Problem cases: “Not for the demo. Yes, for a MVP …” · “Demo just the display unit in the STS ‘label’.”

So the demo

A missing mandatory value, unit or measured / estimated flag is an error that names what is missing; no consistency checks, conflicts or unit conversion.

You wrote

“Not for the demo — yes for the proof of concept, or MVP.”

So the demo

The supplier confirms nothing before the customer’s review; it can read its own label, read only.

You wrote

“Accepting, or request for clarifications.” · Clarification rounds: “No needed for a demo.” · The original file: “No for security/privacy reasons.”

So the demo

Accept, or request clarification with a note — no rounds; an answer by a new document is ready only if you want it. The customer reads labelled values, never the supplier’s file.

You wrote

“Since customer can use BI or AI, any of these formats are ok.” · Custom-trained, privately hosted model: “No.”

So the demo

CSV, with Excel and JSON if time allows; an existing AI service, synthetic data only.

You wrote

“Focus on one clear Scope 3 example” · “a minimal, concrete illustration, not a product build.”

So the demo

Scope 3 emissions only — not the water, renewable, social and governance fields or the per-battery footprint of your STS Flow example; no accounts, dashboards or integrations from our design concept.

You sent

Your STS Flow example, “Lithium Mine to Battery Manufacturer”, five parties.

So the demo

Four parties in ours: the rail leg from the mine to the refinery is inside the mine’s figure, Category 1 under the GHG Protocol; the one transport transaction is the refiner-to-customer leg, Category 4.

The short spec

The 1–2 page product spec agreed on 16 October.

The short product spec agreed on 16 October — what the demo is, its scenario, its label, what is in and out, and the open questions — is a page of this site, ready to print or save as PDF: Demo specification.