Interoperability: Planning Systems |
  
|
Interoperability: Planning Systems |
|
This section provides supplementary information & guidance regarding the installation and configuration of some of the 3rd party planning systems supported by SYNCHRO Software Ltd as this relates to interworking with the SYNCHRO Client application
SYNCHRO can exchange information with 3rd Party planning systems. Direct synchronisation is provided for Asta Powerproject™, and Microsoft Project™ XML, and Primavera™
Product: |
File Extension(s): |
Version(s): |
Note(s): |
Asta Poweproject |
PP |
9, 10, 11, 12, 13, 14, 15 |
|
Microsoft Project |
XML |
2003, 2007, 2010, 2013 |
Export to MS-Project 2003 ONLY (Can be opened in 2007, 2010 & 2013) |
Microsoft Excel |
xls,xlsm |
2003, 2007, 2010, 2013 |
Requires MS-Excel ODBC drivers |
PMA NetPoint |
XML |
4.1 |
|
Primavera P6 |
6.2, 7.0, 8.0, 8.1, 8.2, 8.3, 8.4, 15.1, 15.2, 16.1, 16.2, 17.7 |
Requires Primavera Integration API to connect directly P6 DB. P6 XML files can also be used without the API installation. XER files can be imported into P6 DB, then read by SYNCHRO. P6 Integration API 15.2 and higher requires Java Development Kit 8 to be installed separately |
|
Safran |
7.1 |
Requires Safran Web Services SDK to be installed separately |
(For more interoperability details, refer to the appropriate sub-section)
Synchronisation is the process through which a plan in a 3rd party system can be updated with changes made in SYNCHRO and vice versa. This has a number of benefits:
| · | You can keep using your familiar planning environment while and harness the abilities of SYNCHRO for project simulation and 4D planning. |
| · | You can continue to leverage the powerful reporting of your original planning system. |
| · | You can feedback progress reports and changes from SYNCHRO to your original plan. |
To achieve successful synchronisation with external project plans, there are a few principles and recommendations which need to be observed:
| 1. | The application being synchronised to or from may be running, but the file should be closed. |
| 2. | Import, or develop your schedule in SYNCHRO and Export, ONCE, and thereafter Synchronise. Once the project plan has been imported (or exported), all subsequent project plan changes should be exchanged using the Synchronise (To or From) operations. |
| 3. | Manage Change. Decide which application contains your Master Schedule. Try to make changes to the Master Schedule FIRST, then Synchronise to the Servant Schedule. Making changes to both schedules at the same time could result in conflicts, loss of information and unexpected behaviour. |
| 4. | Some parameters cannot be exchanged. Some properties within SYNCHRO may not have a corresponding property or value within the 3rd Party software, or vice-versa (see Interoperability: Planning Systems for specific details with regards your planning application) |
| 5. | Reschedule, Reschedule, Reschedule Make sure your project schedule, either in SYNCHRO or your Planning application, is correct before import, export or synchronisation. In SYNCHRO, use the Automatic Rescheduling option to keep you schedule up to date, or press F9 to manually reschedule. Check the documentation of your planning application for similar functionality; in Primavera P6, use the "File->Commit Changes" command (F10 key) and "File->Refresh Data" command (F9 key); in Asta PowerProject, use "Views->Refresh Views", or the F5 key. Rescheduling before import, export, or synchronisation allows you to quickly visually check that the operation was successful; and also avoids confusion when tasks are Automatically Rescheduled in SYNCHRO - this is particularly useful if you are working with applications that don't reschedule automatically. |
| 6. | Use the Original Schedule The import (or export) process establishes a 'link' ('tie', or 'synchronisation reference') between the schedule in SYNCHRO and the original import (from Asta, Primavera or MS Project). This 'link' can include (but is not limited to) the following information: |
| · | Filename |
| · | Database Name (including server hostname) |
| · | Project Name (either within a File or Database) |
When importing or exporting from scheduling systems, there are occasions where one system defines and treats information slightly differently.
An example of this is the 'Resource Appearance Profile' which in SYNCHRO defines the assignment of Resource to a Task; this concept does not exist in Asta Powerproject, Primavera or MS Project.
The following general behaviour should be expected when using synchronisation:
| 1. | SYNCHRO will automatically reschedule Tasks to ensure that any Task Dependencies and Constraints are adhered to. This may be a manual operation in your 3rd party planning application - so your tasks may move in time following import or synchronisation. |
| 2. | Start to Finish links imported to SYNCHRO will show as 'unsustainable' (with the exception of Start to Finish links with positive delays). |
| 3. | Task comments are not fully supported in the synchronisation process. (In Primavera ONLY Activity and WBS notebooks with a 'synchroNotebook' topic - typically created as a result of an export from SYNCHRO - will be synchronised) |
| 4. | Rounding Error - Durations. Started Tasks exported to Primavera will need to be re-Scheduled in Primavera to update % Complete and Remaining Duration values. Duration values may also be rounded in Primavera to the nearest day. For example the % Completed for a 10 day task can only be 10, 20, 30… 90 or 100. Primavera will round to the nearest hour if its User Preference for duration format is set to hours |
| 5. | A Suspend/Resume Task operation is not supported and is ignored by SYNCHRO |
| 6. | Task Sorting. Some 3rd Party Planning applications sorts the Task (by name, Task Id, or Activity Code) This does not affect Synchronisation although the sequence of activities between the two applications may not match. |
Related Topics:
Working with Asta Powerproject
Working with Microsoft Project
This information is subject to change without notice.
While every reasonable precaution has been taken in the preparation of this document, Bentley Systems, Inc. assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. The information contained in this document is believed to be accurate. However, no guarantee is provided (especially with regards information on 3rd party products). Use this information at your own risk.
When in doubt please consult any documentation or support related to 3rd party products mentioned herein...
Bentley Systems, Inc is not responsible for the content of external internet sites.
If you have any comments or questions, we'd be happy to hear from you.
| i. | Warning Serious problems might occur if you modify your system incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Bentley Systems, Inc cannot guarantee that these problems can be solved. IN NO EVENT SHALL BENTLEY SYSTEMS INC AND/OR ITS RESPECTIVE SUPPLIERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF INFORMATION AVAILABLE FROM US. Modify the registry at your own risk. |
| ii. | Some of the instructions contained in this document require Administrator privileges. |