Part 2: Timeliness of Critical Business Functions: Difference between revisions

Latest revision as of 22:27, 23 October 2020

Function No
- Cross reference to the function number from original Function No assigned in Part 1
Normal Timescale
- The timescale for a business function to be carried out on a normal day. You can consider it as how long does it takes to do one transaction. Insert the appropriate timescale found in the BIA Questionnaire.
  - Example of a typical entry is “1” if time scale is less than 4 hrs, “2” if less than 1 day. Refer to the scale found in Part 2.

Crisis Timescale - sometime refer to as Disaster Timescale or RTO
- During a disaster, would you be able to stretch the timescale during the delivering of this business function? Would your customer be able to bear with the delay?
  - Please make a personal judgment based on a “credible” Worst Case Disaster Scenario.
  - Could the business function be carried-out over a longer period, possibly by using different means during a disaster?
  - Assume it is not possible to access your office location.
Optional: Recovery Point Objective (RPO)
- This column is added to document the RPO as specified by the business units with the IT team.
Time of Year/ Month/ Week/ Day that the function is most vulnerable
- State the specific time e.g.
  - Month-end
  - Year-end
  - 25th of month
  - 4.30 pm daily
  - Not applicable

etc. whereby the business function is most vulnerable.

Notes (1): Try to discourage answers such as “All day” and “Ad-hoc.”
Notes (2): The key is to identify how much time it takes to complete a transaction and compare this with the time to be taken during a disaster.
Notes (3): Imput the "Timescales" (by entering the number "1" to "7" only) in the first two columns of this table.
- (1) 4 hours or less
- (2) 5 hours to 1 day
- (3) 2 to 3 days
- (4) 4 to 7 days
- (5) 8 - 13 days
- (6) 2 weeks to 1 month
- (7) > 1 month