Lessons Learned from Lessons Learned from NETPDTC Central Site NETPDTC Central Site

ImplementationsImplementations

23 Aug 11

Peg David, NETPDTC Project MgrDan Seward/ATC Chris Hamilton,

CNATT AIM AdminsJake Aplanalp, AIM Pgm Mgr

Ron Zinnato, AIM Lead EngineerJamie Stewart, AIM Lead ISD

OverviewOverview• NETPDC perspective• CNATT perspective• AIM program perspective

NETPDTCNETPDTC• Get users identified and account request paperwork

completed and submitted as soon as possible• Work with NETPDTC to generate implementation

documents based on posted templates• Identify working level POC as well as Trusted Agent in

Center IA organization and involve both in planning• Determine method to collect ‘baseline’ copy of all

curricula and pass those AIM export baselines to NETPDTC Sys Admin Charlie Odom

• Decide how to identify and resolve data conflicts (e.g., PPP tables, IMIs, etc.) that may occur during import into NETPCTD instance

CNATTCNATT• Establish standardized naming conventions for

agencies and learning sites prior to migration• Standardize terms between Centers and AIM

developers to minimize misinterpretations in correspondence (i.e.,: AIM Agency=CNATT Site, AIM Learning Site=CNATT MTU)

• Establish a Help SOP to ensure users receive assistance at the appropriate level within Learning Site/Center, from NETPDTC for technical issues, and from traditional AIM Help Desk for appropriate issues

CNATTCNATT(contd)(contd)

• Contractors are not authorized access to AIM online – Currently all users have the ability to view all courses – presents

possible conflicts of interest and unfair advantages for future contract bids

– Addition of a 6th role for contractors requested via ACR

• AIM does not provide tools for efficient account management– CNATT has approximately 500 users that transition frequently

– AIM needs tools that would enable efficient purging of accounts Export of account list to MS Excel

Sorting columns within AIM User Admin

Generating reports grouped by agency or privilege level

AIM TeamAIM Team• Users should go through their own chain of command for

issues rather than coming directly to AIM Help Desk• Centers, NETPDTC, and AIM team need to come up with a

business process on how to handle Trouble Reports• Each center has their own requirements/approach of how

a centralized instance should be set up:– SSP wanted 3 levels of permissions

– CNATT wanted 5 (now 6) levels

– CSFE is still trying to determine what will work best for them

– As other centers come on board, they will have their own ideas – unless there's a major problem with current implementation, need to adapt to the way things are

• Get your paperwork in EARLY!

Questions?Questions?