A structured operational framework for MEGC-based hydrogen logistics — covering system pre-requisites, filling execution, safety integration, and full traceability from reception to transport release.
Bridging the Gap Between Regulation and Operational Reality
The introduction of MEGC solutions for H₂ logistics at higher pressures does not occur within a widely applicable, standardized operational framework. As an emerging market, the lack of harmonization in operating practices limits large-scale deployment and industrial maturity.
This protocol consolidates available information gathered from previous deliverables to define a structured baseline. Its objective is to enable operators and equipment providers to improve standardization efforts and facilitate the broader adoption of MEGC technologies — yielding safer, more economically viable, and more competitive alternatives within the industrialization of MEGC-based hydrogen logistics.
This document presents a consolidated protocol framework covering the full transfer sequence, from system pre-requisites and pre-filling checks to active filling control, stabilization, and post-operation procedures.
Why Standardization Matters
Safety
Consistent safety envelopes across operators and sites
Scalability
Generic approaches applicable across diverse MEGC assets
Compliance
Traceable alignment with applicable regulatory standards
Industrialization
Supports competitive and economically viable deployment
Scope & Definitions
Protocol Scope: What Is Covered
This protocol defines the operational conditions applicable to the filling of Type III and Type IV MEGC (Multi-Element Gas Containers) intended for the transport of compressed hydrogen. It covers all stages of the filling process — from MEGC reception on site to its release for transport.
Vessel Types
Type III (metal liner with composite reinforcement) and Type IV (polymer liner with composite reinforcement) high-pressure vessels
Service Pressures
Service pressures ranging from 200 bar to 700 bar, with initial filling pressures up to 20 bar (no empty start)
Ambient Conditions
Ambient temperatures from −20°C to +45°C, with meteorological monitoring required at operating boundaries
Station Configuration
Stationary hydrogen transfer units equipped with compression and/or cascade systems, with or without active cooling, staff
Constraints & Requirements
Physical, Safety, and Operational Constraints
Physical Constraints
The protocol operates within hard physical limits defined by both station and MEGC parameters. Maximum deliverable pressure is bounded by the dispenser system (cascade or compressor maximum), and MEGC limits are set at 1.25 × NWP — corresponding to 437 bar at 350 bar NWP, 475 bar at 380 bar NWP, and 800 bar at 640 bar NWP.
Liner temperature limit: 65°C
Gas temperature limit: 85°C
Maximum filling rate defined by connector specification
PRD and safety valve pressure identification required
Safety & Operational Constraints
All operations must be conducted within ATEX-compliant environments. Hydrogen concentration shall remain below 4% vol (LEL) in confined areas, with alarm thresholds at 25% LEL triggering preventive actions. Access is restricted to trained, authorized personnel only.
Fixed or portable gas detection systems required
All metallic/electrical equipment must be ATEX-certified or removed
Electrostatic discharge risks minimized via proper grounding and bonding
Maximum filling duration and station availability must be respected
Pressure deviation beyond acceptable thresholds requires immediate operational stop and activation of automatic or manual shutdown systems. The protocol prioritizes early interruption to prevent activation of safety relief devices or uncontrolled hydrogen releases.
Design Philosophy
Eight Guiding Principles for Protocol Definition
The protocol is not a static checklist — it is a constraint-driven, adaptive, and auditable framework. The following principles govern every design and operational decision.
1
Safety Envelope First
All strategies operate strictly within predefined pressure, temperature, dP/dt, and SOC limits — including worst-case scenarios.
2
Cost–Benefit Arbitrage
Each configuration results from a trade-off: filling time vs. energy consumption, throughput vs. equipment stress, simplicity vs. performance.
3
Adaptive Boundary Conditions
The protocol dynamically adapts to varying initial pressure, temperature, and ambient conditions — avoiding one-size-fits-all strategies.
4
System-Level Optimization
Protocol definition considers the entire hydrogen transfer chain — station, storage, compression, and transport unit — ensuring global optimization.
5
Robustness & Repeatability
Consistent outcomes are delivered despite sensor noise, environmental variability, and operational uncertainty.
6
Automation Readiness
Directly translatable into PLC/SCADA control logic, with clear decision rules and minimal operator ambiguity.
7
Traceability & Auditability
All decisions and outcomes are traceable, enabling compliance demonstration, incident analysis, and continuous improvement.
8
Scalability & Standardization
The approach is applicable across different MEGC assets and storage systems, supporting future standardization in hydrogen logistics.
Stakeholder Engagement
Key Protocol Stakeholders & Responsibilities
Successful implementation of the hydrogen transfer protocol requires clear roles and responsibilities across all involved parties, from design to daily operations. Each stakeholder plays a critical part in ensuring safety and efficiency.
1
MEGC OEM
Provides technical specifications, maintenance guidelines, and supports design compliance for the containers.
2
MEGC Owner
Ensures MEGC maintenance, re-qualification, and overall asset integrity throughout its lifecycle and operation.
3
Logistics Operator
Manages MEGC transport, scheduling, and coordinates efficient supply chain movements to and from sites.
4
HTU Operator
Directly manages the hydrogen transfer process, monitors parameters, and ensures safe, compliant filling operations.
5
Driver
Responsible for safe transport of MEGCs, pre-departure checks, and initial site coordination upon arrival.
6
Document Validator
Oversees and approves all protocol-related documentation, ensuring compliance with regulatory and operational standards.
Operational Phases
The CRIMP Execution Framework
The hydrogen transfer protocol is structured as a sequence of five consolidated operational phases — simplified from seven granular steps for field applicability. The CRIMP acronym (Check / Ready / Inject / Monitor / Purge & Close) provides an intuitive mnemonic for operators and automation engineers alike.
1
C2 — "Compliance" and Check
Phases 0 & 1: System pre-requisites, sensor/valve/ESD verification, visual inspection, grounding, and pressure compatibility checks.
2
R — Ready
Phase 2: Connection & inerting, certified leak-free connection, inerting if required, system readiness confirmed for pressurization.
3
I — Inject
Phase 3: Filling definition & execution, pressure ramp profile, controlled ΔP/dt within thermal and mechanical constraints.
4
M — Maintain
Phase 4: Maintain below 100% SOC, stabilization, thermal equilibration, optional top-up, continuous P/T monitoring until final stabilized state is reached.
5
P — Purge & Close
Phases 5 & 6: Valve closure, depressurization, disconnection, data logging, incident handling, and release authorization.
Phase 0 Detail
Phase 0 – System Pre-Requisites: The Mandatory Hold Point
Color code: blue for documentary & compliance preparation, yellow for physical operator checks, and green for automated system checks.
Objective
Ensure that all equipment, interfaces, and safety systems are fully operational and compliant prior to any filling operation. This phase constitutes a mandatory hold point before proceeding to pre-filling checks — no filling operation may commence without successful completion.
Documentary & Compliance Preparation
Verify equipment specifications and certifications
Confirm ATEX compliance of all tools and powered equipment
Automated System Checks
Confirm ESD systems: available and functional
Run automated sensor consistency cross-check
Verify system readiness signal before proceeding
Validation / Hold Point
If any condition is not met: stop operation immediately, correct the issue before proceeding, and involve maintenance or technical support if required.
State Machine
Finite State Machine: Deterministic Operational Logic
The protocol is implemented as a finite state machine (FSM), ensuring deterministic and automatable execution across all phases. Every state transition is conditioned on validated hold points, and any fault at any state triggers an immediate transition to the safe fault state.
State Transitions
01
S0 → S1
System initialized and pre-checks initiated
02
S1 → S2
All pre-filling checks validated
03
S2 → S3
Connection completed and certified
04
S3 → S4
Leak test passed — filling authorized
05
S4 → S5
Target pressure reached or stop condition triggered
06
S5 → S6
Stabilization complete, all limits satisfied
Fault Handling — S7
Any state may transition directly to S7: Fault upon detection of an anomalous condition. Fault handling triggers:
Immediate transition to safe state
Automatic shutdown and system isolation
Operator alert and ESD activation
Mandatory incident registration before resumption
Fault state S7 is reachable from any operational state. Recovery requires documented root cause analysis and supervisor authorization before returning to S0.
Safety-critical signals — hydrogen leak detection, flame detection, and ambient H₂ concentration — are handled within the SIS, operating with fail-safe logic (loss of signal = alarm/trip) and highest-priority interlocks that override all process control commands.
Every phase transition is conditioned on a formal GO / NO-GO validation. Any rejection must be argued, registered in the filling record, and accompanied by the immediate action taken and a long-term corrective initiative to prevent recurrence.
Any rejection must be argued and registered in the filling record, including: the immediate action taken and the long-term initiative to prevent recurrence.
Reporting & Logging
Traceability: Incident Reporting & Filling Records
Incident Reporting Protocol
An incident is defined as any deviation from normal operation, including pressure or temperature exceedances, leak detection, hydrogen concentration above threshold, equipment malfunction, or unexpected activation of safety systems. Every incident triggers a mandatory structured response.
01
Immediate Stop
Halt filling operation and secure installation via isolation and shutdown if required
02
Personnel Safety
Evacuate personnel if necessary and inform the responsible supervisor immediately
03
Post-Incident Analysis
Root cause analysis, identification of corrective actions, and update of operational rules if necessary
Filling Operation Record Template
Complete, signed filling records are mandatory for MEGC release authorization. Missing data blocks release until all fields are validated.
Continuous Improvement
Data Use and Risk Monitoring: Building a Learning System
The long-term value of this protocol extends beyond individual filling operations. Systematic data collection and analysis enables the hydrogen transfer ecosystem to evolve, self-correct, and continuously improve operational safety and efficiency.
Historical Database
Build a longitudinal record of MEGC and station behavior across all operations, enabling statistical trend analysis and behavioral benchmarking over asset lifetime.
Anomaly Detection
Detect abnormal trends and recurring issues before they escalate — supporting predictive maintenance and early identification of systemic failure modes.
Preventive Maintenance
Use operational history to plan maintenance interventions proactively, reducing unplanned downtime and extending the operational lifetime of MEGC assets and station equipment.
Protocol Optimization
Continuously refine filling procedures, safety thresholds, and control parameters based on real-world operational data — closing the loop between field performance and protocol