Transcript Slide 1

Mobile Business Solutions for a
Productive HHS Workforce – A Case
Study
Debby Wattman, IRM
Department of Family and Protective Services
05/25/05
Agenda
Project Overview
• APS Reform Background
• Goals & Expectations
• Mobile Environment Model
Mobile Architecture
•
•
•
•
Guiding Principles for Mobile Architecture
HHS Enterprise Architecture Direction
Mobile Architecture Selection
Mobile Architecture Diagram
• DFPS and HHS Enterprise Partnership
• Enabling Enterprise Standards
• Re-using Enterprise Assets
• Sharing DFPS assets relevant to HHS Enterprise
2
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
Adult Protective Services (APS)
Reform Background
• Governor’s Executive Order RP 33 directed HHSC to conduct a
review of APS
• HHSC’s November 2004 final report identified 252 corrective
actions
• In March 2005 DFPS finalized a contract with Accenture to:
• Complete IMPACT changes associated with Reform
• Develop the Mobile Protective Services (MPS) application that extends key
IMPACT documentation tools to the field
• Approximately 500 In-home caseworkers will receive Tablet PCs
and digital cameras between June – October 2005
3
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
APS Goals & Expectations
• Mobile technologies will help erase the boundary between field
and office
• Caseworkers will utilize mobile technology to reduce
documentation time whenever & wherever feasible
• Caseworkers will complete documentation for a given contact
closer to the time the contact occurred (as compared to current
practice)
4
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
Mobile Environment Benefits: Blends Current & New Resources
Evidence Gathering/Sharing
Current World
Mobile workers continue to use phones for direct
communication with supervisor/experts/peers
Documentation/Case Management
The office does not go away, but
reliance is reduced
New World
IMPACT Usage
Mobile device provides field
access to resources currently
available only in office
Mobile device(s) provide easier
capture of evidence or information
that can be shared from the field
Forms
Field Work
IMPACT & MPS
Usage
Digital Camera
Data
Policy
Audio Recordings
5
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
Mobile Architecture Guiding Principles
• Leverage IMPACT Architecture Features
• MVC Framework
– JSPs and EJBs
• XML
• Web Services
• Maximize code reuse to minimize maintenance effort
•Retain look and feel of User Interface as much as possible to
minimize retraining
• Align with HHSC Service Oriented Architecture Principles and
Framework
6
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
HHS Enterprise SOA Vision
Enabling Secure and Relevant Information Delivery Anytime, Anywhere
BACK-END
FRONT-END
Business Processes/Services/Systems
HHS SOA Platform (Portal)
Rich Client
Business Context
& Activities
Monitoring
Workflows/Service Application Adapters
Collaboration Services
Information
Interaction &
Access Services
Browser/Portal
Managed Client
Services
Search,
Analysis
Mobile Clients
Tablet PC
7
Enhancing Accountability
Improving Services
Integration
Increasing Efficiencies
Data &,
Content
7/18/2015
Mobile Architecture Selection Process
• Selecting an appropriate mobile architecture was crucial to
maintaining the guiding principles
• DFPS is the first department to use a mobile application within
HHS; therefore HHS IT assisted in the selection process
• Several commercial architecture solutions were evaluated
• iAnywhere Platform selected based on the following criteria:
– HHS Enterprise SOA direction compatibility
– Application Code Reuse and Maintainability
– User Adaptability/Training
– Adaptability to Emerging Standards/Technologies
– Performance
– Ease of Data Synchronization
– Security
– Manageability and Deployment
– Leveraging Tablet Features (pen, Digital Ink, Voice)
8
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
High-Level Mobile Architecture
• Tablet PC
•
•
•
•
Microsoft Office
Application Data Store (ex. Mobile Database; XML Data Store)
Synchronization Client or API
Streets and Trips
• Synchronization Server (iAnywhere)
• File and Application Data Synchronization Services
• System Management Service
– Deployment
– Asset Management
9
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
MPS Synch Architecture
Tablet PC
Mobile Server
Web Service
Synchronization
Software
EJB/Tuxedo Services
JBOSS
IMPACT
JSP/EJB
Mobile
Sync
Module
Remote Database
JBoss/IMPACT – Uses the IMPACT code
base with minor modifications, but limited
to certain modules.
Mobile Sync Module – Syncing
module that initiates synch with mobile
server.
Remote Database – Data
repository with subset schema
similar to IMPACT.
IMPACT Database
Publications /
Subscriptions
Mobile Server – A separate server
which provides synchronization of
application data for Tablet Client.
- Publish/Subscribe Model used for
downloading/uploading data.
Application
Tables
Staging
Tables
Web Service – Exposes EJBs/Tuxedo
Services they can be called within
synchronization process.
- Data downloaded into tables identical
to IMPACT schema.
- Data uploaded into staging
tables/database.
- After upload into staging table,
existing EJBs/Services called to move
data into application tables.
** The Remote Database and Mobile Server are logical representations. This could be
accomplished with Oracle or IAnywhere databases.
10
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
MPS Data Sync Architecture
Benefits
Considerations
• The mobile code base would use the IMPACT
code base. This would simplify maintenance when a
change is made to a mobile component (ex. Adding
a field to a web page).
• Requires the use of JBoss and a database on the
Tablet. There are many internal components and
configuration aspects of these applications thus
decreasing the manageability of the mobile
application.
• Users would be able to adapt to the mobile
application quickly because it would look like
IMPACT. There would be less to learn for users
allowing them to become proficient quickly.
• Tuxedo services would be converted to EJBs to
support the disconnected application. This is inline
with the IMPACT maintenance strategy to make
IMPACT more J2EE compliant and get off Tuxedo.
• Narrative and Form data entry may not be fullyfeatured. For example, Spell Check may be limited.
• Requires re-coding of some Document
Architecture components for Narratives.
• Uses a skill set that the FPS AD&M team knows
and is trained in.
• Data modified offline goes through business rules
server side before going into the database.
• Data moved from server to device with database
synchronization software.
11
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
Enterprise HHS Mobile Platform Roadmap
• Phase 1: DFPS Mobile Platform Project (Dates: March-June 2005)
•
•
•
•
Validate business operations Issues
Validate Architecture Integration Issues
Validate Architecture Security Issues
Establish Solution Benchmarks
• Phase 2: Establish HHS Enterprise Mobile Architecture Standards
• Support of Mobile Architecture in HHS Enterprise SOA Platform
• Establish HHS Enterprise IT Services Model for Mobile Applications
Development and Management
• Phase 3: On Ramp Business Application to the Mobile Platform
12
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015
Thank You
13
Enhancing Accountability
Improving Services
Increasing Efficiencies
7/18/2015