utah’s workforce system utah’s development of a one-stop ... · rich carbon washington cache...
TRANSCRIPT
Utah Department of Workforce Services
June 2001
Utah’s Workforce System
Utah’s Development of a One-Stop Operating System
Russell Smith UWORKS Project Manager
Presenter
On July 1, 1997 five Utah agencies merged tocreate The Department of Workforce Services(DWS) :• Office of Family Support (Welfare)• Department of Employment Security (Job Service)• Office of Job Training (JTPA)• Turning Point (Office of Education)• Office of Child Care (Economic & Community Development)
DWS History
One Stop Employment Centers
Tooele
Millard
Iron San Juan
Kane
Juab
Box Elder
Uintah
Emery
Garfield
Grand
Utah
Beaver Wayne
Duchesne
Sevier
Summit
Rich
Carbon
Washington
Cache
Sanpete
Piute
Wasatch
Davis
Weber
DaggettMorgan
Logan
Brigham City
Ogden South
Clearfield
Tooele
Park City
Heber
Roosevelt
American Fork
Provo North
Payson
Nephi
CastledaleDelta
Fillmore
Moab
BeaverJunction
Loa
Cedar CityPanguitch
St. George Kanab
Monticello
Western Region
Western Region
Mountainland Region
rVernal
rBlanding
Eastern Region
Western Region
$ZKaysville
$Z
$Z
$Z
$Z
r Richfield
Orem
rManti
â
â North Region
East Carbon
Price
Admin North
Central AdminCentral ESC
MidvaleSouth County
SL TPO
Downtown
$ZMagna
Green River
Metro
Utah Department of Workforce ServicesFacilities Legend
Employment Centers
ESC/Regional Admin
r EC/ESC
â EC/ESC/Admin
State/Regional Admin
Regional ESC
$Z Storefronts
Central Region
Eastern Region
North Region
Western Region
Mountainland Region
March 1, 2001
DWS Computer SupportMajor Systems used at DWS preUWORKS– PACMIS– GUIDE– USSDS– CATS– UTES– RIC– JTPA Case Management
DWS Business Need• Development of a computer system that supports
the Employment Connection (service delivery)pathway of the Department of Workforce Services
• Integration of disparate and redundant computersystems used for tracking EmploymentConnection services and activities
• Ability to interface with other DWS computersystems (i.e. eligibility, UI) to gather keycustomer information
DWS SolutionUtah’s Workforce System - UWORKS– Consistent structure throughout– Organized and integrated– Centrally managed data– Expandable– Economical to maintain– Accessible to anyone with Internet access and
proper security using industry standard tools
Client Server Architecture vs.Multi-tier
Server
PC
Client ServerSystems
Executable programwith business logic
and rules
Shared systemlogic withdatabase
Database
WEB Browser
Web Server
Application Server
WEB Browser
Displays WEB Pagesfrom a Server
Business logic andrules in one location
Data storage handlesadds, changes and
deletes
Multi-tier Environment
UWORKS Architecture
Self ServiceEmployer & Job Seeker
pure HTML
DWS OfficeMediated
Oracle FormsIE 4.0 + JVM
SONETOC-3
IBM MainframeOS 390
Oracle 8iAdabas access through
MQ SeriesProcedural Gateway &
ETA Transparent Gateway
U-WorksSUN E4500
10 400mhz CPU32 G HD
Server Name : DB1Oracle 8i
CATS, Appeals, etcSUN E4500
4 336mhz CPU32 G HD
Server Name : DB2Oracle 8i
DWSDevelopment
SUN E4502 300mhz CPU
8 G HD
Server Name : DevelopmentOracle 8i
DWS Test/Training
SUN E4502 300mhz CPU
8 G HD
Server Name : DB3Oracle 8i
U-Works SelfService
SUN E4502 300mhz CPU
8 G HD
Server Name : BatchOracle 8i
DWS DataWarehouseSUN E450
4 300mhz CPU152 G HD
Server Name : DwarehouseOracle 8i
Application ServersGateway Windows NT
8 Duel 550mhz 2 G RAMalso includes Oracle Matrix Server
Sized at 80 users per CPUfor 1280 Users
Internet
Zylan gigabit Switch
Utah Department of Workforce ServiceU-Works Project
High Level AtrchitectureFebruary 2000
100 MB
100 mb
T1
Modem speed
FederalReports
SQL ReportGenerationPrograms
InformationTables
Web ReportGeneration Package
UWORKSDATABASE
ORACLE8iWAREHOUSE DATABASE
ETTProcedures
Workstation Browser
OracleApplication Server
DWS Datawarehouse Server: SUN E450
Web ReportRequest
HTMLFormatted Report
DBLink
Utah DWS Data Warehouse: ETA and VETS ReportGeneration Overview
• Self service and staff assisted• Registration• Initial screening• Access to state, local and nation WEB
based products• Scheduler (workshop, testing and
resources)• Pre-application (partial application for
specific programs)
UWORKS Functions
UtahJob.Net Sign Up/Log On Screen
UtahJob.Net Job Seeker Account Activity Screen
UtahJob.Net Job Seeker Personal Attributes Screen
UtahJob.Net Job Seeker Personal Resume Screen
UtahJob.Net Employer Account Activity Screen
UtahJob.Net Employer Registration Screen
UtahJob.Net Employer Job Order Summary Screen
UtahJob.Net Employer Job Order Search Screen
• Staff assisted only components• Application and eligibility (multiple
programs)• Enrollment (program specific)• Activities• Initial assessment• Comprehensive assessment• Employment plan
UWORKS Functions
• Staff assisted only components continued• Job seeker progress tracking/case
management• Post-program termination (follow up
services)• Provider information
UWORKS Functions
UWORK Job Seeker Registration Form
UWORK Job Seeker Services Form
UWORK Job Seeker Notes Form
UWORKS Rapid Response Form
UWORKS Employer Registration Form
UWORKS Employer Job Order Form
UWORKS Assessment Form
UWORKS Assessment Summary Form
UWORKS Employment Plan Form
UWORKS Provider Information Form
UWORKS Referral Form
UWORKS Employment Monitoring Form
UWORKS Placement Form
UWORKS Administrative Form
UWORKS Search for Employers Form
UWORKS Employer Correspondence Form
UWORKS Case Management Online Reports Form
UWORKS Objectives
– Self service and staff assisted– Multi-tier architecture– Service driven not eligibility– Service coordination– Flexibility and easily modified and maintained– Ability to interface with other DWS systems– Eliminate redundant collection of data
UWORKS Objectivescontinued– Protect customer privacy– Standardized collection of data for reporting– System documentation– Accessible from a standard web browser
UWORKS Timeline
– Review TWIST system in Texas Aug 98– Request for Information RFI Sep 98– Application development shootout Oct 98– Vendor selection Nov 98– Utah visit from DOL Nov 98– Join consortium Dec 98– Requirements document due Mar 99
UWORKS Timeline
– Combine forces with AJB/OSOS Apr 99– Completion of system requirements May 99– Missed system deadline #1 Aug 99– Unable to sign contract with Oracle Sep 99
and AJB– Withdraw letter from Utah Sep 99– Signed contract with Oracle Oct 99– Fix OSOS requirements to Utah’s Nov 99
UWORKS Timeline
– UWORKS development begins Dec 99– Y2K backup system for WIA Jan 00– Training Utah staff Jan-Feb 00– UWORKS programming begins Jan-Apr 00– UWORKS testing Mar-May 00– UWORKS training May – June 00– UWORKS conversion July 00
UWORKS Timeline
– UWORKS CM in production July 5, 2000– UWORKS Fin in production July 25, 2000– UWORKS – PACMIS interface Aug 8, 2000– Decision to re-write job matching Oct 00– UWORKS II team selected Dec 00– Version II prototype approved Jan 01
UWORKS Timeline
– UWORKS consortium states Feb 01• Alabama• Montana• North Dakota• South Dakota• Washington
– Version II implementation date Jan 02
System DevelopmentObstacles / Responses
– Mixed funding sources– New program specifications– Political impact– New technology– Competition to produce first OSOS
System DevelopmentObstacles / Responses
– Technology transfer– Purchasing RFP process– Software licensing– Contract / vendor management– Project management
Action That Could FacilitateState Efforts to Modernize
Systems– Sharing of code– System certification specifications– Need for a national clearinghouse of
technological initiatives– New technology– Project management training for government
systems