-->

NEW EVENT: KM & AI Summit 2025, March 17 - 19 in beautiful Scottsdale, Arizona. Register Now! 

Making smarter connections with knowledge graphs

Article Featured Image

The selection of AllegroGraph was based on two major factors. “The most important factor was the maturity of AllegroGraph for production deployment,” commented Yuson. “Our first production application was deployed just 9 months after engaging the company.” The second factor was the reputation Franz had for providing customer support. “We received excellent consulting help and technical support throughout our development process and after deployment,” he added.

Now that the fulfillment system is in place, Essilor can manage the supply and delivery of each product efficiently. “We have full visibility into our supply chain,” continued Yuson, “and we can understand the impact before a fabrication lab goes down for maintenance, greatly minimizing the risk of order disruption. Timely delivery and order impact predictability risks have been significantly ameliorated with the deployment of our supply chain fulfillment system.”

Essilor is considering other applications for AllegroGraph, including using it to support the company’s pricing system. “Every region has great flexibility in special pricing and promotion,” Yuson explained. “The current pricing system, which is based on relational tables, is very cumbersome to update and change. With Franz’s semantic knowledge graph approach, the pricing system would be much simpler to use, more adaptive to changes, and easier to administer.” 

Also on the road map are several projects using AI and machine learning to predict equipment breakdowns, optimize maintenance periods, and improve efficiencies at the fabrication lab. “The idea is to correct any problem before it causes a breakdown that could cause serious supply chain issues,” Yuson concluded.

Graph databases are used to present aggregated data in call centers and to integrate information from hospital systems to make analytics easier. “In many call centers, agents have to open multiple screens to resolve customer issues,” said Jans Aasman, CEO of Franz, Inc., “and they are often able to solve only 60% of the problems the first time, which presents an expensive challenge.” Relational databases generally do not work well because they don’t provide a comprehensive connection with all the data related to a client.

When a knowledge graph is used, the outbound target becomes the core entity of the knowledge graph, and every action is an event object, such as an outbound call or text interaction. “The data is streaming from different databases and is connected in the knowledge graph for processing to provide a 360-degree view of that target for a streamlined sales process,” said Aasman. “This provides sales agents with all the background knowledge about a customer along with competitive information on a single screen and delivered in real-time—an ideal knowledge-driven sales tool.”

For companies that want to get started with graph databases, the advice Aasman offers is to aim first for the low-hanging fruit. “Pick a high-value project that is supported by data and one for which developing an ontology is feasible,” he advised. Finally, extract data from multiple sources and put it into a knowledge graph so people can get an overview that would not otherwise be available through traditional database architecture in order to demonstrate the value of graph databases.

Data fabric is the next level of maturity for data integration, according to Aasman, and it can make very effective use of knowledge graph technology. “This architecture provides a systematic approach to search a variety of databases for relevant information,” he observed. “It can document every table, column, and description of data; what business line owns the database; and who is responsible for it, as well as what applications are affected if it goes down.”

Data fabric built from knowledge graphs

As an emerging concept, data fabric is not yet part of the mainstream. “It is important to understand that data fabric is not a platform, tool, or technology,” said Ehtisham Zaidi, senior director analyst at Gartner. “It is a data design concept, which needs a collection of composable capabilities that is provided by several data management tools and best practices to deliver and combine data, often through automation techniques, via active metadata, AI, and machine learning.” When data sources are heterogeneous and inte gration is complex, a design pattern is needed that allows integration and delivery that is both automated and agile, which data fabric offers.

“The promise of data fabric is dependent on an organization’s ability to incorporate knowledge graphs into their data architecture,” he continued. “That in turn depends on ontologies that reflect a good understanding of an organization’s information, processes, and the connections among entities.” The first step is to collect and integrate as much metadata as possible, and it should not be restricted to technical metadata; it should include business and social metadata as well as performance metadata elements such as frequency of access.

A limiting factor in the growth of data fabric is the absence of metadata stan- dards, according to Zaidi. One of the few such standards is Egeria, an open meta-data exchange standard that provides linking and exchange of data among heterogeneous repositories and tools so that users of different tools can collaborate and share data. Another factor is expertise. “It is difficult to gather enough experienced data engineers with the right skills to translate requirements of uses case into architecture,” Zaidi added. However, with the ongoing increase in volume and diversity of data and only 2%–5% of the companies that could benefit from the data fabric having utilized it so far, solutions to these issues are likely to evolve.

KMWorld Covers
Free
for qualified subscribers
Subscribe Now Current Issue Past Issues