1 / 12

“ Locutus ” (?) Centralized Experience Project

“ Locutus ” (?) Centralized Experience Project. Overview. Goal. One “experience” for Verio customers and employees Unified starting point All destinations represented in UI Role managed and brandable. User. Role Management / SSO. “FRAMEWORK”

kasimir-harvey
Download Presentation

“ Locutus ” (?) Centralized Experience Project

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. “Locutus” (?)Centralized Experience Project Overview

  2. Goal • One “experience” for Verio customers and employees • Unified starting point • All destinations represented in UI • Role managed and brandable

  3. User Role Management / SSO “FRAMEWORK” (Rendering layer; owner of IA; controls functional visibility) Native Content SSO “Framed Content” Combinations surfaced based on role API

  4. User Role Management / SSO “FRAMEWORK” (Rendering layer; owner of IA; controls functional visibility) Native Content SSO Core framework acts as the over-arching rendering and access control engine. This framework needs to be built to be load-balanced across multi-servers in multiple datacenters. It will be the default go-forward framework for ALL employee and customer interaction. “Framed Content” Combinations surfaced based on role API

  5. User Role Management / SSO “FRAMEWORK” (Rendering layer; owner of IA; controls functional visibility) Native applications will only have access to infrastructure data via REST API calls. Goal: Build applications on same API set customers use; API functionality robustness improves as a side-effect of Verio building more applications that utilize API’s. Native Content SSO “Framed Content” Combinations surfaced based on role API

  6. User Need to make assumption content is NOT Verio developed and may not have ability to support our default look and feel. Examples of content: SharePoint, Signature CP, Satools, Zimbra CP, CMAG tool, etc. Applications will maintain their own access control; ideally via SSO. Role Management / SSO “FRAMEWORK” (Rendering layer; owner of IA; controls functional visibility) Native Content SSO “Framed Content” The IS Team should not integrate applications in a way that makes the IS team a participant in the turn-on or ongoing maintenance of these applications. To eliminate risk and reduce complexity, the aggregation of applications should be kept as simple as possible. API

  7. User Framework will act as “collector” of content under one roof. Users can enter one location and navigate down to any piece of content available to the various roles represented in the CP. Role Management / SSO “FRAMEWORK” (Rendering layer; owner of IA; controls functional visibility) Native Content SSO “Framed Content” Combinations surfaced based on role It will be Jeff Faller’s role to organize the content in the base framework navigation; any new applications needing to be added will be slotted by Jeff and enabled via the role management system. API

  8. Header and horizontal nav owned by centralized framework HEADER HORIZONTAL NAV Workspace and left nav owned by target application “WORKSPACE” LEFT NAV !!! Both header and workspace need to be “brand aware” and have ties into the branding system for customization and localization !!! “Branding” should also be URL-driven so different customers can utilize same framework installation.

  9. User New Starting Point[generic support content](Anonymous) Create New Account “Richer” Experience With Access to More Functionality(Logged In) Nimbus

  10. Built by IT on “anonymous” side of the wall User Built by IT in WordPress. Can this be one framework supporting both states? New Starting Point[generic support content](Anonymous) Create New Account Built by IS; in today’s world this is the “new” backroom with the first application being the new support content Anonymous Registered “Richer” Experience With Access to More Functionality(Logged In) Advanced Support IT System Nimbus Fetch data via API

  11. Goal is to have this functioning as usable beta by May 3rd User New Starting Point[generic support content](Anonymous) Create New Account Anonymous Registered “Richer” Experience With Access to More Functionality(Logged In) Advanced Support IT System Nimbus Fetch data via API

  12. User New Starting Point[generic support content](Anonymous) Create New Account Anonymous Next application DNS CP; work in parallel with additional headcount Registered “Richer” Experience With Access to More Functionality(Logged In) Advanced Support DNS CP Nimbus

More Related