Consulting Firm proposes to conduct a discovery phase to define a new global file services architecture for Potential Client. Key deliverables include documenting application and business process dependencies, requirements, conceptual solution options, and a target state architecture. Consulting Firm will analyze solutions against requirements and provide recommendations to facilitate vendor selection and migration planning to eliminate dependencies on Novell by July 2016.

1. Enterprise File Services
Discovery Phase
November 13th, 2014

2. 2
• Consulting Firm Discovery Approach
• Key Deliverables
• Preliminary Schedule
• File Service Solution Development Leadership Structure
• Sample Consulting Firm Team Members and Experience
• Appendix
• Enterprise File Services Requirements Framework
• Preliminary Vendor Positioning
Proposal Outline

3. 3
Consulting Firm Discovery Approach
Consulting Firm Proposes to Accelerate the Definition of a new Potential Client Global File Services Architecture
Consulting Firm proposes to conduct requirements gathering through interviews with stakeholders and through detailed
discovery activities:
• Consulting Firm will gather and document application and business process dependencies on global file shares in
scope. Potential Client wishes to eliminate dependencies on Novell by July, 2016.
• Consulting Firm will gather and document key business, application, and technical requirements for the new
enterprise file services architecture
• For each business and technical requirement, Consulting Firm will establish, with Potential Client representatives,
the relative importance or priority of the requirement: must have; important to have; nice to have or similar simple
scale
• For each requirement needed to achieve required functionality, Consulting Firm will map solution options engaging
internal Consulting Firm and Potential Client SME’s, third party partnerships, and independent research
organizations that are part of Consulting Firm’s knowledge and research capabilities
• For each solution option, Consulting Firm will provide degree of solution fit (against the requirements), estimated
high-level pricing, timing, pros/cons, risks, technology and other impacts, and other recommendations
• Consulting Firm will define, with Potential Client representatives, candidate architectures based on a subset of
solution options for deeper evaluation
• With Potential Client representatives, Consulting Firm will document a target state architecture and any required
variations
• Consulting Firm will develop a plan for the POC, pilot, and deployment for the selected solution vendor(s).
The Outcomes
The result of this exercise will be a set of facts, analyses, and options that results in:
• a quality solution decision
• a path to realization of a defined target state architecture
• a basis for a vigorous execution strategy

4. 4
Key Deliverables
Deliverables
• Plan Documents
• Current State Architecture
• Discovery Project Plan
• Dependency Document
• application and business process
dependencies for approximately
500 Novell volumes (globally)
• Conceptual Solution Options socialized
with stakeholders
• Requirements Document of applicable
business, application, technical, and
security/regulatory requirements
Discovery Vendor Selection
Target State Architecture and
Planning
Potential Client seeks a solution that will transform File Services, specifically those file services based on Novell, in order to
get to one global solution. Consulting Firm will assist in requirements and dependency discovery and will produce
deliverables to facilitate the project; team meetings, status meetings, management updates, and stakeholder alignment.
Below is a summary of what we believe are key deliverables required by Potential Client to successfully complete this
assignment.
Deliverables
• Target State Architecture for File
Services in the context of applicable
strategy and vision
• Document small / medium /
large solution variations
• Document cross-impacts to
other deployed technologies,
processes, or programs
• Implementation and Migration Plans
for POC, Pilot, and Deployment (to
follow)
Deliverables
• Solution Map of market alternatives in
the file services space with specific
applicability to Potential Client
requirements
• Solution Options (top x)
• Assessment of requirements
coverage for each solution
• Analysis of solution options and
documentation of differences
• Cost, risk, pros/cons solution fit
• Executive Presentation for Potential
Client management team
• RFI/RFP support, if required
Phase 1 Phase 2

5. 5
Preliminary Schedule
(to be adjusted based on start date)
VendorSolutionSelectionDiscovery
1. Assess Application and Business
Process Dependencies for
approximately 500 Novell volumes
(globally)
3. Conduct Interview-based
requirements gathering from identified
stakeholder group representatives and
based on applicable architecture
documentation
4. Develop conceptual architecture
options based on Consulting Firm
provided starter templates. Select Top
(x) vendors
5. Assessment of requirements coverage
for each solution (Top x)
6. Executive Presentation for Potential
Client management team with
supporting documentation
Activities
Executive
Presentation
Plan
Documents
0
0. Prepare Project Plan and review all
existing Potential Client documentation.
Define Stakeholders
Requirements
3
January April June…February March
Phase 1 Phase 2Gain Stakeholder
Alignment
6
Dependency Mapping (Global)
1
Arch
Options
Requirements
Mapping (Top x)
4
5
RFI/RFP/RFQ Process 7. Assist Sourcing team with RFP/RFQ
8. Deliver Technical Architectures, Bill of
Materials, and Migration Project Estimate
and TCO of solutions from responding
vendors
9. Deliver Project Roadmap for Migration
elimination of Novell Globally
7
Migration &
Implementation
Planning
9
8

6. 6
File Service Solution Development Leadership Structure
Executive
Governance
Strategy,
Organization, and
Cross-Functional
Decisions, Program
Executive Oversight
Steering Committee
Approve Solutions and Recommendations, Mobilize Resources, Overcome
Barriers, Secure Buy-in, Drive Direction of Overall Program
Program Management
XXXX
IT Oversight, Review Solutions and Recommendations,
Issue Coordination and Elevation
Regional Business
Leaders,
Industry &
Potential Client
SME Advisor
Represent Business
Priorities, Schedules,
Operating Windows,
Dependencies &
Constraints
Advisory
Dedicated
File Services Solution
Development Subject
Matter Expert Advisors
XXXX, Research Team
Consulting Firm File Services Solution
Development and Deployment Experts
Consulting Firm Principal
Consulting Firm Associate
Delivery Quality and
Executive
Communication
Consulting Firm Account
Manager

7. 7
Appendix

8. 8
Enterprise File Services Requirements Framework
Security
• AD Integration
• 2-factor
authentication
• PKI Integration
• Storage Encryption
• Transfer Encryption
Mobile Security
• Mobile Encryption
• Mobile Remote
Wipe
Deployment Options
• Cloud Deployment Option
• Hybrid Deployment Option
• On-Prem Deployment Option
• Use Leading Cloud Options
Storage Options
• Use any CIFS Share
• BLOB Storage Option
• File Size Limits
Client Options
• Windows Client
• Mac Client
• Mobile Client
• 3rd Party FTP/SFTP
• Supports WebDAV
Clients
Client Integration
• Outlook Integration
• SharePoint
Integration
• FileShare Integration
• Novell FileShare
Integration
Lifecycle and Compliance
• Rights Management
• Content Expiration
• Legal Hold
• e-Discovery
• ECM / Document Management
• User Activity Auditing
Desktop Mobile
User Experience

9. 9
Preliminary Vendor Positioning
Sharefile EMC
SyncPlicity
OneDrive
Business
Dropbox
Enterprise
Box.net Accellion
Deployment
Storage
Security
Mobile
Security
Client Options
Client
Integration
Lifecycle &
Compliance
Branding
~100% ~75% ~50% ~25% ~0%
Legend: Degree of Requirements Alignment

10. 10
CASE STUDY: Delivering “Day 1” Effectiveness through End-User
Services Transformation
Leading United States beverage distributor
Business Drivers
• The merger of three companies would produce one of the nation’s
largest beverage distributors
• Given application and business process dependencies on file services
and email, the goal of “One Company” Collaboration on Day 1 meant
that Directory Services, E-Mail, and File Services needed to align to an
agreed target state, including migration away from Novell-based Email,
Directory, File and Print Services in the case of one “legacy” company.
Results
Following behind-the-scenes transformation, scripted weekend
conversions provided “Day 1” collaboration capabilities using a
new Windows Active Directory, Windows File Services, and
Exchange-based Email. End Users were presented with a new
logon on the day of their legacy company’s conversion, along with
access to historical email and file services on the new platform.
Approach
• Developed technical approach to gain agreement from the executives
of each legacy company
• Conducted detailed target state architecture planning including low-
level design and capacity planning for target platform
• Selected enabling technologies for interim Directory and File services
synchronization
• Conducted detailed discovery of file servers, print queues, and email
services including account and dependency mappings
• Built a representative POC environment for script creation and testing
• Deployed script to transform user access and copy email over
conversion weekend Microsoft DSS Syncs User Accounts
Migration Factory Copy and Sync of Files
Platform Sync Process

11. 11
CASE STUDY: Insurance Brokerages File Server Consolidation
Results
Created reference architecture, functioning DMS POC,
consolidated document-related workstreams into master portfolio,
drove platform stability and maturity and informed support
models.
Approach
• Worked with representatives from business and compliance teams to
define the target state architecture
• Reviewed application infrastructure and advocated for more robust
support model
• Worked with IT to define a tiered storage model and recommended
adjustments to architecture design process
• Developed taxonomy and integration points across CRM and LOB
applications
• Reviewed branch location network capabilities to ensure
development model addressed low bandwidth needs
• Lead project through development, POC and into pilot and developed
UAT strategy to ensure business needs alignment
Leading US Healthcare Insurance Brokerage
Business Drivers
• Internal compliance demands and inability to meet them required a
platform that allowed for more robust legal hold and ediscovery
capabilities
• Need for workflow to increase efficient collaboration with offshore
colleagues
• The need for standard client file practices to ensure the smooth
transition of a client from one branch to another
• Be able to centralize and justify storage costs and simplify lifecycle
management
Web Application:
Foundations defined at Web Application level and made available to each Site Collection:
•Taxonomy: Fields, Base Content Types (features activated on each Site Collection)
•Security Policy: Base Security Groups (features activated on web app level; properties defined at SC level)
•Timer Jobs: Example: QCS Timer Job that places documents in Branch site collections
•Branding: “Look and feel” as well as some navigation elements
Site
Collectio
n: Doc.
Mgmt.
DMS
workflow
s
Site
Collection:
Branch
Example:
Boston
•QCS
content
•DMS
content
Site Collection:
Niches
•Niches content
types instances
•Navigation
•Forms
Managed Path: /dms/Branches
Managed Path:
/Publishing(?)
Farm
•Taxonomy: Enterprise Keywords and Term Sets
Managed Path:
/Niches/
Site
Collection:
Branch
Example:
Boston
•QCS
content
•DMS
content
Gallagher
SharePoint
Document
Storage
BenefitPoint
GBS User
Access Analysis
Documents
SharePoint
Workflow
Email Quote Response
Offshore User
Insurance Carrier
Access Quote Documents
Initiate and
Update Workflow
Update Workflow
Plan Data Entry
Email Quote Request
XiDocs