AnnexB - Appendix3B - Kiran

Federal Electricity and Water Authority REQUEST FOR PROPOSAL Tender No. 15EW/2009

BIDDING DOCUMENTS FOR A CONTRACT TO DESIGN, SUPPLY, INSTALL, IMPLEMENT, TRAIN AND PROVIDE SUPPORT SERVICES FOR AN ERP AND CRM /BILLING SOLUTION ON A TURNKEY BASIS

ANNEXURE B: APPENDIX 3B COMPLIANCE SHEET

Annex B: Appendix 3B- Compliance Sheet

Page ii of 89

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 7.1 Form for Clarification Questions...................................................................147 7.2 Form for Deviations from RFP......................................................................148

Annex B: Appendix 3B- Compliance Sheet

Page 1 of 89

1

Proposed ERP and CRM/Billing Solution

It is mandatory for all bidders and all their related subcontractors and/or partners (if any) to fill all listed items within this document in a detailed fashion. Failure to provide all the needed information can result for immediate disqualification.

1.1

Overall System Architecture

1.1.1

General Product Information

Kindly furnish information for each product / application separately in case more than one product / application is offered System name

ERP 6.0 (Base Product), SAP For Utilities

Date of launch ( Globally and in UAE )

June (ERP 6.0), SAP for Utilities, multiple releases since late 90’s.

Date when first client site went live ( in UAE ) with client name

First ERP 6.0 clients in 2006. SAP for Utilities currently under implementation at DEWA. Live in Saudi Arabia since 2004.

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

• • •

Today, more than 82,000 customers in over 120 countries run SAP applications and the demand for the SAP ERP 6.0 application software in production environment ( in 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.

Clients using the proposed 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

Largest customer for the proposed product

• • • • •

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

Name of the customer Number of customer installed accounts ( active accounts )

C: \Users\ C5037555\ C: \Users\C5037555\ Document s\Client s\ FEWA\ Document References_ERP_6.xls s\Clients\ FEWA\ References_I S_Ut ilit ies.xls

Transaction volume Number of remote site DR availability ( is it hot-standby or cold-standby )

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

Annex B: Appendix 3B- Compliance Sheet

Page 2 of 89 Is it restricted as to the location of installation or global? ( explain the license mobility if its supported )

contracts.

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

The installation is not restricted. The regions that the software may be utilized in a documented in the contract.

• • •

• • • •

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 goto release, and with SAP enhancement packages, we continue 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.

Annex B: Appendix 3B- Compliance Sheet

Page 3 of 89 What is the road map of the proposed product for the next 3 to 5 years? Please As the world’s leading provider of business systems, SAP has a proven track record in developing software and providing regular upgrades to assist our customers perform business more effectively explain it in details. Use additional sheets if required. and efficiently. We recognise that our customers need to have tools and technologies that provide flexible business processes and adaptive business models to enable you to respond rapidly to 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

In recent years, major version releases have included: Available since May 2000 Available since July 2002 ERP 2004 Available since June 2004 ERP 2005 Available since October 2005 ERP 6 Available since June 2006

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

Annex B: Appendix 3B- Compliance Sheet

Page 4 of 89 What is the next scheduled major release of the proposed software?

Please see product roadmap above

How often are new versions released?

Please see the attached material on SAP’s upgrade strategy which is based on

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 All additions have been incremental over time, no major re-writes. indicate which release and when it has been released. Indicate all users screens (if any) which will not be in dual languages Arabic ERP and SAP CRM and Billing for Utilities support Arabic. and English ( if you didn’t indicate any , then FEWA assume all screens will be bi-lingual (Arabic/English )

1.1.2

System Architecture

(Kindly furnish information for each solution separately in case more than one application/option is offered)

Annex B: Appendix 3B- Compliance Sheet

Page 5 of 89 1

Provide a detailed architecture of the proposed solution on a separate sheet. This should include but not limited to :

•

Application architecture showing the interaction of the different modules being proposed

•

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.

Annex B: Appendix 3B- Compliance Sheet

Page 6 of 89 2

Please provide architecture schematic for the major components required to implement your solution (s). Complement the schematic with typical hardware platforms, OS, memory requirements, and all prerequisites for each component. System architecture and proper sizing of a customer’s mySAP™ Business Suite application is of the highest concern to SAP. To ensure proper sizing for the 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

Annex B: Appendix 3B- Compliance Sheet

Page 7 of 89 3

From the offered applications, Please provide the following details of the systems that the proposed software has been interfaced with:

• • • • •

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)

• •

• Report generator (e.g. report writer)

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

See previous section.

Annex B: Appendix 3B- Compliance Sheet

Page 8 of 89 Presentation tools

See previous section.

Development language

Customers get the source code of SAP applications, as well as the development tools used to create the applications. The development tools support both ABAP (Advanced Business Applications Programming) and 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

Annex B: Appendix 3B- Compliance Sheet

Page 9 of 89 Interface developer

SAP’s products are extendable by a variety of processes including configuration, the use of user exits, and finally modification of the code. (A more detailed description of each is provided below.) Configuration is the simplest of the options and entails using the provided SAP tools to configure the system to meet a wide variety 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. Additionally, Business APIs (BAPIs) are traditional APIs that allow communication using technologies such as

Annex B: Appendix 3B- Compliance Sheet

Page 10 of 89 Application Server

SAP NetWeaver Application Server – Supports platform-independent Web services, business applications, and standards-based development, enabling you to leverage existing technology assets for Web-services-oriented solutions

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

Development Tool

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 • 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

Annex B: Appendix 3B- Compliance Sheet

Page 11 of 89 6

Describe your logical and/or physical data model. (Please provide the models for review.) Please describe the ease and process of adding custom fields to your product’s data architecture. 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.

Annex B: Appendix 3B- Compliance Sheet

Page 12 of 89 9

Please describe the type of Restore/Recovery procedures supported within the proposed package, in the event of transaction or process failure and the estimated time to complete the process, also indicate if such Recovery/Restore procedure will cause downtime? An SAP® software implementation comes with all the necessary components to ensure high availability and effective recoverability when faults occur. SAP 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.

Annex B: Appendix 3B- Compliance Sheet

Page 13 of 89 12

Please describe the interoperability of the proposed product. And what standard interfaces is supported , and how FEWA can utilize the proposed product to interface/integrate with other application ( if its require ) e.g. ( Contact Center , QMS .. etc ) 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 Adapters to Connect to Third Party and Messaging Systems Systems File/FTP Adapter IDoc Adapter Database (JDBC) Adapter RFC Adapter Java Messaging Service (JMS) Adapter Specialized Messaging Adapters Adapters to Connect to Marketplaces "Plain HTTP" Adapter

Marketplace Adapter

SOAP 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. Please see the answer given to Question 12 in this section.

Annex B: Appendix 3B- Compliance Sheet

Page 14 of 89 15

Please explain and list all available testing , auditing , and backup/restore/recover features that is included in the proposed solution without any additional licenses and/or additional cost. Functional & Technical Testing Tools: Wipro shall use Solution Manager eCATT tool for performing Testing the Functionality customized during the Realization 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)

Data conversion using the Legacy System Migration Workbench (LSMW).

Annex B: Appendix 3B- Compliance Sheet

Page 15 of 89 18

Mention the database management tools that is included within your proposed offer (If any eg. Schema management, archiving storage tools, data backup recovery tools, database monitoring, performance tuning and optimization, job creation & scheduling, security, file management, etc) The SAP Solution Manager application management solution, is provided free of charge and facilitates technical support for distributed systems with functionality 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.

· .

· · · · ·

Annex B: Appendix 3B- Compliance Sheet

Page 16 of 89 19

Please describe the nature and levels of security measure that is supported by the proposed system ( this should include Audit capabilities, logging details, Database file lock, encryption , Access level , password strength and enforcement .. etc ) . In addition, also outline the details and architecture of 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.

Annex B: Appendix 3B- Compliance Sheet

Page 17 of 89 20

Does the product handle concurrent uses of the same ID? If yes then explain the handling process and flow , what is the impact on the security side ?, if not please explain the log-off enforcement for idle users , and also explain the alarming and log activity for such scenario SAP uses the named user concept and does not support multiple users of the same ID as it creates a security risk. SAP does allow users to have multiple sessions 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 23

24

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. 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. Please suggest what operations can be supported at stand-alone branches, which do not have network connectivity. Elaborate the possible architecture and functional coverage. Implementer to respond

Annex B: Appendix 3B- Compliance Sheet

Page 18 of 89 25

Availability of (i)Test system , (II) Production system , (III) Standby System, These are fully supported. The integrated transport management system controls all movement between environments in a secure and controlled manner.

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 30

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. 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.

Annex B: Appendix 3B- Compliance Sheet

Page 19 of 89 31

In case of modules being tightly integrated, effect of any change made to an application on the other applications? SAP upgrade process ensures full synchronization across applications. All applications are kept in synch using the enhancement package concept. Clients add just the business functionality required, enhancement packs ensure all affected application components are synchronized.

2006

2007

2008

2009

2010-2015

Enhancement Packages SAP ERP 6.0

Next ERP Release

32

SAP NetWeaver

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.

Annex B: Appendix 3B- Compliance Sheet

Page 20 of 89 35

Please provide the technique and integration for Data Warehousing for all historical data The SAP® solution includes the SAP NetWeaver Business Intelligence (SAP NetWeaver BI ) component, which is a fully functional, end-to-end data warehouse that is tightly integrated to SAP’s transactional systems, but open to other data sources. It is built on data warehousing “best practices”, using star-schema to 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

Annex B: Appendix 3B- Compliance Sheet

Page 21 of 89 d.

Production

2)

The recommended hardware deployment architecture should consider a Disaster Recovery provisioning site

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 1

Please provide a list of the application modules proposed to address the requirements of this functional area:

Annex B: Appendix 3B- Compliance Sheet

Page 22 of 89 Application Module 1.

Core ERP ( Financials & Controlling, Supply Chain Management, Asset Lifecycle 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

12345_SAP_EHS_Manage 6SAP_Business_Suite__Achieve_Process_Excellence,_Lower_Costs,_Seize_Opportunities_(A4).pdf CustomerCare_&_Billing_(A4).pdf Enabling_AMI_Integration_for_Utilities_(A4).pdf SAP_Business_Communications_Management_for_Utilities_(A4).pdf ment_Solution_Brief.pdfStreamServe_Utilities_-_Solution_Brief_(A4).pdf

789101112StreamServe_Utilites_Bill.pdf Enterprise_Asset_Management_Solution_Brief_(A4).pdf Maximizing_Revenue_and_Retention_.pdf Rate_Life-Cycle_Management_for_Utilities_(A4).pdf Interactive_Dashboards_for_Decision_Makers_.pdf Manage,_Share,_and_Deliver_Critical_Business_Reports_.pdf

131415SAP_BusinessObjects_Integration_.pdf SAP_BusinessObjects_Live_Office_.pdf 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

Annex B: Appendix 3B- Compliance Sheet

Page 23 of 89 4

Please provide details of how the proposed solution modules integrate/interface with the relevant modules of other application to complement the solution. This should include the following details: a. An overall schematic of the integration across modules identifying the exchange of key data elements 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. 5

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

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)

Annex B: Appendix 3B- Compliance Sheet

Page 24 of 89

7

a.

An Implementation Checklist, listing the key steps adopted while implementing this module

b.

Available configuration options highlighting the key parameters that can be configured in the system, FEWA will decide the best approach for 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.)

Does the proposed application module provide APIs for interfacing with any 3 rd 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. Functional Enhancements Planned: Information is provided in Page 19 of this Document.

Annex B: Appendix 3B- Compliance Sheet

Page 25 of 89

1.2.2

Website and E-services

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

They are over 2800+ e services available from SAP, See list below:

Annex B: Appendix 3B- Compliance Sheet

Page 26 of 89 Example of the e services for CRM:

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

Annex B: Appendix 3B- Compliance Sheet

Page 27 of 89

Annex B: Appendix 3B- Compliance Sheet

Page 28 of 89

1.2

Compliance

Requirements Eservices Portal

SUP

1.2.1

Activation of Supply

Yes

1.2.2

Billing complains

Yes

1.2.3

Yes Change of bill address Yes

1.2.4

Bill enquiry

1.2.5

Change of landlord info

Yes

1.2.6

Clearance certificate request

Yes

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

1.2.8

Clearance payment request

Yes

1.2.9

Manage statement code

Yes

1.2.10

Tariff calculator

Yes

1.2.11

Statement code request

Yes

1.2.12

Contractor Registration, renewal and payment

Yes

MOD

3RD

CST

Remarks FUT

NS

Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver and utilizing the Outage management and GIS systems Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver

Annex B: Appendix 3B- Compliance Sheet

Page 29 of 89 Compliance

1.2 1.2.13

Requirements Application for Permanent /Temporary/Additional Load/Shifting

Yes

1.2.14

Building NOC

Yes

1.2.15

Demolition NOC

Yes

1.2.16

Distribution Substation Inspection

Yes

1.2.17

Electronic Building Violation Service

Yes

1.2.18

Local Purchase

Yes

1.2.19

LV Design Provisional Approval

Yes

1.2.20

LV Inspection & Release of Supply

Yes

1.2.21

Tenders

Yes

1.2.22

Substation Layout Drawing

Yes

1.2.23

Substation Location & Size Approval

Yes

1.2.24

Project-Generation Document Submission

Yes

1.2.25

LV Shop Drawing Approval

Yes

1.2.26

Provide Secure E-services for online payment

Yes

1.2.27

FEWA Careers and self services

Yes

1.2.28

Registered Customer for FEWA e-services

Yes

Remarks Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver

In your proposed solution, please provide a detailed description of the Website Portal 1.2

Compliance

Requirements Eservices Portal

SUP

1.2.29

Dynamic Menus

Yes

1.2.30

Administration modules which will give FEWA the capability to upload new facilities, pages, etc.

Yes

MOD

3RD

CST

Remarks FUT

NS

Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver

Annex B: Appendix 3B- Compliance Sheet

Page 30 of 89 Compliance

1.2 1.2.31

Requirements Well presentable website which is representative of FEWA’s market stature

Yes

1.2.32

Easy integration with third party applications.

Yes

1.2.33

Full training to be provided for website development and support

Yes

1.2.34

Website Portal should support Arabic & English (GUI)

Yes

1.2.35

Bidder should proved minimum three prototypes for the Website design to be approved by FEWA.

Yes

1.3

Remarks Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver Using e-services enabled by SAP NetWeaver

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

Compliance

Document Management System SUP

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

1.3.2

The document management software provides fast, reliable and securitycontrolled access to these documents throughout the company network

Yes

1.3.3

Integrated Workflow which allows routing documents (based on preset

Yes

MOD

3RD

CST

Remarks FUT

NS

Using SAP core DMS System Using SAP core DMS System Using

Annex B: Appendix 3B- Compliance Sheet

Page 31 of 89 1.3

Compliance

Document Management System SUP

MOD

3RD

rules), and support automatic escalation flow.

1.3.4

Easy-to-use interface.

Yes

1.3.5

Greatly improved the effectiveness and efficiency of the business operations

Yes

1.3.6

With a high security measure, the proposed solution should allow document mark-ups (i.e notes and highlights) without altering the original document and also allows to print or email any document on the system.

Yes

1.3.7

Allows to locate document quickly and easily ( please explain )

Yes

1.3.8

The DMS may extract metadata from the document automatically or prompt the user to add metadata.

Yes

1.3.9

The proposed solution should support Optical Character Recognition (OCR) on scanned images.

Yes

CST

Remarks FUT

NS

SAP core DMS System and Work Flow engine Using SAP core DMS System By utilizing the internet browser or SAP GUI or MS Explorer Using SAP core DMS System Using SAP core DMS System including redlining and electronic stamp Using SAP core DMS System Using SAP search engine and use the Document Finder to find and display documents Using SAP core DMS System The Drivers used in the Scanner shall perform the OCR functions and communic ate the same to

Annex B: Appendix 3B- Compliance Sheet

Page 32 of 89 1.3

Compliance

Document Management System SUP

MOD

3RD

CST

Remarks FUT

NS

SAP in a Flat File. 1.3.9

Archived data migration from the current system

Yes

1.3.10

Interfaces, Reports and Data that are supported in English/Arabic

Yes

1.3.11

DMS should support and integrate with the ERP and CRM/Billing to achieve all the transactions that need archiving through OCR and OCX

1.3.12

Ability to archive Soft-documents as well as Hard-Documents

Yes

1.3.13

DMS should support Documents workflow.

Yes

1.3.14

Supporting the encryption of the URL in the browser for security wise.

Yes

1.3.15

Source Code

Yes

1.3.16

Develop a solution for Inbound/Outbound Letters and internal announcements … etc.

Yes

Using SAP core DMS System utilizing SAP migration tool Using SAP core DMS System Yes

1.13.17

Security

1.3.17.1

Provides role-based security for individual authors

Yes

1.3.17.2

Provides role-based security for group of authors

Yes

1.3.17.3

Provides role-based security for organizational unit of groups

Yes

1.3.17.4

Provides role-based security for individual domains/sites

Yes

1.3.17.5

Prevents "un-authorized viewing/access" after permanent deletion

Yes

Using SAP core DMS System Using SAP core DMS System Using SAP core DMS System Using SAP core DMS System Using SAP core DMS System SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles &

Annex B: Appendix 3B- Compliance Sheet

Page 33 of 89 1.3

Compliance

Document Management System SUP

1.3.17.6

Prevents viewing of expired content

Yes

1.3.17.7

Allows access to checked-out content from a secure location

Yes

1.3.17.8

Creates view-only format for content

Yes

1.3.17.9

Immediately revokes all access and view privileges

Yes

1.3.17.10

Restricts access based on profile

Yes

1.3.17.11

Restricts access based on document

Yes

1.3.17.12

Applies a security category to a file folder

Yes

1.3.17.13

Applies a security category to a document

Yes

1.3.17.14

Applies a security category to a user

Yes

1.3.17.15

Applies a security category to a group

Yes

1.3.17.16

Provides lower or equal security level in file structure

Yes

MOD

3RD

CST

Remarks FUT

NS

Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion SAP BASIS Roles & Authorizat ion

Annex B: Appendix 3B- Compliance Sheet

Page 34 of 89

1.4

Functional/Technical Requirements

The appendix provides the key requirements from the proposed ERP and CRM/Billing application. The requirements are presented in the form of a matrix. Each Bidder is required to respond as follows:

•

Respond ‘Yes’ if the requirement is fully met, or if the question asked is fully answered. Please provide information in the Comments column to describe how your company/system meets the requirement. Respond ‘No’ if the requirement cannot be met. Comments should be included if there is an alternate solution. If the requirement will be met through a planned or future release, provide details in the Comments column. Respond ‘Partial’ if the requirement is partially met AND include details as to why in the Comments column. If a requirement contains multiple points and not all can be supplied then just a single 'Partial' indication is the appropriate response. Do not address each point, but use the Comments to provide details of which of the requirements cannot be met and why. Each last level requirement should be responded to as per the following fashion

• • •

Example: Reference in Proposal Sr. No.

Requirement Description

Remark Yes

99.1

1.4.1

Sr. No.

Bidder will implement full ERP System

Part.

No

Page 26, Sec. 3

Financial Management will not be provided

Customer Relationship Management and Billing

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

1.0 Customer Relationship Management 1.1

System should enable setup of a single customer/person record in a single location, so this record is preserved when that person moves or wishes to purchase new services. System should support the tracking of complex customer ownerships associated with that person or customer. System should enable the definition of user-defined fields to the person & account records, and these user-defined fields are maintained during upgrades.

Yes

CRM and billing

Yes

CRM and billing CRM and billing

1.4

System should allow multiple names (aliases) to be specified for the same person. These names should all be available for searching.

Yes

CRM and billing

1.5

System should enable multiple forms of identification to be linked to the person. E.g. Drivers license. These identifiers should be available for searching.

Yes

CRM and billing

1.6

System should enable the definition of an account that is linked to a specific customer.

Yes

CRM and billing

1.7

Account information should contain all critical data related to that account, including contact persons, payment terms and methods.

Yes

CRM and billing

1.8

Account should remain linked to the specific customer indefinitely, eliminating the need to setup a new account when the person moves or purchases new services.

Yes

CRM and billing

1.9

System should has the capabilities to add a priority tag for certain accounts and route any related issues to specific FEWA staff for special handling.

Yes

CRM and billing

1.10

System should support the association of a single account with multiple services.

Yes

CRM and billing

1.11

System should support hierarchical linking of services.

Yes

CRM and billing

1.2 1.3

Yes

Annex B: Appendix 3B- Compliance Sheet

Page 35 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

1.12

The system should support services consolidation for services that span over multiple locations (e.g., add usage from several meters)

Yes

CRM and billing

1.13

System should provide robust, easy-to-use capabilities for starting and stopping customer service.

Yes

CRM and billing

2.0 Customer Lifecycle Management 2.1

System should enable searches by name, address, account number, phone number, person identifier, or any other configurable criteria.

Yes

CRM and billing

2.2

When a customer is identified, all appropriate fields on the system screen should be populated and contextual information be displayed where necessary (e.g., payment information should display on the payment screen).

Yes

CRM and billing

2.3

System should provide a contextual, user-centric portal that displays only the account information that is most applicable to the needs of the user.

Yes

CRM and billing

2.4

The system should have an optional dashboard which allows the user to maintain focus of the customer & account in context, contact notes, and financial information. It should also be able to show work items.

Yes

CRM and billing

2.5

The portal should be fully configurable, allowing FEWA to configure specific portals around alerts, billing graphs, financial balances, other account details, etc.

Yes

CRM and billing

2.6

FEWA should be able to embed configured specific business processes to be launched from any of the data displayed in the portals.

Yes

CRM and billing

2.7

System should maintain contact notes and other contact data as customer contact records.

Yes

CRM and billing

2.8

System should provide robust integration capabilities with Contact Center via CTI and to support IVR portal integration

Yes

CRM and billing

2.9

System should provide a “one-step” enrollment process for new customers in a quick & efficient fashion and be able to validate the data.

Yes

CRM and billing

2.10

System should provide for the creation of “packaged” services that may trigger a discount.

Yes

CRM and billing

Yes

CRM and billing

3.0 Customer Billing - Bill Rating 3.1 System should provide a robust rating engine that defines the pricing for products and services offered to the market. 3.2

The rating engine should be configurable without the need for customization.

Yes

CRM and billing

3.3

The rating engine should allow the definition of products that accept charges calculated within external applications, optionally adding other calculations (e.g., VAT, taxes .. etc.) to facilitate bill consolidation.

Yes

CRM and billing

3.4

System should support complex regulated & unregulated rate calculations without the need to modify the base system. System should permit rates to have multiple components that produce the actual charges on bills.

Yes

CRM and billing CRM and billing

System should support plug-ins or other non-customized functionality that support more complex rate calculations. System should support short and long billing rates, as well as rate changes during a period. (without any further development)

Yes

3.5 3.6 3.7

Yes

Yes

CRM and billing CRM and billing

Annex B: Appendix 3B- Compliance Sheet

Page 36 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

3.8

System can define multiple rules use to modify consumption values before applying the rate.

Yes

CRM and billing

3.9

System should also support consumption estimates where advanced metering is not used. Please explain the methodology that the system does support. The system should enable the following specification of prices:

Yes

CRM and billing

3.10.1

Directly on the rate

Yes

3.10.2

Via a bill factor that can be referenced on multiple rates

Yes

3.10.3

As the result of another rate component

Yes

3.10.4

As the result of a set of configurable rules

Yes

3.10.5

As entered into the system via an interface to an external system

Yes

3.11

The system should allow the definition of “bill factors” that contain frequently used amounts, and can be setup to define flat fees, per-unit fees, and percentage rates.

Yes

CRM and billing

3.12

The values of bill factors must be date effective to enable simple changes over time.

Yes

CRM and billing

3.13

Proration should be supported when the bill factor value changes during the billing period.

Yes

CRM and billing

3.14

The system should enable “what if” analysis to test the results of applying a particular rate in various scenarios.

Yes

CRM and billing

3.15

The system should handle sophisticated cross-product discounting scenarios.

Yes

CRM and billing

Yes

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

3.10

4.0 Customer Billing ( should support all the following ) 4.1 Internally rated charges (rated by the system’s rating engine).

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

4.2

Externally rated charges (passed through from another system).

Yes

4.3

Complex billing charges (e.g. half-hourly electricity charges).

Yes

4.4

Advance billing with service provisioning

Yes

4.5

Billing of metered services

Yes

4.6

Billing of non-metered services

Yes

4.7

Fees, such as flat rate (for example, a connection charge). System should also allow for the calculation of fees as a percentage of another charge (for instance, a late fee on an overdue balance).

Yes

4.8

System should provide the following standard billing capabilities:

Yes

CRM and billing

4.8.1

Automatic handling of meter exchanges

Yes

4.8.2

Proration of long or short bill periods

Yes

4.8.3

First and last bills

Yes

CRM and billing CRM and billing CRM and billing CRM and billing

4.8.4

Optional estimation of meter reads when actual data is not available

Yes

Annex B: Appendix 3B- Compliance Sheet

Page 37 of 89 Sr. No. 4.8.5

Requirement Description Automatic normalization of consumption information for rate calculation for bills when billing period is longer/shorter than userspecified range

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

Yes

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

4.8.6

Calculation and addition of taxes

Yes

4.8.7

Discounts

Yes

4.8.8

Margins

Yes

4.8.9

Customization of bill due dates

Yes

4.8.10

Definition of exact due dates

Yes

4.8.11

Overrides on due dates

Yes

4.9

System should generate a summary bill that can be associated with many additional services.

Yes

4.10

System should provide bill printing & rendering of online bill image functionality.

Yes

CRM and billing

4.11

System should support cancel/re-bill functionality, to permit recalculation of charges once source data is corrected. System should support online, real-time corrections of individual bills.

Yes

CRM and billing CRM and billing

4.13

System should support automatic re-billing when earlier meter-read estimates fall above or below pre-defined thresholds.

Yes

CRM and billing

4.14

System should support the specification of a date range during which bills may be produced, which enables FEWA to immediately begin bill production as meter reads come in. System can automatically create statements that consolidate information across multiple accounts and/or multiple billing periods.

Yes

CRM and billing

Yes

CRM and billing

4.16

System should provide billable charge templates and other tools to support one-off and 3rd party charges that fall outside normal business operations.

Yes

CRM and billing

4.17

System can bill customers a standard budget amount each period, based on previous usage trends, customer history, or other factors.

Yes

CRM and billing

4.18

System should support convergent billing, i.e., the consolidation of billing information created by other systems in a single bill to the customer.

Yes

CRM and billing

4.19

System can add permanent or one-time messages to bills, including meter reading remarks and ad hoc CSR comments.

Yes

CRM and billing

4.12

4.15

Yes

5.0 Customer Billing - Multi Party Billing 5.1 System should maintain contract agreement information for services providers, including the following service provider types:

CRM and billing

5.1.1

Energy (energy supply companies, energy service providers, retailers, and suppliers)

Yes

CRM and billing

5.1.2

Meter service (meter service providers and meter agents)

Yes

5.1.3

Meter reading (meter data management agencies & meter reading service providers)

Yes

CRM and billing CRM and billing

5.1.4

Billing (billing agents)

Yes

System should maintain the following relationship types:

Yes

5.2

CRM and billing CRM and

Annex B: Appendix 3B- Compliance Sheet

Page 38 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

billing CRM and billing CRM and billing CRM and billing CRM and billing

5.2.1

Billing relationships

Yes

5.2.2

Consumption relationships

Yes

5.2.3

Receivable (payment) relationships

Yes

System should support various types of billing calculations and presentation, including the following:

Yes

5.3.1

Rate-ready, when another service provider’s rates are loaded into the system

Yes

CRM and billing

5.3.2

Bill-ready, when another service provider’s calculated charges are loaded into the system

Yes

CRM and billing

5.3.3

Billing on behalf of a service provider

Yes

5.3.4

Consolidated service provider billing of charges. In this instance, charges are interfaced to another service provider, which the system views as the customer. Split billing, where multiple providers were each of them has their own billing charges

Yes

CRM and billing CRM and billing

Yes

CRM and billing

5.4

Proposed solution should comply with local market transaction standards in a deregulated market (e.g., system switches service providers as customers direct).

Yes

CRM and billing

5.5

Bidder should support updates to the market transaction functionality as new market standards and rules are published by the governing bodies.

Yes

CRM and billing

5.6

The system should support in flight messages when standards change.

Yes

CRM and billing

5.7

The system should be able to display market transactions which are directly linked to the relevant customer records and be able to see the automated processing and provide support for manual intervention when necessary.

Yes

CRM and billing

5.8

The system should be able to either integrate with a transaction hub or parse large incoming message files into individual transactions.

Yes

CRM and billing

5.9

List deregulated energy markets where the software has been implemented.

Yes

CRM and billing

Yes

CRM and billing

System should support batch processing of payments (i.e. through staging tables) to permit the creation of payments in the system from different source. For payment distribution, system should support either “balance forward” (in which payments are applied to the oldest debt first) or “open item” distribution (in which payments are applied to specific bills, charges, service agreements, or a combination of these).

Yes

CRM and billing

Yes

CRM and billing

6.4

System should support automatic payments, including Electronic Funds Transfers (EFT), direct debits, and credit card payments.

Yes

CRM and billing

6.5

System should support payment alternatives (pay plans, etc.) under automatic payment provisions. System should support prepayment in advance of service &be able to calculate amount of allowable consumption.

Yes

CRM and billing CRM and billing

5.3

5.3.5

6.0 Receivables Management - Payment Processing 6.1 System can manage payments from many sources, including mailed-in or walk-in payments, remittance processors, lock boxes, etc. 6.2 6.3

6.6

Yes

Annex B: Appendix 3B- Compliance Sheet

Page 39 of 89 Sr. No.

Requirement Description

6.7

System should support integration with prepaid metering devices.

6.8

System should support following cashiering functions:

Compliance SUP

Yes

MOD

3RD

CST

Remark FUT

NS

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

6.8.1

Adding and viewing payments online

Yes

6.8.2

Scanning bill stubs

Yes

6.8.3

Endorsing checks

Yes

6.8.4

Printing receipts

Yes

6.8.5

Managing and balancing individual cash drawers in a payment center

Yes

6.8.6

Single/multiple check(s) for multiple accounts

Yes

6.8.7

Popup messages alerting operators to excess cash in a drawer

Yes

6.8.8

Online, real-time transfer or payments between accounts (to facilitate error correction)

Yes

6.9

System can halt ongoing collection activity if payment is received for a delinquent account.

Yes

CRM and billing

6.10

System should support online cancellation of payments and levying of automatic fees for bounced checks.

Yes

CRM and billing

6.11

System should provide powerful search capabilities to help users locate a particular payment, including:

CRM and billing

6.11.1

Account (by name or Account ID)

Yes

6.11.2

Amount (with a ‘between’ range allowed)

Yes

6.11.3

Payer Account (by name or Account ID)

Yes

6.11.4

Payment tender amount (with ‘between’ range allowed)

Yes

6.11.5

Tender Source

Yes

6.11.6

Payment Date range

Yes

System should provide for the creation of non-billed budget plans to standardize a customer’s payments over time, particularly where bills are created infrequently.

Yes

6.12

7.0 Receivables Management - Credit & Collections 7.1 System can monitor how much customers owe to ensure they have not violated debt predefined levels. 7.2 The debt should be monitored by balance due or by individual items such as bills, adjustments, or charges. 7.3 When a violation is detected, the system should support the following:

Yes Yes

7.3.1

Encourage the customer to pay

Yes

7.3.2

Terminate service

Yes

7.3.3

Write off debt

Yes

7.4 7.4.1

System encourages customers to pay by providing the following functions: Generate letters

CRM and billing CRM and billing CRM and billing

Yes

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

Annex B: Appendix 3B- Compliance Sheet

Page 40 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

7.4.2

Credit-rating notifications

Yes

7.4.3

Cancel existing budget plans

Yes

7.4.4

An outbound call to the customer

Yes

7.4.5

Establish payment plans (installments, levelised bill payments, etc.)

Yes

System should initiate severance processing if the above steps do not result in a satisfactory payment arrangement. System should be able to create a write-off event to trigger a collection agency referral.

Yes

7.7

System should support automatic and manual cancellation of write-offs.

Yes

7.8

In the case of a write-off, system should generate accounting notification processes required to complete the necessary transactions.

Yes

7.9

Credit & collection activities can be processed automatically or manually, or mixture thereof, based on FEWA’s specific practices & regulatory requirements. Automatically-triggered collection-based activities can be overridden manually.

Yes

CRM and billing

Yes

CRM and billing

System can calculate & maintain an internal credit rating on each account based on account lifecycle events.

Yes

CRM and billing Credit rating will calculated externally by a credit services

7.5 7.6

7.10 7.11

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

Yes

CRM and billing CRM and billing

Assuming the infrastruct ure of such services available in UAE 7.12

Collection rules can be configured to take the credit rating into account when deciding on the appropriate collection path for the customer.

Yes

7.13

System should support cash and non-cash deposits, such as letters of credit and surety bonds.

7.14

System can automatically recommend a customer’s suggested deposit amount.

Yes

7.15

System can calculate interest on deposits, periodically (via a batch process) and when a refund is anticipated. If deposits are received over time, system calculates interest on each payment separately.

Yes

CRM and billing

7.16

System can refund deposits automatically when a customer meets userdefined criteria (which may be based on credit rating, length of service ..etc.).

Yes

CRM and billing

7.17

System should support "challenger" configurations of collection events that can be initiated randomly to test alternatives which improved debt collection.

Yes

CRM and billing

Yes

L/c & Surety Bonds Module will be developed CRM and billing

Annex B: Appendix 3B- Compliance Sheet

Page 41 of 89 Sr. No. 7.18 7.19

Requirement Description

SUP

Control reports and reconciliation reports. Typical reports like cash collection summary, receipt cancellation with reason code, reconciliation between cash collected and deposited to bank at each area office etc Functionality to generate bank pay-in-slips from the system to avoid manual steps

8.0 Field Operations - Geographic Data Management 8.1 System can record basic geographic information about each location or address.

8.2

Compliance

Multiple geographic identifiers may be linked to the premise/service location (e.g., map coordinates, GPS).

MOD

3RD

CST

Remark FUT

NS

Yes ECC 6.0 Yes ECC 6.0 Yes

Yes

CRM and billing The exact location and coordinate s will extracted via the integration with GIS CRM and billing The exact location and coordinate s will extracted via the integration with GIS

8.3

8.4

System should support searching by geographic identifiers.

System should support an unlimited number of distinct Service Points for each premise. (A Service Point is a location where a given service is actually provided.)

Yes

Yes

GPS will be utilized to identify the location for routing and directions CRM and billing The exact location and coordinate s will extracted via the integration with GIS CRM and billing The exact location and coordinate s will extracted via the

Annex B: Appendix 3B- Compliance Sheet

Page 42 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

integration with GIS 8.5

Landlord agreements may be attached to a premise.

Yes

8.6

Landlord agreements should control the automatic service reversion rules (to the landlord) when a tenant moves out of a premise. System should enable the linkage of multiple Service Points to a single service agreement.

Yes

8.8

System should also enable the linkage of a single Service Point to multiple services.

Yes

CRM and billing

8.9

System should provide for hierarchical structuring of parent & child premises for buildings, Mall, apartment complexes, etc.

Yes

CRM and billing

Yes

CRM and billing

8.7

9.0 Field Operations - Premise Management 9.1 System should provide powerful query & other tools that can quickly perform mass updates on premises or check the account status of, (i.e. all apartments in a building) 9.2 Mass updates actions should, at a minimum, include:

Yes

Yes

9.2.1

Assign or remove parent premise

Yes

9.2.2

Assign or remove landlord

Yes

9.2.3

Start or stop service

Yes

10.0 Field Operations - Meter and Device Management 10.1 System can record the relationship between a device and the Service Point it serves.

CRM and billing Using business document link CRM and billing CRM and billing

Yes

10.2

System can track meters & equipment installations through their life cycle. When meters are used at different locations, records are kept of initial and terminal readings at each site.

Yes

10.3

Users should be able to access the history of a meter or service point, including all meters installed over time.

Yes

10.4

System should allow for specification of a stock location (which includes on hand in a truck) whenever a meter or item is removed from a service point.

Yes

10.5

Tracking by stock location can be activated for individual meter types and item types.

Yes

CRM and billing CRM and billing CRM and billing CRM and billing Using Device manageme nt CRM and billing Using Device manageme nt CRM and billing Using Device manageme nt CRM and billing Using Device manageme nt and material manageme nt CRM and billing Using

Annex B: Appendix 3B- Compliance Sheet

Page 43 of 89 Sr. No.

Requirement Description

Compliance SUP

10.6

System can maintain records on non-metered equipment such as transformers, backflow devices, lamps, and other items installed in the field.

Yes

10.7

System should also be able to handle sets of un-badge item types that use a single Service Point but are not individually identified (i.e. all lamps in a parking lot).

Yes

10.8

To reduce data entry, system should enable data replication from template entries for meters and items, and supports the automatic incrementing of badge numbers and serial numbers.

Yes

10.9

System should include features for selecting devices to be tested and recording test results.

Yes

11.0 Field Operations - Meter Reading 11.1 System should support meter read cycles and routes, to which Service Points can be assigned. (A route is a group of properties whose meters can be read by a meter reader on a given full or partial day.)

MOD

3RD

CST

Remark FUT

NS

Device manageme nt CRM and billing Using Device manageme nt CRM and billing Using Device manageme nt CRM and billing Using Device manageme nt CRM and billing Using Device manageme nt including QA

Yes

CRM and billing

System provides staging tables to load in the meter read data, which is then processed and used to create meter reads in the system. System should support the loading of reads from traditional manual reading processes, or from automatic meter reading systems.

Yes

CRM and billing CRM and billing

11.4

System should permit uploading remark codes with meter read data.

Yes

11.5

The remark code should be able to trigger one or more user-defined events, e.g., whenever a meter read with a “broken seal” remark is recorded in the database, the system might trigger the creation of a field activity to investigate the meter. System should support the tracking, reviewing, and correction of meter read errors.

Yes

Yes

CRM and billing

System should enable the ability to add non-cyclical meter reads, such as when a customer starts or stops service. System should support meter read estimation when an actual meter read is not available.

Yes

CRM and billing CRM and billing

11.9

System should support both trend-based and historical estimation.

Yes

11.10

System should support the definition of and comparison against high/low limits that are based on estimated usage for the account.

Yes

11.11

System should store a complete online history of all meter reads, including those uploaded from handheld devices, no reads, & manually entered reads.

Yes

11.2 11.3

11.6 11.7 11.8

12.0 Field Operations - Field Work

Yes

Yes

CRM and billing CRM and billing

CRM and billing CRM and billing CRM and billing

Annex B: Appendix 3B- Compliance Sheet

Page 44 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

12.1

System should provide handling for all customer field requests, including meter installs & removals, turning service on or off, and service investigations.

Yes

CRM and billing

12.2

When a customer calls to start service at a premise, the system should review the current status of service, & may create one or more field activities as applicable to start service.

Yes

CRM and billing

12.3

System should allow a single field activity to be linked to several pending service agreements.

Yes

CRM and billing

12.4

System should provide a dispatch query that presents pending Field Activities that need to be dispatched, which can be grouped and given to work teams.

Yes

CRM and billing

12.5

Yes

12.5.1

System should feature an automated field order dispatch process that selects pending field activities that: are not yet connected to a Field Order

12.5.2

have been assigned a dispatch group

Yes

12.5.3

are linked to an Field Activity type that permits automated dispatching

Yes

12.5.4

have a schedule date earlier than today’s date plus the specified Dispatch Ahead Days

Yes

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

Field work completion activities should trigger any of the following system updates:

Yes

CRM and billing

12.6.1

Meter Installation, new meter & the start reading are recorded

Yes

12.6.2

Meter Removal - the removal and the related end reading are recorded

Yes

12.6.3

Record Meter Reads

Yes

12.6.4

Service Point Connection Status update

Yes

12.6.5

Device At Service Point Status - indicates if the meter is on or off (or, for lamps, if the eye is in or out) System should support appointment functionality. (e.g. dispatch groups would receive effective-dated work schedules, which define their workday with time slots & the number of resources available for each time slot) The system should be able to override a dispatch group’s normal work schedule for events like holidays.

Yes

CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing CRM and billing

Integration with a Workforce Management system should enable additional appointment functionality in the core system (e.g., whether appointments are required at dispatch time. (Optional not allowed for field activities of that type).

Yes

CRM and billing

Yes

CRM and billing and HR CRM and billing and HR CRM and billing and HR CRM and billing and HR

12.6

12.7

12.8

13.0 Field Operations - Work Force Management 13.1 System should provide standard integration with a HR management system. 13.2 13.3 13.4

Yes

Yes

Should permit the user to view the available time slots, choose from them, and, in a real-time transaction, both reserve the time slot and update the field activity. All activities should take place without the need to jump between the two systems.

Yes

Should send status values to the Customer Relationship Management system so that users can inform customers about field visit status, e.g., “the worker is on the way.”

Yes

Yes

Annex B: Appendix 3B- Compliance Sheet

Page 45 of 89 Sr. No. 13.5

Requirement Description System should support a field activity history log to capture the changes to the field activity that are triggered by messages coming from the field operations stamped with the date/time and action that was performed.

14.0 Energy Data Management 14.1 System should calculate and manage all types of time-series data, including raw consumption, aggregated load, standard load profiles, prices, and other factors. 14.2 System should include many features to process this data, including validation, editing & estimation (VEE), derivation, aggregation, time-ofuse mapping, and complex billing. 15.0 Energy Data Management - Meter Data Management 15.1

Compliance SUP

Yes

Yes

15.1.2

Consumption values

Yes

15.1.3

Standard load profiles

Yes

15.1.4

Time-of-use maps

Yes

15.1.5

Prices

Yes

15.1.6

Contractual terms

Yes

System should allow loading of new or corrected data without corrupting existing data, including a history of what has been loaded in support of retroactive adjustments and calculations. System should permit calculations and manipulations of this interval data in order to perform many different functions.

Yes

15.4

System should permit interval data processes to be performed as data becomes available.

Yes

15.5

System should support multiple time zones and daylight-saving shifts.

Yes

16.3 16.4

System should support aggregation of interval data (the accumulation of data for multiple sources into a single stream, such as when a single Service Agreement exists for multiple service points or meters). System should support time-of-use mapping by providing tools that help users upload data, define standard reusable templates, classify and price usage periods, etc. System should store and process both interval-based and time-of-usebased prices.

NS

CRM and billing and EDM CRM and billing and EDM

Raw and aggregated data

16.2

FUT

Yes

15.1.1

16.0 Energy Data Management - Complex Billing 16.1 System should include a module for complex billing that takes over when raw interval data has been processed.

CST

CRM and billing and HR

Yes

15.3

3RD

Yes

System should support many forms of interval data, in any interval size, including:

15.2

MOD

Remark

Yes

Yes Yes Yes Yes

CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM

Annex B: Appendix 3B- Compliance Sheet

Page 46 of 89 Sr. No. 16.5

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

System should include formulae in the base system that supports, at a minimum, the following:

Yes

16.5.1

Profile data conversion for aggregation of peak demand (sum of curves or the maximum peak in each period).

Yes

16.5.2

Profile data conversions for unit of measure and time intervals—for instance, from KWh/15-minute interval values to KWh/30-minute interval values. A rate component calculation capability to pick out a “peak curve value.”

Yes

Complex billing systems should, at a minimum, be able to support the following:

Yes

16.6.1

Straight time-of-use pricing, where time-of-use data is derived from timeseries usage.

Yes

16.6.2

Pure real-time, interval pricing, where spot market prices are applied interval by interval to the customer’s time-series usage.

Yes

16.6.3

Combination products, where fixed prices are offered for pre-defined loads (or for usage within a band of loads), and the excess or under-used energy is sold or bought on a spot market contract.

Yes

16.6.4

All of these types of products should support integration with special contract options, such as price- or demand-response load-management triggers.

Yes

CRM and billing and EDM

16.7

System should calculate and manage all types of time-series data, including raw consumption, aggregated load, standard load profiles, prices, and other factors.

Yes

CRM and billing and EDM

16.8

System should support sophisticated contract options for the management of curtailment and interruption periods.

Yes

CRM and billing and EDM

16.5.3 16.6

1.4.2

CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM CRM and billing and EDM

Yes

Finance and Accounting

Sr. No.

Requirement Description

1.0

Organization Structure

1.1

Allows multi-company environment in a single instance

1.2 2.0

Allows definition of legal entity, its divisions, branches, plants, distribution centers etc. Allows definition of profit centers within organization General (across all modules in financials)

2.1

Definition of country , regions, sub-regions to meet legal requirements

2.2

Flexibility to define fiscal year including start month and end month.

2.3

Ability to define 12 periods “months” within a fiscal year.

2.4

Ability to revise no. of periods in a fiscal year during year

2.5

Provision for separate logical periods for the purpose of annual closing activities

Reference in Proposal SUP

Yes Yes

MOD

3RD

CST

FUT

Remark NS

SAP ERP Financials SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials

Yes Yes

Annex B: Appendix 3B- Compliance Sheet

Page 47 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials

2.6

Multiple fiscal year closings are allowed. Multiple sets of same books of accounts is permitted.

2.7

Allows closing of fiscal periods to restrict transactions posting

2.8

Allows to keep multiple periods open across financial years or within financial year

2.9

Ability to re-open closed period, subject to valid authorization Ability to define exchange rates with multiple currencies vis-à-vis base currency

Yes

2.10

Ability to process transactions entered in foreign currency based on exchange rates definition in a online mode

Yes

2.11

SAP ERP Financials

Tracking of all foreign currency transactions in both transaction currency as well as base currency

Yes

2.12

SAP ERP Financials

Yes

SAP ERP Financials

Yes Yes

SAP ERP Financials SAP ERP Financials

2.13

Ability to calculate exchange fluctuation gain or loss automatically on closing of open transaction as well as simultaneous posting of such gain / loss based on pre-determined criteria without any further user intervention Ability to calculate value of open items in foreign currency as of end of a fiscal year and end of period within fiscal year.

Yes

2.14

SAP ERP Financials

Yes

SAP ERP Financials

2.15

Flexibility to choose rules for posting of such revalued items at the end of fiscal year and end of period for each type of account such as receivable, payable, assets Flexibility options for posting of these differences meet criteria defined by IFRS

Yes

2.16

SAP ERP Financials

Yes

SAP ERP Financials

2.17

Ability to draw complete set of books of accounts such as profit & loss account, balance sheet for the legal entity, each of the business unit branch, plant etc.

Yes 2.18

Availability of various document types for different financial transactions

SAP ERP Financials

Yes 2.19

Availability of system generated numbering for the documents

2.20

Availability of an option of manual numbering for certain documents

SAP ERP Financials SAP ERP Financials

2.21

Numbering sequence for all documents is reset per fiscal year.

2.22

Option of setting numbering sequence based on location, branch etc for the same document type

2.23

Supports legal requirements for UAE

2.28

Supports capturing of various tax codes

2.31

Flexibility to control posting to specific ledger accounts with specific documents

Yes Yes Yes Yes Yes

2.32 3.0 3.1 3.2 3.3 3.4

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Flexibility to define date formats, number formats per user

Audit trail For re-opening of fiscal year periods Yes Tracking of user, date and time for each transaction Yes Tracking of changes made to any document Yes Tracking of creation and changes to any master data in the system

Annex B: Appendix 3B- Compliance Sheet

Page 48 of 89 Sr. No. 3.5 3.6 4.0 4.1 4.2

Requirement Description Tracking of creation and changes to any set up data in the system, eg. codes, etc.

Reference in Proposal SUP

3RD

CST

FUT

Remark NS

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials

Tracking of changes to authorization profile / approval profile General Ledger Ability to define chart of account for the company No restriction of the arrangement or the number of accounts

MOD

Yes

Allows grouping of general ledger account for the purpose of account management

Yes

Allows creating general ledger accounts in online mode

Yes

Allows creating general ledger accounts in batch mode using external interface

Yes

If required, allows creating master records during transaction entry

Yes

SAP ERP Financials

Can block / delete general ledger accounts if postings are to be blocked

Yes

SAP ERP Financials

4.8

Possible to map general ledger account codes to specific business transactions in other modules

Yes

SAP ERP Financials

4.9

Ability to post transactions from other modules in online mode based on such pre-defined criteria

Yes

SAP ERP Financials

Allows creation & posting of journal entries online or in batches.

Yes

SAP ERP Financials

Allows definition of recurring transactions and periodicity of recurrence

Yes

SAP ERP Financials

Creates these automatic transactions based on predefined criteria

Yes

SAP ERP Financials

Allows to create reversible journal vouchers with date definition for reversal

Yes

SAP ERP Financials

Automatic reversal of vouchers based on pre-defined criteria

Yes

Allows definition of certain GL accounts in a way that individual transactions can be tracked based on its 'open' status. e.g. Security deposits, clearing accounts etc.

Yes

SAP ERP Financials SAP ERP Financials

Allows manual clearing of such accounts by matching transactions

Yes

SAP ERP Financials

Option to capture due dates for such security deposits and query / report to highlight deposits / advances which are due for repayment

Yes

4.17

SAP ERP Financials

4.18

Flexibility to define rules for automatic clearing of such accounts and clearing of open items based on such criteria

Yes

SAP ERP Financials

4.19

Allows cash accounting with multiple cash points for a single or multiple cash GL accounts

Yes

SAP ERP Financials

Ability to define banks, bank accounts within system

Yes

Allows upload of bank statements into the system

Yes

Allows manual entry of bank statements into the system

Yes

4.23

Allows to define criteria for bank reconciliation & carries out bank reconciliation based on pre-determined criteria

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

4.24

Allows entry of incoming Cheques for current as well as future period and segregation based on dates possible

Yes

SAP ERP Financials

4.25

Allows to view & print Cheque deposit statement for a day

Yes

SAP ERP

4.3 4.4 4.5 4.6 4.7

4.10 4.11 4.12 4.13 4.14 4.15 4.16

4.20 4.21 4.22

SAP ERP Financials SAP ERP Financials

Annex B: Appendix 3B- Compliance Sheet

Page 49 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Financials SAP ERP Financials

Allows to define 'Cash Management Systems' which are offered by various banks in the country

Yes

Captures value date for Cheque deposits and payments

Yes

Enables calculation of interest based on value dates captured in the system

Yes

Flexibility to write certain validation rules to support business rules which are not supported directly by standard product features

Yes

4.29

SAP ERP Financials

4.30

Built in maker - checker concept for approval of documents by supervisory authority

Yes

SAP ERP Financials

4.31

Supports process of transfer of all revenue statement account balances to retained earnings on closure of fiscal year

Yes

SAP ERP Financials

4.32

Ability to transfer balances of profit & loss account to retained earnings account multiple times during a fiscal year closing process

Yes

SAP ERP Financials

Yes

SAP ERP Financials

4.26 4.27 4.28

SAP ERP Financials SAP ERP Financials

5.1

GL - Query / Reporting requirements Allows listing of all transaction for a particular document type in books of accounts

5.2

Ability to query all accounts and transactions on-line for current & previous periods including previous fiscal years

Yes

SAP ERP Financials

Flexibility in definition of transaction fields that are displayed in such query / report based on requirements without any programming efforts

Yes

5.3

SAP ERP Financials

5.4

Ability to drill down from balance to individual transactions for any account

Yes

SAP ERP Financials

5.5

Allows classification of expenses on the basis of pre-defined parameters. e.g. Telephone number, Vehicle number etc.

Yes

SAP ERP Financials

5.6

Generates error report in case of rejections or any errors at the time of data transfer using batch mode.

Yes

SAP ERP Financials

5.7

Allows to define multiple formats of annual accounts (i.e. Balance sheet and profit & loss account) at the same time

Yes

SAP ERP Financials

Ability to take these annual accounts at legal entity level, division etc.

Yes

SAP ERP Financials

Allows to take comparative balance sheet, profit & loss account, trial balance where a corresponding period which can be selected by user

Yes

SAP ERP Financials

Allows to define schedules to support annual accounts

Yes

Report on all foreign currency transactions entered during a period

Yes

SAP ERP Financials SAP ERP Financials

Allows to extract trial balance for entire company, division, branch, location etc.

Yes

SAP ERP Financials

Allows to extract actual cash flow of the company

Yes

Ability to generate financial reports on both cash and accrual basis based on specific reporting requirements Costing

Yes

SAP ERP Financials SAP ERP Financials

Adherence to costing record rules for the purpose of cost audit requirements

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP

5.0

5.8 5.9 5.10 5.11 5.12 5.13 5.14 6.0 6.1 6.2 6.3 6.4

Flexibility to perform costing for a legal entity or across legal entities Flexibility to define fiscal year including start month and end month. Flexibility to define periods within a fiscal year

Annex B: Appendix 3B- Compliance Sheet

Page 50 of 89 Sr. No.

6.5 6.6 6.7 6.8 6.8.1 6.8.2 6.8.3 6.9 6.10 6.11 6.12 6.13 6.14 6.15

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Financials SAP ERP Financials SAP ERP Financials

Yes Allows closing of fiscal periods to restrict transactions posting Ability to define cost centers based on internal reporting requirements

Yes

Allows grouping of cost centre in a tree structure at least upto 5 levels

Yes

SAP ERP Financials

Allows transfer of cost from one cost centre to another cost centre

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials

Yes On ad-hoc basis - manual transactions online Yes On predefined criteria including a specific amount, percentage or formula Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Flexibility to define departments, divisions, branches of the company as profit centers Allows grouping of profit centers in a tree structure at least up to 5 levels

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Allows transactions to flow from cost centers, general ledger accounts to profit centers

Yes

SAP ERP Financials

Yes

SAP ERP Financials

In case of formula, flexibility to change formula with an effective date Flexibility to transfer costs pertaining to specific expense head only Flexibility to retain origin information of cost even after transfer of costs Availability of sender and receiver cost centre information at all the time

Allows assets and liabilities to be allocated to individual profit centers

6.16

Ability to extract profit & loss account and balance sheet for each profit centre

Yes

SAP ERP Financials

6.17

Allows transfer price mechanism across profit centers for stock transfer across profit centers

Yes

SAP ERP Financials

6.18

Ability to derive unrealized profit in stocks at the end of period of fiscal year

Yes

SAP ERP Financials

6.19

Ability to arrive at standard product cost based on materials, labor and overheads consumption.

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials

6.20 6.21 6.22 6.23 6.24 6.25 7.0

Ability to calculate standard cost of products based on the above

Ability to calculate actual cost of products based on allocation of expenses during a period

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials

Yes

SAP IS-U EDM

Yes Variance analysis between standard / budgeted cost and actual cost Ability to produce cost reports at production sites and operational unit levels Ability to report transmission / distribution losses Budgeting Flexibility to define and change budgets for accounts and cost centre level

Yes

Yes

7.1 7.2

Yes Ability to calculate actual cost of product based on production data

Allows to create various versions during budgeting process with one version identified as firm budget

Yes

SAP ERP Financials /BPC SAP ERP Financials /BPC

Annex B: Appendix 3B- Compliance Sheet

Page 51 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

Flexibility in allocation of annual budget over accounting periods in a fiscal year

Yes

Either in equal installments

Yes

Any other formula / criteria

Yes

Flexibility of creating budgets

Yes

Without any reference to previous year's budgets / actual

Yes

As a percentage variation from previous year's / current year's budgets or actual data

Yes

Allows tracking of budget on a real time basis vis-à-vis actual transactions and commitments and highlight

Yes

On actual figures exceeding budget figures

Yes

On actual figures reaching a predetermined percentage of budget figures

Yes

Flexibility to define this tracking for each individual period or for entire fiscal year or combination of both

Yes

7.6

Ability to consolidate budgets of various departments, regions, branches into one corporate budget for the company

Yes

7.7

Provides budget vis-à-vis actual comparison on a on-line basis as well as periodic intervals

Yes

7.8

Flexibility to change budget figures during a fiscal year / period

Yes

7.3

7.3.1 7.3.2 7.4

7.4.1 7.4.2 7.5

7.5.1 7.5.2

7.9 8.0

Account Payable - General

8.1

Allows creation of vendors in the system and vendor codes can be Numeric and/or Alphanumeric

8.2

Vendor numbers can be generated by the system

8.3

If required vendor codes can be manually assigned

8.4

Captures critical vendor information such as Name and address, key person at vendor company

Yes

Captures state where vendor is located

Yes

Captures email ID of vendor

Yes

Bank account details

Yes

Payment terms, discount terms, payment methods

Yes

Legal status of the vendor such as corporate, non-corporate etc.

Yes

Ability to hint that vendor code may be existing in the system

Yes

3RD

CST

FUT

Remark NS

SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC SAP ERP Financials /BPC

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP

Yes Yes 8.4.1 8.4.2 8.4.3 8.4.4 8.4.5 8.4.6 8.5

MOD

Annex B: Appendix 3B- Compliance Sheet

Page 52 of 89 Sr. No.

Requirement Description

8.6

Allows creation of vendor codes in an online mode as well as in a batch mode

8.7

If required vendor codes can be created during transaction entry

8.8

Allows to define payment terms in following scenarios:

Reference in Proposal SUP

Yes Yes

MOD

3RD

CST

FUT

Remark NS

Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Standard payment term of payment due after specific no. of days

Yes

Payment term with discount slabs for payment before specific no. of days. Should allow up to 5 slabs in such cases

Yes

8.8.2

Payment term where discount is offered as interest component for early payments

Yes

8.8.3

SAP ERP Financials

Payment term which allows retention money

Yes Yes

8.9

Allows blocking of specific vendors so that transactions with such vendors cannot be entered

SAP ERP Financials SAP ERP Financials

Yes

8.10

Allows linking of many vendors to capture group exposure / transaction volume

SAP ERP Financials

Yes

8.11

Allows linking of vendors with customers in case a company is both vendor as well as customer

SAP ERP Financials

Yes

8.12

Allows creation of vendors' financial data independent of purchase and materials related data

SAP ERP Financials

Yes

8.13

A unique vendor code can be used for all the divisions, branches, multiple legal entities based on the requirement

SAP ERP Financials

Allows to define various TDS rates, works contract tax rates in the system & attach relevant rates to vendors based on applicability

Yes

8.14

Allows clearing of vendor transactions by matching two or more open debit and credit items Allow to segregate and track vendor transactions into: Normal invoices and payments

Yes

SAP ERP Financials SAP ERP Financials

Advance payments to vendors

Yes

Guarantees

Yes

Security deposits with vendors

Yes

Bank guarantee, letter of credit to vendors

Yes

AP - Accounting and Vendor credit processes Allows invoice processing With respect to a Goods Receipt Note (GRN) in the system

Yes

With respect to capital job note in case of capital asset receipt

Yes

With respect to service entry note in case of a service vendor

Yes

Expense voucher where vendor is credited without PO/GRN in the system

Yes

8.8.1

8.8.4

8.15 8.16

Yes

8.16.1 8.16.2 8.16.3 8.16.4 8.16.5 9.0 9.1

9.1.1

9.1.2

9.1.3

9.1.4

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent

Annex B: Appendix 3B- Compliance Sheet

Page 53 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

Yes 9.2

Supports typical 3 way match (PO, GRN, Vendor invoice) bill passing process Yes

9.3

Considers quantitative details from GRN and price details from PO during the 3way match Yes

9.4

Bills are processed based on PO, GRN even if invoice does not match with value arrived at using these two documents Yes

9.5

Vendor bills should be booked at gross and any rejection, disallowance should be captured during bill processing as a separate entry. Rejection, deductions should be printable during printing of payment advice Yes

9.6

Ability to prompt / automatically deduct all deductible charges at the time of vendor bill processing Yes

9.7

Ability to automatically account for all these deductions based on predetermined criteria Yes

9.8

Defaults master data information of vendor during invoice processing Yes

9.9

Allows to define parameters to determine whether default master data information can be changed during processing and changes are allowed only based on this. The same can be done only based on authorization. Yes

9.10

Allows entry of transaction in vendor account In online and/or batch mode Yes

9.11

Allows to evaluate amount of pending GRN for invoice processing to arrive at provision figures Yes

9.12

Triggers commitment and updates budget on issue of purchase orders for goods / services Yes

9.13

Ability to track duplicate invoice based on vendor code and invoice number Yes

9.14

In case of labor bills ability to check individual time sheets Yes

9.15

Ability to post debit notes and credit notes as well as print these for sending across to vendors Yes

9.16

Ability to calculate overdue interest for vendors based on individual transaction due dates in following scenario:

MOD

3RD

CST

FUT

Remark NS

SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent

Annex B: Appendix 3B- Compliance Sheet

Page 54 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

Interest is accrued at each period end for all outstanding line items beyond due date

Yes

Interest is accrued only at the time of payment of principal. Till then although interest is calculated , however not accounted for

Yes

9.16.1

9.16.2 10.0 10.1

3RD

CST

FUT

Remark NS

SAP ERP Financials /Procurem ent SAP ERP Financials /Procurem ent

AP - Payment processing Ability to process vendor payment in Manual payment mode

Yes

Automatic payment processing based on predefined parameters

Yes

10.1.1 10.1.2 Yes 10.2

MOD

Allows payment for following scenarios: Advance payment – ad-hoc

Yes

Advance payment only against purchase orders

Yes

Payment against one or multiple invoices - matching amount

Yes

Payment against one or multiple invoices - partial amount

Yes

Payment against one or multiple invoices – ad-hoc amount

Yes

10.2.1 10.2.2 10.2.3 10.2.4 10.2.5 Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

10.3

Ability to capture and report capital and revenue advances separately Ability to block certain vendor invoices so that they cannot be paid unless cleared by appropriate authority

Yes

10.4

SAP ERP Financials

Ability to block certain vendors for payment so that no payments can be made to such vendors unless appropriately approved

Yes

10.5

SAP ERP Financials

Ability to provide funds requirement based on due date for a user determined period.

Yes

10.6

SAP ERP Financials

Yes

SAP ERP Financials

10.7

The funds requirement information also identifies currency, branches, divisions for all the individual transactions which are captured based on due dates Allows to processes one or more vendor invoices, debit notes, credit notes and allows to make net payment

Yes

10.8

SAP ERP Financials

10.9

For the purpose of automatic payment processing system enables:

SAP ERP Financials

Allows to run payment program for future date

Yes

Allows to process multiple payment programs runs for different dates, same date - different criteria

Yes

Identification invoices due by a particular date

Yes

Allows to select / deselect certain invoices for payment processing

Yes

For the purpose of payment processing, allows to pay on one single day

Yes

SAP ERP Financials

Flexibility to process payment of all invoices at one go, however, strictly on due date basis.

Yes

SAP ERP Financials

Identifies banks based on predetermined criteria and funds availability

Yes

SAP ERP Financials

10.9.1 10.9.2 10.9.3 10.9.4 10.9.5 10.9.6 10.9.7

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Annex B: Appendix 3B- Compliance Sheet

Page 55 of 89 Sr. No. 10.9.8

Requirement Description Based on the process, posts accounting entries in bank accounts as well as vendor accounts

Clears vendor items wherever clearing is possible

Reference in Proposal SUP

3RD

CST

FUT

Remark NS

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials

10.9.9 Yes 10.10

MOD

During payment (automatic or manual) system automatically calculates discount if any and proposes net amount for payment processing Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials

10.11

Ability to generate accounting entry after considering discount figures & posting of entry based on pre-determined account mapping

10.12

Allows maintenance of Cheque stationary and tracking of Cheque based on available stationary and usage

10.13

Allows printing of Cheques for various banks Option of sending payment details to banks in a soft copy format so that payment processing can be carried out by bank

Yes

10.14

Option of Cheque printing by banks on transfer of payment instruction and updating of Cheque nos. back in the system

Yes

10.15

SAP ERP Financials

Allows printing of payment advice along with Cheque which may be sent across to vendors along with their payment

Yes

10.16

SAP ERP Financials

Ensures updating of Cheque register on printing of Cheque as well as updates the payment voucher with details of Cheque no.

Yes

10.17

SAP ERP Financials

Flexibility to update Cheque register in case Cheque are issued manually, Cheque is destroyed, damaged etc. AP - Reports

Yes

10.18 11.0

SAP ERP Financials

Yes

SAP ERP Financials

11.1

Statement of account for the purpose of sending it across to vendors for balance and transaction confirmation, with an option to define format of confirmation letter

Yes 11.2

Due date wise analysis of vendor accounts

11.3

Ageing analysis of vendor line items

11.4

Vendor account trial balance

11.5

Vendor account line item details

11.6

Vendor account details segregated into:

11.6.1

Invoices and payments

11.6.2

Advances paid to vendors

11.6.3

LCs and bank guarantees

11.7

Vendor account balances & transactions per vendor control account

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

11.8

Allows regrouping of vendor balances based on debit / credit balances

11.9

Yes Yes Yes Yes Yes Yes Yes Yes Yes

SAP ERP Financials

Ability to view / print all the above vendor account and line item reports per branch, division, location etc.

Yes

SAP ERP Financials

Allows to capture separate ageing analysis for different categories of vendors

Yes

11.10

SAP ERP Financials

Availability of details of payments made before due data and corresponding cash discount earned

Yes

11.11

SAP ERP Financials

Allows to extract details of purchase orders, GRNs, invoices, accounting documents of individual vendors

Yes

11.12

SAP ERP Financials

Annex B: Appendix 3B- Compliance Sheet

Page 56 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Ability to provide details of payments segregated into on time payment, early payment and delayed payment

Yes

SAP ERP Financials

Ability to report on total volume of business generated, discounts earned from vendors Accounts Receivable - General

Yes

11.16 12.0

SAP ERP Financials

Allows creation of customers in the system and customer codes can be Numeric and/or Alphanumeric

Yes

12.1

SAP ERP Financials

Yes 12.2

Customer numbers can be generated by the system

12.3

If required customer codes can be manually assigned

12.4

Captures critical customer information such as

12.4.1

Name and address, key person

12.4.2

Bank account details

12.4.3

Payment terms, discount terms, payment methods

12.4.4

Legal status of vendor such as corporate, non-corporate etc.

12.5

Allows defining multiple groups in which individual customers may be clubbed such that different groups may exist for different class of customers. eg. Industrial, domestic etc.

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

12.6

Ability to hint that customer code may be existing in the system

12.7

Allows creation of customer codes in an online mode as well as in a batch mode

12.8

If required allows creation of master data during transaction entry

12.9

Allows to define specific credit limits for individual customers

12.10

Allows specific credit limit for each customer within a customer category

12.11

Allows tracking of any change to the credit limit set Yes

12.12

Ability to provide specific overriding authorization for allowing transactions over and above credit limit

Yes

12.13

Ability to provide separate credit limits depending upon product to the same customer

SAP ERP Financials

Yes 12.14

Ability to define dynamic credit limits based on:

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

11.13

Allows to segregate imported and local purchases and expenditure in foreign currency

11.14

Allows to extract details of capital commitment made by the company

11.15

Yes Yes Yes Yes Yes Yes Yes

Yes Yes Yes Yes Yes Yes

Yes 12.14.1

Sale of past 'x' months where value of 'x' is freely definable Formula to alter credit limits of all customers as a % of existing credit limit e.g. + / - 10% for all customers in a category

Yes

12.14.2

Yes

12.14.3

Percentage of a total of security deposit and advances as reduced by outstanding bills beyond due date

12.15

Allows to define payment terms in following scenarios:

Yes Yes 12.15.1

A fixed date as payment date such as every Monday, every 7 th of month Yes

12.15.2

Standard payment term of payment due after specific no. of days

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

SAP ERP Financials SAP ERP Financials SAP ERP Financials

Annex B: Appendix 3B- Compliance Sheet

Page 57 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Payment term with discount slabs for payment before specific no. of days. Should allow upto 5 slabs in such cases

Yes

12.15.3

SAP ERP Financials

Payment term where discount is offered as interest component for early payments

Yes

12.15.4

SAP ERP Financials

Yes 12.15.5

Payment term which allows retention money Yes

12.16

Allows blocking of specific vendors so that transactions with such vendors cannot be entered

SAP ERP Financials SAP ERP Financials

Yes

12.17

Allows linking of many customers to capture group exposure / transaction volume

SAP ERP Financials

Yes

12.18

Allows linking of vendors with customers in case a company is both vendor as well as customer

SAP ERP Financials

Yes

12.19

A unique customer code can be used for all the divisions, branches, multiple legal entities based on the requirement

SAP ERP Financials

Yes

12.20

Allows clearing of customer transactions by matching two or more open debit and credit items

SAP ERP Financials

12.20.1

Allow to segregate and track transactions into:

12.20.2

Normal invoices and payments

12.20.3

Advance payments

12.20.4

Guarantees

12.20.5

Security deposits from customers

12.20.6

Bank guarantee, letter of credit to customers

Yes Yes Yes Yes Yes Yes

12.21

Ability to calculate unbilled revenue based on revenue recognition policy

13.0

Accounts Receivable - Invoicing and collections

13.1

Allows to create manual / system invoices for customer charges

13.2

Allows to create invoices in batch mode so that invoices can be uploaded into system from external file / database in case billing is generated in a different solution

13.3

Automatic invoice no. generation by the system

13.4

Generation of invoice no. can be any of the following:

13.4.1

Unique across company

13.4.2

Unique per branch, division, location

13.5

Allows posting of debit notes / credit notes in the system both manually, or in a batch mode thru an external file / database

13.6

Allows entry of payments in any of the following ways:

13.6.1

Manual cash / Cheque receipt

13.6.2

Batch upload from an external file / database

13.6.3

Electronic upload of the Data through system checks like bill No.

Yes Yes

Yes

Yes Yes Yes

Yes Yes Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials A report will be developed for the same. SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Annex B: Appendix 3B- Compliance Sheet

Page 58 of 89 Sr. No. 13.7

Requirement Description Allows clearing of open invoices, other items on entry of payment against those items

13.8

Ability to clear multiple debit, credit line items in a single transaction

13.9

Ability to segregate customer transactions and automatic accounting parameters based on:

13.9.1

Payment against invoice - Partial payment or complete payment

13.9.2

Payment for other charges such as maintenance, repair

13.9.3

Non-revenue payments such as security deposit from customers

13.9.4

Capital receipt from customers such as connection charges

13.9.5

Excess payments compared to outstanding invoices

13.10

Possible to park amounts in suspense accounts in case of unaccounted credit / debit

13.11

Automatically Calculates and account for 'cash discounts' based on predetermined parameters in case of payment before specific time interval

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Yes Yes Yes Yes Yes Yes

SAP ERP Financials

Yes

SAP ERP Financials

13.12

Automatically calculates and account for 'delayed payment charges' in case of payment is not made by due date. The charges can be computed in any of the following manner: Charges are accrued at each period end for all outstanding line items beyond due date

Yes

13.12.1

SAP ERP Financials

Yes

SAP ERP Financials

13.12.2

Charges are accrued only at the time of payment of principal. Till then although calculation is made, the same is not accounted for. Allows reversal of payment transaction in case of 'returned' cheques in any of the above scenarios

Yes

13.13

SAP ERP Financials

In case of cleared transactions, the clearing is reset on reversal of payment transaction

Yes

13.14

SAP ERP Financials

Ageing of such invoices is restated to original date for the purpose of calculation of:

Yes

13.15

SAP ERP Financials

Yes 13.15.1

No. of days of outstanding bill

13.15.2

Calculation of overdue interest / penalty

13.16

Ability to configure dunning / automated reminders to customers where payments are not made against invoices

SAP ERP Financials SAP ERP Financials SAP ERP Financials

13.16.1

At least 3 levels of dunning can be configured

13.16.2

Summary as well as details of transactions outstanding can be provided

13.16.3

Details of interest charges / penalties can be provided

13.17

Ability to transfer information related to collections to an external file / database where collections are identified as:

13.17.1

Collections against invoices

13.17.2

Ad-hoc payment by customer

13.17.3

Advance payments by customers

13.17.4

Any other payments by customers

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

Annex B: Appendix 3B- Compliance Sheet

Page 59 of 89 Sr. No.

Requirement Description

13.18

Possible to allow processing of billing while closing of accounts and financial year closing activities

14.0

AR – Reports

14.1

Statement of account for the purpose of obtaining confirmations from customers on balance and transactions

14.2

Due date wise analysis of customer accounts

14.3

Ageing analysis of customer line items

Reference in Proposal SUP

14.5

Ageing can be taken on the basis of both, invoice date & due date

14.6

Customer account trial balance

14.7

Customer account line item details

14.8

Customer account details segregated into:

CST

FUT

Remark NS

SAP ERP Financials

Yes

SAP ERP Financials

Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials

Yes Buckets for ageing can be freely defined by user based on requirements

3RD

Yes

Yes

14.4

MOD

Yes Yes Yes

Yes Invoices and payments Yes Advances paid Yes LCs and bank guarantees Yes

SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials SAP ERP Financials

14.9

Customer account balances and transactions per vendor control account Yes

14.10

Ability to view / print all the above customer account and line item reports per branch, division, location etc.

SAP ERP Financials

Yes

14.11

Availability of details of payments made before due data and corresponding cash discount allowed to customers

SAP ERP Financials

Yes

14.12

Ability to provide details of payments segregated into ontime payment, early payment and delayed payment

SAP ERP Financials

Yes

14.13

Ability to report on total volume of business generated, discounts allowed to Customer

SAP ERP Financials

15.0

Assets - CWIP Yes

Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g

15.1

Allows capitalization of assets through CWIP route Yes

15.2

Allows debiting direct purchases to CWIP Yes

15.3

Allows debiting of materials issues to CWIP Yes

15.4

Allows capital receipts to be credited to CWIP before capitalization of assets

15.5

Allows apportionment of total cost of CWIP over multiple assets based on: Yes Pre-determined criteria

Financials and assets accountin g

Annex B: Appendix 3B- Compliance Sheet

Page 60 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

Yes Formula entry at the time of capitalization Yes Direct entry of amounts from CWIP to Asset Yes 15.6

Allows allocation of indirect expenses to CWIP Yes

15.7

Allows definition of multiple parts of one single asset. Allows classification of CWIP expenses over asset parts as well Yes

15.8

CenVAT(Central Value Added Tax) net off record is maintained and reversed if asset is disposed off in specific time frame Yes

15.9

Allows adjustment in capitalization due to exchange fluctuation

15.10

Supports capital expenses budgeting such as: Yes

15.10.1

Asset level budgeting is possible Yes

15.10.2

Project level budgeting is possible Yes

15.11

Allows classification of assets into groups to facilitate grouping of similar assets

15.12

Allows creating assets with all requisite information such as: Yes

15.12.1

Description of asset Yes

15.12.2

Date of capitalization Yes

15.12.3

Vendor details Yes

15.12.4

Quantity of assets Yes

15.12.5 15.12.6

Location of asset, cost centre Depreciation related details such as method, rate

Yes

MOD

3RD

CST

FUT

Remark NS

Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin

Annex B: Appendix 3B- Compliance Sheet

Page 61 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

g Yes 15.12.7

Asset insurance details Yes

15.13

Any change in any of these details should be carried out as per makerchecker concept Yes

15.14

Flexibility to create equipment details out of asset records to track and control maintenance jobs on the assets Yes

15.15

Allows recapitalization of assets for further capital receipts such as registration charges, connection charges etc.

15.16

Ability to create projects and develop project budgets

15.17

Ability to capture costs for each project (either capex or otherwise) and link to contracts, HR costs, overheads and material issues

Yes Yes Yes 15.18

Project variance reports Yes

15.19

Ability to manage project accounting like milestone definition, payment certificate and accounting against relevant contract Yes

15.20

Ability to maintain separate account management for retention with vendor wise details

16.0

Assets - Depreciation Yes

16.1

Allows defining different types of depreciation methods such as:

Yes 16.1.1

Straight line method (SLM) Yes

16.1.2

Written down value method (WDV) Yes

16.2

Allows multi-shift depreciation Yes

16.3

Allows working of different depreciation for same assets which may be used for different purposes

Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Project Systems Project Systems Project Informatio n Systems Project Systems with Certificate to be developed as per FEWA’s requireme nt. SAP ECC 6.0 Financial Managem ent Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g

Annex B: Appendix 3B- Compliance Sheet

Page 62 of 89 Sr. No.

Requirement Description

Reference in Proposal SUP

Yes 16.3.1

For the purpose of books of accounts Yes

16.3.2

For the purpose of costing / MIS purposes Yes

16.4

Allows to calculate depreciation on a pro-rata basis Yes

16.5

Allows defining a threshold value below which assets need not be defined, and a threshold limit below which assets should not be depreciated. Yes

16.6

Allows automatic calculation of depreciation based on pre-defined criteria Yes

16.7

Allows calculation and posting of depreciation at monthly intervals, with an option of posting, posting with reversal entry Yes

16.8

Allows both upward and downward revaluation of assets

16.9

Supports accounting of revaluation of assets Yes

16.10

Allows depreciation calculation on revalued portion and charge of revaluation depreciation on: Yes

16.10.1

Revaluation reserve Yes

16.10.2

Capital reserve Yes

16.11

Option of calculation of depreciation with retrospective effect in case of change of method or rate of depreciation. Yes

16.12

For retrospective change, calculation of prior period items posted during current fiscal year.

16.13

Allows transfer of an asset to other locations, departments, divisions or branches

17.0

Assets - Sale

Supports sale of asset and carries out profit & loss calculation

3RD

CST

FUT

Remark NS

Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g

Yes Yes

17.1

MOD

Financials and assets accountin g

Annex B: Appendix 3B- Compliance Sheet

Page 63 of 89 Sr. No.

Requirement Description

17.2

Posting of capitalization, depreciation, sale of asset is automatic based on pre-determined characters

17.3

Supports automatic calculation of profit or loss on sale of assets based on book depreciation

18.0

Assets - Reports

18.1

Reference in Proposal SUP

Asset no. with part no. and asset description

Date of capitalization, original cost, accumulated depreciation and WDV

Additions and deletions from assets over a period Yes Cost centre, location of asset

18.1.5

Unit of measurement of asset such as meters, feet, kgs etc. Yes

18.2

Reports on transactions during the year such as: Yes

18.2.1

Purchase of new assets Yes

18.2.2

Sale of assets Yes

18.2.3

Details of sale, transfer and written off Yes

18.2.4

Location details of assets to be used for physical verification Yes

18.2.5

Income tax depreciation details

18.2.6

Book depreciation

Remark NS

Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g Financials and assets accountin g

Assets register to provide all the details about every asset in the books of accounts. Some of the critical details include:

18.1.4

FUT

Yes

Yes 18.1.3

CST

Financials and assets accountin g Financials and assets accountin g

Yes 18.1.2

3RD

Yes

Yes 18.1.1

MOD

Annex B: Appendix 3B- Compliance Sheet

Page 64 of 89 Sr. No. 19.0 19.1

Requirement Description Payroll Accounting Integrated with the HR module for Employee's details like : Name, Address, Employee code, designation, grade, position, cost centre, etc.

Reference in Proposal SUP

Allows to maintain and update employee's salary / wage structure

19.3

Allows to track changes made to the structure

Yes Yes 19.4

Provision for commission tables for complex calculations

19.5

Captures employee's bank account number and bank details

19.6

Allows to define different salary or wage classes and scales

19.7

Allows to define unlimited no. of new heads of pay or new heads of deduction at a later date to accommodate any changes in the salary structure / wage structure due to internal changes or statutory changes

19.8

Allows to capture cost centre of each employee and salary or wage data can be allocated to various cost centers

3RD

CST

FUT

Remark NS

Yes

Yes 19.2

MOD

Yes Yes Yes

SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM

Yes

19.9

Yes

Unlimited number of salary / wage types and bases Yes

19.10

Allows to define standard and branch / division or location specific salary / wage types

19.11

Allows defining designation / grade specific salary or wage type

Yes Yes

SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM

19.12

Allows transferring of attendance records to payroll system in batch mode or manually

19.13

Allows calculation of overtime and other shift dependent allowances based on the attendance records transferred to payroll system.

19.14

System should be able to categorize the deductions (deduction on advance taken, loans from company or external organizations, payments for any other purposes to external org., etc)

19.15

Provision of supporting loan details / advances taken via: amount taken, tenure, amount of each installment

Yes

SAP HCM

Provision to set loan and advances re-payment schedule with an option to modify the same

Yes

SAP HCM

Provision to print salary / wage slips as per user defined format providing details of emoluments and deductions

Yes

SAP HCM

19.16 19.17 19.18

Yes Yes

SAP HCM Yes

Option of exporting salary / wage slip in desired format Yes

19.19

Provision to carry forward negative salary / wage of an employee to the next payroll cycle subject to specific authorisation

19.20

Provision to consolidate salary bill across groups, slabs, seniority etc

Yes Yes

19.21

Global editing of wage records (e.g: if conveyance allowance has increased uniformly across grade levels then a single update in the Salary Master will drill down to the individuals in that category)

19.22

On-line and batch payroll statements

Yes Yes

19.23

Selection of salary by departments, locations, grade or bank through which payment will be processed

19.24

Should allow for Pro Rata calculations

Yes Yes

19.25

Wage payments by electronic system such as Bank transfers / Cheque / Cash

SAP HCM

Yes

SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM SAP HCM

Annex B: Appendix 3B- Compliance Sheet

Page 65 of 89 Sr. No. 19.26

Requirement Description

Reference in Proposal SUP

MOD

3RD

CST

FUT

Remark NS

Unlimited number of salary statements per month

19.27

Should be able to generate employee-wise records of unpaid salary

19.28

Should be able to calculate the arrear payment automatically once the details of arrear payments are entered

Yes

SAP HCM SAP HCM SAP HCM

19.29

Should allow for employees to claim allowances as per the approved salary structure

Yes

SAP HCM

Yes Yes

19.30

Should allow for each claim to be approved, on a workflow basis

19.31

Should allow for automatically converting the claims to payment vouchers, based on the nature of claim and amount.

Yes

SAP HCM SAP HCM

19.32

Print and export to a file payroll journal by month / period / cumulative / previous years

Yes

SAP HCM

Yes

19.33

19.34 19.35

1.4.3

In the case of Full and Final Settlements, the final salary / is to be generated upon receipt of clearances as per the HR module. Calculations for End of Service benefits to be done as per user definitions and added to the settlement package. In case of final settlement, the system should stop processing salary for that employee

Yes SAP HCM

Yes

The system should have provision to stop payment for employees who are marked as absconding

SAP HCM

Supply Chain Management

Sr. No. 1

SAP HCM

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

General

1.1 1.1.1

Possible to define material master Item code

1.1.2

Item description

1.1.3

Unit of measure (in alphanumeric characters)

1.1.4

Specifications (should have provision for attaching documents / drawings)

1.1.5

Shelf-life

1.1.6

Reorder point (maximum / minimum stock levels)

1.1.7

Economic order quantity

1.1.8

Size/volume

1.1.9

Categories as capital, consumable, operations & maintenance

1.1.10

Cross-reference qualified vendor information to each purchased part of subassembly by:

1.1.11

Vendor number

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

1.1.12

Vendor name

1.1.13

Vendor part number

Yes Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 66 of 89 Sr. No. 1.1.14

Requirement Description

Compliance SUP

MOD

Item code Manufacturers' part number Yes

1.2

Possible to define material as the following

1.2.1

Capital for projects (Steel, etc.)

1.2.2

Consumable

1.2.3

Spares

1.2.4

Operations & maintenance (e.g. maintenance tools)

1.2.5

Damaged material

1.3

Possible to define groups of materials like main group, sub group etc.

1.4

Should be possible to mark items as indigenous or imported

CST

Remark FUT

NS

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Yes 1.1.15

3RD

Yes Yes Yes Yes Yes Yes Yes

SAP ERP MM SAP ERP MM

Yes 1.5

System should generate material code (alpha-numeric) based on user defined logic

1.6

Possible to map material code of a processed material with material codes of components that are used to prepare the processed material

1.7

Possible to avoid generation of material code for the same material specification

Yes

In case of generation of a new material code, ability to map all old codes with the new codes

Yes

1.9

Possible to define a master list of vendors with following details

Yes

1.9.1

Company details (address, contact person, etc.)

Yes

1.9.2

Material supplied by the vendor

Yes

1.9.3

Lead times for material supplied by vendor

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

SAP ERP MM

Yes

SAP ERP MM Yes

1.8

1.9.4

Prices of items supplied by vendor

Yes

1.10

Possible to define stores in the system with following details

Yes

Location of store

Yes

Code for the store (multiple stores definition possible)

Yes

Whether FEWA store or contractor store

Yes

Name of the contractor whose store it is

Yes

Department using the store

Yes

Items stored in the store (Capital / Spares / Consumables. etc.)

Yes

1.11

Provision to pass rectification entries for any errors during document creation/approval

Yes

1.12

Possible to capture details about Letter of credit

1.10.1 1.10.2

SAP ERP MM

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

1.10.3 1.10.4 1.10.5 1.10.6

Yes

SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 67 of 89 Sr. No. 1.12.1 1.12.2

Requirement Description

Compliance SUP

MOD

Provision to capture letter of credit/Buyers' credit information

Yes

Provide reports on L/Cs pending retirement, expiry dates

Yes

Provision to track L/c limits

Yes

Provision to load L/C charges on goods received

Yes

Provision to track payments through L/Cs, remittances

Yes

1.13

Possible to enter rectification vouchers for any wrong entries made earlier

Yes

1.14

Possible to define audit information like creator, approver and define access control for information

3RD

1.12.4 1.12.5

Contracts Possible to define a contract with the contractor (selected based on tendering process) with following details

Yes

2.1.1

Contract type

Yes

2.1.2

Contract number

Yes

2.1.3

Terms and conditions

Yes

2.1.4

Scope of work under the contract (attach documents / drawings as a part of specifications)

Yes

2.1.5

Schedule of rates (i.e. rates for each activity under the contract)

Yes

2.1.6

Start date / End date

Yes

2.1.7

Contractor details

Yes

2.1.8

Sub-Contractors

Yes

2.1.9

Payment terms and amount

2.1.10

Normal (allowable) loss of material

Yes

2.2

Possible to define contract types

Yes

2.2.1

Annual rate contract (ARC)

Yes

2.2.2

Single purchase contract

2.3

Possible to capture following details specific to contracts with Energy/Water suppliers

Yes

2.3.1

specifications of the Energy to be supplied with possible range of parameters (e.g. range within which the supply voltage should fall)

Yes

2.3.2

upper and lower limit of quantity of volume to be supplied with possible range of parameters

Yes

NS

SAP BASIS SAP ERP MM SAP ERP MM

Yes

2.1

Remark FUT

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

1.12.3

2

CST

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM Can be customize d as per the actual requireme nt SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM Using the material master data parameter s. SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 68 of 89 Sr. No.

Requirement Description

Compliance SUP

2.3.3

Charges for consumption on time-of-day

Yes

2.3.4

Charges for consumption limits (upper and lower limit)

Yes

2.3.5

Pricing formulae (involving addition, subtraction, etc.) using above specifications of contract Other terms and conditions (take or pay, Billing, credit period, etc.) (refer to

Yes

MOD

3RD

CST

Remark FUT

NS

SAP ERP MM SAP ERP MM SAP ERP MM

requirements defined in "Billing" for further details)

Yes

2.4

Possible to define above contract details based on the data already captured during tendering process

Yes

SAP ERP MM SAP ERP MM

2.5

Possible to link Project(s) with the Contract (i.e. link Project number(s) with a Contract number)

Yes

SAP ERP MM

2.6

Possible to amend the contract by defined authority

Yes

2.7 2.8 3 3.1

Monitor contract performance and input key contract events Possible to capture Guarantee (if any) related to the contract Material requisition and indent Possible to define list and quantity of material (Bill of Material) requirement for provision of each domestic connection

Yes

3.2

Possible to compute aggregate material requirement based on the conversion targets for the year

Yes

SAP ERP MM SAP ERP MM

3.3

Possible to arrive at monthly indent plan for the material requirements for an year arrived as above

Yes

SAP ERP MM

Yes

SAP ERP MM

Yes

SAP ERP MM

2.3.6

Yes

SAP ERP MM Can be customize d as per the actual requireme nt

3.4

Possible to prompt for raising an indent when material reaches reorder level

3.5

Possible to release a Delivery order for an ARC contract when material reaches reorder level (considering on variable demand)

3.6

Possible to check material delivery pending against existing Purchase orders

3.7

Possible to generate an indent for material with following details

Yes

3.7.1

Material code, description and quantity

Yes

3.7.2

Expected delivery date

Yes

3.7.3

Project number of project for which the material is required

Yes

3.7.4

Location where material is required

Yes

3.7.5

Material inspection plan / approach

Yes

3.7.6

Material delivery location (possible to indicate more than one locations)

Yes

3.7.7

Packing details

Yes

3.7.8

Fields for 'Purpose of indent', 'Remarks', Attaching separate file for BEC

Yes

3.7.9

Bid evaluation criteria (Technical)

Yes

3.8

Possible to view item-wise estimated price / last purchase price for each material

Yes

SAP SRM SAP ERP MM SAP ERP MM

3.9

Possible to indicate the total value of the indent

Yes

SAP ERP MM

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 69 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

SAP ERP MM

3.10

Possible to check available stock (at all stores including the contractors' stores) before raising indent

Yes

3.11

Possible to consolidate multiple indents into one

Yes

3.12

Possible to check following before raising indent

Yes

3.12.1

Pending orders

Yes

3.12.2

Material in transit

Yes

3.13

Possible to define authority and limits of raising indent based on designation

Yes

3.14

Possible to check budgeted purchase limits before accepting an indent

Yes

3.15

Possible to grant financial concurrence by finance dept., in case of nonbudgeted items

Yes

SAP ERP MM SAP ERP MM

3.16 3.17

Possible to define workflow based approval process for indents Enables the creator of indent to define the approver

Yes

SAP ERP MM

3.18

Provision to predefine approver for indent depending on

Yes

3.18.1

reporting hierarchy

Yes

3.18.2 3.18.3

amount of indent Type of indent (nomination, limited tender, proprietary, etc.)

Yes

SAP ERP MM SAP ERP MM SAP ERP MM

3.19

Enable changing the indent (quantity, material code, etc.) once it is created

Yes

SAP ERP MM

3.19.1

by creator

Yes

3.19.2

by reviewer

Yes

3.20

Provision for approver to put comments on the indent received for approval by reviewer

Yes

SAP ERP MM SAP ERP MM SAP ERP MM

3.21

Possible to track the history of an indent in terms of creation, modification and approval

Yes

SAP ERP MM

3.22 4

Possible to maintain and view Indent register based on Project number, location and date Tendering process

Yes

SAP ERP PS

4.1

Possible to define workflow and steps for different tendering process like Open, two bid system, etc.

Yes

SAP ERP MM

4.2

Possible to assign the indent to personnel in Purchase department for initiating tendering process

Yes

SAP ERP MM

4.3

Sap ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Yes

4.4

Possible to define a new tender by aggregating multiple indents Support creation of Request for Quotation by including items required, quantity, shipment location, validity period, technical specification, taxes, etc.

4.5

Possible to view list of vendors available for a particular item

Yes

4.6

Support creation of Request for Quotation for service and construction contracts by including work orders

Yes

4.7

Possible to enter responses from vendors in the system

Yes

4.8

Possible to capture the deviations and validity of responses from vendors

Yes

SAP ERP MM SAP ERP MM

Yes SAP ERP MM SAP SRM Binding Period is supported SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 70 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

4.9

Possible to enter revised bids from the vendors in the system with a reference to the revision number which it has undergone

Yes

4.10

Possible to maintain a history of all revised bids received from vendors

Yes

4.11

Possible to capture details of Bid Security received from vendors

Yes

4.12

Possible to define workflow for evaluation of vendor responses involving two stages (Technical and Commercial evaluation)

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

4.13

Enables evaluation of responses based on a pre-defined evaluation criteria and rejection criteria

Yes

SAP ERP MM

4.14

Possible to capture issue of letter to vendors if Bid quotation criteria is not met

Yes

SAP ERP MM

4.15

Possible to arrive at ranking of bidders after consolidation or responses

Yes

4.16

Possible to maintain an audit trail of bidding process in following steps - Approval of Bid quotation / evaluation / qualification criteria - Release of RFQ - Receipt of bids from vendors - Technical / Commercial qualifications - Bid evaluation and negotiations - Selection of vendor

Yes

4.17

Possible to maintain a tender opening register with details of price bids for each vendor

4.18 4.19

Yes

SAP SRM SAP ERP MM

SAP ERP MM SAP ERP MM

Possible to customize the tendering process by adding / removing steps (e.g. open tending process will have additional step of placing newspaper advertisement) System maintains a historical record of bidding process and updates vendor profile by registering every win by vendor

Yes

Purchase order

Yes

5.1

Possible to generate a purchase order using data from one / multiple indents

Yes

SAP ERP MM SAP ERP MM

5.2

Possible to capture details of purchase proposal identifying the material requirements and terms of purchase like delivery date

Yes

SAP ERP MM

5.3

Possible to generate a PO without going through some or all activities like indenting, tendering process & selection of vendor

Yes

5.4

Possible to generate a purchase order / delivery order (for ARC) with following data

Yes

5.4.1

Material code and description

Yes

5.4.2

Material specification

Yes

5.4.3

Quantity

Yes

5.4.4

Price

Yes

5.4.5

Delivery date

Yes

5.4.6

Delivery location (single / multiple)

Yes

5.4.7

Supplier details

Yes

5.4.8

Payment terms

Yes

5.4.9

Names of third party inspection agency

Yes

5

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 71 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

5.4.10

Inspection plan (inspection stages, inspecting agency)

Yes

5.4.11

Packaging details (free text input)

Yes

5.5

Possible to define the purchase order type based on supply source

Yes

5.5.1 5.5.2

Local Imported

Yes

5.6

Possible to link a PO with following

Yes

5.6.1

User department (e.g. O&M, HR)

Yes

5.6.2 5.7

Project code(s) for a project

Yes

SAP ERP MM SAP ERP MM SAP ERP MM

Possible to identify a PO for spares related to particular capital item

5.8

Should allow modification of PO with approval from authority. Modification should be possible related

Yes

SAP ERP MM

5.8.1

Quantity

Yes

5.8.2

Items

Yes

5.8.3

Spares

Yes

5.8.4

Delivery date

Yes

5.9

Should allow maintaining a history of modifications made to PO

Yes

5.10

Should be possible to reopen a PO after it is closed (i.e. material / services provided and payments made). The reopened PO should allow entering of additional material / services

Yes

5.11

Should allow capture of Bank Guarantee details

Yes

5.11.1

BG No.

Yes

5.11.2

Bank name

Yes

5.11.3 5.11.4

Date Amount

Yes Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM Can be customize d as per the actual requireme nts Can be customize d as per the actual requireme nts Can be customize d as per the actual requireme nts Can be customize d as per the actual requireme nts Can be customize d as per the actual requireme

Annex B: Appendix 3B- Compliance Sheet

Page 72 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

Validity

Yes

5.11.6

Vendor / Contractor name

Yes

nts Can be customize d as per the actual requireme nts Can be customize d as per the actual requireme nts

5.12 5.13

System should prompt in advance (user defined number of days) before expiry of BG Should allow analysis of PO's based on following

Yes

SAP ERP MM

Yes

5.13.1

Contract number

Yes

5.13.2

Vendor

Yes

5.13.3

Delivery date

Yes

15.13.4

Quantity

Yes

15.13.5

Rate

Yes

15.13.4

Payment terms

Yes

5.14

Possible to link one or more indents with PO

Yes

5.15

Yes

5.16

Possible to link one or more POs with one or more indents Possible to open and close PO depending on the status of delivery and payment

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

6 6.1 6.2

Material receipt Possible to define an agency for inspection of material Possible to input material inspection details in the system

Yes

SAP ERP MM

6.2.1

Inspection agency

Yes

6.2.2

Name of the inspector

Yes

6.2.3 6.2.4

Inspection date Inspection findings

Yes

6.3

Possible to track status of material from the suppliers' premise

Yes

6.3.1

Dispatched

Yes

6.3.2 6.3.3

Damaged in transit Received at recipient's end

Yes

6.4

Possible to capture material receipt details

Yes

6.4.1

Challan (Receipt for payment or delivery) details

Yes

6.4.2 6.4.3

PO for which material is received Contract number for which material is received

Yes Yes

5.11.5

Yes SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP

Annex B: Appendix 3B- Compliance Sheet

Page 73 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

6.4.4

DO (Delivery order for ARCs) for which material is received

Yes

6.4.5

Date of receipt

Yes

6.4.6

Store where material is received

Yes

6.4.7

Material code of material received

Yes

6.4.8

Quantity of material received

Yes

6.4.9

Date and time of receipt

Yes

6.5

Possible to define location other than the store (e.g. user department at the FEWA Office) where the material is received directly

Yes

6.6

System should alert if the material receipt quantity is greater / less than the quantity mentioned in the PO

6.7

Possible to generate a note to be sent to the supplier identifying following

Yes

6.7.1

Over receipt of material

Yes

6.7.2

Under receipt of material

Yes

6.7.3 6.7.4

Damaged material received Rejection of material after inspection

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

6.8

Possible to modify material receipt details (for reasons like wrong entry initially)

Yes

SAP ERP MM

6.8.1

Material code of material received

Yes

6.8.2

Quantity of material received

Yes

6.8.3

Value of material received

Yes

6.9

System should support capture of multiple PO's for single receipt

Yes

6.10

Possible to define details of material accepted / rejected after inspection on receipt of material

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

6.11

System should automatically update stock in stores on receipt of material

Yes

SAP ERP MM

6.12

System should deduce the quantity of amount "yet to be delivered" from a PO on receipt of material

Yes

SAP ERP MM

6.13

Possible to identify defective material returned by contractor as manufacturing defect or damage due to mishandling

Yes

SAP ERP MM

6.14 7

Possible to map the receipt of processed material from contractors against the issue of material to contractor for preparation of processed material

Material issue

7.1

Possible to capture material requisition details

Yes

7.1.1

Material code

Yes

7.1.2

Material quantity

Yes

7.1.3

Name of the person requesting material

Yes

7.1.4 7.1.5

Name of the entity (FEWA / Contractor) requesting material PO / Contract number

Yes Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP

Annex B: Appendix 3B- Compliance Sheet

Page 74 of 89 Sr. No.

7.1.6

Requirement Description

Date of requisition

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

Yes

MM SAP ERP MM

SAP ERP MM

7.2

Possible to generate a unique issue requisition number

Yes

7.3

Should enable posting details of material issue

Yes

Reference material issue requisition number

Yes

FEWA department to which issue is made

Yes

Name of Contractor to whom issue is made

Yes

Name of personnel requesting material issue

Yes

Project code for which material is issued

Yes

Contract number against which the material is issued

Yes

Material codes of material issued

Yes

Quantity of material issued

Yes

Cost centre for which material is issued Store from which material is issued

Yes

7.4

Should deduct the stock available to the extent of material issued

Yes

7.4.1

In stores

Yes

7.4.2

Available for a project as compared to what was budgeted

Yes

7.4.3

Available for a department as compared to what was budgeted

7.5

Possible to capture lending of material on returnable basis

Yes

7.5.1

Possible to track material issued for processing job & returnable basis

Yes

SAP ERP MM SAP ERP MM

7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 7.3.6 7.3.7 7.3.8 7.3.9 7.3.10

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

7.5.2

Possible to define input/output material conversion unit of measure

Yes

SAP ERP MM

7.5.3

Reconciliation of material issued from processing & received back

Yes

SAP ERP MM

7.6

Possible to mark against each Goods Receipt Voucher, any charges on suppliers

7.7

Possible to capture details of material sale from the stores with following details

Yes

SAP ERP MM

7.7.1

Party whom the sale is made

Yes

7.7.2

Rate of sale

Yes

7.7.3

Quantity of material sold

Yes

7.7.4

Material code of material sold

Yes

7.7.5

Date of sale

Yes

7.7.6

Date of material dispatch from the stores

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 75 of 89 Sr. No.

Requirement Description

Compliance SUP

7.8 8

Possible to trigger an entry for accounts receivables in F&A module equivalent to the value of sale in above case Material stock management

Yes

8.1

At any point of time indicate material

Yes

Budgeted for each project / department

Yes

Ordered for each project / department

Yes

Available at FEWA stores for each project / department

Yes

Available at Contractor's store for each project

Yes

8.1.1 8.1.2 8.1.3 8.1.4 8.1.5

3RD

CST

Remark FUT

NS

SAP ERP Financials SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Consumed by each project / department during the financial yea r

8.2

Track material transfer from

Yes

8.2.1

One store to another

Yes

8.2.2

One project to another

Yes

8.2.3

One contractor to another

Yes

8.2.4

FEWA store to contractor's store

Yes

8.3

Possible to add freight when material is transferred

Yes

8.4

Possible to track material issue under following heads

Yes

8.4.1

Usage for steel for projects (with project number)

Yes

8.4.2

Usage for CPE work at the consumers

Yes

8.4.3

CRN (consumer number) where it is used

Yes

8.4.4

Project number for PE installation

Yes

8.5

Possible to track material through following mechanism

Yes

8.5.1

Capture of material issue information when material is issued

Yes

8.5.2

Capture of information when physical verification is done at project site

Yes

8.6

Possible to track GRV details for capital material received in past

Yes

8.7

Should enable computation of Reorder levels based on the lead times and consumption pattern

Yes

8.8

Should support ABC analysis of material

Yes

8.9

Should support analysis of material loss in transit

Yes

8.10

Should support analysis of normal loss as provided in the contract

Yes

8.12

Possible to make recovery from contractor for loss of material by raising auto-invoice Should support analysis of material budgeted vs. actual for both (Rate and Quantity )

8.13

Possible to capture findings of physical verification of stock

8.11

MOD

Yes Yes Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM Sap ERP PS SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 76 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

Yes

SAP ERP MM

Yes

SAP ERP MM

Yes

SAP ERP MM

Yes

SAP ERP MM

8.14

Possible to update the available stocks of material based on the findings of verification of stock

8.15

Provision to enter material consumption details (based on laid drawings) for a project

8.16

Possible to get an approval from the FEWA engineer for the details on consumption entered in the system

8.17

Provision to get material valuation for material entered as consumed for a project based on purchase price

8.18

Provision to undertake material reconciliation for material consumed vs. material issued for each project

Yes

Vendor / Contractor management

Yes

SAP ERP PS SAP ERP MM

9

9.1

Possible to define frequency and time period for evaluation of vendors

Yes

SAP ERP MM

9.2

Possible to define framework and evaluate vendors based on these parameters

Yes

SAP ERP MM

9.2.1

Lead times for supply

Yes

9.2.2

Quality of material supplied

Yes

9.2.3

Prices of material

Yes

9.2.4

Flexibility shown by the vendor in terms of lead times & prices

Yes

9.3

Possible to define vendors in terms of ranking

Yes

9.3.1

Best performing (long term business partners)

Yes

9.3.2

Average performance

Yes

9.3.3

Blacklisted vendors (to avoid undertaking business in future)

Yes

9.4

Possible to summaries following for each vendor for a user defined period

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

9.4.2

Variability of delivery schedules as compared to agreed schedules

Yes

9.4.3

Variability of prices over a period of time

Yes

9.4.4

New vendors during the last user defined period

Yes

9.5

Provide reports on each vendor

Yes

9.5.1

Orders placed with the vendor during user defined period

Yes

9.5.2

Orders currently live with delivery of material pending

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

9.6 10

Possible to find list of all new items which are developed / procured in user defined period Material valuation

Yes

SAP ERP MM

10.1

Possible to capture following prices related to material

Yes

10.1.1

Current market price

Yes

10.1.2

Actual purchase price

Yes

9.4.1

Instances of material rejected on quality parameters

Yes

SAP ERP MM SAP ERP MM SAP ERP MM

Annex B: Appendix 3B- Compliance Sheet

Page 77 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

SAP ERP MM

10.2

Possible to capture actual purchase price of material directly from the purchase order of the material along with overheads (loading factor) as per PO.

10.3

Possible to link payments of custom duty, transportation, C&F charges, etc along with GRV

Yes

SAP ERP MM

10.4

In case of transfer / issue of material, ability to trace the purchase price of material at any stage (in transfer) for the purpose of valuation

Yes

SAP ERP MM

10.5

Possible to arrive at individual material price based on overall price in case of bulk purchase

Yes

SAP ERP MM

10.6

Possible to define material stock valuation methodologies based on (FIFO, LIFO and/or Weighted average )

Yes

10.7

Possible to arrive at material stock valuation for following groups

Yes

10.7.1

Valuation of material in a project

Yes

10.7.2

Valuation of material in a department

Yes

10.7.3

Valuation of material in a stores

Yes Yes

10.8

Possible to maintain a history of material valuation for user-defined periods

11 11.1 11.2

Business Applications Catalogue Collaboration process support for material management Price Deviations Engineering change order variance and notifications

11.3 11.4 11.5 11.6 11.7 11.8 11.9 11.10 11.11 11.12

1.4.4

Yes

SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM SAP ERP MM

Order tracking and status alerting Quality and yield management Inventory shortages, including notification to replenishment systems Quality control with control charts Machine breakdown alerts and causal analysis Demand volatility, including deviations due to new orders, cancellations, and wrong mix Real-time detection of shrinkage Policy rules analysis and deviation analysis Logistics trace and track notifications of such issues as late deliveries and deviation from routes

Human Capital Management

Compliance Sr. No.

Remark

Requirement Description SUP

1 1.1

Employee Database and Organization Structure Maintain employee information including:

1.1.1

Employee number

Yes

MOD

3RD

CST

FUT

NS

SAP ERP HCM

Annex B: Appendix 3B- Compliance Sheet

Page 78 of 89 Compliance Sr. No.

SUP

1.1.2 Employee name

Yes

Address (Present and permanent)

Yes

Phone number, mobile number, e-mail ID, extension number

Yes

Date of Birth and Gender

Yes

Marital status

Yes

Details of children

Yes

Academic Qualifications and Professional qualifications

Yes

Designation Previous experience capturing Names of companies, Sector of industry were worked Tenure (from - to) and Role

Yes

Trainings or courses undergone before joining MGL

Yes

Date of joining

Yes

Cost to Company (this field should be password protected)

Yes

1.1.3 1.1.4 1.1.5 1.1.6 1.1.7 1.1.8 1.1.9 1.1.10

1.1.12 1.1.13 Status (Permanent, Probation, Management Trainees, Graduate Engineer Trainees)

MOD

3RD

CST

FUT

NS

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Yes

1.1.11

1.1.14

Remark

Requirement Description

Yes

1.1.15

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Nationality

Yes

ID Number

Yes

Passport Number and resident ID ( for non Local )

Yes

Blood group

Yes

Other details like insurance

Yes

1.2

Should be possible to transfer all (available) fields mentioned above from the applicant database (generated during the recruitment process) to employee database

Yes

1.3

Should support defining reporting hierarchy for employees to include multilevel reporting or multi disciplinary reporting

Yes

1.4

Should be possible to capture details of transfer of an employee from one department to another without changes other attributes like employee number

Yes

1.5

Should track all employee history in MGL in terms of past roles as well as past performance and positions

Yes

SAP ERP HCM

1.6

Should allow for maintaining a checklist of details to be mentioned in each employee's personnel file

Yes

SAP ERP HCM

1.1.16 1.1.17 1.1.18 1.1.19

1.7 1.8

System should capture frequency of replacement for items issued to employees System should support 150 free fields per employee to support capture of additional employee information

SAP ERP HCM SAP ERP HCM

Yes Yes

SAP ERP HCM There is space available to store documents , make

Annex B: Appendix 3B- Compliance Sheet

Page 79 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

MOD

3RD

CST

FUT

NS

notes, and create documents and to store them per employee in the DMS. SAP ERP HCM

1.9

Should support creation of organisation structure to include Location, Department and assigning employees to it

Yes

1.10

Possible to allocate employees to cost centers

Yes

Should support maintaining an employee history to include change in assignments, promotions, transfers, pending issues etc.

Yes

SAP ERP HCM SAP ERP HCM

Yes

SAP ERP HCM

1.11 2

Manpower Budgeting

2.1

Should support planning for manpower across all departments and cost centers

2.2

Should support automatic planning of manpower based on yearly revenue budgets on basis of user defined rules. This planning should be for - No. and Type of personnel - Employees or Contract personnel - Skills of personnel

Yes

2.3

The system should support workflow based approval of manpower budgets

Yes

2.4

Manpower planning should be integrated with Cost Centre and other levels of Budgeting

Yes

2.5

Should have facility to consolidate the manpower requirements

Yes

2.5.1

Department wise

Yes

2.5.2

Function wise

Yes

2.5.3

Grade wise

Yes

2.5.4

Profile wise

Yes

2.6 3

Should support what-if analysis tool for increase or decrease in wages or number employees to analyze the financial impact of the same Recruitment

Yes

SAP ERP HCM

3.1

Maintain personnel databank for details of candidates applied along with interview details

Yes

3.2

Should support recruitment through agencies

Yes

3.2.1

Track resume through agencies

Yes

SAP ERP HCM SAP ERP HCM and FI CO SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt

Annex B: Appendix 3B- Compliance Sheet

Page 80 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

3.2.2

If recruited then create a liability to pay the agency based on an agreed contract

Yes

3.3

Should provide for maintaining a database of recruitment agencies

Yes

3.4

Should be possible to initiate recruitment process involving following

Yes

3.4.1

Recruitment portal (possible to interface with the portal for data exchange)

Yes

3.4.2

Educational institutions

Yes

3.4.3

Internal recommendations / referrals

Yes

3.5

Should support preparation of a recruitment plan outlining following

Yes

3.5.1

Details of posts to be filled

Yes

3.5.2

Start date of recruitment process

Yes

3.5.3

Source(s) of recruitment

Yes

3.5.4

Involvement of MGL personnel in recruitment process

Yes

3.6

System should support checking of qualifications, experience, etc. of internal staff before preparing an eternal recruitment plan

Yes

MOD

3RD

CST

FUT

NS

SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt

Annex B: Appendix 3B- Compliance Sheet

Page 81 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

3.7

The system should support deduction in requirement of manpower once the manpower is recruited against a posted requirement

Yes

3.8

Should support comparison of manpower budgeted vs. manpower recruited for a particular period

Yes

3.9

Should support workflow based approval of manpower requirements based on budgets

Yes

3.10

Should provide for defining multiple types of correspondence with applicant

Yes

3.10.1

Interview schedule letters

Yes

3.10.2

Appointment letters

Yes

3.10.3

Regret letters

Yes

3.11

Should have facility to keep a track on the status of recruitment activities

Yes

3.11.1

Screening

Yes

3.11.2

Interviews

Yes

3.11.3

Selection

Yes

3.11.4

Pay package negotiation

Yes

MOD

3RD

CST

FUT

NS

SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt

Annex B: Appendix 3B- Compliance Sheet

Page 82 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

3.11.5

Acceptance of offer

Yes

3.11.6

Joining facilities

Yes

3..11.7

Appointment

Yes

3.11.8

Nomination form

Yes

3.11.9

Medical test

Yes

3.11.10

Should support workflow based recruitment process involving approvals at various -stages of recruitment process

Yes

3.12

Should have feature to analyse the history of recruitment events

Yes

3.12.1

College/Institute/Agency

Yes

3.12.2

No. of applications

Yes

3.12.3

No. of candidates appeared

Yes

3.12.4

No. of candidates selected

Yes

3.12.5

No. of candidates joined

Yes

MOD

3RD

CST

FUT

NS

SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt SAP ERP HCM and eRecruitme nt

Annex B: Appendix 3B- Compliance Sheet

Page 83 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

3.13 4

Should have facility to define contract terms and generate Employment Contract Training

Yes

4.1

Should be possible to prepare budgets for training

Yes

4.2

Should support workflow based approval of training budgets

Yes

4.3

Should be possible to define minimum training hours for employees

Yes

4.4

Should support definition of standard / compulsory trainings required (e.g., induction, basic course) for employees depending on the designation, company and department

Yes

4.5

Should be possible to define types of trainings

Yes

4.5.1

Technical training

Yes

4.5.2

Managerial training

Yes

4.5.3

Engineers' training

Yes

4.5.4

Yes

4.6

Safety related training Should be possible to define codes for training programs based on type of training, area of training, internal / external training

4.7

Should be possible to define the master list of training programs covering following

Yes

4.7.1

Training code

Yes

4.7.2

Training duration

Yes

4.7.3

Target audience / department

Yes

4.7.4

List of trainers (internal / external)

Yes

4.8

Should have facility to design training calendar

Yes

4.8.1

Trainer

Yes

4.8.2

Trainee

Yes

4.8.3

Courses

Yes

4.8.4

Training date

Yes

4.8.5

Training evaluation criteria

Yes

4.8.6

Training subject

Yes

4.8.7

Expenses

Yes

4.8.8

Batches

Yes

4.8.9

Employee performance parameter

Yes

Yes

MOD

3RD

CST

FUT

NS

SAP ERP HCM and eRecruitme nt SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Annex B: Appendix 3B- Compliance Sheet

Page 84 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

MOD

3RD

CST

FUT

NS

SAP ERP HCM

4.10

Should support allocating personnel for training courses defined in the training calendar Should support selection of personnel for training based on present skills, improvement areas and previous trainings taken (Gap analysis)

4.11

Should support identification of training needs for each employee on a yearly basis

Yes

4.12

Support capturing details of training courses conducted as :

Yes

4.12.1

Names of participants

Yes

4.12.2

Training subject and description

Yes

4.12.3

Duration of training

Yes

4.12.4

Faculty involved in imparting training

Yes

4.12.5

Cost incurred in provision of training

Yes

4.13

Monitor training taken by an employee for a user defined period

Yes

4.14

Monitor month-wise budgeted vs. actual expenditure in training

Yes

4.15

Should have facility to collect feedback and analyse effectiveness of the training

Yes

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

4.16

The system should support triggering of training due date for employees for recurring trainings (refresh trainings)

Yes

SAP ERP HCM

4.17

Monitor training expenses by employee, department or cost centre

Yes

4.18 5

Defining a framework for assessing benefits to employee after training is imparted Performance appraisal

Yes

5.1

Should have provision to remind for confirmations a month before the probation period / training period ends

4.9

Yes Yes

Yes

5.3

Should be possible to define goals for the organisation and departments to arrive at appraisal framework / parameters System should support definition of appraisal parameters and framework depending on Department, Designation, Role and Others

5.4

Possible to define KPI's for each employee and monitor the same during the year

5.5

Should support definition of appraisal framework involving rating on different parameters and doing mathematical computation to arrive at a final scores / ranking for employee

Yes

5.6

Should support process of self appraisal where employees may assess their own performance for the performance period

Yes

5.7

Should be possible to define the frequency (yearly, half-yearly, quarterly, etc.) of performance appraisal

Yes

5.8

Should have facility to track status of performance appraisal process (Issuing of appraisal forms, Review of performance, Revision of benefits, Approval of the appraisal, Issuing increment letter, Ranking category, Updating revision in payroll)

Yes

5.9

System should support checking following details as a part of appraisal

Yes

5.9.1 5.9.2

Performance grading Years of experience in the same grade

Yes Yes

5.2

Yes

SAP ERP HCM SAP ERP HCM

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Yes Yes

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP

Annex B: Appendix 3B- Compliance Sheet

Page 85 of 89 Compliance Sr. No.

SUP

5.9.3

Remark

Requirement Description

Training undergone

Yes

MOD

3RD

CST

FUT

NS

HCM SAP ERP HCM SAP ERP HCM

5.11

Possible to define minimum years of experience required for each grade before promoting to next grade The system should support workflow based appraisal involving multiple rounds of interactions / discussions / finalisation

5.12

System should support definition of all personnel who would evaluate an employee and the sequence (e.g. immediate superior followed by the Head of Department) of appraisal

5.13

The system should capture the process of feedback and counseling between employees and respective appraisers

Yes

5.14

Should support entering a development plan for employee at the end of appraisal process

Yes

SAP ERP HCM

5.15

Possible to monitor progress on the development plan for each employee

Yes

SAP ERP HCM

5.16 6

The system should support analysis of department-wise increase in cash outflow in case of increments Travel Management

Yes

SAP ERP HCM

5.10

Yes Yes

Yes

6.1

Should allow for recording travel requisitions as per travel policy with the following details

Yes

6.1.1

Employee

Yes

6.1.2

From/To, Travel Dates and Mode of Travel

Yes

6.1.3

Project Code

Yes

6.2

Should be possible to define the purpose of travel (eg. Training, Supplier Development, Holiday, etc)

Yes

6.3

Should support requisitions for:

Yes

6.3.1

Travel Tickets

Yes

6.3.2

Vehicles

Yes

Accommodation

Yes Yes

6.3.3 6.4

Should support a workflow based authorization for travel requisitions. The authorizing person should be determined based on:

SAP ERP HCM SAP ERP HCM SAP ERP HCM

SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel

Annex B: Appendix 3B- Compliance Sheet

Page 86 of 89 Compliance Sr. No.

SUP

6.4.1

Project Code

Yes

6.4.2

Employee, supervisor

Yes

6.5

Should allow for recording travel arrangements booked against each travel requisition

Yes

6.6

Should allow for recording advances for travel against a requisition, after approval

Yes

6.7

Should allow for recording travel expense report once the travel is completed

Yes

6.8

Should automatically account for the travel expense report after approval

Yes

6.9

Should be integrated with accounts payable for creating liabilities against each travel expense recorded in the travel expense report

Yes

6.10

Should be integrated with Project Management for recording travel related expenses against the project

Yes

6.11 7

Remark

Requirement Description 3RD

CST

FUT

NS

Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent SAP ERP Travel Managem ent

7.2

Should allow for final settlement of a travel Time and attendance System should capture leave entitlements for different types leaves, for each employee depending on the employee profile (legal entity, designation, years of service in company , etc.) Should support to define rules for leave management for short leaves, overtime, compensatory leaves company wise or department wise

7.3

Should be possible to define hierarchy for approval of leave for every employee

Yes

7.4

Should be possible to apply and track approval of leave

Yes

7.5

Should have integration with external attendance registration systems for capturing time-in and time-out of every employee

Yes

7.6

Should be possible to define the office timings per office location

Yes

7.7

Should be possible to capture employee-wise days of attendance and leave taken details

Yes

SAP ERP HCM SAP ERP HCM

7.8

Possible to generate report with details of office time for each employee (department-wise)

Yes

SAP ERP HCM

7.8.1

Late coming to office

Yes

SAP ERP HCM

7.1

Yes

MOD

SAP ERP HCM Yes Yes

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Annex B: Appendix 3B- Compliance Sheet

Page 87 of 89 Compliance Sr. No.

Remark

Requirement Description SUP

7.8.2

Late sitting

Yes

7.8.3

Over time

Yes

7.9

Should be possible to capture location where the employee was on duty for every day of presence marked

Yes

7.10

Should be possible to define types of leaves (e.g. Annual leave, Medical leave, etc.)

Yes

7.11

Should have facility to track leave status of employee

Yes

7.12 8

Should have integration with payroll processing system to transfer data like no. of days present in a month, overtime taken, leaves taken, absent without notice, etc. for the purpose of computation of salary Separation

Yes

8.1

Should have facility to track status of separation process

Yes

8.1.1

Submitting resignation letter

Yes

8.1.2

Acceptance letter

Yes

8.1.3

Notice period validation

Yes

8.1.4

Accounts settlement

Yes

8.1.5

Yes

8.2

Issue of experience certificate Capturing of exit interview details. The details include - Date of exit interview - Conducted by - Key findings in the Exit Interview

8.3

Should support check of return status of material issued to employees for final clearance

Yes

8.4

Should support calculation of amount due as End of Service benefits

Yes

8.5

Provide classification of separation due to

Yes

8.5.1

Resignation

Yes

8.5.2

Terminal notice

Yes

8.5.3

Death

Yes

MOD

3RD

CST

FUT

NS

SAP ERP HCM SAP ERP HCM Informatio n from the external attendance registratio n systems (integrated into SAP ERP HCM) can be used to locate an employee’ s whereabo uts for the day. SAP ERP HCM SAP ERP HCM SAP ERP HCM

SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Yes SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM SAP ERP HCM

Annex B: Appendix 3B- Compliance Sheet

Page 88 of 89 Compliance Sr. No.

SUP

8.5.4

Disciplinary action

Yes

8.5.6

Contractual terms

Yes

8.5.7

Retirement

Yes

9 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 9.11 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 10.14 10.15 10.16

Remark

Requirement Description

Health and Safety Report and investigate incidents of injury and illness for employees and contractors Initiation of corrective actions related to an incident Logging of first aid records and reports Manage occupational injury and illness claims Report incidents involving vehicles and equipment Detect and monitor hazardous conditions (areas) and materials & exporting them via an interface for further processing Maintenance of agent composition and information in a central database Integration with supply chain and HR modules Perform accident investigations, identifications, and recording Support OSHA “Occupational Safety and Health Act” , and safety regulatory reports Maintain database of all MSDS(material safety data sheet) sheets for all materials used Employee Self-Service Review and maintain name, address, telephone number, etc., associated with life events Review or enroll in benefits for open enrollment period

MOD

3RD

CST

FUT

NS

SAP ERP HCM SAP ERP HCM SAP ERP HCM Wipro shall develop the same. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Yes Yes

Change benefits related to a life event

Yes

View pay stub info: gross pay, other deductions, net pay, pay period, and year-to-date totals Maintain dependents and beneficiaries

Yes

Maintain emergency contacts

Yes

Review vacation and sick day balances and submit leave requests

Yes

Review and maintain bank info for direct deposit and reimbursements

Yes

Review and enter or submit expenses

Yes

Account for time based on type of absence or attendance

Yes

Choose and maintain personal passwords

Yes

Posting and updating resumes

Yes

View personal training history

Yes

Search for available courses based on topic, text, language, and location

Yes

View course calendars and details

Yes

Enroll in or cancel participation in courses

Yes

Yes

SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP HCM ESS SAP

Annex B: Appendix 3B- Compliance Sheet

Page 89 of 89 Compliance Sr. No.

SUP

10.17 10.18

1.4.5

Review and maintain deduction information for automatic bill payment service Review and maintain a knowledge sharing diary

1.1 1.2

MOD

3RD

CST

FUT

NS

HCM ESS SAP HCM ESS SAP HCM ESS

Yes Yes

Asset Lifecycle Management

Sr. No. 1

Remark

Requirement Description

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

General

Possible to define zones / areas for operations and maintenance Associate following with the defined zones / areas

Yes

1.2.1

O&M team responsible for the zone / area

Yes

1.2.2

Control room number for the zone / area

Yes

1.3

Possible to capture equipment details

Yes

1.4 1.5

Possible to mark sending of communication to entities with details of the equipment Define category of maintenance

Yes

1.5.1

Distribution network

Yes

1.5.2

Consumer end (PE, etc.)

Yes

1.5.3

Network station

Yes

SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Work Flows SAP ERP Plant Maintenan ce Order Parameter s SAP ERP Plant Maintenan ce Order Parameter s SAP ERP Plant Maintenan ce Order Parameter s

Annex B: Appendix 3B- Compliance Sheet

Page 90 of 89 Sr. No.

1.5.4 1.6

Requirement Description

Others ( please specify ) Define type of maintenance

Compliance SUP

Yes

1.6.1

Preventive maintenance

Yes

1.6.2

Breakdown maintenance

Yes

1.6.3

Emergency maintenance

Yes

1.7

Ability to define routine maintenance activities for each equipment with following characteristics

1.7.1

Frequency

Yes

1.7.2

Calendar based schedule

Yes

1.7.3 1.7.4

Details of maintenance to be done Equipment / spares required to undertake maintenance

Yes Yes

MOD

3RD

CST

Remark FUT

NS

SAP ERP Plant Maintenan ce Order Parameter s SAP ERP Plant Maintenan ce Preventive Maintenan ce Managem ent SAP ERP Plant Maintenan ce - Work Order Managem ent SAP ERP Plant Maintenan ce - Work Order Managem ent

SAP ERP Plant Maintenan ce Strategies of Maintenan ce SAP ERP Plant Maintenan ce Strategies of Maintenan ce SAP ERP Plant Maintenan ce Preventive Maintenan ce Planning SAP ERP Plant Maintenan ce Preventive

Annex B: Appendix 3B- Compliance Sheet

Page 91 of 89 Sr. No.

Requirement Description

Compliance SUP

1.7.5

Expected time required for maintenance activity

Yes

1.8

Ability to capture maintenance activities recommended by the manufacturer of equipment

Yes

1.9

For all the maintenance activities defined in the system, defining clearances required from internal (safety department) / external agencies

Yes

1.10

Ability to define teams with maintenance responsibility associated with following

1.10.1

Category of maintenance to be carried out

Yes

10.2

Zone / area of maintenance

Yes

1.11

Ability to define operations staff for each zone / area

Yes

1.12

Definition of contractors for maintenance activities with following attributes

1.12.1 1.12.2

Zone / area of maintenance Category of maintenance to be carried out

Yes Yes

MOD

3RD

CST

Remark FUT

NS

Maintenan ce Planning SAP ERP Plant Maintenan ce Preventive Maintenan ce Planning SAP ERP Plant Maintenan ce Maintenan ce Planning & Schedulin g SAP ERP Work Clearance Managem ent

SAP ERP Plant Maintenan ce Master Data of Work Centers SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data

SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master

Annex B: Appendix 3B- Compliance Sheet

Page 92 of 89 Sr. No.

Requirement Description

Compliance SUP

1.12.3

Equipment (make, equipment ID) for which maintenance to be done

Yes

1.13 2

Should have integration with Contracts modules to capture data (including the rates for services, etc.) related to contractors for maintenance work Asset management

Yes

2.1

Possible to define unique alpha-numeric asset code based on following

2.1.1

Specification of equipment

Yes

2.1.2

Model number, Capacity, make

Yes

2.1.3

location of installation

Yes

2.1.4 2.2

name & code of manufacturer (vendor) Possible to define equipment asset master with following details

Yes

2.2.1

Asset code

Yes

2.2.2

Asset specifications

Yes

MOD

3RD

CST

Remark FUT

NS

Data of Work Centers SAP ERP Plant Maintenan ce Object Lists on Orders SAP ERP Plant Maintenan ce / Materials Managem ent Services & procureme nt

SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data SAP ERP Plant Maintenan ce Master Data

Annex B: Appendix 3B- Compliance Sheet

Page 93 of 89 Sr. No.

2.2.3

Requirement Description

Material codes for all movable/replaceable parts within the equipment

Compliance SUP

Yes

2.2.4

No. of replaceable / movable parts within the equipment

Yes

2.2.5

Name and code of manufacturer (vendor)

Yes

2.2.6

Spares required for the asset

Yes

2.3

Possible to interface with the material management module to map the material code with asset codes

Yes

2.4

Possible to integrate with the inventory module to find spares available for each asset

Yes

2.5

Possible to capture spares available free of cost from the manufacturer with the original equipment

Yes

2.6 2.7

Possible to integrate with the Planning and engineering software for exchange of data on equipment assets Possible to integrate with SCADA for exchange of data on equipment assets

Yes Yes

MOD

3RD

CST

Remark FUT

NS

SAP ERP Materials Managem ent Materials Master SAP ERP Plant Maintenan ce - Bill of Materials SAP ERP Materials Managem ent Materials Master SAP ERP Plant Maintenan ce - Bill of Materials SAP ERP is a fully integrated real time solution SAP ERP is a fully integrated real time solution SAP ERP Materials Managem ent / Plant Maintenan ce Bill Of Materials SAP Integratio n Kits Available with Planning & Engineeri ng Softwares SAP ERP PM - PCS Interface links SAP & SCADA for transfer of readings and informatio n across

Annex B: Appendix 3B- Compliance Sheet

Page 94 of 89 Sr. No.

Requirement Description

Compliance SUP

2.7.1

Asset code and details

Yes

2.7.2

specification of equipment

Yes

2.7.3

location of installation

Yes

2.8

Track movement of asset from one location to another

Yes

2.9

Possible to transfer the meter reading along with the asset

Yes

2.10

Possible to retain the asset health history when it is moved from one location to another

Yes

2.11 3

Possible to integrate with inventory and Finance modules to link the asset codes (definition) and value of the asset Operations management Operations budget

Yes

3.1

Possible to define budget for operating costs for each department

Yes

3.2 3.3

Possible to define the operations budget under user defined categories like maintenance, material, etc. Possible to define operations budget across dimensions like locations, zones / areas

Yes Yes

MOD

3RD

CST

Remark FUT

NS

the system SAP PMPCS Interface SAP PMPCS Interface SAP PMPCS Interface SAP ERP Plant Maintenan ce - Usage Lists SAP ERP Plant Maintenan ce Measuring Points & reading transfer SAP ERP Plant Maintenan ce Object Informatio n Lists & usage lists SAP ERP is a fully integrated real time solution

SAP operation and maintenan ce cost budgeting SAP operation and maintenan ce cost budgeting SAP operation and maintenan ce cost budgeting Also can be done by asset and

Annex B: Appendix 3B- Compliance Sheet

Page 95 of 89 Sr. No.

Requirement Description

Compliance SUP

3.4

Possible to have workflow based approval process for budget

Yes

3.5

Monitor actual expenditure vs. the budget for operating costs

Yes

MOD

3RD

CST

Remark FUT

NS

function location SAP operation and maintenan ce cost budgeting and work flow SAP operation and maintenan ce cost budgeting Support by reports and dashboard s

Emergency handling 3.6

Register a call related to an emergency with following details

3.6.1

Control room number

Yes

3.6.2

Caller details

Yes

3.6.3

Details of person receiving the call

Yes

3.6.4

Details of incident (place, time, date)

Yes

3.7

Possible to generate a unique call number for every call

Yes

3.8

Possible to forward the call details to relevant personnel

Yes

3.9 3.10

Possible to capture time taken to attend and resolve the incident Possible to capture following related to attending the incident

Yes Yes

CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service

Annex B: Appendix 3B- Compliance Sheet

Page 96 of 89 Sr. No.

Requirement Description

Compliance SUP

3.10.1

Time taken to resolve

Yes

3.10.2

Activities done

Yes

3.10.3

Personnel who attended

Yes

3.10.4

Material used

Yes

3.11 3.12

Possible to request for a breakdown maintenance in case of large breakdown Possible to monitor all the calls which remain

Yes

3.12.1

Unattended

Yes

3.12.2 3.13

Unresolved Possible to analyse the emergency calls

Yes

3.13.1

Frequently occurring emergencies

Yes

3.13.2

Zone / area where emergencies are occurring frequently

Yes

3.13.3

time / day / period during the year when emergency is occurring frequently Meter reading / recording

Yes

3.14 3.14.1

Possible to capture meter reading at consumer end with following details Meter reading value

Yes

MOD

3RD

CST

Remark FUT

NS

and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders

CRM, customer service

Annex B: Appendix 3B- Compliance Sheet

Page 97 of 89 Sr. No.

Requirement Description

Compliance SUP

3.14.2

Consumer number (CRN number)

Yes

3.14.3

Date and time of meter reading

Yes

3.15

Possible to reset the meter reading (the opening reading is different from the previous closing reading) with authority

Yes

3.16

Possible to highlight cases of exception where meter reading is possibly incorrect (based on meter reading trends)

Yes

Integration with the billing module to transfer meter reading data for billing purpose at the frequency defined in the billing module

Yes

3.17 3.18

MOD

3RD

CST

Remark FUT

NS

and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders CRM, customer service and work orders

Possible to capture meter readings with following details

3.18.1

Meter reading value

Yes

3.18.2

Date and time of meter reading Equipment monitoring

Yes

3.19

Definition of following for purpose of monitoring (by taking readings) of equipment operations

Yes

3.19.1

Equipment ID

Yes

3.19.2

Parameters (e.g. temperature, pressure, vibration, dispenser internal / external) to be monitored

Yes

CRM, customer service and work orders CRM, customer service and work orders SAP ERP Plant Maintenan ce Condition Monitorin g SAP ERP Plant Maintenan ce Condition Monitorin g SAP ERP Plant Maintenan ce Measuring Points / Parameter s

Annex B: Appendix 3B- Compliance Sheet

Page 98 of 89 Sr. No.

Requirement Description

Compliance SUP

3.19.3

Frequency of monitoring

Yes

3.20

Possible to record the equipment monitoring parameters (operations readings) for the defined frequency for the equipment

Yes

3.21

Possible to interface with SCADA system (which captures real time data of equipment) to get the operations readings

Yes

3.22

Ability to undertake trend analysis for observing any abnormality

Yes

3.23

Ability to use the monitoring data (readings and trend) to provide inputs to following

3.23.1

Equipment health history

Yes

3.23.2

Maintenance requirements for the equipment Disconnection

Yes

3.24

Possible to integrate with the CRM / Billing module to consolidate requests related to disconnection

Yes

3.25

Possible to prepare a schedule for disconnection and approve the same through a workflow

Yes

3.26

Possible to input following where disconnection is achieved

Yes

3.26.1 3.26.2

CRN number of disconnection Date of disconnection

Yes Yes

MOD

3RD

CST

Remark FUT

NS

SAP ERP Plant Maintenan ce Schedule of Condition Monitorin g Plans SAP ERP Plant Maintenan ce Measurem ent Reading Lists SAP ERP PM - PCS Interface links SAP & SCADA for transfer of readings and informatio n across the system SAP ERP Plant Maintenan ce Measurem ent Point Trend graphs

SAP ERP Plant Maintenan ce SAP ERP Plant Maintenan ce CRM and Billing CRM and Billing Using workflow CRM and Billing CRM and Billing CRM and

Annex B: Appendix 3B- Compliance Sheet

Page 99 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

3.26.3

Agency / Personnel involved in disconnection

Yes

3.26.4

Closing reading

Yes

3.26.5

Reason for disconnection

Yes

3.26.6

Disconnection charges

Yes

Billing CRM and Billing CRM and Billing CRM and Billing CRM and Billing

3.27

Possible to capture type of disconnection done (permanent, temporary, non-payment)

Yes

CRM and Billing

Yes

CRM and Billing

Yes

CRM and Billing CRM and Billing

3.28

Possible to update the Billing module with cases where disconnection is achieved (to stop billing for such consumers) Reconnection

3.29

Possible to integrate with the CRM /Billing module to consolidate requests related to Reconnection

3.30 3.31

Possible to prepare a schedule for Reconnection and approve the same through a workflow Possible to input following where Reconnection is achieved

Yes

3.31.1

CRN number of Reconnection

Yes

3.31.2

Date of Reconnection

Yes

3.31.3

Personnel involved in Reconnection

Yes

Opening reading

Yes

CRM and Billing CRM and Billing CRM and Billing CRM and Billing CRM and Billing

3.31.4 3.31.5

Reason for Reconnection and request received from which source

3.32

Possible to capture type Reconnection done (permanent, temporary, Nonpayment)

Yes

3.33

Possible to update the Billing module with cases where Reconnection is achieved (to start billing for such consumers)

Yes

3.34

Possible to capture the charges for Reconnection Meter Damage / Faulty

Yes

CRM and Billing CRM and Billing

3.35

Capturing meter faulty

Yes

CRM and Billing

3.36

Capturing meter damaged by consumer and recover charges from consumers

Yes

3.37

Replacement of new Meter and reasons thereof Patrolling

Yes

3.38

Possible to plan a route for patrolling at points like consumer site, DRS, etc.

Yes

3.39

Possible to allocate staff for executing the patrolling task

Yes

3.40

Recording findings of each staff on completion of patrolling

Yes

3.41

Possible to intimate relevant personnel to resolve issues identified during patrolling

Yes

3.42

Possible to track actions taken for the issues

Yes

3.43

Possible to list issues which are unresolved Audit

Yes

CRM and Billing CRM and Billing CRM and Billing Including GIS CRM and Billing CRM and Billing CRM and Billing CRM and Billing CRM and Billing

Annex B: Appendix 3B- Compliance Sheet

Page 100 of 89 Sr. No. 3.44

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

Possible to define the audit scope and plan

3.44.1

Date of audit

Yes

3.44.2

Personnel involved

Yes

3.44.3

Outlet to be audited

Yes

3.45

Report on audit undertaken

Yes

3.45.1

Personnel involved

Yes

3.45.2

Findings

Yes

3.45.3

Actions to be taken for resolution

Yes

3.45.4

Responsible personnel for actions

Yes

3.46

Alert the relevant personnel about the tasks to be undertaken for resolution of issue identified through audit

Yes

3.47 4

Tracing the action taken on findings by Audit team Maintenance planning

4.1

Possible to define budgets for maintenance with break up in terms of following

Yes

4.1.1

Material cost / consumables

Yes

4.1.2

Contractors' cost

Yes

4.1.3

Spares required for maintenance

Yes

4.1.4 4.2

Other costs Possible to define separate maintenance budget for categories of maintenance and arrive at an aggregate budget

Yes Yes

CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking CRM and Audit tracking

SAP ERP Maintenan ce Cost Budgeting / SAP Financials SAP ERP Maintenan ce Cost Budgeting / SAP Financials SAP ERP Maintenan ce Cost Budgeting / SAP Financials SAP ERP Maintenan ce Cost Budgeting / SAP Financials SAP ERP Maintenan

Annex B: Appendix 3B- Compliance Sheet

Page 101 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

ce Cost Budgeting / SAP Financials 4.3

Preparation of maintenance schedule based on following

4.3.1

Maintenance schedule recommended by the manufacturer

Yes

4.3.2

History of equipment health

Yes

4.3.3

Maintenance activities which are pending / not completed

Yes

4.3.4

Years since commissioning was done (for domestic consumers)

Yes

4.4

Possible to prepare maintenance plan annually with details available for monthly and weekly plan. The maintenance plan should cover following

4.4.1

Details of maintenance activity to be carried out

Yes

4.4.2 4.4.3

Involved personnel / Department / Contractor Date of maintenance

Yes Yes

SAP ERP Plant Maintenan ce Maintenan ce Planning & Schedulin g SAP ERP Plant Maintenan ce Object Informatio n List & Informatio n Systems SAP ERP Plant Maintenan ce - Work Order List Functions SAP ERP Plant Maintenan ce Informatio n Systems

SAP ERP Plant Maintenan ce Maintenan ce Planning & Schedulin g SAP ERP Plant Maintenan ce Maintenan ce Planning & Schedulin g SAP ERP Plant

Annex B: Appendix 3B- Compliance Sheet

Page 102 of 89 Sr. No.

Requirement Description

4.4.4

Estimated time required for maintenance activity

4.5

Possible to prepare a work order for maintenance identifying following

Compliance SUP

Yes

4.5.1

Personnel to undertake maintenance job

Yes

4.5.2

Equipment / areas to be covered for maintenance

Yes

4.5.3

Spares required for maintenance

Yes

4.5.4

Date and time of maintenance

Yes

4.5.6 5 5.1

All approvals required for carrying out maintenance Maintenance execution Possible to electronically intimate different departments for taking clearances before undertaking maintenance job

Yes Yes

MOD

3RD

CST

Remark FUT

NS

Maintenan ce Maintenan ce Planning & Schedulin g SAP ERP Plant Maintenan ce Maintenan ce Planning & Schedulin g

SAP ERP Plant Maintenan ce - Work Order Managem ent SAP ERP Plant Maintenan ce - Work Order Managem ent SAP ERP Plant Maintenan ce - Work Order Managem ent SAP ERP Plant Maintenan ce - Work Order Managem ent SAP ERP Plant Maintenan ce - Work Order Managem ent & Work Flows SAP ERP Plant Maintenan

Annex B: Appendix 3B- Compliance Sheet

Page 103 of 89 Sr. No.

Requirement Description

Compliance SUP

5.2

Intimating FEWA personnel and other agencies before undertaking maintenance job

Yes

5.3

Possible to Tag an equipment when taken for maintenance

Yes

5.4

Possible to input a report on maintenance

Yes

5.4.1

Equipment / Consumer premise of which / location

Yes

5.4.2

Material used

Yes

5.4.3

Activity summary

Yes

5.4.4

Time taken

Yes

5.4.5 5.5 5.5.1

Personnel / Contractor involved in maintenance activities For breakdown maintenance, following should be supported Cause of breakdown

Yes Yes

MOD

3RD

CST

Remark FUT

NS

ce & Work Flows SAP ERP Plant Maintenan ce & Work Flows SAP Work Clearance Managem ent SAP ERP Plant Maintenan ce Notificatio ns SAP ERP Plant Maintenan ce Work Order Managem ent SAP ERP Plant Maintenan ce Work Order Managem ent SAP ERP Plant Maintenan ce Work Order Managem ent SAP ERP Plant Maintenan ce Confirmat ions of Work Orders SAP ERP Plant Maintenan ce Work Order Managem ent Capacities SAP ERP Plant Maintenan

Annex B: Appendix 3B- Compliance Sheet

Page 104 of 89 Sr. No.

Requirement Description

Compliance SUP

5.5.2

Damage caused by breakdown

Yes

5.6

In case of calibration as a maintenance activity, updating the calibration details for the instrument

Yes

5.7

In case of change of meter as a part of maintenance activity, the Billing department should be alerted about the same

Yes

5.8

Update the equipment history with maintenance activities

Yes

5.9

Capture extent of services provided by each contractor / vendor during a user defined period

5.9.1

Man-hours

Yes

5.9.2

Number of activities carried out

Yes

MOD

3RD

CST

Remark FUT

NS

ce Notificatio ns SAP ERP Plant Maintenan ce Notificatio ns SAP ERP Plant Maintenan ce Planned Maintenan ce / Measuring Points SAP ERP Plant Maintenan ce Work Order Managem ent & Work flows SAP ERP Plant Maintenan ce Informatio n Systems , Object Informatio n Lists & Usage Lists

SAP ERP Plant Maintenan ce - Work Order Managem ent & Service Entry Sheets SAP ERP Plant Maintenan ce - Work Order Managem ent & Service Entry Sheets

Annex B: Appendix 3B- Compliance Sheet

Page 105 of 89 Sr. No.

Requirement Description

Compliance SUP

5.9.3

Equipment (ID, specifications & location) on which maintenance was done

Yes

5.10

Possible to update the annual / monthly / weekly maintenance plan with details of maintenance completed

Yes

5.11

Possible to integrate with the Contracts module to define mechanism for payment to contractors

5.11.1

Based on man-hour rate

Yes

5.11.2

Fixed charges monthly / annual

Yes

5.11.3

Free services as a part of AMC for first year

Yes

5.12

Calculate costs incurred for maintenance with break up in terms of following

5.12.1 5.12.2

material cost contractors' cost

Yes Yes

MOD

3RD

CST

Remark FUT

NS

SAP ERP Plant Maintenan ce - Work Order Managem ent SAP ERP Plant Maintenan ce Maintenan ce planning & execution

SAP ERP Plant Maintenan ce / Materials Managem ent Service Contracts SAP ERP Plant Maintenan ce / Materials Managem ent Service Contracts SAP ERP Plant Maintenan ce / Materials Managem ent Service Contracts

SAP ERP Plant Maintenan ce Work Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Work

Annex B: Appendix 3B- Compliance Sheet

Page 106 of 89 Sr. No.

Requirement Description

Compliance SUP

5.12.3

other costs

Yes

5.12.4

Spares required for maintenance

Yes

5.12.5

cost incurred at which cost centre

Yes

5.12.6

cost incurred at which location

Yes

5.13 5.14

Possible to monitor budgeted vs actual cost incurred in maintenance for a user defined period Possible to generate a report on frequently occurring breakdown for each asset

Yes Yes

MOD

3RD

CST

Remark FUT

NS

Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Work Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Work Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Work Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Work Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Work Order Managem ent & Informatio n System Reports SAP ERP Plant Maintenan ce Informatio

Annex B: Appendix 3B- Compliance Sheet

Page 107 of 89 Sr. No.

Requirement Description

Compliance SUP

MOD

3RD

CST

Remark FUT

NS

n System & List Reports 6

6.1 6.2

Equipment health management

Possible to define parameters (e.g. vibrations, temperature, running hours, failures, etc. which are monitored) for each asset / equipment that define its health Possible to analyze the health data to identify following

Yes

6.2.1

Mean time before failure

Yes

6.2.2

Average running hours per period (day, month)

Yes

6.2.3

Average hours of operations before maintenance required

Yes

6.3 6.4

Possible to maintain historical health data for equipment for user defined time period Possible to summaries the health data by

Yes

6.4.1

Manufacturer

Yes

6.4.2

Location

Yes

SAP ERP Plant Maintenan ce Measuring Points & Condition ed Based Maintenan ce Planning SAP ERP Plant Maintenan ce Informatio n System SAP ERP Plant Maintenan ce Informatio n System SAP ERP Plant Maintenan ce Informatio n System SAP ERP Plant Maintenan ce Informatio n System & Usage Lists SAP ERP Plant Maintenan ce / Business Intelligenc e Reports SAP ERP Plant Maintenan ce / Business Intelligenc e Reports

Annex B: Appendix 3B- Compliance Sheet

Page 108 of 89 1.4.6

Performance Management (Business Intelligence)

Sr. No.

Requirement Description

Compliance SUP

1

3RD

CST

FUT

NS

Reports and Queries

1.1

Real-time reports accessing multiple data stores

Yes

1.2

Web-queries

Yes

1.3

Ad-hoc queries

Yes

1.4

Interactive data exploration with analytics

Yes

1.5

Integration of queries/reports with Desktop tools such as Excel

Yes

1.6

Support tree-style structure to logically organize data

Yes

1.7

Combine multiple reports into a single report/dashboard

Yes

Supports graphical interface to avoid complex languages Report Accessibility Including Real time reports access operational data stores Generates reports automatically Web query Ad-hoc queries Column-based indexing for faster data retrieving Navigates all connected relational databases Interactive data exploration with analytics Desktop interface to advanced analytics Multiple data sources and platforms Accesses delimited ASCII files and Fixed ASCII Schedules information alerts based on specified conditions Real time access to operational data Report drill through from OLAP cubes Embedded production report writers Batch production and distribution of reports Combines multiple reports into a single "report dashboard" Exports reports to other formats ( please define export format ) Integrates with 3rd Party HTML development tools Graphical interface avoids complex languages, such as C or Java

Yes

1.8 1.9 1.9.1 1.9.2 1.9.3 1.9.4 1.9.5 1.9.6 1.9.7 1.9.8 1.9.9 1.9.10 1.9.11 1.9.12 1.9.13 1.9.14 1.9.15 1.9.16 1.9.17 1.9.18 1.9.19

MOD

Remark

SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e

Annex B: Appendix 3B- Compliance Sheet

Page 109 of 89 Compliance Sr. No.

SUP

2

2.1

Yes

2.1.1

Regression algorithm

Yes

2.1.2

Scoring

Yes

2.1.3

Classification

Yes

2.1.4

Groupings

Yes

2.1.5

Clustering

Yes

2.1.6 2.1.7

Variable contribution Time series analyses predicts patterns and trends in data over time Association rules identifies patterns in transaction data for describing which events frequently occur together Consistent coder automatically fills in missing values & detects out of range data Sequence coder aggregates events into a series of transitions Event log aggregates events into periods of time Segmentation

Yes

2.1.9 2.1.10 2.1.11 2.1.12

Yes 2.2

Supports time-series analysis patterns and plots trends over time Yes

2.3 3 3.1

Yes

3.2

Supports Forecasting Workflow Represents complex processes that are comprised of sub-processes &activities Processes can be defined or mapped into the system

3.3

Graphically portrays business processes and activities

Yes

3.4

Shares activities and sub-processes between processes

Yes

3.5

Reuses an activity already defined in the process without having to define it again; Defines absolute or relative dates when activities or work-items must be completed

Yes

3.6

MOD

3RD

CST

FUT

NS

Analytics

Supports predictive modeling techniques such as:

2.1.8

Remark

Requirement Description

Yes

Yes

SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e

SAPBusiness Warehous e SAPBusiness Warehous e SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver

Annex B: Appendix 3B- Compliance Sheet

Page 110 of 89 Compliance Sr. No.

SUP

3.7 3.8

Defines absolute or relative dates when activities or work-items must be completed Schedules tasks to start automatically at a specified time

Yes

3.9

Terminates a workflow in a process, based on user privileges security

Yes

3.10

Suspends or resumes a workflow in process & specifies inactive periods

Yes

3.11

Processes to have multiple points and end at any end point

Yes

3.12

Displays decision logic using text, the branch concept, or a decision icon on the process map

Yes

3.13

Specifies note (activity) properties at design time

Yes

3.14

Displays the path traveled between activities (color change)

Yes

3.15

Supplies activity and task names

Yes

3.16

Views overall status and display active node (activity)

Yes

3.17

Support definition of Resources & Roles

Yes

3.18

Support definition of Rules and Routing

Yes

3.19

Support definition of Queues & Work Lists

Yes

3.20

Support definition of Triggers

Yes

3.21

Supports scheduling

Yes

4 4.1

Data Integration Has defined tools for ETL from transaction data bases

Yes

4.2

Has built-in tools to facilitate data cleansing and transformation

Yes

4.3

Supports Data Matching and Consolidation

Yes

4.4

Supports definition of metadata

Yes

4.5

Concurrent processing of multiple source data streams, without writing procedures Event-based change data capture Bulk data movement Explores raw data in disparate systems to uncover relationships and discrepancies between and within data sets Components that can be used to work around the file size or platform limitations Updates data capture and loads only changed records into the data source

4.6 4.7 4.8 4.9 4.10

Remark

Requirement Description MOD

3RD

CST

FUT

NS

SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPNetweaver SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e SAPBusiness Warehous e

Annex B: Appendix 3B- Compliance Sheet

Page 111 of 89 Compliance Sr. No.

SUP

4.11 4.12

1.4.7

MOD

3RD

CST

FUT

NS

Automatically generates data extract programs Automatic updates for slowly changing dimensions

Technical Requirements

Sr. No.

Compliance

Requirement Description SUP

1 1.1 1.1.1 1.1.2 1.1.3

Remark

Requirement Description

Solution architecture and integration Should support application deployment involving Centralized architecture Decentralized architecture Distribution architecture

MOD

3RD

CST

Remark FUT

NS

Yes Yes Yes Can be deployed this way but subject to design and cost constraints .

1.2

Should support deploying application components at local locations to continue operations in case of WAN link failure

Yes

1.3

Should be possible to access application from remote location (Remote office , Remote users , please explain )

Yes

1.4

Should support storing / replicating data related to critical functions at the local locations to support functioning at branches in case of WAN link failure

Yes

Should be able to integrate with BW, DSS and EIS s/w without conversion of Data

Yes

Browser, Mobile. Can be deployed this way but subject to design and cost constraints Sap is fully integrated.

Should support workflow based routing of transactions according to userdefined rules. Provide details about functionality provided inbuilt or through external package / interface

Yes

Fully integrated.

Support for data exchange between modules using Messaging System calls Application function calls

Yes Yes Yes

1.5 1.6

1.7 1.7.1 1.7.2 1.7.3

1.7.4 1.8 1.8.1 1.8.2

Any other specify

Yes

Support selective export / import of data in the following formats:

ASCII Text

Yes Yes

Standard we services functionali ty based on XML, prebuilt connectors .

Annex B: Appendix 3B- Compliance Sheet

Page 112 of 89 Sr. No.

Compliance

Requirement Description SUP

1.8.3 1.8.4 1.8.5

Formatted from Microsoft Excel and DAT files Unformatted

1.9

Availability of any of the following for interfaces for external data exchange

1.9.1 1.9.2 1.9.3 1.9.4 1.10

APIs MOMs RPC Any other please specify In case of any of the message based mechanisms, does the system integrate with:

Yes Yes Yes

1.10.1

MQ Series

Yes

1.10.2

MS MQ

Yes

1.10.3

Tibco Active Enterprise

Yes

1.10.4 1.11

Others (Please Specify) Should provide "n" levels in workflow based routing of transactions for different functions

1.12

Should be able to integration / interface with other packages without duplication of Data

1.13 1.14 1.15

Should support messaging solutions with integration with MS Exchange Server and Contact Centre (SMS, fax, etc) Availability of source code with the application Possible to integrate with following other software’s

Yes Yes Yes

MOD

3RD

CST

Remark FUT

NS

But conversio n to internal formats needed.

Using web Services Standards. Some configurat ion will be needed. Using web Services Standards. Some configurat ion will be needed. Using web Services Standards. Some configurat ion will be needed.

Yes

NetWeave r BPM, NetWeave r PI

Yes

NetWeave r PI

Yes Yes

1.15.1

SCADA

Yes

1.15.2

GIS

Yes

1.15.3 1.15.4 1.15.5

POS system External databases (e.g. oil prices, company-wise car sales) Scanned image storage and retrieval applications

Yes Yes

NetWeave r PI

LifeCycle Data Managem ent NetWeave r PI NetWeave r PI NetWeave

Annex B: Appendix 3B- Compliance Sheet

Page 113 of 89 Sr. No.

Compliance

Requirement Description SUP

1.15.6

AutoCAD

Yes

1.15.7

Mapinfo

Yes

1.15.8

MS project / Primavera

Yes

1.15.9a

Contact Center

Yes

1.15.9b

DMS

Yes

1.15.9c

Yes

1.16

MS Office Possible to integrate with FEWA website to disseminate information to customers as :

1.16.1

Bill paid / pending

Yes

1.16.2 2

Consumption of gas Technology platform and OS capabilities- Web Based Solution

Yes

2.1

Should utilize Multi processor / Parallel Processing / Multi-Threading of the OS

2.2 2.3 2.4

Should provide for Automated Backup to off-peak hours / Online Backups Provide menu-driven GUI front-end for OS Support load balancing between

MOD

3RD

CST

Remark FUT

NS

r KM LifeCycle Data Managem ent Using web Services Standards. Some configurat ion will be needed. LifeCycle Data Managem ent NetWeave r PI LifeCycle Data Managem ent, KM LifeCycle Data Managem ent, KM, DUET

Yes

Yes

Yes Yes

Enterprise Portal Enterprise Portal SAP NetWeave r Platform Offline and Online backups strategies can be applied SAP GUI

AS.jpg

2.4.1

Application server

Yes

2.4.2

Database server

Yes

2.5 2.6 2.7

Should enable automatic scheduling of job to reduce load during peak load hours Should support Automated tasks as part of job scheduler Provide all backup and restore/recovery Capabilities (for losses,

Yes Yes Yes

Part of architectur e Part of architectur e

Annex B: Appendix 3B- Compliance Sheet

Page 114 of 89 Sr. No.

Compliance

Requirement Description SUP

MOD

3RD

CST

Remark FUT

NS

corruption/damage … etc) as well as the ability to flashback to previous timestamp or before drop.

2.8 3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 3.1.9 3.1.10

3.1.11 3.1.12 3.1.13

3.1.14 3.2 3.2.1

Please provide details of OS supported by the applications Security Should provide authentication at the following levels: User level Application level Menu level File level Record level Field level Operation level (add, change, delete) Terminal System Module Master File

Time of day and day Screen or field Function performed

Authority levels based on amounts Support facility to allow the defining of the password construct Number of characters and the complex password ( explain)

Yes

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Yes Yes Yes Yes

Yes as part of standard workflows .

Yes

Yes 3.3

Time of day is stamped on transactio n.

Rules can be defined and enforced by the system.

Support defining user activity (on transactions) access to be based on the following and not limited to:

3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6

Input Hold Modify Delete Authorize Reverse

Yes Yes Yes Yes Yes Yes

3.3.7

View/Display

Yes

Reverse is only by adding a cancelling transactio n.

Annex B: Appendix 3B- Compliance Sheet

Page 115 of 89 Sr. No.

Compliance

Requirement Description SUP

3.3.8 3.4

Print Support definition of group passwords (e.g. groups – system administrator, Projects, Contractor, etc) with which certain functions / job descriptions are associated

3.5

Support storage of password, in the database, in encrypted form

Yes Yes

3.6

Possible to define external users (from outside company) with access rights and authentication as described above

Yes

3.7

System should support authentication from local server in case of WAN failure and local application access. The access rights defined centrally should also be valid in case of local operations

3.8 3.9

Provide ability to lock entry screen after a user-specified number of incorrect password attempts Should log all update transactions in a secure audit trail file

3.10 3.11

Should provide for required changes to user passwords based on a userspecified period of time Report attempts of unauthorized system access or use

3.12 3.13

Provide the ability to define an access category relating to groups of users (e.g., members of a department or management class). Provide for data encryption when transmitted over network

3.14

Should provide a facility to automatically logout the user if the system is inactive for more than a specified period of time The system should support automatic logout in case of disconnection of user from the application server

Yes

3.15

The system should support definition of access rights for online available reports Transaction Logging and Recovery

Yes

3.16 4

MOD

3RD

CST

Remark FUT

NS

Yes

Yes Yes Yes Yes Yes Yes Yes

4.1

Provide clear audit trails of all transactions from source data entry through summarization at higher levels or integration with other application systems. Audit trail information should include before and after images, and the date, time and identification of the person making the entry.

Yes

4.2

Audit trail should highlight the entries made by accessing the system through dial-in or through Internet

Yes

4.3

Provide option to enable/disable audit trail of any specified transaction with all the above details (before and after images, date, time, person etc.)

Yes

4.4

Provide on-line inquiry to both status information and detail transactions

Yes

4.5

System should support switching to alternate/standby server to provide uninterrupted availability

Yes

4.6

Branch accessing applications / data from central server should provide and indication of WAN link availability status

4.7 4.8

The system should maintain transaction integrity in case of WAN failure while the transaction is under execution at the accessing branch Provide transaction logs to assist in recovery of data or files

All state changes in data a fully logged with all data required here. Trigger is data change regardless of access path used.

Network design status.

Yes Yes

Sap supports

Annex B: Appendix 3B- Compliance Sheet

Page 116 of 89 Sr. No.

Compliance

Requirement Description SUP

MOD

3RD

CST

Remark FUT

NS

full rollback capability. Incomplet e transactio ns are automatic ally rolled back to the previous state.

4.9

Provide on-line access to audit trail information including terminal operator ID, time, date, revised amount, and before & after update and transaction types results (insert, updates, delete etc)

4.10

Allow validation rules to be changed easily by the user without program changes

4.11

The System should accept/reject transactions on the basis of master file values (e.g.. Account Code, Project code etc.).

4.12 4.13

Easily correct data entry errors within a batch The system should support recovery of application software in case of damage

Yes

Yes

Yes

Yes Yes

Business validation rules are not usually put in control of users. Such changes require a formal approval process, testing and promotion as part of the system control SAP does this in real time to avoid later issues. Only fully validated transactio ns are entered into the system. Sap uses very little batch processing . Where it is done, an error list is generated for repair. Full recovery back to last

Annex B: Appendix 3B- Compliance Sheet

Page 117 of 89 Sr. No.

Compliance

Requirement Description SUP

MOD

3RD

CST

Remark FUT

NS

complete transactio n is supported. 5

5.1 5.2

5.3 5.4

5.5 5.6

Data storage

Provide details of databases supported by the system including detailed database clustering/mirroring/replication, please specify Operating system supported by Database server Unix, Windows, Linux , please specify

Monitor on-line file capacity control for master and transaction files. The DBA to be notified when a file is approaching capacity .

Should be supported on ODBC compliant Databases

Should be possible to support pooling of multiple database connections when the load is high Automatic expansion of file when approaching limits of usage

Yes Yes

Yes Yes

Yes Yes

SAP supports all common databases including MS SQL server, MaxDB, Oracle. SAP supports mirroring, clustering and replication but these are a factor of server and network design. All supported. Sap includes (at no cost) the Solution manager tool which allows online monitorin g of all aspects of system operation from both an applicatio n and database perspectiv e. Sap supports load balancing to ensure response times.

Annex B: Appendix 3B- Compliance Sheet

Page 118 of 89 Sr. No.

Compliance

Requirement Description SUP

5.7

Provide multi-user operations down to the program level so that many people may access the same files and programs at the same time

Yes

5.8 5.9

Allow seamless data exchange and automatic update of data within the subsystems of the same package Should provide a comprehensive data dictionary

Yes Yes

5.10 6

Should provide for online data access for a period of 3 financial years and up to 10 years of historical data in some summarized format. Provide details. Edits and Controls

6.1 6.2

All sub-modules of the package should use the same master files online Maintain all master files, tables and descriptive transaction fields on-line

6.3

Provide report accuracy such that all reports provide summary totals regardless of rounding factors

6.4 6.5

Should provide for a consistent screen format across all modules Should provide for changing field labels to suit FEWA's terminology

6.6 6.7

Should provide for templates for rapid data entry and validations.

7 7.1

Reporting and Query Route output to printer, file or workstations

Yes

MOD

3RD

CST

Remark FUT

NS

SAP supports file locking. If a user has a file locked for editing other users are read only till it is checked in. This is done to include integrity. SAp only delivers fully integrated processes. Retention and offline backup strategy is user defined.

Yes

Yes

All transactio ns are done in real-time.

Yes Yes Yes Yes

Should provide for replication of transactions for reduced data entry

? Yes

Meaning is unclear. More details needed. Fast data entry is provided where appropriat e as is the ability to batch load.

Annex B: Appendix 3B- Compliance Sheet

Page 119 of 89 Sr. No.

Compliance

Requirement Description SUP

7.2

Transmit reports to multiple locations

7.3 7.3.1 7.3.2

Automate the report distribution process including: Varying the number of copies of each report Produce the report in report distribution sequence, rather than report number sequence

7.3.3 7.4 7.5

Labeling of reports to specific recipients Ability to define and store report formats separately for each department Possible to define priorities for handling queries depending on the user / department / designation, etc.

MOD

Support report distribution via Fax, e-mail and Popup screen Print selected reports at user-specified printer locations

7.9

Allow selective report information to be sent to a screen instead of being directed to a printer

Yes

7.10

Perform screen prints on request

Yes

7.11

Ability to generate Static and Dynamic and all BI reports.

7.12

Ability to generate the reports in different File format (PDF, MS Word, MS Excel, Text, HTML …. etc). Productivity Tools Provide easy to use on-line screen generator capability to allow user to design or modify screen display formats.

Provision of self-learning Tutorials for each functional areas for users to teach themselves operation of ERP

9 9.1

User Interface Should provide intuitive and easy to use interface (GUI)

Meaning unclear.

?

7.7 7.8

8.3

NS

Yes Yes Yes

Should be possible to define the frequency at which reports need to be prepared and distributed to different pre-defined users

Provide user--defined on-line HELP screen for field description, policies or procedures related to specific screens

FUT

Yes

7.6

8.2

CST

Also includes broadcast control tools.

Yes

8 8.1

3RD

Remark

Yes Yes Yes

Yes Yes

Yes

Yes

Yes Yes

All screens Customers can create customize d help screens based on SAP provided data. SAP provides a third party product (RWD ) that allows the customizat ion of online tutorials linked to the SAP help system. SAP GUI, Portal, Adobe Interactive Forms, Mobile,

Annex B: Appendix 3B- Compliance Sheet

Page 120 of 89 Sr. No.

Compliance

Requirement Description SUP

MOD

3RD

CST

Remark FUT

NS

DUET 9.2

Workstation OS for installing the front-end systems (clients)

9.2.1

Windows 98, 2000,XP and Vista

9.2.2 9.3

Linux Allow the user to move from screen to screen without moving through menu hierarchies and/or without signing off one application to sign on to another Interrupt current screen to perform function on another application's screen and to return to interrupted screen with all original screen data intact

Yes

Yes

9.4 9.5 9.5

Ability to provide single sign-on Should support access to all modules, functions under single log-in. In case there are more than one log-ins required, provide details

Yes Yes Yes Yes Yes

9.6 9.6.1 9.6.2 9.6.3 9.6.4

System should allow defining fields as Mandatory Non-mandatory Highlighting of mandatory fields Default fields

Yes Yes Yes Yes

9.7 9.7.1 9.7.2 9.7.3 9.7.4

Application should support defining additional fields based on and not limited to Text Number Date Character

Yes Yes Yes Yes

9.8

Possible to populate default values for fields on screen (e.g. today's date) to reduce level of data entry

Yes

9.9 10 10.1

The system should support generating search on fields providing results relating to every area (sales, marketing) within the ERP application Report Writer Create custom, ad hoc reports without systems or application programming involvement functions

Windows 98 is only supported for SAP Frontends until 01/15/200 4. Microsoft limited the product support for Windows 98 to this date

Yes Yes

SAP BW

10.11 10.2 10.3

Ability to create dynamic reports (drill downs, dashboards with KPIs etc) Specify contents and layout of user-specified reports Prompt the user for data and report specifications at the terminal interactively

Yes Yes Yes

SAP BW SAP BW SAP BW

10.4

Provide access to master, summary and detail records through interactive inquiry

Yes

SAP BW

10.5

Download information from any transaction and summary file to standard PC software formats such as MS-OFFICE suite of products

Yes

SAP BW

Annex B: Appendix 3B- Compliance Sheet

Page 121 of 89 Sr. No.

Compliance

Requirement Description SUP

MOD

3RD

CST

Remark FUT

NS

10.6

Access external files (of other third party applications not included in this procurement) for data to be included in reports

Yes

SAP BW

10.7

The application should have in-built report writer. Mention if external report writer tools is provided.

Yes

SAP BW

10.8 10.8.1 10.8.2 10.9 10.10

Process complex selection criteria utilizing: Operators (=, ≠,, from-to, and not from-to, AND, OR ) Multiple data files across system boundaries Store report layouts in user libraries for display at any time Include "report writer" reports in standard report printing menus and inbatch jobs

Yes Yes Yes Yes Yes

SAP BW SAP BW SAP BW SAP BW SAP BW

10.11

Copy standard reports over to user libraries and make specified changes to them without altering the original report.

Yes

SAP BW

10.12 10.12.1 10.12.2 10.12.3 10.12.4 10.12.5 10.12.6 10.12.7 10.12.8 10.12.9 10.13

Design a report based on the following user-defined criteria: Selected data elements Sort sequence Mathematical functions (calculations) Time interval Print formats, Column headings Subtotals/totals Grouping functions Retention of prior column values Multiple files accessed Access any data elements and files (permanent or temporary) within the system

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

SAP BW SAP BW SAP BW SAP BW SAP BW SAP BW SAP BW SAP BW SAP BW SAP BW

10.14 10.14.1 10.14.2 10.14.3 10.15

It should be possible to attach following to a report Charts Custom defined logos Graphic pictures Provide access control/security that limits a specific User ID from accessing:

Yes Yes Yes

SAP BW SAP BW SAP BW

10.15.1 10.15.2 10.15.3 10.15.4 10.15.5 10.16

Report writer system Specific databases Specific data files/records Specific data fields Database update capability

Yes Yes Yes Yes Yes Yes

SAP BW SAP BW SAP BW SAP BW SAP BW SAP BW

Yes

SAP BW

10.17

Create report writer programs using "English" descriptions for data elements rather than specifying the exact file data element name Calculate and total columns and rows of data for which user can specify subtotals or a subtotal on multiple levels or specific level

10.18

Allow partial fields (e.g., the first two digits of field) to be used as selection criteria

Yes

SAP BW

10.19

Perform rounding of amount fields based on user defined rules

Yes

SAP BW

Annex B: Appendix 3B- Compliance Sheet

Page 122 of 89

2

System Installation

2.1

Installation Services

Please provide details of the system installation services offered in this section: 1

Deployment Architecture - Please detail below the overall system (applications and technology) deployment architecture for installing the proposed applications for FEWA, considering that FEWA intends to have four environments viz: Sand-Box, Development, Test and Production along with a Disaster Recovery Site. _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

2

Installation Plan - Please provide below a detailed plan (module wise and the plan must show sequence of events of the integration process between deferent modules and including timelines, resources, pre-requisites, etc.) for installation of the proposed applications. The Plan should clearly indicate the roles of the Product Vendor, bidder, and FEWA IT staff. _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

3

Installation Testing - Please provide below detailed testing plan on how the installed system will be tested to ensure a successful installation. Anand to add Please

4

Post-install management - Please provide details of how the tested installation will be managed for subsequent implementation activities. Anand to add please

2.2

CVs of proposed team members for System Installation

For each proposed resource, please provide a detailed CV in the following format: FORMAT OF CURRICULUM VITAE (CV) FOR PROPOSED KEY STAFF Proposed Position: Name of Firm: Name of Staff: Profession: Date of Birth: Years with Firm/Entity: Members Bidder in Professional Societies: Detailed Tasks Assigned:

Key Qualifications:

Annex B: Appendix 3B- Compliance Sheet

Page 123 of 89 [Give an outline of staff member’s experience and training most pertinent to tasks on assignment. Describe degree of responsibility held by staff member on relevant previous assignments and give dates and locations. Use about half a page.] Education: [Summarize college/university and other specialized education of staff member, give names of schools, dates attended, and degrees obtained. Use about one quarter of a page.] Employment Record: [Starting with present position, list in reverse order every employment held. List all positions held by staff member since graduation, giving dates, names of employment organizations, titles of positions held, and locations of assignments. For experience in last ten years, also give types of activities performed and client references, where appropriate. Use about two pages.] Languages: [For each language indicate proficiency: excellent, good, fair or poor in speaking, reading and writing.]

Certification: I, the undersigned, certify that to the best of my knowledge and belief, these data correctly describe me, my qualifications, and my experience. I also certify that I have only given permission for my CV to be included in the Bid submitted by [Fill in name of Bidder here.] Date: [Signature of staff member and authorized representative of the firm] Full name of staff member: Full name of authorized representative:

Day/Month/Year

Annex B: Appendix 3B- Compliance Sheet

Page 124 of 89

3

System Implementation

3.1

Implementation Approach

1

Provide the Project plan with details of phases (e.g. To-Be Process mapping, design, solution setup, customisation, configuration, training, user testing. etc) of project. Provide the location plan for all the project activities (i.e. which activities will be carried out where – Project office location, FEWA site, VENDOR training centre, Vendors Development centre, etc.).

R

Wipro shall implement the Solution in a Phased Manner. There will be Four Waves in the implementation. Each wave has the following Milestones: Business Blueprint. Realization Final Preparation & Go Live. The details are provided in the “Technical Proposal” Document which is given as an appendix to this document.

1a

Please provide details of the Application Configuration Plan

R

Since Wipro is proposing a Phased approach there will be Requirements Gathering stage (Business Blueprint) in each Wave. Post the Business Blueprint is Signedoff, the Configuration and Development shall start. The Detailed plan for the same will be provided during the Project Preparation Phase.

2

Provide details of the infrastructure Set-up (e.g. servers, network, software, etc.) proposed for configuration, customization and testing of the ERP application during implementation. Provide details of specific tools that will be used and made available by BIDDER for the purpose of implementation of ERP solution. Provide overview below and attach additional sheets to the proposal, if required.

R

The Infrastructure such as IDES Systems will be installed at the beginning of the project and make them available for Training. The Development Servers, Quality Servers and Product Server Installation Pplan will be discussed in detail during the Project Preparation Phase.

3

Provide details of application customization plan (for customization of each module, indicate timelines and resource deployment, location of customization, involvement of FEWA personnel). Provide overview below and attach additional sheets to the proposal, if required.

R

A High Level MPP plan is provided for the project which will be refined by the PMO (Wipro & FEWA Project Managers) during the Project Preparation Phase.

4

Provide details of how the reporting requirements identified in the requirement matrix will be configured in the ERP application? Describe tools to be used for same and involvement of FEWA team, if any.

R

Wipro shall provide Most of the Operational Reports through the SAP System. Intelligence Reports covering Multiple Functional Areas with High Detail of Information shall be provided using the Infocubes from SAP BI and SAP BO. KPI’s, Dashboards also will be provided as part of the deliverables.

We have covered the requirements as per the cap mentioned in the RFP.

Annex B: Appendix 3B- Compliance Sheet

Page 125 of 89 5

Provide details of Sign-off procedures. Provide overview below and attach additional sheets to the proposal, if required.

R

Every Milestone in each Wave has a Sign-off procedure to ensure the Quaility of Service to the Satisfaction of the FEWA’s Team.

6

Provide details of User Acceptance Test (UAT) plan, script templates to be used, approach to be taken, FEWA involvement (department, user profile, etc.) and signoff procedures to be followed.

R

The User Acceptance Plan for each of the Wave in Application (UAT). Shall use SAP SOLMAN 7.0 eCATT Tool for UAT.

7

Confirm that Post-implementation support for a period of one year from the date of Go-Live is included in this proposal. The cost of additional support should also be specified in the commercial section.

R

Wipro Confirms that Post-implementation support for a period of one year from the date of Go-Live. The Support is On-Site & Off-Shore.

8

Provide details of Change management plan and procedures during the project.

R

A Dedicated Change Manager will be positioned on Site for 6 Months to provide Strategy, Direction of Change Management. He will provide Hand Holding Services to FEWA’s Change Manager who is also a Full Time Member on the project till completion.

For further details please refer to the Technical Proposal which is provided as an Appendix to this document.

9

Provide details of the Project Risk management plan. Provide overview below and attach additional sheets to the proposal, if required.

R

Wipro’s Governance Strucutre will handle the Risk Management and provide Mitigation Plans for the senior Management.

For further details please refer to the Technical Proposal which is provided as an Appendix to this document.

10

Provide details of the Project controls proposed. Provide overview below and attach additional sheets to the proposal, if required.

R

The Governance Strucutre will handle the Project Controls like Communication Plan, Escalation Matrix and Responsibility.

For further details please refer to the Technical Proposal which is provided as an Appendix to this document.

11

Provide the Project Quality management plan with clarity on procedures, roles and responsibilities. Provide overview below and attach additional sheets to the proposal, if required.

R

Wipro shall engage a person from Wipro Quality Organization which acts as an Independent Reviewer and appraises the Steering Committee on the Quality Activities.

For further details please refer to the Technical Proposal which is provided as an Appendix to this document.

Annex B: Appendix 3B- Compliance Sheet

Page 126 of 89

12

Provide details of Escalation procedures and issue resolution plan for the project. Provide overview below and attach additional sheets to the proposal, if required.

R

The Details are provided in the Technical Proposal which is provided as an Appendix to this Document.

13

Please provide details of Internal Quality standards that BIDDER follows for projects involving implementation of ERP. Please confirm if the BIDDER has achieved standard certifications for the internal Quality processes.

R

The Details are provided in the Technical Proposal which is provided as an Appendix to this Document.

14

Provide the proposed Project organization chart outlining Project roles (e.g. Steering Committee member, Project manager, Module leader, etc.), Organization (e.g. FEWA, Lead BIDDER, supporting BIDDER, etc.) and roles and responsibilities of each role (e.g. Project manager = Project planning, monitoring, resource management, etc,). Please use additional sheets if required.

R

The Project Organization Chart for Wipro and FEWA is provided in the Technical Proposal which is provided as an Appendix to this document.

3.2

Data Migration

1

Please provide a brief overview of the Data Migration Strategy typically adopted by the BIDDER in such implementation projects

R

Wipro shall follow Standard SAP Suggested Cutover Methodology in Migrating Data from Legacy Systems to SAP System. Wipro shall follow SAP DWH Strategy for migrating Historical Data from Legacy Systems to SAP System.

The Same has been provided in the Appendix “Technical Proposal”

2

How do you establish the acceptability of the data available from legacy applications?

R

The Data has to be approved by the FEWA’s Business Owners on the Correctness of Data.

3

What are the considerations for deciding whether manual or automated correction/validation should be adopted to facilitate the data migration?

R

If the Records are more than 100 and covering Multiple Screens along with its frequency of use during Live Environment, Wipro and FEWA shall jointly decide on the approach. If the Master Data Population is small Wipro suggests to create the Data Manually to save time and effort in developing and Testing of Upload Programs.

4

Does the BIDDER intend to use any specific tools to facilitate data migration? If so, please provide details.

R

Wipro Shall use SAP SOLMAN 7.0 Legacy Data Migration Workbench coupled with Batch Data Convertion Programs to upload data from Flat Files to SAP System or SAP DWH System as the case may be.

5

How is the accuracy of the Data Migration process established? Please provide details of the control mechanism that the BIDDER deploys to ensure integrity of the data migration process.

Annex B: Appendix 3B- Compliance Sheet

Page 127 of 89 R

The Data Migration is Marked Successful only after drawing a report on Number of Records Loaded and Trial Balance Generated out of SAP System. FEWA’s BPO & Data Migration Team shall provide Data in a CD in the required format.

6

Please clearly identify the involvement of FEWA in the data migration process and also indicate the requirements from FEWA staff.

R

Wipro Team and FEWA’s Core Team shall identify the Objects for which Data Migration has to be performed.

PMO will develop a Data Migration Plan for Each Wave and create a Dedicated Team comprising of FEWA IT personnel and Data Collectors representing each location. This team is responsible for Extraction, Enrichment, Conversion in the formats provided by Wipro Consultants. Wipro consultants shall provide Training in Enrichment and Conversion to this team.

We will require a Team of 15 persons representing each Area of Business for Data Collection.

3.3

Interfaces

1

Please provide a brief overview of how BIDDER will handle the Interfaces proposed by FEWA and the proposed Billing/ ERP Applications. The proposed interfaces are with Contact center, e-services, Document Management System, Cash Settlement Machines, Bank Statements, Emirates Post Receipts, Credit Card Readers, GIS/ SCADA, etc.

R

Wipro team shall provide API’s to integrate with Contact Center, Payment Gateways, Banks, GIS/SCADA, SMS Gateways.

The Technical Proposal which is provided as an appendix gives further details on how Wipro plans to provide integration.

2

How would the BIDDER approach designing, developing and testing the interfaces?

R

Wipro shall follow the FRS – TRS – DEVELOPMENT – TESTING – MOVEMENT methodology in Designing, Developing the Interfaces.

3

How would the BIDDER handle the subsequent changes to the interface requirements?

R

The FEWA IT Team will be provided Training on making changes and also the procedure that has to be followed in releasing the developments from one envrionement to another.

Any Subsequent changes in the Interface requirements which cannot be handled by the FEWA IT team will be provided. However any modification which can take more than 3 Man Days of effort will be provided after initating a Change Control Procedure.

3.4

Documentation

Kindly furnish information for each solution separately in case more than one solution is involved

Annex B: Appendix 3B- Compliance Sheet

Page 128 of 89 Please list which of the following documentation are provided with your product(s)

•

User manuals

•

Implementation manual

•

System Administration manual / Operations manual

•

System manuals – Architectures, Entity-Relationship diagrams, Source code etc.

•

On-line User Manual

•

Online context sensitive help

1

How many copies of related software user documentation are provided with the software purchase? Please mention the form of documents (hard copy, soft copy, etc.)

R

SAP Documentation is available On Line. It is SAP’s and Wipro’s Policy to make the Planet a Greener Place to Live. Hence Hardcopies of the same are provided only against additional charge.

2

How many copies of related software technical documentation are provided with the software purchase?

R

No Hardcopies Please.

3

Can additional copies be made by FEWA in-house or must additional manuals be purchased?

R

Project Teams, FEWA Team and IT Team of FEWA can take printout of the documents any number of times, there is no restriction and cost implications on the same.

4

a. Is documentation provided in loose-leaf format in case of updation?

R

Documentation of Updates is On Line and is not given as an addendum. b. Are documentation updates available in an electronic form? If yes, please provide details.

R

All the Documentation on SAP Help, SAP Notes is available in Electronic Format and can be Downloaded from http://service.sap.com or http://help.sap.com

5

Does the Bidder provide documentation updates to correspond with each software release?

R

The Documentation is directly available to FEWA and Wipro does not pose any restriction on the use of the same by FEWA Team.

6

On what fee basis are additional documentation updates provided? Provide these details in the commercial section.

R

For Electronic Format, Neither Wipro, nor SAP shall charge the customer. If the Documentation is required in Hardcopy the same shall be provided at a price that can be mutually decided.

7

Does the Bidder provide for downloading documents or white papers from its web site

R

The information on the Links to the Documentation shall be provided both by SAP and Wipro and none will place any Restriction on using the same.

Note: All costs should be specified in the commercial section only.

Annex B: Appendix 3B- Compliance Sheet

Page 129 of 89

3.5

Bidder Staffing Plan

Since the Implementation is a Phased approach having multiple Waves, it is not possible to give a split as per the Schedule given below.

Project Role

Phase I – Project preparation, Training and Design

Phase II – Software Configuration / Customization / UAT Signoff

Phase III – Preparation of Go-live, End user training, Go-Live

Phase IV – Post GoLive

No. of personnel

No. of personnel

No. of personnel

No. of personnel

Involvement Person/Days

Project Management Steering Committee member

1

Project Manager

1

Functional / Module related Module Name



Technical areas Technical Leader Technical team member 1 Technical team member 2

Support areas Support team member

Involvement Person/Days

Involvement Person/Days

Involvement Person/Days

Annex B: Appendix 3B- Compliance Sheet

Page 130 of 89 Project Role

Phase I – Project preparation, Training and Design

Phase II – Software Configuration / Customization / UAT Signoff

Phase III – Preparation of Go-live, End user training, Go-Live

Phase IV – Post GoLive

No. of personnel

No. of personnel

No. of personnel

No. of personnel

Involvement Person/Days

Support team member

Involvement Person/Days

Involvement Person/Days

Involvement Person/Days

Annex B: Appendix 3B- Compliance Sheet

Page 131 of 89

3.6

CVs of team members

Please fill up following tables for each of the proposed team members of BIDDER for FEWA project. In case of multiple Bidders please provide details of team members of all the involved Bidders. FORMAT OF CURRICULUM VITAE (CV) FOR PROPOSED KEY STAFF

Proposed Position: Name of Firm: Name of Staff: Profession: Date of Birth: Years with Firm/Entity:

Nationality:

Members Bidder in Professional Societies:

Detailed Tasks Assigned:

Key Qualifications: [Give an outline of staff member’s experience and training most pertinent to tasks on assignment. Describe degree of responsibility held by staff member on relevant previous assignments and give dates and locations. Use about half a page.]

Annex B: Appendix 3B- Compliance Sheet

Page 132 of 89

Education: [Summarize college/university and other specialized education of staff member, give names of schools, dates attended, and degrees obtained. Use about one quarter of a page.]

Employment Record: [Starting with present position, list in reverse order every employment held. List all positions held by staff member since graduation, giving dates, names of employment organizations, titles of positions held, and locations of assignments. For experience in last ten years, also give types of activities performed and client references, where appropriate. Use about two pages.]

Languages: [For each language indicate proficiency: excellent, good, fair or poor in speaking, reading and writing.]

Certification: I, the undersigned, certify that to the best of my knowledge and belief, these data correctly describe me, my qualifications, and my experience. I also certify that I have only given permission for my CV to be included in the Bid submitted by [Fill in name of Bidder here.]

Date: [Signature of staff member and authorized representative of the firm] Full name of staff member: Full name of authorized representative:

Day/Month/Year

Annex B: Appendix 3B- Compliance Sheet Page 133 of 89

3.7

FEWA team involvement FEWA TEAM INVOLVEMENT

Project Role

Phase I – Project preparation, Training and Design No. of person nel

Project Management Steering Committee

Project Manager

Functional / Module related

Role in the project

Expected skills

Phase II – Software Configuration / Customization / UAT Signoff No. of pers onne l

Role in the project

Expected skills

Phase III – Preparation of Go-live, End user training, Go-Live No. of pers onne l

Role in the project

Expected skills

Phase IV – Post Go-Live (3 month support period) No. of pers onne l

Role in the project

Expected skills

Project Sponsor, Business Process Owners (Required on Part Time Basis). These resources have to attend the Steering Committee Meetings which are organized Once every Month.

1

Project Management

Person working with FEWA and responsible for IT Projects

1

Project Management

Person working with FEWA and responsible for IT Projects

1

Specified as Below

Project Management

Person working with FEWA and responsible for IT Projects

1

Project Management

Person working with FEWA and responsible for IT Projects

Annex B: Appendix 3B- Compliance Sheet Page 134 of 89

FEWA TEAM INVOLVEMENT Project Role

Phase I – Project preparation, Training and Design No. of person nel

Role in the project

Expected skills

Human Capital Management

3

HCM Team from Corporate Services will be the Core Team Members in the Project

Experience in Handling HR Requirements in FEWA and Working in the areas of Recruitment, Performance Appraisal, Payroll, Personnel Development.

Performance Management (Business Intelligence)

2

IT persons from IT Department who will be the Technical Core Team Members in the Project

Persons who invloved developing Senior Management Reports invloved in Development FEWA

IT persons from IT Department who will be the Technical Core Team Members in the Project

Persons who invloved developing Senior Management Reports invloved in Development FEWA

Performance Management

2

are in the

Phase II – Software Configuration / Customization / UAT Signoff No. of pers onne l 3

2

and IT at are in the and IT at

2

Role in the project

Expected skills

HCM Team from Corporate Services will be the Core Team Members in the Project

Experience in Handling HR Requirements in FEWA and Working in the areas of Recruitment, Performance Appraisal, Payroll, Personnel Development.

IT persons from IT Department who will be the Technical Core Team Members in the Project

Persons who invloved developing Senior Management Reports invloved in Development FEWA

IT persons from IT Department who will be the Technical Core Team Members in the Project

Persons who invloved developing Senior Management Reports invloved in Development FEWA

are in the

Phase III – Preparation of Go-live, End user training, Go-Live No. of pers onne l 3

2

and IT at are in the and IT at

2

Role in the project

Expected skills

HCM Team from Corporate Services will be the Core Team Members in the Project

Experience in Handling HR Requirements in FEWA and Working in the areas of Recruitment, Performance Appraisal, Payroll, Personnel Development.

IT persons from IT Department who will be the Technical Core Team Members in the Project

Persons who invloved developing Senior Management Reports invloved in Development FEWA

IT persons from IT Department who will be the Technical Core Team Members in the Project

Persons who invloved developing Senior Management Reports invloved in Development FEWA

are in the

Phase IV – Post Go-Live (3 month support period) No. of pers onne l 3

2

and IT at are in the and IT at

2

Role in the project

Expected skills

HCM Team from Corporate Services will be the Core Team Members in the Project

Experience in Handling HR Requirements in FEWA and Working in the areas of Recruitment, Performance Appraisal, Payroll, Personnel Development. Persons who are

IT persons from IT Department who will be the Technical Core Team Members in the Project

IT persons from IT Department who will be the Technical Core Team Members in the Project

invloved in developing the Senior Management Reports and invloved in IT Development at FEWA Persons who invloved developing Senior Management Reports invloved in Development FEWA

are in the and IT at

Annex B: Appendix 3B- Compliance Sheet Page 135 of 89

FEWA TEAM INVOLVEMENT Project Role

Phase I – Project preparation, Training and Design No. of person nel

Role in the project

Supply Chain Management

2

Supply Directorate Team

Financial Management

5

Members from Corporate Team of FEWA will be Functional Core Team Members in the Project

Asset Lifecycle Management

3

Members from Shared Services Directorate of FEWA will be Functional Team Members in the Project

Expected skills

Persons invloved in the Supply Directorate of FEWA and has exposure to the Business Processes at FEWA. Persons involved in the Corporate Functions of FEWA and who has exposure to all the Business Processes of Costing, Budgeting, G/l, AR, AP etc. Persons invloved in the Shared Services Directorate and who has exposure to all the Business Processes of Asset Management.

Phase II – Software Configuration / Customization / UAT Signoff No. of pers onne l 2

Role in the project

Supply Directorate Team

5

Members from Corporate Team of FEWA will be Functional Core Team Members in the Project

3

Members from Shared Services Directorate of FEWA will be Functional Team Members in the Project

Expected skills

Persons invloved in the Supply Directorate of FEWA and has exposure to the Business Processes at FEWA. Persons involved in the Corporate Functions of FEWA and who has exposure to all the Business Processes of Costing, Budgeting, G/l, AR, AP etc. Persons invloved in the Shared Services Directorate and who has exposure to all the Business Processes of Asset Management.

Phase III – Preparation of Go-live, End user training, Go-Live No. of pers onne l 2

Role in the project

Supply Directorate Team

5

Members from Corporate Team of FEWA will be Functional Core Team Members in the Project

3

Members from Shared Services Directorate of FEWA will be Functional Team Members in the Project

Expected skills

Persons invloved in the Supply Directorate of FEWA and has exposure to the Business Processes at FEWA. Persons involved in the Corporate Functions of FEWA and who has exposure to all the Business Processes of Costing, Budgeting, G/l, AR, AP etc. Persons invloved in the Shared Services Directorate and who has exposure to all the Business Processes of Asset Management.

Phase IV – Post Go-Live (3 month support period) No. of pers onne l 2

Role in the project

Supply Directorate Team

5

Members from Corporate Team of FEWA will be Functional Core Team Members in the Project

3

Members from Shared Services Directorate of FEWA will be Functional Team Members in the Project

Expected skills

Persons invloved in the Supply Directorate of FEWA and has exposure to the Business Processes at FEWA. Persons involved in the Corporate Functions of FEWA and who has exposure to all the Business Processes of Costing, Budgeting, G/l, AR, AP etc. Persons invloved in the Shared Services Directorate and who has exposure to all the Business Processes of Asset Management.

Annex B: Appendix 3B- Compliance Sheet Page 136 of 89

FEWA TEAM INVOLVEMENT Project Role

Phase I – Project preparation, Training and Design No. of person nel

Role in the project

Expected skills

Phase II – Software Configuration / Customization / UAT Signoff No. of pers onne l 3

Role in the project

Expected skills

Members from Customer Service Directorate of FEWA will be Functional Team Members in the Project

Persons involved in the Customer Services Directorate and who have exposure to all Business Processes of Customer Life Cycle.

Phase III – Preparation of Go-live, End user training, Go-Live No. of pers onne l 3

Role in the project

Expected skills

Members from Customer Service Directorate of FEWA will be Functional Team Members in the Project

Persons involved in the Customer Services Directorate and who have exposure to all Business Processes of Customer Life Cycle.

Phase IV – Post Go-Live (3 month support period) No. of pers onne l 3

Role in the project

Expected skills

Members from Customer Service Directorate of FEWA will be Functional Team Members in the Project

Persons involved in the Customer Services Directorate and who have exposure to all Business Processes of Customer Life Cycle.

Customer Care & Billing

3

Members from Customer Service Directorate of FEWA will be Functional Team Members in the Project

Persons involved in the Customer Services Directorate and who have exposure to all Business Processes of Customer Life Cycle.

Technical areas

10

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

10

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

10

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

10

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

System administratio n

2

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

2

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

2

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

2

Members from IT Team shall be Technical Core Team Members in the Project.

Persons who have Programming Experience in any Language and has Learning Capability to imbibe new Technologies.

Interface development System programming

Included in Technical Areas (Persons who got trained in the Technical Areas will also be given Assignments in Development) Included in Technical Areas (Persons who got trained in the Technical Areas will also be given Assignments in Development)

Annex B: Appendix 3B- Compliance Sheet Page 137 of 89

FEWA TEAM INVOLVEMENT Project Role

Phase I – Project preparation, Training and Design No. of person nel

Role in the project

Expected skills

Data migration

Change Manager

1

Change Leader

A person who can enable change in the Organization

Phase II – Software Configuration / Customization / UAT Signoff No. of pers onne l 10

1

Role in the project

Expected skills

Members of this Team are responsible for Collecting, Collating and Correcting the Data from Legacy Systems.

The Members should be able to work on Excel Sheets and Transform the Data from Legacy System to the format compatible for SAP Upload.

Change Leader

A person who can enable change in the Organization

Phase III – Preparation of Go-live, End user training, Go-Live No. of pers onne l 10

1

Role in the project

Expected skills

Members of this Team are responsible for Collecting, Collating and Correcting the Data from Legacy Systems.

The Members should be able to work on Excel Sheets and Transform the Data from Legacy System to the format compatible for SAP Upload.

Change Leader

A person who can enable change in the Organization

Phase IV – Post Go-Live (3 month support period) No. of pers onne l

1

Role in the project

Change Leader

A Team of 45 Members (Functional & Technical Core Team Members, Data Migration Team Members) are required to work on this project Full Time. Project Manager, Change Manager are also required from Project Management office to work Full Time. Senior Leadership Team like Sponsors etc are required on a Part Time Basis only.

Expected skills

A person who can enable change in the Organization

Annex B: Appendix 3B- Compliance Sheet Page 138 of 89

3.8

FEWA Infrastructure Requirements Expected resource requirements from FEWA (hardware, software, office space, etc.) for the implementation of proposed solution. Provide overview below and attach additional sheets to the proposal, if required.

R

Wipro shall require a Project Office to accommodate 100 persons (Both FEWA Team and Wipro Team) with Meeting Halls, Discussion Rooms. Separate Cabins each for Wipro Project Manager and FEWA’s Project Manager. Media Equipment like Projectors, Writing Boards. Seating Space and Document Storing Sapce to each Member. Desktops / Laptops for the Team Members. Two Power Sockets (One Standard, One UPS), LAN Cable to each Desk. Printers, Stationery, Communication Equipment. A minimum of 1 MBPS Internet Connection Datacenter with Access Controls and Precision A/c to house the Servers. Network with Firewalls with No Restriction to SAP Marketplace and other Authorized Sites. Common Amenities and Support Staff.

Wipro’s Project Manager shall provide small suggestions during the Project Preparation Phase if any additional is required.

Annex B: Appendix 3B- Compliance Sheet Page 139 of 89

4 1

Training What amount of training is included in terms of number of people type of course/agenda (technical, administration, business users, etc) and number of man-days? Clearly mention if BIDDER proposes that FEWA should source any of the components of training from ERP vendor. CONSULTANT LEVEL TRAINING: Training will be given during the Phase I of the project. Training will be provided for a Team of 19 Members. Training will be Given by Certified Members from SAP. Module wise Trainees split is as follows: Training Course

Persons

Days

SAP FIN, AC010, AC050 (Financial Accounting) (Basic Course)

2

12

AC040 (Management Accounting)

1*

5

Human Capital Management – SAP HR - (Basic Course)

2

2

HR050, HR305

1*

5

HR400 & HR110

1*

2

SAP SCM - (Basic Course)

2

3

SCM500, SCM510

1*

10

SCM 515, SCM520

1*

8

PM - (Basic Course)

2

10

IUT (IS-Utilities) – IUT110 - Basic Course

3

5

IUT210, 220, 225

1*

8

IUT221, 230, 235

1*

8

IUT240, 250

1*

8

Administration

1

13

ABAP

5

15

BI

1

1

Enterprise Portal

1

2

* Included in the Persons identified in the Basic Course

Training will be given out of FEWA’s Project Office. Certificate of Attendance will be provided to the Participants who have attended for more than 95% of Attendance.

Annex B: Appendix 3B- Compliance Sheet Page 140 of 89

2

Describe all pertinent training courses for all the phases of project and all the types of training (e.g. End-user, core team, System administration training, etc.). For each course, include the following information:

•

Course Title

The Details are provided in the Technical Proposal Attached.

•

Location

____________________________________ _

•

Phase of the project when training will be imparted

____________________________________ __

•

Mode of training (e.g. classroom, online)

____________________________________ __

•

Target participants (e.g. Core team functional team members, end-users)

____________________________________ _

•

Number of participants per batch

____________________________________ _

•

Duration of training

____________________________________ _

•

Frequency of offering

____________________________________ _

•

Prerequisites

____________________________________ _

•

General description

_____________________________________________

3 List the courses you will not be able to train the dual language Arabic/ English Consultant Level Training, Level III Training and Customization Training & “Train the Trainer” will be done only in English. End User Training will be done in both English & Arabic.

Annex B: Appendix 3B- Compliance Sheet Page 141 of 89

5

Support Questionnaire

Please provide details of support to be provided by BIDDER. 1

Please indicate the structure of providing support with details of escalation procedures. Clearly identify the role that BIDDER will play and what will be the role of ERP vendor in terms of providing support. ______________________________________________________________________________________ ______________________________________________________________________________________

2

Please describe the problem reporting and resolution mechanism that would be used if FEWA identifies a problem with the package. Does the Bidder have dial-up capability into the FEWA system to correct application program bugs? Provide details of security arrangements in case your personnel log into FEWA’s servers. _____________________________________________________________________________________ _____________________________________________________________________________________ _____________________________________________________________________________________

3

Do you have a user Hotline? ( Y / N ) If yes:

•

Availability: hours/day (specify time in Dubai) - Does this include weekends? FEWA would prefer local support 7 am to 6 pm support (Dubai), six days a week.

Specify service outside the normal office hours and at weekends. Also specify if the number to be dialed is within Dubai. Amit / MIT team to add please

4

What is the maximum response time for all the queries / issues registered by FEWA personnel?

R

The Response Time and Resolution Time shall be discussed and Mutually agreed before the Warranty Support Starts.

5

Please provide details of the software (e.g. helpdesk software), hardware and WAN infrastructure used to offer support to clients.

R

Amit / MIT team to add please

6

Charges - Is the Hotline support inclusive in the annual maintenance charge, or are users charged per call? If charged on a per-call basis, please provide cost in the relevant section in Commercial bid.

R

Amit / MIT Team to add please

7

Provide details of locations in UAE from where Bidder will provide support. Indicate details of type of support (direct or through a partner company).

R

Amit / MIT Team to add please

8

How many releases of your product are currently supported? Please identify.

R

Annex B: Appendix 3B- Compliance Sheet Page 142 of 89

9

Will BIDDER provide support for system customization as a part of annual support contract? Provide details.

R

In Sustenance Support, Wipro only provides support for the Functionality Implemented and Objects Developed during the Implementation Phase. Any New Modules Implementation, New Functionality Implementation, Change in Organization Structure, development of New Reports, Infocubes, Pages will be provided after initiating a Change Control Procedure.

10

Please discuss your policy regarding releasing future application software versions to users who have modified software (modified either for implementation at FEWA by implementer or a 3rd party). Please indicate your policy regarding supporting these modifications / customizations in subsequent versions/enhancements.

R

SAP has a Roadmap of Releasing Functional Enhancements Twice Every Year. If the Functionality released by SAP is found to be useful for FEWA, the same shall be Implemented. However we have factored for a Minimal Effort of 2 days for this activity. If this calls for more effort beyond 2 days including all the Technical & Functional Resources required for implementing Functional Set Enhancement, the same shall be routed through Change Control Procedure.

11

In case of new software upgrades, are the upgrades available to FEWA free of cost? If not, what is the policy? Provide details.

R



12

Is web-based support available? What features are supported?

R

OSS Connection with SAP is provided through the SAP Solution Manager which will provide direct Support Services from SAP. SAP has defined the SLA’s for the Support Issues. The Support is provided on 24 X 7 model.

Annex B: Appendix 3B- Compliance Sheet Page 143 of 89

6

BIDDER Organization Details

6.1

Company Profile

(Kindly furnish information for each Bidder separately in case more than one Bidder is involved) General Company Name Date of Incorporation Holding Company or Parent Company (if any) Company local (in UAE) address Contact details: Name, phone, fax and e-mail Please provide details of ownership: private/public; ultimate parent; major shareholders. Any significant changes in ownership in the last two years? Who are the primary shareholders? (Also indicate major shareholders with percentage holding in case of limited companies) Number of years in business Account Representative Address and Phone

Financial Background (last published report) Annual Revenue Annual Net Income Please indicate what percentage of total revenues of the company is contributed by the ERP and related services. (Indicate this for UAE as well as international operations of the company) Please provide a history of sales figures during the past five years. Please attach most recently available annual report, and audited balance sheets and income statements for previous three years. Any pending or past litigation (within 3 years)? If yes, please explain. Please also mention any claims/complaints received in the last three years.

Certifications Please provide details of any quality process certifications (e.g. SEI CMM etc.) Any other certifications, please specify

Staff Total number of employees

• •

UAE World-wide

In UAE Please provide a break-up of the number of employees by function, e.g.

• • • • • •

Sales/marketing Administrative staff Research & Development Implementation staff Technical Support staff Others

Provide details of total number of skilled manpower in the organization relevant for FEWA’s ERP implementation

Annex B: Appendix 3B- Compliance Sheet Page 144 of 89

• • •

Functional ERP consultants (for the ERP for which implementation is proposed) Technical experts Team leaders / Project managers Mention location where the above manpower is located in UAE / worldwide.

Number of implementations carried out in UAE for the ERP solution. Please provide number of implementations for all the applications / modules.

Staff with Arabic Skills List the of total number of skilled manpower in the organization relevant for FEWA’s ERP implementation which is able to communicate (oral and written) in Arabic

• • •

Functional ERP consultants (for the ERP for which implementation is proposed) Technical experts Team leaders / Project managers Mention location where the above manpower is located in UAE / worldwide.

Infrastructure Provide details of Support Center for the ERP which is to be implemented at FEWA.

• • • •

Infrastructure available Location of service center Manpower available for provision of support Number and reference names of clients which are supported from the support center

Provide details of Research and Development (R&D) center for the ERP for which implementation is proposed

• • •

Facilities available Team available Location of the center

Alliance between Other Bidders (fill only if multiple Bidders involved) Years since alliance between Bidders Nature of alliance (marketing, financial, etc.) between Bidders Countries where the alliance is applicable Number of prior instances when marketing / bidding carried out together by the Bidders. Number of prior instances when implementations carried out together by the Bidders. Please provide client names and countries.

6.2

Reference Site Details

The reference site details should be given in the following format separately for implementation carried out. A separate copy should be used for each reference site. Company Name Company Address Telephone Number

Annex B: Appendix 3B- Compliance Sheet Page 145 of 89 Fax Number Contact Name Title What is or was the contact’s role in the implementation/ project? State the duration of the implementation. Go Live date for the pilot location Which modules and version of the software are being currently used? Provide details of extent of customisation effort required on the base software to meet the referred client’s requirements (man-days, etc). State which of the applications / modules (which are proposed to FEWA) were implemented at the reference site State if the reference site includes integration between applications which are proposed to FEWA (in case the applications proposed to FEWA were implemented at reference site) What version of operating system, database etc. is in use? Are there any other system used in conjunction with the application software like front end systems etc.? Please provide details if any. State number of locations where this software is used State the number of employees, stores, etc which were mapped in the system State, if any, interfaces to external systems are implemented at this site State the role played by the Bidder and its scope in the project (e.g. process mapping, data migration, training, etc.) Indicate the role played by the reference client during implementation of the product(s)

6.3

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

Provide below the number of implementations in GCC/ UAE and specifically in the utility industry Implementations in GCC by industry : Finance Govt Utilities Private Companies Others Total Implementations in UAE by industry: Finance Govt Utilities Private Companies Others Total

Annex B: Appendix 3B- Compliance Sheet Page 146 of 89

Annex B: Appendix 3B- Compliance Sheet Page 147 of 89

7

Other Formats

7.1

Form for Clarification Questions Form for Clarification Questions

Bidder’s Name: Bidder’s Address: Item No.

1. 2. 3. 4. 5. 6.

Section Reference

Date Submitted: Page No.

Section or Article No.

Question/Query/Clarification/Comment

Annex B: Appendix 3B- Compliance Sheet Page 148 of 89

7.2

Form for Deviations from RFP

Please outline all the deviations in your proposal from the scope, requirements and terms & conditions defined in the RFP.

Deviations provided in the Technical Proposal which is given as an Appendix to this document.

Sr. No.

RFP Reference (Chapter, Section)

Details of deviations