New member:

Ben Heideveld

May 04, 2022 14:43

 Hi, my name is Ben Heideveld. 

I started at Stedin this week. Before I worked at Shell and led the CoE BiZZdesign for Shell Architects. I am a newbie to BlueDolphin though.

Reach me at ben.heideveld@stedin.net

Stedin is a Dutch Distribution System Operator, who distributes natural gas and electrical power to consumers and businesses.

0

• 

  David Allen

  December 29, 2022 17:04

  Hello Ben. I am David Allen, the architecture manager with Gravie, Inc. in Minneapolis, Minnesota, US

  I just started learning Blue Dolphin.

  0
• 

  Zevans

  January 16, 2024 18:18

  Hi David and Ben,

  I am just now beginning my Blue Dolphin journey.  Any lessons learned, best practices you've learned having operated the software for a year now?

  0
• 

  David Allen

  January 16, 2024 18:22

  Hi, Zevans . I would be happy to share my thoughts. Can you tell me a bit about what you hope to do with BlueDolphin? What are some of the problems you are trying to solve? 

  0
• 

  Zevans

  January 17, 2024 13:23

  We are trying to create high level and detailed process maps for our entire organization to show how each group is integrated with each other, the applications that each group uses, responsibilities of each role in the organization, etc.

  Questions we are struggling with on how to start is:

  - Naming convention of the levels, should it be by department, or should it be numbers like the APQC structure referenced in trainings.

  - Reporting.  We want to create a connection with Power BI to show high level reporting by application, role, etc.  We also want to be able to see which views or processes are being looked at the most by users with read only access in the organization.  So we can see who is actually using blue dolphin by user and department.

  I appreciate the quick response.

  0
• 

  David Allen

  January 17, 2024 14:07

  I have not used Power BI so cannot help there.

  I recommend you do the high-level processes in ArchiMate, not the BPMN tool. 

  Naming conventions: 

  If you do it by department, it will be easier for your business teams to comprehend (at first). This may be a good choice for documenting current state, because that is probably how everyone in your company sees things. You can do a heatmap at process level to indicate opportunities for improvement.

  Once everyone understands the issues and shows a will to improve, you could stick with the same model. Or you could invite them to re-envision the organization with the APQC version. This may give them a fresh perspective and serve better in the long run to educate employees about what the company does. Switching from Dept to APQC may be able to reuse all of what you did before.

   

  0

Please sign in to leave a comment.