Migrating Template Structure from SiteManager

Data migration is the process of moving data from one product database to another, usually for a product upgrade or relocation. A migration only transfers data that does not already exist in the target location. Once successfully migrated, data is managed in the new location and can no longer be managed in the source location.

The system supports migration of SiteManager template structure and usage data for DWR item postings and material tests. SiteManager template structure is migrated into AASHTOWare Project as agency entities and agency views. An agency entity is a business entity composed of database fields defined by the agency in AASHTOWare Project (see Maintaining an Agency Entity). An agency view is a user interface designed by the agency to enable users to access and change data in an agency entity (see Maintaining an Agency View). The system automatically creates agency entities and their associated agency views during template structure migration. The system also migrates any associations between reference items and templates or material tests and templates.

The agency entities that result from migrating template structure are marked as Migrated and cannot be modified. Template structure must be migrated before template usage data can be migrated. Usage data is the information that was entered and stored by using the templates in SiteManager. Once usage data is migrated, the associated agency views cannot be modified.

If the agency wants to continue using a migrated agency entity to store new data, the agency entity and associated agency view must be copied and renamed. The new agency view must then be updated with the new name for the appropriate agency entity.

For material test templates, the Test Spec, Mix Design Table Name, and Mix Design Column Name fields are migrated as Notes for the agency entity field.

Template fields with a type of NU are migrated as numeric agency fields. For numeric fields with a specified field length, the system creates an IsNumber validation rule with the correct precision.

Template fields with a type of AN, LA, and CO are migrated as text agency fields. For CO type fields, the system creates a calculation rule that contains the expression as a comment. For text template fields with a specified length, the system creates a MaxLength rule with a MaxAllowed value.

Templates that have one or more fields with invalid field types or invalid field lengths are not migrated. When a template name matches an existing agency view name, the template will not migrate.

Follow these steps to migrate contract data from template structure from SiteManager to AASHTOWare Project:

From any page in the system, select Execute System Interface from the Actions menu on the Menu bar.

The system takes you to the System Interface component, which displays a list of all the available interfaces.
In the list, select Migrate Template Structure from SiteManager.
Optional: If you want to schedule the interface process to run at a later time, select Schedule Interface on the Settings menu on the component subheader. Select the Enable Scheduling check box and set scheduling information as required. For more information, see Scheduling a Process.
Click the Execute button on the component header.

The system runs the interface process. Depending on the size of the database you are migrating from, this process might require a long period of time to complete.
You can monitor the status of the interface process on the Process History Overview component.

When the process completes, you can view the start and finish times and the log files. For more information, see Viewing Process History.