Handoffs

A key feature of PIPES is the data handoff management between two models in an integrated modeling project. PIPES manages these data handoffs across both the planning and the operations levels of the graphs. Specifically:

• Planning
• Operation

For planning, handoffs are planned in the Project Config. The handoffs are represented as an edge property between two models and have a unique handoff_id associated with them. What's more, handoff requirements are further declared (associated datasets, transformation requirements, etc.) in the Model Run configuration .

For operation, all handoff activities occur under model runs and are represented by a collection of nodes:

1. a Transformation Task
2. the resulting transformed handoff Dataset,
3. and, a QAQC Task (see image below).

PIPES uses handoffs to track progress and determine what transformations need to occur on datasets (see Validation and Tasks for more information).

We recommend creating a handoff for every unique dataset that will be exchanged by a model, and for every unique exchange of a dataset, even if the source dataset (e.g., Dataset 1 in the image above) is the same. This allows PIPES to help you track and manage differences in requirements for the consumption of that dataset for the different models. For example, if Dataset 1 in the above image was going to be shared with another model – Model C – we would recommend creating a second handoff for this exchange so that PIPES can ensure the metadata requirements of the transformed dataset are appropriate for Model C.