Future Modules

Here is an example of what is possible

https://www.yfiles.com/demos/showcase/largegraphaggregation

This need an investment of £10K to get the compiler and few months to create the software

Note on Microsoft Project (MSP) Usage:
MSP schedules must adhere to high-quality standards and proper planning practices.

Key Considerations:

1. Date Integrity
   MSP can be manipulated to display illogical dates. Rigorous validation is essential to ensure chronological accuracy.

2. WBS/Activity Separation
   MSP allows conflating Work Breakdown Structure (WBS) elements with actual activities. Maintain clear differentiation between deliverable-oriented WBS components and task-based activities.

3. Constraint Management
   Beware of “invisible constraints” driving activity start dates. These often stem from WBS-related dependencies rather than physical workflow links. Explicitly document such constraints rather than relying solely on predecessor relationships.

The most common way of doing a schedule, is from Excel file with a “to do” list and a Level 1 WBS.

Most of the Engineering specialist will be able to create in no time. The advances of getting this list and making a basic network diagram , in 10 sec during a meeting, can be a very powerful way of engaging them to help you with the logic, by pointing out their logic fallacies and gaps.

Template@work

Video@work

Excessive links undermine the core purpose of scheduling—to build a clear, actionable plan. Minimizing redundancy improves logic clarity, reduces system load, and builds stakeholder confidence. Here’s how redundant links cause problems:

1. Increased Schedule Complexity and Confusion

Redundant links (e.g., A → C when A → B → C exists) clutter the logic and visuals, complicating stakeholder communication.

2. Inefficient Critical Path Analysis

Extra links can distort the critical path, misrepresent float, and shift focus to non-driving activities, wasting time.

3. Unpredictable Schedule Turbulence

In large projects, delays ripple unpredictably through redundant dependencies, leading to unintended changes and loss of control.

4. Computational Inefficiency

More links mean slower recalculations. Tools like P6 and MSP must process every link—even irrelevant ones—reducing performance.

5. Risk of Errors and Miscommunication

• Hidden Dependencies: Obscure logic leads to misaligned execution.
• Documentation Gaps: Redundancies are hard to justify in audits.
• Maintenance Issues: Replanning becomes error-prone.

Best Practices to Mitigate Issues

• Logic Reviews: Use P6’s Trace Logic or plugins to spot and remove redundant links.
• Simplify Dependencies: Use milestones or buffers instead of extra links.
• Avoid Over-Linking: Focus on essential, driving relationships.
• Document Rationale: Clarify any non-standard logic in activity notes.

@work

@work 

Integrate Risk Register’s mitigation steps,  related to a risk for specific schedule activity.

NOTE: The future LogicReader v30 (June 2025)  linked to ChatGPT API to perform this operation.

@work Video

@work

@work – Video with 4K Touch screens .