2. Barker University
• A public institution consisting of nine schools.
• Long standing tradition of decentralized
administration.
• All had independence, local control, and self-
sufficiency.
• Many approaches to administration and
operations with differing process and procedures.
• Own IT staffs, computer and networking facilities,
local applications, and approach to funding IT
investments.
3. The Data Problem
• Collect information about Barker’s staffing and
finances.
• Cost-containment committee had been only
marginally effective.
• Lengthy and complicated negotiation with the
newly formed Barker Union of Clerical and
Technical worker.
• Barker’s existing business process were very
paper intensive and decentralize.
• Shadow systems
4. Administrative Data Task Force
for a coherent administrative information processing environment
• Address common information processing and
data access needs at the sub-department, school,
and university levels
• Enable efficient administrative transaction
handling through shared, cooperative process.
• Provide access to required administrative
information at every desktop through affordable
and consistent tools
• Be flexible and supportive of change in the way
Barker conducted its business.
5. Administrative Data Task Force
No overarching framework to manage the information
• Process Redesign
– Streamline the way Barker operates
– Take advantage of new systems opportunities
• Information Architecture
– Data elements of common interest
– Access and sharing information key policies
• Technology Architecture
– Computer, networking, and software facilities
6. Administrative Data Project
• Financial Process Design Team
– Redesign of financial workflows
– Prototype of new automated financial process
• Human Resources Process Design Team
– Redesign of human resource workflows
– Prototype of new automated financial process
• Information Architecture Team
– High-level model of core HR and Finance
– Information ownership, responsibility, business rules.
• Technical Architecture Team
– Technical framework and standard for administrative
– Seamless and integrated administrative information system
7. ADP Deliverables
• Prototype
– Desktop Utility
– Data Warehouse
• Report of findings and recommendation
– Common information with standard definition
8. ADP Work Plan
• Starting up and gathering information
• Defining set of solutions
• Developing and implementing the prototype
9. ADP Organization
Leadership
(Task Forces)
Project Direction Coordination
and Oversight and Support
Advisors and Advisors and Advisors and Advisors and
Resource People Resource People Resource People Resource People
Information Technical
HR Process Financial Process
Architecture Team Architecture Team
Team Leader Team Leader
Leader Leader
Core Team Core Team Core Team Core Team
Members Members Members Members
10. ADP Work Plan and Schedule
Phase 1 Phase 2 Phase 3
Standards
Technical
Tools, and Prototype
Project Team Technical Team Framework Report
Development Environment
and Services
Partnerships
• Project Design
and Start-up Common vs. Information
10/15/93 Definition and
Data Team Unit Specific Architecture
• Training Policies
11/30/93
Information Design
• Current State
• Prototype
• Barker Inits.
9/30/94
11/5/93
• Report 9/30/94
• Current State
12/1/93 Data
• External Inits.
12/1/93
HR & Finance Collection Workflow Policies and
• Communications Team Needs Map Procedures
Ongoing Definition