in great detail but the dms 38 that slaves from the gis 40 is used to energize the system and may use more current and or less detailed infrastructure information fig4 illustrates a flow diagram view of an embodiment of a process 70 for synchronizing infrastructure information from a slave application e g the dms 38 the slave application receives a proposed update block 72 via the user interface 58 and or the communication interface 56 the proposed update indicates that the system grid 10 will change has changed or is otherwise different than the infrastructure information stored in the master application e g gis 40 the proposed update may include a permanent change or a temporary change for example a permanent change may include a physical re routing of components of the grid system and a temporary patch may include connectivity changes as part of a work package such as a fault condition in some embodiments patches resulting from proposed permanent changes may be labeled as created ready or implemented additionally in certain embodiments proposed updates that include currently implemented changes in the system grid 10 may be indicated as a u201c redline u201d patch as discussed below a redline patch may be visually distinguished in the slave application after the slave application receives a proposed update the slave application creates a patch that reflects the proposed update block.