Archive for February, 2009

Friday’s Feature: Snapshots In Enterprise 2.0 UX/UI – Microsoft Dynamics

Usability and User Experience Matter in Enterprise 2.0 Apps

Welcome to the first in a series of Friday’s Features showcasing the latest and greatest in enterprise apps usability.   Many ERP software vendors including Epicor, IFS, Infor, Lawson, Microsoft Dynamics, and Syspro have made significant progress in improving usability as they progress to Enterprise 2.0 apps.  As mentioned in a December 29th, 2008 post, customer expectations for Enterprise 2.0 apps include users rich user experiences, actionable insight, and business process orientation. The impact of overall user experience and user interaction often tie back to seven key Enterprise 2.0 characteristics:

  1. Richer user experiences - role based scenarios across various usability paradigms
  2. Business process orientation – support for end to end business processes
  3. Configurable change – designing with flexible models and rules instead of customizations
  4. Actionable insight – pulling all the key information to make a decision in the context of business process and user role
  5. Collaboration – providing secure private interactions and open and innovative connection with stakeholders
  6. Intelligent response – responding to contextual models and business events
  7. Hybrid deployment – deploying all models from on-premise, hosted, instance virtualization, multi-tenant SaaS, and cloud based BPO.

Part 1:  Microsoft Dynamics Highlights The Power of Role Tailored meets Microsoft’s “Rainbow Stack”

One key design point in the Microsoft approach is a role tailored approach based on the Microsoft Customer Model. Microsoft’s usability team modeled 1 corporate group, 5 departments and 61 personas.  These roles form the design basis of how users interact with process, data, and interface. The result – improved usability which reduces complexity, increases focus, promote likely actions, pushes information, supports collaboration, and ensures flexibility.   Add better adoption of Tools and Technology from the Microsoft Tools teams enables better integration with key products such as SharePoint, Office, Performance Point, and Project Server.  Here are a few highlights of the role tailored approach in action:

  • Role tailored view – ( Prakash, a project manager using Microsoft Dynamics NAV 2009). From the Microsoft Dynamics Customer Model -Prakash is part of the professional services team and is responsible for project delivery.  He works with Reina (i.e. Resource Manager), to provide adequate resources and staff.  He has approval authority for all project related changes as well as any other materials changes.
  • Role tailored view – ( Eduardo, a production planner using Microsoft Dynamics NAV 2009). From the Microsoft Dynamics Customer Model – Eduardo manages scheduling and planning of production. he often needs to reshuffle existing orders to make room for more urgent orders. He considers exceptions to be the rule.
  • Role tailored view – ( Stan, a small business owner using Microsoft Dynamics NAV 2009). From the Microsoft Dynamics Customer Model – Stan manages the business from start to finish. He is responsible for everything and has to understand every aspect of the business
  • Role tailored view with analytics – ( Sammy, shipping and receiving using Microsoft Dynamics NAV 2009). From the Microsoft Dynamics Customer Model – Sammy manages shipping and also receives goods and verifies them against purchase orders. He also supervises other warehouse employees.
  • Role tailored view with analytics – ( Ken, Controller using Microsoft Dynamics AX 2009). From the Microsoft Dynamics Customer Model – Ken tracks the departments’ financial goals. He continually improves processes to achieve financial goals.  he proposes and helps implement changes to optimize performance. He may approve documents and payments.
  • Environmental sustainability dashboard highlights analytics capability. Microsoft’s new solution attempts to meet growing demands for environmental sustainability by government regulations and litigation, NGO’s and media, business and consumer customers, financial markets and risk assessment, and employees. Using Microsoft Dynamics AX, a new environmental sustainability dashboard brings in information from a multitude of sources to help determine issues such as, “How green is my supply chain?”
  • Performance Management Balanced Scorecard demonstrates integration to Performance Point. Users can configure corporate scorecard, map point, corporate strategy maps, and other web parts in Microsoft Dynamics AX.
  • Office Integration with Microsoft Dynamics AX 2009 highlights native advantages.  Based on Microsoft Windows SharePoint Services, Microsoft Dynamics AX 2009 eliminates redundant data entry by enabling integrated data exports with Word, Excel, and Outlook.  Users of Microsoft Excel 2007 can build custom reports from an OLAP database and create Pivot Table Views via drag and drop metaphors.  Other 0ut of the box integrations include Microsoft Office Project Server and Microsoft Office Share Point Server.

Software Insiders Point of View Photo Stream (click image for details)

(Source: Microsoft Business Solutions, Microsoft Dynamics)

Your POV.

Do you like how your apps UI currently look?  Will user experience lead to cost savings for you?  Is this enough to make you want to switch?  What do you think of Microsoft’s UI?  Post your thoughts or send me a private email to rwang0@gmail.com.

Friday’s Feature: Snapshots in Enterprise 2.0 UX/UI

  1. Epicor 9
  2. Eshbel Priority 13
  3. IFS Applications 7.5
  4. Lawson SmartOffice 9.0x
  5. Microsoft Dynamics AX and NAV

Next Friday’s Feature: IFS’ iPod like user experience

Copyright © 2009 R Wang. All rights reserved.

News Analysis: SAP Launches Business Suite 7 – Transformational Change Or Expensive Repackaging?

From SAP’s Morton Street New York City marketing HQ, SAP publicly launched Business Suite 7 on February 4th, 2009.  At first, the suite offering of SAP PLM, SAP SRM, SAP SCM, SAP CRM, SAP ERP, and industry applications may seem like a repackaging exercise.  But on deeper analysis, there is a bit more than “harmonized” UI updates and a bundling of previous products with 3 letter acronyms.  In fact, the movement to a synchronized release structure for 5 of the key flagship products onto the common “switch framework” in SAP NetWeaver is no small technical feat.  Key highlights from this morning’s announcement include:

  • Synchronized release strategy improves upgrade experience. Product families in the Business Suite now use the same “Switch Framework”, which allows clients to upgrade 4 categories of enhancements that include usability, horizontal features, vertical features, and composite apps/web services.  This provides one upgrade strategy for all products and brings all the releases into synch.  Some clients have stated that this helped with reducing the pain of some upgrades.

    POV: The movement to synchronize all releases is a good start.   System integrators have traditionally bore the burden of integrating and synchronizing the various product families.  Going forward, customers will expect usage of a common data model via a revamped MDM approach.  With all products on the switch framework, customers can take advantage of the SAP Enhancement Pack technology, which makes SAP upgrades a tad bit easier, though mature SAP customers with a ton of user exits and customizations may beg to defer.  One key concern – will my EhP 27 be dependent on uptake of EhP3?  Also, SAP’s shift from 6 to 8 months for each enhancement package to 1 year may need to be reexamined in light of the quarterly pace of innovation found with the SaaS vendors.

  • Renewed focus on end to end business processes ties “Value Scenarios” to business drivers.  SAP focuses improvements by bringing together traditional functional fiefdoms across various roles.  One example of a value scenarios is collaborative demand and supply planning where SAP takes a process view across fiefdoms like sales, supply chain, operations: manufacturing, operations: procurement, and finance.  The goal: timely, profitable response to stakeholder demand.  Other examples include financial close processes, HR- recruiting and talent, sales-reporting, shared-services, etc.

    POV: Customers will find the Value Scenarios compelling as they align with the key business drivers facing today’s organizations (e.g operational efficiency, regulatory compliance, growth, and strategy).  The initial list covers a basic range of cross-functional processes.  Albeit limited in the initial launch, one can expect more to come from SAP in future enhancement packs (EhP).  As with all best practices, SAP will need to make it easy for customers to modify those scenarios.  SAP customers would want a library of business processes that are not based on the past but designed to change for the future. Partners and customers in the SAP ecosystem will also want an easy way to extend these processes so that they are supported in future upgrades.  This dependency on SAP Visual Composer and other SAP NetWeaver components may prove a learning and training hurdle for some customers.

  • Pay by module pricing  lessens the burden of buying a monolithic suite. SAP states that the new suite offering will now include options for customers to purchase by module.  Prospects do not have to buy the whole suite to activate each module and modules are at a more granular unit than an application family. In fact, SAP claims new customers can start one process at a time.

    POV: Enterprises could always just buy a functional module. However, users will most likely question what the dependencies are on other SAP infrastructure products.  If the footprint is too big, then this module to module approach may not pan out.  There may be hope if SAP manages to resurrect lessons learned from Business By Design (ByD) and serve up the modules in an on Demand fashion.  Hybrid deployment options may be the best approach for existing SAP customers and prospects who want to pipe in innovation or take advantage of new functionality.  Interesting to note that SAP did not focus more on other cost saving programs such as vendor financing and hosting to combat any SaaS vendor marketing pitches.

  • Usability improvements incorporate role based analytics.  Demo watchers were treated to new dashboards and visualization technology. Many of these scenarios focused on role based analytics which are an important part of the progression towards Web 2.0 Enterprise Apps.  These analytics deliver role based and process based information for actionable insight.

    POV: In the demo during the event, SAP showcased more integration of BOBJ with heavy usage of SAP NetWeaver Business Client (NWBC) and SAP’s BPM componentry.  What’s interesting is not the lack of usage of SAP GUI but the improved integration with BOBJ components such as Xcelsius, which of course were vendor agnostic to begin with. Users will still want to know what UI strategy should they move forward with as BS 7 progresses.

The bottom line – more than repackaging but will clients find this compelling enough to upgrade?

Available May 21st, 2009, Business Suite 7 provides much needed change to SAP customers and is another carrot to incentivize customers to upgrade. The challenge will be to make this compelling enough to prospects and existing customers in the midst of the downturn.  Conversations with over 800 SAP clients in the past 5 months indicate that SAP can do more by emphasizing financing options and potentially lowering maintenance fees.  As clients look to recession proof their apps strategy, we hope SAP continues to find new ways to lower the cost of ownership and speed up the delivery of innovation.  Announcements of the adoption of RunSAP methodology by Atos Origin, CapGemini, EDS, Hyperformix, IBM and Wipro show good alignment in the partner ecosystem.  However, more effort should be invested in concert with other solution providers such as Acresso, GuiXT, Hayes Technology, IBM Optim, IntelliCorp, VMWare, and West Trax who focus on reducing the overall cost of owning SAP.  Moreover, SAP could take the opportunity during this launch to restore  vendor-client trust by lowering the overall cost of ownership, delivering more choices in deployment options, increasing the investment and pace of innovation, supporting greater heterogeneity, and orchestrating more value in its partner ecosystems.

Your POV.

As a prospect, are you now more or less compelled to buy an SAP solution?  As an existing customer, do you feel this is a good use of your maintenance dollar?  Will this push you over the edge to move to the next upgrade?  Post your thoughts or send me a private email to rwang0@gmail.com.

Check out my esteemed colleague Paul D. Hamerman’s view on Business Suite 7 on the Forrester Business Process And Applications Blog

Related posts and blogs worth checking out on SAP’s Business Suite 7 (#BS7)
(Updated February 6th 00:46 PST -8:00)

Copyright © 2009 R Wang. All rights reserved.

Monday’s Musings: Master Data Management – Do Styles of MDM Matter Anymore?

Three Architectural Styles Represent Different Technologies To Build MDM

In 2003, customer data hub (CDI), product information management, and master data management (MDM) vendors strived to differentiate themselves by architectural style.  Each approach had its advantages and disadvantages.  A religion about styles emerged overnight along with a hard core following.  Here’s a quick recap (see Figure 1):

Figure 1.  The Three Architectural Styles of Master Data Management

Three Common Styles Of Master Data Management

The bottom line – choose a style that aligns with your project’s business driver
While these approaches still exist, leading vendors such as D&B Purisma, IBM, Initiate Systems, Oracle, Oracle-Siebel, SAS DataFlux, and Siperian now have offerings in more than one style. This may make the question seem less relevant, however, its still important to understand the trade-offs while beginning your MDM journey.  In fact, it’s best to align the style and approach based on your business driver.  Here’s a high level summary:

  • Cross-referenced registry delivers rapid results for operational efficiency business drivers. This approach is best suited for rapid implementation scenarios such as POC’s that prove the value of master data.  Also valuable when data can not be stored on-site.
    Pro’s: Rapid implementation without having to agree on a common enterprise data model.  Utilize existing source systems.
    Con’s: Deduplication of source systems not addressed.  Data quality must be solved in each independent source system.
  • Hybrid harmonized reference enables compliance and regulatory business drivers. This approach allows the best of both worlds, especially when moving to a transactional operational data store is not politically feasible and data governance and stewardship activities are just starting up.
    Pro’s: Single master copy of reference data.  Uses links to access source system records.  Model allows data quality efforts to be applied to shared master  reference data.
    Con’s: Synchronization with source systems can create some complexity if changes are not made in the hub.
  • Transactional operational data store supports strategic business drivers.  This approach provides a long term path for how legacy applications utilize data.
    Pro’s: Single master copy of data.  No fussing with latency or synchronization issues.  Minimal mapping issues.
    Con’s: Requires an agreed upon common enterprise data model to be used by all applications.  History must be harmonized and requires extensive key mapping.  Assumes homogeneity and requires tons of ETL and dedupe.

Your POV.

Which MDM style are you deploying? What successes have you seen?  Post your thoughts or send me a private email to rwang0@gmail.com.

Which one MDM style are you currently using or considering?

  • Hybrid harmonized reference (44%, 46 Votes)
  • Cross-referenced registry (35%, 36 Votes)
  • Transactional operational data store (21%, 22 Votes)

Total Voters: 104

Loading ... Loading ...

Copyright © 2009 R Wang. All rights reserved.

User Group Event: COLLABORATE 09 – Technology and Applications Forum for the Oracle Community

Title: User Group Event: Oracle Collaborate
Location: Orange County Convention Center, Orlando, FL
Link out: Click here
Description: Survive and Thrive with COLLABORATE 09 — OAUG Forum

Where on earth can you find:

* 1,000+ User-Led Sessions Packed with Best Practices and Case Studies
* 19 Educational Tracks
* 8 Deep Dive Workshops
* Peer-to-Peer Interaction
* Dozens of Networking Events, Geographic and Special Interest Group Meetings
* 150+ Cutting Edge Exhibitors
* Unparalleled Training Value?

Right here at OAUG Forum!
Conference News

* Divide and conquer: groups of four or more save hundreds.
* Don’t get left behind. Justify your COLLABORATE attendance.
* Registration is now open. Register today and save USD $400 with early-bird registration rates.

More About COLLABORATE 09

The Independent Oracle Users Group (IOUG), the Oracle Applications Users Group (OAUG) and Quest International Users Group (Quest) have joined forces to present COLLABORATE, offering in-depth education and exclusive networking opportunities. You benefit through access to a powerful global community of technology and applications professionals and experts and experience a dynamic exchange of ideas and best practices. Learn what works — and what will work best for you. Design your educational experience from hundreds of user-led sessions developed by the OAUG for Oracle E-Business Suite, Oracle Retail, PeopleSoft, Siebel, Oracle Communications, MetaSolv, Hyperion and the rest of the growing family of Oracle Applications.
Start Date: 2009-05-03
End Date: 2009-05-07