Architecture Assessment and Performance Benchmarking are the two milestones in this phase as it applies to MS CRM technical implementation before sandbox environment installations.
Architecture Assessment Considerations:
A Data Collection Questionnaire to collect information about the customer's existing environment and their deployment goals is usually presented to the client, and is the necessary first step for a successful Architecture Review.
This data collection will vary between customers but some of the typical focus areas involve:
1. Business Requirements: Concurrent users, Web/Outlook clients; Data in core entities, Data in custom entities; Transaction Volumes; Integration points - lead generation systems, other external systems.
2. Network Topology Overview: Visio of the MS CRM enviornment; other information such as remote office location, bandwidth and latency of connections to the remote offices, logical distribution of servers, intgration points are also important considerations.
3. Directory Structure: Single or multiple domains, Single or multiple forests, Relationships or trusts between the domains/ forests, the domains or forests that will have MS CRM users and where MS CRM deployment servers will be located.
4. Required Stack Components: Key components including version and revision levels are important in determining applicability and supportability. Components to review include the SQL Server, IIS, AD, MS Dynamics CRM, MS SQL Server Reporting Services
5. Optional Microsoft Components: Key components to review here should include Windows SharePoint Services/ Office SharePoint Server, Microsoft Biz Talk Server, Microsoft Visual Studio/ Microsoft Visual Source Safe, Microsoft Systems Management Server, Microsoft Systems Center Operations Manager, Other Components.
6. High Availability/ Disaster Recovery: It is important to understand the supported options for high availability specific to MS CRM. General backing & recovery of each MS CRM component can be found here.
7. Non-Production Environments: Identify the customer's requirements for development and test environments.
8. Hardware Inventory: The most important parts of this inventory are the hardware specifications (RAM, processors, OS, disk configurations, processor, etc.) and whether or not the systems are on the WHCL.
A Visio should be presented to the customer for all Core Components required (both production & non-production environments) at the end of this phase, to mark the beginning of the next phase 'Design' in MS CRM Implementations:
Visual Studio / Visual Source Safe
SMS
Other components
Architecture Assessment Considerations:
A Data Collection Questionnaire to collect information about the customer's existing environment and their deployment goals is usually presented to the client, and is the necessary first step for a successful Architecture Review.
This data collection will vary between customers but some of the typical focus areas involve:
1. Business Requirements: Concurrent users, Web/Outlook clients; Data in core entities, Data in custom entities; Transaction Volumes; Integration points - lead generation systems, other external systems.
2. Network Topology Overview: Visio of the MS CRM enviornment; other information such as remote office location, bandwidth and latency of connections to the remote offices, logical distribution of servers, intgration points are also important considerations.
3. Directory Structure: Single or multiple domains, Single or multiple forests, Relationships or trusts between the domains/ forests, the domains or forests that will have MS CRM users and where MS CRM deployment servers will be located.
4. Required Stack Components: Key components including version and revision levels are important in determining applicability and supportability. Components to review include the SQL Server, IIS, AD, MS Dynamics CRM, MS SQL Server Reporting Services
5. Optional Microsoft Components: Key components to review here should include Windows SharePoint Services/ Office SharePoint Server, Microsoft Biz Talk Server, Microsoft Visual Studio/ Microsoft Visual Source Safe, Microsoft Systems Management Server, Microsoft Systems Center Operations Manager, Other Components.
6. High Availability/ Disaster Recovery: It is important to understand the supported options for high availability specific to MS CRM. General backing & recovery of each MS CRM component can be found here.
7. Non-Production Environments: Identify the customer's requirements for development and test environments.
8. Hardware Inventory: The most important parts of this inventory are the hardware specifications (RAM, processors, OS, disk configurations, processor, etc.) and whether or not the systems are on the WHCL.
A Visio should be presented to the customer for all Core Components required (both production & non-production environments) at the end of this phase, to mark the beginning of the next phase 'Design' in MS CRM Implementations:
- Microsoft Dynamics CRM Database (SQL) Server
- Microsoft Dynamics CRM Application Web Server
- Microsoft Dynamics CRM Client
- Storage Area Network or other storage devices
- Optional Microsoft components
- Microsoft SharePoint® technologies / Microsoft Office SharePoint Server
Visual Studio / Visual Source Safe
SMS
Other components
No comments:
Post a Comment