“We looked at the areas of technical and commercial risk within data access projects, and created a combination of product features and commercial policies that, as far as is possible, mitigate this risk.”
Ontology website.
The diagram link above shows the five principles put forward by an organisation named Ontology. It just so happens that it aligns with concepts I’ve discussed in earlier posts, such as the “no more data synch” entry.
I believe that the approach they outline on the Ontology link above certainly has merits, particularly as data sets get larger as well as integrations and data integrity becoming more difficult to manage. It’s well worth a read.
Please note that I have never had any contact with Ontology, nor involvement or experience with them, so I can’t vouch for their products or services in any way. A friend and colleague simply passed on their URL [thanks Evan!], having read some of my earlier postings and thought other readers might benefit from the Ontology insights too.
Over the years, I’ve often referred to The Corkscrew Analogy or Momentum Spiral to describe a mindset of incremental improvement that’s needed to keep an
We’ve embarked on a journey of trying to plan for the future of OSS/BSS, not by predicting the future, but by seeking ways to be
As discussed in the previous article, “Future Scenario Planning: Have you given up on doing an OSS transformation? (part 1)” part of the fun of
Earlier in the week, a friend mentioned he was reading “Alchemy” by Rory Sutherland. It’s not an OSS book per se, but does provide some
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
