1 / 11

Garbage In, Garbage Out: IM/IT Requirements Process

Garbage In, Garbage Out: IM/IT Requirements Process. Col Benny Merkel CIO, Air Force Medical Service 3 May 2002. Overview. Problem #1, MHS Requirements Process Problem #2, AFMS Requirements Process Symptoms Recommendations. Problem #1, MHS Requirements Process.

washi
Download Presentation

Garbage In, Garbage Out: IM/IT Requirements Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Garbage In, Garbage Out:IM/IT Requirements Process Col Benny MerkelCIO, Air Force Medical Service3 May 2002

  2. Overview • Problem #1, MHS Requirements Process • Problem #2, AFMS Requirements Process • Symptoms • Recommendations

  3. Problem #1, MHS Requirements Process We (i.e., the AFMS) have little to no involvement in the MHS require-ments (i.e., capabilities) process which is weak at best.

  4. MHS IM/IT Program Capital Investment Process Functional Integration Work Group (05/06 Functional Experts) Army Navy Air Force TMA CIOsReview Army Navy Air Force TMA Integrate and prioritize functional requirements Optimization TeamReview Requirements • Scoring Criteria (Value/Risk) • Readiness • Life Cycle Mgmt • Fed/DoD Regs • Program Continuity • Return on Investment Army Navy Air Force TMA Resource ManagersReview Prioritized requirements Clinical Requirements Resources Requirements MHS Optimization Plan Force Health Protection TFWG ------------- TFSC ( 05 / 06 ) ( 07 ) MHS IM/ITInvestmentPortfolio Military Medical Readiness Logistics Requirements Theater Requirements MHS Strategic Priorities RM/CIO/OT Unified Review (06/GS-15)Review and endorse requirements and recommend portfolio EI/DS Requirements Infrastructure Requirements Program Executive Office, MHS IT Army TMA Execute approved IT program MHS Information Management Proponent Committee (08/SES)Ensure alignment with strategic objectives and approve portfolio Navy Air Force MHS IM/IT Integrated Investment Portfolio MHS IM/IT Integrated Investment Portfolio Recommended portfolio Approved portfolio Army JS Navy TMA Air Force HA Program Objective Memorandum — Budget Estimate Submission — President’s Budget — Annual Execution POP Health

  5. Requirements & Configuration Management Process 1. IDENTIFICATION AND CLASSIFICATION 2. FEASIBILITY ASSESSMENT IM IM IM Help Desk JROC Approval Process Prepare and Validate ORD • Classify • Assign • Review • Coordinate Dev, DT&E OT&E IM Web Site Doctrine No ORD IM IT IM Training/ Education Validate and Research Submissions Service/ TMA Initial LCCE & Infrastructure Impact Analysis Assemble Portfolio Approved ORD • Submissions: • New Requirements • SCRs • SIRs Materiel SCRs Strategic Operational Tactical Organi- zation MHS Optimization Plan Leader Customer Feedback JHSS 2010 Service Member Legislation 4. REQUIREMENTS DEFINITION, DEVELOPMENT AND TESTING 3. CAPABILITIES APPROVAL IM/IT IT/IM MRSP IM/IT IMPC FIWG • Functional Requirements • Define • Integrate • Analyze Acquire / Develop / Test AIS Solution Deployment, Training, & User Education • Draft Portfolio • Ranked Capabilities Approve Portfolio Other Spiral Develop Yes Implemented AIS Product No Major Changes from Development, DT&E & OT&E Customer Feedback

  6. Problem #2, AFMS Requirements Process We (i.e., the AFMS) have no require-ments process.

  7. Symptoms • MHS Systems That Do Not Meet AFMS Needs • MHS Requirements Creep (No Go-To-Market) • No Integration of MHS/AFMS Requirements (Overlapping MHS/AFMS Initiatives) • No Linkage Between MHS/AFMS Business Objectives and AFMS IM/IT Initiatives • Multiple AFMS Communities of Interest Developing/Deploying Systems (Hobby Shopping) • AFMS Direct Care Dollars Being Spent on IM/IT

  8. Symptoms • No AFMS Life Cycle Costs (No ROI) • Multiple SC/SG Interoperability Issues • Multiple Redundant AFMS Servers/Storage Devices and Software Licenses • Non-Certified, Non-Accredited AFMS Systems (Back Doors) • No AFMS Configuration Control • Questionable Information Integrity (Patient Safety) • Non-Sustainable AFMS Deployed Systems

  9. Symptoms

  10. Recommendation MHS Require- ments Process AFMS Strategic Planning Process AFMS IM/IT Clearing House Process AFMS Group/Board Process MAJCOM CIO IPT Process IM/IT Panel Process

  11. Recommendations • Establish an AFMS Requirements “Clearing House” and Integrate It with the MHS Requirements Process • Decouple AFMS IT Initiative Funding Streams and Channel Through the IM/IT BAG • Develop an AFMS Enterprise-Wide Information Management Architecture

More Related