> For the complete documentation index, see [llms.txt](https://host2host.onibonje.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://host2host.onibonje.com/docs/41-training-and-handover.md).

# Training and Handover

## 1. Overview

RFP §11 — implementation approach and training requirements. Ensures bank teams can operate the platform post-delivery.

***

## 2. Training Audiences

| Audience                    | Duration | Topics                                      |
| --------------------------- | -------- | ------------------------------------------- |
| Integration analysts        | 3 days   | Admin portal, mappings, publish workflow    |
| Integration developers      | 5 days   | JAR modules, Camel routes, scripts, plugins |
| Operations / NOC            | 2 days   | Dashboards, DLQ, retry, runbooks            |
| Security officers           | 1 day    | Vault, certs, RBAC                          |
| Platform ops / DevOps       | 3 days   | Helm, Terraform, DR, monitoring             |
| Partner onboarding officers | 2 days   | Partner wizard, sandbox testing             |

***

## 3. Deliverables

| Deliverable           | Format                                                 |
| --------------------- | ------------------------------------------------------ |
| Architecture overview | This documentation set                                 |
| Admin user guide      | Derived from [05](/docs/05-low-code-admin-platform.md) |
| Operations runbooks   | [34](/docs/34-operations-architecture.md)              |
| API partner guide     | [37](/docs/37-partner-portal.md) + OpenAPI             |
| Hands-on labs         | Sandbox environment exercises                          |
| Recorded walkthroughs | Video per persona                                      |

***

## 4. Handover Checklist

| Item                          | Owner                |
| ----------------------------- | -------------------- |
| Source code + CI access       | Vendor → Bank IT     |
| Helm/Terraform repos          | Vendor → Bank DevOps |
| Vault policies                | Joint                |
| Keycloak realms               | Joint                |
| Admin credentials             | Bank IAM             |
| Runbook validation            | NOC sign-off         |
| First partner go-live support | Hypercare 4 weeks    |

***

## 5. Hypercare Period

4 weeks post go-live: vendor on-call for P1/P2, daily standup, issue triage.

***

## 6. Related Documents

* [10 Implementation Roadmap](/docs/10-implementation-roadmap.md)
* [06 Personas and RBAC](/docs/06-personas-and-rbac.md)
* [34 Operations Architecture](/docs/34-operations-architecture.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://host2host.onibonje.com/docs/41-training-and-handover.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.