Monitoring and availability - what bank ops should expect
Think of AIS-backed lending like utilities your branches rely on: power is usually on, but you still have flashlights, generators, and a number to call. The goal here is shared vocabulary with AIS-not access to AIS internal dashboards unless your contract provides them.
Health in plain language
Most banks ask for a simple traffic‑light story:
- Green: primary journeys (for example login, application intake, scoring, approval queue) are meeting agreed response times.
- Yellow: slower responses or non‑critical features degraded; workarounds may exist.
- Red: a material outage for many users or a regulatory‑sensitive path blocked-activate your incident bridge and AIS support path (see Incident response & support).
Who defines “material”? Your service level annex and internal severity matrix-not this portal.
Synthetic checks (“mystery shopper” probes)
A common pattern is synthetic transactions: a scheduled test application or health call that proves the full path works, not just that a server answers “OK.” Ask AIS whether your program includes:
- Frequency (for example hourly vs business hours).
- Which environment probes run against (usually non‑production for write tests).
- Who gets alerted when a probe fails (AIS only vs joint distribution list).
What bank ops can monitor themselves
Even without AIS internals, you can track:
- Branch call volume spikes tied to lending journeys.
- Core banking rejects or timeouts on interfaces you own that sit next to AIS.
- Decision PRO “cannot connect” help‑desk tickets (pattern counts).
Correlate those signals with AIS‑announced maintenance or releases (see Releases & notifications).
Availability targets (placeholders)
| Topic | Typical bank question | Where the answer lives |
|---|---|---|
| Monthly uptime % | What is excluded (planned maintenance, your network)? | Contract SLA - not standardized here |
| RTO / RPO | How fast restore? How much data at risk? | BCP annex - placeholders until AIS publishes approved numbers |
| Status page | Public vs partner‑only? | Per program - confirm with AIS |
:::caution No implied guarantee
Monitoring reduces surprise; it does not replace contractual SLAs or your business continuity plan.
:::
Next: Maintenance windows · Overview