1. Office of Technical Assistance (OTA)1 FIU Development Supporting FIU Operations with effective Information Technology 2004

2. Office of Technical Assistance (OTA)2 Overview Organizational Structure & Operations –Roles & Responsibilities –Organizational Structures –Reporting Structures –Etc. Technology Strategy –Management –Coordination of Activities –System Development –Contractors / Vendors –Knowledge Transfer

3. Office of Technical Assistance (OTA)3 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.

4. Office of Technical Assistance (OTA)4 Technology Strategy Management Coordination of Activities System Development Contractors / Vendors Knowledge Transfer

5. Office of Technical Assistance (OTA)5 Operations Architecture Strategy Governance Flexibility Management Quality Visionary Pragmatic Technology Vision Technology Strategy Vision Mission Constitution Linkages Technology Architecture Development Services Engineering and Deployment Technology Research Program Management Critical Ongoing Concerns of an Effective Organization

6. Office of Technical Assistance (OTA)6 Management “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. VisionMission

7. Office of Technical Assistance (OTA)7 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

8. Office of Technical Assistance (OTA)8 Coordination of Activities Development Priorities & Application Architecture Application Development Operations & Customer Service Infrastructure Development & Technical Architecture Program Office DevelopmentSupport Services to users Technology Services Within the Technology Department

9. Office of Technical Assistance (OTA)9 Coordination of Activities Between IT and the rest of the organization. Operations & Customer Service Support Services to users FIU Management Administration Legal Analysis International Relations Etc.

10. Office of Technical Assistance (OTA)10 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

11. Office of Technical Assistance (OTA)11 System Development Risk Time Requirements Design Code & Test Implement Subsystem Test Waterfall Development

12. Office of Technical Assistance (OTA)12 System Development Iterative Development Rational Unified Process 2000, Rational Software

13. Office of Technical Assistance (OTA)13 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.

14. Office of Technical Assistance (OTA)14 Process Model CustomerPerformer

15. Office of Technical Assistance (OTA)15 PreparationNegotiation PerformanceAcceptance Customer Performer Request or Offer Commitment Declaration of Completion Declaration of Satisfaction Conditions of Satisfaction Process Model

16. Office of Technical Assistance (OTA)16 Customer C P COS C P C P C P C P Performer Conditions of Satisfaction Process Model

17. Office of Technical Assistance (OTA)17 ? ? Performer Do performers have the right skills to fulfill the conditions of satisfaction 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 do you enable negotiation? Are alternatives clear? Do you counteroffer or just say no? How do you determine COS? 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? How does the vendor ensure Management’s satisfaction? Diagnosis

18. Office of Technical Assistance (OTA)18 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)

19. Office of Technical Assistance (OTA)19 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