FIU Development
Supporting FIU Operations
with effective
Information Technology
2004
Office of Technical Assistance (OTA)
1
Overview
• Organizational Structure
& Operations
– Roles &
Responsibilities
– Organizational
Structures
– Reporting Structures
– Etc.
• Technology Strategy
– Management
– Coordination of
Activities
– System Development
– Contractors / Vendors
– Knowledge Transfer
Office of Technical Assistance (OTA)
2
Outcome
• Enhanced understanding of roles and
responsibilities.
• Increased internal organizational cooperation and
decreased departmental overlap.
• Motivation to pursue development of business
process as a long term activity.
Every FIU has specific needs and environmental influences. The
key to an effective organization is communication and planning.
Office of Technical Assistance (OTA)
3
Technology Strategy
•
•
•
•
•
Management
Coordination of Activities
System Development
Contractors / Vendors
Knowledge Transfer
Office of Technical Assistance (OTA)
4
Management
Critical Ongoing Concerns of an Effective Organization
Visionary
Governance
Flexibility
Vision
Mission
Constitution
Linkages
Strategy
Technology Vision
Technology Strategy
Technology Research
Pragmatic
Quality
Architecture
Technology Architecture
Development Services
Program Management
Engineering and Deployment
Operations
Office of Technical Assistance (OTA)
5
Management
Vision
Mission
“Provide the vision, leadership, and technical
means to implement and support the strategic
architecture and emerging technologies in support
of the John Hancock current and long-term
business strategy.”
Our goal is to make it easy to develop, integrate,
and implement business applications aligned to JH
Architecture standards.
Office of Technical Assistance (OTA)
6
Coordination of Activities
•
•
•
•
•
•
•
Planning and Management
Determine resources and groups
Levels of involvement/time requirements
Levels of responsibility/accountability
Effective and efficient (avoid complexity)
Status and Updates
Above all - Communication
Office of Technical Assistance (OTA)
7
Coordination of Activities
Within the Technology Department
Program
Office
Development Priorities
&
Application Architecture
Development
Application
Development
Technology
Services
Operations
&
Customer
Service
Support
Services
to users
Infrastructure Development
&
Technical Architecture
Office of Technical Assistance (OTA)
8
Coordination of Activities
Between IT and the rest of the organization.
FIU
Support
Services
to users
Management
Administration
Legal
Analysis
International Relations
Etc.
Operations
&
Customer
Service
Office of Technical Assistance (OTA)
9
System Development
• Coordination among FIU departments to
develop “requirements”
• Phased development approach
• Iterative process versus “waterfall”
• Functionality and development review
– “what will this do for us” / “where are we now”
• Milestones and sanity checks
Office of Technical Assistance (OTA)
10
System Development
Waterfall Development
Requirements
Risk
Design
Code & Test
Subsystem Test
Implement
Time
Office of Technical Assistance (OTA)
11
System Development
Iterative Development
Rational Unified Process 2000, Rational Software
Office of Technical Assistance (OTA)
12
Contractors / Vendors
• Know what you need before talking to potential
vendors.
• Do your homework. Who can provide what you
need effectively and affordably.
• Follow a “model” for establishing the Conditions
of Satisfaction (COS)
• Establish contract(s) and service level agreements
(SLAs) that reflect the COS.
• Manage vendors by monitoring SLAs & COS.
Office of Technical Assistance (OTA)
13
Process Model
Customer
Performer
Office of Technical Assistance (OTA)
14
Process Model
Preparation
Customer
Declaration of
Satisfaction
Acceptance
Negotiation
Request or
Offer
Conditions
of
Satisfaction
Declaration of
Completion
Office of Technical Assistance (OTA)
Commitment
Performer
Performance
15
Process Model
C
COS
P
COS
C
Conditions
of
Satisfaction
Customer
Performer
COS
C
C
COS
P
Office of Technical Assistance (OTA)
P
C
P
COS
16
P
Diagnosis
• How will the Request/Offer stage begin and
carried out:
• Who will contract & who is the customer?
• Clear communications of Processes?
• Roles and responsibilities
• Etc.
• Is FIU Management clear about
vendor offers?
?
• How does the vendor ensure
Management’s satisfaction?
• How do you enable negotiation?
• Are alternatives clear?
• Do you counteroffer or just say no?
• How do you determine COS?
?
•Performer
• Do performers have the right
skills to fulfill the conditions
of satisfaction
• Is Management kept informed of
progress? (who is kept informed?)
• Does everyone involved know who the
customer is and do they understand the
COS
• How will Management handle completion
/ transition?
• Are there SLAs in place?
Office of Technical Assistance (OTA)
17
Knowledge Transfer
• Phased development and implementation
• Transfer of knowledge during all phases
• SLAs should ensure transfer
– Day to day
– Documentation
• Vendors should provide support (SLAs)
– FOC
– “One-off” / “as needed”
– Follow-on contract(s)
Office of Technical Assistance (OTA)
18
Thank You
Joe Bognanno
Enforcement Advisor
joe.bognanno@ota-it.us
T: +1 571.275.7480
F: +1 703.573.6660
Office of Technical Assistance (OTA)
US Department of the Treasury
Office of Technical Assistance (OTA)
19