Authoring Instructional Materials (AIM)
AIM and CeTARS – Notional Course of Action
Courses of Action (COA)
COA #1: eTRMS as a Stand Alone POR
eTRMS deployed as an “As-Is” Stand-Alone application solution where all data, regardless of its type, is a manual input.
Personnel (P), Equipment (E), and Space (S) data into eTRMS will be accomplished via manual input by Learning Centers and
Learning Sites. No automated data exchanges from or to CeTARS or other data sources.
COA #2: CeTARS Interfaces into eTRMS – Two Systems Maintained
CeTARS as the Authoritative Data Source (ADS) for Personnel (P); Equipment (E); Spaces (S); and the creation of the
Execution Schedule (C).
eTRMS as the Execution Scheduler and Resource Manager (eTRMS).
eTRMS will remain as a Stand-alone Program of Record (POR) maintaining independent ATO, hardware and software
requirements but receiving P/E/S authoritative data and availability status from CeTARS via to be determined data
COA #3: Full Integration of eTRMS into CeTARS
Full integration of all eTRMS functionality and capabilities into the CeTARS application and database schema.
CeTARS will become the Authoritative Data Source (ADS) for P/E/S/C.
eTRMS will remain as a Stand-alone Program of Record (POR) for all existing users in an “As-Is” state with no new users
added until full integration and transfer of functionality to CeTARS has been completed.
CMS Working Group: Database differences between CPM and CeTARS indicate a deep
dive into the requirements of CeTARS and CPM for the Course Master Schedule (CMS).
As the data density of CPM increases, current CMS Web Service from AIM II will need to be revisited for
inclusion or revision of data elements from CPM.
As Capacity Modeling requirements are identified for inclusion in the Execution Scheduler, the CMS will
need to reflect those capacity requirements as possible scheduling tags.
RRL Working Group: Currently, CNATT uses the RRL as a component of eTEM. When the
final COA is selected, the RRL will become, at some point, a major component in the
Execution Scheduler and Resource Manager.
An AIM-CeTARS RRL interface will be required in order to provide scheduling components for RRL TE.
The RRL will be matched with the current inventory to produce TE availability status inputs into the
selected Execution Scheduler.
AIM-CPM does not currently have the programming capability to designate the final approved RRL as
“Approved”: versioning will need to be incorporated through programming of AIM.
Workgroup Team Make-up:
CMS Working Group to capture new CMS process with AIM-CPM and CeTARS and reflect Capacity
RRL Working Group to capture new RRL process with AIM-CPM and CeTARS.