CEI Document Management in S/4 Initial Call

(1)

CEI Document Management in S/4

– Initial Call

Anurag Jain, SAP Labs India

(2)

Disclaimer

The information in this document is confidential and proprietary to SAP and may not be

disclosed without the permission of SAP. This document is not subject to your license

agreement or any other service or subscription agreement with SAP. SAP has no obligation to

pursue any course of business outlined in this document or any related presentation, or to

develop or release any functionality mentioned therein. This document, or any related

presentation and SAP's strategy and possible future developments, products and or platforms

directions and functionality are all subject to change and may be changed by SAP at any time

for any reason without notice. The information in this document is not a commitment, promise

or legal obligation to deliver any material, code or functionality. This document is provided

without a warranty of any kind, either express or implied, including but not limited to, the

implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This

document is for informational purposes and may not be incorporated into a contract. SAP

assumes no responsibility for errors or omissions in this document, except if such damages

were caused by SAP intentionally or grossly negligent.

(3)

Agenda

Duration

Topic

Participants

5 min Welcome and Introduction Anurag Jain

15 min Scope of Interaction Model Benefits & Efforts for customers

Anurag Jain

30 min Innovation done so far in Document Management System and Future Scope

Anurag Jain

10 min Overall Project Plan/planned activities including timelines

Anurag Jain

5 min Prerequisites for participation (NDA/Feedback Agreement, …)

Anurag Jain

10 min Wrap-up, feedback & next steps Anurag Jain

(4)

Agenda

Duration

Topic

Participants

5 min Welcome and Introduction Anurag Jain

15 min Scope of Interaction Model Benefits & Efforts for customers

Anurag Jain

Anurag Jain

(5)

What we offer - Levels of Engagement

In Detail

Up to three customers

Activities



SAP would like to visit

you



Detailed discussions

Support for

implementation project

by developers on site

Info

For everyone who

would like to participate

Activities



Learn about status,

provide feedback



Ca. once every four to

five months

Review

Up to seven customers

Activities



Calls / Workshops in

Walldorf



Interviews

(6)

What we expect – efforts at customer side

In Detail

Activities



Regular calls – once a

month will require

preparation



Willingness to be visited

by us



Willingness to invest

time to prepare our

visit, to give detailed

feedback and comment

on progress

Info

Activities



Willingness to invest

time for Calls and their

preparation

Review

Activities



Willingness to invest

time for calls and their

preparation ca. once

every three months



Willingness to travel to

Walldorf for workshop

(we can’t cover your

travel costs) and invest

time for preparing the

workshop and if

(7)

Benefits for the customer in engaging with SAP during

product development lifecycle

Primary benefits



Gain early insights into SAP‘s product visions / ideas / research projects



Provide requirements and feedback directly to the product team



Gain early insights into potential later products through evaluation of early prototypes before

they are implemented



Establish a direct line of communication to the product development organization



Be amongst the first to take new functionality into production

Ancillary benefits



Opportunity to share ideas, solutions and best practices within an ecosystem of similar SAP

customers and partners

(8)

Agenda

Duration

Topic

Participants

5 min Welcome and Introduction Anurag Jain 15 min Scope of Interaction Model

Benefits & Efforts for customers

Anurag Jain

30 min Innovation done so far in Document Management System and Future Scope

Anurag Jain

Anurag Jain

(9)

2 23 10 15 3 3

56 qualified IRs

improvement already existing Planned for develpment Rejected - prioritization

Rejected - Violating design rules Rejected - exceeding size & effort Rejected - others

Improvement Requests – Overview – DMS CC - 2014

# IRs submitted by DMS customers 134

+ # IRs handed-over from PLM Recipe 2

- # rejected IRs (due to lack of customer subscriptions) 66 - # rejected IRs out-of-scope 14

= # qualified IRs (5 or more subscriptions) 56

Thereof (recommendation):

#IRs already exists 2

# IRs to be scoped (planned for development) 22

# IRs to be rejected

(overview of reasons see in chart on the right) 32

# IRs to be handed over (IR will be tracked within SAP

(10)

18 23 4 7 1 1 10 2

# of qualified IRs

Already delivered

Planned for development pending

Rejected - prioritization

Rejected - exceeding size/effort Rejected - no fit in product strategy Rejected - violating design rules Rejected - others

Improvement Requests – Overview – DMS CC -2015

# IRs submitted by customers 118 - # rejected IRs (due to lack of customer

subscriptions) 36

- # out of scope IRs (already communicated) 14

= # qualified IRs (5 or more subscriptions)

68

Thereof (recommendation):

# IRs already delivered 18

# IRs to be scoped (planned for development) 23

# IRs pending 6

# IRs to be rejected

(overview of reasons see in chart on the right) 25 # IRs to be handed over (IR will be tracked within

(11)

(12)

(13)

Working with Mobile Documents

(14)

Working with Mobile Documents

(15)

Working with Mobile Documents

(16)

Working with Mobile Documents

(17)

Document Management in S/4 Future Plans

Simplification of DMS in S/4 HANA



Role based User Experience for DMS



FIORI UI for CV01, CV02, CV03 transactions



Relook transaction based access and provide access environment based on user needs.



Simplify Design/Concepts



Relook on existing features/customizing which are not used by customers and remove

them.



Simplify design where possible and add value

(18)

Agenda

Duration

Topic

Participants

Anurag Jain

10 min Overall Project Plan/planned activities including timelines

Anurag Jain

Anurag Jain

(19)

Planning

2015

Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

(20)

Rough time investment estimation on customer’s side for

**selected activities* (I)**

Activity

Who is involved at customer‘s side

Estimated time

_investment

Site Visit One person as contact for SAP team to support identification of end user(s), setup agenda and logistics, internal selling at customer‘s side

Line of business expert(s): should be available for meeting on business processes and wrap-up session

IT expert(s): should be available for meeting on business processes and wrap-up session

End user(s): should be available for interview and observation in their work environment

2 days preparation, 0,5 day wrap-up communication

meeting time: 4 hours / person

4 hours / person Interview One person as contact for SAP team to support identification of end user(s), setup agenda

and logistics, internal selling at customer‘s side

End user(s): should be available for a 1 hour session (via telephone, webex, etc.) Line of business expert: should be available for a 1 hour session (via telephone, webex,

etc.)

1 day preparation and wrap-up communication

1 hour / per interview

Workshop (at SAP location)

One person as contact for SAP team to support identification of end user(s), setup agenda and logistics, internal selling at customer‘s side, prepare travel

Workshop participants: line of business expert(s), end user(s), IT

2 days preparation and wrap-up communication

Travel time + 8 hours workshop time per participant Use case

validation (at customer’s site)

One person as contact for SAP team to setup validation session and logistics, internal selling at customer‘s side

Line of business expert(s): should be available for meeting on business processes and wrap-up session

IT expert(s): should be available for meeting on business processes and wrap-up session

Validation session: end user(s) + line of business expert(s) to discuss use cases

1 day preparation, 0,5 day wrap-up communication

meeting time: 2 hours per person

meeting time: 2 hours / person

2 hours / person

(21)

Who will be involved

Setup can vary dependent on level of engagement

SAP

Solution Management

Engineering



Product Owner



Developer

Customer

Business User (Business Process

Expert)

User from IT department

(22)

Business User (Business Process Expert)

Scenarios / Business Processes in focus: Working for Managing Document,

Document Structures, Sharing Documents.

Years of experience the user has in the requested role: Professional level, i.e.

roughly 2+ years of experience

Software experience the user has to have: Experiences with a tool supporting

Engineering Content Management - not necessarily one provided by SAP.

(23)

User from IT department

Scenarios / Business Processes in focus: Setting up ECM environment that is

storage server, access to various document type, recovering document etc.

Years of experience the user has in the requested role: Professional level, i.e.

roughly 2+ years of experience

Software experience the user has to have: Experience with configuring ECM tool

for various LoBs i.e. procurement, EAM, Project Management, Engineering etc.

(24)

Developer / Project Lead

Scenarios / Business Processes in focus: User involved in projects related to

DMS in various area like EAM, Project System etc.

Years of experience the user has in the requested role: Professional level, i.e.

roughly 2+ years of experience

Software experience the user has to have: Experiences in working with

development and customizing tools.

(25)

Agenda

Duration

Topic

Participants

Anurag Jain

5 min Prerequisites for participation (NDA/Feedback Agreement, …)

Anurag Jain

(26)

Why do we need a Feedback Agreement?

The Feedback Agreement describes the principles of the working relationship with all involved parties. The most important ones are:

Intellectual Property (IP): Customers want to influence SAP software (maybe even services). Customers

want to see their feedback/ideas in SAP software. For being able to actually incorporate such feedback in our software, SAP needs the right to do so. That's why SAP needs a royalty free license. SAP does not want the Intellectual property on the feedback/ideas. This remains with the customers, such that customers could use that IP to create own solutions or even products. Section 6 of the Feedback Agreement says that very clearly.

Non-disclosure: All information and feedback exchanged needs to be treated as confidential, needs to stay

within the group. This is true for information SAP discloses as well as info customers disclose to SAP or to each other. In many cases we share either immature planning or internal information, that needs to be treated confidential. This is being handled in the feedback agreement section.

Customer Commitment: In many cases we discuss software to be built or shipped in 1-2 years time.