Work Order Relationship Types in Oracle eAM

In Oracle Enterprise Management we can define 4 different type of relationships between work orders.

1. Parent Child.
2. End to Start Dependency,
3. Cost
4. Follow-up Work

Relationship between work orders helps to manage complex maintenance jobs.

1. Parent Child: This relationship enables a network of Work Orders, which includes one top level Work Order that defines the time line of all its children Work Orders. The start and end dates of the children Work Orders are within  the start and end dates of the parent Work Order. A child Work Order can be parent to another Work Order. One parent can have multiple children, but one child can have a single parent. There can be an infinite number of parent-child Work Order levels, within the Parent-Child relationship.
2. End to Start Dependency: You can create Work Orders with scheduling dependency relationships (including child sibling Work Orders). For example, one Work Order's scheduled start date is dependent on another Work
Order's completion. With this relationship, the next Work Order cannot start until the prior Work Order is completed.
3. Cost: You can roll the child Work Order costs into the parent Work Order, for reporting purposes. You can base the cost roll up, within a hierarchy, on scheduling relationships. Scheduling relationships are not required to roll up costs within a hierarchy. You can create a cost reporting hierarchy that is different from the scheduling hierarchy.
4. Follow-up Work: You can create a Work Order for the current capital Asset Number or Rebuildable Item, while executing work for the asset on another Work Order. For example, a second problem with the asset is discovered while executing a Work Order. A Follow-up Work Order, associated with the original Work Order, is created for the issue. This is independent of scheduling or cost relationships