170 likes | 307 Views
Portal Infrastructure as a Shared Service. Bob Nevins, Director bob.nevins@state.ma.us 617-626-4450. What drives shared services?. Fiscal realities Shrinking budgets Reduced staffing Re-usability All parties benefit from innovation Single view of government Consistency for the customer
E N D
Portal Infrastructure as a Shared Service Bob Nevins, Directorbob.nevins@state.ma.us617-626-4450
What drives shared services? • Fiscal realities • Shrinking budgets • Reduced staffing • Re-usability • All parties benefit from innovation • Single view of government • Consistency for the customer • Extensibility • Ability to extend vertically and horizontally
What were the drivers of Mass.Gov? • Navigation by audience and topic, not government structure • Single gateway to multitude of services • Increased visibility of transactions • Corporate look and feel, simple navigation • Separate content from presentation • Ease of maintenance (and migration) • More centralized approach to governing
The portal stood our existing business process on its head • Centralizedpublishing at enterprise level -- content pushed to web by ITD, not agencies • Centralizedpublishing at agency level -- content maintained by programmers, not subject matter expert Before • Decentralized publishing standards and practices for 100s of agencies = 100s of unique websites = 100s of unique navigation schemes= 100s of experts = 100s of toolsets • Costly to maintain, chaos for users
Centralized publishing standards and practices for 100s of agencies = One portal, a handful of subportals = One navigation scheme= One team of experts and community of content authors= One toolset Diminishing costs to maintain, simple for users The portal stood our existing business process on its head • Decentralizedpublishing at enterprise level -- content pushed to web by agencies, not ITD • Decentralizedpublishing at agency level -- content maintained by subject matter experts, not programmers After
Mass.Gov (enterprise top level) Navigation by audience and intention, while retaining some navigation by org. structure Emphasis on transactions Pages composed of reusable, recombine-able modules with multiple display attributes Feature story to promote high visibility content, keep site fresh Database-driven repository for content User-friendly interface for content authors
Health & Human Services Navigation by audience and intention, while retaining some navigation by org. structure Emphasis on transactions Pages composed of reusable, recombine-able modules with multiple display attributes Feature story to promote high visibility content Database driven repository for content User-friendly interface for content update by contributors Access to Virtual Gateway for Human Services Going from 18 websites, to one sub portal
Consumer Affairs & Business Regulation Navigation by audience and intention, while retaining some navigation by org. structure Emphasis on transactions Pages composed of reusable, recombine-able modules with multiple display attributes Feature story to promote high visibility content Database driven repository for content User-friendly interface for content update by contributors Going from 8 websites, to one sub portal
Governor’s Office Feature story to promote high visibility content Database driven repository for content User-friendly interface for content update by contributors Streaming video Archiving of press releases
ITD Employee Only site Database driven repository for content User-friendly interface for content update by contributors Emphasis on transactions Re-usable modules (e.g. search, Homeland Security, news&updates, etc. Category-based navigation
Enterprise Level Mass.Gov Executive Level Governor’s Office, EOHHS, Econ Development, Consumer Affairs, etc Agency Level DTA, DSS, DMR, etc Sub-agency Level ITD Empl. site Portal Structure works on various levels
Elements of the portal • Hosting environment • Physical servers • App server and web server software • Network access/bandwidth • Portal software • Content management software • Small centralized portal team • Growing base of expert users, shared toolsets = shared knowledge
VALUE Incremental value of shared service vOLUME COST Yr 1 Yr 4 Yr 2 Yr 5 Yr 3 Yr 6
Wrap up - Benefits of Shared Services • Build once, use many • Distribute cost across entities and over time • Shared tools prevents “job lock” • Promotes “one-enterprise” culture
Questions? Bob Nevins, Directorbob.nevins@state.ma.us617-626-4450