Flows/Set up the example and send the request

Flows

Set up the example and send the request

Main story · The customer keeps the prepared example or picks the other industry, gets the STS label and sends the request to the three suppliers.

Who
The presenter, acting as the customer, Velmora Battery Works
Starts at
Setup with the default lithium chain
Ends with
The Chain view, each supplier’s step requested
Step 1 of 7 This screen is not drawn yet
  1. 1 The prepared example

    Presenter’s control

    Setup

    Prepared example · Lithium-ion batteries

    Industry and companiesFive inputs, nothing else by hand
    Industry
    Lithium-ion batteriesFood packagingAnother industry…
    The two prepared industries need no AI; another is generated, if time allows.
    Originating company ID · QuillaraLithium
    Originating company ID · BrisemontRefining
    Originating company ID · FerrovaneFreight
    Originating company ID · VelmoraBatteryWorks

    Each ID is the prefix urn:pact:company:customcode:buyer-assigned: and the code. Setup issues them; they are never typed.

    A change starts the walkthrough overA new name renames the example at once, without the AI, and its ID with it; another prepared industry puts its own example in place. Once a request has been sent, you confirm first what is discarded.
    What the example holds
    IndustryLithium-ion batteries
    PartiesFour, in chain order
    1. QQuillara LithiumMine
    2. BBrisemont RefiningRefiner
    3. FFerrovane FreightCarrier
    4. VVelmora Battery WorksCustomer
    ContainerCNT-BR-0417
    ContentsBattery-grade lithium carbonate · 15.6 t
    Made fromLithium concentrate · 24 t

    The figures and the response documents stay with the suppliers: this screen shows neither.

    Sees the industry, the four companies with their IDs and the container. Keeps the example — or changes a name 1, which renames the example at once without the AI, or picks the other prepared industry — and presses Apply 2. Once a request has been sent, applying a change first names what it discards and asks to confirm; that is not drawn as a step.

  2. 2 Generating (another industry, if time allows)

    Setup

    Another industry · generating

    Industry and companiesFive inputs, nothing else by hand
    Not a prepared industry: generated by the AI.
    Originating company ID · QuillaraLithium
    Originating company ID · BrisemontRefining
    Originating company ID · FerrovaneFreight
    Originating company ID · VelmoraBatteryWorks

    Each ID is the prefix urn:pact:company:customcode:buyer-assigned: and the code. Setup issues them; they are never typed.

    The walkthrough waitsNo request is sent and no party acts until the example is ready. The presenter’s control comes back with it.
    What the example holds
    Generating the example… The parties, the container, the figures and the three response documents are built from the five inputs. The result appears here.

    Only an industry that is not prepared is generated by the AI — if time allows; a new name or the other prepared industry is in place at once, and this step is skipped. While it generates, the Setup screen stands alone: the presenter’s control is hidden, and the result appears where the summary was. Nothing to act on.

  3. 3 The example in place

    Presenter’s control

    Setup

    Prepared example · Lithium-ion batteries

    Industry and companiesFive inputs, nothing else by hand
    Industry
    Lithium-ion batteriesFood packagingAnother industry…
    The two prepared industries need no AI; another is generated, if time allows.
    Originating company ID · QuillaraLithium
    Originating company ID · BrisemontRefining
    Originating company ID · FerrovaneFreight
    Originating company ID · VelmoraBatteryWorks

    Each ID is the prefix urn:pact:company:customcode:buyer-assigned: and the code. Setup issues them; they are never typed.

    A change starts the walkthrough overA new name renames the example at once, without the AI, and its ID with it; another prepared industry puts its own example in place. Once a request has been sent, you confirm first what is discarded.
    What the example holds
    IndustryLithium-ion batteries
    PartiesFour, in chain order
    1. QQuillara LithiumMine
    2. BBrisemont RefiningRefiner
    3. FFerrovane FreightCarrier
    4. VVelmora Battery WorksCustomer
    ContainerCNT-BR-0417
    ContentsBattery-grade lithium carbonate · 15.6 t
    Made fromLithium concentrate · 24 t

    The figures and the response documents stay with the suppliers: this screen shows neither.

    Sees Setup with the new example in place; the label is already created. Opens Label and request 1 in the menu.

  4. 4 The label

    Presenter’s control

    Label and request

    CNT-BR-0417 · The STS label for the container

    Label created
    ProfileLithium-ion batteries · Battery-grade lithium carbonate, t
    1. QQuillaraextraction · Cat 1
    2. BBrisemontprocessing · Cat 1
    3. FFerrovanetransportation · Cat 4
    4. VVelmoracustomer
    #The six mandatory fields
    1Originating company IDThe party the value comes from, as Setup issued its ID.
    2Units of measurementThe unit the document gives each figure, shown as written.
    3Source of dataWhere a value came from, in the document’s words.
    4VerificationSelf-verified, or audited with the verifier named.
    5Scope 3 emissionsEmbedded in the material at hand-over: own figure plus what arrived.
    6How the Scope 3 were producedThe own figure — Scope 1–2, or transport — plus what arrived.
    What each supplier receives
    Addressed toQuillara Brisemont Ferrovane
    ContainerCNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t
    AsksThe six fields and the eight questions, each emission figure with its method flag
    SentTo all three at once, directly — not along the chain
    #The eight label questions
    1Who generated the emissions?The party that reported them.
    2What activity caused them?The business event of the party’s step, as the profile names it.
    3Which product do they impact?The product the emissions are attributed to.
    4Where did they occur?The place of the party’s facility.
    5How were they calculated?The document’s description, with its allocation to the material.
    6When did they occur?The period the emissions cover.
    7Which STS transactions support the calculation?The parent transactions the figures rest on, from the chain.
    8How do they roll up into Scope 3 reporting?The roll-up rule, stated once in the label.
    The field names are the demo’s ownNo STS dictionary exists yet, so these names are the demo’s. The roll-up rule is stated once, as the answer to question 8.

    Sees the STS label: its profile — the industry, the product, and each place with its party, event and Scope 3 category, the part that follows the example — then the six fields, the eight questions and what each supplier receives. Opens Label definition 1 before sending; Send request 2 is the next action.

  5. 5 The label definition

    Presenter’s control

    Label definition

    The demo’s own: no STS dictionary exists yet, and the working group will define it · the same for every party

    Read only
    #FieldUnitComes fromWhen there is none
    1Originating company IDThe party a value comes from.—The requestnever missing
    2Units of measurementEach figure’s unit, as written.—The documentan error
    3Source of dataWhere a value came from.—The documentan error
    4VerificationSelf-verified, or audited and by whom.—The documentan error
    5Scope 3 emissionsEmissions embedded in the material at hand-over — the party’s own figure plus what arrived with the material. The buyer counts it in its Scope 3; the profile says which category each part falls in.tCO2eRoll-up: own + receivedawaiting upstream
    6How the Scope 3 were producedThe own figure — Scope 1–2, or the transport of the container — plus what arrived.tCO2eDocument and parentan error
    7Method flagMeasured, or estimated and how.—The documentan error
    8Embedded emissions receivedWhat arrived with the material: the upstream party’s reported total.tCO2eThe parent transactionawaiting upstream
    #QuestionComes fromWhen there is none
    1–6Who generated the emissions, what activity, which product, where, how calculated, when?The documentnot stated
    7Which STS transactions support the calculation?The chain: the parent links—
    8How do they roll up into Scope 3 reporting?The roll-up rule—
    Rules
    Applies toOne container, CNT-BR-0417
    AllocationEach supplier allocates its own emissions to the material in this container and says how; the demo computes no allocation or yield.
    Roll-upOwn + received is what a party passes on; the customer’s Scope 3 is the carrier’s total
    Document termThe supplier’s own name for a value, shown beside it in the review

    Sees the label as a semantic layer, read only: each field’s meaning, unit, where its value comes from and what stands in when there is none, and the rules — among them that each supplier allocates its own emissions to the material in the container and says how. Goes back to Label and request 1 and presses Send request; it is not confirmed.

  6. 6 Request sent

    Presenter’s control

    Label and request

    CNT-BR-0417 · The STS label for the container

    Label requested
    Request sent to the three suppliersAll three at once, directly from the customer. Each supplier now has the request addressed to it; the chain view shows each step as requested.
    SupplierOriginating company IDEventRequest
    QQuillara LithiumQuillaraLithiumExtractionRequested
    BBrisemont RefiningBrisemontRefiningProcessingRequested
    FFerrovane FreightFerrovaneFreightTransportationRequested
    What each supplier receives
    Addressed toQuillara Brisemont Ferrovane
    ContainerCNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t
    AsksThe six fields and the eight questions, each emission figure with its method flag
    SentTo all three at once, directly — not along the chain

    The request is sent at 14:20: sees the three suppliers, each requested. Opens Chain view 1.

  7. 7 The chain

    Presenter’s control

    Chain view

    CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

    Chain incomplete
    1. Q
      Quillara LithiumMine · extraction

      24 t lithium concentrate

      Requested

      No transaction yet

    2. B
      Brisemont RefiningRefiner · processing

      24 t concentrate → 15.6 t lithium carbonate

      Requested

      No transaction yet

    3. F
      Ferrovane FreightCarrier · transportation

      CNT-BR-0417 · 15.6 t, Mejillones → Austin

      Requested

      No transaction yet

    4. V
      Velmora Battery WorksCustomer · end of the chain

      CNT-BR-0417 delivered

      No transaction of its own

    No roll-up yet Nothing has responded. The roll-up appears once each of the three steps has had a transaction.

    Sees the path mine → refiner → carrier → customer, each step with what it handled — the concentrate, the carbonate, the container on its way — each supplier’s step requested and no roll-up yet. The request is out; the suppliers answer next.