What is synchronization?
A copy of the EMS engagement file exists on the server; a copy also exists on each engagement team member’s laptop. In general, team members exchange updated documentation between one another, and keep the server up-to-date, through synchronization (sync).
EMS documentation consists of both information in the EMS database (data) and in working papers. While the ‘data’ is always exchanged through sync, there is an option to exclude working papers from sync and to instead exchange working papers through Check In / Check Out (CICO) with the server. (See the Check In / Check Out Performance Support).
The copy on your laptop is a complete engagement file , giving you visibility to the entire file . When you sync with another team member or the server, EMS compares your version with the other party’s version, and exchanges the differences, such that both parties end up with equal copies (i.e., you are in-sync with one another until you each start making changes). There are different methods of synchronizing, which are explained in the Sync Methods section below.
Everything in the engagement file is editable by every engagement team member . That means two people could both make changes to the same item. When their versions are synchronized, the system identifies a ‘Sync Conflict’. In some cases, the system can resolve the changes automatically. In other instances, the two people need to compare the two versions and agree on the one to keep. This is explained more in the ‘Sync Conflicts’ section below.
Sync takes time (seconds to minutes), the amount of which is dependent on a number of factors. You need to be aware of those factors, particularly the ones you can control, in order to minimize this time. Further, only one person can sync with the server at a time. Engagement teams with a large number of people, exchanging large volumes of information, may need to manage their sync behavior to avoid clogging the server, preventing an efficient flow of information, and frustrating one another.
Due to the variety of sync options, the desire to avoid conflicts and wasted time, and other factors, it is a leading practice for each engagement team to discuss and set direction about sync behaviors for that team. Further, large engagement teams may need an explicitly defined ‘sync strategy’. This is explained more in the ‘Engagement Team Sync Practices’ section below.
As engagement circumstances are highly variable, and synchronizing engagement files may be new to you and your engagement team, occasionally issues arise. EMS provides Sync Messaging, a Synchronization Summary of your past syncs, and a Synchronization History of the entire engagement team to help you troubleshoot what happened, and how to resolve. All of this, and more, is explained in the ‘Troubleshooting’ section below.
What is synchronization?A copy of the EMS engagement file exists on the server; a copy also exists on each engagement team member’s laptop. In general, team members exchange updated documentation between one another, and keep the server up-to-date, through synchronization (sync). EMS documentation consists of both information in the EMS database (data) and in working papers. While the ‘data’ is always exchanged through sync, there is an option to exclude working papers from sync and to instead exchange working papers through Check In / Check Out (CICO) with the server. (See the Check In / Check Out Performance Support).The copy on your laptop is a complete engagement file , giving you visibility to the entire file . When you sync with another team member or the server, EMS compares your version with the other party’s version, and exchanges the differences, such that both parties end up with equal copies (i.e., you are in-sync with one another until you each start making changes). There are different methods of synchronizing, which are explained in the Sync Methods section below.Everything in the engagement file is editable by every engagement team member . That means two people could both make changes to the same item. When their versions are synchronized, the system identifies a ‘Sync Conflict’. In some cases, the system can resolve the changes automatically. In other instances, the two people need to compare the two versions and agree on the one to keep. This is explained more in the ‘Sync Conflicts’ section below.Sync takes time (seconds to minutes), the amount of which is dependent on a number of factors. You need to be aware of those factors, particularly the ones you can control, in order to minimize this time. Further, only one person can sync with the server at a time. Engagement teams with a large number of people, exchanging large volumes of information, may need to manage their sync behavior to avoid clogging the server, preventing an efficient flow of information, and frustrating one another.Due to the variety of sync options, the desire to avoid conflicts and wasted time, and other factors, it is a leading practice for each engagement team to discuss and set direction about sync behaviors for that team. Further, large engagement teams may need an explicitly defined ‘sync strategy’. This is explained more in the ‘Engagement Team Sync Practices’ section below.As engagement circumstances are highly variable, and synchronizing engagement files may be new to you and your engagement team, occasionally issues arise. EMS provides Sync Messaging, a Synchronization Summary of your past syncs, and a Synchronization History of the entire engagement team to help you troubleshoot what happened, and how to resolve. All of this, and more, is explained in the ‘Troubleshooting’ section below.
การแปล กรุณารอสักครู่..