Xena software primavera

A new Primavera version may be selected for the output to match the Primavera version you are using. A prefix can be automatically applies to any of the code structures.

The additional tabs display code values from the original XER file and allow users to map these codes to the desired production database codes or to rename the codes in the revised XER file. Other features allow the ability to change activity codes from Global to Project level.

Conversion templates may be re-used. This useful feature means consistent handling of XER files repeatedly from the same source, such as when applying weekly updates from a contractor. Email: info projectcontrolsonline. Schaefer developed custom online training sessions and conducted these on a weekly basis over four weeks. The involvement of AcceleratedPM allowed Marathon Oil Company to utilize Primavera P6 on an enterprise level more effectively providing a high return on their investment in the tool.

Routine Daily Maintenance is the work required to keep a refinery running efficiently and safely. Marathon Routine Daily Maintenance schedulers and central support team continue to require occasional support as processes change or improvements are made.

Most recently, compliance reporting, a maintenance industry standard methodology to measure the overall effectiveness of work order scheduling and completion, is being reactivated. Marathon will go live with the new compliance reporting in the first quarter of Armed with that information, Marathon tasked their central support team with implementing schedule compliance measurement reporting.

During the design phase of compliance reporting Marathon again approached Accelerated PM to review their concept document. Marathon relied heavily on Mr. Schaefer during the pilot testing phase. He established an excellent working relationship with the central support team and was able to provide relevant and timely feedback. This allowed adjustments to be made in time for each round of pilot testing.

This detail provided the data necessary for proper analysis so that Mr. Schaefer could determine the source of several variances from the reporting goal. Do you run into problems while importing your subcontractor or partner data into the production P6 database?

Primavera P6 users commonly need to import projects for a variety of reasons including migrating data from an older P6 database or reviewing a project created in another department or company. Primavera users and schedulers are usually required to repeat this project import every month or every reporting cycle. Since the other company or subcontractor database is different, the potential exists to import large amounts of unwanted data and configuration codes into the production P6 database.

Most P6 users have encountered this difficulty with configuration control. These issues perpetuate themselves throughout the project by causing confusion and loss of productivity for other users when assigning values from these dictionaries. The end result is that users that import projects for status updates have found that they must spend several hours after each update cycle cleaning up the mess created from the imported project.

Other organizations have prohibited users from importing projects altogether forcing the user to implement significantly less efficient methods of updating projects, once again adding more hours to each update cycle. The solution to these problems lies in having a more robust import process than the one currently provided in the Primavera P6 application.