MSEA Binder

Here's some best practices to using the MSEA binder tool:

      Create separate projects for each version of the same project SCT database you import. (e.g. Project1_v1, Project1_v2, etc.). This will allow you to manage project version better instead of stacking different archive versions within the same project name. You don't have the option to delete individual version if they are loaded into the same project.

      For older projects, export out the project as XML and delete from the database to improve performance. The more projects and points you have in your database the slower your overall performance will be.

      Large projects will take longer to import. Plan accordingly.

      Keep your project database local to the PC. This will improve performance.

      When multiple people are working on the same project but not sharing the same MSEA binder database, have one person handle importing new SCT databases and re-validating.  After it is complete, export the new project file and have the others import it into their instance of MSEA binder.