Codes
You can showcase project data at a summary level, a detailed level, or any level within the project by establishing a coding system and assigning codes to your project. A well-designed coding system offers lucid and succinct information.
Code files can be a flat file representing a list of managers, for example, or they can have parent-child relationships or a hierarchical structure defining a work breakdown structure (WBS). After creating a code file, you can assign that code file to your project and the codes become a pick list of valid codes during data entry. Codes are used for roll-up reporting, filtering, and processing, among others.
The table below provides information on the areas in Cobra where you can assign codes.
Area | Number of codes that you can assign | Example |
---|---|---|
Project | 9 | Product line, division, sector |
Control Account | 3 | Work Breakdown Structure (WBS), Organization Breakdown Structure (OBS) |
Codes assigned to a control account | 20 | Charge number for loading actual costs, recurring versus non-recurring costs |
Control Account Manager | 1 | Used in CAP and Pivot reports showing the responsibility matrix (RAM) and security for explanation of variance |
Work Package field | 1 | Alternate rollup for reporting |
Codes assigned to a Work Package | 20 | Change request number, location of the work, vendor, and codes from an activity in the schedule, and so on |
Code to use against the baseline changes and/or audit log | 1 | Change numbers for audit log |
Code on codes | 9 | Alternate codes for customer WBS, contract line item number (CLIN), Integrated Product Team (IPT) lead, and so on |
Resource codes | 9 | Cost centers, cost element codes, and so on |
Rates | 2 | Overhead codes and so on |
Parent-Child Relationships in Code Files
If your code file has parent-child relationships or hierarchy, you are often allowed to select a level of the code file for reporting summaries or filters. It is helpful to create related codes at the same level. For example, the codes of cost (such as Labor, Material, and ODC) should all be at the same level of your resource file. Defining related codes at the same level allows you to easily report or filter on labor, for example. When you run a report, you can choose resources and then a level of the code file as a section criterion, or as a filter for reporting or processing your project.
- Related Topics:
- Code Usage in Cobra
Cobra uses codes in different ways. - Code Files
The initial step that a project manager usually takes is to establish the project’s scope. - Types of Code Files
Typically, a project has two code file structures: one for the Work Breakdown Structure (WBS) codes and another for the Organizational Breakdown Structure (OBS) codes. - Code File Structures
Cobra uses three types of code file structures to define the parent-child relationships for codes. - Use a Code File in Multiple Projects
Although a project typically has multiple breakdown structures associated with it, a specific code file can also be used with more than one project. - Validate Code Assignments — Solve Roll-Up Issues
The Validity Check utility has an option for validating codes. This option checks for code assignments that are no longer in the code file. - Codes and the Integration Wizard
You can add code files and code assignments to your project using the Integration Wizard. - Codes and the Report Wizard
When you use the Report Wizard to run a report, you can select the codes that you want the system to use. - Variance Thresholds
Management by exception, concentrating on areas that exceed predefined thresholds, is an efficient way to manage a large project. - Code View
When you create a project, you have the option to validate a number of code fields against a code file. Utilize the Code view to create the valid list of codes. - New Code File Wizard
Use the New Code File Wizard to create code files. - Code File Properties Dialog Box
Use the Code File Properties dialog box to view or modify code file information. - Code File Security
A code file can be accessed by either a user or a group, provided that they are granted permission to do so.