Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this


  1. 1. Wednesday, October 22, 2008 <ul><li>Records Management Integrated Project Team Kick-Off Session </li></ul><ul><li>1:30 pm – 3:00 pm </li></ul><ul><li>HHS Auditorium </li></ul>
  2. 2. Agenda <ul><li>Agenda Overview: Vision, Goals and Objectives </li></ul><ul><ul><li>Terry Nicolosi, Director, OCIO Office of Resources Mgmt </li></ul></ul><ul><li>Welcome and Acknowledgements </li></ul><ul><ul><li>Charlie Johnson, Assistant Secretary for Resources and Technology </li></ul></ul><ul><li>Records Management Program Status and Future </li></ul><ul><ul><li>Co-Leads: Integrated Project Team (IPT) </li></ul></ul><ul><ul><li>Larry Gray, HHS Departmental Records Officer </li></ul></ul><ul><ul><li>Vickie Robey, CMS Records Officer </li></ul></ul><ul><li>OMB Chief Architect on Enterprise Architecture and Records Management </li></ul><ul><ul><li>Introduction by HHS Deputy CIO John Teeter </li></ul></ul><ul><ul><li>Kshemendra N. Paul, OMB Chief Architect </li></ul></ul><ul><li>Embedding Records Management into Agency Business Processes </li></ul><ul><ul><li>Laurence Brewer, CRM; NARA Director of Lifecycle Management </li></ul></ul><ul><li>Records Management (RM) Enterprise Architecture (EA) </li></ul><ul><li>Quarterly Goals and Objectives </li></ul><ul><ul><li>Mary Forbes, Lead Enterprise Architect </li></ul></ul><ul><li>Next Steps </li></ul><ul><ul><li>Terry Nicolosi, Director of ORM </li></ul></ul>
  3. 3. Vision : HHS will facilitate the quality, coordination and effectiveness of building a Department-wide electronic records management system; Goals : D efine and implement simplified standard processes and standard data definitions for records management; protect the confidentiality and integrity of HHS records while providing appropriate access and availability of these records; Standardize and improve the efficiency of the collection of HHS records, reduce the financial burden storage of HHS resources across the department. Objectives : Meet the NARA Bulletin 2006-02 (government-wide deadline of September 30, 2009) for agencies to identify and schedule all existing records; Meet the EA RM IPT Quarterly milestones for FY 2009. <ul><li>Vision, Goals and Objectives </li></ul>
  4. 4. Assistant Secretary for Resources and Technology Charlie Johnson <ul><li>Welcome and Acknowledgements </li></ul>
  5. 5. Larry Gray, Departmental Records Officer What are we doing? <ul><li>Current and Future of HHS RM Program </li></ul><ul><li>The Department RM Program has taken the lead to standardize Record Keeping Policies, Practices, and Guidelines across the organization. </li></ul><ul><li>Created the HHS Records Management Council. </li></ul><ul><li>Revised RM Policies. </li></ul><ul><li>Documenting the Functions being performed. </li></ul><ul><li>Department Wide-Inventory conducted. </li></ul><ul><li>Cross walk mission statements and organization charts to a Records Schedule. </li></ul>
  6. 6. RM Council (Partnership with IPT) <ul><li>Current and Future of HHS RM Program </li></ul><ul><li>RM Charter requires members to establish continuous program improvement by ensuring that RM issues are addressed in: </li></ul><ul><li>Strategic Planning </li></ul><ul><li>Business Process Design </li></ul><ul><li>Capital Planning and Investment Control </li></ul><ul><li>Solutions Development Lifecycle </li></ul><ul><li>Enterprise Architecture </li></ul><ul><li>Information Security </li></ul><ul><li>E-Government </li></ul>
  7. 7. <ul><li>Current and Future of HHS RM Program </li></ul>Records Officers as the subject matter experts in Records Management play an integral role in the successful transformation to a successful department wide records management program. The Partnership will allow the RM community to push forward with not only the normal end of year requirements but also meet the additional requirements for an Administration change.
  8. 8. <ul><li>Current and Future of HHS RM Program </li></ul>Vickie Robey, CMS Records Officer <ul><li>Working with IT and EA to identify RM processes. </li></ul><ul><li>Pioneered Electronic Filing of E-mail </li></ul><ul><li>Developing E-Recordkeeping Business Process Management (BPM) </li></ul><ul><li>Completed records management piece for a FOIA and Correspondence BPM </li></ul><ul><li>Submitted to NARA our electronic systems inventory. </li></ul>
  9. 9. HHS Deputy Chief Information Officer John Teeter <ul><li>Introduction of OMB Chief Architect </li></ul>
  10. 10. OMB Chief Enterprise Architect Kshemendra N. Paul <ul><li>Enterprise Architecture and Records Management </li></ul>
  11. 11. Embedding Records Management into Agency Business Processes Laurence Brewer, CRM Director, Lifecycle Management Division National Archives and Records Administration
  12. 12. Adapting to the current business environment requires IT & RM collaboration to ensure: A systematic approach to managing records Coordinated records, information, and knowledge management strategies Technology is utilized effectively RM requirements are addressed early in the life cycle <ul><li>Goals </li></ul>
  13. 13. Agency records management procedures do not integrate people, policies, processes and technology well Agency enterprise architectures (EA) do not systemically address records management requirements Agency planning and execution of IT investments often overlooks the value of records management (RM) Systems are often funded, designed and implemented without adequate thought about how those records will be managed over their entire lifecycle <ul><li>Challenges </li></ul>
  14. 14. NARA Bulletin 2006-03 Availability of Federal Enterprise Architecture (FEA) RM Profile, released December 23, 2005 A framework for embedding records management into IT governance and development processes A resource to guide integrating records management seamlessly into agency business processes <ul><li>Strategies </li></ul>
  15. 15. Establish a common Government-wide framework for identifying records management requirements Identify records management issues and requirements and link them to their implementing technologies and business processes Build records management requirements into agency IT governance processes for enterprise architecture (e.g., CPIC, BPD, SDLC) <ul><li>Strategies </li></ul>
  16. 16. <ul><li>Conceptual view </li></ul>
  17. 17. Continue to socialize and implement RM Profile Planning Webinar in early 2009 Leverage related tools and technologies (e.g., Toolkit for Electronic Records, Records Management Services) <ul><li>Next Steps </li></ul>
  18. 18. Laurence Brewer, CRM Director, Lifecycle Management Division National Archives and Records Administration [email_address] (301) 837-1539 <ul><li>Contact information </li></ul>
  19. 19. Records Management (RM) Enterprise Architecture (EA) Quarterly Goals and Objectives Mary Forbes HHS Lead Enterprise Architect
  20. 20. Architecture is the Plan for Realizing Your Vision Gaps
  21. 21. Records Management EA Approach <ul><li>Leverage work of NARA and other federal partners </li></ul><ul><li>Use structured methodology for collection and analysis of segment-related information </li></ul><ul><ul><li>HHS Architecture Development Methodology (ADM) </li></ul></ul><ul><ul><li>Federal Segment Architecture Methodology (FSAM) </li></ul></ul>Provides RM Transition Plan ADM & FSAM Methodology Data Collection Templates Tools Guidelines FEA Records Management Profile NARA Toolkits
  22. 22. EA Quarterly Objectives and Goals: First Quarter (ending December 2008) <ul><li>Identify and Document Current Records Management Business Process Activities </li></ul><ul><ul><li>Review Existing Records Management Business Process Models </li></ul></ul><ul><ul><li>Conduct Stakeholder Interviews </li></ul></ul><ul><ul><li>Develop Current RM Business Process Models Applicable to HHS and all OPDIVs </li></ul></ul><ul><ul><li>Validate Findings with Integrated Program Team </li></ul></ul>IPT Validate and Finalize Develop Draft Models Conduct Stakeholder Interviews
  23. 23. EA Quarterly Objectives and Goals: Second Quarter (ending March 2009) <ul><li>Develop Gap Analysis </li></ul><ul><ul><li>Review Existing Documentation including </li></ul></ul><ul><ul><ul><li>RM Self Assessment Survey Results </li></ul></ul></ul><ul><ul><ul><li>NARA CRF 36 </li></ul></ul></ul><ul><ul><li>Conduct Interviews with OPDIVs to identify Target State of RM </li></ul></ul><ul><ul><li>Develop Gap Analysis Document </li></ul></ul><ul><ul><li>Review and Validate Findings with IPT </li></ul></ul>IPT Validate And Finalize Develop Gap Analysis Document Conduct Stakeholder Interviews
  24. 24. EA Quarterly Objectives and Goals: Third Quarter (ending June 2009) <ul><li>Develop Target RM Business Process Activities </li></ul><ul><ul><li>Incorporate Gap Analysis Findings into Target RM Business Process Models </li></ul></ul><ul><ul><li>Develop Target RM Business Process Models </li></ul></ul><ul><ul><li>Validate Findings with IPT </li></ul></ul>IPT Validate And Finalize Develop Target RM Business Process Models Incorporate Gap Analysis Findings
  25. 25. EA Quarterly Objectives and Goals: Fourth Quarter (ending September 2009) <ul><li>Create RM Segment Transition Plan </li></ul><ul><ul><li>Incorporate Baseline and Target Artifacts Created From ADM and FSAM </li></ul></ul><ul><ul><li>Develop RM Segment Transition Plan </li></ul></ul><ul><ul><li>Review and Finalize with IPT </li></ul></ul>IPT Validate And Finalize Develop RM Segment Transition Plan Incorporate Baseline and Target Artifacts
  26. 26. RM EA Approach – Development of the Transition Plan <ul><li>The RM Segment Transition Plan will: </li></ul><ul><ul><li>Provide HHS an Overview of the Key Elements Necessary to Successfully Transition from the Current State of the Segment to the Desired State </li></ul></ul><ul><ul><li>Identify Cost Saving, Efficient, and Timely Strategies for Transitioning the Segment </li></ul></ul><ul><ul><li>Minimize the Impact on Personnel, Current Operations, and Operating Divisions (OPDIVs) </li></ul></ul>
  27. 27. EA Quarterly Objectives and Goals: Fourth Quarter (ending September 2009) EA Team IPT OBJECTIVE RM TRANSITION PLAN Management Supports Supports
  28. 28. The “So What?” <ul><li>The way we work has changed. </li></ul><ul><li>The way we manage the records of that work has not kept pace. </li></ul><ul><li>Systems are often funded, designed and implemented without adequate thought for the records they create and how those records will be managed across time. </li></ul><ul><li>Critical electronic records can be: </li></ul><ul><ul><li>buried with marginally important information </li></ul></ul><ul><ul><li>difficult, time consuming and expensive to find or worse— </li></ul></ul><ul><ul><li>deleted, destroyed or overwritten before their time </li></ul></ul><ul><ul><li>stored in obsolete formats and no longer accessible </li></ul></ul><ul><li>Business processes with poorly managed records are often more costly, more risky, harder to defend and slower. </li></ul><ul><li>Enterprise Architecture and The Records Management Profile are key to catching up and keeping pace. </li></ul>L. Reynolds Cahoon, 2006
  29. 29. <ul><li>Next Steps </li></ul><ul><li>Sign up for being a member of the Integrated Project Team at our registration table; </li></ul><ul><li>Send me your questions, comments, suggestions regarding IPT at [email_address] ; </li></ul><ul><li>First IPT member working session to be held the week of January 26, 2009 to review and finalize first quarter milestone; </li></ul><ul><li>All presentations and information will be posted on our OCIO Records Management internet site; </li></ul><ul><li>Thank you all for being with us today and thanks to our speakers. We look forward to working with all of you on Records Management. </li></ul>
  30. 30. Terry Nicolosi Director, Office of Resources Management, Office of the CIO Department of Health and Human Services [email_address] (202) 690-6162 <ul><li>Contact Information </li></ul>
  31. 31. Name:___________________________________ Email:____________________________________ Comments, Questions, Suggestions:_________________ ____________________________________________________ ____________________________________________________ ____________________________________________________ <ul><li>Comments, Questions, Suggestions </li></ul>