When Oracle was first explained as an Enterprise System, the idea of moving from the multiple bases of greenbar to a system that encompassed all of the data elements and mechanics needed to run a company was the most exciting business prospect we could think of in the 1980's. During the 1990's we were still thinking through databases, the internet, email, and tools to extract data and utilize it at various levels of the requirement. As we entered the 21st century we started to think more about the Market, Valuation and Risk. Globalization made business thinking more complex. And it required a great deal of turning, tuning and timing.
Working through every major kind of industry we noticed something. All of them were functional on the same basis (something we learned as little beanies), when turned sideways they all produced the same kind of data. There were a few minor differences in the way costing and reporting was done, but otherwise all of the activities that produce conversion were the same. So we started to look into the business cube more inquisitively.
We found that project management helped to encompass these activities and could work with more than one timeline, more than one set of elements and a portfolio. We found this to be very similar to video production. When the idea of photosynthetic virtualization entered our minds, we realized that objects can be built this way, and hence the foundation for our earlier blogs. We are describing something that we can visualize. (This is a sketch of what such a system could do. Similar to the outline of Oracle that we thought about in the 1980's. It was a much more complex 20 year process than we could have imagined.)
This became for us the practical application of something that physicists have thought about for years: motivating time and space. How did we get on board the Starship Enterprise? Well, obviously we beamed over and hardly noticed the transformation. (This means we are indeed naive, but so what.)
But for others the idea of moving from a static cube to a space-time cube would be outrageously impossible. Oh, the naysayers keep saying you can't move to inner space, you'll be destroyed. We have found this to be more than a little interesting, full of distinct possibilities for practical applications, and worth explaining to our hostile audience as well as to our friends.
Meta data lives inside the system, and usually produces graphical analysis. It also runs the system. And there are more people out there who understand meta data as it currently lives in a binary system than you can shake a stick at. But we have to think in terms of quantum, and so now we've got two sets of requirements, both of them are sideways.
Right now it would appear to anyone like Howard Hugh's Spruce goose. It won't fly they said. Well, that goose it flew but it needed a lot of improvement to become the sleek and sophisticated craft like a Harrier we now deploy in the universe. Packaging energy is very key to enabling this process to make sense.
So we have to stand on our heads and learn to rethink what we thought we knew. If you were flying an airplane, you would have to maneuver not just in a linear way across a screen, but you would need to fly up and down, in circles, and quite frankly, land in all kinds of patterns. This means that you need to pull data from both an inner cube and an outer cube, both sitting in the same position.
The difference here in the quantum based system is that time is in one cube and space is in the other, at the level of the system environment. The time cube sizes and proportions the space cube. So when you land your airplane on that position, you can insert your payload and it will perform according to the way that cube is arranged. Suppose it was a 50 year performance cube. It could bring activity up to date by tomorrow, just based on the way it is scaled and proceeds at quantum speed. The ratio of time and speed does in fact lengthen or shorten the distance to the goal. All of a sudden, project managers everywhere breathe a sigh of relief. Whatever the scale, now we can point our payload from a positioned space to a window in time.
Now that we've landed and taken our data out of another cube, we can look at meta data another way. Once again we have an inner cube and an outer cube. Based on a progression, we can use a series of operations to define the outcome of our project. In a string based nano system, string is constantly produced. This enables us to virtually wrap our project with all of the elements required to produce a fused object from a programmable environment.
The sizing of our inner cube this time is based on Resource and our Outer Cube is based on Energy Packaged as Equity. We begin with an investment package that we need to convert and optimize.
This strategy is the same as if you wanted to resize a company and develop the portfolio. It just requires you to think in terms of a production project. Graphically you can store all of your metrics and requirements in baskets that float along the project timeline(s.)
As in all applications, nothing ever became an application without learning to package and deliver energy. So the idea of our electric car being motivated by the packaging and delivery of electrons in a meta based string is not so far fetched as some may suggest. Moving into Virtual Photosynthetic production is far and away, but within our long range focus. Pandora is repackaged to illustrate the dynamic we can work with.