Coordinating work packages between LRP and Production
Long range planners are responsible for the scheduling of a work package until maintenance begins. Once the work package enters the Commit or In Work status, maintenance production (who interact with core Maintenix) will take control of the visit and will manage all dates and locations.
Even if LRP is no longer in control of the work package, LRP must stay informed of any scheduling changes being done by production, since those changes may affect other upcoming work. To reflect this, whenever you run the Load Actuals feature in LRP and the work package is in Commit or In Work status, the scheduling information (start date, end date, and location) will be updated to reflect the values in core Maintenix. In addition, the work package will be locked so that LRP cannot modify it (you cannot change the dates or location).
When you publish a long range plan, if the work package is in Commit or In Work status, LRP will not make any updates whatsoever to the work package.
Work packages that are created by the Long Range Planner (LRP) and published to Maintenix remain under the control of LRP until they are committed. This means that while the work package is active, you cannot remove any of the tasks within Maintenix that are in the workscope that was published from LRP.