Table / Status
Publications
Conceptually analogous to Infrastructure Table Publication vs Infrastructure Status Publication: structure vs time-varying snapshots.
Standard & disclosure
Understanding DATEX II
DATEX II structures how charging infrastructure data is disclosed. Telemetry stays in CPMS; OB7 is not a CPMS — optional enrichment when OB7 sits in your stack.
DATEX II with AFIR profileMobilithek as the national intakeNAP: EU term National Access PointMaster vs runtime dataCPMS as sourceOptional enrichment (e.g. ad hoc pricing)
Demonstration: connector Occupied becomes Available and the tariff shifts from €0.45 to €0.42 per kWh.
CPMS
Charge point
OccupiedAvailable
Tariff per kWh
€0.45€0.42
optional
OB7 Admin
Charge point
OccupiedAvailable
Tariff per kWh
€0.45€0.42
Mobilithek
Charge point
OccupiedAvailable
Tariff per kWh
€0.45€0.42
CPMS
Charge point
OccupiedAvailable
Tariff per kWh
€0.45€0.42
optional
OB7 Admin
Charge point
OccupiedAvailable
Tariff per kWh
€0.45€0.42
Mobilithek
Charge point
OccupiedAvailable
Tariff per kWh
€0.45€0.42
Illustrative feed excerptstream
Location & status dataok
Price dataok
Telemetry and master data still originate inside CPMS. Where needed, OB7 can enrich disclosures or align tariff fields coming from authoritative OB7 modules—for example QR or ad hoc pricing—before DATEX II payloads are handed toward Mobilithek or other national intake pathways. Legislation refers to those doors as National Access Points (NAP). Other routes remain possible.
Separate responsibilities
DATEX II frames what you publish — CPMS still owns the signals.
Field and master data stay in CPMS; OB7 cannot replace it and is not another CPMS. German teams commonly publish via Mobilithek — statutes call that role a National Access Point (NAP). With OB7 in the path you can optionally enrich payloads or reconcile tariffs—for example wherever ad hoc pricing is authoritative.
~24h / ~1 min
Freshness benchmarks
Dynamic fields generally need tighter refresh cycles than slow-moving master-data tables; check AFIR for the binding numbers.
AFIR · DE
German context
Mobilithek onboarding guidance operationalises national Level-C nuances on top of the European baseline.
Hardware to filings
Anything the public reads must match what you genuinely operate.
You publish a hierarchy (area → station → EVSE → connectors) alongside separate live facets for availability and, when required, pricing. Stable IDs, disciplined ownership per field, and a straight CPMS→export path matter more than another slide deck.
Example staging between charger IT stack and MobilithekDATEX II
Structural table
Site & connector kernel
Addressing, geo, connector topology, nominal power caps, accessibility rules compose the comparatively static façade.
Runtime layer
Operational status
Live availability or disruptions should reference immutable keys from the structural tree and refresh far more aggressively.
Tariff façade
Price / access artefacts
AFIR mandates transparent price signals beyond hardware facts; granularity depends on the national profile and your tariff engine.
Publication hand-over
Mobilithek wording vs statutory NAP
Mobilithek is the German intake portal teams actually open. Laws say National Access Point (NAP) for the generic duty around the bloc. Screens, tokens, and auth stay whatever your rollout agreed on.
Dominant artefacts
DATEX II is ongoing housekeeping, not a one-off spreadsheet dump.
These blocks show up in every serious reporting dossier, whether OB7 carries the packets or CPMS emits them outright.
Topology
Location graph & plugs
Consistent surrogate keys tie dynamic telemetry back to deterministic hardware rows.
Tariff façade
Access & tariff signals
Keep canonical monetary intent close to operational billing stacks to dodge double bookkeeping.
Velocity
Update cadence
Short feedback loops blunt driver confusion and search-engine drift.
Quality gate
Schema & semantic lint
Catch enum violations & missing mandatory nodes before external rejection loops.
Mobilithek
Dispatch path
OB7 optionally enriches and stages payloads; who holds ingestion credentials toward Mobilithek or allied NAP components stays with your project agreements.
Role OB7
Admin orchestrator
Stay white‑label operator admin, not CPMS: optionally enrich payloads, validate them, and stage them toward filing channels rather than rewriting live stack signals.
Optional lane
Four checkpoints when OB7 shuttles payloads.
Signals start inside CPMS. OB7 layers can augment them but never erase the charger-side source.
01
CPMS remains authoritative
Inventory churn, transactional pricing baselines and availability semantics emerge where charging is operated.
02
(Optional) OB7 enrichment
UI-assisted gap fill, merges from parallel sources, QA dashboards before egress.
03
Profile validation
Check cardinality, enums, and lineage markers early so Mobilithek does not bounce the batch late.
04
DATEX II drop toward Mobilithek
Transmit per your technical appendix, commonly next to whatever other outbound routes you operate.
Why it matters
Clean data reaches drivers sooner and cuts busywork downstream.
Published, current data improves visibility, routing, and trust for drivers.
Separate competencies
Marketing pages are not tailored legal diligence, and texts under AFIR or DATEX keep changing. Decide how work splits among CPMS vendor, fleet IT, and counsel. OB7 provides technical scaffolding, not charger-field operations and not your CPMS stand-in.
Drivers
Better discoverability
Navigation and mobility services can display charge points more reliably when data is structured and current.
Operations
Less manual work
Automated feeds reduce recurring maintenance across spreadsheets, portals, and manual reporting paths.
Governance
Traceable data quality
Required fields and changes become visible as a process and can be owned internally.
FAQs
Frequently Asked Questions
Straight answers about DATEX II plus where OB7 fits without pretending to be a CPMS.
What is DATEX II?
DATEX II is a CEN-managed family of content models and exchange patterns. For charging, think of at least two aligned publication families: structural master data (locations, EVSEs, connectors) and dynamic status-style snapshots (availability, sometimes tariff pointers) according to the AFIR recharging profile.
What is Mobilithek, and why do people mention NAP?
Mobilithek is Germany's national electromobility data platform where operators routinely complete onboarding. Across the EU statutes call that duty a National Access Point (NAP), even when the portal branding differs Member State by Member State.
Which data does that cover?
Expect connectors, capacities, openings, visibility into availability, and price transparency cues where regulation demands them. Mobilithek publish their German guidance atop the EU baseline, so Legal should still confirm scope for your estate.
Am I legally obliged to publish?
Publicly accessible infrastructure generally triggers AFIR transparency duties, but exact obligations, actors, and timelines should be validated with counsel. Technically you can fulfill them through CPMS exports, OB7-assisted staging, or hybrid paths.
Does OB7 originate the underlying signals?
No. OB7 is not a CPMS: raw charger truth still comes from your charging platform stack. OB7 may enrich disclosures—such as aligning tariff cues when QR or ad hoc pricing is authoritative in OB7—and publish DATEX II‑ready artefacts if your architecture chooses that lane.
How might OB7 help optionally?
Depending on rollout, OB7 can merge masters, QA them, add missing tariff or access cues from authoritative OB7 services, then relay structured payloads into Mobilithek intake or whichever downstream queues you nominate—without claiming to originate on-site instrumentation.
What about “real-time” expectations?
Regulators benchmark dynamic data far tighter than multi-day master-data drift (often minute-scale vs daily-scale windows). Achievable latency still depends on your CPMS quality, network, and chosen export cadence.
Are interface features always bundled free?
Contractual packaging varies; do not assume silent inclusion. Confirm scope and fees with sales when planning Mobilithek or other NAP-adjacent exports.