Purpose
Generates tab-delimited code files for SIA configuration and Data Robot support on the district automation machine.
Current state
The enabled `SIA` job description explicitly says it is a manual code pull used to provide configuration files to SIA for use with a Data Robot installed on the automation machine. The job generates seven tab-delimited text files including Attendance, Language, Ethnicity, HispanicFlag, Schools, Grade, and Status. This is strong evidence of a real supported workflow, but it behaves more like a manual vendor-support export than a fully automated recurring integration. Current registry state: Production [Validation Needed] / Active / Medium. Manual vendor-support export. Trigger / frequency: enabled but batch-disabled; the config description explicitly frames it as a manual run..
Next step
confirm whether this job is still actively used, and if so by whom and how often. Yes - confirm whether the manual export is still in active use and capture its runbook if so.
Interfaces
Inputs- Aeries SIS code and reference data.
Outputs- SIA A2A or Data Robot configuration workflow.
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesNot in scope.
Human InterfacesNot in scope.
Operational AdoptionNot in scope.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Data integrity and contracts
Source of truth rules
- Aeries SIS code and reference data. remain the authoritative upstream inputs for this workflow.
- SIA A2A or Data Robot configuration workflow. should be treated as downstream copies, recipients, or operational consumers rather than the authoring system.
Safe handling
- Protect credentials, generated files, logs, and any transient export artifacts.
- Treat student identifiers, rosters, and related records as FERPA-restricted data.
Operational notes
Reliability posture
Integr8r report details and generated files provide runtime artifacts, but there is no documented annual or monthly checklist. Failure impact: delayed vendor setup or manual data preparation burden. Manual fallback: ad hoc manual query generation..
Observability
- Integr8r report details and generated files provide runtime artifacts, but there is no documented annual or monthly checklist.
- Failure impact: delayed vendor setup or manual data preparation burden..
- Manual fallback: ad hoc manual query generation..
Security and privacy
local manual export with no automated upload shown in config. Classification: restricted student operational data. data appears more code-oriented than identity-heavy, but still requires district handling.
Dependencies
Upstream- Aeries SQL access and current vendor expectations.
Downstream- SIA A2A or Data Robot configuration workflow.
Ownership
OwnersTechnology Services, Josh Barton / Technology Services
UsersTechnology Services, attendance or data stakeholders
SIA A2A Manual Code Export
Operational Notes
- Method: Aeries SQL extract to tab-delimited text files.
- Implementation: Integr8r job key
SIA in Config/Config.ps1 with SQL under SIA/SQL/. - Trigger / frequency: enabled but batch-disabled; the config description explicitly frames it as a manual run.
- Failure impact / fallback: delayed vendor setup or manual data preparation burden. Manual fallback: ad hoc manual query generation..
- Related references:
README.md, Config/Config.ps1, SIA/SQL/.
Registry Alignment
- Mapped registry entry:
INT-068 - Registry clarified: The enabled
SIA job description explicitly says it is a manual code pull used to provide configuration files to SIA for use with a Data Robot installed on the automation machine. - Validation gaps: confirm whether this job is still actively used, and if so by whom and how often.
