You are currently browsing the category archive for the ‘Supply Chain Performance Management (SCPM)’ category.

The blockchain distributed database was invented to create the peer-to-peer digital cash called bitcoin in 2008. Although the future potential of bitcoin and other cryptocurrencies has been debated, the distributed ledger structure using a blockchain database that supports bitcoin is likely to be adopted for a range of commercial and governmental purposes. Distributed ledgers are a secure and transparent way to digitally track the ownership of assets while enabling faster transaction speeds and reducing potential for fraud. How quickly companies, governments and individuals start using distributed ledgers and for what specific purposes remain to be seen, but their use will be independent of cryptocurrencies’ fortunes. Expansion in the use of distributed ledgers will depend heavily on the success of the initial applications and whether there are major hiccups in their use.

To the extent that people have even heard of distributed ledgers, most associate the technology with bitcoin or some sort of payment system. However, it can do more than that. The technology can complement and enhance a variety of enterprise applications, facilitate commercial transactions of all types and provide governments with the ability to streamline interactions with the public.

Here’s a summary of the technologies involved: A distributed ledger is a shared database of assets and their owners located on multiple nodes (sites) on a network. All nodes have an identical copy of the ledger, and any changes to the ledger are incorporated rapidly (at a maximum within minutes; ideally within seconds) in all copies. Distributed ledgers’ distinct value is their ability to securely identify ownership of any form of asset – physical, financial, legal or virtual – and faithfully record all transactions involving these assets. The security of the validity and dependability of the distributed ledger depend on several factors: its blockchain construction, decentralized ownership of identical copies of a ledger, the use of public key encryption of the entries in the database and the use of digital signatures for access control. An important advantage of it lies in moving much of the complexity of managing security onto the structure of the system itself, making such systems easier and less expensive to manage and use than conventional on-premises and cloud-based applications.

Blockchain algorithms enable transactions to be aggregated in blocks that are added sequentially to a chain of existing blocks using a cryptographic signature. A transaction may be, for example, the sale and purchase of an asset or the addition of a health record or a patent filing.

When someone wants to add to the database, each owner of the distributed ledger runs a set of algorithms to evaluate and then verify the proposed transaction. If a consensus (usually a majority of participants) agrees that the transaction looks valid – that is, the identifying information matches the blockchain’s history – then the new transaction will be approved and a new block added to the chain in that ledger. If the participants deciding on the validity of the transactions are preselected, the ledger is said to be “permissioned.” If the process is open to everyone (like bitcoin), the ledger is “unpermissioned.” The advantage of an unpermissioned ledger is that it evades control by authorities. This may be to achieve ethical objectives (for instance, overcoming censorship or theft by autocratic or kleptocratic governments) or for nefarious purposes (money laundering or trade in contraband). Permissioned ledgers can have an advantage if managed by actors (such as self-regulated commercial body or governments) that have the trust of the participants. Permissioned blockchains provide highly verifiable data sets because the consensus process creates a digital signature visible to all parties.

The cryptographic signature using public key encryption can provide individual privacy while validating the identity of the individual making the change. Already in wide use public key encryption enables anyone to encrypt a message using the public key of the receiver, but such a message can be decrypted only with the receiver’s private key. Public key encryption is often compared to a locked mail box with a mail slot. The mail slot is accessible to the public, and its location – the street address – is the public key. Anyone can drop a message through the slot, but only the individual who has the private key can open the mailbox and read the message.

The blockchain structure provides a permanent audit trail since no records can be deleted without collusion on a massive scale. Distributed mirrored databases substantially reduce the ability of anyone to tamper with data since each instance would have to be altered in an identical fashion almost simultaneously. A cryptographic hash function provides a fast and highly efficient means of detecting if a blockchain has been tampered with and for assuring the integrity of transmitted data. That said, distributed ledgers are not invulnerable to attack. Anyone who can find a way to modify one copy legitimately might be able to modify all copies of the ledger. This will happen if systems can be compromised through, for example, phishing or pretexting.

How a given distributed ledger is controlled can vary. Although the ledgers are distributed, there can be varying degrees of centralized control to suit the specific purpose of the ledger. Unpermissioned ledgers (such as bitcoin) are not owned by any individual or entity and anyone can contribute data to the ledger. At the other end of the spectrum, permissioned ledgers may have one or many owners and only they can determine who can add records and verify the contents of the ledger. In practice, the latter can only be considered a distributed ledger (in the definition I’m using) if the number of owners and their independence are sufficient to ensure that the possibility of successful collusion to alter the database is sufficiently low to achieve public confidence. I’ll leave it to others to decide for themselves if a distributed ledger organized and controlled solely by a single organization such as the financial network SWIFT should be regarded as a “true” distributed ledger. By my definition it is. It’s likely that some existing single-entity controlled networks (such as those that manage supply chains) will adopt the distributed ledger structure for all or part of their operations to provide new services or to modify their existing architecture to reduce costs, enhance performance or gain flexibility.

There is no shortage of potential uses of distributed ledgers. There are so many that they – and the underlying blockchain methodology – can appear to be another example of a new technology in search of a mission. Distributed ledgers are not an application but a facility that can support application functions. They can, for example, record the basics of a transaction (such as the details of the item that has been exchanged and the corresponding payment) or serve to signal events (such as accepting a shipment).

Distributed ledgers could serve as a secure platform for all forms of contracts; potentially they could make it easier to enforce contracts of all types in parts of the world where the rule of law is weak because the platform could ban all participants that renege. Distributed ledgers also could be used in settling securities trades of all types – this is more of an evolutionary improvement over today’s systems. In concept, a distributed ledger could cut reconciliation costs by more fully automating the trade settlement process and substantially improving the quality of data, as well as enabling financial institutions to make more efficient use of collateral and regulatory capital by limiting the volume of trades in limbo because they failed to settle.

In commerce, distributed ledgers have the potential to substantially enhance visibility in multitier supply chains and multistep distribution, increase traceability of materials and combat drug counterfeiting. They can provide accurate and immediate customer records or immediately reflect changes to the properties in product life-cycle management and product information management. Networks for connecting members of a value chain have been difficult to establish because typically they have been set up by one of the major players. Competitors of that major player cannot (will not) participate in that network, blunting its effectiveness and leading to network fragmentation. Distributed ledgers might be less prone to this defect because they provide a secure, auditable mechanism for data capture and exchange that can complement but not replace the functionality of a value-added network. Companies therefore would be able to operate on different value-added networks that all use the same transaction data.

In the public sector there are many ways in which governments can use distributed ledgers including property record-keeping, healthcare data, a digital notary system, recording government contracts and handling tax and other payments.

Despite these potential uses it’s not clear how quickly distributed ledgers will gain traction and profitability in the commercial realm. In developed economies, there already are many trusted networks and methods for transacting business governed by commercial codes. Ultimately they may adopt a distributed ledger structure because it’s superior to the technology they are currently using in terms of speed and robustness. Some observers estimate that banks collectively could save billions of dollars in IT infrastructure costs by employing them for payments across borders, securities trading and regulatory compliance. Beyond savings, the desire to improve service or the threat of competition from an upstart will drive the process. There are many opportunities to create permissionless networks in less developed economies, but it may be difficult to make them more than marginally profitable initially until some combination is achieved of their networks becoming large enough and their costs getting small enough.

Much work still needs to be done to make distributed ledgers a reality. One serious issue for distributed ledgers is the large amounts of computing (and electrical) power required to make them work. Another issue to be addressed is auditing. Accountants will need to be able to audit records on permissioned ledgers. Then, too, there is the matter of governance structures. This is less of an issue in largely free-market jurisdictions with solid rules of law. Rules established by the owners and participants of a ledger that safeguard their private interests must be supported by legislation and regulation consistent with existing commercial codes. In turn legislation and regulation must balance public and private interests without being so rigid as to stifle innovation and growth.

For the time being, it’s not clear that distributed ledgers will displace trusted networks such as those offered by ERP vendors because it won’t have the functionality and process control that are part of those products. Those running trusted networks probably will not be in a hurry to open up their management to others since all have some value associated with being in charge. And the security issues that SWIFT has encountered (hackers managed to steal $US 81 million from Bangladesh’s central bank) would not have been prevented through the use of blockchain. It’s likely that there are scores of opportunities to create blockchain networks that are economically workable, but it’s not clear how soon these will become economically significant.

I’ll leave it to others to comment on the future of cryptocurrencies. I’m fairly certain that their impact on the adoption of blockchain technology is neutral. All the attention that bitcoin and others have showered on blockchain is fully offset by entities that hold a negative view on cryptocurrencies because of their association with illegal commerce and theft. Nevertheless it is likely to have an impact someday, and software executives and information technology service providers would be well-advised to familiarize themselves with the technology and its potential.


Robert Kugel

Senior Vice President Research

Follow Me on Twitter and

Connect with me on LinkedIn.

There were two noteworthy themes in SAP CEO Bill McDermott’s keynote at this year’s Sapphire conference. One was customer assurance; that is, placing greater emphasis on making the implementation of even complex business software more predictable and less of an effort. This theme reflects the maturing of the enterprise applications business as it transitions from producing highly customized software to providing configurable, off-the-rack purchases. Implementing ERP will never be simple, as I have noted, but as companies increasingly adopt multitenant software as a service (SaaS), vendors will need to make their implementations as repeatable as possible and enable flexible configuration of parameters and processes that substantially reduce the billable hours required to complete a deployment. “Customer assurance” is an important stake in the ground, but it will be an empty concept unless there is complete overhaul of the entire value chain to take it beyond good intentions. Otherwise, customer assurance will be an ongoing rearguard action to overcome technology-driven challenges and disincentives for improvement. Business applications must be re-engineered to facilitate implementation, substantially reduce the likelihood of implementation errors and facilitate subsequent changes to adapt to changing business conditions. Moreover, software vendors’ partners will need to demonstrate that they can reliably cut a substantial number of billable hours per implementation engagement. This will require partners to restructure their business models. Neither of these changes will be easy to accomplish. To its credit SAP has set a course for increasing the simplicity of using its core ERP and financial management software. Getting there soon would greatly enhance its ability to retain if not gain customers in these mature markets.

McDermott’s second notable touch point was the “digital boardroom,” a wall-size set of monitors displaying a broad array of current company data (including some in real time) in easy-to-understand visualizations and in vr_Office_of_Finance_06_information_isnt_timely_enoughalphanumeric format. The digital boardroom demonstration contained not just the standard set of drill-down and drill-around capabilities but also the ability to work interactively with data to do what-if scenario planning and analysis. While some might view it as only eye candy, the immediacy of the data and the ability explore potential outcomes based on different conditions or actions would represent a substantial breakthrough in the use of data and analytics by senior executives.

The idea behind the digital boardroom is sound: Boards of directors, executives and management need up-to-date information to help them understand the current state of the business, its opportunities and challenges. However, in our benchmark research on the Office of Finance fewer than one-third of companies said that the information they receive is timely. In the past, somewhat timely information might have been the best one could expect but no longer. Analyses and plans based on out-of-date information may not be actionable. However, the business value of the digital boardroom will be an empty promise unless companies address the root causes of the timeliness issue. They include scattered information, a heavy dependence on desktop spreadsheets for aggregating and analyzing data, and limited penetration of advanced analytics. Our research also shows that fewer than half of finance departments use relatively straightforward analytic techniques such as product and customer profitability, only 22 percent employ economic and market data and trends in their analysis, and just 12 percent use predictive analytics. SAP’s existing and planned software can help address these shortcomings, but it cannot overcome the data management issues that prevent companies from having timely information or the lack of analytical skills and training that also hamper a company’s ability to present incisive, action-oriented analyses and prescriptive models in a digital boardroom.

One of SAP’s objectives in demonstrating the digital boardroom is to make senior executives aware of what’s possible. Ideally this would be a potent source of “demand pull” – directives from the top to enhance a company’s systems and modeling capabilities by addressing data, training, process and systems requirements. SAP’s enterprise software generally and its Universal Journal in particular can begin to address the technology and vr_NG_Finance_Analytics_09_too_much_time_to_prepare_datasome of the data issues. But experience makes me reluctant to assume the best. It seems likely that for the time being the numbers and analyses that wind up being displayed in a digital boardroom will be created using the same crude, time-consuming methods. Our next-generation finance analytics research finds that two-thirds (68%) of individuals spend the greatest amount of their time on data-related tasks in preparing for analysis while only 28 percent are able to focus on the analysis itself. One can hope that data environments will improve and that users will switch to dedicated analytic software from desktop spreadsheets, but applications vendors should focus on adapting to shoddy IT environments rather than hoping that customers will change their behavior. SAP also will need to ensure that the full range of its analytics and business intelligence software is readily integrated with the digital boardroom. Doing this must include its newly acquired technology from Roambi, which provides mobile support for smartphones and tablets.

The ERP and financial management software categories are currently in a process of transformation, as I have written, one that will be as sweeping as the shift to client/server applications in the 1990s. The trend to cloud-based multitenant architectures gets the most attention, but real-time information availability, a more productive and pleasant user experience, improved in-context collaboration and a lower total lifetime cost of ownership will be key factors in determining winners and losers. Aware that they are vulnerable to disruption, established vendors – including SAP – have been adapting. Statements of direction are useful for communicating with customers and the market generally. However, SAP needs to accelerate its pace of development to arrive at the transformed state it promises if it is to remain competitive.


Robert Kugel

Senior Vice President Research

Twitter Updates


  • 121,108 hits

Get every new post delivered to your Inbox.

Join 75 other followers

%d bloggers like this: