03 DMS Technical Requirement
1
TECHNICAL REQUIREMENTS FOR DMS Sr. No. Requirement Description Vendor Comments 1 Yes 2 3 Yes 4 Content Server Yes 5 Yes 6 Yes Assuming BASIS & ABAP is in scope o 7 Yes Assuming BASIS & ABAP is in scope o 8 Yes 9 Yes 10 Yes 11 Yes ABAP Development required 12 13 Yes 14 Need More clarity 15 Yes 16 Yes 17 Yes Assuming BASIS is in scope of Dilig 18 Yes 19 Yes 20 Downtime Yes 21 22 Yes 23 Offisite 24 25 Yes 26 Yes Assuming BASIS is in scope of Dilig 27 Yes 28 Documentation Yes 29 Deliverables: 30 After go live support for 15 days Vendor Confirmati on YES/NO SAP DMS Implementation and configuration SAP DMS Implementation and configuration along with easy DMS are in the scope of vendor. Server and Storage Sizing Vendor has to provide the Server and Storage sizing for 5 years SAP DMS Installation on HP Unix Platform Installation of SAP DMS on HINCOL HP UNIX Server are in the scope of vendor All documents uploaded from SAP ECC should get stored only in the Content Server Operating System, SAP Application, Basis and ABAP Activities All work of Operating System, SAP Application, Basis and ABAP related to DMS Installation/configiration are in the scope of vendor. Assuming BASIS & ABAP is in scope of Diligent Software Download from SAP Vendor has to download all the required software/media from SAP Support Portal which is required for DMS Implementation/configuration SAP Support Pack , SAP Note, Any Support Pack and SAP Note required for DMS implementation/configuration and any time during the implemantion/confiuration period needs to be applied by the vendor. Support Pack and SAP Note related to DMS requirement are in the scope of vendor. Number of DMS Instance Number of DMS System to be Installed. 1. Development 2. Production Number of DMS Instance to be linked with ECC Number of DMS System to be linked with ECC 1. Development 2. Production 1.Asset Master AS02 – (ANLA) 2.Equipment Master IE02 – (EQUI) 3.Customer Master – XD02 – (KNA1) 4.Vendor Master – XK02 – (LFA1) 5.Material Master – MM02 – (MARA – MARC) 6.Purchase Order – ME22N 7.Create Notification QM02 – (QMEL) 8.Purchase Requisition ME52N 9.Inspection Methods QS32 10.BOM- CS02- Configuration to make the provision to upload document in change mode in content server and to view the same in display mode for all the mentioned T- codes are in the scope of vendor. 1.MIGO - Create Mode 2.FB01 /FB50L Create and Change Mode 3.MIRO / FB60 Create Mode 4.FB75 Credit note Create and Change Mode 5.ME51N – Create Mode Enhancement to be done to make the provision to upload document in content server in the mode specified and to view the same in display mode for all the mentioned t codes are in the scope of vendor. the number of documents uploads, users should be able to attached N number of documents to any sap object. User should be able to upload any number of documents for the above t codes even for the t codes where enhanement is done and for the t codes where the function is already avaliable are in the scope of vendor. the authorizations of the SAP object it is attached with. User should be able to upload and view the uploaded documents in content server as per their authorization of ECC are in the scope of vendor. developed for creation of the “File Note”. This file note will route based on the originator(user) and amount specified in this file note (the amounts should be entered in a separate filed). 1. Provision to attached multiple documents in the file note to be provided. 2. Provision to attached the file note document in the LPR-ME51N and ME52N 3. Before configuring the same Vendor has to provide complete document and detail understanding to HINCOL about the configuration and the actual configuration to be done based on the mutual discussion between HINCOL and vendor Three separate document types to be created for Knowledge Repository. These documents will be used for knowledge repository and will be directly created and uploaded in the content server through CV01N Access to these documents should be thorugh controled authorization Existing Functionality of ECC The DMS requires configuration changes in ECC EHP7 however the vendor has to ensure that the existing functionality should work the same way even after DMS configuration. The Vendor has to do the necessary testing using SAP Tools or any other tool to ensure the same. DMS config. Will not effect any other SAP module functioning. Backup and Restoration of ECC and DMS devlopment and production system of DMS and ECC servers peridoncally during the period of DMS installation/configuration and incase if the backup needs to be restored it has to be done by the vendor. All backup and restoration are in the scope Business Continuity Vendor has to ensure that their is business continuity during DMS implementation/configuration. Minimum Down Time There should be minimum down time when we GO LIVE with DMS. vendor. Vendor may review the infrastructure to provide realistic downtime. System Prerequiste System Prerequiste like RAM, Mount Points, media etc needs to be provided by the vendor Implementation Methodolgy The vendor has to provide the implementation methodology Vendor can do all the work from offsite from their office, vendor has to visit HINCOL ERP center for the meetings and the cost for the same have to be born by the vendor. Internal Connectivity between the systems Transport Route and all other internal RFC connections to be working as it is are in the scope of vendor. External Connectivity PI to be working as it is are in the scope of vendor. Assuming BASIS & ABAP & Interface is in scope of Diligent System Testing Content Server and Fine Tunning after Upgrade Load Testing, Performance Testing, fine tunning of database, application, content server and os parameters are in the scope of work of vendor Functional Testing Functional Testing will be done by HINCOL, the vendor has to resolve all the issue reported by the HINCOL Team. Installation and Configuration Documentation of DMS needs to be provided by the vendor. Config document will be responsibility of Diligent Making and submititng the Installation Document that should consists of all installation steps and parameters details and content server details are in the scope of vendor. a 2-3days training session in HINCOL Turbhe Office to do the knowledge transfer of all the functional configuration settings done during DMS configuration. 2.Technical Knowledge Transfer :- Vendor have to provide the document and a 2-3 days training session in HINCOL Turbhe Office to do the knowledge transfer of all the technical installation settings done during DMS Post Go Live Support
-
Upload
saurabhrites -
Category
Documents
-
view
9 -
download
0
description
Document Management System
Transcript of 03 DMS Technical Requirement
TECHNICAL REQUIREMENTS FOR DMS
Sr. No. Requirement DescriptionVendor Comments
1Yes
2
3Yes
4 Content ServerYes
5
Yes Assuming BASIS & ABAP is in scope of Diligent
6Yes Assuming BASIS & ABAP is in scope of Diligent
7
Yes Assuming BASIS & ABAP is in scope of Diligent
8Yes
9Yes
10
Yes
11
Yes ABAP Development required
12
13
Yes
14
Need More clarity
15
Yes
16
Yes
17
Yes Assuming BASIS is in scope of Diligent
18Yes
19Yes
20 DowntimeYes
21
22 Yes
23
Offisite
24
25Yes
26
Yes Assuming BASIS is in scope of Diligent
27Functional Testing Yes
28Documentation Yes
29
Deliverables:
30After go live support for 15 days
Vendor Confirmation YES/NO
SAP DMS Implementation and configuration
SAP DMS Implementation and configuration along with easy DMS are in the scope of vendor.
Server and Storage Sizing
Vendor has to provide the Server and Storage sizing for 5 years
SAP DMS Installation on HP Unix Platform
Installation of SAP DMS on HINCOL HP UNIX Server are in the scope of vendor
All documents uploaded from SAP ECC should get stored only in the Content Server
Operating System, SAP Application, Basis and ABAP Activities
All work of Operating System, SAP Application, Basis and ABAP related to DMS Installation/configiration are in the scope of vendor.
Software Download from SAP
Vendor has to download all the required software/media from SAP Support Portal which is required for DMS Implementation/configuration
SAP Support Pack , SAP Note,
Any Support Pack and SAP Note required for DMS implementation/configuration and any time during the implemantion/confiuration period needs to be applied by the vendor. Support Pack and SAP Note related to DMS requirement are in the scope of vendor.
Number of DMS Instance
Number of DMS System to be Installed.1. Development2. Production
Number of DMS Instance to be linked with ECC
Number of DMS System to be linked with ECC1. Development2. Production
1.Asset Master AS02 – (ANLA)2.Equipment Master IE02 – (EQUI)3.Customer Master – XD02 – (KNA1)4.Vendor Master – XK02 – (LFA1)5.Material Master – MM02 – (MARA – MARC)6.Purchase Order – ME22N7.Create Notification QM02 – (QMEL)8.Purchase Requisition ME52N9.Inspection Methods QS3210.BOM- CS02- (STKO)11.Sales Order VA02 – (VBAP)
Configuration to make the provision to upload document in change mode in content server and to view the same in display mode for all the mentioned T- codes are in the scope of vendor.
1.MIGO - Create Mode2.FB01 /FB50L Create and Change Mode3.MIRO / FB60 Create Mode4.FB75 Credit note Create and Change Mode5.ME51N – Create Mode
Enhancement to be done to make the provision to upload document in content server in the mode specified and to view the same in display mode for all the mentioned t codes are in the scope of vendor.
No capping on the number of documents uploads, users should be able to attached N number of documents to any sap object.
User should be able to upload any number of documents for the above t codes even for the t codes where enhanement is done and for the t codes where the function is already avaliable are in the scope of vendor.
Documents in the DMS will have the authorizations of the SAP object it is attached with.
User should be able to upload and view the uploaded documents in content server as per their authorization of ECC are in the scope of vendor.
FILE NOTE WORKFLOW: A separate customized process to be developed for creation of the “File Note”. This file note will route based on the originator(user) and amount specified in this file note (the amounts should be entered in a separate filed).
1. Provision to attached multiple documents in the file note to be provided.2. Provision to attached the file note document in the LPR-ME51N and ME52N3. Before configuring the same Vendor has to provide complete documentand detail understanding to HINCOL about the configuration and the actual configuration to be done based on the mutual discussion between HINCOL and vendor
Three separate document types to be created for Knowledge Repository.
These documents will be used for knowledge repository and will be directly created and uploaded in the content server through CV01N
Access to these documents should be thorugh controled authorization
Existing Functionality of ECC
The DMS requires configuration changes in ECC EHP7 however the vendor has to ensure that the existing functionality should work the same way even after DMS configuration. The Vendor has to do the necessary testing using SAP Tools or any other tool to ensure the same.
DMS config. Will not effect any other SAP module functioning.
Backup and Restoration of ECC and DMS
Vendor has to take the backup of both devlopment and production system of DMS and ECC servers peridoncally during the period of DMS installation/configuration and incase if the backup needs to be restored it has to be done by the vendor. All backup and restoration are in the scope of vendor.
Business Continuity
Vendor has to ensure that their is business continuity during DMS implementation/configuration.
Minimum Down Time
There should be minimum down time when we GO LIVE with DMS.
Planned downtime to be provided by the vendor. Vendor may review the infrastructure to provide realistic downtime.
System Prerequiste
System Prerequiste like RAM, Mount Points, media etc needs to be provided by the vendor
Implementation Methodolgy
The vendor has to provide the implementation methodology
Vendor can do all the work from offsite from their office, vendor has to visit HINCOL ERP center for the meetings and the cost for the same have to be born by the vendor.
Internal Connectivity between the systems
Transport Route and all other internal RFC connections to be working as it is are in the scope of vendor.
External Connectivity
Connectivity to other systems such as BI, PI to be working as it is are in the scope of vendor.
Assuming BASIS & ABAP & Interface is in scope of Diligent
System Testing Content Server and Fine Tunning after Upgrade
Load Testing, Performance Testing, fine tunning of database, application, content server and os parameters are in the scope of work of vendor
Functional Testing will be done by HINCOL, the vendor has to resolve all the issue reported by the HINCOL Team.
Installation and Configuration Documentation of DMS needs to be provided by the vendor.
Config document will be responsibility of
Diligent
Making and submititng the Installation Document that should consists of all installation steps and parameters details and content server details are in the scope of vendor.
1.Functional Knowledge Transfer :- Vendor have to provide the document and a 2-3days training session in HINCOL Turbhe Office to do the knowledge transfer of all the functional configuration settings done during DMS configuration. 2.Technical Knowledge Transfer :- Vendor have to provide the document and a 2-3 days training session in HINCOL Turbhe Office to do the knowledge transfer of all the technical installation settings done during DMS configuration.
Post Go Live Support
