and forms contained within the Proposal Kit helps me organize and accurately bid jobs for clients. Using the Proposal Kit is a big timesaver and it limits project creep. Necessary upfront planning is covered by the client interview questionnaire, flowcharts and design tools."
Governance Plan The Governance Plan will serve to provide unified centrally administered approach to records management within Decker Hubbard and Brown. Why we need governance plan The Governance Plan is the road map for the overarching content environment architecture system development process policy and decisions for the Records Management Program. This plan also identifies the area of ownership for Decker Hubbard and Browns information management group and identifies who is responsible for which areas of the Records Management Program. The Governance Plan sets the regulations and rules for the use of records and system environments so that the content to be managed is sustainable and grows in consistent manner that is in line with Decker Hubbard and Browns goals and business requirements. Governance Program Goals The Decker Hubbard and Brown governance plan outlines the content types that will be governed and the organization of the governance model. The plan will detail who will govern what and how the content will be governed.
Governance Structure The Content Committee develops the roadmap and vision for the content management program and insures that the project timelines are socialized and delivered to the organization. The Content Manager insures the stakeholder expectations are managed and communicates any issues and change requirements. The departmental Content Specialist will train other personnel on asset management and provide requirements to business analyst and are the Go To leads for business groups. The CIO is responsible for the architecture and long term support for the content management system. Records Program Committee Reference Program RACI for detailed roles and responsibilities. The Content Governance Committee will meet on monthly basis to review system health and growth rates to track trends and update the roadmap for current and future needs. The roadmap will cover year rolling plan to include business process workflow and automation to increase adaption of the content management program. Contact List Names Responsibilities Executive Sponsor Martha W. McCowan CEO Project Owner Patrick T. Pearson Project Manager Department Managers Content Specialist Jon M. Scott Administration Donna K. Marshall Asset and Facility Management Christine A. Teeter Financial Management Thomas J. Green
Human Resources Management Gregory C. Shafer Information Management Chandra T. Cole Legal Records Neal W. Kehoe Professional Service Gail L. Madrid Sales and Marketing Management Information Technology IT Geralyn L. Hernandez CIO Records Manager Maria L. Everett RM Legal Oscar S. Paulsen Legal Information Stewards or Content Owner Content Managers Cindy J. Cox HR Admin Facilities Judy H. Holloway Finance Legal Pamala J. Meyers Sales marketing prof services Operations Areas governed by the Records Program Item Description Content Stores ServerA ServerB Files and content on servers. Systems SharePoint ECM System and legacy accounting system Applications that generate content. Departments Administration * Asset and Facility Management * Financial Management * Human Resources Management
* Information Management * Legal Records * Professional Services * Sales and Marketing Management Content types to be governed by department. Reference the File Plan for all content types for each department. Standards
Records Related Standards Standard Name Documentation Location IT Server capacity and storage requirements * Supported OS * Supported browsers ServerA Content * Supported file types * Supported applications ServerA Business Content storage locations by department ServerA Regulatory HIPPA CIP and SOX ServerB Guidelines All Content Related Policies and Procedures Policy Name Policy Location Process for developing policies and procedures RACI * File Plan * Stakeholder Management
* Business Case * Road Map ServerA Communication plan Stakeholder Management plan * Stakeholder Communication Log ServerA Change management Change Requests ServerA Internal and external content Content developed by 3rd parties * Content we control ServerA Structured and unstructured content Structured content Master Data * Unstructured content such as invoices or project files and content that is not managed in database. ServerA ServerB
Training Records Training Guidelines and Materials Training Documents Document Location Policies and procedures Content Management Best Practices * Retention Schedules ServerA Systems and applications Use manual * Power User * Administrator Manual ServerB Content specific material Archive File Formats ServerB Infrastructure Records Maintenance Infrastructure Documents Document Location SLA Disaster Recovery
* Upgrade hotfix Schedules * Support Response SLA ServerB Backup Full and Partial Backup Schedules ServerB Disaster recovery Disaster Plan ServerB Monitoring Error log maintenance ServerB Reports System Health monitoring ServerB The development of the Records Policy and procedures and the enforcement of standards should be reviewed managed and updated by the governance committee as outlined above.