Project Atlas AetherDev project hub
Atlas project production

HMH DataManager Assessment Provisioning Export

Seasonal Integr8r-driven export that sends location and staff-user files to HMH DataManager for CogAT and related assessment account provisioning.

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

Purpose

Provision or refresh HMH DataManager accounts during seasonal assessment windows without rebuilding the export logic each year.

Current state

The updated registry distinguishes this seasonal assessment provisioning workflow from the separate instructional rostering path for HMH MyHRW and ThinkCentral. Integr8r evidence shows an enabled but batch-disabled job, which strongly suggests a separately scheduled or operator-run seasonal process.

Next step

Document the annual run window, business owner, validation checklist, and recovery procedure for the next testing cycle.

Interfaces

Inputs
  • Aeries location and staff-user data for grades 3-6 testing support
Outputs
  • dated location CSV
  • dated staff-user CSV
  • vendor upload for assessment account readiness

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Not in scope.

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 the exported location and staff-user data.
  • HMH DataManager is the downstream provisioning target, not the authoring system.

Safe handling

  • Protect FTPS credentials and generated files.
  • Treat seasonal export artifacts as restricted operational data.
  • Record annual owner sign-off before the workflow is run.

Operational notes

Reliability posture

The workflow is production-relevant but seasonal. The main support risk is not core logic drift but missing annual runbook discipline, owner coverage, and downstream validation steps.

Observability

  • Integr8r runtime logs
  • generated dated CSV artifacts
  • vendor-side account readiness checks

Security and privacy

Uploads contain restricted staff and operational testing data and should remain internal, with FTPS credentials and generated files tightly controlled.

Dependencies

Upstream
  • Aeries data quality
  • testing calendar discipline
  • Integr8r job availability
Downstream
  • CogAT or related testing-account readiness

Ownership

Owners

Technology Services, Josh Barton

Users

Technology Services, assessment or testing stakeholders

HMH DataManager Assessment Provisioning Export

Operational Notes

  • This page intentionally stays separate from HMH MyHRW / ThinkCentral Instructional Rostering Workflow. The registry now makes that boundary clearer: one workflow is seasonal assessment provisioning, the other is recurring instructional access.
  • Current evidence points to an Integr8r-managed seasonal job that creates dated location and staff-user files and uploads them to HMH DataManager through an FTPS path for CogAT or related testing support.
  • The main documentation debt is the annual runbook: when it runs, who approves it, how success is validated, and what the manual fallback is if the seasonal window is at risk.

Registry Alignment

  • Mapped registry entry: INT-063.
  • Registry clarified: this is a seasonal but active assessment-platform provisioning export, not the same thing as the recurring HMH instructional roster workflow.
  • Validation gaps: annual timing, business owner, testing-program scope, and downstream validation steps still need documentation.