Become a Guru!

NEW: IPMR DI-MGMT-81861

IPMR DI-MGMT-81861, What Is It?!

The new Integrated Program Management Report (IPMR) Data Item Description (DI-MGMT-81861) both updates and combines DI-MGMT-81466A Contract Performance Report (CPR) and DI-MGMT-81650 Integrated Master Schedule (IMS) that have been in place since 2005. Contracts meeting Earned Value requirements must comply with guidelines in the American National Standards Institute/Electronic Industries Alliance Standard 748, Earned Value Management Systems (ANSI/EIA-748) and report Format 1 through 7 established in the IPMR DID. Format 6 applies to all development, major modification, and low rate initial production efforts regardless of DFARS 252.234-7002 applicability.

Click here to Download a copy of the new DI-MGMT-81861

Bottom Line Up Front!

  • DI-MGMT-81861 supersedes DI-MGMT-81650 and DI-MGMT-81466A.
  • Reporting requirements limit the number of reportable variances to 15.
  • IPMR takes effect on all applicable new contracts after 01 July 2012.
  • Combines previous CPR (Formats 1 through 5) and IMS DIDs into a SINGLE and UPDATED document with seven Formats.
  • Introduces new terms such as Driving Path and Schedule Visibility Tasks.
  • Clarifies previous topics such as Critical Path and Schedule Margin.
  • Contact AzTech for help with the DI-MGMT-81861
 

New



Driving Path - Para # 3.7.1.3.5.8
Milestone Target - Para # 3.7.1.3.6.5
Required IMS Fields - Para # 3.7.1.3.7.3
Schedule Visibility Task (SVT) - Para # 3.7.2.1
Different
Schedule Percent Complete - Para # 3.7.1.3.5.4
Critical Path - Para # 3.7.1.3.5.9
 Baseline Schedule - Para # 3.7.1.3.5.11
Schedule Risk Assessment (SRA) - Para # 3.7.1.3.6
SRA Results - Para # 3.7.1.3.6.3
Monthly Analysis - Para # 3.7.1.4
Lead/Lag - Para # 3.7.2.2
Constraints - Para # 3.7.2.3
Schedule Margin - Para # 3.7.2.4

Click here to download a printable version of the DI-MGMT-81861 comparison

Further Detail

New:
3.7.1.3.5.8. Driving Path
Driving Path is a new term added to distinguish a driving path to an interim milestone as opposed to the critical path to program completion and defines it similarly to critical path. [Back]

3.7.1.3.6.5 Milestone Target
A new item added to the DID states that the Government determines the milestone target(s) for the SRA based on contract events. [Back]

3.7.1.3.7.3 Required IMS Fields
A new item that specifies the applicable fields that need to be identified in the IMS and described in the Data Dictionary. [Back]
  • Control Account/Work Package
  • Subcontractor
  • Justification of Lead, Lag, Constraint
  • Earned Value Technique (EVT)
  • Risk Mitigation Tasks
  • Critical Path and Driving Paths

3.7.2.1 Schedule Visibility Task (SVT)
A new item added to the DID that increases management visibility and functionality of the schedule for non-PMB related items. SVTs can model the effects of duration related to vendor lead time, awaiting customer approvals, or facilities maintenance activities for example; time that would otherwise be reflected with less visible constraints and lags to represent the duration. [Back]

Different:
3.7.1.3.5.4. Schedule Percent Complete
Clarifies percent complete is task duration based and is not used to status BCWP. [Back]

3.7.1.3.5.9 Critical Path
Critical Path definition clarifies that it represents the contract’s longest total duration through the network; meaning to program completion. Refer to the Driving Path when analyzing the longest path to an interim milestone. Clarifications incorporated previous subparagraphs, alerting that critical path does not rely on zero or negative total float, but on logic lead/lag, durations, constraints, and status. The revised paragraph dropped “near-critical” and “easily identified” from its criteria. Elsewhere Format 6 refers to "primary, secondary, and tertiary driving paths" for previously used term “near-critical”. [Back]

3.7.1.3.5.11 Baseline Schedule
Clarification defines typically setting the baseline equal to the current schedule early dates at the time of the baseline establishment. Intent may be to address previous experience with programs setting the baseline according to the latest possible dates (“late dates”), and executing according to their “early dates”; where the baseline does not represent the planned work. [Back]

3.7.1.3.6 Schedule Risk Assessment (SRA)
Clarifications to three-point estimates uses the terms “minimum remaining duration, most likely remaining duration, and maximum remaining duration", and uses the terms "primary, secondary, and tertiary driving paths" for previously used term “critical / near critical” paths. [Back]

3.7.1.3.6.3 SRA Results
Clarification includes using Format 5 to discuss results, added sub paragraphs for SRA Reporting Frequency, specifying that SRAs are required prior to an IBR, before processing an OTB or OTS, and before implementing a significant cost and schedule reset, also referred to as a single point adjustment.  Dropped the previous DID statement, “The risk analysis may be performed within the IMS or within a separate risk tool as appropriate based on the capability of the automated scheduling tool.” [Back]

3.7.1.4 Monthly Analysis
Format 6 monthly analysis requirements are defined in Format 5 Explanations and Problem Analyses, paragraph 3.6.7. [Back]
Clarifications include:
  • analysis of primary, secondary, and tertiary critical and driving paths
  • trends of total float and mitigations applied
  • variance to baseline schedule at the total contract level in days
  • any changes in the duration of schedule margins
  • changes to Task Activity Codes and Data Dictionary
  • results of any internal schedule health analysis
Note that variance reporting requirements have changed to limit the number of reportable variances to 15 and are described in 3.6.10.2 Variance Analysis Selection and Reporting Overview.

3.7.2.2 Lead/Lag 
This revised item adds Lead to the topic along with Lag, perhaps giving more recognition of its use, but still discourages Leads, and further requires documentation within the IMS for using Leads and Lags. [Back]

3.7.2.3 Constraints
Clarification to definition, minimize those constraints affecting “late” dates or both “late and early” dates, and requires justification for constraints affecting “late dates” or both “late and early” dates, and “early dates” one month beyond status date. Constraints affecting both “late and early” dates are hard constraints. [Back]

3.7.2.4 Schedule Margin
Clarification to definition includes stronger required baseline language, placed as last task/activity/gap before a contract event or end item deliverable, clearly label if reflected as a task, and discuss changes in Format 5. Interpretation is that an IMS may have several schedule margin conditions in the IMS, placed immediately prior to an interim milestone as well as program completion. [Back]


IPMR Format Definitions


The IPMR contains data for measuring cost and schedule performance on Department of Defense (DoD) acquisition contracts. It is structured around seven formats that contain the content and relationships required for the electronic submissions.
 
Format 1 defines cost and schedule performance data by product-oriented Work Breakdown Structure (WBS).
Format 2 defines cost and schedule performance data by the contractor's organizational structure (e.g., Functional or Integrated Product Team (IPT)).
Format 3 defines changes to the Performance Measurement Baseline (PMB).
Format 4 defines staffing forecasts.
Format 5 is a narrative report used to provide the required analysis of data contained in Formats 1-4 and 6.
Format 6 defines and contains the contractor’s Integrated Master Schedule (IMS).
Format 7 defines the time-phased historical & forecast cost submission.
 
Note: IPMR Format 6 has many changes to DI-MGMT-81650 in the content and format, clarifications, and added items.

Downloadable Content
AzTech can help your team with compliance of the new DI-MGMT-81861. For more details, please contact us.