portfolio management gary stevens and craig palmer

Portfolio Management

Gary Stevens

And

Craig Palmer

“Uniting Technology and Healthcare” 2

Learning Objectives

• Compliance through databases• Rehearsal of Concept (ROC) Drill

– How the Services work together

• Interim and Long-Term Goals– MSIR (MEDCOM System Inventory Repository)– Portfolio and Project Management (PPM)Tool

“Uniting Technology and Healthcare”

IT Portfolio Management

• What is IT Portfolio Management?– A method aligning IT projects with business goals to

deliver capability– Projects are managed in an integrated portfolio to

rationalize the delivery of total capability– Presents picture on what is the “required” number of

systems to deliver capability– Dependent on strong management and influence by

Subject Matter Experts who know which capabilities are required

– Allows for an alignment of resources based on the functional capabilities to be delivered in the portfolio

4


• Per the DODD 8115.01 IT Portfolio Management, Navy Medicine is working on moving towards a capability based portfolio – Effort has been made to align all items within

DADMS to a capability• Working on this alignment with the Functional

Managers

– All capabilities will be aligned to the Navy Medicine Mission

5


Maturity Model

6


Where are we now?

7

8

Compliance

• DHP SIRT

• DADMS

• SDLC• IPR

8“Uniting Technology and Healthcare”


What is the DHP SIRT

• Web-based tool

• Central repository for:

– Compliance

– Investment information

• Organization’s portfolio management and certification activities

– Feeder system to DITPR

• Developed by TMA to collect information for DHP-funded systems

• DHP systems are required to be reported per the Office of the Secretary of Defense (OSD), the Office of Management and Budget (OMB) and Congress

9


What is DADMS?

• The Authoritative Data Source (ADS) for DON application and database portfolio management

• A web-enabled registry of Navy and Marine Corps systems/applications, and their associated data structures

• An enterprise service that supports DON CIO mission and functions

• An 18 October 2002 DONCIO Memorandum designated DADMS as an Authoritative Data Source citing references (a) and (b):

– SECNAV Instruction 5000.36, “DON Data Management and Interoperability,” of 01NOV01– Under Secretary of the Navy memo, “Designation of DON Functional Area Managers,’ of 14MAY02

• To facilitate the objectives of references (a) and (b), the memorandum established DADMS as the Authoritative Data Source (ADS) for DON IT and National Security Systems applications, database inventory and IT Systems Registration.

10


DADMS as a Baseline Portfolio

• DADMS is Navy Medicine IT Software Inventory and Baseline Portfolio

• DADMS is required by SECNAVINST 5000.36A • Each FAM is a Portfolio Manager for the

systems/applications within its portfolio• Operational Activity Taxonomy can provide an

outline of functional capabilities that are required by the FAMs

• DADMS provides a solid first step by creating a system inventory and allowing for a high-level functional mapping

11

12

Tri-Service Working Group

• Goals – Consolidated portfolio– Capability mapping

• Throughout January we were placing all systems and applications into like buckets

• Rehearsal of Concept (ROC) Drill– Early Feb

12“Uniting Technology and Healthcare”

Contact Information

• Presenter’s name• Presenter’s email• Presenter’s telephone #


15

Questions


16

Once your Navy Days 11 presentation draft is complete, please follow the naming convention and version control instructions below: 1. File name begins with Navy Days 11 plus the name of your session then the date of submission in a mm_dd_yyyy format then the word Draft, e.g., ND11_Fixing the World Via Powerpoint_11_15_2010_Draft. 2. Each time the draft is revised, a version number is added, e.g., ND11_Fixing the World Via Powerpoint_11_15_2010_Draft_V1; ND11_Fixing the World Via Powerpoint_11_15_2010_Draft_V2, etc. 3. When the final version of the presentation has been approved, replace the word Draft with Final. 4. With any changes made to the Final, begin the versioning process at 1 again, e.g., ND11_Fixing the World Via Powerpoint_11_15_2010_Final; ND11_Fixing the World Via Powerpoint_11_15_2010_Final_V1. 5. Save the file in MS Powerpoint 97-2003 and 2007 to accommodate the reviewers' operating systems.


portfolio management gary stevens and craig palmer

Documents