Difference between revisions of "Advanced automation/Increasing capacity automatically as required"

From AdCiv
Jump to: navigation, search
Line 2: Line 2:
  
 
This capability means we will be able to do things that are simply not possible at the moment. Mega-scale engineering projects become feasible. If a task is complicated, tedious and a great effort we only need to design the system for the job and let it get on with it. Easier said than done of course. But as these systems become more sophisticated, so will the design tools. The engineering teams will only need to interface with these complex systems at ever higher levels of abstraction. It will be similar to high-level programming languages hiding the lower levels of code - the individual nuts and bolts will be like the noughts and ones of machine code.
 
This capability means we will be able to do things that are simply not possible at the moment. Mega-scale engineering projects become feasible. If a task is complicated, tedious and a great effort we only need to design the system for the job and let it get on with it. Easier said than done of course. But as these systems become more sophisticated, so will the design tools. The engineering teams will only need to interface with these complex systems at ever higher levels of abstraction. It will be similar to high-level programming languages hiding the lower levels of code - the individual nuts and bolts will be like the noughts and ones of machine code.
−
 
−
These systems needs to be carefully controlled by people. We will always need to understand how they work, at every level, and they will need to be monitored. Some people wonder whether we will get to a stage where the machines are so sophisticated, and we have relied on them for so long, that no-one will actually know how they work, and therefore we will not be fully in control of them. The reality is that there will always be people interested in this sort of thing - engineers, scientists and geeks in general. They want to know how to make things and understand how they work. There always have been geeks, and luckily there always will be.
 
−
 
−
People will need to improve the designs and make sure they are safe and efficient. We must make sure that we always remain part of the loop. It is highly likely that we will develop computer-controlled systems more capable at certain tasks than we are, in fact we already have done, but this trend will inevitably continue until there is very little in terms of system control that can't be done better by a machine system. However they will still ultimately be tools for people to work with and do a job for us.
 
 
<noinclude>{{refresh|Closed-loop automation}}</noinclude>
 
<noinclude>{{refresh|Closed-loop automation}}</noinclude>

Revision as of 22:40, 29 December 2006

A major advantage of having processes almost completely automated is that the capacity can easily be scaled up. Just as the manufacturing and construction machinery can be repaired automatically, more manufacturing machinery can also be created by machine. The work-force can almost be conjured up from material in the ground (or recycled material), as needed.

This capability means we will be able to do things that are simply not possible at the moment. Mega-scale engineering projects become feasible. If a task is complicated, tedious and a great effort we only need to design the system for the job and let it get on with it. Easier said than done of course. But as these systems become more sophisticated, so will the design tools. The engineering teams will only need to interface with these complex systems at ever higher levels of abstraction. It will be similar to high-level programming languages hiding the lower levels of code - the individual nuts and bolts will be like the noughts and ones of machine code.

Refresh Closed-loop automation with updated text

Retrieved from "http://adciv.org/wiki/index.php?title=Advanced_automation/Increasing_capacity_automatically_as_required&oldid=3823"