Fin & Tech Eval Sheet 2 V0.1

8/12/2019 Fin & Tech Eval Sheet 2 V0.1

http://slidepdf.com/reader/full/fin-tech-eval-sheet-2-v01 1/14

What?

Section

EJADA PCS VERSOS FAKHROO ELITE

% Score % Score % Score % Score % Sco

1. Experience

1.1. Reference Sites 10 40 40 12.00 30.00 15.00 5.00

1.2. No. Of sites world wide 5 20 20 15.00 15.00 8.00 15.00

1.3. Upgrade in Middle East 2 8 8 8.00 8.00 8.00 8.00

1.4. Telecom Reference 5 20 20 0.00 10.00 8.00 0.00

1.5. SI role and in Ref Sites 3 12 12 12.00 12.00 12.00 0.00

Total 100 100 47.00 75.00 51.00 28.00

A. Experience Weighted Score (20%)

2.Functional

2.1. Architecture Overview 5 40 21.62 40.00 40.00 31.00 23.00

2.2. Usability/User Interface 5 30 16.22 25.00 25.00 30.00 30.00

2.3. Administration 5 15 8.11 10.00 10.00 10.00 10.00

2.4. Token Type 5 20 10.81 17.00 17.00 17.00 17.00

2.5. Token Life /Subscription 5 15 8.11 10.00 10.00 9.00 13.00

2.6. Redundancy 5 5 2.70 5.00 5.00 5.00 5.00

2.7. Support 5 35 18.92 32.00 32.00 26.00 28.00

2.8. The respondants should enlist the

databases that their solution supports 5 1.00 1.00 5.00 5.00

2.9. Logging Capabilities 5 20 10.81 20.00 20.00 20.00 20.00

Total 185.00 97.30 160.00 160.00 153.00 151.00

B. Functional Weighted Score (20%)

3. Project Methodology EJADA PCS VERSOS FAKHROO ELITE3.1. Tools 2 8 13.33 7.00 7.00 6.00 6.00

3.2. Project Management Proposal 3 12 20.00 10.00 10.00 9.00 9.00

3.3. Methodology 3 12 20.00 10.00 10.00 7.00 7.00

3.4. Maintenance Support 2 8 13.33 6.00 7.00 5.00 5.00

3.5. Remote support during warranty

period 3 12 20.00 9.00 10.00 7.00 6.00

3.6. Training 2 8 13.33 6.00 7.00 5.00 5.00

Total 60 100 48.00 51.00

C. Project Methodology Weighted Score (10%)

Notes;

Scoring Sheet

* Score from Zero to 4 mark for each module.

Score Basis

Business Priority

Weight

Max Weighted

Score of 100%



What?

Section

EJADA PCS VERSOS FAKHROO

% Score % Score % Score % Score

1. Experience

1.1. Reference Sites 10 40 40 12.00 30.00 15.00 5.00

1.2. No. Of sites world wide 5 20 20 15.00 15.00 10.00 12.00

1.3. Upgrade in Middle East 2 8 8 8.00 8.00 8.00 8.00

1.4. Telecom Reference 5 20 20 0.00 10.00 8.00 0.00

1.5. SI role and in Ref Sites 3 12 12 12.00 12.00 12.00 0.00

Total 100 100 47.00 75.00 53.00 25.00

A. Experience Weighted Score (20%)

2.Functional

2.1. Proposed Hardware Solution 5 50 7.04 50.00 50.00 11.00 28.00

2.2. Support for current Infrastructure 5 95 13.38 95.00 93.00 95.00 86.00

2.3. Installation 5 15 2.11 15.00 15.00 10.00 9.00

2.4. Password Management 5 35 4.93 31.00 31.00 35.00 35.00

2.5. Encryption Standard 5 30 4.23 28.00 28.00 30.00 24.00

2.6. Redundancy 5 5 0.70 5.00 5.00 5.00 5.00

2.7. Technical Support 5 20 2.82 17.00 18.00 8.00 8.00

2.8. Access Control 5 25 3.52 25.00 25.00 19.00 11.00

2.9. Session Timeouts 5 15 2.11 14.00 14.00 15.00 7.00

2.10. Logging, Archiving and Purging 5 35 4.93 35.00 35.00 30.00 35.00

2.11. Report Generation 5 25 3.52 21.00 21.00 15.00 12.00

2.12. Time and Attendance 5 5 0.70 5.00 5.00 1.00 5.00

2.13. Microsoft Compatibility 5 20 2.82 20.00 20.00 12.00 14.00

2.14. Authentication 5 35 4.93 30.00 30.00 35.00 23.00

2.15. Scalability 5 5 0.70 5.00 5.00 5.00 5.002.16. Network Time Protocol 5 5 0.70 5.00 5.00 5.00 5.00

2.17. Operating System Feature support 5 25 3.52 25.00 25.00 25.00 25.00

2.18. Users and Group 5 15 2.11 15.00 15.00 15.00 15.00

2.19. Date and time settings 5 25 3.52 12.00 12.00 21.00 25.00

2.20. Logging and Auditing Features 5 30 4.23 30.00 30.00 10.00 30.00

2.21. Administrative Control Features 5 25 3.52 21.00 21.00 20.00 25.00

2.22. Backup Features 5 10 1.41 10.00 10.00 10.00 10.00

2.23. Error Handling 5 15 2.11 10.00 10.00 11.00 15.00

2.24. The respondents should be able to provide

a proof of solution for the services/productsbeing offered 5 5 0.70 5.00 5.00 5.00 5.00

2.25. Market competency 5 30 4.23 22.00 26.00 3.00 10.00

2.26. Availability and Reliability 5 0.70 1.00 1.00 1.00 1.00

2.27. System Availablity Levels 5 30 4.23 30.00 30.00 8.00 30.00

2.28. Modularity 5 5 0.70 5.00 5.00 5.00 5.00

2.29. Reference Manuals and documentation 5 45 6.34 45.00 45.00 45.00 45.00

Score Basis

Business Priority

Weight

Max Weighted

Score of 100%





Section Responsibility

Supplier 1 Supplier 2

% Score % Score

Business Priority

Weight

Max Weighted

Score of 100%

Score Basis

Ownership

3.2. Project Management Proposal 3 12 20.00

3.3. Methodology 3 12 20.00

3.4. Maintenance Support 2 8 13.33

3.5. Remote support during warranty

period 3 12 20.00

3.6. Training 2 8 13.33

Total 60 100 0.00 0.00C. Project Methodology Weighted Score (10%)

Notes;

Scoring Sheet

* Score from Zero to 4 mark for each module.



Responsibility

Supplier1 Supplier2

% Score % Score

SAP 45

7.2.1.2 Provide a complete schedule of the hardware and operating

system/utilities necessary to meet our requirements.

5 20 1.38

7.2.1.3 Does the proposed upgraded version operate on more than one

hardware/operating system environment? If so, which.

5 20 1.38

7.2.1.4 Does your proposed software operate only on the proposed

hardware?

5 20 1.38

7.2.1.5 What hardware supplier/model/range are you proposing? 5 20 1.387.2.1.6 Is your hardware solution future scalable? 5 20 1.38

7.2.1.7 What is the name and version level of the operating system you are

proposing?

5 20 1.38

7.2.1.8 Does your solution require MS SQL servers? Which versions of MS SQL

does your system run over?

3 12 0.83

7.2.1.9 Does your proposed solution work on HP/Compaq blade technology. 2 8 0.55

7.2.1.10 IS your hardware fully compatible with CISCO network equipments 5 20 1.38

SAP 60

7.3.1.1 Can your system be accessed by standard IBM compatible Pentium

PC's over a pure TCP-IP network?

5 20 1.38

7.3.1.2 We wish to be able to access various platforms (e.g. Mainframe and

Unix), Lotus Notes, via single PC workstations. You should confirm

that your proposal supports this approach.

3 12 0.83

7.3.1.3 Will your solution be able to direct printed output to dual XEROX

model 92C & 4890 Laser Printers for large volume reports?

3 12 0.83

7.3.1.4 Can your solution print to a standard UNIX network printer? 3 12 0.83

7.3.1.5 Will your solution be able to direct small volume reports (e.g. bill

reprints) to locally attached laser printers? (i.e. user PC’s)

3 12 0.83

Infrastructure

Owenrship

TW

Compatibility with Existing Hardware

Proposed Hardware

7.2.1.1 Diagrammatically make a clear recommendation on the preferred

hardware solution considering the whole requirements listed in this

RFP.

5

Out of 100%

Score Basis

Section

Weight

20 1.38



7.3.1.6 All application authentication Servers should integrate with AD witha

single sign on process and any other applications server should be a

member server in order to be part of the domain to apply all security

updates and for monitoring purpose.

3 12 0.83

7.3.1.7 Does your application integrate with Microsoft Active Directory forauthentication

3 12 0.83

7.3.1.8 Does your application support NLB, OS Clustering and Application

Clustering

5 20 1.38

7.3.1.9 Will your solution required an administrative rights to be performed

from the client side

3 12 0.83

7.3.1.10 Does your application use Web enable client with dynamic port

allocation that’s easily to be change in case of conflicts with any of the

exist application

3 12 0.83

7.3.1.11 Does your application compatible with Microsoft security updates 5 20 1.38

7.3.1.12 Does your application compatible with Anti-Virus Software (Trend

Office scan)

5 20 1.38

7.3.1.13 What is your client application installation files MSI/EXE. 2 8 0.55

7.3.1.14 Does your client application works with windows standard printing

mechanism

3 12 0.83

7.3.1.15 Is your client web based (thin) or thick. 3 12 0.83

7.3.1.16 Does your client application supported on Arabic enabled Windows

XP SP.2

3 12 0.83

7.3.1.17 Pleaseindicate anylimitationsthatyour proposed solution can’t work

on and/or affect its performance, given the technical environmentdescribed in section 1 Technical Environment

5 20 1.38

40

7.7.31 The system should allow for the concurrent operation of on-line,

batch and data transfer functions where this is required to meet

performance/service levels.

5 20 1.38

7.7.32 The need to perform data backups should not compromise this level

of concurrency.

5 20 1.38

7.7.33 Where on-line and batch processes are running concurrently, theremust be a recovery strategy to return to a single point of consistency.

5 20 1.38

Concurrency



7.7.34 Where on-line and batch processes are running concurrently, it

should be possible to dynamically tune the priorities of each process.

5 20 1.38

7.7.35 On-line and batch processes should share common routines 3 12 0.83

7.7.36 Any limitations on concurrency not covered above should be

specifically mentioned.

5 20 1.38

7.7.37 Error handling 5 20 1.38

7.7.38 Date utilities, date/time stamping 3 12 0.83

7.7.39 File controls and hash totalling 2 8 0.55

7.7.40 Device handling, printer control 2 8 0.55

3

7.8.1 Business functions should be modularized as clearly identifiable

segments of the system.

3 12 0.83

SAP 82

7.9.1.1 A comprehensive set of Reference Manuals must be provided for all

elements of the proposed solution.

5 20 1.38

7.9.1.2 An electronic version of the manuals 5 20 1.38

7.9.1.3 Reference Manuals are maintained up to date 5 20 1.38

7.9.1.4 Final manuals delivered to Batelco will reflect full details of any

customization work, and details of any “Batelco Specific”

extra/amended functions and facilities

5 20 1.38

7.9.1.5 Documentation/manuals must cover in the following areas: • User

Manual• Operations Manual

• Technical Reference Manual-S

• Training manuals

5 20 1.38

7.9.1.6 A full set of operations documentation that lists:

Name of job plus a high-level overview of what processes are

carried out

More detailed description of each job step

The command line that starts the batch job plus details of

mandatory and optional parametersList of files used by job step, as well as data tables accessed.

Typical and maximum elapsed time for each job step and complete

job

Modularity

Reference Manuals and Documentation

5 20 1.38



Priority of the job

Mandatory/optional status

Impact on on-line users

Pre-requisite jobs and jobs that must be run after a specified job.

Jobs that cannot be run with a specified jobUse of temporary storage space.

Details of any special rollback processing required if this job fails.

7.9.1.7 All documentation must be provided in hardcopy and softcopy form

and must be updated via a change control process.

3 12 0.83

7.9.1.9 Jobs must provide explicit messages that they have started and that

they have finished. In the latter case it must be clearly stated whetherthe job has been completed successfully or failed.

5 20 1.38

7.9.1.10 Safety mechanisms should exist that will prevent a batch job or on-

line process from starting if a dependent job or process has not

completed successfully. This will prevent, for example, an operator

starting a job by mistake when that job should be delayed until a

problem is fixed with an earlier job. Such safety mechanisms can only

be overridden by appropriately authorized staff.

3 12 0.83

7.9.1.11 If a job exceeds its maximum run time or it must be terminated for

any other reason then the operator can do so and the changes made

by the batch job will be rolled- back.

3 12 0.83

7.9.1.12 The batch job must have a consistent structure and naming

conventions such that the operators can monitor progress using

standard operating system facilities.

3 12 0.83

7.9.1.13 All operator-initiated jobs must be able to run in a batch mode rather

than being run in foreground. A batch job should consist of a script

file that Batelco could readily integrate into a menu system or into a

job-scheduling package.

3 12 0.83

All messages should have a reference number that corresponds to a

message number in the messages manual with further information

such as: -

·What the message means.

· The criticality to the system

7.9.1.14 3

12 0.837.9.1.8 A complete inventory of documentation elements should be available. 3

12 0.83





SAP 125

7.11.1.1 Identification information must be securely maintained by the system

and should be associated with an individual's authorization and

system activities.

5 20 1.38

7.11.1.2 The logon procedure should not identify the system or application

until the logon process has been completed successfully.

5 20 1.38

7.11.1.3 The system must validate the logon information only on completion

of all input data. After a rejected logon attempt, the logon procedures

must terminate. The procedure must not explain which piece of

information (the User-Id or password) was the reason for the logon

terminat ion. If an error condition occurs, the system must not

indicate which part of the data is correct or incorrect. The logon

procedures must set a maximum time allowed for the logon process.If the time is exceeded, the system must terminate the logon process.

5 20 1.38

7.11.1.4 On successful completion of logon, the logon procedures should

display the date/time of the previous successful logon, and the

number and date/time of unsuccessful logon attempts since the last

successful logon.

5 20 1.38

Auditing and Logging:

The system must be capable of Auditing and Logging controls

including audit trails and activity logs. These features should bedesigned into the systems.

Input Validation:

The system should have GUI based provision for through validation of

input data.

Session Management

The System must be capable of keeping track of which applications

are open and which documents each application has opened, so that

the same state can be restored when the user logs out and logs in

later.

Data Encryption:During transmission and storage of data it must be protected by

encryption, hashing, or truncation using standards like Advanced

Encryption Standard (AES) algorithm and Triple Data Encryption

Standard (3DES) algorithm.

Information Security Baseline Standards

7.11.1.5 5 20 1.38

7.11.1.6 3

7.11.1.7 3

0.83

7.11.1.8 3

12

12 0.83

0.8312



Security of Application Integration and Interfaces with network

platforms:

The system should provide Interface with all network platforms (e.g.

Switches, NGN. etc).

The system should be able to seamlessly interface with Batelco’s

corporate applications.7.11.1.10

The Solution shall have the ability to force periodic password changes.

5 20 1.38

7.11.1.11 The Solution shall have the ability to set the number of failed log-in

attempts before locking out the user

5 20 1.38

7.11.1.12 The Solution shall have the ability to set the lockout period before the

a user can reattempt log-in

5 20 1.38

7.11.1.13 The Solution shall have the ability to prevent passwords being created

that are blank and empty

5 20 1.38

7.11.1.14 Ability for any user to change their own password 5 20 1.38

7.11.1.15 Ability to inhibit any user from using any last ‘n’ passwords 3 12 0.837.11.1.16 Ability to define password rules, e.g. minimum number of characters,

capitals, alphas and numeric

3 12 0.83

7.11.1.17 Ability to encrypt passwords so that they cannot be viewed 5 20 1.38

7.11.1.18

Ability for the systems administrator to reset passwords to a default

5 20 1.38

Capability of segregate all actions. For example the changes to be

made (creation, modification, deletion) on the user and group profiles

between two security officers

(i.e., one will do the change and the other will authorize it)

Firewall need to be implemented if:- External Access to Batelco network.

- Access from sensitive network to less sensitive and vice versa.

- A new site that has no protection implemented yet

- Very critical systems with vulnerable services and protocols.

7.11.1.21 VPN need to be implemented for sensitive data through entrusted

cloud

5 20 1.38

7.11.1.22 Instal ling security agents which shall be instal led by Batelco in al l

servers to enforce Batelco security policies

3 12 0.83

7.11.1.23

Provide list of ports and services which will be used to connect to the

other systems and provide protocols types too.

3 12 0.83

7.11.1.24 Systems installed on the network should use static ports 3 12 0.83

7.11.1.19 5

207.11.1.20 5

7.11.1.9 5 20 1.38

1.38

20 1.38



7.11.1.25 Insecure Ports are not allowed. (e.g. Telnet, FTP) 5 20 1.38

7.11.1.26 Systems installed on the network that require FTP, HTTP or Telnet,

should be configured to use secure ports e.g. SSH

5 20 1.38

7.11.1.27 No Modems allowed on the network. For dial-up, users should use

Batelco’s secure dial up server

5 20 1.38

7.11.1.28 High Level Network Design logical and physical should be submittedwith IP Addressing schemes.

3 12 0.83

7.11.1.29 Note: Any additional software packages/features or operating system

releases/utilities required to achieve the required access security

should be explicitly mentioned in your response and included in your

costing schedule

3 12 0.83

Totals 1452 100 0 0

D. Infrastrucutre Weighted Score (10%) #REF!



Section Supplier 1 Supplier 2 Responsibility

% Score % Score

1. Experience

Reference Sites 4 16 14.29 13.00 0.00 OR1, OR3

Telecom Reference 5 20 17.86 0.00 5.00

Configuration in ECC 6.0 4 16 14.29 2.00 0.00

Experience in Methodology 5 20 17.86 1.00 3.00

Project size 5 20 17.86 2.00 17.00

Training 5 20 17.86 0.00 17.00

Total 112 100.00 18.00 42.00

Plant Maintenance Experience Weighted Score (20%)


% Score Score (%)

A. Plant Maintenance Functional

A.1 Overall SolutionFunctional understanding of the

requirements

Provision of Integration areas with Plant

Maintenance

To provide the benefits of integration

A.2 Master Data

Accommodate for the equipment master

data in the RFP

Accommodate for Resources master data

A.3 Preventive / Predictive Maintenance

Maintenance Schedule Creation

The schedule can be set to weekly /

monthly / daily

Auto creation of work orders based on

schedule

Creation of relationships based on

maintenance type

Check sheets creation for maintenance

componentsCheck Sheets data requirements

Send emails to technical with check sheets

For What?

Score Basis

Business Priority

Weight

Max Weighted

Score of 100% Ownership

Plant Maintenance Functional

Ownershipof 100%

Score Basis

Business Priority

Weight

Max Weighted

Score




% Score Score (%) Ownershipof 100%

Score Basis

Business Priority

Weight

Max Weighted

Score

Send report of outstanding activities to line

managers via email

Rescheduling ability

Time Tolerance feature

A.4 Work OrdersGenerate different types of work orders

based on the requirementsWork Order status tracking

Include work order information as

requested

Include the work order functionality as

requested

A.5 Reporting and History Management

Track History data of Maintenance

Generate the required reports for

maintenance

A.6 Integration

Integration with Fixed AssetsIntegration with SAP Materials

Management

Integration with SAP project systems

Integration with SAP Accounting module

A.7 Flexibility and Additional Features

Flexibility in changing processes

Additional features

A.8 Sizing and Performance

Impact on Database growth

Data Migration to SAP-PM

Total 0 0 0 0

A. Plant Maintenance Functional (20%)

Documents

Fin & Tech Eval Sheet 2 V0.1