The CAFE2 database is separate from the CAFE database, i.e. persistent objects created in one database will not appear in the other. This provides a useful testbed for the example described in this memo. From here on, CAFE will refer to the normal, local CAFE database and CAFE2 will refer to the remote CAFE database. This is needed because while machines are specified by string names in the processflow, machine objects are referenced via pointers in the task tree. This machine is located at a remote site.
CAFE detects that the next operation utilizes a machine located in a remote facility.
At this point several things need to be done. The data can then be manually copied into the CAFE database. Once all the data from the remote operations have been entered, the machine operations in SubProcess 3 are done again in the usual local manner. There are many problems with this zeroth-order model. Another problem is that there is no mention of data integration or transparency.