Deltek Acumen 8.6 Online Help

Using the Help Search
Using the Help Search
  • Phrase:Returns all topics that contain the exact phrase in the search criteria. Use quotation marks around the phrase.
    Ex."system administration"
  • And:Returns all topics that contain all the words in the search criteria, in any combination. Insert a plus sign between all words in the search criteria.
    Ex.system + administration
  • Or:Returns all topics with any combination of words in the search criteria. This is the default.
    Ex.system administration
For more information:Searching Online Help

S2 // Logic Tab

The logic analysis view is used to run detailed logic integrity checks against the schedule(s).

In addition to using Acumen Fuse to perform diagnostic checks on schedule attributes, Fuse can evaluate relationships between activities and perform circular logic checks.

The logic analysis provides multiple advanced logic checks on a project (or multiple projects) including:
  • Analysis of logic types
  • Positive and negative lags (leads): Negative lags (or leads) cause concern within a schedule as they can lead to reverse logic. Likewise, positive lags often result in detail being lost within a schedule during statusing / execution.
  • Redundant logic: A redundant link occurs when, in addition to the link in question, there is a more detailed logic link between the same two activities. For example, a link from Activity A to activity C is made redundant by an existing link from Activity A to Activity B and another one from Activity B to Activity C.
  • Circular logic: Circular links often occur in multi-project schedules. For example, a circular link would be a link from A to B and then another link from B to A. Circular logic analysis checks for paths of activities that loop back on themselves. This is a big concern in multi-project environments (for example, multiple Primavera files that reference each other) where circular logic checks can otherwise go undetected.
  • Open ends: Open ends analysis checks for any activities that are missing either predecessors or successors, causing the activity to be "open ended."
  • Relationships on summaries
  • Out of sequence status updates: This analysis checks for clashes between logic progress/status updates. Out of sequence errors occur between activities when the successor activity status contradicts the logic with its predecessor. For example, a successor activity starting before its FS predecessor has started
  • Reverse logic: Reverse logic errors occur when the start of a successor activity starts before the start of the predecessor. Typically caused by negative lags (leads), these reverse logic errors should be avoided at all costs.
  • Dangling activities (Open Start and Open Finish): Dangling activities occur as a result of a FF or SF predecessor link (open start) or SS or SF successor link (open finish) and not when there are any missing predecessors or successors. The successor ends up with an open start and the predecessor ends up with an open finish.
  • Logic Sensitivity™: You can identify how potential delays affect key activities or milestones later in the project