Public Sector Data Vault

public sector data vault

the data vault has many uses in the public sector, ranging from homeland security to email capture, to dynamic data integration and unlimited scalability. the data vault is currently deployed in several public sector ventures, and is highly successful.

the following topics are covered on this site:

  • beyond standard data warehousing
  • the needs of the government
  • dynamic structure integration
  • massive volumes in near real time
  • data mining relevancy ratings
  • classified information stores
  • benefits to the public sector
  • sei / cmm and compliance
  • learning models, nanotechnology

beyond standard data warehousing
in the government, there are needs which extend way beyond standard data warehousing. there are also more stringent requirements to be met, audits to pass, and classified information to hold. the standard data models (3rd normal form and star schema) don’t always meet these needs. the gif (government information factory) is created as a framework, and provides guiding principles that help architecture experts begin to meet those needs. the data vault is an architecture that provides the integration “how-to” standards which are capable of nailing those needs in place.

as practitioners, we must begin to stretch our boundaries and build models, and content which allow flexible, scalable information stores. limits must be eliminated, pending any hardware limitations that are artificially imposed and will be overcome with time. thinking beyond standard data warehousing includes dynamic re-structuring of the content, unlimited scalability, application of data mining to both content and context.

the needs of the government
the government (public sector) has many needs. one of these needs is to have data integration stores that are stored separately, and only integrated during the analysis phase. another is to integrate massive amounts of information quickly from all over the world. other needs include unlimited scalability without heavy change impacts, keeping parts of data classified while reusing existing data models and leveraging unclassified domain information.

the government, due to privacy regulations, cannot conglomerate the data into a single information store. they are only allowed to analyze the information across information stores, and produce the integrated analysis, particularly in the case of air-port screening crossed with bank records and email traffic.

the data vault architecture allows separation of physical data, and integration of the information at analysis time.

“the government needs to connect relevant information systems so it can analyze data, share information, and ultimately predict and prevent future attacks.” (

a dynamic data modeling architecture is needed behind the scenes to support flexibility, change, and discovery. the data vault provides for data mining of the structure and content together, to impute context and connections that previously, did not exist. therefore the data vault paired with data mining operations can help discover unknown relationships across data.

there are many more needs that the government and any federal or international agency has. however, in the interest of time we’ve listed only a few more below: security mandates for separate physical information stores, brought together only during the analysis phase.
single keyed information for faster access, and consistent integration.
provide automated monitoring, and self-managing systems.
achieve current administration goals quickly, and efficiently without “losing” or altering existing information structure and services.

reduction/elimination of duplicate data stores.
dynamic information structures to meet ever-changing business dynamics.
do more with less, allow smaller teams to handle bigger projects with ease.
reuse and extend non-classified data and data model in a classified world.

dynamic structure integration
if it were discovered that rental car reservations were important, it would be easy to add the elements to store historical data, and then build the link to the other information in the discovery linkage. if it were discovered that phone calls had a relevance to emails, or maybe the decision is to find out if there’s relevancy to emails – the addition of a second discovery linkage and a phone call history element is easy to do without disturbing the rest of the information. the modeling technique capable of dynamic addition of information without losing history. the architecture allows addition of information at any time, and the linking of the information to be tested for relevancy – if the information linked is not relevant (or no particular significance is discovered) the link can be dissolved without losing history of the information.

additional questions to ask:

  • what if links can establish correlations between disparate data in near-real time?
  • what if each component can discover meaningful associations with other components in near-real time?
  • what if you can weigh, measure, and produce a visual colored graph of important or “hot” linkages between information in near real time?

disparate data sources such as bank-records, cia systems, fbi systems, emails, and ins systems can be integrated rapidly and easily. for instance, linking emails to bank transactions, and airline ticket purchases becomes a much easier task (compared to previous methods). the architecture provides an unprecedented information linking (integration) capability. the flexibility of the design/architecture of the data vault is limitless. because of the link mechanism, granularity of “joining” information together no longer is of consequence. the information is joined because it makes sense to the business, not because the technology says it can be.

having the linkages allows dynamic integration of disparate data. applying ai to the link can then discover if the link needs to be dissolved (lack of relevancy), or if a new link needs to be built between contextual elements because one doesn’t exist today and the information makes sense. from a pattern perspective, ai can discover new relationships and essentially evolve the data storage structures over time, learning which relationships make sense and which ones don’t.
ultimately the data model begins to be morphed into what is relevant or critical to the business, be it intelligence, security, or commercial.

massive volumes in near real time
each set of elements is independent of the others. this allows the frequency of loading to vary without impact across the warehouse. it also isolates the growth patterns to the necessary data. the discovery linkage is run from a data mining process which learns over time – and only picks up the altered or new information. the structures in each area are part of what makes the architecture extremely powerful. the dynamic linking of the nodes make the information flexible, and scalable. the architecture is built for enterprise data warehousing, and is capable of storing massive volumes of information over time. **the white papers explain how this works.

the data vault structures are designed to allow near real time feeds of information. they are also capable of storing massive sets of information over time in the most efficient storage possible without utilizing compression techniques. for instance, suppose there is a need to capture emails in nrt, and bank transactions once every hour. the structural integrity does not break down under volume loads, nor does the integration of this information. the structural design allows the feeds to be set up as fault-tolerant, fully restartable processes.

data mining relevancy ratings
data mining is extremely important, particularly to discover relationships among vast amounts of information. using the data vault, a mining model can be built for the structural relevancy as well as the data inter-relationships. in other words, new cross-links can be “discovered” through data mining based on content of the surrounding information hubs. if data is seen to have a strong correlation, the mining tool may suggest new link structures to span the information hubs. the mining model results can also score the new relationship to assist in the interpretation of confidence levels that the relationship actually exists.

this can evolve the data model over time into a more effective and useful integration model, thus arriving at dynamic data integration, where not only the data changes, but the structure changes too. this can be monitored and guided (like a neural network), by manually approving the model changes, and/or changing the confidence level rankings that are stored within the model itself.

there is a need to discover relationships across information (utilizing data mining), and once discovered, judge the relevancy of the relationship. if the relevancy of the relationship meets a certain threshold, dynamically establish the relationship or integrate the data on-the fly. the data vault provides this capability of dynamic structure adaptation. for instance, the results of data mining show an 80% relevancy between occurrences of rental cars/trucks and the purchases of chemical items within the recent days by a suspected terrorist. a relationship across this data will need to be dynamically constructed, and analyzed to determine impact.

questions that can be asked when dynamic data structures can be built:

  • what if relevancy can be viewed graphically across thousands of relationships?
  • what if items that weren’t relevant to certain relationships could be dropped after interrogation?
  • what if outlier activity appears in a discovery link across an extremely important relationship?

the functions can determine these items based on data vault relationships, and produce graphical or visual images which allow visual scanning of thousands of components of information rapidly. massive volumes and high levels of integration can provide a data mining engine a goldmine of information. sampling of the information isn’t good enough to find the outliers that one might be looking for – it may be the outliers (the unusual occurrences) that are interesting to the government. pieces of information that are out of the ordinary. the data vault structures are architected to assist data mining tools to do their work in the database. with massive volumes, it doesn’t make sense to extract the information out of the database – often there isn’t enough time to extract information simply to mine it.

applying a combination of data mining and artificial intelligence algorithms, relationships can not only be discovered and built, but can then be weighed, measured and applied with a relevancy factor. weak relationships can be noted, stored, or destroyed. strong relationships can provide a cluster-building foundation. strong relevancy between contextual data can be watched closely for outliers. when the outliers hit (actions causing strange results), they can immediately be flagged for further examination. this architecture supports parallelism all the way to the data structure level.

is this a concept of object oriented databases repackaged? i don’t believe so. these elements are independent of each other and carry context. each could be construed as a base-level object with zero inheritance – that is one possible application, however the dynamic relationships are objects themselves that facilitate run-time reconfiguration of the data storage trees. it is not known if this effect is achievable through object-oriented design. this design does not employ the concerns and benefits of inheritance or polymorphism.

information does not need to be evaluated for importance before being put into the data vault. the human “judgment” about what is relevant and the “politics” about which agency provides it (cia or fbi) is now a thing of the past. the information is simply entered regardless of what it is and the data vault structural mining operation makes the relevant connections through the process of data mining and discovery.

classified and protected information stores
many organizations require classified information, sometimes even the private or commercial sector likes to protect data, specifically financial data. in the case of classified data, it is absolutely vital to re-use the data model and the information that is unclassified; replicating it to the classified world, and have the flexibility of adding only those components that are desired without impacting existing structure, or information (content).

in the case below, the tables and areas in red show the components which were added to the classified model with zero impact to the existing structures, and zero impact to the existing data or content.

the first step is to make a copy of the unclassified data model, and build it behind closed doors. the second step is to build a one way data copy, which pushes unclassified information directly to the classified staging area, the classified staging area then engages “import” routines that pull the data onto the classified machine. from here, the cleared data modelers and business users can make additions and changes to the data model safely. they can extend the model into the classified world and add all of the information that is deemed necessary without “replicating” development work, and without altering original unclassified structures.

the structure of the data vault allows updates to be made to the unclassified data model and information set, and provides the ability to roll those into the classified world; quickly, easily, and without disturbing any of the content that has been built. absorption of changes and upgrades is near 100%, with near 1% impact.

benefits to the public sector
there are many benefits to the public sector, some of them have been covered above. others include reduced cost of maintenance, reduced time to implement, standard and repeatable data architecture, elimination and reduction of redundancy (exception: classified world), increased worker productivity, better mapping of the business.

  • provide automated monitoring, and self-managing systems.
  • achieve current administration goals quickly, and efficiently without “losing” or altering existing information structure and services.
  • reduction/elimination of duplicate data stores.
  • dynamic information structures to meet ever-changing business dynamics.
  • do more with less, allow smaller teams to handle bigger projects with ease.
  • ability to load hundreds of thousands of transactions rapidly per second into the warehouse.
  • dynamically extendable, adaptable to structure changes.
  • binding function to form. utilizing data mining – patterns can be discovered, weighed and measured for applicability to the goal.
  • capable of structure changes without loss of information.
  • capable of dynamic/automated expansion and extension with new data sources.

the data vault architecture makes it easier to create systems that have 999999 uptime. because it’s based on semantic business keys, it is easy to add and delete “areas” of business without losing data in other areas. the linkages make it possible to change the data model and the grain of the information quickly and easily with very little downstream impact.

when data mining is used on the content, it can “create” new linkage structures on the fly, connecting information that previously was unconnected. thus modifying the model dynamically. it can also weigh the certainty of the connection that it created, and report these findings to the users.

monitor and watch for “hot-spots” in data in near real time?
for example: would you be interested in dynamically discovering a large cash deposit, followed by several specific emails from a known/suspected terrorist, followed by purchase of airline tickets?

the benefits are many, contact us today to find out more about the data vault 2.0