Skip to main content
Regulaxy

Insurance & institutional

The night is not free.
It belongs to the batch.

In an insurer the window is measured against the batch — claims, policy, actuarial calculation, feeds to external bodies — not against office hours. An hour that looks empty on a calendar is usually an hour when a job is running that must not be interrupted. Regulaxy books the window against that cycle rather than against the clock.

What breaks today

The window is right against the calendar and wrong against the system.

  • The window lands on the batch

    Whoever booked it saw an empty night. Whoever runs the calculation knew otherwise. The gap shows up when a job is cut in half.

  • Period-end freeze

    Month-end, quarter-end and annual reporting close large parts of the calendar. Anyone who doesn't hold that calendar books into it and finds out late.

  • Ownership that moved

    A core system that changed teams, and nobody is certain who signs for it now. That question adds a week to every window.

  • The supervisor asks you to show it

    The question is not whether you patched. It is how you demonstrate it. A folder of mail is not evidence of a process.

Figure — a night at an insurer: processing run against maintenance window

0006121824
  • Maintenance window
  • Processing run
Figure — a night at an insurer: processing run against maintenance window

What changes

The window is chosen against the cycle, and the approval is kept.

  • A dependency map from the infrastructure

    Linked systems are read from the estate itself rather than from a document. A window colliding with a dependent system is flagged while it is being booked.

  • A calendar you can see

    Monthly, weekly, quarterly and yearly. Freezes and peak periods are visible before you book, not after.

  • System memory

    Contacts who took part in a previous window on the same system are offered again next time. The knowledge survives the person leaving.

  • An export you can submit

    Every window, its owner, the approval and the checklist, in one file. That is what goes to internal audit or to the regulator.

Questions

Questions we actually get

The detailed mapping we hold today is to Bank of Israel Directive 364, which is the regulation the product was built against. Institutional requirements for patch management, change approval and audit trail are similar in substance — send us the specific circular that binds you and we will map against it with you rather than guess.

Let's look at one real night.

Give us a window that slipped, and we will show you exactly where it would have stopped — and what would have been left in writing.