Omega Naught Database

Omega NaughtWe have developed a revolutionary type of information management system and underlying database called Omega Naught (Omega 0). It is built from modules by the users themselves without programmers. It is this key use of core information modules, joined automatically into a network, that makes this possible.

FreeForm

FreeForm is the application interface for Omega 0. Try out the free online demo and see how easy it is to create your own database.

Driving Forces

The developmet of this new type of information system was motivated by the following key needs: 

  • We often need very rapid development using only domain experts – the agency or company users.  For example, in crisis management a new type of disease might emerge and we need a totally new information system to track the symptoms, correlating factors, and pharmaceuticals. Such a system might need to be built within a few hours (not a year of planning, design, committees, testing, and deployment). Furthermore, the system must allow for rapid evolution and change in the number and design of tables and fields to be captured.
  • We often need very rapid data entry for data centers, crisis management operations, and law enforcement. We need a system where data can be entered with short keywords of 2 or 3 letters followed by the value.  Since the data arrives usually in random order, the data entry must allow for random data entry order.  Furthermore, the data should be entered without the need for a data form and pointing device (such as a mouse where one must seek out the place to enter the data on the form thus moving ones hands away from the keyboard). 

Features

This system allows the user to

  • quickly develop a new system using a default template of modules,
  • to change the modules by adding fields and tables as needed,
  • and enter data at exceptionally high rates (as for a dispatch or call center).

The system can automatically output both valid XML data files of all data as well as a fully developed relational database, thus making the connection with well established and foundational database systems. 

The consequences of this development can be revolutionary because for the first time those persons in a company or agency that have the domain expertise for their job will be able to develop, modify, and manage critical information without translating their needs to computer programmers with associated cost and development time. The Omega Naught system works like people think and process data.

Omega Naught Differences

Anyone experienced in database and information technology will immediately wonder what one gives up with this system since one is aware of four primary areas that require extensive information technology training and programming: (1) the complex design of relational database joins and indexes as based upon the table structure; (2) the area of data edit checks and business logic (such as valid dates and numeric only social security numbers etc); (3) the problem of input table design and structure, and finally (4) the complex task of report and analysis construction. 

The answers to these questions are as follows for each area: 

  1. The complexity of table joins and indexing is automatically built using a network of joins via automatic indexing of every single record with a unique integer index number. It is this network that is most revolutionary about the system. It both replaces the laborious planning of indexed values and of how the joins will be done. 
  2. The task of business logic and edit checks is achieved by the use of JavaScript code attached to the output XML that is generated from the core Omega0 code.  This will be discussed in a more advanced presentation.  Our primary initial concern is for achieving an ultra fast development and data entry application. Thus we do not want delays in inputting data but will accept any data in the initial application with the burden of accuracy on the user.  In the advanced versions, invalid data will be flagged by color or font with an attached message but still allowing input to proceed and data accuracy to be improved later. 
  3. The table design is a simple generic listing of values as based upon the modules and fields in each modular table, so the input tables do not need to be built. The user can specify the order of the fields that will appear in column form with both long and short names.
  4. Some generic reporting is available utilizing existing XML tools.  In subsequent versions this will be enhanced although standard relational database reporting and analysis which can be done on the default output XML and later using the relational databases by database personnel.