The Truth, the whole Truth, and Nothing But the Truth

PDFPrintE-mail

Almost everyone has had some experience during which two or more people have been working on the same task at the same time.  In such cases, it is often hard to determine who has the “master copy” of the project, and changes made by one individual can easily get lost or overwritten by changes made by someone else working on the same thing.  If, for example, you and I are both given the same spreadsheet and told to perform some analysis and report on the results, it would be very difficult to combine both of our changes and different calculations after the fact to create a single report, and we would likely come up with different conclusions.  Now imagine that we are not working with a spreadsheet, but with millions of pieces of data across an enterprise, and there are not only you and I, but hundreds of other individuals and systems manipulating the data, all at the same time.   Because situations like this happen every day within large organizations, it is of utmost importance to establish a comprehensive trusted source of data in order to maintain systems that are complete, consistent, and correct. An organization will have established a trusted source of “master” data across the enterprise when its information systems provide a single version of every item of shared data that is consistent with the rest of the data in the system – and when everyone who needs a data item knows where to go to find that authoritative version.  While establishing such a trusted source is extremely important, there are obstacles and challenges that threaten the trusted source in numerous ways:
  • A user may be confronted with conflicting information from different sources and not offered any help in interpreting or resolving the differences.  Worse, the user may happen on one version of the data, never suspect that different (and perhaps truer) versions exist, and make decisions based on inaccurate information.
  • The information obtained by a user is often incomplete, because the missing information is stored in a system that is “too many clicks away” from the portal through which the user is accessing the data.
  • There is a lot of redundant data entry.
  • Sources sending information into the enterprise database often have conflicts.
  • Attempts to achieve a single trusted source by multi-directional synchronization of independent databases (containing, for example, order and return information) present the danger that timing problems may cause valid data to be overwritten by invalid data.
Even if a database contains a single definitive copy of all the data, those data are of no use unless the user application’s interface and other user aids enable people to find the information they need, when and where they need it.  The master database needs accurate, legible, documented, understandable, and up-to-date models to support the development of user interfaces and aids that make this data available to its users. Finally, once a user has obtained the one true version of some piece of data, one more thing has to happen to turn the data into valid and valuable information:  The user must accurately understand what it means.  Standardizing procedures and processes across the enterprise can help an organization to ensure that users understand the data:
  • Standard codings, terminology, and classifications for crucial shared entities (accounts, projects, etc.) need to be developed, adopted and put into common use.
  • Time-tagging data items can prove useful in informing users how up-to-date they are.
  • Educating new users of an application (and educating current users of a changing application) on the meaning and timeliness of the information they will be obtaining through that application is an essential component of maintaining the integrity of the database and the enterprise.

Finding the single source of truth

With the proliferation of silos and channels comes the problem of knowing whose version of the “truth” is correct: where did it originate, and how trustworthy is it? The first part of any information management effort should be to ascertain the owner and original source of each type of data in an information flow. Only this “single source of truth” should be accessed for that data by all the other organizations in the system. It is also important to pay attention to the management of metadata and master data to improve transparency into the lineage and quality of data.  Organizations need to consolidate systems that provide data for similar business processes, identifying and resolving duplicate data and incomplete data, so that data is entered and updated consistently in one place...the single source of truth.

Add comment


Security code
Refresh

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

May Puzzle

David is often referred to as Rainman due to his peculiar ability to effortlessly figure out a certain date's day of the week. He recently displayed this talent when I asked him if there was a conflict with the upcoming Fuzzy Dice Conference and our weekly court-ordered community service. He asked the date of the convention. It was April 20th, 2012.

"Oh, that’s a Friday," he said, effortlessly. "And your sentences have you committed for the next few dozen Wednesdays so you'll be able to go." And of course he was right.

One day a few weeks ago I asked out loud in the office about the date June 5th. And of all people, my brother Tommy piped up and said "Oh, that's a Tuesday."

"That's right," said David.

Well how about Otcober 3rd?

"That's a Wednesday," said Tommy. Then I asked about Christmas Day 2012.

"Oh, that's a Tuesday." David nodded in agreement.

Do we now have two rainmen? Or had Tommy figured something out?

Show solution...

Solution

Here's what was going on. Tommy was using something called anchor dates. And these dates apply to each and every year. April 4th, or 4/4 we’ll call it from now on, June 6th or 6/6, 8/8, 10/10, 12/12, are all the same day of the week, each and every year.

So too are 5/9 and 9/5, May 9th and September 5th. So too are 7/11 and 11/7, and all the above dates are the same day of the week, as is the last day in February, Leap Year or not. And they’re all the same day as January 4th, it would otherwise be January 3rd, but this was a leap year, and that’s changes the anchor day from January 3rd to January 4th.

Tommy also knew that New Year's Day was a Sunday. He was sobered up by then. And he knew it was a Sunday because Christmas was a Sunday in 2011, so New Year's Day is a Sunday, so the Anchor Day for 2012, January 4th, has to be a Wednesday!

So if that's a Wednesday, then 4/4, 6/6, 8/8, 10/10, 12/12, 5/9, 9/5, 7/11, 11/7, and February 29th are all the same day of the week, and they're all Wednesdays. So when I ask for example, about October 3rd, he knew October 10th was a Wednesday, 10/10. So 10/3 must also be a Wednesday. 12/12 is a Wednesday in 2012, so it’s 12/26, which is two weeks later. So 12/25, or Christmas Day, must be a Tuesday.

Success Tips for Oracle Project Management

  • Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
  • Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
  • If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
  • Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
  • Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
  • Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
  • Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
  • Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
  • Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
  • Include governance, risk, and compliance management as part of the project plan.
  • Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.

The Analyst Corner

John Van Decker, Research VP of Gartner, states:

"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."