Semantic Arts exists to shepherd organizations on their Data-Centric journey.
Our core capabilities include:
• Semantic Knowledge Graph Development and Implementation
• Legacy Avoidance, Erosion, and Replacement
We can help your organization to fix the tangled mess of information in your enterprise systems while discovering ways to dissolve data silos and reduce integration debt.
What is Data-Centric?
Data-Centric is about reversing the priority of data and applications.
Right now, applications rule. Applications own “their” data (it’s really your data, but good luck with that). When you have 1,000 applications (which most large firms do) you have 1,000 incompatible data silos. This serves to further the entrenchment of legacy systems, with no real motivation for change.
Data-Centric says data and their models come first. Applications conform to the data, not the other way around. Almost everyone is surprised at the fundamental simplicity, once it’s been articulated.
It sounds simple, but fifty years of “application-centricity” is a hard habit to break. We specialize in helping firms make this transition. We recognize that in addition to new technology and design skills, a major part of most projects is helping shepherd the social change that this involves.
If you’re fed up with application-centricity and the IT-fad-of-the-month club, contact us.
Read More: What is Data-Centric?
What about those legacy systems?
The move to a more data-centric architecture requires thoughtful planning. Early phases look more like a surgical process of dealing with legacy applications in a way that realizes quick wins and begins to reduce costs, helping to fund future phases. Usually, it looks something like this:
-
Legacy avoidance: The recognition that a firm has slowed down or stopped launching new application systems projects, and instead relies on the data that is in the shared knowledge graph.
-
Legacy erosion: Occurs when firms take use cases that were being performed in a legacy system and instead implement them directly on the graph. Rather than wholesale legacy elimination (which is hard), this approach allows the functionality of the legacy system to be gradually decommissioned.
-
Legacy replacement: Once enough of the data, functionality, and especially integration points have been shifted to the graph, legacy systems can be replaced. Not with “legacy modernization” systems, but with lightweight standalone use cases on the graph.
Read more: Incremental Stealth Legacy Modernization
ABOUT US
THOUGHT LEADERSHIP
PROBLEMS WE SOLVE
Taking a different path STARTS NOW. Become Data-Centric to simplify and enhance your enterprise information landscape:
5 Business Reasons for Implementing a Knowledge Graph Solution
1. Comprehensive data integration
2. Contextualized knowledge discovery
3. Agile knowledge sharing and collaboration
4. Intelligent search and recommendation
5. Future-proof data strategy
Integrating semantic capabilities into enterprise business processes has been the foundational shift that organizations such as Google, Amazon, and countless others have leveraged. The results are tangible: increased market share and revenue, lower costs, better customer experiences, reduced risks, and the promotion of innovation.
Semantic Arts’ professional services deliver true solutions (not gimmicks) for current and future information management challenges.
FROM OUR BLOG
Strategy and Your Stronger Hand
Those of us in the complex sale sector need to be aware that volume operations from adjacent marketplaces will soon enter ours. The December 2005 issue of the Harvard Business Review has excellent articles by two of my favorite business authors, Geoffrey Moore (“Strategy and Your Stronger Hand“) and Clayton Christiansen (“Marketing Malpractice: The Cause and the...Continue reading→
The Zachman Framework
Shortly after you start your inquiry about software architecture, or enterprise architecture as it is often called, you will come across the Zachman Framework. The Zachman Framework is a product of John Zachman who has been championing this cause for at least 15 years, first with IBM and then on his own. As with so...Continue reading→
Architecture and Planning
“Action without planning is folly but planning without action is futile.” In this write-up, we explore the intimate connection between architecture and planning. At first blush, they seem to be completely separate disciplines. On closer examination, they appear to be two sides of the same coin. But in the final examination, we find that they...Continue reading→
Response Time Quanta
How do we perceive software response time? (I’m indebted to another author for this insight, but unfortunately I cannot credit him or her because I’ve lost the reference and can’t find it either in my pile of papers I call an office, nor on the Internet. So, if anyone is aware whose insight this was,...Continue reading→
Time Zones
Reflections on low-level ontology primitives. We had a workshop last week on gist (our minimalist upper ontology). As part of the aftermath, I decided to get a bit more rigorous about some of the lowest level primitives. One of the basic ideas about gist is that you may not be able to express every distinction you might...Continue reading→
Semantisize
Semantic technology resources I was alerted to this site: www.semantisize.com from a comment. It’s pretty cool. You can while away a lot of time on this site which is rounding up lots of podcasts, videos, etc., all related to Semantic Technology. I got a kick out of a video of Eric Schmidt taking a question from the...Continue reading→
Part 6: Definitions are even more important than terms are
In recent posts, we stated that while terms are less important than concepts, and they mean nothing from a formal semantics perspective, they are very important for socializing the ontology. The same is true for text definitions, but even more so. Just like terms, the text definitions and any other comments have zero impact on the inferences...Continue reading→
Part 2: Don’t let terms get in the way!
It frequently happens that a group of experts use a term so differently that they just cannot agree on a single meaning or definition. This problem arises in spades in the area of ‘risk’. For example, in traditional operational risk management (ORM), when you measure risk, you multiply the probability of a loss times the...Continue reading→
Application Scope: A Fractal View
The scope of an application is one of those topics that seems to be quite important and yet frustratingly slippery. There are several very good reasons for its seeming importance. One, the scope of an application eventually determines its size and, therefore, the cost to develop and/or implement it. It’s also important in that it...Continue reading→
Part 5: Good terms are important for socializing the ontology
In my previous post, I explained why, when building an enterprise ontology, it is a good idea to focus on concepts first and to decide on terms later. Today, we will discuss what to do when ‘later’ arrives. But first, if terms don’t matter from a logic perspective, why do we care about them? In short,...Continue reading→
gist: 12.x
gist: is our minimalist upper ontology. It is designed to have the maximum coverage of typical business ontology concepts with the fewest number of primitives and the least amount of ambiguity. Our gist: ontology is free (as in free speech and free beer–it is covered under the Creative Commons 3.0 attribution share-alike license). You can use as you see fit for any purpose, just give us attribution.
Semantic Arts Plays Well With Others
Click on an icon for a synopsis of our work with these firms.
