Purisma renames and updates

To 'hub' or not to 'hub'


Comment Purisma has just announced version 2.0 of what used to be called the Purisma Customer Registry and has now been re-named the Purisma Data Hub. I can understand why it has dropped the "customer" from its name, as it also supports suppliers, patients, and so forth but I am less happy about the use of the term "hub".

Purisma has opted to use the term "hub" because the Gartner Group classifies master data management solutions into either registries, which are very narrowly defined, or as hubs. Now, Purisma certainly does more than a registry so it is therefore more or less forced to call itself a hub, but I think this is misleading.

The company is certainly not promoting the sort of approach that is characterised by the Oracle Customer Hub, for example. These sort of big hub implementations typically take years to implement, whereas with Purisma you would expect to take weeks or possibly a few months at most.

Now, to be fair to Gartner it does have various sub-categories of hubs, but that doesn't help when you are trying to name your product. In my view there needs to be at least a third category - we call them repositories but it doesn't really matter what you call them - but there has to be something that is more than a registry and less than a hub.

Anyway, enough of nomenclature, what about the new features of the product? Well, I am very pleased to say that Purisma has taken the view that a "single view of the customer" is overly simplistic. Regular readers will know that I have been preaching about this for some time: that traditional approaches to "merge and purge" customer information (that is you merge all the records into a new, composite record and then throw away the old ones) is simply not good enough if you really want to understand your customers - that you need to understand how and when and where they buy. So, what Purisma is now supporting is that you can create a merged master record but keep (if you want to) unpurged original records.

Complementary to this, Purisma has extended its hierarchy capabilities. Put simply, this allows you to organise customer (say) hierarchies so that, for instance, you can understand how one operating division of a customer company relates to another. At the same time you can build your own views against these hierarchies.

So, for example, suppose you sell software. You might have some sales forces that market by geography while others are vertically focused by industry. These two groups would not want to view customer hierarchy information in the same way, so release 2.0 of Purisma allows you to set up such views according to the way you want to see your customers.

Of course, these are not the only new features in release 2.0; there are also new real-time synchronisation capabilities, extended Dun and Bradstreet integration, and support for what the company calls a right-sized data model (that is, you implement what you require initially and then evolve the model as your needs grow). However, for me the main interest is in how Purisma now treats the customers (or suppliers or whatever) in its "hub".

Copyright © 2006, IT-Analysis.com


Other stories you might like

  • GPL legal battle: Vizio told by judge it will have to answer breach-of-contract claims
    Fine-print crucially deemed contractual agreement as well as copyright license in smartTV source-code case

    The Software Freedom Conservancy (SFC) has won a significant legal victory in its ongoing effort to force Vizio to publish the source code of its SmartCast TV software, which is said to contain GPLv2 and LGPLv2.1 copyleft-licensed components.

    SFC sued Vizio, claiming it was in breach of contract by failing to obey the terms of the GPLv2 and LGPLv2.1 licenses that require source code to be made public when certain conditions are met, and sought declaratory relief on behalf of Vizio TV owners. SFC wanted its breach-of-contract arguments to be heard by the Orange County Superior Court in California, though Vizio kicked the matter up to the district court level in central California where it hoped to avoid the contract issue and defend its corner using just federal copyright law.

    On Friday, Federal District Judge Josephine Staton sided with SFC and granted its motion to send its lawsuit back to superior court. To do so, Judge Staton had to decide whether or not the federal Copyright Act preempted the SFC's breach-of-contract allegations; in the end, she decided it didn't.

    Continue reading
  • US brings first-of-its-kind criminal charges of Bitcoin-based sanctions-busting
    Citizen allegedly moved $10m-plus in BTC into banned nation

    US prosecutors have accused an American citizen of illegally funneling more than $10 million in Bitcoin into an economically sanctioned country.

    It's said the resulting criminal charges of sanctions busting through the use of cryptocurrency are the first of their kind to be brought in the US.

    Under the United States' International Emergency Economic Powers Act (IEEA), it is illegal for a citizen or institution within the US to transfer funds, directly or indirectly, to a sanctioned country, such as Iran, Cuba, North Korea, or Russia. If there is evidence the IEEA was willfully violated, a criminal case should follow. If an individual or financial exchange was unwittingly involved in evading sanctions, they may be subject to civil action. 

    Continue reading
  • Meta hires network chip guru from Intel: What does this mean for future silicon?
    Why be a customer when you can develop your own custom semiconductors

    Analysis Here's something that should raise eyebrows in the datacenter world: Facebook parent company Meta has hired a veteran networking chip engineer from Intel to lead silicon design efforts in the internet giant's infrastructure hardware engineering group.

    Jon Dama started as director of silicon in May for Meta's infrastructure hardware group, a role that has him "responsible for several design teams innovating the datacenter for scale," according to his LinkedIn profile. In a blurb, Dama indicated that a team is already in place at Meta, and he hopes to "scale the next several doublings of data processing" with them.

    Though we couldn't confirm it, we think it's likely that Dama is reporting to Alexis Bjorlin, Meta's vice president of infrastructure hardware who previously worked with Dama when she was general manager of Intel's Connectivity group before serving a two-year stint at Broadcom.

    Continue reading

Biting the hand that feeds IT © 1998–2022