Work Order Concept
With CAP4, the analogy used to describe how information is passed is framed in an organizational framework that includes:
- Director and/or Associate Director
- Manager
- Worker
Work Orders are messages that are passed amongst Directors and Managers onto workers. While in the future it may be possible for a work order to be placed via a worker, for now we will only allow work orders to be placed from these two roles. The concept of a work order can be one that encompasses many managers and operates on at least one Worker. Work orders can have varying state such as:
- Creation in process
- Created and not expired
- Created and expired
The concept of expiration allows new work orders to be regenerated and integrate new processes to handle work. For CAP4 a work order will mostly encompass the work a Manager does on a group of Workers. The operations that can be done on workers include:
- Console()
- Power()
- Status()
- Manage()
Work will be Managed using std ipc style forking and alarm handling. Work Orders will leverage Device Driver functions that can operate on their own outside of the CAP framework, and eventually evolve into other packages (think CPAN). These drivers merely need to present the above 4 available operations to work in the CAP4 environment.
