Project Atlas AetherDev project hub
Atlas project production

HMH MyHRW / ThinkCentral Instructional Rostering Workflow

Send Aeries roster data into HMH instructional platforms so digital curriculum access stays aligned to live class rosters.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-24
Visibility
Internal

Purpose

Send Aeries roster data into HMH instructional platforms so digital curriculum access stays aligned to live class rosters.

Current state

The registry now separates the active instructional HMH workflow from the seasonal assessment-oriented DataManager export. Production evidence combines the enabled Integr8r `HMH` job, explicit job definition in `Config/Config.ps1`, and weekly-report references to nightly Aeries-based access updates.

Next step

Document current packaging details, schedule, owner, and whether launch is primarily Clever-mediated, direct, or mixed by campus.

Interfaces

Inputs
  • Aeries roster and identity data
  • Clever or vendor configuration
  • site or program scope rules
Outputs
  • instructional roster payloads
  • student and teacher access readiness

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Aeries remains canonical for roster and identity source data.
  • Clever or the vendor platform reflects downstream access state and should not silently become the source of truth for SIS records.

Safe handling

  • Limit vendor admin access and exported roster artifacts.
  • Treat student and teacher roster data as restricted instructional data.
  • Document scope and approval expectations before expanding to new sites or programs.

Operational notes

Reliability posture

The child workflow matters because access drift quickly becomes classroom-visible, but owner, cadence, and launch-path details are still not centralized.

Observability

  • vendor-admin checks
  • site access incidents
  • wrapper or upload runtime evidence where available

Security and privacy

Instructional roster and access data remain restricted student and staff records and should stay within approved vendor-sharing boundaries.

Dependencies

Upstream
  • Aeries data quality
  • vendor ingest expectations
  • current site or course mappings
Downstream
  • teacher and student access to the platform

Ownership

Owners

Technology Services

Users

Educational Services, school sites, Technology Services

HMH MyHRW / ThinkCentral Instructional Rostering Workflow

Operational Notes

  • This page intentionally separates instructional rostering from the distinct assessment-provisioning workflow already documented in Atlas.

Registry Alignment

  • Mapped registry entry: INT-081.
  • Registry clarified: this child workflow now has enough production-backed evidence to justify a dedicated Atlas page instead of remaining only inventory context, and Config/Config.ps1 provides direct Integr8r job evidence for the scheduled workflow.
  • Validation gaps: exact package structure, current launch path, schedule, and owner remain unresolved.