90 likes | 189 Views
BCP Federation Overview 11/18/11. BCP Federation History. Pre-2005: Worked on Disaster Recovery initiatives (See Disaster Recovery Journal Vol. 19, No. 2) Spring 2005: Ad hoc conversations between OSU and other IUC members Summer 2005: Informational sessions with IUC members
E N D
BCP Federation Overview 11/18/11
BCP Federation History • Pre-2005: Worked on Disaster Recovery initiatives (See Disaster Recovery Journal Vol. 19, No. 2) • Spring 2005: Ad hoc conversations between OSU and other IUC members • Summer 2005: Informational sessions with IUC members • Fall / Winter 2005: Memorandum of Understanding • February, 2006: Signed contract with vendor • March, 2006: 2-day configuration session • July 1, 2006: Go Live • July 13, 2008: Migrated from LDRPS 9.1 to L10 • 2008 – 2011: Annual “summits”
Participating Institutions • Columbus State Community College • Office of Budget Management for the State of Ohio • Shawnee State University • The Ohio Board of Regents • The Ohio State University • The University of Akron • Wright State University New Orleans, LA Hurricane Katrina, 2005
BCP Federation Purpose • To collaborate, support, and share best practices related to Business Continuity Planning (BCP) • To purchase, customize, and utilize a single instance of a supporting BCP application
BCP Federation Benefits • Save money: Thousands of dollars in savings per institution • Save time and effort: • Piloted, tested, and customized system (ready-to-go) • System administration by OSU • Templates, methodology, and supporting documentation for ALL • Allow for sharing and collaboration
MOU Details – Costs • All members share software costs per percentage of institution’s total operating and non-operating revenues • Future members will pay either: • Percentage of original purchase price and on-going maintenance (based on recalculated total cost per institution’s total revenues) • Cost of additional users licenses • All members share portion of “Super Administrator” costs
MOU Details – Governance • Annual agreement signed by all members • Executive Governing Board representative: one from each organization • One vote per organization; all matters decided by majority vote (as needed) • Any member of the BCP Federation may withdraw at any time; however fee payment must continue for the full term
MOU Details – Change Control • EGB established an initial / baseline LDRPS configuration • Change Control Board representative: one from each organization (Local Admins) • Local Admins constitute a LDRPS Change Control Board (CCB) • All changes that affect any cross-institutional users submitted to the CCB • Each institution is entitled to one vote per institution; all matters decided by majority vote (as needed)
Questions? • Contact Information: • OSU Continuity Management ProgramPhone: (614)247-6166 or (614)247-5360