Industrial automation distributed project control with milestone rollback

A method, comprising:

• maintaining, on a system comprising a processor, system project data that, in response to execution on one or more industrial devices, facilitates monitoring and control of an industrial automation system;
• receiving, by the system from one or more client devices, edit records defining modifications requested to be performed on the system project data;
• classifying a first subset of the edit records that are applied to the system project data as applied edit records;
• classifying, by the system, a second subset of the edit records that are not applied to the system project data as unapplied edit records;
• and
• in response to determining that first project modifications defined by a first edit record conflict with second project modifications defined by a second edit record and currently applied to the system project data, and determining, based on application of a conflict resolution rule, that the first edit record is to be applied instead of the second edit record:
• undoing, by the system, the second project modifications from the system project data,
• applying, by the system, the first project modifications to the system project data,
• storing, by the system, the first edit record in association with the system project data as one of the applied edit records, and
• reclassifying, by the system, the second edit record from the applied edit records to the unapplied edit records.

A non-transitory computer-readable medium having stored thereon instructions that, in response to execution, cause a system comprising a processor to perform operations, the operations comprising:

• maintaining system project data that, in response to execution on one or more industrial devices, facilitates monitoring and control of an industrial automation system;
• receiving, from one or more client devices, edit records defining edits to be applied the system project data;
• classifying a first subset of the edit records that are applied to the system project data as applied edit records;
• classifying a second subset of the edit records that are not applied to the system project data as unapplied edit records;
• and
• in response to determining that first project modifications defined by a first edit record conflict with second project modifications defined by a second edit record and currently applied to the system project data, and determining, based on application of a conflict resolution rule, that the first edit record is to be applied instead of the second record:
• undoing the second project modifications from the system project data,
• applying the first project modifications to the system project data,
• storing the first edit record in association with the system project data as one of the applied edit records, and
• redesignating the second edit record from being classified as one of the applied edit records to being classified one of the unapplied edit records.