Notebook type scrubbing, improved UI

Written by Ravi Wallau

Written by Ravi Wallau

This blog is a deep dive into what can be accomplished with codes using P6-Scrubber prior to importing an XER/XML file. Frequently, when importing a schedule from an outside source into our existing database, there are codes we want to either delete, rename or, in the case of activity codes, rolldown to the project level. P6-Scrubber is able to handle all of these cases.

When receiving an XER or XML from an outside party, we more than likely want to remove or alter their data so it is easily identifiable when we import it to our own databases. This cleansing of data makes it much easier to keep our own data pure in our own P6 database, while still getting the information needed from an outside source.

We may receive a file with codes, UDFs, Resources, Resource shifts and curves that we either do not want to import at all, or, perhaps, we want to prefix them so we can identify where they came from after they are imported. Global calendars also pose a problem. When global calendars are imported with an XER or XML file, those calendars overwrite the definition of a calendar with the same name in your existing database, which could alter dates on your existing projects. When those projects are rescheduled, the new calendar definition is used to calculate the dates. We also may not want the new imported calendars polluting our group of organizational global calendars. Ideally, we want to keep the global calendar in the imported project and move it to a project calendar so the integrity of the project dates is not altered by removing the calendar.

P6-Scrubber gives us a quick and easy way to handle data that we merely want to remove, prefix or roll down called the Simple Scrub. Simple Scrub is a “one stop shop” for handling all these data items. It is contained all in one window, so you can quickly define what you want to do with each data element.

Do you get Microsoft Project (MSP) XMLs that need to be imported to your P6 environment but you want to control the data being imported? This cleansing of data makes it much easier to keep your own data pure in your own P6 database, while still getting the information needed from the MSP XML.

MSP data imported as an XML file contains the following that you may want to control:

• Activity Codes and Dictionary
• Activity User Defined Fields
• Resources
• Resource Codes and Dictionary
• Calendars

P6-Scrubber gives you a quick and easy way to handle this data. You can import the MSP XML into the tool to look at what the XML contains and create definitions to save and use over and over again. Let's look at each piece of data and see what can be done with MSP XML data prior to import.

Deal with Data Items in XERs and XMLs Quickly Prior to Import

Are you looking for a quick and clean way to remove or prefix data, roll global calendars to the project level or assign the resources to import to an existing resource node in an XER/XML before importing it into your production database? By doing things like this, you can keep your organization’s codes, UDFs, calendars and resources tidy and easily identify what was imported.

P6-Scrubber - Simple Scrub will allow you to do one or all of these things quickly and easily. Once a definition is set up, it can be saved to scrub other files with the same parameters, saving even more time.

Are you polluting your P6 data when you import XERs/XMLs from other companies? Do you have a scrubbing database you import XERs/XMLs into just so you can clear out unwanted data from them, re-export the cleaned project, and then re-import it to your working database? Both of these scenarios are very common and in the first case, can really pollute your working database with all kinds of unwanted garbage or in the second case, cause lost time cleaning out someone else’s junk.

P6-Scrubber is the answer to your data pollution woes. This tool designed by Emerald Associates will take care of clearing out that unwanted garbage prior to importing the XER/XML by allowing you to easily decide what is acceptable in the file. The P6-Scrubber Definition Configurator allows you to set up and save definitions for each client to be used over and over without rebuilding it each time. Definitions can also be edited, so if a new cleansing definition is needed, it can be added to the existing one.

P6-Scrubber can be deployed stand alone or it can be pointed at one or many database so data can be validated against what is already in the database.

Have you ever had the need to demote an XER from a higher version of Primavera P6 to a lower version so you can import the file into your database? This can be a problem when the file was generated in a higher version and you have a lower version in your organization. Manually modifying the version can cause data corruption and bring your database to its knees.

Are you importing schedules into scrubbing databases, taking out all the unwanted data you don't want to pollute your production database, re-exporting the schedule and then importing it into the database where it should have gone in the first place?

Do you have required specifications your contractors need to follow for their schedules, but have a hard time knowing whether those details are missing or incorrect until you've already imported them?

Do you want to ensure you are not importing POBS tables and corrupted RISKTYPE tables?

That's a lot of quality assurance to do! Maintaining your corporate data standards for dashboarding and reporting can be a full time job, especially when project teams have their own coding structures and requirements for their P6 Environment.

Don't worry; there's relief. Emerald has developed a new tool that will do all that work for you! We are now introducing P6-Scrubber.