Lack of direction, not lack of time is the problem.
So we know what requirements we have and we do have a vision but does it support the vision of the Elephant or vice versa?
At Vestas we are focusing on delivering capabilities based on generic services. This is also relevant for the SAP DMS area. We have for many years focused on delivering the whole package, capability and the front-end solution. This is going to be changed, we see the demand to be driven by access to the capability and embed this in 3.part solutions.
Realizing that matter changes what we have today and by that of course the strategy.
Technology wise we already have good experiences with Rest Services and named OData based capabilities. We are using the SAP API Management solution and we want to build a capability repository based on the services we get with The Elephant. But there is no doubt we are beginners and need to learn how do we utilize the potential of OData services.
Questions comes up like:
Is the service stable?
How is the performance?
How can we control and learn on the performance reporting?
ow do we implement the service as a capability for the users?
The baseline of services
The term service indicates SAP DMS delivers a pre-defined output based on input from the client. But as a user I am interested to understand where and how can this support my daily work?
We need to catch the users and understand how these services can support them. For that we started a task up with investigation were and what we should focus on. More to come in the coming blogs.
Secondly, we will build a baseline of capabilities
Testing the performance
urvey the stability and expectations
An example is the mass creation SAP DMS objects.
The capability gives us the option to create Document Information Record (DIR) in a standard way and much more flexible then today. We have a migration tool which is used for handling this scenario today which is not intended to handle daily operations and it should be replaced by this capability.
So first step is to create a baseline of performance expectations. We take our baseline from SAP EasyDMS and compare with The Elephant on their test environment, which we gladly have access to as part of the cooperation.
An example is the mass creation SAP DMS objects. EasyDMS -> Based on 100 create runs the median is 31,5 seconds Elephant -> Based on 100 create runs the median is 8 seconds
This is quite amazing, but still remember it is not on Vestas’s own environment.
We will in this week receive the transports from Netcare International for being installed on our sandbox. From here we will do the same testing and will update in the next blog.
Searching the relevant Document Information Records (DIR) will be done by document type and date range. We have already proposed some enhancements like:
To deliver F4 simple search options to find relevant documents
Change object links by mass change functionality
Change user groups by mass change functionality
Add existing Document Information Records(DIR) to an existing document structure
Create new structures by uploading Document Information Records (DIR)
So this will give us a new set of services which we do not have today. Yet another step in the right direction.
Don’t forget to read Part 1 & 2 of this blog to find out more about how we are changing the working environment.