Solution Options Report

The purpose of this section is to define the gap between the current (as-is) and target (to-be) state business architectures. Mandatory/optional: This section is optional as not all the domain teams need to produce a business architecture for their respective domains. However, it can also be used by the domains that do not produce a full (current and target) or current state business architecture but still want to know the (priority) areas on which to concentrate, and thus minimise effort. In terms of quality criteria, this section should make clear: • Description of the gap between the current (as-is) and target (to-be) state business architectures. This difference, or delta, defines the scope of work that needs to be undertaken in order to transition from the current to the target business architecture. This scope is thus the scope of the program(s) or project(s) that need to be completed in order to reach the target business architecture. The suggested steps are as follows: • Draw up a matrix with all the Architecture Building Blocks (ABBs) of the baseline architecture on the vertical axis, and all the ABBs of the target architecture on the horizontal axis. • Add to the baseline architecture axis a final row labeled ‘‘New’’, and to the target architecture axis a final column labeled ‘‘Eliminated’’. • Where an ABB is available in both the baseline and target architectures, record this with ‘‘Included’’ at the intersecting cell. • Where an ABB from the baseline architecture is missing in the target architecture, each must be reviewed. If it was correctly eliminated, mark it as such in the appropriate ‘‘Eliminated’’ cell. If it was not, an accidental omission in the target architecture has been uncovered that must be addressed by reinstating the ABB in the next iteration of the architecture design – mark it as such in the appropriate ‘‘Eliminated’’ cell. • Where an ABB from the target architecture cannot be found in the baseline architecture, mark it at the intersection with the ‘‘New’’ row as a gap that needs to filled, either by developing or procuring the building block. When the exercise is complete, anything under ‘‘Eliminated’’ or ‘‘New’’ is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the function. Potential sources of gaps include: • Business domain gaps: o People gaps (e.g., cross-training requirements) o Process gaps (e.g., process inefficiencies) o Tools gaps (e.g., duplicate or missing tool functionality) o Information gaps o Measurement gaps o Financial gaps o Facilities gaps (buildings, office space, etc.) • Data domain gaps: o Data not of sufficient currency o Data not located where it is needed o Not the data that is needed o Data not available when needed o Data not created o Data not consumed o Data relationship gaps • Applications impacted, eliminated, or created • Technology impacted, eliminated, or created