Proof of concept service
Evaluate eBRP with your own data — before you commit.
eBRP’s Proof of Concept service puts the platform in front of your stakeholders using your actual organizational data, your industry context, and your priority plan types. Working results in weeks. POC data carries forward to full deployment if approved.
Typical POC timeline — 4–6 weeks
Week 1
Scoping & data loading
POC scope agreed, representative data loaded, PPTDFS entity structure configured to your organization.
Setup
Week 2
BIA & risk assessment run
First BIA survey cycle completed, risk assessments populated, eRMA gap analysis demonstrated on your program data.
BIA + Risk
Week 3–4
Plans, dashboards & eRMA
Priority plans built using BIA outputs, dashboards configured, eRMA queried against your program data across all three pillars.
Plans + AI
Week 5–6
CommandCentre exercise & review
A tabletop exercise run in CommandCentre using your scenario. POC findings report and program maturity assessment delivered.
Exercise + Review
What’s included
A complete program view — not a demo environment.
The eBRP POC is scoped to your organization, loaded with your data, and configured to reflect your industry and regulatory context. It’s not a generic demo — it’s a working program preview.
Your data, your structure
POC loaded with a representative subset of your organizational entities — processes, systems, locations, teams — scoped to your industry and risk profile.
BIA + risk assessment cycle
A full BIA survey run with weighted-average computation, plus entity-embedded risk assessments — demonstrating the analytical capability against real program data.
Priority plans built
Your highest-priority plan types built from BIA outputs as executable task playbooks — BC, IT DR, or sector-priority types based on your POC scope.
eRMA demonstrated on your data
eRMA queries run against your program data across all three pillars — program development, crisis management, and program administration — using your actual entities and RTOs.
CommandCentre exercise
A tabletop exercise activated in CommandCentre using a scenario relevant to your industry — plan activation, adaptive task workflow, eRMA intelligence, and after-action review.
POC findings report
A structured findings and program maturity assessment — documenting what the POC revealed about your current program gaps, eRMA insights, and a recommended deployment path forward.
Who the POC is for
Three situations where a POC is the right starting point.
The eBRP POC is designed for organizations that need to see the platform working against their own context before committing to a full deployment.
Building internal buy-in
You need to demonstrate platform value to a CIO, CISO, or procurement committee before a budget commitment. The POC gives you a working proof, not a vendor presentation.
Comparing platforms
You are evaluating eBRP against other BCM platforms and want a like-for-like comparison using your own data, your use cases, and your stakeholders — not a scripted demo.
Validating fit before migration
You are on a legacy platform and want to validate that eBRP Suite can handle your program complexity, plan types, and regulatory requirements before committing to migration.
Common questions
What to know before starting a POC.
Does my POC data carry forward to a full deployment?
Yes. If you proceed to full deployment after the POC, your entity structure, BIA parameters, and plans carry forward — you don’t start from zero. The POC is a head start, not a throwaway environment.
How much data do we need to provide?
A representative subset is sufficient — typically a core set of processes, 20–30 technology entities, key facilities, and a small team structure. Our team guides you through what to prepare and handles the data loading.
How long does a typical POC take?
Four to six weeks from kickoff to final findings report — depending on the breadth of scope and stakeholder availability for the BIA cycle and exercise. The timeline is agreed at scoping.
Is the POC available on AWS and on-premises?
Yes. The POC can be deployed in the eBRP AWS hosted environment for speed, or on your own infrastructure if data sovereignty or infosec requirements demand it. Both options are available from the start of the engagement.
Can we include eRMA in the POC scope?
Yes — and we recommend it. eRMA is most compelling when demonstrated against your actual program data. The POC includes eRMA queries across all three intelligence pillars: program development, crisis management, and program administration.
Start your eBRP proof of concept.
Talk to our team about scoping a POC for your organization — your industry, your data, your use cases. Working results in weeks.