HIGH INTENSITY DRUG TRAFFICKING AREA FINANCIAL MANAGEMENT DATABASE PROJECT.

Slides:



Advertisements
Similar presentations
GBA 573 Final Presentation Jonathan Stone Summer 2003.
Advertisements

How to commence the IT Modernization Process?
UT San Antonio PeopleSoft Project September 2010.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
INL’s Cellular Data Stipend Jonathan Homer NLIT 2009.
Chapter 20 Introduction to Systems Development and Systems Analysis Copyright © 2012 Pearson Education 20-1.
Centers for IBM e-Business Innovation :: Chicago © 2005 IBM Corporation IBM Project October 2005.
Why Managers Must Understand IT Managers play a key role –Frame opportunities and threats so others can understand them –Evaluate and prioritize problems.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
High-Level Assessment Month Year
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
SAS 112: The New Auditing Standard Jim Corkill Controller Accounting Services & Controls.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
SPAWAR HQ (General Fund) Navy ERP Implementation Lessons Learned – Comptroller View.
Basel Accord IITRANSITIONSERVICES Business Integration Support FCM Management Limited Paris New York Toronto.
TrainingFinder Real-time Affiliate Integrated Network (TRAIN) The nation’s premier learning resource for professionals who protect the health and safety.
Learning with a Purpose: Learning Management Systems Patti Holub, Director District Initiatives and Special Projects Miguel Guhlin, Director Instructional.
Revenue Cycle Management Medical Technology Acquisition and Assessment Team Members: Joseph Dixon, Michael Morotti, Mari Pirie-St. Pierre, David Robbins.
Rutgers Integrated Administrative System RIAS Phase III – HRMS, Budgeting, and Enterprise Reporting Treasurer’s Luncheon December 2, 2008.
ENTERPRISE DATA INTEGRATION APPLICATION ARCHITECTURE COMMITTEE OCTOBER 8, Year Strategic Initiatives.
Systems Analysis and Design: The Big Picture
DMV’s Service Transformation Program AASHTO Auditor’s Conference Tom McClellan, DMV Administrator and Dawn Farr, Interim STP Lead Oregon Department of.
Systems Analysis and Design in a Changing World, 6th Edition
Project Management Process Overview
 OSA MeetingMay 17,  Project Vision  Scope, Governance, Benefits  Timetables & Next Steps  Realizing the Vision - Procurement  Questions 2.
IT Project Management Cheng Li, Ph.D. August 2003.
State of Maine NASACT Presentation “Using the Business Case to Guide a Transformation Procurement” 1 Using the Business Case to Guide a Transformation.
State of Kansas Financial Management System Needs Assessment Steering Committee Meeting November 30, 2006.
1 EIR Accessibility Web Scanning Program Jeff Kline, Statewide Accessibility Coordinator Texas Department of Information Resources October, 2012.
U.S. Department of Agriculture eGovernment Program August 14, 2003 eAuthentication Agency Application Pre-Design Meeting eGovernment Program.
Software Engineering Project Assignment 7 Group 3 IT-201.
IIA_Tampa_ Beth Breier, City of Tallahassee1 IT Auditing in the Small Audit Shop Beth Breier, CPA, CISA City of Tallahassee
Introduction  Easy English, Inc. Chinese based company specializing in Language translation  Background Translations are currently done manually by.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
Lecture 7. Review of Lecture 6 Project Scheduling: The process of defining project activities, determining their sequence, estimating their duration Scheduling.
Software Project Management
1 What’s Next for Financial Management Line of Business (FMLoB)? AGA/GWSCPA 6 th Annual Conference Dianne Copeland, Director, FSIO May 8, 2007.
Financial Systems Needs Assessment Administrator Briefing Spring Quarter 2009.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
1 Building a Foundation With Standardization Dianne Copeland, Director, FSIO Federal Financial Management Conference March 11, 2008.
Presentation to the Information Services Board March 6, 2008 Bill Kehoe, Chief Information Officer Bill Kehoe, Chief Information Officer.
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
Office of Sponsored Projects & Industry Partnerships eSRA Electronic Sponsored Research Administration Jeff Weiner Office of Sponsored Projects & Industry.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Chapter 11: Alternative Approach - Purchasing Systems.
The CSO’s IT Strategy and the GSBPM IT Directors Group October 2010 Joe Treacy Central Statistics Office Ireland.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Development Processes Chapter Study Questions Q1: How are business processes, IS, and applications developed? Q2: How do organizations use business.
FI$Cal Change Discussion Guide General Ledger Guide April 2016.
Government of Mongolia Government Financial Management and Information System (GFMIS) FreeBalance Case Study ICGFM, April 2004.
Clinical Decision Support Implementation Victoria Ferguson, COO - Program Manager Christopher Taylor, CIO – Business Owner Monica Kaileh, CMIO – Steering.
Chapter 11 Project Management.
Introduction to Project Management Chapter 7 Managing Project Resources Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
Defense Enterprise Accounting Management System (DEAMS)
Systems Analysis and Design in a Changing World, 4th Edition
Information Systems Selection
Enterprise Content Management Owners Representative Contract Approval
State Treasury Agency, Azerbaijan Republic
Protecting the Integrity of Federal Payments
Welcome.
CMGT 410 Education for Service-- snaptutorial.com.
CMGT 410 Teaching Effectively-- snaptutorial.com.
Department of Licensing HP 3000 Replatforming Project Closeout Report
Project Management Chapter 11.
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
SHARE Special Project SHARE Benefits Optimization
Voice Upgrade Project Initiation Certification Request
NM Department of Homeland Security and Emergency Management
Closeout Certification Request May 23, 2019
Presentation transcript:

HIGH INTENSITY DRUG TRAFFICKING AREA FINANCIAL MANAGEMENT DATABASE PROJECT

INTRODUCTION: HIDTA Overview  Congress established the High Intensity Drug Trafficking Area (HIDTA) Program to operate under the direction of the Office of National Drug Control Policy (ONDCP) by the Anti-Drug Abuse Act of 1988 (P. L , November 18, 1988) and the ONDCP Reauthorization Act of  Resources provided to the HIDTA Program have grown from $25 million in Fiscal Year 1990 to $206 million in FY  The FY 2001 HIDTA Program coordinated the efforts of a total of 941 local, 170 state and 35 Federal law enforcement agencies and 60 other agencies participating in 482 HIDTA-funded initiatives

INTRODUCTION: Project Background  The HIDTA Financial Management Database Project will give the HIDTA program a single national financial management system for all HIDTA locations.  Benefits include providing one set of financial records for all HIDTA participants, a standardized process for budget development and programming of funds, standardized reporting, ad-hoc reporting, and will provide better financial communication across the organization.

PROJECT ANALYSIS: The Problem…  Each HIDTA office develops and manages its own budget separate from the national financial records.  The records maintained by the national HIDTA program office frequently differ from the records tracked by each individual HIDTA office.  32 HIDTA offices has each have a financial manager who spends at least 8 hours per week fixing discrepancies between local and national numbers.

PROJECT ANALYSIS: The Objectives… 1.Reduce errors and improve the accuracy of HIDTA financial data. 2.Reduce the time and cost of reconciling HIDTA budgets by integrating all HIDTA financial records into one system. 3.Speed up the budgeting and reprogramming approval processes. 4.Improve financial reporting and managerial decision making capabilities.

PROJECT ANALYSIS: In Scope…  All end-user interaction via web based interface  Custom HIDTA input form  Custom HIDTA reports – specific to program  Digital approval process equal to current process  Web-based remote management of product  Budgeting Process  Automated management of Grants Administration

PROJECT ANALYSIS: Out of Scope…  Expenditure Tracking  Wide Area Network Design / Implementation  GroupWare

RETURN ON INVESTMENT: Expected Benefits

RISK MANAGEMENT: Risk Assessment…  Users might not buy into the system after rollout  System software could be dropped by vendor  System software might not work as advertised  Could be more expensive to manage than planned

RISK MANAGEMENT: Risk Control…  Training, support, and financial manager empowerment  Product is standards based and code is available  A third party could modify and/or support  Could contract with 3 rd party for less expensive support

PROJECT IMPLEMENTATION: Timeline and Work Breakdown Structures…  Estimated 127 working days to complete entire project.  Core team of 15 people – 13 HIDTA, 2 contractors  Design phase 60 working days to complete.  Development phase 44 working days to complete.  Implementation phase 23 working days to complete

Critical Path Gantt Chart

FINAL ANALYSIS: Methods of Evaluation…  Project completed on time and on budget.  Documented use by all financial analysts.  Budget reconciliation time eliminated.  Reduce reprogramming processing time from 3 days to 1  Reduce budget approval process from 5 months to 3

HIGH INTENSITY DRUG TRAFFICKING AREA FINANCIAL MANAGEMENT DATABASE PROJECT