ChargeLink Documentation Logo

Overview

  • What ChargeLink is
  • Simulator roles: EVSE, EVCC, and bench-linked execution
  • Standards, protocols, and conformance position
  • Product status and claim boundaries

Getting started

  • Installation and workstation preparation
  • Quickstart: first EVSE session, first campaign, first report

Guides

  • Guide: EVSE operations
  • Guide: EVCC operations and backend orchestration
  • Guide: scenarios, campaigns, packages, qualification, and suites
  • Guide: trace, replay, diagnostics, reporting, and artifacts
  • Guide: MCS, HIL, and bench proof
  • Guide: UI and API surfaces

Reference

  • Data and artifacts reference
  • Profile catalog
  • Hardware profile reference
  • Package and suite catalog
  • API reference overview
  • chargelink-monitor
  • CLI reference
    • chargelink evse
    • chargelink evcc
    • chargelink hil
    • chargelink scenario
    • chargelink campaign
    • chargelink qualification
    • chargelink suite
    • chargelink report
    • chargelink trace
    • chargelink replay
    • chargelink lab
    • chargelink beckhoff
    • chargelink protocol
    • chargelink artifacts
    • chargelink sequence
    • chargelink macro
    • chargelink verdict
    • chargelink step
    • chargelink profile
    • chargelink template
    • chargelink library
    • chargelink batch
    • chargelink campaign-stress
    • chargelink service
    • chargelink requirements
      • Reference syntax
      • Subcommands
      • map
        • CLI help
        • Production examples
      • import
        • CLI help
        • Production examples
      • link
        • CLI help
        • Production examples
    • chargelink backend
    • chargelink evidence
    • chargelink audit
    • chargelink ports
    • chargelink env
    • chargelink capture
    • chargelink ci
    • chargelink sessions
    • chargelink fault
    • chargelink network
    • chargelink fuzz
  • Glossary
ChargeLink Documentation
  • CLI reference
  • chargelink requirements
  • View page source

chargelink requirements

Map campaign content to requirements and link imported requirement IDs to runs.

Reference syntax

usage: chargelink requirements [-h] {map,import,link} ...

positional arguments:
  {map,import,link}

options:
  -h, --help         show this help message and exit

Subcommands

Subcommand

Purpose

map

Map a campaign document to requirement references.

import

Import requirement IDs into the runtime registry.

link

Link a requirement ID to a run.

map

Map a campaign document to requirement references.

CLI help

usage: chargelink requirements map [-h] campaign

positional arguments:
  campaign

options:
  -h, --help  show this help message and exit

Production examples

Generate a map from a production input.

chargelink requirements map 'campaigns/interoperability/iso15118_20/ac/cl_int_iso20_ac_negative_realistic.json'

Generate a second map.

chargelink requirements map 'campaigns/conformance/iso15118_2/dc_pnc/cl_conf_iso2_dc_pnc_seed.json'

import

Import requirement IDs into the runtime registry.

CLI help

usage: chargelink requirements import [-h] [--runtime-root RUNTIME_ROOT] file

positional arguments:
  file

options:
  -h, --help            show this help message and exit
  --runtime-root RUNTIME_ROOT

Production examples

Import a requirements file.

chargelink requirements import 'requirements.json' --runtime-root '.tmp/runtime'

Import a second file.

chargelink requirements import 'requirements_extra.json' --runtime-root '.tmp/runtime'

link

Link a requirement ID to a run.

CLI help

usage: chargelink requirements link [-h] [--runtime-root RUNTIME_ROOT]
                                    requirement_id run_id

positional arguments:
  requirement_id
  run_id

options:
  -h, --help            show this help message and exit
  --runtime-root RUNTIME_ROOT

Production examples

Link a requirement to a run.

chargelink requirements link 'REQ-001' 'run_1' --runtime-root '.tmp/runtime'

Link a second requirement to the same run.

chargelink requirements link 'REQ-ISO20-DC-001' 'run_1' --runtime-root '.tmp/runtime'
Previous Next

© Copyright 2026, devLink AB.

Built with Sphinx using a theme provided by Read the Docs.