More materials coming soon
Need a specific document? Contact us
The downloads index curates the assets that customers, channel partners, and integrators most commonly request. Brochures cover the product family at a level suitable for non-technical decision-makers. Manuals cover installation, commissioning, and routine maintenance for engineers. Engineering briefs document specific subjects in more depth, such as the EMC behaviour of EAPD in harsh environments, or the analytics logic behind a particular risk model. Each asset has a stable URL and a clear version number. Visitors can browse by category or use the filter to narrow to a specific product family. Updates to assets are common; visitors are encouraged to subscribe to email alerts for the categories they care about. New assets are added when a topic reaches a stable editorial state, rather than at arbitrary deadlines.
If a particular asset is not listed, the request channel is the contact form on the contact page. Many requests turn out to be commercially sensitive, in which case they are routed to the relevant account manager; others can be answered by the technical team through the existing asset index. Customers with framework agreements often have a defined asset-delivery channel that supersedes the public route. Large deployments frequently generate their own custom briefs, which become candidates for anonymized inclusion in the index once the original customer has reviewed and approved a publication-friendly version. The publication pace on this index reflects that flow, not a separate editorial calendar.
Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.
What does a deployment review look like?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Long-term operational considerations include spare-parts policy, end-of-life planning, regulatory drift, and personnel turnover inside the customer's organization. A protective-device deployment that ignores these considerations produces a system that works well at commissioning but deteriorates silently across the second and third years. Our deployments are designed around these considerations from the start, with documentation that the customer team can refresh across personnel changes.
How do we plan for personnel turnover?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Calibration and measurement discipline is the foundation of credible alert output. Sensors that drift produce false alarms that erode operator trust; sensors that are not recalibrated produce missed events. Our deployment methodology specifies calibration intervals that respect the sensor class and the operating environment, with the discipline embedded in the maintenance record rather than left to the operator's initiative.
How often should sensors be calibrated?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.
What does a deployment review look like?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Long-term operational considerations include spare-parts policy, end-of-life planning, regulatory drift, and personnel turnover inside the customer's organization. A protective-device deployment that ignores these considerations produces a system that works well at commissioning but deteriorates silently across the second and third years. Our deployments are designed around these considerations from the start, with documentation that the customer team can refresh across personnel changes.
How do we plan for personnel turnover?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Calibration and measurement discipline is the foundation of credible alert output. Sensors that drift produce false alarms that erode operator trust; sensors that are not recalibrated produce missed events. Our deployment methodology specifies calibration intervals that respect the sensor class and the operating environment, with the discipline embedded in the maintenance record rather than left to the operator's initiative.
How often should sensors be calibrated?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.
What does a deployment review look like?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Long-term operational considerations include spare-parts policy, end-of-life planning, regulatory drift, and personnel turnover inside the customer's organization. A protective-device deployment that ignores these considerations produces a system that works well at commissioning but deteriorates silently across the second and third years. Our deployments are designed around these considerations from the start, with documentation that the customer team can refresh across personnel changes.
How do we plan for personnel turnover?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Choosing among equally defensible engineering tradeoffs is part of the work that experienced teams do well and that newer teams sometimes sidestep. In our deployment practice we walk customers through the tradeoff space, document the chosen path with its rationale, and revisit the choice at every annual review. This deliberate approach reduces the kind of regret that surfaces when original assumptions were not stated plainly.
What does a deployment review look like?
This section reflects the deployment practice we've refined across the installed base. Customers who want more detail on the specific topic for their site can request a focused engagement through the contact form on our contact page.
Are the assets free to download?
Yes, an email subscription is available for asset updates by category.
Historical revisions of manuals remain linked from the current asset page so that field deployments can verify their documentation set.