YaSM

The YaSM process model for ARIS™ in BPMN notation ► https://lnkd.in/dV-s6Jc -- ARIS, one of the pioneers of business process management tools, has just turned 30. ARIS popularized 'event-driven process chains' (EPCs) as a modeling language, and long-standing users of ARIS will be familiar with this way of describing business processes.   But over the years Business Process Model and Notation (BPMN) has emerged as the de-facto standard for business process diagrams, and support in ARIS for BPMN has much improved. Today, new users of ARIS will most likely choose BPMN over EPC notation.   So we have upgraded our ARIS templates to the latest BPMN model and symbol types.   On the #YaSM website you will find a complete overview of the various models and contents included in the YaSM Process Map for ARIS, complete with screen shots.   If you would like to do a test install, please get in touch!   #ServiceManagement #ARIS #BPMN

YaSM #StrategyManagement ► https://lnkd.in/d4e2XYb -- All service management frameworks recommend that service providers apply strategic thinking to guide the development of their business. The concepts and ideas of 'strategic management' have a long history and are a whole management discipline in their own right, with numerous models and frameworks to support strategic decision-making in businesses. In the #YaSM service management model we boiled down the strategic process to the essentials. -- From our YaSM #ServiceManagement Wiki

The most important #metrics to track in #ServiceManagement ► https://lnkd.in/daeDdWq -- Defining process metrics is above all about deciding what exactly is considered 'successful' process execution.   The #YaSM Wiki lists the relevant #KPIs for the service lifecycle processes and supporting processes that can be managed in the long term.   #YaSM #EnterpriseServiceManagement #ITSM

Does DevOps replace ITSM and service management best practice? ► https://lnkd.in/d8KDTwH -- ITSM frameworks like #ITIL® have earned themselves a reputation for being overly complex, slowing organizations down. DevOps has often been seen as a way to break free from this world of rigid processes and get things done faster.   There are many benefits of DevOps, but over time it has become clear that organizations can hardly work with free-wheeling cross-functional teams alone. Properly defined processes are still needed to provide direction and control. How else would organizations ensure, for example, that the services offered are aligned with customer needs, and delivered as promised?   So today, the common view is that #DevOps and #ITSM are not the same. They are complementary and should be combined!   #YaSM #ServiceManagement

Video: Service management process templates for BIC Process Design® ► https://lnkd.in/eyjTGSsC -- The YaSM process model for #ServiceManagement is available for various platforms, among them BIC Platform® - a #ProcessManagement tool that is used by businesses and public administrations for modeling, analyzing and controlling business processes.   In this video, Stefan Kempter shows how to import the YaSM repository into your BIC Process Design, and he provides an overview of the process diagrams and contents included in the YaSM® Process Map for BIC.   #ServiceProviders #YaSM #BICplatform

The problem management process in the YaSM model ► https://lnkd.in/dFeDpJA -- YaSM #ProblemManagement is about managing the lifecycle of all problems. A "problem" is the underlying cause of one or several (potential) incidents.   The primary objective of the process is to prevent service incidents from happening, and to minimize the impact of incidents which cannot be prevented.   The process is aligned with #ISO20000, the international standard for #ServiceManagement, and it corresponds to the #ITIL4 practices of 'problem management'.   In our free YaSM Wiki you'll find the detailed process description, definitions of the process outputs, suitable process metrics and the responsibility matrix!   #ESM #ITSM #YaSM

Video: The YaSM data model and document templates ► https://lnkd.in/dtXX47s -- If you have some experience with enterprise modeling and describing the essential components of a business, you will know that enterprise architectures usually cover different domains, such as the business processes, the human resources and the data required by the organization to operate.   The data domain describes the documents and records ('data objects') created in the #ServiceManagement processes, such as - Service definitions, - The service portfolio, - Customer service agreements, - And incident records.   The 'YaSM data model' and the 'object lifecycle diagrams' in the #YaSM® Process Map provide an overview of these service management data objects, with their key relationships.

The incident management process in the YaSM model ► https://lnkd.in/dNbinfx -- YaSM's incident management process is about resolving service incidents (reports of suspected or actual service failures) or requests for service.   In the case of service incidents, the primary objective of the process is to return the service to users as quickly as possible.   In some cases this involves applying a workaround if the root cause cannot be readily identified and/ or resolved.   The process is aligned with #ISO20000, the international standard for #ServiceManagement, and it corresponds to the #ITIL4 practices of 'incident management', 'service desk' and 'service request management'.   To get the complete picture, please visit the YaSM Service Management Wiki where you'll find the detailed process description, descriptions of the process outputs, suitable process metrics and the responsibility matrix!   #ITSM #EnterpriseServiceManagement #ESM #YaSM

What is #EnterpriseServiceManagement, and what are the benefits of ESM? ► https://lnkd.in/d3eTsNU -- Enterprise service management (#ESM) does not have a long history yet, but IT organizations have been following the IT service management guidance for decades and seen many improvements.   If you would like to learn more about the history of enterprise service management and what it is about, head over to our #YaSM Service Management Wiki!

Service transition ► https://lnkd.in/eFk5Nshm -- #ServiceTransition is about ensuring that any modifications or transitions to the live operational environment meet the agreed expectations of the business, customers and users. This includes high-level activities such as - planning and coordinating service changes, - building and testing new or changed service components, - and deploying new or changed service components into the live environment.   The service build process in #YaSM gets triggered by the service design process once a service definition and a service implementation blueprint have been created. At the end of the process, the service that is "ready for activation", which means customers can now be invited to sign a service agreement for the service and start using it.   #ServiceProviders #ITSM #EnterpriseServiceManagement #ServiceManagement