In our last Topic about a Qve example of Quantum based production emulation we had shown the idea of moving from the concept of building a design set and moving it out to a production site or the additional concept of moving a virtual machine to a specialized task in the Virtual Universe. But there are several functional aspects of Time and Motion that need to be deployed in the spectrum, and here we want to see how many topic related aspects of this we can use to answer questions about this idea. In our last blog entry we asked this question:
See if you can help us solve this puzzle. When do you apply the Time Bottle, when do you apply Timelines and when do you apply the Manifold? We are going to talk about this next...
The Time Bottle idea is the Gini System that enables all of the parts of the Machine to communicate with one another. In some ways this idea can work with the ship in a bottle idea or the manifold net which can both be deployed from string based elements like plastic space. So this idea can actually be deployed anytime but is distinctly part of any object deployed into a METAframe or as part of the internal METAframe. The time bottle arrangement should also have a watch window that enables a proxy to follow the output, time any changes and deploy new object relations.
The Manifold always controls the overall deployment and operation of any object. Gini objects always communicate with the Manifold. There are some standards that are plainly written such as 144 cubits which are mentioned throughout time, and while may relate to earlier technologies, certainly remain appropriate. ISO standards are what makes development connectable with new technology and existing formats, even as it relates to the inner space of the Virtual Universe. We mention this because this is probably the way things will progress from the beginning.
While we have shown 3 or more timelines used in Development, and we have made calculations of how to develop an agile project using these timelines^, we haven't discussed using the cloning process. It is possible to clone more than one proxy arrangement during development and to use teams to manage various aspects of the project such as more than one Instance to aid in correspondence. Using plastic space and creating your own timing device or Brane, a series of impulses can set up the timings that you are looking for. Also, color coding the impulses can allow you to know the progress or stage of your project.
^may not be published in this series
Additionally, in the production of Virtual Glass, it may be necessary to tie different lattice arrangements in certain sequences. This is the type of utility idea that may make sense.
Because these ideas are just the beginning of building in the Virtual Cube we can offer only a few ideas, but these are here to give some substance to the ideas in emulating strategies for development.
In order to enable the correct rotational speed from our keys to deliver subassemblies to our production we increased our manifold speed.
Most notably we need to correlate this to our maps: using portion below note the call ops process found here: http://quantumve.blogspot.com/2016/12/manifold-delivery-in-qve.html
Now all of our ideas are coming together more closely and we can see that everything is based on spintronics. The way we position subassemblies with our keys is important to the strategic planning of production assembly but we keep using our utility maps as the means to co-ordinate our process. The process is always going to rotate subassemblies according to a random access program and this would enable very good encryption.
The maps we used equated to the area that we required and it also created some topography that we could use to distribute our requirement. We are certain that this would not be the only setup that the operation could use. All of the different analogies of how a Quantum Cube works are found in different media.
The use of a Flag system is also part of the Time and Motion control relative to the Formula ONE theory of the best use of materials and processes to refresh and rebuild in a META State.
Another reason for using the Flagler Rail map is the idea of the Cube and the Progression. We began with a Walk progression and moved to a Run progression when we learned how to move onto the Manifold. Cubes move the process much like a rail system.
Also Read:
An example... more to follow in QVE
Disclaimer: Blog material is presented as the basis of discussion material and is not to be construed as advice, counsel or education, and may at times be misconstrued if read in a context different than the writer's intent. No portion of this blog has been knowingly reproduced. Any resemblance to a specific company or entity is purely coincidental
Disclaimer: Blog material is presented as the basis of discussion material and is not to be construed as advice, counsel or education, and may at times be misconstrued if read in a context different than the writer's intent. No portion of this blog has been knowingly reproduced. Any resemblance to a specific company or entity is purely coincidental