SEAS consulting team has completed Situation Analysis (SA) with 51 clarified concerns related to ABM case study. The teams has identified multiple problems in the current ABM business which are related to people, process, information and technology areas. An Enterprise Architecture stream has been setup to take responsibility for further in depth analysis from EA perspective and in this regard EA stream has selected TOGAF 9.1 as a framework to develop architectural artifacts.
The issues faced by ABM currently are mostly related to the overall operating mechanism, structure of the organization and IT automation of the business. Following are the problems explained in details from EA perspective:
ABM Operating Mechanism:
ABM has some major issues related to business processes being followed by its departments. In many departments processes are executed on an ad-hoc basis, this is due to the fact that none of the processes have been documented and no availability of Standard Operating Procedures SOP for any department. For architects, this element is one of the major issues due to which ABM is not able to sustain its operation and is the main cause of disconnect between different business functions.
Even though ABM organization structure has the core departments to run the business but these departments are also performing support functions as well. Functions like Project Management, Demand Management, Innovation Management e.t.c ideally should be separate departments to provide support related inputs functions mentioned. Architects believe that the current organization structure needs revamp by introducing new business units to increase the overall efficiency ABM operation.
Another area of high concern for architects is the use of technology to support business functions. After having a session with the board, it was highlighted that ABM is mostly using excel sheets to support their activities such as , sales forecasting ,production schedules, customer management and product cataloguing. On the other hand there is only one known IT system being used by Finance and that is Oracle Financials. From EA perspective, IT is core enabler for business’s smooth and sustainable operation.
In the light of above issues , it is understood that the reason of not having crucial information available to the right stakeholder is due to the lack of business process automation and for the automation, business processes have to be documented and owned by the rightful owner.
The approach which EA stream has defined , utilizes the TOGAF 9.1 Architecture Development Method ADM. There are multiple artifacts which are required to ensure a proper development of the architecture but for the problem on hand, EA stream has identified list of artifacts from ADM and will be using to develop the architecture. As per plan, the first most thing to deliver is the AS-IS architecture state of ABM. Due to the non-availability of the documented information related to ABM’s business structure, Enterprise Architects will have to develop a high level of AS-IS architecture state. This will include artifacts such as Organization Structure, Value Chain, Business Functions Decomposition and Business Context Diagram.. The second deliverable through ADM, will be the TO-BE architecture state and will consist of detailed architectural artifacts. The list of TO-BE architecture artifacts will be identified once the AS-IS state is completed and the progress in this regards will be published in future blogs.