It is noted that all the FSM customers has their environments in cloud , is limited to set up only 3 environments.
01) Is there any specific reason for that?
02) Is this same for the customers who has their environments hosted on premises ?
Solved
FSM environment Setup
Best answer by ChristineLaVoi
What Mike says is true, there is a cost to environments, however, we have worked with customers when there is a need for additional environments; those can be made available at a cost.
On premise customers may create a 4 environment to test either initial data loads or to test conversions. The number environments is really controlled from an on-premise standpoint on what the customer needs at that point in their life cycle; our services organization helps determine what is logical for their implementation.
The true key to any number environments is control of patching and configuration levels as customers who lose control of their environments can end up with significant costs to their project just troubleshooting what is different in environment a vs environment b vs environment c with the end result turning out to be something as simple as a new screen configuration, business rule or a change in an Application Parameter.
View originalOn premise customers may create a 4 environment to test either initial data loads or to test conversions. The number environments is really controlled from an on-premise standpoint on what the customer needs at that point in their life cycle; our services organization helps determine what is logical for their implementation.
The true key to any number environments is control of patching and configuration levels as customers who lose control of their environments can end up with significant costs to their project just troubleshooting what is different in environment a vs environment b vs environment c with the end result turning out to be something as simple as a new screen configuration, business rule or a change in an Application Parameter.
+1701) Yes. Azure subscriptions can be costly. The Managed Cloud offering uses the same essential structure for all FSM Managed Cloud customers and is the 'default' where we can offer a price that is expected to be acceptable to a customer. The Cloud Services Center team is commissioned to manage 3 environments for each FSM customer.
As our Cloud program evolves, this could certainly change, and a more 'a-la-carte' model could emerge. I believe the current model of 3 environments is based on expected 'average customer need' and price point.
02) For on-premise customers, there is still a cost for each environment they maintain, but the ability to change this on a whim is their choice to make. That's the upside, but they have to do everything themselves and absorb all the costs and risks for maintaining however many environments they stand up.
As our Cloud program evolves, this could certainly change, and a more 'a-la-carte' model could emerge. I believe the current model of 3 environments is based on expected 'average customer need' and price point.
02) For on-premise customers, there is still a cost for each environment they maintain, but the ability to change this on a whim is their choice to make. That's the upside, but they have to do everything themselves and absorb all the costs and risks for maintaining however many environments they stand up.
There is only one truth.
What Mike says is true, there is a cost to environments, however, we have worked with customers when there is a need for additional environments; those can be made available at a cost.
On premise customers may create a 4 environment to test either initial data loads or to test conversions. The number environments is really controlled from an on-premise standpoint on what the customer needs at that point in their life cycle; our services organization helps determine what is logical for their implementation.
The true key to any number environments is control of patching and configuration levels as customers who lose control of their environments can end up with significant costs to their project just troubleshooting what is different in environment a vs environment b vs environment c with the end result turning out to be something as simple as a new screen configuration, business rule or a change in an Application Parameter.
On premise customers may create a 4 environment to test either initial data loads or to test conversions. The number environments is really controlled from an on-premise standpoint on what the customer needs at that point in their life cycle; our services organization helps determine what is logical for their implementation.
The true key to any number environments is control of patching and configuration levels as customers who lose control of their environments can end up with significant costs to their project just troubleshooting what is different in environment a vs environment b vs environment c with the end result turning out to be something as simple as a new screen configuration, business rule or a change in an Application Parameter.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.