Recommendation
The core issue is that Aras Innovator’s Project Management module stores all datetime values in UTC internally, and the standard Gantt chart rendering in 12.0 does not automatically localize display times per user. The recommended approach combines server-side user locale configuration, a client-side presentation layer fix, and a dependency modeling discipline.
1. Enforce time zone at the User item level, not just preferences.
Navigate to Administration → Users and confirm each user’s time_zone property is explicitly set (e.g., America/New_York, Europe/Berlin, Asia/Tokyo). The Gantt widget reads this property at render time — if it is null, it falls back to server time zone, which is likely UTC. Verify in your version whether 12.0 SP levels affect this fallback behavior; patch levels from SP4+ reportedly improved consistency here.
2. Apply a Method-based time zone offset on the Gantt datasource query.
Rather than relying on the presentation layer alone, offset datetime values before they reach the chart. Override the GetProjectItems server Method to apply a UTC offset based on the requesting user’s time_zone property. This ensures the Gantt receives pre-adjusted values.
// Simplified AML fragment within a server-side Method
var tz = this.getPropertyValue("time_zone"); // from current user item
// Apply offset logic before returning project task datetimes
3. Model cross-site dependencies with explicit lag time.
For EST→JST handoffs, use Finish-to-Start with lag equal to the non-overlapping gap between work calendars. Define separate Work Calendars per site under Project → Calendars, assign tasks to site-specific calendars, and let the scheduler calculate realistic start windows. This eliminates the phantom overlap problem.
4. Create role-specific Gantt views using saved searches.
Use ItemTypes → saved searches to scope each site’s default view to their calendar and filter out off-shift dependencies from the primary display. Teams then see only actionable tasks without cross-timezone noise cluttering standups.
Common Mistakes
- Setting time zone in Personal Preferences UI only — this does not reliably propagate to the Gantt widget in 12.0.
- Using a single global Work Calendar — this is the primary cause of phantom overlapping dependency windows.
- Storing task notes with local times as freetext — creates documentation drift when engineers in different regions interpret the same note differently.
- Customizing the Gantt presentation layer via XSLT without adjusting the underlying AML query — offset must happen at the data layer, not the display layer.
Version-Specific Note
Aras 12.0 Gantt functionality is built on a third-party charting library that has limited native time zone awareness — verify in your version whether any applied service packs include Gantt timezone patches before investing in Method-level overrides. In Aras 14+ (verify in your version), the rearchitected Project Management module provides improved locale-aware scheduling natively, which may reduce the need for custom Method overrides described above.
This draft is based on general Aras Innovator knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.