One of our internal customers has the following use case. I know about all the integration points AppMon has been Splunk, Jenkins, Coradiant, LoadRunner, etc. However, I'm wondering if there are any known use cases where dT has been used to gather information useful for capacity planning. Please see the verbiage below for details. Thank you in advance for your reply. Rob Herring
EPIC Description :
As an XTRAC professional services engineer or performance engineer, it is very important to understand the system capacity for model definitions and model instances planned to be deployed and run on any system. This effort will generate a tool and analysis that allows the engineer to plan for future needed capacity according to model definition and topography.
Professional Services Engineers
Customer Service Engineers
Business Value / Impact :
The ability to plan for capacity for any software offering is paramount in the successful engagement and delivery of software as a service. this epic will provide for a tool that will allow effective capacity planning for PM/Workflow through analysis of the process definitions and predicted volume.
At the current situation, Mike O., Don H. and others remain hesitant to bring on additional business for fear that the system may not handle the additional planned capacity. A capacity tool would allow a high level of confidence for delivery.
This would allow for the answer of the following Big 3 Capacity Questions:
1. Determine Service Level Requirements
2. Analyze Current Capacity
3. Planning for the future
Scenarios / Use Case(s) :
As modeled from 
1) Determine Service Level Requirements
2) Analyze Current Capacity
a. Measure Service Levels and Compare to Objectives
compare the measurements of any items referenced in service level agreements with
their objectives. This provides the basic indication of whether the system has adequate
b. Measure Overall Resource Usage
Next, check the usage of the various resources of the system (CPU, memory, and I/O
devices). This analysis identifies highly used resources that may prove problematic now
or in the future.
c. Measure Resource Usage by Workload
Look at the resource utilization for each workload. Ascertain which workloads are the
major users of each resource. This helps narrow your attention to only the workloads that
are making the greatest demands on system resources.
d. Identify Components of Response Time
Determine where each workload is spending its time by analyzing the components of
response time, allowing you to determine which system resources are responsible for the greatest portion of the response time for each workload.
3) Plan for the Future
a) Determine Future Processing Requirements
forecast what your organization will require of your IT systems in the
b) Plan Future System Configuration
Once you know what to expect in terms of incoming work, you can use TeamQuest Predictor
to determine the optimal system configuration for meeting service levels on into the future.
EPIC Acceptance Criteria :
1. Determine service level requirements
a. Define workloads
b. Determine the unit of work
c. Identify service levels for each workload
2. Analyze current system capacity
a. Measure service levels and compare to objectives
b. Measure overall resource usage
c. Measure resource usage by workload
d. Identify components of response time
3. Plan for the future
a. Determine future processing requirements FPCMS & FCC next 6 months.
FPCMS Performance Requirements (1427841)
b. Plan future system configuration
Hi Rob, just saw your post, wondering if you still need capacity prediction from Dynatrace data? We (Performance Assurance Ltd, http://www.performance-assurance.com.au/ ) are a Dynatrace technology partner with a performance modelling solution using Dynatrace data, so may be able to assist. My email is: email@example.com