Difference between revisions of "ZUGSEIL Lifecycle Management"

From ZUGSEIL Wiki
Jump to navigation Jump to search
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
Asset tracking through '''ZUGSEIL Lifecycle Management (LCM)''' is a valuable tool for organizations that need to manage and maintain large numbers of physical assets, It helps to ensure that these assets are used effectively and efficiently, and that they are properly accounted for and maintained over time. Asset tracking can be used in a variety of industries, including manufacturing, logistics, healthcare, and retail, among others. The information gathered through asset tracking can also be used for accounting purposes, as well as for compliance with regulations and industry standards.
'''ZUGSEIL Lifecycle Management''' (LCM) is a fundamental concept to ZUGSEIL , which enables management and maintenance of large numbers of physical assets with:


=== Core functionality ===
* current location
* current state
* lifecycle history from first contact to decomissioning


* Combine procurement of assets with initial assignment (if desired)
Usage scenarios are
* Allows re-assignment and resource planning of assets
* Tracking of assets over their entire lifecycle across company borders
*Organize maintenance for assets (laundry, refurbishment, )


=== Reasons for LCM ===
* Management of personal protective equipment
* Helping organizations to make informed decisions about how to manage and allocate their resources
* Management of workplace equipment
*Ensuring operational readiness of critical items (security checks)
* Managment of project based equipment
*Improve operational efficiency and reduce the risk of loss or theft
* general product    instance tracking or asset tracking
*Ecological footprint (Reuse scenarios of goods)


=== Integrates with ===
The conecpt of lifecycle management (LCM) is an integral part of the b-op data model and can be activated in our products by deployment of our [[ZUGSEIL Lifecycle Management Tools (LCM)]] service bundle.
* [[ZUGSEIL Shop]] - determine directly throughout the shopping process the first station of the lifecycle. This can save a lot of time and effort that procurement and assignment can be done in one step. Assignment of assets is supported by our [[ZUGSEIL SHOP Extension - Personal Equipment Management (SHOP-PEM)|Personal Equipment extension]] and the [[ZUGSEIL SHOP Extension - Workplace Equipment Management (SHOP-WEM)|Workplace Equipment extension]]
*[[ZUGSEIL Equipment Point of Service (POS-EQ)]] - this module is used when employees do not self-manage their equipment through the shop, but rather go to service stations which act as '''equipment service points'''.
*[[ZUGSEIL Service Fulfillment & Maintenance (SFM)]] - this module can be used to plan and perform (maintenance) services with assets. It can be used internally or externally supporting the [https://www.b-op.com inter-digital collaboration capabilities of b-op].


== Related Articles ==
== Cross company lifecycle management ==
With b-op exists the first state-of-the-art IT systems which allows lifecycle management which is not limited to the reach of one company. Existing systems lead to undesirable dependencies from service providers, which tell you to "help taking care of your product data" - but in reality they are creating customer binding for themselves and dependencies, ultimately resulting in higher spendings on your side.


* [[ZUGSEIL Procurement-Suite]]
With b-op enabling cross company lifecycle management, this unhealthy dependency can be resolved as the lifecycle data is automatically handed centralized at owner of the products. All partners can be integrated without any interfaces to be written or designed as long as all partners work with their own b-op digital. It is a unique selling preposition of ZUGSEIL to offer the [[ZUGSEIL Lifecycle Management Tools (LCM)|first life-cycle management solution]] based on b-op.
*[[ZUGSEIL Service Fulfillment & Maintenance (SFM)]]
 
* [[ZUGSEIL Shop]]
== Real world example ==
*[[ZUGSEIL SHOP Extension - Personal Equipment Management (SHOP-PEM)]]
Currently hugely scaled laundering businesses are getting more and more profitable. Profitability is driven by total-care, leasing or pay-as-you-use business models, which are based on data on products with customers: The laundry knows more on the customer specific lifecycle data than the customer himself. With this big knowledge advantage over the customers the scaled laundries can build very profitable business models based on superior knowledge than competition, but also on a good negotiation positions.
*[[ZUGSEIL SHOP Extension - Workplace Equipment Management (SHOP-WEM)]]
 
*[[ZUGSEIL Service Scheduling (SRS)]]
Implications:
*
 
__NOTOC__
*'''Massive information gap between laundry and customer'''
**The laundry has detailed information on the lifecycle (location, state, history) '''and can do''' data science on the data of the products of customer
**The customer in most cases has only the billing information and has very little information to verify and '''can not do data science''' on their own data.
**Information which would allow cost reductions or better understanding of the business are not accessible to the customer. This prevents a better negotiation position and better decisions on the customer side (e.g. on average usability of products) to bring down costs
**The laundry hands-out billing information on a regular basis - the customer does neither have time nor access to the main data to verify it.
*'''Undesirable partner binding'''
**Changing the laundry is a major project, which means a lot of IT investment to analyse the data and convert to the format of the new laundry partner.
**This makes changing the laundry partner a very painful process, putting a huge barrier to this endeavor.
* '''Bad ecological footprint due to lacking interoperability'''
** As data is only with one laundy patrner and the partner in most cases refuse to interoperate, customers can not mix laundry partners.
** Regional approaches, which would mean less logistics between the huge laundry sites and the decentral sites of customers, are blocked. This means that customers are incurred a larger ecological footprint. Exceptions are only possible with a major IT effort on the customer side.
* '''In-compliance with data privacy regulations'''
**The laundry in most cases has name and location of wearing persons of the customer. This is irresponsible and at least problemantic with DS-GVO / nDSG regulations, as unwanted profiling of the customer's staff is possible.
All these issues are resolved with a b-op based life cycle management as ZUGSEIL offers. The data is fully kept on the customers side and the laundries (multiple allowed) are just gettiing information as they request persmissions to deliver theirs service. As each of these services are authorized by the customer (automatically), purchase orders are issues for each service. Through this the entire process of servicing/maintainance becomes fully transparent to the customer, which is no longer bound to a single laundry. 
 
==Related articles==
* [[ZUGSEIL Lifecycle Management Tools (LCM)]]
 
[[Category:ZUGSEIL Abilities]]

Latest revision as of 20:05, 26 August 2023

ZUGSEIL Lifecycle Management (LCM) is a fundamental concept to ZUGSEIL , which enables management and maintenance of large numbers of physical assets with:

  • current location
  • current state
  • lifecycle history from first contact to decomissioning

Usage scenarios are

  • Management of personal protective equipment
  • Management of workplace equipment
  • Managment of project based equipment
  • general product instance tracking or asset tracking

The conecpt of lifecycle management (LCM) is an integral part of the b-op data model and can be activated in our products by deployment of our ZUGSEIL Lifecycle Management Tools (LCM) service bundle.

Cross company lifecycle management

With b-op exists the first state-of-the-art IT systems which allows lifecycle management which is not limited to the reach of one company. Existing systems lead to undesirable dependencies from service providers, which tell you to "help taking care of your product data" - but in reality they are creating customer binding for themselves and dependencies, ultimately resulting in higher spendings on your side.

With b-op enabling cross company lifecycle management, this unhealthy dependency can be resolved as the lifecycle data is automatically handed centralized at owner of the products. All partners can be integrated without any interfaces to be written or designed as long as all partners work with their own b-op digital. It is a unique selling preposition of ZUGSEIL to offer the first life-cycle management solution based on b-op.

Real world example

Currently hugely scaled laundering businesses are getting more and more profitable. Profitability is driven by total-care, leasing or pay-as-you-use business models, which are based on data on products with customers: The laundry knows more on the customer specific lifecycle data than the customer himself. With this big knowledge advantage over the customers the scaled laundries can build very profitable business models based on superior knowledge than competition, but also on a good negotiation positions.

Implications:

  • Massive information gap between laundry and customer
    • The laundry has detailed information on the lifecycle (location, state, history) and can do data science on the data of the products of customer
    • The customer in most cases has only the billing information and has very little information to verify and can not do data science on their own data.
    • Information which would allow cost reductions or better understanding of the business are not accessible to the customer. This prevents a better negotiation position and better decisions on the customer side (e.g. on average usability of products) to bring down costs
    • The laundry hands-out billing information on a regular basis - the customer does neither have time nor access to the main data to verify it.
  • Undesirable partner binding
    • Changing the laundry is a major project, which means a lot of IT investment to analyse the data and convert to the format of the new laundry partner.
    • This makes changing the laundry partner a very painful process, putting a huge barrier to this endeavor.
  • Bad ecological footprint due to lacking interoperability
    • As data is only with one laundy patrner and the partner in most cases refuse to interoperate, customers can not mix laundry partners.
    • Regional approaches, which would mean less logistics between the huge laundry sites and the decentral sites of customers, are blocked. This means that customers are incurred a larger ecological footprint. Exceptions are only possible with a major IT effort on the customer side.
  • In-compliance with data privacy regulations
    • The laundry in most cases has name and location of wearing persons of the customer. This is irresponsible and at least problemantic with DS-GVO / nDSG regulations, as unwanted profiling of the customer's staff is possible.

All these issues are resolved with a b-op based life cycle management as ZUGSEIL offers. The data is fully kept on the customers side and the laundries (multiple allowed) are just gettiing information as they request persmissions to deliver theirs service. As each of these services are authorized by the customer (automatically), purchase orders are issues for each service. Through this the entire process of servicing/maintainance becomes fully transparent to the customer, which is no longer bound to a single laundry.

Related articles