Modeling and Planning QMS using ArchiMate

[Duncan William Gibbons]

Hi all,

I would just like to get your opinions and hopefully even past experience of using ArchiMate and such EA methods for planning and modeling quality management systems (QMS) within the manufacturing industry. To me, it seems very logical to use such EA tools and methods to identify, model, and manage internal and external organizational factors, as well as information, material, resources, etc.

Has anyone tried this before, and possibly used EA and ArchiMate during a QMS audit?

Does anyone have any literary sources about this area?

Has anyone used ArchiMate for planning ERP and or PLM implementation?

And what are your general views on the topic?

Many thanks,

Duncan

[Pascal Dussart]

No experience with modeling QMS but the way you describe it " identify, model, and manage internal and external organizational factors, as well as information, material, resources, etc." seems a sensible use case for Archimate. As always, the challenge is knowing when to stop modeling in Archimate. From my experience, unless there are clear guidelines and rules and responsibilities defined about where EA stops and solution architecture starts, there's a risk of EA's going into too much detail while the real expertise to do that is with the solution architects/product specialists. But again: it all depends on how the organization perceives the world of architecture and (thus) how boundaries are defined. 

Regarding ERP and PLM (product lifecycle mngmnt, I assume) : I could get you in touch with people who might be of interest to you.  How about we connect on LinkedIn and see where we go from there?

--
Met vriendelijke groeten  - Best regards

Pascal Dussart

--
You received this message because you are subscribed to the Google Groups "ArchiMate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-archimate-f...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-archimate-forum/710e162f-bab0-434f-b4e9-b308a3a7971b%40googlegroups.com.

[Duncan William Gibbons]

Hi Pascal

Thanks for your input, I fully agree. Im currently playing around with ArchiMate mainly to conceptually/graphically model the organizational structure as part of my thesis, stopping at the machine/process level of abstraction whereby standard operating procedure are referenced. For the case I am using ArchiMate I see the value in having a graphical and potentially interactive model the organization (as opposed to a paper and text-based QMS that sits on the shelf) for employee training, stakeholder and upper management acceptance and ensure quality-focused and standardized processes are followed.

PS I sent you an invite on LinkedIn

All the best,

Duncan

To unsubscribe from this group and stop receiving emails from it, send an email to open-archimate-forum+unsub...@googlegroups.com.

[Mastering ArchiMate]

On 27 May 2020, at 19:23, Pascal Dussart <pascal....@april10.be> wrote:

No experience with modeling QMS but the way you describe it " identify, model, and manage internal and external organizational factors, as well as information, material, resources, etc." seems a sensible use case for Archimate. As always, the challenge is knowing when to stop modeling in Archimate. From my experience, unless there are clear guidelines and rules and responsibilities defined about where EA stops and solution architecture starts, there's a risk of EA's going into too much detail while the real expertise to do that is with the solution architects/product specialists. But again: it all depends on how the organization perceives the world of architecture and (thus) how boundaries are defined. 

ArchiMate is equally usable for high over and detailed architectures and works very well for solution architectures. If you are a high over architect and you model your stuff in ArchiMate that doesn’t mean others can model solutuion architectures in it. In fact, I consider ArchiMate much more useful for solution architectures (or entire landscapes of solution architectures) than for strategy level stuff (where the metamodel doesn’t really bring you a lot of advantages.

As far as I’m concerned there is no clear demarcation between ea and solution architecture, sometimes certain details are essential.

As far as QMS goes, just look at it as you would look at any business activity: what is the behaviour, what are the objects, what are the subjects. ArchiMate is a EA grammar/language and it can only be that if it can model what any business/organisation does.  

As always: you have to answer the question: how is this model going to be used. That tells you what has to go into a model. ArchiMate itself is agnostic.

G