AnnexB - Appendix3B - Kiran

(1)

Tender No.

15EW/2009

B

IDDING

D

OCUMENTS

F

OR

A C

ONTRACT

T

O

D

ESIGN

, S

UPPLY

, I

NSTALL

, I

MPLEMENT

, T

RAIN

AND

P

ROVIDE

S

UPPORT

S

ERVICES

FOR

AN

ERP

AND

CRM /B

ILLING

S

OLUTION

ON

A

T

URNKEY

B

ASIS

A

NNEXURE

B:

A

PPENDIX

3B

C

OMPLIANCE

S

HEET

(2)

Current version and release date (GA) This is the latest version of our product and was released in 2006. However, SAP is evolving the _{SAP ERP major release schedule to a five-year rhythm to better align with the customer adoption} cycle. To ensure that customers take advantage of innovations while minimizing the impact to core operational systems, SAP plans to accelerate delivery of new functionality through enhancement packages that customers can optionally implement on top of SAP ERP. Enhancement packages are intended to contain functional enhancements and enterprise services in areas such as shared services, end-to-end business processes such as order to cash or "hire to retire," supplier collaboration, and industry specific functionality. The intent is to deliver more innovation, more quickly, in a more accessible way. SAP is thus ensuring the greatest possible protection of your investments by continuing to deliver high-quality ERP functions.

Number of

•

Clients using the proposed software in production environment ( in UAE)

•

Major clients in GCC using the proposed software with details of year of implementation

•

Installations in the last financial year that has been implemented by bidder and contact details

Today, more than 82,000 customers in over 120 countries run SAP applications and the demand for the SAP ERP 6.0 application

is especially high, and to date more than 10,000 customers are using it in live operation. A large number (200+) of customers are using SAP ERP versions in the GCC. 3 GCC utilities are live with SAP and 1 is under implementation.

Largest customer for the proposed product

•

Name of the customer

•

Number of customer installed accounts ( active accounts )

•

Transaction volume

•

Number of remote site

•

DR availability ( is it hot-standby or cold-standby )

Please review the attached excel sheets which list our customer references for ERP 6.0 and IS-Utilities.

C:\Users\C5037555\

Documents\Clients\FEWA\References_ERP_6.xls C:\Users\C5037555\

Documents\Clients\FEWA\References_IS_Utilities.xls

How can the proposed software be acquired? (purchase/lease/other) Purchased In case of licensing, explain software licensing systems schema and cost

structure.

Licensing is a mixture of named user and metrics based: SAP ERP is based on named users and priced according to roles. SAP CRM and Billing for Utilities is based on the number of active

(4)

Is the license agreement per site, per CPU, per concurrent user, per named user, per server licence, per database , per enterprise basis or combined of a mix of the mentioned methodology ? ( Please explain in details )

ERP is per named user based on role. Utilities tools are licensed based on metrics as per the answer to the previous section. Some solutions, such as SAP explorer, are also available per CPU.

Is the source code available? Yes

IF the answer on the previous question is yes then please indicate the Escrow availability of the source code .

Under the terms of the SAP Software End-User License Agreement, SAP provides application source code. Basis source code is placed in escrow. The escrowed code can be made available to SAP customers in the event of SAP filing bankruptcy or going out of business.

If the proposed product has any additional features ( not listed in the RFP ) that will be useful in evaluating of the product(s) / solution, then state them

• SAP ERP is proven, world-class, integrated ERP software that addresses the core business software requirements of the most demanding organizations around the world – in all industries and sectors.

• With 47 country versions, SAP ERP is a truly global application used by organizations across multiple industries, currencies, and accounting standards to support international workforces.

• The SAP strategy of growth through innovation and scope contrasts with the strategies of some competitors that try to achieve growth through merger and acquisition, which can cause disruption for customers. SAP ERP has a clear product road map that gives organizations a choice as to how they want to consume new features and functionality. SAP ERP 6.0 is the go-to release, and with SAP enhancement packages, we continue go-to deliver innovation without disruption to SAP ERP customers.

• SAP ERP is built on SAP NetWeaver, the SAP technology platform that reduces IT complexity while supporting scalability and growth.

• SAP ERP is tightly integrated to optimize cross-functional business processes and to enable comprehensive collaboration within and beyond an organization.

• SAP ERP delivers industry-specific functionality that supports the best business practices in more than 25 industries based on SAP’s experience with thousands of successful customers. With SAP ERP, companies can implement industry-specific functionality easily.

• With 35 years of proven performance and results, SAP has earned the position of trusted adviser to organizations. Likewise, SAP ERP has earned its place as the trusted software foundation for thousands of global organizations.

What are major enhancements are planned in the next 24 months Describe any limitations of the proposed product ( if any ) in term of capacity , number of users, number of transaction, volume of Database , languages support DR support and/or any other essential feature.

There are no software limitations. Only limitations are HW and network capacity. SAP solutions are used by some of the largest Utilities in the world and are very scalable.

(5)

change, opportunities, and threats.

SAP has a clearly defined upgrade path for all its solutions. Over the past few years SAP has adapted its product release strategy and roadmap of SAP ERP to deliver on two key components; simplification and innovation without disruption.

In recent years, major version releases have included: 4.6c Available since May 2000

4.7 Available since July 2002 ERP 2004 Available since June 2004 ERP 2005 Available since October 2005 ERP 6 Available since June 2006

We continue to build on the successful release strategy of SAP ERP, in which the core remains stable, while customers receive enhancement packages that offer regular innovation on top of the business process platform.

What Are Enhancement Packages? Enhancement packages are:

• Optionally installed and activated software innovations for SAP ERP 6.0

• Software innovations include

• UI simplifications

• Functional enhancements

• Industry specific capabilities

• Enterprise services

• Cumulative in nature: current enhancement packages contain entire content of earlier packages

• Enhancement packages are not support packages

SAP enhancement packages will be delivered for all Suite Applications

• Enhancement packages are released regularly enabling a customer to benefit from new functional enhancements without having to perform entire system upgrades every couple of years, which has been costly and time consuming in the past.

• SAP enhancement packages will be delivered for all Suite Applications

• Enhancement packages are released regularly enabling a customer to benefit from new functional

How many releases of your product have been produced during the last five years?

In recent years, major version releases have included: 4.6c Available since May 2000

4.7 Available since July 2002 ERP 2004 Available since June 2004 ERP 2005 Available since October 2005 ERP 6 Available since June 2006

(6)

Does the product have a support centre in UAE /in GCC? If yes, since when and where is located and what services does provide ?

SAP offers support on a global basis in a follow the sun model. Customers are offered online and phone access to the support organization. A toll free number is offered in the UAE. More details on Sap Active Global support are in the attached document.

Indicate contractual agreements, and terms of use. Please attach the draft copy of the agreement for the below .

Software purchase ( ) Software licence ( ) Software maintenance /AMC * ( )

* Indicate clearly if upgrade process for minor and/or major releases is including in the proposed AMC?

Did the proposed product pass through major rewrite statue ? , if yes then indicate which release and when it has been released.

All additions have been incremental over time, no major re-writes.

Indicate all users screens (if any) which will not be in dual languages Arabic and English ( if you didn’t indicate any , then FEWA assume all screens will be bi-lingual (Arabic/English )

ERP and SAP CRM and Billing for Utilities support Arabic.

1.1.2 System Architecture

(7)

•

System Deployment Architecture

•

Recommended Network infrastructure requirements

The SAP solution for utilities is based on the Netweaver Web Services Platform. This enables the system to be deployed as a web services solution as well a N tier

architecture where front end, application and database services may be separated. Please see supporting materials on the Netweaver platform.

SAP Architecture Overview

SAP’s n-Tier Architecture

SAP components are each built on an n-tier client/server architecture, which includes presentation, application and database service components that communicate using industry-standard protocols, such as TCP/IP, and are based on a single repository. SAP NetWeaver includes the embedded SAP Web Application Server (SAP Web AS), which embraces native Web technologies through a standards-based approach. SAP is fully accessible via remote, mobile, and Web-based means. Based on the highly scalable SAP Application Server infrastructure, technologies have been implemented for directly processing HTTP requests (or other protocols) coming from the Internet (that is, from a browser), and for sending HTTP requests as HTTP client requests to the Internet.

(8)

mySAP Business Suite landscape, SAP involves the hardware partners at mySAP hardware competency centers. SAP will work with FEWA and the certified hardware vendor of choice to ensure proper sizing of your landscape and will provide FEWAwith configuration recommendations based on various variables (number of named users, concurrent users, functional areas and components used, network bandwidths, high availability, and so on).

All required SAP® components can operate on a single server (multi-CPU SMP machine) or a cluster of smaller machines (blade servers) equally well with a storage-attached disk (SAN). Without further information from FEWA on the desired operating system, database, and hardware vendor, it is not possible to provide a more detailed hardware configuration.

An example landscape including the SAP NetWeaver Portal, SAP applications, and SAP data warehouse (DW) is provided in the following diagram. Please note that there is significant flexibility in deployment of the final desired architecture for FEWA based on business requirements and platform choices. Not all components are mandatory in this scenario. In this scenario, the SAP applications (SAP HR) and the SAP DW have separate databases, but this is not required. Both applications and analytics can run on a single database.

SAP recommends the physical isolation of configuration data through a multiple system landscape when supporting a production landscape. SAP’s embedded change management system supports phased implementations and team-based development and deployment. Through the use of separate physical databases in development, quality assurance, and production systems, SAP provides for structured testing and auditing in 21 CFR Part 11 scenarios. SAP’s embedded workflow management system can be used for migrating changes from one environment to another, along with enforcing automated and electronic testing procedures through the embedded SAP test workbench tool

(9)

•

Name of software

•

Type of software

•

Type of interface

•

Details of sites were the interfaces are currently operational

•

In case the offer includes multiple software’s, please provide details of integration between the offered applications.

All SAP products are fully integrated. There are no interfaces required. SAP products are integrated with many hundreds of 3rd party products. In many cases, certified interfaces are available from SAP and 3rd parties. In addition, Sap Netweaver offers the ability to interface using industry standards. An interface development kit is also provided to support the development of customized interfaces.

4 List any additional utility package required for the proposed application software to comply with the requested requirement. None

5 What productivity tools are available with the proposed system? Check the features that apply, and Indicate your product name which supports the mentioned features ( the mentioned example for guideline and doesn’t indicate any preferred product and/or solution )

Feature Product name

Data dictionary/model SAP includes an integrated Data Dictionary that performs the functions of a metadata repository. The Data Dictionary centrally describes and manages all the data definitions (both technical and business) used in the system. The Data Dictionary supports the definition of user-defined types (data elements, structures, and table types). You can also define the structure of database objects (tables, indexes, and views) in the Data Dictionary. These objects can then be automatically created in the database with this definition. The Data Dictionary also provides tools for editing screen fields, for example for assigning a field an input help. The most important object types in the Data Dictionary are tables, views, types (data elements, structures, and table types), domains, search helps, and lock objects. The Data Dictionary also provides standard functions for editing fields on the screen; for example, for assigning a screen field an input help. The Data Dictionary permits a central description of all the data used in the system without redundancies. New or modified information is automatically provided for all the system components. This ensures data integrity, data consistency and data security.

Query language (e.g. SQL) • SAP NetWeaver Composition Environment – Provides a robust environment for design, deployment and running of

composite applications that comply with enterprise service-oriented architecture

• SAP NetWeaver Developer Studio – Offers a convenient user interface and rich functionality for developing J2EE applications

•

SAP NetWeaver Visual Composer – Simplifies the creation of portal content and analytics applications, enabling business analysts to build or customize applications using a visual user interface rather than manual coding

(10)

Java.

For ABAP development, the ABAP Development Workbench is provided. The ABAP Workbench is a set of tools and libraries for designing, implementing, testing, and maintaining transactions and reports written in ABAP Objects.

For Java development, SAP provides NetWeaver Developer’s Studio, an Eclipse-based Java development environment.

SAP also provides Visual Composer, a model-driven development tool that produces Web based screens. User-developed customizations, such as configuration changes and code inserted at pre-defined points, are maintained separately from the core applications, and if properly applied can easily be preserved through an upgrade. Only changes to the core applications (i.e., modifications to the source code) are not automatically upgraded. However, even in this case, an audit is performed before upgrading the core applications, and any changes are highlighted to allow the changes to be extracted and

(11)

of business needs. When this does not meet the customer’s needs, we have user exits provided in the standard code, which allow for minor customization. Finally, the ABAP tool provided with the software provides the ability to make customizations as needed.

During the realization phase of the project, the project team can create their unique SAP installation via the following:

• Configuration - Project team members identify the business requirements and make modifications as

needed to enable the solution via the Implementation Guide (IMG). Application code is designed to operate based on configuration tables--as such, no programming is required to "customize" the system within these design parameters. The IMG is specifically designed for use by the functional members of the Project Team, and is based on application appropriate user interfaces for creating business rules and configuration tables.

• Enhancement - Project team members identify the "user exit" location and then write a definition of the

extension needed which is then coded by a tools consultant (using the ABAP Workbench). A "user exit" is a pre-defined point in a transaction at which customers typically want to perform some site-specific processing. Customer-developed applications are also an example of an enhancement, and can developed using ABAP or J2EE.

•

Customization - If the project team cannot find solutions using either of the first two processes then it will

need to request that a modification of the product be made. These are defined and presented to the steering committee and project management for approval. Frequently the business process change team engages in this area to see if there are business solutions that can avoid this. A customization modifies an SAP provided business object; the ABAP Workbench includes tools to manage modified objects.

Through SAP NetWeaver, businesses can achieve end-to-end process integration with pre-integrated SAP solutions. NetWeaver also enables disparate applications and systems work to work together to perform business processes from a combination of SAP and non-SAP systems.

SAP adheres to an ESOA (Enterprise Services Oriented Architecture) as supported by SAP NetWeaver. This adaptable model provides enterprises the flexibility to easily extend system functionality by leveraging existing IT investments that include SAP and non-SAP applications. Based on a Web services paradigm, this model elevates IT to efficiently meet the needs of the enterprise and deliver a TCO that maps to an enterprises objectives.

SAP NetWeaver offers an Integration Broker (SAP PI) and a Business Process Management (BPM) solution for process integration besides the message-oriented middleware.

Interfaces are at the heart of every cross-component process. They are almost constantly referenced during design and configuration. It is therefore vital that an interface description can be accessed at a central point. The following are interface description types that you can save in the SAP Process Integration (SAP PI, formerly known as SAP NetWeaver Exchange Infrastructure, or SAP NetWeaver XI) Integration Repository:

• Platform-independent message interfaces

• Imported interfaces for which an XML representation of a BAPI, RFC, or IDoc is generated in the Integration Repository

• External WSDL, XSD, or DTD definitions containing message schemas that you can access in the Integration Builder

The standard SAP interfaces are web services and are published centrally in the XML-based Interface Repository. They are stored as XML schema, which means that they are immediately available for use in integration scenarios where multiple components communicate with each other using the Internet.

(12)

Database Management Tool _{The SAP system supports the use of relational database management systems (RDBMS) to include: Oracle,}

Microsoft SQL Server, DB2, and mySQL MaxDB. All supported RDBMS are ANSI SQL compliant. SAP does not recommend one RDBMS over another. All system functionality is database independent.

Standard tasks such as performance tuning and backup are required. A trained DBA can easily support the SAP application from a database perspective.

SAP software comes with its own backup and restore utility, a full system and database administrative tool called Computing Center Management System (CCMS). Both full and partial backups are supported. Backup and recovery is always performed at the database level. The SAP backup utility supports two modes of backup: offline and online. In offline mode, the application is not available for the duration of the backup. In online mode, users have full access to the application while backup is running.

Business Intelligence (BI) builder _{SAP NetWeaver Business Intelligence}_{– Enables you to integrate data from across the enterprise and transform}

it into practical, timely business information to drive sound decision-making

Development Tool • User productivity enablement -- Help users and groups improve their productivity through enhanced

collaboration, optimized knowledge management, and personalized access to critical applications and data.

• Data unification -- Consolidate, rationalize, synchronize, and manage all master data for improved business processes.

• Business information management -- Increase the visibility, reach, and usefulness of structured and unstructured enterprise data.

• Business event management -- Ensure that business events from multiple systems are distributed to the appropriate decision makers in the context of the relevant business processes.

• End-to-end process integration -- Make disparate applications and systems work together consistently to perform business processes.

• Custom development -- Rapidly create new enterprise-scale applications that drive your company's differential advantage.

• Unified life-cycle management -- Automate application management processes and optimize all facets of an application's life cycle.

• Application governance and security management -- Maintain an appropriate level of security and quality in your intellectual property and information assets.

• Consolidation -- Deploy a consolidated technology platform with the ability to allocate computing power according to changing business needs.

•

Enterprise service-oriented architecture design and deployment -- Consolidate and standardize your basic processes and leverage existing investments to compose new, distinctive business processes

.

Case tool (e.g. Designer 2000 etc.) Included in development environment of SAP. See previous sections

RDBMS (e.g. Oracle, DB2 etc.) Oracle, DB2 are supported. The SAP system supports the use of relational database management systems (RDBMS) to include: Oracle, Microsoft SQL Server, DB2, and mySQL MaxDB. All supported RDBMS are ANSI SQL compliant. SAP does not recommend one RDBMS over another. All system functionality is database independent

(13)

As the Sap solution is built on top of an integrated Enterprise Services environment, clients have a number of methods of adding fields, modifying processes and adding new functionality. Please see supporting materials describing Netweaver

7 Please provide details on scalability, high-availability, reliability, and flexibility features based on the product(s) architecture. In addition, please illustrate load-balancing features provided in your proposed solution (if any ).

The SAP NetWeaver® Application Server component relies on its J2EE-based clustering architecture to provide high-availability. Fail-over capabilities include:

• Replication and partition of components inside a cluster architecture

• Cluster wide resource locking API, with high availability features such as lock replication

• Database and persistency layer with reconnect functionality Stateful session failover is supported at various levels:

• Session stickiness via cookies or URL rewriting

• Session failover at EJB level via redirect to alternative server nodes

Granularity of failover can be adjusted in a flexible manner to cover each user request or each http session. Flexible session persistency is achieved via file system, RDBMS, shared memory or shared closures (part of the VM container architecture by SAP). Planned downtime is fully supported by the high availability concept of SAP NetWeaver Application Server. Servers and individual components can be shut down on a schedule defined by the system administrator. The cluster architecture automatically redirects processes to other available instances of the server.

Using the three- or multi-tier approach, all requests must access the application server. The application sever does the necessary processing and database access and returns the results to the presentation client. The application server is highly scalable and performs log on load balancing. This mechanism ensures transparency to the users from the logon process to the system

8 Please describe any limitations that exist and/or may arise in the proposed software/operating system/file manager etc based on the volume of Data that can be handled and processed. (Number of table entries, master data fields, key values, etc.)

There are no software imposed limits. Server capacity and Network throughput are the only limitations. The SAP environment can be configured to meet requirements and is infinitely scalable to meet expected growth.

(14)

software comes with its own backup and restore utility. Both full and partial backups are supported. The SAP backup utility supports two modes of backup: offline and online. In offline mode, the application is not available for the duration of the backup. In online mode, users have full access to the application while backup is running. From an SAP perspective, one method is as good as another. All database systems have their tools to back up and restore their databases. The SAP environment interfaces to native database tools to support the backup and restore functions. With all dataase systems supported by SAP, database backups can be scheduled and triggered from the computer center management system (CCMS) functionality; alternatively, external backup tools can also be used. SAP backup support of tape stackers combined with SAP scheduling allows you to run backups unattended. SAP backup also provides tape volume management. Recovery in cases where data is lost is managed with a combination of the SAP restore utility and database logging. SAP restore is normally used to bring a data file back to a known state by applying the most recent full backup (and any incremental backups since that time). Once this is done, database logs are applied to bring the system back to the last committed transaction. Any “in-flight” transactions are captured in an update log where broken transactions can be reviewed by the system administrator and the user to determine the most appropriate course of action. Users are also notified of any failed transactions via an e-mail message. SAP database management tools come with a check and restore function. Check and repair functionality is used to uncover any inconsistencies in the database. If an inconsistency is found, SAP restore uses information from backup logs and tape volume management to find the appropriate files to restore, and provide automated recovery.

10 Describe the control features included within the system to ensure integrity of data (i.e. input and update, totals maintained, crosschecks carried out, audit trails, error reports, etc.)

The SAP® system handles all validations in the application layer. As a result, the SAP system provides far better data integrity during system interfaces. Other solutions provide interfaces (including batch interfaces) to the system at the database or middleware level. The problem with such an approach is that basic validation rules (in the client) are bypassed and must be reproduced in the interfacing program. Of course, as soon a rule has to be maintained in more than one place, there is a virtual guarantee that those rules eventually drift apart, resulting in invalid data.

By providing an interface layer at the application server, the SAP system ensures that all data fed to the system (whether batch or real-time) is processed by a single set of validation and security rules. It is technically impossible to pass the SAP system invalid data through an interface. The system can record user actions and create an audit trail for data integrity. All data changes are logged by user ID, date and time stamp, and before and after values. The data log is stored indefinitely until it is archived out of the system. The transaction log keeps an audit of all transactions executed in the system by user ID, data and time stamp, terminal ID, and detailed performance statistics. This data is stored in a cyclical file. The SAP system comes delivered with the security user information system (SUIM) and audit information system (AIS), which provide diagnostic, reporting, and auditing functionality, as well as extensive checklists to assist in ensuring systems are secure. All data is checked by the application – as a result, the data is always in sync.

11 Describe the modules within your proposed solution , and highlight in clear Manner the dependency/interdependency of each module and the nature of such dependency and the possible constraints of such relation on that might impose on the implementation and/or on the operation

All Sap modules proposed are fully integrated in real time. Customer care and billing are fully integrated with the back end ERP system that provides accounting, receivables and payables solutions. As a result there are no constraints imposed on clients. There is no need to factor integration into any implementation or costing plans.

(15)

Detailed information about available adapters, including adapters from partners, can be found at the SAP® Service Marketplace under http://service.sap.com/xi. See SAP NetWeaver® Exchange Infrastructure in Detail and Connectivity.

Adapters delivered by SAP

The SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) component supports all integration scenarios based on IDOCs, BAPI®s or RFCs. IDOC structures and BAPI/RFC signatures can be imported directly into the Repository of SAP NetWeaver XI as preparation for the implementation phase.

GRAPHIC (Adapter Overview)

Adapters to Connect to Existing SAP Systems

IDoc Adapter

RFC Adapter

Adapters to Connect to Third Party and Messaging Systems

File/FTP Adapter

Database (JDBC) Adapter

Java Messaging Service (JMS) Adapter

Specialized Messaging Adapters "Plain HTTP" Adapter

SOAP Adapter

Adapters to Connect to Marketplaces Marketplace Adapter

Connectivity to Mainframes

Connecting CICS and SAP NetWeaver XI by Using SOAP

The IDOC- and the RFC-Adapter can be used to communicate with SAP system release versions 3.1x or higher in both directions (inbound and outbound). For applications executed on the SAP NetWeaver Application Server (SAP NetWeaver AS) component version 6.20 or higher, custom ABAP™ or Java Proxies can be generated into the application (as Java or ABAP Objects classes). In these cases, the proxy runtime of SAP NetWeaver AS executes the HTTP-communication to the SAP NetWeaver XI integration server, while the customer-specific proxies are either called by the application (inbound proxy) or the proxy runtime (outbound proxy) to exchange data with the application via local interfaces. More and more mySAP™ solutions (mySAP SCM, mySAP CRM, and so on) are delivered with built-in standard proxies. Therefore, SAP NetWeaver XI proxies will more and more become a standard interface to SAP systems, just like RFCs, IDocs, and Web Services.

13 Please confirm if the proposed product can be run on external front portal (e.g. Citrix, SSL virtual workspace ..etc ). If, yes please provide cases (reference clients) where such implementation has been done. Explain if such implementation has any limitation on the full functionality of the proposed solution ( Java applet limitation , Active-X , https …. Etc )

SAP solutions may be used with the Citrix front portal solution. Sap is also certified for WTS. Sap has many customers using Citrix. SAP uses Citrix for global traing on SAP systems and Citrix itself uses SAP.

14 Please describe the techniques/methodology to facilitate 3rd_{party product to integrate with the proposed solution, please explain in details all technical,}

licenses and legal aspects.

(16)

Phase. The Test Scenarios, Test Cases and Test Data will be prepared by FEWA and Wipro jointly.

Wipro shall use SAP’s BR Tools for Backup, Restore & Recover Features. (Request Anand to add content if he has factored HP Dataprotector or any Data Back up tools for managing Tape Library for Backup & Restore Functions).

Load / Stress / Volume Testing Tools: Wipro shall use HP LoadRunner for performing these Tests during the Realization to see the Performance under Sustained periods. The Licenses for using these tools shall be procured by Wipro on Limited Period Basis (One Month). If FEWA desires to have these tools for Longer Periods, the same shall be provided after initiating Change Control Procedure.

16 Please indicate all hardware requirement for your proposed solution including (Memory, CPU, OS, Storage Space for application “disk space” and also indicate the Database/reports storage space requirement per month “based on your proposed solution and on your understanding of FEWA business nature and load”.

IMPLEMENTER TO ANSWER – Anand to Respond with BOM and Sizing Summary.

17

_{What type of import and export capabilities are available for creating customized data feeds?}

By using SAP Data Transfer Workbench you can transfer data which supports the automatic transfer of data into the system.

The Workbench is particularly useful for various business objects with large amounts of data. It guarantees that data is transferred efficiently and ensures that data in the system is consistent. The Data Transfer Workbench was designed for the initial transfer of data. If you want to transfer data repeatedly at regular intervals, we recommend that you use tools such as ALE (through the IDoc interface) or the Process integrator (PI)

The Data Transfer Workbench provides the following functions:

• Administration and organization of data transfer projects

• Tools for analyzing the required SAP structures

• Integration of standard data transfer programs

• Registration and integration of your own data transfer programs and help programs

• Various techniques for loading data

The data is read from a transfer file in SAP format and loaded into your system using one of the techniques below:

1. BAPI interface

2. Batch input

3. Direct input (DINP)

(17)

that covers all key aspects of solution deployment, operation, and continuous improvement. It is a centralized, robust application management and administration solution that combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership. SAP Solution Manager is now mandatorily used in all SAP Consulting implementations of core SAP processes. SAP Solution Manager Enterprise Edition provides additional functionality required for SAP Enterprise Support services. Features and functions that we can leverage are:

· Service level management – SAP Solution Manager allows you to define and report service levels, providing an automated reporting across several systems requires less manual effort. Service Reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.

· Service processing – SAP Solution Manager makes appropriate service recommendations and acts as a vehicle for delivering SAP support services. These include services from the SAP Safeguarding portfolio, which helps you manage technical risk; services from the SAP Solution Management Optimization portfolio, which helps to exploit the full potential of your SAP solutions; and services from the SAP Empowering portfolio, which helps acquire core competencies to manage your solutions.

Specifically, Solution Manager facilitates the running of your End to End operational support through managing: · Root Cause Analysis – SAP standards for Incident Management

· Change Control – SAP standards for Change Control and Application Management SAP standards for Functional, Regression and Volume Testing · Business Process Integration and Automation - SAP standards for Job Scheduling, Interface and Business Process Monitoring

· Enterprise SOA readiness - SAP standards for Service Enablement, Upgrades and Migrations

· End-user training – SAP Solution Manager helps create and deliver interactive learning units to educate all users about new or changed functionality, thus reducing the cost of end-user training.

· Upgrade and change management – You can manage and accelerate your upgrade and change management projects with SAP Solution Manager to increase ROI.

· SAP implementation – SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.

. Synchronization of custom settings – With SAP Solution Manager, you can maintain consistency as you customize your heterogeneous IT

environment. It enables safer administration of customization, less error-prone replication of custom settings, and simpler consistency checks. SAP Solution Manager reduces manual synchronization efforts by automatically distributing custom settings to various systems simultaneously, and by centrally managing all requests to synchronize settings.

· Testing – SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.

· IT and application support – The support desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.

· Solution monitoring – SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.

· Service-level management and reporting – SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provide a consolidated report containing the information you need to make strategic IT decisions.

· Service processing – SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.

(18)

any external security components that will be require

Access to SAP® software is only via a valid user name and password. The user is then assigned roles, which relate to authorization objects. Various rules exist for password changes, including length, special characters rules, and password expiry times.

Several mechanisms are available for authenticating users on the SAP NetWeaver® platform. When many systems are involved in your system landscape, SAP also supports the following option for single sign-on:

• User ID and Password – default mechanism that can be used for user authentication for both SAP and Internet protocols, regardless of the front-end client.

• Secure Network Communications (SNC) – can be used for user authentication and single sign-on when using SAP protocols (dialog, RFC) and the SAP GUI for Windows or SAP GUI for Java as the front-end clients. Transport layer security is also provided when using SNC.

• SAP logon tickets – can be used for single sign-on when using Internet protocols and a Web browser as the front-end client.

• SSL and X.509 client certificates – can be used for both user authentication and single sign-on when using Internet protocols and a Web browser as the front-end client.

• Pluggable Authentication Services (PAS) – available as a service with the SAP GUI for HTML Web GUI. The user is issued a logon ticket after being authenticated by an external authentication mechanism.

SAP also provides the SAP NetWeaver® Identity Management solution. An overview of the architecture of the SAP NetWeaver® Identity Management component is available in the figure below. The provisioning option of SAP NetWeaver Identity Management stores all identity, configuration and policy, and audit and logging data in a database. User management and approval processes are managed through a Web-based graphical user interface (GUI). Configuration is managed through a Windows thick client (Microsoft Management Console – MMC). Connectivity with authoritative and target applications is done through the dispatchers. User provisioning and identity data synchronization jobs are set up in the database to be picked up by available dispatchers. Three-tier architecture allows high levels of availability and scalability.

(19)

open against a single ID.

21 What kind of external devices/software are recommended for system/Database backups, please include recommended backup process and methodology. What kind of external devices/software are recommended for system/Database restore/recovery, please include recommended restore/recovery process and methodology.

Implementer to respond – Anand to respond if we are proposing Tape Library

22 Nature of possible operations at the remote locations when central server and/or WAN link is down.

Subject to technical design based on the requirements of each process step.

23 In case of any failure of the central server what is the provision to retrieve the business continuity ( Hot/cold-standby server, DR support ) and what is the expected downtime for each scenario , also list the requirement for DR setup .

Disaster recovery strategies rely on partner products, such as cluster solutions, replication software, and storage. SAP® software comes with all the necessary components to ensure high-availability and effective ability for recovery, should faults occur. SAP software comes with its own backup and restore utility and supports both full and partial backups. The SAP software backup utility supports two modes of backup: offline and online. In offline mode, applications are not available for the duration of the backup. In online mode, users have full access to the application while the backup is running. From our perspective, one method is as good as another.

SAP software provides transaction rollback (not saving incomplete transactions) and database recovery in the event of software interruptions. From the point of view of database programming, a database logical unit of work (LUW) is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been executed successfully, the database is in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started.

The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In SAP software, you can use either implicit or explicit commands to trigger database commits and rollbacks. SAP has developed a unique technique that completely insulates the user from low-level locking that takes place at the database level. Our use of an LUW makes this possible. Because of the LUW technique, SAP software is then free to establish actual database locking in line with whatever particular database vendors consider optimal for their database.

The LUW of SAP software is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW. Unlike a database LUW, an LUW in SAP software can span several dialog steps, and can be executed using a series of different work processes. In an application program, you end an LUW of SAP software either with the “COMMIT WORK” or “ROLLBACK WORK” statement. An SAP software transaction is an application program that you start when using a transaction code. It can contain one or more LUWs of SAP software. Whenever the software reaches a “COMMIT WORK” or “ROLLBACK WORK” statement - not at the end of the last dialog step of the SAP software transaction - it opens a new LUW of SAP software. If a particular application requires that you write a complex transaction, it can often be useful to arrange logical processes within the SAP software transaction into a sequence of individual LUWs of SAP software.

24 Please suggest what operations can be supported at stand-alone branches, which do not have network connectivity. Elaborate the possible architecture and functional coverage.

(20)

26 In case of any failure of the main servers and as result system switch to offline mode how Data synchronisation will be achieved?, what about the system feature to assure Data integrity? please explain

SAP software provides transaction rollback (not saving incomplete transactions) and database recovery in the event of software interruptions. From the point of view of database programming, a database logical unit of work (LUW) is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been executed successfully, the database is in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started.

The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In SAP software, you can use either implicit or explicit commands to trigger database commits and rollbacks. SAP has developed a unique technique that completely insulates the user from low-level locking that takes place at the database level. Our use of an LUW makes this possible. Because of the LUW technique, SAP software is then free to establish actual database locking in line with whatever particular database vendors consider optimal for their database.

The LUW of SAP software is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW. Unlike a database LUW, an LUW in SAP software can span several dialog steps, and can be executed using a series of different work processes. In an application program, you end an LUW of SAP software either with the “COMMIT WORK” or “ROLLBACK WORK” statement. An SAP software transaction is an application program that you start when using a transaction code. It can contain one or more LUWs of SAP software. Whenever the software reaches a “COMMIT WORK” or “ROLLBACK WORK” statement - not at the end of the last dialog step of the SAP software transaction - it opens a new LUW of SAP software. If a particular application requires that you write a complex transaction, it can often be useful to arrange logical processes within the SAP software transaction into a sequence of individual LUWs of SAP software.

27 Provide the minimum WAN bandwidth requirement for remote location per user keeping in mind FEWA will have MPLS network at the

implementation time, any network protocol/Interface is required (please state all network dependencies ). Also please include your recommendation for WAN accelerator

Implementer to respond – SI Team to respond

28 What is the guaranteed response time of the proposed solution ( assuming high speed network is available )

Implementer to respond – SI & EPD Team to respond

29 Does the system support access of the application from a remote location through VPN/SSL-VPN? Provide details.

VPN/SSL-VPN is fully supported by Sap applications. See supporting material on Netweaver for full details.

30 In case of replication of data, please detail the type of data that is replicated across locations. Describe your replication mechanism.

SAP supports data replication where appropriate to support processing, for example when using mobile devices. Installed locally on each mobile device, the SAP NetWeaver® Mobile component client includes its own synchronization layer, persistence layer, user interface (UI) runtime (local Web server or abstract windowing toolkit), and other convenience application programming interfaces offered to mobile applications. This is all part of a light-installation runtime environment that extends enterprise capabilities to users, whether or not they are connected to the network. Mobile applications use the functionality offered by the SAP NetWeaver Mobile client to run their local business logic, data persistence, data validation, and UI.

In the disconnected mode, users access data stored on the client’s local data persistence. When the client is in online mode, users can synchronize clients to upload the changed data and get the latest data from the data orchestration engine (DOE).

For data changed or edited in the field, SAP NetWeaver Mobile provides a synchronization and replication layer that resolves enterprise-level data redundancy by synchronizing the mobile device with back-end systems through the DOE to smartly resolve all redundancies in the application server proactively, to ensure data consistency. SAP NetWeaver Mobile also includes a centralized, role-based deployment console that simplifies deployment tasks in a global, multiple-device IT environment.

(21)

32 Support mirroring of data into a secondary server (e.g. Batch, Real-time, Online (time lag) .. etc ) please provide details Anand to Respond

33 In case the system requires specific drivers for ( Printers, scanners ..etc ) , mention them along with the name of the vendors. Anand to Respond _____________________________________________________________________________________ _____________________________________________________________________________________

_____________________________________________________________________________________

34 Will the size of database affect the speed of retrieval? , please explain

Retrieval speed is always a function of ecosystem design. By ensuring the correct combination of HW, network and management strategies, response times can be kept to suitable levels.

2007

2008

2009

2010-2015

2006

SAP NetWeaver

SAP ERP 6.0

Enhancement Packages

ERP

Release

(22)

provide multi-dimensional analysis. It comes pre-configured with data models based on SAP’s industry experience (both cross-industries and specifically for retail) covering all aspects - such as procurement, supply chain, financials, sales, inventory, assets, and so on. The models, however, are open to additional configuration to meet the specific needs of the business, but the approach means a much quicker time or lower cost to implement based on a rigorous (and widely accepted) metadata schema.

SAP NetWeaver BI has a range of ETL tools (extraction, transformation, and load). From the SAP transactional systems there is a very tight level of integration with approximately 700 integration points, which include the ability to drill back from the reports to actual transaction screens. Load supports a delta mechanism (loading only changes since the last load) and real-time data feeds. The data warehouse is equally suited to loading non-SAP data via a range of in-built ETL capabilities from simple flat file loads to the universal data integrator (UDI) that connect via ODBO and JDBC drivers to over 200 potential sources.

Reporting is available in a thin client (needs only a Web browser such as Internet Explorer / Firefox) and an MS Excel client. Both interfaces give the end users an interactive reporting environment where they can slice and dice the data, filter on fields and drill down to the detail.

The solution has a series of open interfaces for loading data, exchanging metadata (designed to meets the CWMI – common warehouse metadata interchange standards) and ODBO, BAPI® programming interface and xmla interfaces for alternative front-end reporting tools. There are many certified third party reporting tools that can access via these interfaces including tools such as Cognos, Business Objects, SAS, Hyperion, and so on.

1.1.3 Recommended Hardware

Please provide the details of proposed hardware that comply with the ERP principle recommendations that will be the foundation of the entire solution ( please indicate your hardware solution is it based on new hardware or using the existing one). In all solution scenarios, the offer should cater for the following

1) FEWA would prefer to have the following environments of the application: a. Sand-box

b. Development c. Test

(23)

3) Current business volumes and expected system performance are provided in Annex B - Appendix 3A of the bid documents. The system should be sized to support at least 20% growth in business volumes for a 5 year period, without any performance degradation or the need of hardware upgrade. 4) Hardware redundancy without any single point of failure

5) In addition to the servers and storage(SAN), Bidders are also requested to provide specifications for other devices such as: a. High Speed, Quality, and Heavy Duty printers to facilitate printing of customer bills

b. Storage devices c. Backup devices

d. Any other devices, that may be required for smooth operations of the proposed solution.

6) Please provide an overall schematic layout for the hardware environment that clearly highlight the connectivity between them and the network interface with server/storage assignment per module (if any) . In addition, for each element please list the following facts:

System name Model

Processor (Please provide details) Proposed RAM/ Maximum RAM

Proposed disk drive capacity/ Maximum disk drive capacity

Operating System

Name and version

Networking protocol supported (Layer 2 and Layer 3 ) Other details

1.2 Proposed Application Modules and E-Services Interface

1.2.1 Proposed Application Modules

Please provide the following details for each of the proposed functional areas. Customer Relationship Management& Billing, Finance & Accounting, Supply Chain Management, Human Capital Management, Asset Lifecycle Management, Performance Management (Business Intelligence)

Application Area: Customer Relationship Management& Billing, Finance & Accounting, Supply Chain Management, Supplier relationship

management, Human Capital Management, Enterprise Asset Lifecycle Management, Mobile infrastructure, Performance Management/Business Intelligence (business Objects) and NetWeaver

(24)

Management, Maintenance, Document Management System, Human Resources, Self Service Human Resources…)

2. ERP business Suite ( 290 users, developer, business expert, professional & limited professional + 1000 employee self service)

3. Payroll ( 3200 employee master records)

4. II- IS-U CRM & Billing for Utilities Customer Financial Management for Utilities 5. Business Objects Reporting ( Crystal Reports, Web Intelligence,Polestar, Xcelcius Enterprise,Enterprise Premium, Dashboard Builder, Live Office, Mobile, Voyager..) 6. Business Information & Analysis Package ( 290 users)

7. Energy Data Management for Utilities 8. AMI – optional

9. Environment, Health & Safety – optional 10. WCM – Work clearance management – optional 11. BCM - Business Communication Manager - optional

2 Please provide detailed illustration for the key features of the proposed application modules. In case pre-printed literature is available describing the features, please attach them as appendixes and mention the reference in this section

Please see fle attached

1- SAP_Business_Suite__Achieve_Process_Excellence,_Lower_Costs,_Seize_Opportunities_(A4).pdf 2- CustomerCare_&_Billing_(A4).pdf 3- Enabling_AMI_Integration_for_Utilities_(A4).pdf 4- SAP_Business_Communications_Management_for_Utilities_(A4).pdf 5_SAP_EHS_Manage ment_Solution_Brief.pdf 6- StreamServe_Utilities_-_Solution_Brief_(A4).pdf 7- StreamServe_Utilites_Bill.pdf 8- Enterprise_Asset_Management_Solution_Brief_(A4).pdf 9- Maximizing_Revenue_and_Retention_.pdf 10- Rate_Life-Cycle_Management_for_Utilities_(A4).pdf 11- Interactive_Dashboards_for_Decision_Makers_.pdf 12- Manage,_Share,_and_Deliver_Critical_Business_Reports_.pdf 13- SAP_BusinessObjects_Integration_.pdf 14- SAP_BusinessObjects_Live_Office_.pdf 15- SAP_BusinessObjects_Xcelsius_Enterprise_(A4).pdf

3 Please provide flow charts for the key business processes supported by the proposed application modules. Use separate sheets, as needed. Please see Attached files

Utilities Business Processes.pdf

(25)

The following graphic is a simple overview showing how SAP NetWeaver process integration (PI) positioned. The important components and concepts are listed on the right-hand side.

SAP NetWeaver PI is part of the usage type Process Integration.

b. How the integration is achieved, i.e. (Online/Batch)? Realtime (onlne), you can also use event driven.

5 Are there any pre-requisites for installation/implementation of proposed modules? In case there are any, please list below all the modules required to implement the proposed module. (E.g. In order to deploy Payroll module, implementation of HR module will be a pre-requisite)

The Roadmap for FEWA has been designed keeping in view these Pre-requisites. There is a Logical progression to implement Modules. FICO & Logistics is the Basic Component which should be implemented before IS-U, CRM, BO and Portals are implemented.

6 Please provide the following implementation considerations for implementing the proposed application modules. This should be provided in terms of: (Please use separate sheets, as necessary)

(26)

the operation (example: For implementing General Ledger, the configuration options may include definition of Financial Year, Chart of Accounts, Currencies, etc.)

c. Key information requirements from FEWA (example: For implementing Item Master, FEWA may need to provide Item Categories, Item Details, Replenishment Planning Parameters, etc.)

7 Does the proposed application module provide APIs for interfacing with any 3rd_{party application? If so, please provide a list of available APIs for} the proposed application module and the financial implication if any

SAP integrates with Third Party Applications either Asynchronously using Flat File Upload & Download using BDC’s.

SAP Can also Integrate Synchronously using BAPI’s, BADI’s, EDI IDoc’s, Process Integrators in Non XML or XML Formats. SAP’s Transactions are exposed to Web for any Service to be Consumed by the Third Party System. There is no Additional Financial Implication on the same.

8 What are the functional enhancements/new features planned in the next release of the proposed application module and the proposed release, please include the expecting releasing date.

Proposed Release Date: Information is provided in Page 19 of this document.

(27)

1.2.2 Website and E-services

1 Please provide a note describing the e-services interface capability of each of the below modules

• Customer Relationship Management and Billing

• Finance and Accounting

• Supply Chain Management

• Human Capital Management

• Asset Lifecycle Management

• Performance Management (Business Intelligence)

• Document management system

• Supplier Relationship Management

(28)

2 Does the proposed solution support interface capabilities with an external e-services portal. If your answer is yes , please indicate if _{interface feature has any limitation , if so please list all of the limitation. In addition please indicate the needed professional services ,} software licenses, Application .. etc that might needed to implement the interface .

No Limitations

In your proposed solution, please provide a detailed description of the E-services Portal capabilities See diagrams below

(29)

(30)

1.2 Requirements Compliance Remarks

Eservices Portal SUP MOD 3RD CST FUT NS

1.2.1 _{Activation of Supply} Yes Using e-services

enabled by SAP NetWeaver

1.2.2 _{Billing complains} Yes Using e-services

enabled by SAP NetWeaver 1.2.3

Change of bill address

Yes _{Using e-services}

enabled by SAP NetWeaver 1.2.4 Bill enquiry

Yes _{Using e-services}

1.2.5 _{Change of landlord info} Yes Using e-services

1.2.6 Clearance certificate request Yes Using e-services

enabled by SAP NetWeaver 1.2.7 Planned Outage :A map service can be published

for customers whose geographical location can be highlighted as part of the planned outage to reflect the affected AREAS.

Yes Using e-services

enabled by SAP NetWeaver and utilizing the Outage management and GIS systems

1.2.8 Clearance payment request Yes Using e-services

1.2.9 Manage statement code Yes Using e-services

1.2.10 Tariff calculator Yes Using e-services

1.2.11 Statement code request Yes Using e-services

1.2.12 Contractor Registration, renewal and payment Yes Using e-services

(31)

/Temporary/Additional Load/Shifting enabled by SAP NetWeaver

1.2.14 Building NOC Yes Using e-services

1.2.15 Demolition NOC Yes Using e-services

1.2.16 Distribution Substation Inspection Yes Using e-services

1.2.17 Electronic Building Violation Service Yes Using e-services

1.2.18 Local Purchase Yes Using e-services

1.2.19 LV Design Provisional Approval Yes Using e-services

1.2.20 LV Inspection & Release of Supply Yes Using e-services

1.2.21 Tenders Yes Using e-services

1.2.22 Substation Layout Drawing Yes Using e-services

1.2.23 Substation Location & Size Approval Yes Using e-services

1.2.24 Project-Generation Document Submission Yes Using e-services

1.2.25 LV Shop Drawing Approval Yes Using e-services

1.2.26 Provide Secure E-services for online payment Yes Using e-services

1.2.27 FEWA Careers and self services Yes Using e-services

1.2.28 Registered Customer for FEWA e-services Yes Using e-services

enabled by SAP NetWeaver In your proposed solution, please provide a detailed description of the Website Portal

1.2 Requirements Compliance Remarks

Eservices Portal SUP MOD 3RD CST FUT NS

1.2.29 _{Dynamic Menus} Yes Using e-services

enabled by SAP NetWeaver 1.2.30 _{Administration modules which will give FEWA}

the capability to upload new facilities, pages, etc.

(32)

Well presentable website which is representative

of FEWA’s market stature enabled by SAP

NetWeaver

1.2.32 _{Easy integration with third party applications.} Yes Using e-services

enabled by SAP NetWeaver 1.2.33 _{Full training to be provided for website}

development and support

enabled by SAP NetWeaver 1.2.34 _{Website Portal should support Arabic & English}

(GUI)

enabled by SAP NetWeaver 1.2.35 _{Bidder should proved minimum three prototypes}

for the Website design to be approved by FEWA.

Yes

Using e-services enabled by SAP NetWeaver

1.3 Document Management System

One of the requirements within this RFP is integration between the ERP and the Document Management System (DMS).

FEWA currently has an existing DMS “SAPERION” which is interfaced with the legacy ERP solution . The Bidder has the choice to offer FEWA one of the following options

Upgrade and re-interface/integrate the existing system with the proposed ERP solution

Offer new Document Management System and migrate all the existing documents into the new platform with full integration with the ERP

We are prposing the replacement of the existing DMS system by SAP DMS. We shall use the Existing DMS Content Server assuming that the same is compatible with SAP System. In case there is a Compatibility Issue, the same shall be replicated in another System.

If the bidder decides to go with option 2 as the methodology of implementing the Document Management System, then the following requirements should be fully maintained and complied TO:

 Efficiency - No time lost filing & retrieving documents

 Collaboration - Share documents with others among the network any time any where any media  Access - Access documents over the Intranet, Internet and/or extranet

 Security - Provide controlled access to specific document based on TAG , and with access log  Savings - Reclaim space used to stored documents

 Compliance - Comply with government regulations for Integrity, Availability, Security and Confidentiality  Disaster Recovery – Ability to ensure business continuity by protecting documents from natural and other

disasters ( Locally and/or offsite )

 Simplification - Single mechanism to manage both electronic and paper documents

Please provide a note describing the Document Management system, Clearly clarify compliance of the down below :

1.3 Document Management System Compliance Remarks

SUP MOD 3RD CST FUT NS

1.3.1 _{FEWA can create a single centralized repository of all their electronic &} paper documents. And ability to provide their staff with controlled access to this repository with Hierarchical Storage Management.

Yes Using

SAP core DMS System 1.3.2 _{The document management software provides fast, reliable and}

security-controlled access to these documents throughout the company network

Yes Using

SAP core DMS System

AnnexB - Appendix3B - Kiran

Tender No.

15EW/2009

B

IDDING

D

OCUMENTS

F

OR

A C

ONTRACT

T

O

D

ESIGN

, S

UPPLY

, I

NSTALL

, I

MPLEMENT

, T

RAIN

AND

P

ROVIDE

S

UPPORT

S

ERVICES

FOR

AN

ERP

AND

CRM /B

ILLING

S

OLUTION

ON

A

T

URNKEY

B

ASIS

A

NNEXURE

B:

A

PPENDIX

3B

C

OMPLIANCE

S

HEET

Contents

1 Proposed ERP and CRM/Billing Solution...1

1.1 Overall System Architecture...1

1.2 Proposed Application Modules and E-Services Interface...21

1.3 Document Management System...30

1.4 Functional/Technical Requirements...34

2 System Installation...122

2.1 Installation Services...122

2.2 CVs of proposed team members for System Installation...122

3 System Implementation...124

3.1 Implementation Approach...124

3.2 Data Migration...126

3.3 Interfaces...127

3.4 Documentation...127

3.5 Bidder Staffing Plan...129

3.6 CVs of team members...131

3.7 FEWA team involvement...133

3.8 FEWA Infrastructure Requirements...138

4 Training...139

5 Support Questionnaire...141

6 BIDDER Organization Details...143

6.1 Company Profile...143

6.2 Reference Site Details...144

6.3 Experience of implementing in the GCC/ UAE and in Utilities in the Gulf

region...145

7 Other Formats...147

_{What type of import and export capabilities are available for creating customized data feeds?}