• No se han encontrado resultados

4.1. GEOLOGIA LOCAL

4.1.3. GEOLOGÍA ECONÓMICA

4.1.3.4. Reconocimiento de vetas en los sectores de Patara y Coricancha

In order to evaluate the utility of the proposed migration plan of figure 44 in this thesis we will conduct several interviews with experts from Ernst & Young and clients of Ernst & Young. This interview will determine if the proposed migration plan will provide a usable template for practitioners to manage the transition from the “as-is” situation to the “to-be” model in their organization. Practitioners will also be asked if they think that following the migration plan proposed in this paper will help their organizations maximize the “to-be” process information management performance. One Ernst & Young expert will be interviewed for this interview as well as two client experts from companies with different data-driven IA maturity. The interview structure and results can be found in appendix I. The interviewees indicated that overall the conceptual migration plan model of figure 44 provided a good overview of how a transition from the “as-is” to the “to-be” situation of this thesis will look like. All interviewees indicated that this model also provided a good practical baseline for experts that are starting up such a transition. Regarding the deliverables in the migration plan model one of the interviewees indicated that in the strategic plan plateau of the model she would have expected a policy and tool selection strategy deliverable. We indicated that this is one of the aspects of the technical architectural plan and the organizational transition plan, but we understood that this was not clear from the interviewee’s point of view. In the validated beta version model of figure 45 we have chosen not to add separate deliverables for these aspects in the migration plan beta version of figure 45, but we have instead chosen to describe the deliverables separately in table 4. Another expert indicated that it is smart to add a business case deliverable for the strategic plan plateau. From this business case the letter of commitment, representing the commitment of the stakeholders, can be derived better. We agreed to this and have added this in figure 45. Two experts indicated that the process was to linear and should include feedback loops in the lowest level of the model. Feedback loops have been added in the model of figure 45. All experts indicated that the training activities in the model are very important and combining this with a feedback loop to the implanting team will make sure the project results will be better. In addition to this all experts indicated that stakeholder commitment to the project prior to the start of implementation is of vital importance. Two experts expected that the information management performance of the “to-be” situation would be better when following this migration plan in contrast to working without a plan. One of the experts thought it would only decrease the implementation time, but would not result in better information

management performance. All experts indicated that it is smart to start with the key business processes and systems as indicated in the migration plan. However two experts indicated that they would probably do a pilot on an easy to implement system first. Our University of Twente supervisors indicated that during the migration process it would be vital to track if the CSF’s are accounted for. These monitoring activities have also been added to the beta version migration plan model of figure 45.

Table 4 provides a more detailed description of the different deliverables described in the migration plan of figure 45 of this paper.

Migration Plan Deliverable Input Activity Tools & Techniques Output

• List of stakeholders

• Prediction of cost and benefit over time

• List of critical systems and processes

• Transtion goals

2. Letter of Commitment • List of stakeholders • Mediation and securing commitment • Discussion based on the business

case • Letter of commitment

• Three lines of defense data need based on XES

• Determine strategy for event data capture

• Strategy development tools and techniques

• List of data/process mining tool vendors

• Determine strategy for data/process

mining tool selection • Event data capture plan

• Selection of data/process mining

vendors • Technical architectural plan

• List of stakeholders

• Developing a strategy to maintain stakeholder commitment throughout the project

• Clear stakeholder commitment throughout the project • List of essential data and process

mining courses and trainings

• Matching employees with relevant

and essential trainings • Human resource training plan

• To-be model gap analysis • Determine policies relevant to the to- be situation

• Strategy development tools and

techniques • To-be situation policy list

• Technical architectural plan

• Determine when to start with data and process analysis activities and on which processes and systems

• Policy development techniques • Organizational transition plan • Technical architectural plan

• Human resource training plan • Organizational transition plan 7. Data/Process Mining

Infrastructure • Technical architectural plan

• Enabling event data capture in the business systems to accommodate three lines of defense data need

• Event data capture tools and techniques

• Infrastructure based on the three lines of defense data need and the XES standard • Datasets of event data capture

enabled systems • Skilled employees • To-be situation model • Event data

• Line of defense sepcific controls • Event data driven dashboard information

• Skilled employees • To-be situation model

• Detailed business case

• Data analysis based internal audit

• Working via the to-be situation model using data sets from systems that the have event data capture enabled

10. Process Analysis Audit Service

• Working via the to-be situation model using event data-driven dashboards for analysis activities

• Process analysis tools and techniques

• Process analysis based internal audit

9. Business Service Platforms

• Develop event data-driven dashboards for the three lines of defense

• Dashboard development tools and techniques

• Event data-driven dashboards for the three lines of defense • List of critical systems and

processes

• Cost-benefit analysis • Listing of corporate skills and capabilities

• Financial analysis and prediction techinques

• Sensitivity analysis

• Data analysis tools and techniques • Planning tools and techniques

• Planning of activities on a timeline • Road map including timeplanning • Strategy development tools and

techniques • Selection strategy 1. Business Case 3. Technical Architectural Plan 4. Human Resource Training Plan 5. Organizational Transition Plan 6. Road Map

8. Data Analysis Audit Service

Documento similar