Cleaned example 1

IT (SITS) Technical Architecture Document
Universal Access Universal Hosting
(UAUH)
(Conceptual Use and Tracking Only)
Project Mana--r:
Prepared by:
Owner: SITS Mana--r Bruce Carr
Version: 1.1
Status: Pre-Charter Requirements Gathering
Date: 9/13/2013
Security Classification Internal
Version Control:
Version
Last
Amended
Date
Amended By Reason for Amendment
1.0 9/13/2013 K. L. Initial TAD creation
1.1 9/13/2013 K. L. Personnel Update
Contributors
Design Contributors
Role In Project Name Company Date
Sr. Project Mana--r 9/13/2013
SITS Project Mana--r – Team
Lead
Sr. Network Architect
Infrastructure Architect
Sr. Security Architect
Sr. Web Design Engineer
Web Design Engineer
Data Center Virtualization
Engineer
Distribution for comments and information:
Distribution
Role In Project Name Signature Date
SITS Mana--r Bruce Carr 9/13/2013
Sr. Project Engineer M.S. 9/13/2013
Printed on: 09/03/2015 Pa-- 1 of 9
/mnt/temp/unoconv/20150309193206/4408cbbc- 4bc8-4cc2-a34d-a781b30b8827- 150309143206- conversion-gate01.doc

1. INTRODUCTION
1.1 Background and Concept
The Universal Access Universal Hosting (UAUH) initiative is a concept
designed by the -- IT SITS Mana--ment Team aimed at providing an application
access component to a variety of internal -- customers in a secure
environment. This secure access would allow -- Sales and Marketing internal
customers the ability to offer controlled and secure access to select
applications by external -- customers and potential customers.
The new UAUH component concept has required extensive background
research regarding technological feasibility, -- Security policy, Federal HIPPA
requirements, Risk identification, Federal and -- Export Control policies and
regulations, Licensing and -- intellectual property protection, -- technology
stack compatibility, scalability, and adherence to all -- “Critical to Quality”
(CTQ) and “Critical to Compliance” (CTC) standards. These policies,
requirements, and regulations are currently being investigated.
1.1.1 Business Objectives
The --neral business objective of the UAUH initiative is to provide the -- Sales
and Marketing Team, and other select -- internal a--ncies, a controlled and
secure environment in which to demonstrate, and allow evaluation of, --
Products by both off-site current and potential external -- customers. This
access, by external customers or potential customers would be achieved by
disallowing unauthorized access to the -- internal network or system. The
current -- policy requires that Sales and Marketing personnel remain on-site
and in the presence of all product demonstrations and evaluations. The UAUH
component as proposed, would allow both current and potential customers the
ability to evaluate -- Products beyond the initial -- HC Sales and Marketing
demonstration without -- oversight.
1.1.2 Business Principles
The business principles to be applied re: UAUH reflect the perpetual
philosophy of the -- SITS Team’s mantra that requires -- Technology integrity
and usa-- throughout the business.
1.1.3 Project Objectives
The UAUH initiative is currently in concept mode and should not be viewed as
an active project. However, this review is intended to present relevant
findings that relate back to and directly support the business objectives.
Printed on: 09/03/2015 Pa-- 2 of 9

1.2 Scope and Application
The -- SITS Team will contribute IT expertise and services to the -- Sales
organization to sustain and enhance -- Healthcare product demonstration
capability. This capability may include installation of the UAUH component
including functional database, database servers, server maintenance, and
operating systems, backup, business continuity planning, and maintenance.
The UAUH component will follow the IT standards and guidelines as prescribed
and required by -- Corporate policy. The -- SITS Team will work in tandem
with the -- Sales Team and Application Support Team (AST) to insure that
product demonstration reliability, ease-of-use, and customer service guidelines
are followed as provided by pre-approved Service Level Agreement(s) (SLA).
The -- SITS Team will insure that all consultant personnel adhere to both
Federal and -- policy requirements and regulations.
1.2.1 Scope
The UAUH initiative is not an active project, but rather an exercise in
research, feasibility, and investigation into stakeholder and VOC requirements,
risk assessment, and should onlt be view as a “concept” at this point. The
following deliverables may be considered.
• Current Customer (end user) requirements
• Prospective customer (end user) requirements
• Funding (BUC & ADN) approval
• UAUH location
• Project Charter development
• Project Mana--ment Plan (Phasing)
• Statement of Work
• Work Breakdown Structure
• Project Time Mana--ment
• Resource Planning
• Communication Planning
• Service Level Agreements (SLA’s)
1.3 CTQs / CTCs
1.3.1 CTQs (Critical to Quality)
The proposed solution regarding UAUH functionality will be constructed via
set forth by the Information Technology Infrastructure Library (ITIL) and by
--neral Electric Infrastructure policy and guidelines.
Printed on: 09/03/2015 Pa-- 3 of 9

1.3.2 CTCs (Critical to Compliance)
All audit requirements; legal regulations, security regulations and constraints
will be in compliance with SOX regulations if applicable, -- and Federal Security
and Export Control regulations as well as security consideration regarding --
Intellectual Property and issuance of appropriate non-disclosure agreements
(NDA) where applicable.
1.4 Compliance Considerations
See 1.3.2 above
1.5 Project Documentation Cross- Reference
Not applicable at this time
2.0 Overview of Options and High Level Component Design.
Pending
2.1 --neral Overview of Solution and Options
Pending
2.2 High Level Risk Identification
Risk Priority Comments Date
Temporary login’s
could be shared by
legal assignees and
unauthorized personn el
Unauthorized License
usa- -
Intellectual Property
2.3 Compliance and Security considerations
A full -- security review of the chosen solution is required. Temporary
licensing limits and authorized usa-- levels are diverse with respect to
each individual application .
(CTQ assessm e nt of each solution pending)
Critical To Quality
Requireme nt
Solution 1
Compliance
Solution 2
Compliance
Notes
Totals:
Printed on: 09/03/2015 Pa-- 4 of 9

2.4 Assumptions, Constraints and Dependencies
Issue Risk
Level
Mitigate / Avoid / Transfer
/Accept
Assumptions
TBD
Constraints
-- Security policy
Funding
Resources
HIPPA Regulations
Dependencies
(Logical
Relationships)
TBD
Totals:
Printed on: 09/03/2015 Pa-- 5 of 9

3.0 Architecture Recommend ations – [Technical Architect
Team]
Technical
Position
Assigned SME Comment Date
Sr. Security
Architect
Data Center
-Virtualization
Sr. Web Design
Architect
Sr. Network
Engineer
Stora-- Engineer
Printed on: 09/03/2015 Pa-- 6 of 9

3.1 Architecture scoring matrix – Some scoring questions to be
revised for UAUH
Solution: UAUH -1
Strengths:
Weaknesses:
Solution: UAUH -2
Strengths:
Weaknesses:
Solution: UAUH -3
Printed on: 09/03/2015 Pa-- 7 of 9
Critical factors of
selection
Scoring process 9,3,1.
Top rating = 9 Weight
Solutio
n
1
Solutio
n
2
Solutio
n
3
Tried and tested
The solution has been used before
& Works to your needs
Speed of Delivery
Solution can be Implemented in
Timescales required
Cost
Low cost of hardware, software
and licenses
Ease of
implementation
Delivery to -- requirements
in a timely manner
Meets Architecture
Req. Solution will fit with future IT strategy
Compliance (Six
considerations)
This solution does not have any SOX
issues
Testing Rigour and
Tools Testing will be straight forward
Technical Clarity of
solution
Clear and understandable –
Simplification
Resilience
Automatic failover or recovery within
Business SLA’s
Availability
Solution can run 24 * 7 or to required
timings
Technology stack
compatibility
Best practice solution in line with
proposed
-- Technology stack
Mana- -ability
SLA’s in place, central location, remote
access for out of hours
Scalability Can cater for future and current volumes
Performance
Meets required Speed of response
& can support all required users
Technical support
Can easily be supported in house
without
the need for further training
Sub Total

Strengths:
Weaknesses:
_______________________________________________________________________________________________
3.3 Recommen d e d Solution (From Project Team)
To Be Determined
3.4 Proof of Concept
Not applicable at this time
4.0 Current State vs. Future State (AS- IS/TO- BE)
Diagram to be inserted when available
4.1 Physical Infrastructure Diagram
TBD
5.0 Detailed Specification
TBD
5.1 Detailed Component Design and Build Approach
TBD
5.2 Capacity Analysis
Not Applicable at this time
5.2.1 Database Backup & DR Requirem ents
As per -- Standards and Best Practices
5.3.2 Database Capacity & Performance
Not Applicable at this time
6.0 Security Requirements
All legal regulations, security regulations and constraints will be applied
and in compliance if applicable according to -- and Federal Security and
Export Control regulations.
7.0 Resilience / Points of Failure
TBD
8.0 Availability
Printed on: 09/03/2015 Pa-- 8 of 9

System maintenance, availability, and support will follow pre-approved
Sales, AST, and -- Service Level Agreement (SLA)
9.0 Infrastructure Specification
TBD
9.1 Stora- - Requirem ents
TBD
9.2 Hardwar e specifications
TBD
9.3 Network & bandwidth
TBD
9.4 Data stores/ database s
TBD
10.0 Backup Requirem ents
TBD
11.0 Chan- - Control and Mana- -ment
TBD
12.0 Service Level Agreem ents (SLA’s)
Service Level Agreements will be established between Customers and
Support TBD
13.0 Resource Projections
13.1 Personnel Staffing
TBD
Printed on: 09/03/2015 Pa-- 9 of 9

Cleaned example 1

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (12)

Similar to Cleaned example 1

Similar to Cleaned example 1 (20)

Cleaned example 1