Wednesday, October 01, 2014
Thursday, September 11, 2014
e-Up new website is live
Dear,
I have abandoned this blog long time ago and for good.. I am sorry for the amount of readers that regularly checked this blog for some news.
The recent 5 years long financial crisis has impacted everyone and everything and so the publishers I was collaborating for to write my articles. Additionally, the attitude of corporations towards consultancy has changed, also due to the lack of quality of many providers, guilty of overpricing very bad quality services.
But they say during crisis the most innovative ideas take place. I hope this is the same in our case, as we dedicated time to hard work and research and started a company based in Dublin in 2012: e-Up Unified Perspective.
We just launched our new website and the new software at the same time.
e-Tools is the result of advanced research and consultancy, and its aim is supporting the implementation and above all the analysis of all existing Siebel applications that are still out there, despite the slow reduction of implementations due to the competition, above all versus Salesforce.com, as prefered CRM platform.
To be honest the first competitor of Siebel has been been its new owner: Oracle. It's their policy towards the one time first CRM platform in the world, that has actually killed it.
As I will attend next Oracle Open World and the Siebel 2014 IP will be presented, I am really curious about the way Oracle will promote its strategy.
Despite some employees still insist on the fact that Siebel is not dead and that new functionalities will be presented towards next years, the market seems to have less and less interest on this technology, even after the advent of Open UI.
Siebel implementations failed and continue to fail because the lack of best practices and tools that support this. Business analysis, for example, has never been supported or "educated" by Oracle, leaving it to the disorganization of Organizations. or to the trends of too heavy and too generic methodologies.
e-Tools will allow the modelling of visual artefacts for all the phases of a typical Siebel implementation, easing the adoption of best practices.
I refer to Siebel Tools as an old punch cards machine, with its old-fashioned parametrization approach, without mentioning the lack of support for anything else (requirements gathering, modelling, application design, etc.). Have a look at the first video about e-Tools and let me know if you realize the difference with the standard Siebel Tools:
If cloud is now so trendy, be sure you will soon find silos also in the sky, not only on your premises...
But I have probably taken too much time and too much space for the initial intention of this post, therefore I end simply simply inviting you to visit our new website www.e-up.pro.
We shall probably introduce a blog section on the website, therefore I might continue posting some articles there... stay tuned!
published by Dr. Breschi Manuel a 7:22 PM 0 commenti
Etichette: e-Up Unified Perspective, Open UI, Oracle open World, Oracle Siebel, Salesforce.com, Siebel Tools
Sunday, February 01, 2009
Asset-based ordering
As part of the Order Management module, Asset-based ordering needs to be activated separately, allowing customization of workflows and business services.
Asset-based ordering bases on a prior order by the customer, thus on the fact that the customer already owns (or uses) a product (service) provided by the company or a partner. A customer that has acquired telecommunications services, providing the organization with a phone line and a phone number, owns, from the provider’s perspective, a valuable Asset on which building on future activities (a key strategy CRM point is in fact maintaining existing customers, before acquiring new ones). The client could, for example, decide to request other phone numbers on the same line, or to split existing numbers on different lines.
Asset-based ordering leverages the order management process as it supports the creation and management of complex orders (containing complex pricing, combined billing types, combinations of services, multiple suppliers, etc.). In the example given above, the phone line could be the property of a partner (as the distributor in an Energy business scenario), while even the service could be provided by another one; nevertheless, the client receives one bill containing the information for the various services, as well as segmented prices based on consumption.
After the first negotiation and order with the client, the sales worker can generate an Asset directly from the order. Starting from this Asset, new quotes and orders can be generated, or changes can be done to existing quotes orders. If the client changes the initial order, changes can be accepted (based on company’s policies) and implemented. It is easier as well managing subscriptions as the Asset management allows suspending, discontinuing or resuming the service provided. If the client does not pay the bill, the provider can decide to act by suspending the service until the payment is realized, so resuming the existing service. A household might request the provider to interrupt the service over a period of time (when they go on vacation for 3 months they do not need the home phone). In this case the provider stops the service and resumes it again at the client’s request. Figure 1 shows a Crm-UP, UML compliant, description of the functional cases managed by Siebel Asset-based ordering module (the module is depicted as the blue cube, reconnecting the business scenario to technical aspects of the Siebel architecture – as a specific case study).
Figure 1. Asset-based ordering – overview use-cases model describing the main actions supported for a sales worker, interacting with the system.
The Assets owned by the customer are registered in a service profile, indicating the installed assets. It is easily accessed from the Account Screen, Installed Assets view, and allows the customization of specific automated workflows to reduce the amount of time to create quotes, orders and assets.
There are three scenarios for initiating Asset ordering. The client can ask for a revision of an existing order (not yet passed over the point of no return). In this case, after negotiating the quote and starting the order process, the client decides to change something (a product/service, or conditions of the order, etc.). Depending on the organizational policies, the order might still be changed, unless is has reached a point when the changing costs are too high (the point of no return for order execution).
A second scenario envisions the client as owner of an Asset, but wishing to modify it. It is the case, for example, of a telco company’s client that wants to change from one type of contract to another, because her/his needs have changed, so that less free minutes are required (a down-grade of contract).
The last scenario envisions the modification of the prior order by adding a new item. The client might want a new phone line and number to be added to the prior subscription. The basic conditions are not modified in this case, just new items are added and might have an impact on the general order (on the sum, etc.).
Figure 2. General flow of Asset-based ordering following three initialization scenarios.
The three scenarios have different evolutions, depicted in figure 2. When modifying an existing Asset, the Sales Worker has to start from the Assets screen and fill in the details as required. Afterwards it is possible to generate a new quote and transform it in an order (following internal processes) with the help of automated workflows (like automatic generation of Quote from Asset, and of Order from Quote). When adding a new item, the Sales Worker starts from the Quotes screen, creating the Quote and filing in its details. If the change regards an existing Order, following organizational policies, the Sales Worker accesses directly the Order and performs the modifications. The execution of the order and its monitoring is facilitated by the integration with back-office systems.
Businesses that combine products and services, such as Telecommunication and Energy industry, can take advantage of the facilities offered by Asset-based ordering, reducing client-service time and improving overall monitoring of customer and service.
published by Dr. Breschi Manuel a 1:42 PM 0 commenti
Etichette: Asset-based ordering, Methodology, Oracle Siebel, Order Management
Friday, December 12, 2008
Order Management – General introduction
Among the other Oracle Siebel CRM modules, Order Management is one of the most used and requested. This is due to its employment in the sales process, across quote and order management processes. The advantages offered by Siebel CRM are the integration with back-office applications (for products, availability, orders, credit check, taxation, etc.) and automation (through various customizable workflows), as well as flexible support throughout the sales process.
Before getting to use it in the Sales process, it is important to prepare the grounds for Order Management usage. As a first step, it is necessary to set up a series of elements and their characteristics (not all of the following are mandatory): Accounts and Contacts, Salespeople, Products, Pricing and Catalogs, Shipping Information, Tax Calculations, Payment Terms, Inventory Locations, Order Types, Order Statuses, Product Selection Favorites, Activity Plan Tempaltes, Availability to Promise, Asset-Based Ordering.
There are also several changes to perform in the application such as Activating Workflows, customizing the Sales, Quote and Order processes, customizing the List of Values, etc.
Integrations with the Back-Office applications could be necessary as well, depending on the infrastructure. Among them:
- Quote and Order process integration assures correct quote/order status and communication among front and back-office departments;
- Product Availability - information is retrieved from third party applications;
- Credit-Check – indicates if the customer has enough credit for purchasing the product ;
- Taxation – facilitates tax calculation based on organization and customer location (taxation legislations).
Creating and managing the catalog establishes the structure of products and services in order to facilitate access definition and navigation. It employs Catalog, Category, Subcategory and Product elements to establish hierarchies.
Presentations can be adapted by customizing the Display Templates and attribute search can be implemented to facilitate finding of products based on their characteristics.
For facilitated products up and cross-selling, the Product Recommendations need to be set in place. Messages are created and related to products in order to indicate to the salesperson possible up-sell and cross-sell products. A score is used for categorizing recommendations based on their importance in comparison with other recommendations, facilitating viewing and decision of what recommendation to make.
One of the competitive characteristics of a company is its approach to the sales process. Oracle Siebel CRM supports variations in the quotes and order processes facilitating flexible adaptation thus the creation of competitive advantages. As part of the Order Management implementation process it is necessary to define and map such processes in order to construct the best application support. In this step it is also very important to take into consideration the company strategy, the difference between it and the “real” selling process carried on by the employees, and decide the best way to suit both, assuring change management and user-acceptance.
A special type of approach to ordering is the asset-based ordering process. It allows companies to create assets from client’s orders, to create quotes for new products and services based on existing assets, create quotes to modify existing products and services, modify existing open orders, manage an existing service and gain visibility into the asset life cycle.
Order Management is a complex Oracle Siebel CRM module.
published by Dr. Breschi Manuel a 9:57 PM 0 commenti
Etichette: Asset based orders, Oracle Siebel, Order Management
Sunday, September 16, 2007
CRM 360° chooses Microsoft Dynamics CRM
There is one big contradiction in the consultancy area related to the CRM scenario. When a company, acting in whatever industry field, requests some kind of support to a consultancy company for the implementation of their own CRM strategy and the related Packaged Application, it expects something that goes beyond the possibilities it has internally.
Apart from the mere expertise on the customization of the platform (being Oracle Siebel, SAP CRM, Microsoft Dynamics or others), the consultancy should postulate a professional expertise in the business context that the application supports, that is the Customer Relationship Management as a general integrated approach to identify, acquire and retain customers.
Have you ever asked your provider which platform do they use internally to support the services they are offering to you, as a client?
Our point of view is that last five years and hundreds of unsatisfactory implementations around the globe should have taught that CRM is not just deploying a more or less customized Packaged Application in a company. We know, there's never time to do a complete analysis of the business and an optimization/adaptation of the processes, once we decide we have to implement something that helps us in the daily interaction with our customers. But this, moreover, underlines the importance of a qualified and business aware consultancy. Once delimeted the business sector, and (why not) the immediate low level requirements for a CRM implementation (salesmen need a concrete support? Contact Center operators should have access to the history of a client to provide better quality services?) a good consultancy should indicate the best solution for you and, above all, how to implement it not to throw your money in something you will never use or, on the contrary, bribing you with easy, light and simple solutions that will cost you in time, facing integration problems and an unrealistic view of your customers.
The real question we asked ourselves is: "how can I really sell myself as a CRM implementation expert and seriously offer my services to my clients, if I don't apply CRM both strategically and technically in my own organization?". Well, it's not so obvious, and daily experiences in many international projects show how poor the strategy in the relationship among the different stakeholders is. No, look, think about it: in consultancy often we are still just on the ERP processes matter, above all on the billing side...
We are aware that, if we don't live the same approach, no real professional support on the delivery of a complete and coeherent CRM infrastructure can be offered.
Let's face the truth: a company that wants to be customer oriented and consequently puts care in the relationship with its customers, doesn't receive the same kind of quality level from the consultancy it receives. This does matter!
Following this concept, based on an analysis of our current business, we have done a coeherent analysis and a consequent software selection, finally deiciding to implement Microsoft CRM (for the moment).
The reasons of this coiche rely on a clear knowledge and awareness of our business and our action scope, together with the functional and technical experience in different platforms.
Microsoft Dynamics is undoubtedly one of the lighter and general purpose CRM solutions. In comparison with other PAs it currently lacks of specific ad-hoc verticalizations, and we cannot exactly talk of functional flows that reproduce business processes in the navigation of the application. Even technologically, above all on the Contact Center side, there are limitations.
Microsoft CRM has the advantage of a full integration with the spreaded Office Automation tools (shall we discuss about the main analysis tool of many sales people, even if the organization has a main BI Tool?).
In any case, the main CRM Domains are there, and a good Model of the main CRM components can be available directly on your Outlook client and that of your colleagues and employees.
After some days of installation I would personally have something to say regarding the platform and component requirements, as well as of the lack of some notes that should be included in the official documentation, but let's keep this for another post...
In the meantime, think about this, and feel free to share with us your opinion. Your impression does matter!
published by Dr. Breschi Manuel a 3:17 PM 0 commenti
Etichette: Microsoft Dynamics CRM, Oracle Siebel, SAP CRM