Three levels of CBTAP data are collected for each internal business unit. They are as follows:
The critical business function is the foundation for all of the other data in CBTAP. You may want to consider identifying all
critical business functions first. A critical business function may be either a manual process or an automated process. Technology should not be considered
when identifying the critical business function.
Once you have defined the critical business functions, you will then look at whether that function is supported by
an IT system or application. There is direct interaction between agency staff and the critical business application. The critical business application does not exist without the critical business function.
Some critical business applications will have external dependencies. These are external IT systems or system components
that are required for your critical application to be fully functional. There must be direct interaction between the application
and the external dependency.
Each of the three levels described above is further broken-down by data grouping sections.
Click on any data section listed below for a detailed description of the data elements
available and the example data provided.
Critical Business Function (Blue Form)
The Ombudsman Function is a critical business function for fictitious "Agency X".
Three staff in one office location use an issues tracking system to perform this function.
The CBTAP function data sections are:
Critical Business Application (Yellow Form)
The Ombudsman Function has one supporting application called the Ombudsman Issues Tracking
System (OITS). The CBTAP application data sections are:
Critical External Dependencies (Orange Form)
The Ombudsman Issues Tracking System (OITS) has no external dependencies.
