Risk and Compliance

Continuity Planning

sd-continuity-planning · bian-risk-compliance

A BIAN service domain in Risk and Compliance. It applies the Plan functional pattern to the Continuity Plan, with the Continuity Plan Plan as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.

View repository ↗The 162-domain platform ↗

Business DomainCompliance

Functional PatternPlan

Asset TypeContinuity Plan

Control RecordContinuity Plan Plan

USEWhat it is used for

Representative use cases for the Continuity Planning service domain within a BIAN-aligned core-banking landscape.

Track Continuity Plan obligations and evidence their fulfilment
Produce and submit regulator-ready reports on schedule
Support internal/external audits with complete records retrieval

APIBIAN semantic API

The control record (Continuity Plan Plan) is exposed through uniform BIAN action terms. Java 21 · Spring Boot 3, OpenAPI at /swagger-ui.html, health at /actuator/health.

Method	Path	BIAN action
GET	`/v1/service-domain`	Service metadata
POST	`/v1/continuity-plan-plan/initiate`	Initiate
GET	`/v1/continuity-plan-plan/{crId}/retrieve`	Retrieve
PUT	`/v1/continuity-plan-plan/{crId}/update`	Update
PUT	`/v1/continuity-plan-plan/{crId}/control`	Control (suspend / resume / terminate)

INTBackend integrations

The systems and standards a real deployment of Continuity Planning would transact with.

GRC: RSA Archer, MetricStream
Reg reporting: AxiomSL, Wolters Kluwer OneSumX, Vermeg
Records: OpenText, Veritas

RUNRun it yourself

Each service domain is its own standalone Spring Boot repository — clone and run in seconds, or deploy onto Kubernetes with the bundled Helm chart behind the Cilium mesh.

# run this service domain standalone
git clone https://github.com/Sreenivas-Sadhu-Prabhakara/sd-continuity-planning
mvn -f sd-continuity-planning spring-boot:run
curl localhost:8080/v1/service-domain

# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-continuity-planning ./helm -n bian-risk-compliance

FAQQuestions

What is a BIAN service domain?

BIAN (the Banking Industry Architecture Network) decomposes a bank into independent service domains, each owning exactly one business capability. Continuity Planning is the service domain for Compliance; it manages the Continuity Plan Plan and exposes it through standard BIAN action terms.

What business area does Continuity Planning belong to?

Continuity Planning sits in the Risk and Compliance business area — the risk, financial-crime and regulatory-compliance domains that keep the bank safe and compliant. It runs in the bian-risk-compliance namespace as one independent Spring Boot microservice.

Is Continuity Planning production-ready?

It is an educational reference implementation: a real BIAN REST API over an in-memory store, ready to be filled with domain logic. It is not a live bank and is not affiliated with BIAN.