Software Capabilities Status

Danette Likens and Mike CoyleAIM Team

19 September 2012

Overview• Tasked and funded software enhancements• Updated software release and distribution

model• Functional gaps between traditional AIM I/II

and CPM/LO Module• LO Module Webification• New capabilities demonstrations

Future Distribution Model• Continued major numbered releases driven

through formal NMCI certification and released to users only when ready for NMCI push

OR• Central Site-based progressive release of

enhanced functionality as software is accepted by the government and needed by user community

Assumptions• All NETC domain AIM I/II/LO Module users will

do production work on the NETPDTC Central Site instances after 30 Sep 12

• Local AIM installations on NMCI PCs within the NETC domain will be minimal

• Non-NMCI PCs used for AIM-based curricula development or maintenance can be updated responsively by local IT staff (government and contractor)

Update Process• Given assumptions, all future functional enhancements

to AIM I/II/LO Module will be done as quarterly incremental updates vs. major numbered releases

• Update packaging will be determined and managed by the AIM Program Manager and Lead Engineer, as coordinated with NETC N74 and FRB

• NETPDTC Central Site System Admins will install updates as released by AIM Pgm Office

• AIM Lead Engineer will post updates and notify non-Central Site users (government or contractor) for responsive download and installation by local IT staff

Outliers• Remaining local NMCI AIM I/II/LO Module instances

(NETC and non-NETC) will still have to go through software push by NMCI, based on formal certification testing

• TRANET classrooms generally lag latest release: should we have a NETPDTC Citrix training instance with the implication of restricting training to CAC holders

• Likely result of this new release process: local NMCI users will lag (possibly far) behind capability of AIM I/II/LO Module users on NETPDTC Central Site or local non-NMCI instances

Mitigating Actions• More aggressive action by NMCI to test and

push annual or semi-annual updates can shorten the lag between Central Site and local NMCI instances

• Alternatives:‒ Identify and bring remaining NMCI users into

central site‒ Wait until CPM & LO Module are merged into 1

web application

Full OCCSTDS Support in CPM• NAVMAC and NETC N7 working closely to transition

full support for OCCSTDS development, maintenance, and publication into OCCSTDS Tab in CPM

• Leverage ongoing functional prototype in work at NAVMAC to define complete business process

• Extend that functionality into CPM OCCSTDS tab (added in CPM Rel 5.0: ongoing functional enhancements for data import into CPM and for OCCSTDS-to-JDTA tab data mapping for the end-to-end NETC N7 learning content business process)

• Schedule and resources TBD

LO Module Webification Phasing• Phase 1: TO 0005, Task 3.2.3.g Final Design Document (FDD) –

fully funded under TO 0005• Phase 2: Update Phase 1 release of ‘Webified’ LO Module to

support desktop client LO Module Release 5.0 functionality as tasked under TO 0011 – partially funded under TO 0011; may required additional resources to provide all Release 5.0 comparable functionality

• Phase 3: Update Phase 2 release of ‘Webified’ LO Module to support all desktop client LO Module functionality tasked under TO 0011 and TO 0012 – TBD K$ under future TO

• Phase 4: Update Phase 3 release of ‘Webified’ LO Module support final desktop client LO Module functionality implemented prior to ‘freeze’ of desktop client enhancements – TBD K$ under future TO

LO Module Webification Schedule

Demonstrations(Thurs am)

• AIM II CTTL Import to CPM for pre-JDTA

• LO Module Webification Prototype 3• CPM Existing Interventions linking• Front End Analysis Prototype

Questions?

Backup Slides