ScheduleCleaner Version 3.6 is Released

ScheduleCleaner Version 3.6 is Released

ScheduleCleaner 3.6 introduces several powerful upgrades focused on protecting sensitive data, standardizing schedule outputs, and making it easier for distributed teams to share licenses. This release deepens control over UDFs and Activity Codes, adds flexible output file versioning, and brings a new hosted floating license model tailored for organizations with many rotating or occasional users.

Smarter control over UDFs and Activity Codes

ScheduleCleaner 3.6 expands the way you can work with User Defined Fields (UDFs) and Activity Codes by extending filters across more transformation categories.

  • Filters in the “Remove” category for UDFs and Activity Codes
    You can now apply filters when removing UDFs and Activity Codes, so you strip only what is sensitive, internal, or unnecessary while keeping the fields that matter for reporting and analysis. This makes it easier to comply with NDAs and internal data-sharing policies while still sending a schedule that “just works” for the recipient.

  • Filters in the “Mask” and “Prefix/Suffix” categories
    Filters are also available when masking or renaming UDFs and Activity Codes, so you can target specific codes or fields instead of applying global changes. This allows you to hide confidential values, anonymize specific portions of the schedule, or enforce naming standards without breaking the schedule structure or downstream reporting logic.

These enhancements give planners more flexibility when preparing versions of the same schedule for different stakeholders, such as clients, subcontractors, or internal management.

Change Output File version to match any P6 environment

Version mismatches between Primavera P6 environments are a common source of friction during schedule exchange. With ScheduleCleaner 3.6, the “Change Output File version” capability allows you to export cleaned schedules directly in the Primavera P6 schema version your recipient uses, regardless of the source file version.

This means you can remove, mask, and standardize fields and then output the result in the exact P6 version required by your client or partner in a single workflow. The result is fewer import errors, less manual conversion work, and smoother collaboration between organizations that are not on the same P6 release.

Hosted Floating license for flexible, shared usage

To better support organizations with distributed, rotating, or part‑time users, ScheduleCleaner 3.6 introduces a hosted floating license (network-based licensing). Instead of activating individual machines, a defined pool of concurrent users can “check out” licenses from a shared pool whenever they need the application.

This model helps teams maximize license utilization and reduce total licensing cost by avoiding idle seats tied to specific devices. It also simplifies deployment and management for IT and PMO teams, especially when many project participants need access to ScheduleCleaner at different times or from different locations.

Better filter behavior in other languages and quality improvements

For international teams, ScheduleCleaner 3.6 improves the behavior and reliability of Filters when using other supported interface languages. This makes the filtering workflow more consistent for users who work in localized environments.

In addition, this release resolves several client-reported issues to deliver a smoother, more stable experience in everyday use. The result is a more robust tool that better supports organizations that rely on ScheduleCleaner to remove, convert, or anonymize sensitive data from XER and XML schedules before sharing.

Why this release matters

Across all these enhancements, the focus of ScheduleCleaner 3.6 is on three main themes: better data protection, stronger standardization, and more flexible access. Teams can now more precisely control which UDFs and Activity Codes are removed or masked, ensure schedule files open cleanly in the recipient’s P6 version, and share licenses efficiently across larger organizations.

Back to blog