generated: '2026-07-27' method: searched source: https://github.com/SmartDCCInnovation/dccboxed-signing-tool summary: >- Smart DCC's sandbox is unusual: rather than a hosted test environment behind a test API key, it is a physical appliance (DCC Boxed) plus a published self-contained test PKI (ZAZ1) whose certificates AND private keys are deliberately shipped in the open so that anyone can sign and validate DUIS messages without touching the live network. There is no test-vs-live key prefix because there is no self-serve live key at all — live access requires Smart Energy Code accession, a DCC User Gateway Connection and SMKI certificates issued through the SMKI Registration Authority. environments: - name: DCC Boxed type: physical test appliance url: https://www.smartdcc.co.uk/our-smart-network/network-products-services/dcc-boxed/ description: >- An Intel NUC-based appliance that emulates the end-to-end smart metering network, aligned with the November 2023 SEC release with all device SRVs supported. Ships with a Zigbee traffic sniffer and USB hub; device emulators (electricity meter, in-home display, proportional load controller switch), a GFI Comms Hub and a Wired ITCH (Instrumented Test Communications Hub) are separately available. self_serve: false note: A commercial product ordered from Smart DCC, not a free hosted sandbox. - name: GFI type: predecessor test tool description: Ships with the same ZAZ1 test certificates and private keys as DCC Boxed. url: https://www.smartdcc.co.uk/our-smart-network/network-products-services/gfi/ - name: Testing Services type: managed test lab url: https://www.smartdcc.co.uk/our-smart-network/network-products-services/testing-services/ description: Smart DCC operates what it describes as Britain's largest secure test lab for customers to test products against the network. - name: Local signing tool type: self-hosted process description: >- The DCC Boxed DUIS signing tool runs entirely locally (default http://localhost:8080) and is preloaded with the ZAZ1 credentials, so signing and validation can be exercised with no appliance and no network access at all. spec: openapi/dcc-boxed-duis-signing-tool-openapi.yml test_pki: name: ZAZ1 description: >- A self-contained PKI for UK smart meter devices used for testing and validation. Used by DCC Boxed and by any smart energy devices attached to it. Documented verbatim in the dccboxed-keystore README. distributed_with: - DCC Boxed - GFI - dccboxed-signing-tool (ships the same test certificates and associated private keys) - '@smartdcc/dccboxed-keystore (keystore.json)' key_format: certificate: PEM-encoded X.509 private_key: EC prime256v1, PKCS#8, PEM keystore_db: https://github.com/SmartDCCInnovation/dccboxed-keystore/blob/main/keystore.json keystore_schema: json-schema/dcc-smart-dccboxed-keystore-schema.json device_certificates: >- Organisation certificates are preloaded; device certificates must be fetched from the SMKI service on the DCC Boxed instance. The keystore library queries SMKI and caches what it finds; the org-certs.zip file can be downloaded from a DCC Boxed instance and converted with `npm run build:db `. warning: >- ZAZ1 key material is test material for a test PKI and is published on purpose. It has no standing on the live DCC network. test_data: - name: DUIS templates (RTDS) package: '@smartdcc/duis-templates' url: https://github.com/SmartDCCInnovation/duis-templates description: >- A searchable catalog of DUIS request templates in JSON, taken from RTDS, keyed by keyword and service request. Surfaced in Node-RED by the duis-template node, which fills in the Originator and Target EUIs. - name: Example tariffs package: '@smartdcc/dccboxed-nodered-nodes' description: >- The duis-tariff node ships three pre-configured example tariffs for ESME SRV 1.1.1 — "TOU (simple)" (single rate), "TOU (complex)" (multiple day profiles and special days) and "Block". - name: Example DUIS request file value: CS08_11.2_SUCCESS_REQUEST_DUIS.XML note: named in the signing tool README as the input to the sign-and-submit example identifiers: originator: >- The DUIS Originator is the sending Remote Party EUI; the Node-RED documentation notes it rarely needs changing from the default in a DCC Boxed setup. target: >- The Target is the EUI of the end device or the ACB; the device EUI is read from the HAN page in DCC Boxed. counter: >- The originator counter is overwritten with System.currentTimeMillis() unless preserveCounter is set — see conventions/dcc-smart-conventions.yml. known_limitations: - >- UTRN tokens generated by the Node-RED nodes encode only the least significant 10 bits of the 32-bit counter, so a UTRN entered manually on a meter keypad may be rejected; this does not affect UTRNs sent programmatically with service request 2.2 (Top Up Device). test_clocks: null fixtures_cli: cli/dcc-smart-cli.yml