A Deltek Cobra IMS integration connects the Integrated Master Schedule (IMS) to the program’s cost and earned value data. The scheduling application manages activities, logic, milestones, constraints and critical paths. Cobra uses mapped schedule information within the Earned Value Management System (EVMS) to organize time-phased budgets, calculate earned value, analyze performance and maintain forecasts.
Cobra does not replace the IMS or calculate its network logic. Instead, it serves as the cost and earned value engine alongside a scheduling tool such as Deltek Open Plan, Microsoft Project or Primavera P6. A reliable integration gives the program one consistent view of scope, schedule and budget.
What role does Cobra play in an IMS environment?
Deltek describes Cobra as a cost and earned value management solution that connects schedule and cost data. In practice, program-controls teams use it to maintain budget, earned value, actual cost and Estimate to Complete (ETC) information.
The IMS performs a different job. It models the sequence and timing of the work. It also identifies dependencies, forecast dates, critical paths and schedule risk. For a detailed discussion of that role, see the complete guide to the DoD Integrated Master Schedule.
The distinction matters because an EV schedule indicator is not the same as network schedule analysis. Schedule Variance (SV) and Schedule Performance Index (SPI) compare earned value with planned value. They do not measure days of delay, calculate float or identify the driving path to a contractual milestone.
Therefore, a program can report an SPI near 1.00 while a critical delivery path is slipping. The team must review Cobra performance data together with IMS critical and near-critical paths. The article on how the IMS supports earned value management explains this relationship in more detail.
How Deltek Cobra IMS integration works
The integration depends on common identifiers. Schedule activities must contain coding that allows Cobra to associate them with the correct control account, work package or other approved project structure.
Deltek’s Integration Wizard documentation explains that activities in an integrated cost and schedule environment are identified with control account points in the EVMS. The wizard supports schedule data from Open Plan, Microsoft Project and Primavera, as well as structured files.
1. Establish the control account and work package structure
First, the program defines the scope hierarchy used by both systems. The Work Breakdown Structure (WBS) identifies the product or scope element. The Organizational Breakdown Structure (OBS) identifies responsibility. Their intersection normally establishes the control account.
Work packages then divide the control account into manageable units of executable work. Cobra stores and analyzes budget and earned value within this structure. Meanwhile, one or more IMS activities may support each work package.
A one-to-one relationship between every schedule activity and Cobra work package is not normally necessary. However, every activity used to drive performance measurement should map unambiguously to the appropriate control point. The program should document its mapping rules in the EVMS description, scheduling procedures or integration work instructions.
2. Add stable mapping fields to the IMS
Next, the scheduler assigns the required coding to the detailed schedule. Typical fields include:
- WBS identifier
- Control account identifier
- Work package number
- Control Account Manager (CAM)
- OBS or responsible organization
- Milestone or activity identifier
- Earned value technique, when the integration design uses it
- Budget or forecast class, when resource assignments will move between systems
The exact fields depend on the scheduling application, Cobra configuration and organizational procedures. For example, a Microsoft Project implementation may use custom text or outline-code fields. Those fields should contain controlled identifiers rather than informal descriptions.
Stable identifiers are critical. Task names can change during normal planning, while task row numbers can change when users insert, delete or sort activities. A durable activity identifier and controlled work package code provide better traceability. Microsoft Project users should understand the difference between Unique ID and Task ID before designing an interface around either field.
3. Import the schedule through a controlled configuration
Cobra can save integration configurations so the team can apply the same mapping and import rules during each accounting cycle. The configuration should identify the source schedule, project keys, date fields, resource mappings and import actions.
For Microsoft Project Professional, current Deltek Cobra documentation describes integration through the Microsoft Project XML format. Supported methods and software versions can change, so administrators should verify the system requirements for their installed Cobra release.
A saved configuration improves repeatability, but it does not eliminate the need for validation. The program-controls team should review import warnings, rejected records, unmatched codes and unexpected additions before accepting the results.
4. Reconcile dates, status and time-phased data
The IMS and Cobra must use compatible calendar and status conventions. At a minimum, the team should reconcile:
- The IMS status date and Cobra calendar cutoff
- Baseline and forecast start and finish dates
- Control account and work package identifiers
- Open, in-progress and completed status
- Budget and forecast periods
- Resources, rates and units when assignments are transferred
The schedule status date deserves special attention. If the scheduler statuses the IMS through one date while the cost team advances Cobra through another, current-period performance can become difficult to explain. See what the IMS status date controls for practical guidance.
Programs also need a defined rule for time-phased resource assignments. Some organizations resource-load the IMS and transfer budget or forecast spreads into Cobra. Others maintain authoritative budget spreads in Cobra and use the IMS mainly for dates, status and forecast timing. Both designs can work if procedures define system ownership and reconciliation controls.
A practical Deltek Cobra IMS example
Consider a fictional program developing a mobile radar subsystem. The IMS contains activities for completing the antenna design, releasing drawings, fabricating the first assembly and conducting qualification testing.
The antenna design control account includes work package WP-220, “Complete Antenna Detailed Design.” Five IMS activities support that work package. Each activity carries the same WBS, control account and work package codes, but each retains a unique schedule activity identifier.
The program has time-phased WP-220’s labor budget in Cobra. During the monthly status cycle, the scheduler updates actual dates, remaining durations, logic and forecast dates in the IMS. The CAM then approves the technical progress used to determine earned value.
After the integration and earned value calculation, Cobra shows that WP-220 earned less value than planned and has an unfavorable cost variance. However, the IMS shows that one incomplete drawing package directly drives the fabrication start milestone. The team therefore treats the issue as both a cost and a schedule problem.
This example shows why Cobra and the IMS must remain separate but synchronized. Cobra quantifies performance against the Performance Measurement Baseline (PMB). The IMS identifies the remaining sequence of work and the date consequences of the delay.
Contract requirements versus software choices
No general Federal Acquisition Regulation (FAR) or Defense Federal Acquisition Regulation Supplement (DFARS) requirement mandates Deltek Cobra. A contract may require an acceptable EVMS, an IMS, specified data deliverables and access for government surveillance. The contractor still selects and configures the tools that support its approved system unless the contract states otherwise.
For example, DFARS 252.234-7002 requires an EVMS and management procedures that generate timely, reliable and verifiable cost and schedule information when the clause applies. It does not prescribe Cobra, Microsoft Project, Open Plan or another commercial application.
Likewise, the exact IMS content, reporting format, submission frequency and data requirements come from the applicable contract clauses, Contract Data Requirements List (CDRL), Data Item Descriptions (DIDs), agency direction and approved tailoring. Teams should review the awarded contract rather than treating a software convention as a contractual rule.
The DAU Integrated Master Plan and IMS guide recommends consistency and traceability between the IMS, work packages, WBS and cost reporting structure. However, guidance documents and recommended practices do not override contract language.
Common Cobra and IMS integration failures
Uncontrolled coding changes
A scheduler changes a work package code to improve a report, but the Cobra mapping still expects the previous value. The next import may reject the activity or create an unintended structure. Controlled codes should therefore follow the same change process as other baseline and system data.
Using task names as primary keys
Names help users understand the work, but they make weak interface keys. People revise names for clarity, customer comments or reporting preferences. Use stable identifiers for integration and retain names as descriptive data.
Different status dates
A schedule updated through Friday and a Cobra period closed on the prior Sunday can produce inconsistent current-period results. The monthly process should define one cutoff convention and address approved exceptions.
Importing without a reconciliation report
A successful system message does not prove that the data is correct. The team should compare record counts, control account totals, work package dates, budget periods and exceptions before calculating or publishing performance.
Allowing Cobra dates to substitute for schedule analysis
Cobra can organize and report time-phased data, but it does not replace critical path analysis. Schedulers still need to evaluate logic, float, constraints, out-of-sequence progress and driving paths in the IMS. The IMS critical path analysis process provides a practical review approach.
Updating the schedule without assessing the PMB
A forecast date change does not always require a baseline change. However, the team must assess whether the schedule update affects time-phased budget, work package boundaries, earned value methods or baseline traceability. The distinction between forecast maintenance and baseline revision is covered in replanning versus rebaselining.
Recommended monthly control sequence
A mature integration process normally follows a defined order:
- Set and communicate the accounting-period cutoff.
- Collect schedule status from CAMs and activity owners.
- Update actual dates, remaining durations, logic and forecasts in the IMS.
- Run schedule quality checks and resolve material exceptions.
- Approve technical progress and earned value inputs.
- Back up the IMS and Cobra project before integration.
- Run the approved Cobra integration configuration.
- Review errors, warnings, unmatched codes and unexpected records.
- Reconcile control account, work package, date and time-phased values.
- Calculate and post earned value in accordance with approved procedures.
- Load and reconcile actual costs.
- Update ETC and Estimate at Completion (EAC) forecasts.
- Analyze cost, earned value and network schedule results together.
The exact sequence may vary because of accounting interfaces, subcontractor data, customer calendars or approved EVMS procedures. However, schedule status should be stable before the team relies on Cobra’s period results and forecasts.
What a good integration should achieve
A good Deltek Cobra IMS integration does more than transfer data. It preserves traceability from detailed activities to work packages, control accounts and the PMB. It also gives CAMs and program managers consistent information for decision-making.
The strongest implementations have clear system ownership, controlled coding, repeatable configurations and documented reconciliations. As a result, the program can explain not only whether performance differs from plan, but also which remaining activities drive the outcome and what corrective action is required.
FAQ
Is Deltek Cobra an IMS scheduling tool?
No. Cobra manages cost, budget, earned value and forecast data. The IMS network normally resides in Open Plan, Microsoft Project, Primavera P6 or another scheduling application.
Does every IMS activity need a Cobra work package?
Every relevant activity should map to an approved control point, but several activities may support one work package. The mapping design should match the program’s planning detail, earned value methods and management needs.
Does a Cobra import automatically make the EVMS compliant?
No. Compliance depends on the complete management system, including processes, people, data quality, baseline controls and consistent execution. Software supports those processes but does not establish compliance by itself.
Should the IMS or Cobra own the forecast dates?
The network schedule should normally remain the authoritative source for logic-driven activity dates. Cobra can use those dates to support time-phased cost and forecast analysis. The organization’s approved procedures should state the ownership rule explicitly.