Distributed Project Conversion Utility (DPCU) provides the capability for Prime Contractors to apply their internal burdens to a “Subcontractor’s” data or another “Division’s” data created in MPM via the Distributed Project function.
The DPCU combines and converts Element of Cost (EOC) data residing in Distributed Project transfer files (.xfr) into resource detail data. This allows the Prime Contractor to import the data, which in turn allows the Prime Contractor to utilize their Resource Library for the purpose of burdening the imported data.
The data within the Transfer Files (.xfr) is first summarized at the Total Price level (through Fee) and then converted to Total Prime (unburdened) dollars in the files created for importing. This will ensure burden costs (Overhead, G&A, Cost of Money and Fee) within the Transfer Files (.xfr) will not be co-mingled with those of the Prime Contractor’s. The Prime Dollars then become the pricing base for the application of the Prime Contractor’s burdens during importing.
For the converted BCWS and ETC data, the Prime Contractor will be required to import monthly estimate data.
For the converted ACWP data, the Prime Contractor will be required to import Actuals - using the Auto Burdening import option.
For BCWP, the process for converting data works somewhat different. Within MPM, Fee is not calculated for BCWP. Therefore, DPCU must compute Fee for the BCWP data within the Transfer File (.xfr) in order to arrive at the Total Price level. This is done to be consistent with the BCWS, ETC and ACWP data types. The formula DPCU uses to compute Total Price BCWP is as follows:
{[Total Dollars BCWP/Total Dollars BAC] x Fee BAC} + Total Dollars BCWP
This calculation ensures that the amount of Fee “earned” is based on the percent complete of the Source WBS Leg (or Project Level) that is being “Distributed”. The computed values are then used for the basis of import. However, the BCWP import file does not categorize values in terms of “Prime” vs. “Total Dollars” vs. “Total Price” etc… Therefore, it is incumbent upon the Prime Contractor to assign a BCWP Base Unit of “Prime Dollars” for the WBS that is to be receiving the converted Distributed data. After the BCWP values are imported, the Prime Contractor’s burdening structure is used to burden the BCWP Prime Dollars up through Total Dollars.
Prior to importing, the following guidelines must be implemented in the Project (s) and WBS (s) receiving the data for the following data types:
BCWP
You must assign Earned Value Method #9 (BCWP Entry) for all WBS (s) receiving the BCWP data. The BCWP import file will include cumulative monthly values and will be imported as BCWP amounts.
You must select Prime Dollars as the BCWP base. This and assigning Earned Value Methods are done within the Integrated Planning Screen - Milestones tab.
You must Calculate BCWP after the import. This is done within the Project Maintenance screen.
ACWP
You must assign a Rate Table ID to be used for the burdening of Actuals. Remember that the Actuals import file is for Auto Burdening, meaning that it does not include any of the following values: Overhead, G&A, Cost of Money or Fee. The rate table must first be created in the Resource Library of the Global File ID that is being used by the Project receiving the data. After creation, identify the Rate Table ID within the Project Maintenance screen.
The WBS element must have a value (any value) in the charge number field in order for MPM to allow Actuals to be accepted for the WBS. You enter this value (any value) within the Work Breakdown Structure screen.
BCWS/ETC/ACWP
You must identify the Resource Code ID that is to be used for the converted Distributed Project data. Enter that code in one of the twelve following fields from within the Work Breakdown Structure screen: Alias, Manager, Xref-1-10. The Resource Code ID may not exceed 10 alpha-numeric characters, or have any embedded blanks.
The Resource Code ID identified in number 1 above, must exist in the Resource Library of the Global File ID being used by the Project receiving the imported data.
Do NOT enter the word DISTRIBUTED under the Xref-1 field, which is normally required only when processing standard (unconverted) Distributed Project transfer files. If this identifier is mistakenly entered, the imported data will be rejected during the import process.
If you wish to compare the data residing in the converted transfer files with the data currently residing in the WBS Element, it is recommended that you import the file into a copy of the Project. Not only is this recommended as a standard back-up procedure for preserving your current contract position, it allows you to run the Project Comparison reports from within MPM. These reports compare the data of two like Projects side by side and display the variances between them. This would allow you to analyze the “before” and “after” positions before actually updating the master Project.
DPCU uses a Microsoft Access database to store the retrieved data from the Transfer Files (.xfr) for further data manipulation and calculations. Performance may be improved by routinely compacting the database. Refer to the following Microsoft Knowledgebase article for further information:
http://support.microsoft.com/kb/288631