Template 2025

Required Information

1. Effective Date: [Insert Date]
2. Application Name(s): [Insert Application Name(s)]
3. Business Department: [Insert Business Department name]
4. Application/System Business Owner: [Insert Business Owner Name]
5. Application/System Technical Owner: [Insert Technical Owner Name]
6. Application/System Vendor Name(s): [Insert Vendor Name(s)]
7. Application/System Business Description: [Insert description of how the application is used by the business department]
8. Application/System Technical Description: [Insert description of the system technology]
9. Disaster Recovery Required: [YES or NO, to be entered]

User Environment

Total Number of Users: [Insert #]

User Physical Locations: [Insert list of locations]

Disaster Recovery Environment/Strategy

Describe DR environment and the strategy for placing this Application/System in a disaster recovery mode.

Disaster Recovery Timing (Refer to BIA Attachments as necessary)

In the event of a disaster, this system [does/does not] require disaster recovery. The Recovery Time Objective, (the overall length of time an application can be in a recovery phase before negatively impacting the application's mission/business function) = X Hours. The Recovery Point Objective (The point in time to which data must be recovered after an outage) = X Hours.

System/Service Availability

This section provides information about the normal schedule of times when the service is available. It also describes the process for enhancing or changing the system or service.

Normal Service Availability

The table below shows the times the system is expected to be available for use. (Times are expressed in "Hours: Minutes" on a 24-hour clock in the US Central Time Zone).

Times	Sunday	Monday	Tuesday	Wednesday	Thursday	Friday	Saturday
Start	0:00	0:00	0:00	0:00	0:00	0:00	0:00 **
Stop	24:00	24:00	24:00	24:00	24:00	24:00	24:00
Critical Hrs.	20:00 - 23:00

**Adjusted when necessary for scheduled outages and non-emergency changes. ***Indicate Critical  hours (i.e., Daily from 20:00 - 23:00)

Maintenance Windows

All planned system maintenance that requires downtime or poses any risk to production will be performed during the pre-approved weekly maintenance window specified below. This maintenance window may not be used each week but is required by IT to be available for maintenance each week as necessary

Enhancements and changes that require a service outage are scheduled at [insert Tome/Day]. Users will be notified two business days before a required non-emergency service outage implementing an enhancement or change.

Regularly scheduled events, including maintenance, can cause a service outage or impact performance (such as slow response times). The table below shows when these are regularly scheduled to occur.

Times	Sunday	Monday	Tuesday	Wednesday	Thursday	Friday	Saturday
Start	3:00
Stop	4:00