Consolidated Enablers Overview Presentation (1.31.03)

U.S. Department of AgricultureeGovernment Program

eGovernment Program

Enablers InitiativesExecutive Summary

January 2003

2

U.S. Department of Agriculture eGovernment Program

Background and Context

eAuthentication Overview

eDeployment Overview

eLearning Overview

Next Steps

Agenda

3


Overview of the Enablers InitiativesThe Enablers originate from seven of the enabling initiatives outlined in USDA’s eGovernment Strategic Plan.

Select PhaseBusiness Case Documents

eAuthenticationBusiness Case

Documents

eDeploymentBusiness Case

Documents

eLearningBusiness Case

Documents

USDA eGov Strategic Plan – Enabling Smart Choices

eAuthentication

Content Management

Document Management

Data Management

Web Presence

Portal Services

eLearning

Pre-select PhaseBusiness Cases

Conceptual

eAuthenticationBusiness Case

eLearningBusiness Case

Web Content Management Document

Management

DataManagement

PortalServices

WebPresence

4


The creation of enterprise services does not only mean the purchase and implementation of technologies, but a holistic approach involving people, operational processes, technology, and an underlying delivery methodology

USDA is creating a suite of “enterprise services” to support its strategic initiatives, enable agency and enterprise program delivery, leverage investments, and save costs

Suite of Enterprise Services

Enterprise-level services allow USDA to:

• Use its resources to focus on program delivery instead of technical infrastructure

• Leverage its current and future investments and realize significant cost avoidance

• Facilitate the sharing of best practices through collaborative design, development, and operations

• Implement standard technology and development methodology across the Department

• Decrease implementation times by leveraging best practices and utilizing a skilled central team

• Communicate as “one voice” to business partners, technology vendors, and employees

StandardMethodology

Agency programsand strategic initiatives

EnterpriseServices

People

TechnologyOperationalProcesses

5


Enablers Approach

We are taking the following approach in developing these enterprise services:

Marketing and Communications

Program Management Approach (Enterprise Solutions Center)

2Q02 3Q02 4Q02 1Q03 2Q03 3Q03 4Q03 1Q04

Develop eGovernment Strategic Plan

• Strategic direction• 24 Strategic initiatives

• Enabling initiatives• Strategic initiatives

Pre-Select Business Cases

• Initial vision• Cost/benefit

analysis• Initial impact

analysis

Implementation and Investment Planning

• Functional & Technical requirements

• Program management approach

• Comprehensive technical architecture

• Implementation Plans• Cost/benefit analysis• Impact analysis

Select-level Business Cases

Change Management Planning and Implementation

Decision to plan and implement Enabling initiatives

Vendor Assessment & Detailed Planning

• Secure hosting SLA’s

• Determine early adopters

• Issue vendor RFP’s

• Conduct formal product selection

Signed Contracts & Procurement

Installation & Testing• Set up hardware• Install software• Perform necessary custom

development (integration)• System test

eAuthentication Services• Publish guide for application developers• Build out service

Early Adopter Development / Strategic Initiative Development

Rollout of version 1 of eDeployment capabilities

Development of version X of eDeployment capabilities

Project Management

(ongoing)

(ongoing)

(Basic services available)

NOW

6


Agency Roll-OutOnce the enterprise eGovernment components have been deployed, agencies can roll-out these capabilities to their users under a “Subscriber Agency Model” or a “Hosting Agency Model”

Subscriber Agency Model

Under this model agencies would use the shared, enterprise instance of the eGovernment capabilities

Each agency would be provided with its own secure, virtual space on the enterprise solution which will contain:

• Secure content storage area• User and administrator accounts• Workflows specific to the agency’s

business processes• Content authoring, workflow authoring,

user and application administration capabilities

This model is cost effective to the agency and best leverages enterprise and agency resources

eGovernment team would provide rollout support

Hosting Agency Model

The Hosting Agency Model would allow an agency to host and use its own instance of the enterprise eGovernment solutions

This model is designed for agencies which have very unique business needs that require a high amount of customization and integration of the eGovernment solutions

Under the Hosting Model, an agency would be provided with:

• Copies of select eGovernment components to host on agency servers

• Strict guidelines on customization and integration of eGovernment components to ensure compatibility with future eGovernment releases

• Development support to install, customize and integrate eGovernment components

This model would be more expensive for an agency to roll-out and maintain

7


Technical Architecture

A scalable technical architecture must be defined as part of the enterprise services vision. Defining the technical architecture had to meet the following goals: Support eGovernment initiatives throughout the Enterprise

• Enterprise-wide initiatives• Cross-agency strategic initiatives• Single-agency initiatives• Federal Government initiatives

Define a scalable and robust architecture that would integrate and leverage current capabilities

Complement current initiatives already underway including efforts around defining our Enterprise Architecture and expanding our telecommunication capabilities

• Support initiatives that support common business processes• Help define the technical layer of the enterprise architecture

The definition of a technical architecture does NOT:• Replace existing business-specific agency applications• Force agency applications to be hosted in a centralized location• Take control of business applications from agencies

8


Non-Web Centric

Application

Web Presence / User Interface (Standards)

StrategicInitiative

(e.g. eLoans)

Agency Applications DigiTop

eAut

hent

icat

ion

(Sin

gle

sign

-on,

Dig

ital S

igna

ture

s)

EnterpriseWeb

Content

EnterpriseDocumentContent

Shared Database

Agency Database

Content Aggregation/Application Integration (enterprise search)

ExternalContentSource

Web Content Management

Document/Records

Management

Data Management Program (Standards,Policies,Services)

eLearning

Presentation

Business Logic/Application

Data

Citizens

Content Distribution

Support CapabilityNon eGov Component

Enabler Initiative Component

Strategic Initiative Component

Standards & Policies

Employees Business PartnersCustomers

Portal(s)

USDA Strategic PlanEnterprise Architecture

Inter-agencyApplications

Conceptual Architecture OverviewData/Content

Department Metadata and Taxonomy Standards

9


Logical Architecture Overview

ContentManagement

Portal ServerWeb Server

Web ServerApplication Server

Database

Web Server

Business Partner

Database

Citizen

Employee

Agency II Application

Agency I Application

Enterprise Portal Application

Hypertext Link

Content aggregation/Indexing server

EAI Server

Firewall

Document/RecordsManagement

Legacy Systems

Intranet

Deploy Content

Index, Search, Integrate

Index

Index

App Integration

Access

Index, Search

Existing Legacy Integration

App Integration

User name, Pass

authenticate

eLearning

User Info Token

Central Data

Repositories

eAuthentication

Web Server

App Integration

Index

10





eLearning Overview

Next Steps

Agenda

11


What is eAuthentication?

eAuthentication verifies a user’s identity when accessing online services…

USDA’s eAuthentication solution will consist of a set of products and services to authenticate the identity of persons accessing USDA’s online offerings.

USDA’s eAuthentication approach will include the use of:

• Electronic signatures (eSignatures) which allow a user to “sign” an online transaction. An eSignature signals a person’s consent, approval, or acknowledgement. An electronic signature can take many forms, such as a name typed at the end of an email message, a digitized image of a handwritten signature, or even a secret code or PIN that identifies the sender to the recipient; and

• Digital signatures, a more advanced electronic signature, that support greater levels of confidentiality, integrity, and non-repudiation.

12


eAuthentication - Business Requirements

Provide a suite of products and services for Agencies to use across the Enterprise. Existing solutions will be leveraged to the extent possible/practicable and external solutions will be used to complete the suite;

Leverage security best practices. A consolidated approach can ensure that each Agency is drawing upon the best authentication solutions to ensure proof of identify and to protect the confidentiality and sensitivity of data in the applications;

Integrate USDA resources with other Government resources as part of the Presidential Initiative;

Improve the user’s experience by not requiring multiple authentication credentials, such as multiple passwords or certificates;

Promote both interoperability and enhanced security across USDA applications; and

Reduce the cost associated with the development and maintenance of multiple sets of authentication solutions.

13


Existing USDA Services That May be Leveraged

The NFC has developed a PKI to provide secure e-commerce over the Internet and satisfy Agency requirements for strong authentication.

Certified by the Federal Bridge Authority.

Supports Government to Government transactions only.

Three county-based Agencies, FSA, NRCS, and RD, have implemented WebCAAF.

WebCAAF currently provides authentication services to 40,000 employees and 2,000 farmers.

Several web farms provide both a network and administrative infrastructure, and a security architecture that authenticates users.

Supports Government to Citizen and Government to Business transactions.

Only OCIO-approved Authentication solutions will be leveraged. Opportunities include:

The Agricultural Marketing Service’s Livestock Mandatory Price Reporting (MPR)

Web-enabled, Government to Business database management system. Using PKI security technology, the system electronically accepts the data from the

livestock industry, archives the data, validates and analyzes the data, produces and stores aggregated data, and creates industry reports for distribution to the public via the USDA's web site.

Web Central Authentication and Authorization Facility (WebCAAF)

National Finance Center’s Public Key Infrastructure

14


Alternative 1 - Status Quo Approach• USDA Agencies individually select approved authentication solutions. • Advantage of this approach is early availability, but the disadvantages are high

implementation and maintenance costs of disparate authentication solutions, possible lack of interoperability, and multiple sets of customer credentials.

Alternative 2 - Combination of Alternative 1 and Alternative 3• Offers individual Agencies flexibility to select their own solutions, where special business

needs must be addressed, but uses a consolidated approach for most authentication solutions.

• Disadvantages are possible lack of interoperability and multiple sets of customer credentials. Alternative 3 - Managed eAuthentication Approach - Recommended

• Offers multiple products and services tailored to fit Agency needs.• Requires some application reengineering to ensure current authentication mechanisms are

supported. • Offers economy of scale and cost reductions since resources are Enterprise-wide. • Allows for re-usability of resources as new applications are developed. • Intends to leverage approved USDA Authentication solutions.• Improves ability to share credentials across USDA and with its Government and business

partners. • Eases integration with the Presidential Initiative for eAuthentication.

eAuthentication - Alternatives AnalyzedThree implementation alternatives were considered for eAuthentication.

15


eAuthentication - Costs and Benefit AnalysisThe consolidated eAuthentication solution offers several quantitative benefits and a 192% ROI.

• Enables USDA to meet GPEA compliance for online transactions with electronic signatures by the date of October 2003.

• Reduces management/administration costs by decreasing the amount of time spent managing usernames, passwords, etc.

• Increases customer usability due to consistent authentication standards across USDA applications, thus enabling customers to use one form of Authentication across many USDA, Government, and business partner applications.

• Reduces maintenance of authentication systems by utilizing a central authentication mechanism.

Cost Type FY 2003 FY 2004 FY 2005 FY 2006 FY 2007 Annual Benefit (AB) $5,564,000 $14,790,000 $20,865,000 $24,424,000 $25,848,000 Annual Costs (AC) $7,801,000 $4,589,000 $7,738,000 $5,783,000 $4,788,000 Discount Factor (DF) 1.0000 0.9728 0.9463 0.9205 0.8954 Discounted Benefit (DB) ABxDF $5,564,000 $14,388,000 $19,744,000 $22,482,000 $23,145,000 Discounted Cost (DC) ACxDF $7,801,000 $4,464,000 $7,322,000 $5,323,000 $4,287,000 Discounted Net (DN) DB-DC $(2,237,000) $9,923,000 $12,421,000 $17,159,000 $18,857,000 Benefit Cost Ratio (BCR) DB/DC 2.92 Net Present Value $56,124,000 Payback Period (Years) 1 Year IRR 485% Modified IRR 45% ROI 192%

16



eAuthentication offers common authentication services to applications within USDAKEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION

COMPONENT VALUE PROPOSITION

The following types of authentication may be created or leveraged over time, as requirements dictate:

• PKI Class 4 (High) Certificate• Biometric• PKI Class 3 (Medium) Certificate• Password• PKI Class 2 (Basic) Certificate

Using these authentication techniques, the Department will be able to offer a comprehensive authentication service:

• Corroborative Authentication Mechanisms– Used in conjunction with each other

• Additive Authentication Mechanisms– Independent use of same type of authentication

• Strong Authentication mechanisms– Independent use of different types of authentication

Provide authentication for electronic services

Interaction with Agency/Enterprise Web Based applications to provide authentication

Agency/Department Legacy Applications interface via a web based proxy

Agency applications to support GPEA

Critical capability in allowing stakeholders to conduct secure transactions with agencies. Legislative mandate states transactions must be conducted online - major cost avoidance in doing enterprise solution

• Synchronous Token• Asynchronous Token• Cognitive Password• PIN• PKI Class 1 (Rudimentary)

17


Logical Architecture Detail: eAuthentication

The following is the detailed logical architecture as it relates to eAuthentication:

Authenticator CredentialManager

AuthenticationData Store(s)

CredentialStore

FederalBridge

CA

Audit Log/Reporting

Store

Registration ReportGenerator

Audit MonitorIDS Monitor

ManagementStation

Data Enclave

Management EnclaveRegistration &Reporting DMZ

eAuthenticationDMZ

Certification DMZ

USDA CertificateStore

USDA WAN

USDAInternal

Applications

USDA WebPresence

Customers& BusinessPartners

Employees

Citizens

USDA WebApplications

eGovPortal

IDS

IDS

IDS

IDS

Document Management


Portal

CA

18





eLearning Overview

Next Steps

Agenda

19


What is eDeployment?

Web Content Management• A Web Content Management solution will aid the creation, review, delivery, and maintenance of

agency-defined information. Document Management

• A Document Management solution will enable the sharing and managing of documents and other electronic assets across USDA (according to records retention schedules.)

Web Presence • Web Presence will provide standards and guidelines to improve the “look and feel” and usability of

Web pages and Web-based applications across USDA. Portal Services

• Portals will provide customers, public and private organizations, and USDA employees with integrated access to USDA information and services.

eDeployment is a fusion of multiple enabling capabilities that will support delivery of USDA information and services.

20


Conceptual Architecture components continued:

Central Data Repositories • The Data Management component represents standards, policies and services around

database/data design and implementation. These standards will reduce data redundancy, improve data quality, promote interoperability and data reuse

Content Aggregation/Application Integration• The Content Aggregation/Application Integration component provides integration of

content and application services for use by portals and other agency and cross agency applications

• A centralized index will allow ubiquitous searching of distributed, heterogeneous content/data repositories

Content Distribution• The Content Distribution component will facilitate the deployment of content to

distributed servers for optimal delivery of content. Distribution of content will reduce application response time, ultimately enhancing the user experience

What is eDeployment?

21


eDeployment - Business RequirementsKey requirements identified by Agencies include:

Provide an automated workflow capability to mirror the creation, review, publishing, and archival process that is currently performed manually.

Enforce the inclusion of standard metadata, headers, footers, etc. for

a file or online content. Enforcing these standards enables information to be organized, re-used, and located.

Provide a comprehensive information architecture (organization and classification of information) to improve access to information.

Provide fast and accurate information retrieval capabilities.

Provide standards and guidelines that ensure a consistent “look and feel” and navigational structure in USDA’s Web pages and Web-based applications.

Provide the ability to integrate with existing legacy systems.

22


eDeployment - Current EnvironmentExisting capabilities vary by Agency and often reflect duplicative and redundant business and technical processes. Most notably, there is a lack of consistency and information sharing across the enterprise.

Some Agencies are currently evaluating individual Web Content Management, Document Management, and Data Management solutions as well as separate Web Presence and Portal initiatives to meet their distinct needs.

Workflow processes are conducted manually and there is no means to drive content and documents throughout their lifecycle, from creation to maintenance to archiving.

Agency documents are primarily static, unstructured content that is not interactive with Web applications, databases, and multiple Web delivery mechanisms.

Agencies have dissimilar technical architectures, which pose a challenge to interoperability.

“Stove-pipe" delivery systems that currently exist are organization bound; content creators from subject matter expertise at any level are not able to contribute to the content that will be delivered to users.

23


Maintain the existing environment – “Status Quo”• Grants the most flexibility by allowing Agencies to choose their own eDeployment solution

and eliminates the need to work through culture barriers; and• USDA Agencies spend millions in duplicative monies to design, build, deploy, and operate

their own solutions and do not benefit from economies of scale pricing. Integrated enterprise solutions in a distributed environment -

Recommended• Delivers enterprise-wide services from multiple hosting facilities (such as NITC, other USDA

hosting facilities, and potential third-party hosting centers); • Supports reuse of existing USDA hardware, software, network, and personnel resources; and• Provides economies of scale for the purchase of software licenses; • Reduces the complexity of system implementation; and• Provides the greatest processing power to ensure optimal response time for users.

Integrated enterprise solutions in a centralized environment• Delivers enterprise-wide services from a centralized hosting facility;• Provides an effective option if audiences are concentrated in a small geographic region and

external systems that need to be integrated are few and centrally located; and• Provides the same benefits as distributed environment, but the processing power would not

be as great and integration would be more complex.

eDeployment - Alternatives AnalyzedThree implementation alternatives were considered for eDeployment.

24


eDeployment - Cost and Benefit AnalysisThe distributed eDeployment solution offers several quantitative benefits and a 103% ROI.

* Assumptions are documented in the business case document

Cost Type (in $000s) FY 2003 FY 2004 FY 2005 FY 2006 FY 2007 Annual Benefit (AB) $13,018,885 $29,456,829 $61,777,507 $111,151,328 $170,818,569 Annual Costs (AC) $37,525,318 $32,901,635 $39,131,268 $40,357,016 $34,657,226 Discount Factor (DF) 1.0000 0.9728 0.9463 0.9205 0.8954 Discounted Benefit (DB) ABxDF $13,018,885 $28,654,503 $58,458,027 $102,314,059 $152,954,628 Discounted Cost (DC) ACxDF $37,525,318 $32,005,482 $37,028,634 $37,148,365 $31,032,827 Discounted Net (DN) DB-DC $(24,506,434) $(3,350,979) $21,429,392 $65,165,694 $121,921,800 Benefit Cost Ratio (BCR) DB/DC 2.03 Net Present Value $180,659,474 Payback Period 3 IRR 92% Modified IRR 26% ROI 103%

• Enterprise-wide aggregation, management, and storage of content increase the amount of

higher-quality information that is available to citizens.• The acquisition of highly extensible and scalable enterprise-wide solutions decreases the

number of redundant purchases across USDA and provides for economies of scale.• Reduces paper costs related to the purchasing, printing, storing, and disposal of paper

assets by accessing, storing, and managing content and documents electronically. • Standardized business and workflow processes instill greater accountability and improve

access to more current, accurate, relevant, and organized products, services, information, and data.

25


Portal Services Overview

A portal integrates application systems, knowledge systems, and content in a centralized place for a targeted audience

KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION


Flexible feature set based on the type of portal being created:

• Internal and External Horizontal portals span a large range of information topics or large range of services

• Internal and External Vertical portals cover one or multiple topic areas very deeply or are integrated with specific applications

• Internal workgroup portals focus on aggregating internal services and information and often house collaboration capabilities

Legacy system integration Personalization of user experience

• Personalization of the user interface• Personalization of content delivery / application

functionality• Role-based personalization

Integration with eAuthentication solutions• Single/enterprise sign-on

Aggregate existing agency and enterprise applications and content

Integrate with existing legacy systems to provide web-based user experience, access to legacy system business logic and data

Work tightly with web content management solution to drive standard user-interface design and content automation

eAuthentication

Vital to the aggregation of content across agencies: helps achieve goal of intentions-based design vs. organization-based design

26


Inte

rnet

Fi

rew

all

Citizen, Employee, Business Partner

Employee

Document Management

Databases

Production Environment

Web Servers

Portal Server

DatabaseMedia Server

Storage Device

Legacy Apps

Web Server

Portal Server

Load Testing Environment

Load Simulation Server

Media Server

Database

Storage Device

Web Server

Database

Development/Configuration Environment

Reporting Server Indexing Server

Agency/Cross-Agency Web Applications

Media Server

Collaboration Server

Email Servers

eAuthentication

App

Inte

grat

ion/

C

onte

nt A

ggre

gatio

n

Logical Architecture Detail: Portal Services

The following is the detailed logical architecture as it relates to portals:


Internet

Intranet

27


Web Content Management Overview

Web Content Management provides a suite of tools that enable the creation and maintenance of web application content more efficiently and with higher quality



Integration with document management solution to make documents available via the web when applicable

Integration with common content repositories and common data repositories

Support of portal component to deliver content

To achieve strategic goals, cannot continue to manage content manually. At the crux of changing the way we do business by exposing information and business processes to our stakeholders

Supports the lifecycle of content for web-based applications:

• Create -The development and maintenance of standard templates that dictate standard layout

• Review – Workflow capabilities to enable reviews of content by the right people during a designated period of time

• Aggregate and Manage – Aggregating content from multiple content sources and supporting the classification of content using meta-data and other techniques

• Distribute and Deliver -- Content is published to one or multiple production environments

• Archive and Delete – Automated processes to archive or delete content

Enables the publishing of content to alternative platforms such as PDA’s and cell phones

Supports the creation and delivery of interactive forms online

28


Logical Architecture Detail: Web Content Management

The following is the detailed logical architecture as it relates to web content management:

Content Delivery MediumsLoad Testing Environment

Template Development Desktop

Document Management

Content Development Workstation

Template/ Content Development Server

Web ServerApplication Server

Database

Content Staging Environment

Content Approval Workstation

Storage Device

Web Server Application Server

Database


Portal

Agency/Cross-Agency Web Applications

Applications on Wireless Devices

Legacy Apps

Web Server

Media ServerDatabase

App Integration/ Content Aggregation

eAuthentication

Employee

Employee

Employee

Email Servers

29


Document/Records Management Overview

Document Management facilitates the sharing of document assets across an enterprise reducing rework, enhancing productivity and quality of work



Supports the lifecycle for documents and other electronic assets:

• Create - Support for all commonly used file types and appendage of meta-data upon creation of asset

• Review - Web-based or desktop-based workflow tools for contributors or reviewers of content

• Aggregate and Manage - Check-in and check-out capabilities to control versions. Automated processes to maintain integrity of assets and clean up asset repositories

• Distribute and Deliver - Multiple search mechanisms to find information, including browsing subject hierarchies, keyword, natural language, etc.

• Archive and Delete - Integration with the National Archives to preserve electronic assets

Collaboration tools Support for a dynamic corporate taxonomy, i.e.

classification of assets can be changed

Integration with content aggregation component to provide robust searching

Integration with web content management solution to push documents/assets to the web

Integration with common content repositories and common data repositories

Key to meeting goals around records management. Enables information to stay in electronic format throughout its lifecycle and enables robust information retrieval capabilities through the classification of all assets - promotes knowledge sharing through asset sharing

30


Logical Architecture Detail: Document/Records Management

The following is the detailed logical architecture as it relates to document/Records management:

Desktop Publishing Tools

Document Delivery Mediums

Content Management

Document Management Server

Document Approval Workstation

Storage Device

Agency File ServersFile Server

Scanning Station

FaxFax Server

eFax

Batch Import Process

Portal

Agency/Cross-Agency Applications

Print

CitizenLegacy Systems

Employee

Employee

Deploy Documents

eAuthentication

App

licat

ion

Inte

grat

ion/

Con

tent

A

ggre

gatio

n

App

licat

ion

Inte

grat

ion/

Con

tent

A

ggre

gatio

n

Email

31


Central Data Repositories Overview

Central data repositories allow re-use of data and decrease the burden on our customers during data collection processes



Will facilitate sharing of data• Groups of applications that need the same data will

leverage centralized repositories• Data stewardship processes defined within the Data

Management Program result in database of records to ensure integrity and quality of shared data

• Central repositories will allow packaging of data from different sources to enhance existing USDA services and define new data centric services

• Data Warehouses will power Enterprise and Agency applications

• Effort around system integration and data migration tasks during system development will be greatly reduced resulting in USDA cost savings

eGovernment Strategic initiatives will leverage shared data repositories

Based on data needs Agency/Enterprise web and non –web based applications may use shared data repositories

Sharing of data outside of the department (business partners, educational institutions, government bodies etc)

Redundant and inaccurate data hinders our ability to provide optimal value to our customers. Shared data repositories will heighten availability, integrity and quality of relevant data to our clients. This will help improve quality of existing services and create opportunities to define new services

32


The following is the detailed logical architecture as it relates to central data repositories:

Logical Architecture Detail: Central Data Repositories

Agency/Cross-Agency Web Application

Legacy Systems

Strategic Initiative

Shared Data

Shared Data

Data Warehouse

External Database Repositories (Universities, other government organizations etc)

33


Content Aggregation / Application Integration Overview

Content aggregation spawns re-use of content and enables powerful information retrieval capabilities



An enterprise content index will deliver powerful searching capabilities across a multitude of data repository types:

• Content Management Repositories• Document Management Repositories• Databases• Web Servers• File Servers• Content originated outside of USDA and migrated to

USDA Databases/File Servers An enterprise application integration framework

will allow the integration of disparate applications in a cost effective manner

• Out of the box connectors will minimize custom development

• Promote industry standard integration mechanisms such as XML

Portal search capability will leverage enterprise content index and application integration to aggregate content and services

eGovernment Strategic and Enabler initiatives

Agency/Department web and non-web Based applications

This is a key component in allowing the integration of eGovernment capabilities into our current infrastructure. Enables ubiquitous access of data and content in a heterogeneous, distributed environment

34


The following is the detailed logical architecture as it relates to content aggregation and application integration:

Logical Architecture Detail: Content Aggregation / Application Integration

Document Management Web Content Management Agency/ Cross Agency databases

Agency/Cross Agency File Server

Web Servers, Existing CM and WCM Repositories

Content/Data Index

Agency/Cross-Agency Web Application Portal

Content Aggregation Server

Content/data Index

Search ResultsSearch Results

Enterprise Index Database

External Database Repositories

35


Content Distribution Overview

Content distribution ensures timely delivery of content and services by physically locating content in specific geographic areas



Content distribution scheme will determine the optimal location to place content based on:

• User physical location• Network infrastructure• Available bandwidth• System administrator settings

Ensure consistency of content across distributed servers

Portal content will be distributed via content distribution scheme

Web Content Management solution will integrate with Content Distribution during content deployment

Agency/Department Web Based applications

Application performance is a key criteria for the success of a solution. A content distribution scheme will allow us to ensure minimal response time for enabler, strategic and agency applications

36


The following is the detailed logical architecture as it relates to content distribution:

Logical Architecture Detail: Content Distribution

Content Distribution Server

Monitoring/Configuration StationDatabase

Portal Location 1

Portal Location 2

Agency/Cross-Agency Web Application Location 1

Agency/Cross-Agency Web Application Location 2

Web Content

Web Content Web Content

Web Content


Deploy

37





eLearning Overview

Next Steps

Agenda

38


What is a Learning Management System?

An LMS allows individuals and groups of users to:• Manage classrooms, learning assets, instructors, schedules,

learning paths, and all of the necessary components to deliver training;

• View complete course listings and course information;• Register, schedule, and track training sessions; • Create, edit, manage and deliver content;• Track competency and certification progress; • Personalize training and development plans; and• Manage payments.

A learning management system provides support in every phase of the learning management life cycle, transforming learning from an event to a continuous process.

A Learning Management System (LMS) is a software application that enables the delivery and management of all facets of training.

39


eLearning - Business RequirementsA world-class enterprise solution will be established with these capabilities:

Multiple online delivery platforms, such as web, video, audio, and videoconferencing, to augment or replace classroom-based training. Some face to face training classes will always need to remain in use since they maximize interactions.

• Robust suite of collaborative tools to allow learners to work with one another to better solve real-world problems and simulate conversation in real situations.

Online administration of curriculum by trainers, such as automatically adding and removing courses to an online course catalog.

Individualized training capabilities and online registration allowing employees to structure curriculums based on training needs and self-register for the courses online.

HR systems are automatically updated with an employee’s training; Department financial systems are automatically updated based on activity in the LMS.

Common content management capability to easily update and customize course content.

• Provide access to expertise and support for developing courses and modules to help the users learn Partnering with other Government Agencies to maximize new contracting mechanisms. Full integration with the Presidential Initiative, eTraining, and www.golearn.gov.

40


eLearning - Current EnvironmentAgencies use three online systems, following are highlights of those systems…

Internet Combined Administrative Management System (I-CAMS) • Web-based integrated human resources information system in use by the county based Agencies, FSA, NRCS, RD and

AMS that allows employees to access employment information, career plans, training requests, and history. • Provides the ability to process personnel actions, manages and tracks learning, provides automatic workflow, creates

automatic reminders, and enables online evaluation for non-catalog training. mGen

• “Off the shelf” third-party learning management system used by APHIS, OC, RMA, and RD with course content available from Learn2, SmartForce, NETg, and ElementK.

• Provides built-in content management system, content authoring tools, assessment tools for quizzes and exams, skills gap analysis.

Training Integrated Personnel System (TIPS) /Virtual Training Assistant (VTA)• TIPS system, utilized by the Forest Service, allows students to evaluate themselves against competencies while

completing their Individual Development Plan.• Included in the Forest Service’s system is an off-the-shelf learning management system called Virtual Training Assistant

(VTA) that has administration, training delivery, and evaluation tools; The Food Safety and Inspection Service uses the VTA system without TIPS, but they are only using it for tracking purposes, not its full learning management capabilities.

41


Alternatives Analyzed

Three implementation alternatives were considered. Allowing each Agency to build its own eLearning solution – “Status Quo”

• Grants the most flexibility and alleviates the need to work through culture barriers; and• Does not allow the enterprise to leverage training across all Agencies or take advantage of

economies of scale pricing.• Consistency across training and skills will not be achieved.

Leveraging an existing learning system within USDA to create an Enterprise-wide eLearning solution

• Utilizes investments in existing systems to decrease costs and system training needs;• Requires capital outlay for new hardware and software; and• Requires implementation time and customization for individual Agencies.

Contract out the eLearning solution - Recommended• Leverages all soft skill content from GoLearn.gov;• Provides the same benefits as leveraging an existing system plus decreased implementation

time and reduced need for skilled Agency resources; • Requires vendor management to ensure compliance by vendor;• USDA can concentrate on the business of training versus managing a large IT infrastructure; and• Economies of scale can be leveraged to purchase excellent training that is “standardized” across

the Enterprise.

42


Description of Factor FY 2003 FY 2004 FY 2005 FY 2006 FY 2007 Annual Benefits (AB) $2,548,388 $12,709,250 $15,572,100 $16,829,950 $16,829,950 Annual Costs (AC) $3,660,481 $6,328,978 $5,888,978 $5,888,978 $5,888,978 Discount Factor (DF) 1.0000 0.9728 0.9463 0.9205 0.8954 Discounted Benefit (DB) ABxDF $2,548,388 $12,363,084 $14,735,367 $15,491,857 $15,069,900 Discounted Cost (DC) ACxDF $3,660,481 $6,156,593 $5,572,546 $5,420,765 $5,273,117 Discounted Net (DN) DB-DC $(1,112,093) $6,206,491 $9,162,821 $10,071,092 $9,796,783 Discount Rate 2.80% Benefit Cost Ratio (BCR) DB/DC 2.31 Net Present Value $34,125,093 Payback Period 1 IRR 617% Modified IRR 48% ROI 131%

eLearning - Cost and Benefit AnalysisAn enterprise-wide eLearning program offers several quantitative benefits and a 131% ROI.

* Assumptions are documented in the business case document

• Enhance the skill development of USDA employees by providing access to a wide array of training not previously available.

• Coordinate management, and promote interagency collaboration, of Federal eLearning services. • Allow for economies of scale in the enterprise-wide purchase of eLearning products and services; and• Reduce travel expenses, training delivery costs, and training administration costs.• Transform the learning experience to include more online courses, in lieu of costly traditional training

methods.• Agency trainers will be able to devote their time to what they do best--training--rather than

administration of IT systems.

43


Logical Architecture Detail: eLearning



eLearning provides self-paced and collaborative learning experiences, delivered over the web, designed to promote comprehension and retention

Features to improve learning management and training administration activities such as:

• Administration of curriculum• Self-registration• Content creation and publishing tools• Standardized skills assessment

Enhanced training experiences through new technologies:

• Individualized training• Online course delivery• Collaboration tools

Seamless integration with legacy training data, human resources systems, and financial systems

Aggregate existing Agency and enterprise applications and content

Integrate with existing legacy training systems, access to legacy system business logic and data

eAuthentication

Mandated by the Presidential Management Agenda and required for USDA to maintain an effective and productive of workforce

44


Inte

rnet

Fi

rew

all

Learner (employee, citizen, partner)

Learner (employee)

Document Management

Production Environment

Web Servers

LMS/LCMS Server

Database

Media Server

Storage Device

Legacy Apps

Web Server

LMS/LCMS Server

Load Testing Environment/Content Staging Environment


Media Server

Database

Storage Device

Web Server

Database

Content Development/Software Configuration EnvironmentAgency/Cross-Agency Web Applications

Media Server

Email Servers

eAuthentication

App

Inte

grat

ion/

C

onte

nt A

ggre

gatio

n

Logical Architecture Detail: eLearning

The following is the detailed logical architecture as it relates to eLearning:

Internet

Intranet

eLearning Administrator

Instructional Content Designer

Portal


45





eLearning Overview

Next Steps

Agenda

46


Condensed Project Timeline

USDA Agencies will adopt Enabler solutions over the next 1-5 fiscal years.

TaskQ1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Ongoing eDeployment Project TasksBuild and Sustain Executive LeadershipObtain and Deploy Personnel ResourcesPhase 1: eDeployment Pre-implementation TasksDevelop Request for Proposal (RFP)Evaluate and Select VendorDesign, Build, and Test Development and Production EnvironmentPhase 2: eDeployment Early Adopter ImplementationRefine Early Adopter RequirementsDesign Early Adopter Business Processes and SolutionDesign and Develop TaxonomyDevelop Procedures, Performance Support, and Training MaterialsBuild and Test Early Adopter SolutionTransition Early Adopter WorkforceDeploy Early Adopter SolutionPhase 3: eDeployment Enterprise-wide ImplementationRefine Solution RequirementsDesign Business Processes and SolutionDevelop Procedures, Performance Support, and Training MaterialsBuild and Test SolutionTransition WorkforceDeploy Solution

FY2007FY2003 FY2004 FY2005 FY2006

47


Proposed Early Adopters

This table identifies the Agencies that expressed an interest in being an early adopter of the Enabler solutions.

Agency Content Management

Document Management

Portal Services

Web Presence

eLearning eAuthentication

AMS X X X X XAPHIS XARS X X X X XCSREES XDA XERS XFAS X X X XFNS X X XFS XFSA X X X X X XFSIS X X XNASS X X X X X XNFC XNRCS X X X X X XOC X XOCE/WOAB X X X XOES X X X XRBS XRD XRMA XRUS X

48


Next Steps

The Next Steps to begin the Enablers implementation are:

USDA Approval and Funding• Incorporate agency comments into the Enabler’s business cases; and• Secure funding for Enabler’s projects (FY03, FY04, and FY05).

OMB Approval• Seek approval from OMB for FY05 budget cycle.

Project Establishment and Kick Off • Select project management; and• Identify and staff project team to support implementation.

Conduct Pre-Implementation Tasks • Refine application requirements; • Develop request for proposal (RFP);• Conduct vendor analysis and select vendors; and• Begin design of development and production environments.

Date post:	16-Apr-2017
Category:	Documents
Upload:	agcristi
View:	701 times
Download:	0 times