Information on the Primavera/SDEF Activity Code Structure
Posted by Ken Avila on 12 August 2010 09:52 AM
Contracts can be configured by the USACE to receive Network Analysis System (NAS) information from Primavera or have the information manually entered into QCS. Primavera is a scheduling software that is able to export information in a format called SDEF (Standard Data Exchange Format) that can be read by QCS. If the Network Analysis System (NAS) information is to come from Primavera then the contractor will have to setup the contract in Primavera so that Primavera can create a SDEF (Standard Data Exchange File) with all of the correct NAS information in it. This will require that the contractor properly configure the Activity Code Structure (ACS) in Primavera and take into account a number of other considerations.
Note that the RMS Center will only be able to answer Primavera questions that relate to the structure of the SDEF file. If you provide us with an SDEF file we will be able to tell if it is correctly structured. We will not be able to provide support in how to create the SDEF file within Primavera or how certain values come to be inside of the SDEF file. To get the answer to those questions as well as answers to the internal workings of Primavera the contractor will need to contact Oracle Global Support at 800-223-1711. All of the information provided in this Knowledgebase article was provided by Oracle and reprinted here for your convenience. None of this information was specified, created, or mandated by the RMS Support Center.
The Activity Code Structure (ACS)
The US Army Corps of Engineers (USACE) requires the consistent use of a predefined Primavera ACS in all projects so that a SDEF file can be properly created. The ACS specifies the sequence, name, and length of Primavera code values in the project. The SDEF format must exactly adhere to this structure.
The ACS for Primavera 3 is as follows:
The SDEF value code Feature of Work (FOW) is 30 characters long. Because the maximum length of a Perimavera 3 value code field is 10 characters, the FOW value code is divided into 3 segments as shown above.
The ACS for versions of Primavera after Version 3 is as follows:
In versions of Primavera after version 3 the value code fields were expanded from 10 characters to 20. As a result the length of the FOW value code can be expanded to a length of 20. However due to an idiosyncrasy in Primavera a FOW with a length of more than 20 characters can still be entered. In the figure below you will find a screen shot from Primavera showing a list of activities with activity A1A2211045 highlighted in the upper panel. The lower panel contains attirbutes related to that activity contained in tabs. The ACS information is in the tab labeled "Codes". For this particular contract you will see activity codes for RESP, AREA, BIDI, PHAS, CATW, FOW, Sub-Area, and Level/Elevation. The activity codes Sub-Area and Level/Elevation are custom activity codes. These codes must come after all of the activity codes required for the ACS. In addition these codes are ignored by QCS. When Primavera creates a SDEF file the values entered into the "Code Value" column are included in the SDEF file as shown by the yellow highlighted cells. The one exception is FOW. Primavera will include in the SDEF file the value in the "Description" column rather than the value in the "Code Value" column. Using the example in the figure below the FOW for activity A1A2211045 is "Plumbing General Purpose" as shown in the blue highlighted cell. Since the description column can be more than 20 characters in length contractors will be able to include in the SDEF file FOW values that are more than 20 characters long in spite of the Primavera requirement that the length of activity code values is less than 20 characters.
Primavera P6 projects can store far more data than the SDEF specification requires. For example, the SDEF file structure allows for only one application of a resource per activity, while P6 enables you to apply a resource to an activity repeatedly using resource lags and durations. P6 projects intended for use with the SDEF interface should comply with the SDEF specification. You should not utilize the additional capabilities that P6 offers because the SDEF file structure cannot store the additional data.
The following is a list of items that a contractor should consider when using Primavera for the purposes of creating an SDEF file.
To store this data in a Project Management module project before you convert it to SDEF, you must create an Activity UDF named 'STMA'. This UDF must have a Data Type of Cost. If you do not create this UDF, the STMA field will be blank when you convert an XER file to an SDEF file.
To store this data in a Project Management module project before you convert it to SDEF, you must create Project UDFs named 'Contract Number' and 'Contractor Name'. These UDFs must have a Data Type of Text. If you do not create these UDFs, the Contract Number and Contractor Name fields will be blank when you convert an XER file to an SDEF file.
In SDEF files, values in the Contract Number field cannot be longer than six characters. When a Contract Number UDF value is more than six characters, this value is truncated to the first six characters when you convert to SDEF.