Architecting.Biz

Tag: ArchiMate Language

  • The Exploration of the Project Delivery Process

    The Exploration of the Project Delivery Process

    The enterprise architect walked through the architecture documentation that he had produced together with the head of departments in the AEC-company, and he correctly identified the need for him to look into this important process as-well.

    For most Architecture, Engineering and Construction companies most of the services and products delivered are delivered through a rigorous project delivery process, since costs can increase significantly if the methodology and planning processes are not dealt with correctly.

    The project delivery process does in the context of the AEC-company handle everything from project methodology, capacity planning, allocation of resources, project planning, project execution and project documentation. The insights the enterprise architect has at this point in time are not thorough enough for producing the relevant planning for the digital transformation of the AEC-company. Consequently, the enterprise architect will have to conduct a similar clarification process for engaging with the subject matter experts with the current findings and then elaborating based on the data how the AS-IS state is and how the TO-BE state should be for the process:

    1. The first workshop is about getting answers for specific questions.
    2. The second workshop is about getting insights on the business applications and the dataflow.
    3. The third workshop is to present the TO-BE version of the process design including its usage of business applications.

    For the first workshop the enterprise architect desires to ask the below questions:

    • When making a planning a new project what applications do you make use of?
    • Who will you be contacting and how do you do so?
    • Where do you store the project planning, capacity requests, and customer data?
    • How do you create an overview of ongoing projects and capacity?

    The primary scope for the enterprise architect is to clarify the business applications (Application Components), the business interfaces and subsequent application interfaces needed in order for the business process to be designed to deliver on the goals that must be realized as part of the business strategy (Course of Action) “Partnering for Green Construction”.

    The enterprise architect designs a high-level view of the “Project Delivery Process” for the TO-BE process beforehand, which makes the below view of the process a premature, and it will likely be updated after workshop 1 and 2:

    Line of Sight

    After the enterprise architect has designed the above view of the TO-BE (Preliminary) process design for the project delivery process, then it is possible to interact with the below line of sight for the specific application components in the model. The below illustration is created by filtering on elements (Application Component) and filtering of viewpoint to “Application Structure”:

  • The Exploration of the Bid Process

    The Exploration of the Bid Process

    The enterprise architect, armed with the documentation produced during the preparations for the preliminary workshop, then calls for the first, second and third workshop. During this the enterprise architect realises that there are certain perspectives that he would have to understand before moving forward with the workshop. 

    During the workshop he would have to approach the subject matter experts with an open mindset. This means that he would ask about how they work together and what tooling (Application Components) they are using in order to get the major steps in the business process working. This would require a set of open questions such as:

    • When making a bid for a new project what applications do you make use of?
    • Who will you be contacting and how do you do so?
    • Where do you store bid, project and customer data?
    • How do you create an overview of ongoing bids, project and customer data?

    The above questions are to lead to the overview of  business applications in scope and how the dataflow works as of today. The background information that the enterprise architect produced based on the workshop with the head of departments can be used as a source of inspiration and can be shared with the stakeholders before the meeting takes place, so they have the opportunity to provide relevant information during the workshop.

    The second workshop would be more about the exact business interfaces and the subsequent identification of needed integrations for supporting the dataflow among the business applications in the AEC-company. The secondary purpose of this workshop is to give the business stakeholders the necessary help to come up with improvements in the form of the TO-BE process. A bit prematurely, it could look like the below illustration, but it would have to be clarified:

    The third and the last workshop is to ensure alignment among the stakeholders on how the processes should be digitally supported. In between these workshops the enterprise architect will engage with the business stakeholders to get their viewpoints and refine the models and the recommendations.

    Line of Sight

    The enterprise architect has now the application view of how the business process likely would be like after the transition architecture will take place for the bid process:

    From the bid management capability view a lot of new information is disclosed:

  • Transition Architecture

    Transition Architecture

    The enterprise architecture of the AEC.company has now the overview of the as-is architecture of the AEC-company, and the enterprise architect revisits the high-level analysis that he conducted for the core business processes and the capabilities of the AEC-company, since this high-level analysis identified that the business strategy “Partnering for Green Construction” leaves some gaps that will have to be addressed by the enterprise architecture function and by the IT-department in the AEC-company in general:

    • The first gap is the lack of knowledge of how to digitalise the core processes in the AEC-company.
    • The second gap is the lack of knowledge of needed operating model improvements.
    • The third gap is the lack of knowledge of business process reengineering.
    • The fourth gap is the lack of an IT-strategic plan.

    These gaps will have to be dealt with in a coherent manner, since it would make no sense for the AEC-company to develop any deliverables of the IT-strategic plan without prior knowledge of how deliver better digitalisation of business processes, how to handle the operating model for the AEC-company in the 2030 plateau, where the business strategy “Partnering for Green Construction” will be delivered. The enterprise architect thought for a while and he realised that he would have to begin preparing workshops to capture the relevant information for the AEC-company to design the relevant architecture strategy and IT-strategy (Course of Action) for the AEC-company to succeed with the business strategy (Course of Action) known as “Partnering for Green Construction”.

    In order for the enterprise to assist the Chief Technology Officer and the IT-department filling the gaps, then he realises that he will have to call relevant stakeholders to a workshop. In this case he reuses the information he collected from the original interview of the heads of departments that he will have also to include the subject matter experts in the individual departments to gain the insights in the workshops. He decides to conduct three workshops for each of the core processes that earlier on have been identified as relevant to improve as part of the strategy, which also will improve the capabilities. The first workshop for each of the core business processes will be about the introduction of what is to be dealt with during the first workshop and the subsequent two workshops, and usually the first workshop is about identifying what is done today, and what is not working according to the subject matter experts. The second workshop will be about how the core business process looks like today and how it could be looking after it has been improved. The last workshop and final workshop for each of the core business processes will be like when implemented and what IT-systems will be when the core processes have been implemented.

    Since this approach is somewhat new for the stakeholders in the AEC-company, then the enterprise architect will have to come up with some suggestions up-front to inspire the subject matter experts during the workshops.

    The first process and subsequent capability that the enterprise architect starts with is the bidding process.

    The bidding process consists of a number of steps and it consists of a number of IT-systems that are used.

    The assumed most critical in these cases are the Office productivity suite since a lot of the communication and organisation of the bids takes place by initiating communication in the relevant departments and teams in the AEC-company.

    The enterprise architect realises that the primary application according to his preliminary analysis shows that Microsoft Office Outlook is to be considered a central business application in the as-is version of the core business process, and it is followed by Microsoft Office Word and Microsoft Office Excel for the internal use for calculating a bid. Lastly, if the AEC-company’s bid is accepted, then Microsoft Office Outlook and the different business applications from Autodesk comes into play in order to provide the relevant visuals for the different stakeholders at the customer side, when or if this is needed:

    The Line of Sight

    The enterprise architect now has the opportunity to look into what the bidding process consists of:

    In addition to this the enterprise architect has the opportunity to use both the business process view and the application view to see what the business process consists of and how it is served digitally as-is. In practice the top-down approach is preferred for strategic planning (course of actions) and the application view can be used for identifying tactical opportunities for business optimization through better use of technologies. This is what the two below diagrams are showing:

  • Products and Applications

    Products and Applications

    The enterprise architect continues his analysis of the AEC-company by continuing the modelling of the information that he collected from the workshop with the head of departments, and by reading through the notes from the workshop the enterprise architect could identify some of the  business applications  used to produce the products. 

    The reason for why the enterprise architect thinks in the terms of business applications and not in the terms of the ArchiMate Language’s use of the terminology is due to business applications are important applications and not “just” applications used for everyday purposes, and in most organisations then the enterprise architect will not be able to keep track of all of the applications used by the organisation. Nonetheless, to ease the communications of the ArchiMate Language the references to application(s) are used.

    The enterprise architect recalls that the AEC-company produces these products today:

    • Construction Consulting.
    • Engineering Consulting.
    • Sustainability Consulting.

    The enterprise architect chooses to visualize the applications by using the ArchiMate element “Application Component”.

    On a side note, then an application can consist of multiple application components, but for this example a business application consists of one application component only.

    The enterprise architect maps the products to the business applications. The enterprise architect identifies that the illustration provides a good basis for knowledge sharing and alignment, and that the AEC-company can make use of to support the IT-strategy of the company and a high-level overview of how digital disturbance can impact the business operations. The below illustration shows the relationship between the products and the business applications:

    The enterprise architect identifies that the products Construction Consulting and Engineering Consulting are supported by the same applications. This is due to the building information modelling (BIM) software capabilities of the applications so these can help with the calculations and the design of the different engineering tasks and with the planning and management of the construction sites.

    The enterprise architect reuses the model on products and processes and added the business applications to the illustration, so it becomes clear for him and other stakeholders in the AEC-company how the capabilities, business processes, products and applications are connected:

    Line of Sight

    The product of Engineering Consulting and how the applications are serving the production of it:

    The product of Engineering Consulting and how the product is realizing capabilities, served by business processes, realizing principles, and how it is served by applications:

    The product of Sustainability Consulting and how it is served by the application Product LCA (Life Cycle Analysis):

    The product of Sustainability Consulting and how the product is realizing capabilities, served by business processes, realizes courses of actions (Function strategies) and realizes principles:

    The product of Construction Consulting and how the applications are serving the production of it:

    The product of Construction Consulting and how the product is realizing capabilities, served by business processes, realizing principles, and how it is served by applications:

    From a capabilities planning point of view the line of sight from the capability “Construction Planning Management” it is visible that there is a portfolio of applications enabling it:

    The above illustration is considered 6 levels below the capability layer in the Archi-tool used to produce the ArchiMate mapping.