This commit is contained in:
parent
bcf9b57595
commit
f2ba44495f
@ -32,7 +32,9 @@ We have batches running and checking if there are new signals, and we have set u
|
||||
So it is very easy for us now to do that process!
|
||||
|
||||
### Why are you using Data Controller, instead of another approach or tool?
|
||||
We heard about Data Controller from the community, and it seemed like a great fit for our use case - it’s SAS friendly and it’s SAS built and it’s easy to incorporate. The things we really like are the EDIT and APPROVAL process, and the HISTORY of all changes that is built into the product.
|
||||
We heard about Data Controller from the community, and it seemed like a great fit for our use case - it’s SAS friendly and it’s SAS built and it’s easy to incorporate.
|
||||
|
||||
The things we really like are the EDIT and APPROVAL process, and the HISTORY of all changes that is built into the product.
|
||||
|
||||
### Is anyone else at AFA using Data Controller?
|
||||
Not right now but we plan to use it more. We have people in the process development team who need to change targets once a year or maybe more often. Right now they send us the new targets and we add them in the programs / update the Visual Analytics reports, but we plan to use steering / control tables for them, so they can update targets themselves in Data Controller. Then they can request to change them when they like, and we have control over the timing of when the changes are applied.
|
||||
@ -43,6 +45,7 @@ We also have some percentages (relating to payments) with levels that change dur
|
||||
|:--:|
|
||||
| *Henrik Forsell (HF)* |
|
||||
|
||||
|
||||
(HF) This takes us completely out of the equation – we don’t have to do the changes, it’s all on them, they own it.
|
||||
|
||||
(FE) Yes – their data, their controls. We can leave it to them from the development environment, so they are not dependent on us for any changes, so it’s really good.
|
||||
|
Loading…
x
Reference in New Issue
Block a user