# Presentation: 536474

## USDALMS Overview MeetingOctober 27, 2003

## Project Team Introductions
Project Overview & Objectives
Implementation Methodology
Project Organization
Project Timelines
LMS at a Glance
Wrap Up

- Project Overview & Objectives
- Implementation Methodology
- Project Organization
- Project Timelines
- LMS at a Glance
- Wrap Up

**Agenda**

**Notes:**
The purpose of this meeting is to launch the Plateau 4 Learning Management System implementation project at the Department of Transportation (DOT). 

The project objectives, scope, and success factors will be reviewed and the overall project processes and controls will be defined and agreed upon by the team members. The project organization, including roles and responsibilities will be discussed and agreed upon. The Plateau ENABLE Implementation Methodology will be presented, and a preliminary discussion of the existing learning processes will take place. The output of this session will provide the basis for the detailed project plan document and Microsoft Project work plan. 

## Project Team Introductions

- Plateau & GPE Learning Team
- Shelly Heiden – Executive Sponsor - Plateau
- Bill Finegan – Project Director – GPE Learning
- Chris Cook – Engagement Manager - Plateau
- Jennifer Milder – Project Manager – Plateau
- TBD – Business Analyst - Plateau
- Manoli Salpeas – Implementation Support – GPE Learning
- TBD – Technical Consultant - Plateau
- Leslie Nicholson – Trainer - Plateau

**Notes:**
Us – PM day to day contact, status report, managing budget, timeline, issue resolution.  
Ron – subject matter expert help map business process to the application.
Dave Mentall -  BA – Solution Design
Subject matter expertise, participation in workshops

## Core Implementation Team

**Notes:**
Identify necessary core team skill sets for a successful implementation
Skill include:
Project mgmt abilities
Technical skills
Training skills

TOPICS:
Roles and responsibilities

## Project Overview & Objectives

**Objective**
- To deliver a comprehensive learning management system to the USDA
**Critical Success Factors: **
- Increased access to training for all employees through web-based courseware.
- An increase in the efficiency of the training system, boosting productivity
- An increase in the utilization of e-learning for USDA courses.
- Reduced costs associated with licenses for current online course delivery.
- Increase in timely, accurate reporting.
- Enable change management

## Implementation Scope

**Phase One Implementation**
**Step 1: Design (10/2003 – 12/2003) **
- Kickoff – 10/27/2003
- Project planning
- Design workshops – 11/17-11/21 & early 12/2003
- Basic Configuration
- Solution Design Document
- Development licenses for 90-day period
- Step 2:  Modify & Test  (January 2004 – March 2004)
- Step 3:  Phase One Rollout – March 2004

## Implementation Scope

- Rollout to approximately ***10,000*** students
- Major functionality - courseware delivery, student registration, student training plans, online exams, and management of Instructor-led and web-based training
- System and application configuration (to include integration of content/online exams)
- One-way batch Interface from (I-CAMS PeopleSoft 8.0) for student demographic information
- Requirements definition for existing USDA LMS’s, USDA Portal, eAuthentication, and procurement system (IAS)
- Data migration from I-CAMS (PeopleSoft 8.0) and NFC’s TRAI for training history of students
- UI branding customizations
- Hosting services

**Implementation Scope**

## Review Implementation Methodology

**A structured implementation methodology tailored to meet the customer’s project requirements**

**Notes:**
In this next section we will be introducing the ENABLE methodology.  
Objectives:
Identify purpose of methodology
Identify each phase within the methodology
Define milestones and tollgates 
Explain purpose of status reports
Classify key deliverables with each phase 

## Benefits...

- Apply Plateau expertise while your application abilities increase
- Leverage Plateau implementation experience in training, developing interfaces, and migrating data
- Apply Plateau tools and guides to facilitate configuration discovery and manage a project
- Work with Plateau leadership to meet your needs and your application roll-out

**Notes:**
What is the purpose/benefits of the Methodology?

## Plateau Global Services Organization

## Professional Services

**Mission Statement: **
- Help USDA maximize their return on investment by implementing best practices in areas of business processes, application configuration, and systems integration.
- Created in January 2001 to extend the Value Proposition of the LMS.
- Blend of Business, Technical, Web, and Project Management Expertise.

## Customer Support

**CSO**
**Services Provided by Plateau Support**
- Product Support
- Communications
- Media Fulfillment
- Customer Surveys
- Product Testing Support
- General Help

## Customer Support

**CSO**
**Product Support **
- Plateau provides a Help Desk to provide technical support services with regard to operation of software. The role of the Help Desk is to respond to your calls about the operation of the application and to include problems you may be encountering while using Plateau software.
- The Plateau CSO Help Desk will respond to *customer*  (employees, clients, partner, prospects) inquiries from a variety of means including telephone, email or FAX.  The Help Desk responds to questions about problems with operations of the application.  Regular business hours are 8 AM to 8 PM Eastern.

## Implementation Methodology

_**ENABLE**_
**E**ngagement Initiation
**N**ormalize Functionality
**A**pplication Configuration
**B**asic Modifications
**L**earning Landscape
**E**nterprise Roll-Out

## ENABLE Phases

- Kick-Off

- Testing
- Production

- Requirements
- Solution Design

- Data Integrations
- Data Migrations
- Look & Feel
- Online Courses

**E**ngagement Initiation

**N**ormalize Functionality

**B**asic Modifications

**E**nterprise Roll-Out

**L**earning Interventions

- Configuration
- Prototype

**A**pplication Configuration

**Notes:**
Major events within each phase (refer to the ENABLE swim lane in handout)

## Workshops

**Functional**
- Organized by LMS Module (i.e. System Administration, Student Management, etc.)
- Guidelines
- Work Together
- Make Decisions
- Keep Customer/Team Open Minded
- Respect Opinions
- Champion the Project
- Build Consensus
- Gap Analysis – Describes functionality gaps and how these will be addressed (i.e. workaround, process change, etc.)
- Student Management Workshop Example

**Notes:**
Summarize primary purpose of conducting application configuration workshops
Define possible naming convention rules and why they are important

TOPICS:
Workshop discussion – differentiate b/w function and technical workshops 
Define primary purpose of each

## Workshop Topics

**Functional**
- System Administration/Global settings
- Domains and Organizations (building an organizational model for data segmentation and security)
-  Role Management and Workflows (determining administrative access and functions)
- Student Management
- Learning Management and Scheduling (how are training components organized and delivered)
- Online Content and Exams
- Commerce and Reports
- User Interface look and feel

## Workshops

**Technical**
- Scope dictates technical workshop
- Common technical workshops include:
- Data Migration
- HRIS / System Integration
- Content Integration
- Detailed technical requirements and design incorporated into Solution Design Document
**Content Integration**
- Review Content Integration Guide

**Notes:**
Summarize primary purpose of conducting technical configuration workshops

TOPICS:
Workshop discussion – differentiate b/w function and technical workshops 
Define primary purpose

## Workshop Topics

**Data Migration**
**Key Tasks**
- Script development
- Business Rule Adjustment
- Testing
**System Integration**
**Key Tasks**
- Clearly documented requirements definition and design
**API’s**
- Components of an HRIS Integration
- Real-time vs. Batch, One-way vs. Two-way
- Entity-mapping
- Delivery (EJB calls vs. MQ vs. FTP vs. DB)
- Format: CSV vs. XML vs. External tables
**Content Integration**
**Key Tasks**
- Design communication (AICC/SCORM) needed for selected content

**Notes:**
Identify possible data migration tool

## Tollgate Checkpoints

**  ****Periodic Reviews:**
- Resolve Issues
- Review Status
- Provide Assistance

## Review Project Organization

**Team Communication Plan**
- Team Meetings
- Status Reports
**Issue Escalation**
**Scope Change Control**
**Roles & Responsibilities **

## Project Timeline

**Oct.**

**Dec.**

**Nov.**

**Solution Design Document Delivered**

**Application Configuration/**
**Integrations and Migrations **

**Initial Testing Completed**

**Launch!!!**

**Readiness**
**Review**

**Phase 0 & 1 Implementation**

**Project Kickoff and  Application Training**

**Jan.**

**Mar.**

**Feb.**

**Functional Workshops**

**Technical Workshops**

## LMS at a Glance

## Slide 24

## Slide 25

## Slide 26

## Slide 27

## Slide 28

## Slide 29

## Slide 30

## Slide 31

## Slide 32

## Next Steps

**Project Team Training**
**Functional and Technical Workshops**
- Understand Current Training Processes
- Your Challenges
- Define and Create LMS Solution and Configuration
- Define Migrations & Interfaces
**Create and Review Solution Design**

## Summary

- Review
- Wrap Up