REQUEST FOR PROPOSAL FOR SELECTION OF TOTAL …excise-bihar.gov.in/Notices/RFP-IEMS-2015-02.pdf · 1 Request for Proposal Datasheet ... Addressee and address at which proposal in

RFP for Selection of Total Service and Solution Provider (TSSP) for Integrated Excise Management System – Volume II

REQUEST FOR PROPOSAL

FOR

SELECTION OF TOTAL SERVICE AND SOLUTION PROVIDER (TSSP)

FOR

INTEGRATED EXCISE MANAGEMENT SYSTEM

VOLUME II

Ref No: BSBCL (IEMS)-2015/01

BIHAR STATE BEVERAGES CORPORATION LIMITED

RFP for Selection of Total Service and Solution Provider (TSSP) for Integrated Excise Management System –

Volume II

Integrated Excise Management System 2 | P a g e

Table of Contents

1 Request for Proposal Datasheet ......................................................................................... 4

2 Scope of the Project ........................................................................................................... 5

3 Detailed Implementation and Roll-out Plan ...................................................................... 66

4 Specification of Components ............................................................................................ 67


Volume II


GLOSSARY OF TERMS

The definitions of various terms that have been used in this RFP are as follows:

“Request for Proposal (RFP)” means all three Volumes and its annexures and any other

documents provided along with this RFP or issued during the course of the selection of bidder,

seeking a set of solution(s), services(s), materials and/or any combination of them.

“Contract / Agreement / Contract Agreement / Master Service Agreement” means the

Agreement to be signed between the successful bidder and <<SDA>>, including all attachments,

appendices, all documents incorporated by reference thereto together with any subsequent

modifications, the RFP, the bid offer, the acceptance and all related correspondences,

clarifications, presentations.

“Bidder” means any firm offering the solution(s), service(s) and /or materials as required in the

RFP. The word Bidder when used in the pre-award period shall be synonymous with parties

bidding against this RFP, and when used after award of the Contract shall mean the successful

party with whom the agreement is signed for rendering of services for implementation of this

project.

“Proposal / Bid” means the Pre-Qualification, Technical and Commercial bids submitted for this

project against this RFP.


Volume II


1 Request for Proposal Datasheet

S. No Information Details

1. RFP reference No and Date BSBCL(IEMS)-2015/01

2. Non Refundable Tender Cost Rs. 10,000/-

3. Earnest Money Deposit (EMD/ Bid Security) Rs. 20 Lakhs

4. Last date and time for submission of queries for

clarifications

04 January 2016, 5:00 pm

5. Date, time and venue of pre-bid conference 6 January 2016, 3:00 pm at

Conference Room,

Department of Registration,

Excise and prohibition

Vikash Bhawan, New

Secretariat

Patna – 800 015

6. Release of response to pre bid queries 18 January 2016

7. Last date, time (deadline) and venue for receipt of

proposals in response to RFP notice

01 February 2016, 3:00 pm

8. Date, time and venue of opening of Technical

Proposals received in response to the RFP notice

01 February 2016, 3:30 pm

9. Place, time and date of Technical Presentations by the

bidders

To be intimated

10. Place, time and date of opening of Financial Proposals

received in response to the RFP notice

To be intimated

11. Contact person for queries Sh Om Prakash Mandal

Assistant Commissioner of

Excise

email: [email protected]

12. Addressee and address at which proposal in response

to RFP notice is to be submitted

Managing Director

Bihar State Beverages

Corporation Limited,

Vidyut Bhawan, Patna

mailto:[email protected]


Volume II


2 Scope of the Project

2.1 Current State Assessment

A detailed assessment of the current state of Department of Excise and Prohibition is very much

crucial for the project, which shall be the basis for various sub sequent sections of this RFP.

The current section provides the analysis of the assessment.

2.2 Assessment objectives

Objective of this stage is to assess the current state of excise system of Bihar from various

facets in order to prepare a future roadmap for implementation of Integrated Excise

Management System.

2.3 Integrated Excise Management System Technical Solution

Key performance considerations for the Integrated Excise Management System solution

architecture are given in the table below. Integrated Excise Management System Architecture

has been envisaged based on these performance consideration.

Table 2: Integrated Excise Management System Solution Architecture –

Key Performance Considerations

S.

No.

Requirement Design Strategy

1 Performance: System should be

performing to support all the

functions as per the turnaround time

requirement of the business.

The solution shall be designed in a manner that the

following can be achieved :

Modular design to distribute the appropriate

system functions on web and app server

Increase in-memory Operations(use static

operations)

Reduce number of I/O operations and N/w calls

using selective caching

Dedicated schemas for each function making

them independent and avoiding delays due to

other function accessing the same schema.

Using batch processing for resource intensive

tasks which need not be done on real time

bases.

2 Portability: The system should be

portable to all major platforms with

minimal changes (or No changes)

and appropriate testing.

Platform agnostic system to be developed with

following considerations

Use a platform to make the Application Source

Code Portable

Solution should support Database Access

Layer Portability.


Volume II


S.

No.


3 Scalability : The system should be

scalable in a manner that as

appropriate the capacity and

compute infrastructure could be

added seamlessly

The design of the system to consider future proofing

the systems for volume handling requirements

System architecture to be based on the

Information Exchange principles

The application functions to be divided logically

and developed as Modular solution

The system should be able to scale horizontally

& vertically.

4 Reliability: The system should have

appropriate measures to ensure

processing reliability for the data

received or accessed through the

application.

It may be necessary to mainly ensure the following

Prevent processing of duplicate incoming files

/ data

Unauthorized alteration to the Data uploaded

in the Integrated Excise Management System

should be prevented

5 Availability : The design of the

system should have considerations

impacting the availability factor

The solution should meet the

availability requirements

Load Balanced across two or more Web

Server avoiding single point of failure

Deployment of multiple application instances

should be possible

Distributed or load balanced implementation

of application to ensure that availability of

services is not compromised at any failure

instance

6 Security: The system should be

appropriately secured considering

the defence – in – depth principles.

Not relying only on the Network

Security, the application should

have its own access control security

mechanism.

The application system should have the following

Role based access for all the stake

holders envisaged to access and use the

system

Specific components to enable data security

Appropriate authentication mechanism

adhering to industry good practice of Password

Policies etc.

Ability to adopt other authentication

mechanism such as Electronic Signature

Certificates

Authorization validity to be ensured for the

users providing the Data to the system. Data

should be accepted only from the entity

authorized


Volume II


S.

No.


Data should be visible only to the authorised

entity

Audit trails and Audit logging mechanism to be

built in the system to ensure that user action can

be established and investigation if any can be

aided. (e.g. Logging of IP Address etc.)

Data alterations etc. through unauthorized

channel should be prevented

Industry good practice for coding of application

so as to ensure sustenance to the Application

Vulnerability Assessment exercise using

professional tools and experts

7 Cost: The system is required to be

optimized in terms of design and

development to keep a check on the

resource utilization etc. there by

helping the overall cost reduction for

the solution

Use of existing resources such as Data Centre at

Transport Department meant for Department of

Registration, Excise and Prohibition

Department,, Bihar State Data Centre and Bihar

SWAN

Use of open source frameworks with commercial

support availability

Solution should enable optimized processing in

accordance with the chosen platform of

deployment

Use of commercial license products where

certain confidence in terms of reliability and

scalability may be required. It is recommended to

consider those products which confirm to Open

System Standards. Further, appropriate

measures to be put in place to reduce the

dependency on the product specific features.

Solution should enable platform independence to

enable possible open system deployment if

required to reduce the overall cost of unit order

processing

8 Open Standards IEMS solution shall be based on open

standards and technologies. The solutions

should follow Services Oriented Architecture.


Volume II


2.4 Mobile Interface

Integrated Excise Management System mobile interface shall be based on the mobile governance

(m-Governance) strategy of Government of India. Under this strategy, Mobile service delivery

gateway has been established to provide basis infrastructure support to any State/ Centre

Government departments.

MSDG (Mobile e-governance Services Delivery Gateway) provides an integrated platform for delivery

of government services to citizen over mobile devices using SMS, USSD, IVRS, CBS, LBS, or mobile

applications installed on the mobile phones.

SMS Gateway of MSDG

The SMS Gateway provides common service of SMS to eGov exchange and is used to deliver SMS

based services to all citizens. SMS Gateway supports both push and pull based services wherein a

common informational services can be pushed to a group of people based on gender, location,

community etc. Integrated Excise Management System can use programmatic interface of MSDG to

push SMS to the citizen. Citizen can also request for specific information at the individual level through

pull based SMS services. Short code 51969 has been reserved by Government of India for the e-

Governance services and this code is already integrated with all the telecom operators of the country.

All the major Telecom Operators have agreed to charge the citizen according to the citizen's SMS

plan (Normally any SMS short code is charged at premium rates, mostly around Rs. 3 for each request

by the citizen).

Mobile App Store

Mobile App store shall provide the mobile applications for various platforms such as Android/ Java/

IOS/ Windows in line with MSDG policy. Mobile app shall connect to Integrated Excise Management

System through 3G/ GPRS/ EDGE/ SMS methods based on the requirements.

2.5 Application Architecture


Volume II


2.6 Data Architecture

Data architecture consists of various different and dedicated schemas for each function making them

independent and avoiding delays due to other function accessing the same schema. Data

architecture consists of the following:-

Data component list, business function and application matrix

Master data

Data security

Data dissemination

Technical implementation

2.7 Deployment Architecture

The application shall be co-hosted at Bihar DC and hence same architecture of SD shall be used for

Integrated Excise Management System. The application would be hosted on web server, industry

strength application server and database hosted on Oracle/ My SQL. Web servers and Application

servers would be hosted on Red Hat Enterprise Linux operating systems. Web server is placed in

WEB DMZ, application server and database servers are placed in Secured Zone. Systems like Email

Arc

hit

ect

ure

Deptt External Systems

Reusable components from Existing Software

Service Monitoring Layer

MIS / Reports

Application Layer

Security Layer

Dat

a C

en

tre

Net

wo

rk

Analytics / BI

GIS

Cyber Security Data Security PKI DSC

Core Application

VMS

Back Office

Depot Management

Inventory

Other Features

De

par

tme

nt

Use

rs

Service DeliveryChannel

Portal/ VPN

PC/ Laptop

Mobile

Kiosk

Acc

ess

Man

age

me

nt

Serv

ice

Ori

en

ted

Arc

hit

ect

ure

Serv

ice

Inte

grat

ion

Data

Rights

1 n

SSL


Volume II


servers would be connected to the Integrated Excise Management System through internal LAN

network of Integrated Excise Management System Infrastructure and will not be directly connected to

the Office LAN. DC Operator shall perform all maintenance tasks such as regular upgrades and

patches to various DC software, hardware and service level management. It is the responsibility of

TSSP, to accordingly perform related migration activities of the Integrated Excise Management

System application as per the latest upgrades done to DC software.

Some of the Key considerations for designing the deployment architecture based on the non-

functional requirement of the architecture are given below

Scalability

All components of the Integrated Excise Management System must support scalability to provide

continuous growth to meet the requirements and demand. A scalable system is one that can handle

increasing numbers of requests without adversely affecting the response time and throughput of the

system. A scalable Integrated Excise Management System shall easily be expanded or upgraded on

demand.

The Integrated Excise Management System shall support both vertical (the growth within one

operating environment) and horizontal scalability (leveraging multiple systems to work together

on a common problem in parallel) by the use of Load balancers and High available servers etc.

Scalability is important because new component is constantly being deployed, either to replace

legacy component or to support new missions.

Increased scalability is also provided by load balancing requests across the 'clustered' servers in

future as and when required.

Modular approach of application development for Integrated Excise Management System makes

it scalable to future requirements. The Integrated Excise Management System should be scalable

enough to accommodate the following:

The Integrated Excise Management System shall be deployed across the state. The indicative

project locations has been provided as below:

Location Name

Number

Number of Users

Secretariat 01 05

Department of Excise and Prohibition HQ 01 50

District Headquarters 38 200

Sugar Mills, Distilleries, Breweries and Bottling Plants 38 50

Total 78 305

Table 7 Integrated Excise Management System project locations and approximate number of

users

1 Growth in number of internal users is minimum and for system design considerations 5%

increase in number of users per annum is considered.

2 Expected numbers of external users shall be all the citizens of the State

3 Expected numbers of concurrent users during the first year are 80 internal users.

4 Concurrent users are expected to grow @5% per annum


Volume II


5 The transaction volumes for each service shall be given in RFP. The volume of transactions

is expected to grow at a compound rate of 15% annually. The solution should be scalable to

meet the load of increased growth of transaction volumes for a minimum of six years.

Availability

All the components of the Integrated Excise Management System must provide adequate redundancy

to ensure high availability of the Integrated Excise Management System applications. Designing for

availability assumes that systems will fail, and therefore the systems are configured to mask and

recover from component or server failures with minimum application outage.

Following are the features of Integrated Excise Management System to make it highly available

Load Balancing at both Web and application level

Link Load balancing at Gateway level in future as the case may be for DC

Deployment of multiple application instances

All the components of the Integrated Excise Management System (Both IT and Non IT) shall

support Simple Network Management Protocol (SNMP) version 2 or higher protocol for the

effective Monitoring and management.

Integrated Excise Management System needs to be available as per SLA of the planned up time.

Interoperability

The entire system / subsystem should be interoperable, in order to support information flow and

integration.

Operating systems and storage technologies from several suppliers shall interact well with each

other.

Integrated Excise Management System to support the open standards based solutions such as

XML, XBRL, LDAP, SOA, etc. where information/data can be ported to any system, whenever

desired.

Security

Integrated Excise Management System would adopt the security approach of the Bihar State Data

Centre. In addition to the above Integrated Excise Management System shall also have application

level securities such as role based access etc to prevent misuse of the system.

The Integrated Excise Management System must provide an end-to-end security blanket to protect

Integrated Excise Management System applications, services, data and the infrastructure from

malicious attacks or theft from external (through internet) and internal (through intranet) hackers.

Integrated Excise Management System shall use SSL/VPN technologies to have secured

communication between Applications and its end users.

All the system logs shall be properly stored & archived for future analysis and forensics

whenever desired.

Well defined access control to maintain application level security: Role based access, appropriate

authentication mechanism and denial of access through unauthorized channels

Manageability


Volume II


The Integrated Excise Management System is designed in an efficient way to ensure an easy

maintenance. Integrated Excise Management System shall have following features to meet the

manageability goals.

Ease of configuration, ongoing monitoring, and failure detection that are vital to the goals of

scalability, availability, and security.

The design shall be able to match the growth of the environment and provide facility for

remote management.

Solution shall be easy to manage with standard and supported tools.

The system shall have online tools for application, network and Support Desk management.

The solution shall lend itself to work closely with Support Desk systems and provide simplified

means for user management, logging, and tracking.

Performance

Performance is an important parameter in the overall architecture. Following are to be considered

as part of performance improvement for Integrated Excise Management System

Use of Load balancers at various server levels (Web servers and Applications servers): load

balancers not only improves the performance by intelligently managing load, but also tracks the

server performance.

Redundant servers in active-active mode with clustering and load balancing.

Integrated Excise Management System being a web based solution where services are offered

through internet, use of Link Load Balancers is very much essential. Link Load Balancer shall

provide following advantages to Integrated Excise Management System.

Can manage multiple ISP links to the data centre automatically, choosing the best-performing

link to ensure compliance with service-level agreements

Can intelligently compress traffic, reducing WAN link bandwidth for lower ISP costs--and

cutting down on bandwidth bottlenecks for faster application delivery.

Can also manage the failover mechanisms for uninterrupted services.

Use of external caching Tier, which Depending on the type of HTTP response being made, they

may decide to store the object for future use. As soon as another request is made for the same

object, the Caching Tier may decide to reuse the previous object; saving a round trip to the next

layer also it quickly receives responses from the Web Tier, freeing it up very quickly, and can

then slowly drain that response to the user.

Usage of Gigabit Ethernet for a very fast, efficient and reliable communication amongst the

devices.

Loose coupling of various layers/ tiers enabling quick recovery time in case of any failures.

Use of Internal cache tier to Caches objects closer to the Application or Web Tiers

Clustering of servers

Data Center

As discussed in previous sections, Integrated Excise Management System shall be co-hosted in

Department of Registration, Excise and Prohibition Data Center. As the DC has adequate access

control mechanism, same would be followed for the security of all the Integrated Excise Management

System data centre equipment.

The IT infrastructure for Integrated Excise Management System is proposed taking into consideration

the IT infrastructure at DC. Details of the same shall be incorporated as part of RFP.


Volume II


DC will provide the following infrastructure for Integrated Excise Management System

Common infrastructure (Space, Power and cooling, etc.)

Security (IPS, Firewall, Antivirus)

Load balancers

Presentation, Application and Data base layer infrastructure (Web servers, Application Servers,

SAN, DBMS, etc.)

Basic services: Patch up gradation, Server maintenance, backup services, etc.

Remote Management

TSSP shall have to provide Content Management Server and additional disks for SAN.

Disaster Recovery

DR site of DC shall be used for Integrated Excise Management System as and when it comes. Till

that arrangement is in place, to avoid data loss, incremental backups should be taken daily and

placed in a different site. Backups should be taken on external media (tapes) as per following

schedule.

Table 8 Indicative Data Backup Frequency

S No

Backup Type

Frequency

Storage Period

No of Backup

Tapes

Location of Storage*

1.

Incremental

Daily

1 week

2

1. Onsite

2. Offsite* 2.

Incremental

Weekly

1 month

2

1. Onsite

2. Offsite* 3.

Full backup

Monthly

1 year

2

1. Onsite

2. Offsite* 4.

Full backup

Yearly

Permanent

2

1. Onsite

2. Offsite*

* Offsite storage location will be specified at a later date; however the location will be within the state

of Bihar and will be outside of the city in which Data Centre is located.

2.8 Network Architecture

Locations shall be connected to the nearest Point of Presence (PoP) through a last mile connectivity

eg. Leased Line/ OFC/ RF. For the locations not feasible to be connected to SWAN shall be

connected to DC through other arrangement such as BSNL Leased Line/ BSNL WiMax / BSNL

VPNoBB/ Private ISPs. The department shall provide connectivity for all of its offices.


Volume II


2.9 Security Architecture

Integrated Excise Management System security shall be covering all aspects at all levels of entry and

exit into the system to ensure that only authorized users/ authorized networks connect to the system

and only legitimate traffic is allowed at the network. While it is already mentioned that Integrated

Excise Management System shall use the DC security architecture, it is worthwhile to mention the

various security features. Following diagram depicts various levels of security adopted for Integrated

Excise Management System

Figure 1 - Integrated Excise Management System Security Architecture

Key considerations at the user level

a. Single Sign On through user name and Password

b. Authentication of applications and attached documents to be performed using Digital

Signatures

c. Role based access to the services, transactions and data

d. Digital Certificate to be used for submission of applications and signing the Documents

The information assets and operations will be governed by a well-defined Information System

Security policy in order to ensure confidentiality and integrity of the system.

The security architecture recommended includes the following components:

I. Authorization

Authorization is the means of establishing and enforcing user rights and privileges. Access policy

needs to be in place including Access Matrix to clearly demarcate which modules/ functionalities are

accessible to which set of users. During operation, the access control rules would be applicable. The

process of updating the access matrix and rules should be easy to manage as it is a continuous and

regular activity in such a scenario.

II. Authentication


Volume II


Authentication is the process of verifying and establishing the identity of the user. Authentication for

accessing information would be of various types

User name and Password for basic information

User name, password and Personal Data validation for particular information like Caveats

Class II digital signature through USB Token for approvals and confidential data

Multifactor authentication.

III. Policy

Information security policies should be well defined to safeguard the information resources.

Appropriate infrastructure should be in place to support these security policies and should be diligently

implemented across the system. The policies have to be regularly updated and adapted in alignment

with the changing external as well as internal factors. External factors could be change in the

government compliance laws whereas internal factors could be an organization wide decision of

adopting a new information security standard, for example adopting ISO 27001 standards. Detailed

security Policy details are mentioned in section for Technology Standards.

IV. Guidelines

In addition to the established information security policy, explicit set of guidelines should also be

prepared. These would include the dos and don’ts for the stakeholders using the Integrated Excise

Management System. The guidelines should also be regularly updated in alignment with the changing

information security policies.Scope of Work

2.10 Broad Scope of TSSP

The TSSP is expected to implement the project “to create an end to end Automated system

for Excise department through IEMS application catering to:

i. Design and implement Vehicle management system through e-locks and GPS

ii. Design, Develop, Commission and Maintain IEMS Portal

iii. Creation of Electronic Database of all Licensees, Chelan, Permits & Transactions in the

State.

iv. Online monitoring of Molasses, Spirit and Liquor movement in supply chain by

computerizing Online all types of permits, transport pass etc.

v. Maintenance of real time inventory Factory, Distillery, Blender, Brewer & Bottler level

across the supply chain.

vi. Integration of excise system for Import and export permit validation in real time through

modern Check post system.

vii. Integrated Surveillance System at all Check posts in Bihar. With Automatic Scanner &

BOOM Barrier System at Distilleries and Bottling Plants.

viii. Record management of all manufacturer’s at all levels as per excise law to be

maintained in real time for effective control including generation of reconciliation reports

of Raw Input/ Finished Goods Output. All requisite excise records which a manufacturer

is supposed to maintain would be through this system including the process stock and

wastage at various stages.


Volume II


ix. Provide Training to government officials to effectively operate centralized applications

for delivery of e-From services

x. TSSP shall be responsible for maintaining Excise Departmental Website & content

updating for the contract period.

xi. Capacity building programme to be carried out throughout the term of the contract to

accommodate department user and field officers.

2.11 IEMS Application Layer Basic Requirement

i. IEMS modules elaborated above is for reference only, the TSSP needs to understand

the requirement and do necessary modification.

ii. All users of the Department of Excise and Prohibition, Government of Bihar will

access the Applications through a centralized Web Portal.

iii. The Application must be customized for the solution which would follow all the

Standards Protocols for like HTTPS and SOAP for communication between

stakeholders and data centre.

iv. All the service delivery components would be exposed through XML Web Services

which internally performs the business logic to process the service through web

services to be exposed to the users.

v. Depending on the kind of request coming in from the users, the user is passed on to

all service or to reporting and business rules service or to workflow service.

2.12 Application Portability

1. The Web Portal contents will be in English & Hindi (Bilingual).

2. It must be compatible with Multiple internet browsers such as Internet Explorer, Mozilla

Firefox, Google Chrome, others.

3. Visual identity of website, Page layout, Graphics, Buttons & Icons, Typography and

Colours will be done in consultation and with the department.

2.13 User Interface

Page layout

1. A consistent page layout must be maintained throughout the website.

2. The placement of navigation & text elements should be uniform across the website;

3. Most important elements should be visible on the first screen and should not go inside

a scroll;

4. Focus should be laid on a few important elements of the page, so that the visitor may

be guided to those portions which deserve most attention. In case a lot of elements in

a webpage are blinking / flashing or highlighted, the visitor will not be able to

concentrate on the essence of the page;

5. Clear demarcation of various components so that the information of one kind is grouped

together and presented visually at one point in the page;

6. Active help ( on all pages) with mouse hovering

Graphics, buttons & icons

The graphic elements like buttons & icons should be simple & their meaning and symbolism

should be self-explanatory and relevant. This simple means that an icon should look like

what it means. Also the buttons & icons should be large enough to be distinguishable on a

high resolution monitor


Volume II


Typography

The content of the site should be readable with default standard fonts.

Use of images – should be limited and the size & format of the image should be

such that the load time is minimized while the display quality is maximized.

Colours – there must be adequate contrast between text and background.

2.14 Payment Gateway

A payment gateway is operation with the Department which supports all the leading

credit/debit cards all the leading banks. There must be provision of Payment Gateway

Interface services by forwarding the payment related operations to the gateway service

provider for payment through credit card, debit cards or direct debit through ECS or RTGS

etc. facilities.

2.15 SMS Gateway

1. The IEMS application needs to be integrated with SMS gateway with both push and

pull services enabled.

2. All Requests/submission/complaints/calls/grievances put forward by user should be

confirmed by SMS and email to the user and any status change shall also be updated

to the user by SMS and email.

3. User should able to query on status by using pull services.

2.16 Phase I: Vehicle Management Module

2.16.1 VMU Description

1. The VMU should be of reputed make, time tested, widely used as well as, as per the

specifications listed out by Department of Excise and Prohibition, Government of Bihar.

2. The vehicle mounted unit must have Electro Magnetic Interference (EMI) / Electro

Magnetic Conductance (EMC) approval from ARAI (Automotive Research Association

of India) permitting use on Petroleum Tank Lorries.

3. Any technical conditions stipulated by PETROLEUM & SAFETY ORGANIZATION

PESO for installation of the vehicle mounted unit are in the Tenderer’s scope.

4. The selected vendor to make provision for maintaining / repair of all Vehicle Mounted

Units/ equipment.

2.16.2 Implementation model of E Lock & GPS Device

1. For Vehicle used for Ethanol, Molasses or Spirit movement within the State of Bihar (

i.e. both start & ending point in Bihar)

2. For Vehicle used for Ethanol, Molasses or Spirit movement from Bihar to another State

within India

3. For Vehicle used for Ethanol, Molasses or Spirit movement from any other state to

another State within India.

2.16.3 Implementation model of Only GPS Device

1. For Vehicle used for Ethanol, Molasses or Spirit movement from any other State within

India to Bihar.


Volume II


2. For Out to Out to vehicle carrying Ethanol, Molasses or Spirit movement.

3. For Vehicle used for Ethanol, Molasses or Spirit movement from any other state to

another State within India.

4. Movement of trucks carrying Bottled Liquor from Bottling Plant to BSBCL Depot

5. If a truck is entering Bihar from outside and is already fitted with a GPS, the system

shall be able to track the movement based on GPS ID of the device fitted on the truck.

2.17 E-Lock

1. All the distilleries, breweries, bottling plants, sugar mills etc are required to fit the

tankers and vehicles carrying Ethanol, Molasses, Spirit or finished products (Liquor

Bottles, Cartons having liquor bottles) with the E-lock system at their own cost. The

bidder, however, has to get the locks fitted and integrated into the system through its

subcontracted agency.

2. The vehicles carrying liquor bottles have to be container shaped with a provision to fit

E-locks.

3. The locking mechanism along with GPS Device Should work as one unit.

4. Any form of tampering or forceful breaking of locks should be automatically notified to

the server.

5. The e-Lock should be mounted at all inlet and outlet point of tanker

6. All Locks should be integrated with spring chain mechanism

7. All equipment and accessories should be industry class and rugged.

8. Below figure is a relative view of the requirement however the bidder is expected to

propose a full proof & rugged system.

9. Facility to punch in numeric lock code received from server.

10. The e-Lock shall have in-built battery support for minimum 24 hours with internal

rechargeable battery as well as external Battery support either 12V DC or 24 V DC from

vehicle battery

11. Emergency Unlocking feature should be available with proper clearance from

Department of Excise and Prohibition, Government of Bihar, for which operating

procedure has to be predefined and agreed upon with Department of Excise and

Prohibition, Government of Bihar and the same needs to be define in the system.

12. E-Lock should send below parameters at least to server at all times:

I. Lid Open

II. Lid Closed

III. Lock Open

IV. Lock Close

V. Any tampering attempt to e-Lock

VI. Remote diagnosis of e-Lock

VII. Any other as proposed by the Bidder


Volume II


The bidders have to make a Proof of Concept demonstration for the department to understand the

effectiveness of the E-Locking system. All the cost for bringing in equipment and logistics required for

the demonstration shall be the borne by the bidder.

2.17.1 E-Lock Process flow diagram

2.17.2 GPS Device

1. The GPS receiver & other accessories to be supplied and installed as per the offered

SMS request to open for Tanker Load send from

registered Mobile number/registered email to

server

6 to 8 digit One Time Password Received from Remote Server

to open lock/LidLoad of Tanker & Close Lid

Remote Server automatically detects Lid closed or SMS

request to closeTanker Lid/Lock send from registered

Mobile number/registered email to server


to open lock/LidLock Lid

Tanker Moves to destination

SMS request to open for Tanker Unload send from

registered Mobile number/registered email to

server


to open lock/Lid

Unload of Tanker


Volume II


technical solution shall be tropical zed and shall conform to all CCITT Wireless

Standards and relevant Indian/International standards for vibration & shock/Noise, Dust

etc.

2. The GPS Unit shall be housed in locked metal enclosure such that it can be fixed on

the dash-board of the vehicle with necessary opening for egress & ingress of cables,

antennas etc. The GPS Receiver shall have required display to note the status/alarm,

interface for audio, antenna, USB–II, RS-232 C etc.

3. The GPS Receiver shall have slots to insert & operate any valid tri band /Quad band

GSM TSSPM with GPRS facility to transmit available GSM data to designated Server

of the BCCL for further processing.

4. The GPS Receiver shall have the facility to reset system both locally and remotely by

SMS Command.

5. Appropriate loop/suitable antenna shall be connected securely to GPS Receiver on the

dash-board of vehicle to avoid any eventual damage to the system.

6. The GPS receiver shall have in-built battery support for minimum 24 hours with internal

rechargeable battery as well as external Battery support either 12 V DC or 24 V DC

from vehicle battery.

7. The GPS Receiver Unit shall be supplied in complete with all associated tools & tackles

to function along with valid TSSPM with GPRS features.

8. GPS Receiver unit shall have capability to record data during GPRS signal-blind-zone

&transfer data as soon as it enters the GRPS signal zone.

9. BSBCL shall arrange for all Valid TSSPM with GPRS facilities for insertion/function to

GPS Receiver on formal request of Service Provider and the rental for all such shall be

fixed as per current tariff of Service provider. Service Provider shall indemnify

Department of Excise and Prohibition, Government of Bihar/Nodal Agency against loss

of TSSPM & its misuse.

10. GPS Receiver shall have location accuracy of <= 5 meters for Vehicle/Truck.

11. All the GPS Receivers are supposed to work under extreme environment of coal mine

conditions of noise, vibration, shock, dust, humidity etc., hence GPS receivers shall

conform to MIL specification :MIL-STD 810 F or relevant Indian Standard.,. etc.

12. The GPS receiver shall be mounted with vibration proof Mounting Brackets.

13. The GPS Module shall be integrated into the System to capture the current location of

the vehicle and Speed and the same will be communicated to Server using GPRS link.

14. The trucks not having pre-fitted GPS and entering Bihar from any of its borders shall

be fitted with the GPS devices at the entry point by collecting a fees on cost plus basis.

15. The device shall be unmounted when the truck exits the Bihar borders.

16. Rules shall be defined by the department regarding time limits between entry and exit.

2.17.3 Vehicle Management System

1. Minimum 180 days (history) data log on the Server. And, therefore, server size be

sufficient enough to handle data transferred from vehicle on GPRS network

continuously. The interval will be every 3 minutes in running conditions. In off condition

and / or halt condition – no data transfer but the last position data shall be available.

2. Multi-level login facility to be provided with proper authentication and privileges.

3. Audit trail: Log of all administration actions as well as all user logins shall also be

maintained.

4. Alarm / Alert on special message from VMU in case of accident / malfunctioning status

of VMU.


Volume II


5. Emergency Alert to VMU shall be provided in the form of LED alert.

6. Velocity and direction monitoring.

7. User friendly GUI.

8. Graphically display the vehicle position on a digitized map with different levels of zoom

9. Geo-fencing of loading and unloading locations within a radius of 15 metres from the

boundary of the loading and unloading locations.

10. Animated Icons in different colours to represent vehicles

11. Display Vehicle Registration no., Driver details and other details on click of Mouse over

the vehicle icon.

12. Graphically display of the route on a digitized map

13. Configure databases based on user requirements. Access to designated administrator

to add, modify, delete vehicles and their related details.

14. The vendor server should be capable of capture vehicle-wise trip details, the trip details

for all dispatches Departmental Application integrated system.

Fleet Management Master Database containing at least below

Sl.

No.

Description Sl.

No.

Description

1 Vehicle Details 2d Driver’s Photo

1a Vehicle Registration number 3 Owner’s Details

1b Engine no. 3a Owner’s name

1c Chassis no. 3b Repair History

1d Capacity (kl) 3c Mandatory clearance status

1e Model 3d license validity date

1f Year of Manufacture 3e RTO

2 Driver’s Details 3f Calibration due date

2a Driver Name 3g Insurance policy details

2b Driver License Number

2c Driver License Issuing Authority

Note: Any addition to the data base shall be informed along with LOI

1. Vehicle Database Trip-wise Details

2. Backup and restoration facility of older data.

3. The Tender once finalized will be covered under Intellectual Property rights of Bihar

Government.

4. Performance Monitoring Reports of Lorries/Tankers on the following parameters to be

provided to all users like BPCL officers as nominated/Dealers (consignee)/

Transporters, the reports needs to be further based on access provisions of BPCL

officers. The access provisions for each officers shall be categorized by their roles and

needs to be approved by the Department :

1) VLTS Uptime % (Vehicle wise/location

wise/Region wise/All India wise)

2) VLTS equipment under Repair


Volume II


3) VLTS Not giving signals 4) No. of Trips per day/ per week/per

month.

5) No. of VLTS tampered. 6) Quantity Delivered (KL) day/month)

7) Distance covered (KM)day/month) 8) No. of work days –Daily.

9) Average distance (KM) per trip-Daily/weekly. 10) Average Delivery time/RO

11) Average Trip Time/RO 12) Total Deliveries- Monthly.

13) Total Distance Travelled 14) Total no. of Trips

15) Daily Deliveries 16) Cumulative Deliveries

17) Route Report 18) Speed Violation

19) Route Violation 20) Accident /Hijacking alerts

5. Apart from route report generated in a report form, the report shall have a link showing

graphical representation on digital map, the standard route and actual route followed.

Report should be selectable based on Source and destination type and for specified

durations, Lorry wise etc. Software should have facility to transpose report to

EXCEL/WORD/PDF format.

6. The report formats as specified in the Tender document are to be configured in the

system.

2.17.4 DIGITAL MAPS & MAPPING:

Department shall procure and provide Digital Maps to the TSSP. However, all the features and functionalities based on Digital Maps shall be the responsibility of the TSSP.

GIS MAPS to have the following features:

1. Play back and live movement management of object on map for real time object

tracking experience Department of Excise and Prohibition, Government of Bihar

authorized or specified web users who receive the location information from the Tank

Lorries spread across the country will be connected with VMS server.

2. Digital Map of delivery areas with roads, important landmarks, other features, with

names shall be provided. Standard routes from Depot to Retail Outlet / Consumer outlet

shall be mapped, with latitudes, longitudes ascertained and place names associated

with the coordinates for all important landmarks along the route. (Mapping should

earmark specified zones of authorized movements / stops or prohibited area of

movement)

3. Digital Map customization as required i.e. the map of each location area will show:

a. Source/destination Points for Spirit

b. Assigned routes of tanker lorries

c. Location of depots / terminals/Warehouse

d. Other important landmarks e.g. Post Office, Hospital, Temple, Churches,

Mosques, Bridge, Railway crossings, other Petrol Pumps etc.

4. Create and link to Records of vehicles by number, dealer name etc.

5. Mapping software functions should include: Zoom (min. 3 levels), measure distances,

show layers, symbols, link to database, show position of tanker lorry on map etc.


Volume II


2.17.5 Route Definition

All the routes to be taken by the Lorries from Source to destination covered by the location

shall be surveyed properly by the vendor. The routes shall match with the roads shown in

the digitized map and prominent landmarks must be plotted on the map. Location of supply

points/ and Retail Outlets/Direct customers must be shown with prominent colour icons.

The survey should be done preferably with the help of an automatic GIS data logger.

Accuracy of latitude/longitude, correlating the same with ground features and geo-fencing

of the routes is of paramount importance.

Successful Vendor has to go to all new Locations for physically Mapping Source to

Destination and the landmarks en route.

2.17.6 Required Alerting Features:

Following audio and/or visual alerts must be generated by the system on mobile or on

screen, along with alert email to designated officers in field & HQ and also alert at Control

room at HQ.

1. Movement Alert: In case transport vehicle stops more than 5 minutes.

2. Geo-fence Alert: Instant SMS/e-Mail alert in case a transport vehicle deviates from the

predefined route.

3. Park Fence Alert.

4. Top Speed Alert.

3 Phase II: Integrated Excise Management System

3.1 Supply Chain management

As per new policy, the liquor shops shall be owned and operated by BSBCL. The retail software

is being developed separately. However, supply chain till the depot level is under the scope of

work of the TSSP. The system shall be able to cater to this need by providing an end to end

supply chain management system. Basic information related to the existing supply chain till depot

level is being provided. However, TSSP shall undertake requirements gathering separately and

reply only on the information collected requirements gathering.

3.1.1 Categorized Unit

This shall be the first layer of categorization for management of Supply Chain which

consists of below categories:

Category 1 : Sugar Factor

Category 2 : Distillery

Category 3 : Blending & Bottling Plant IMFL

Category 4 : Blending & Bottling Plant for Beer

Category 5 : Blending & Bottling Plant FMFL

Category 6 : BSBCL Depot

Cat 1A : Sugar Factory Old Crushing Technique

Cat 1B : Sugar Factory New Crushing Technique

Cat 2A : Distillery ( Molasses Based)

Cat 2B : Distillery ( Grain Based)


Volume II


Cat 2B1 : Distillery ( Grain Based – Mixed Grain)

Cat 2B2 : Distillery ( Grain Based - Potato)

Cat 2B3 : Distillery ( Grain Based - Rice)

Cat 2B4 : Distillery ( Grain Based - Maize)

Cat 2B4 : Distillery ( Grain Based - Malt)

Cat 2B4 : Distillery ( Grain Based - Wheat)

Cat 2B7 : Distillery ( Grain Based - Barley)

Cat 2B8 : Distillery ( Grain Based - Sugarcane)

Cat 2B9 : Distillery ( Grain Based - Sugarbeet)

Cat 5A : BSBCL IMFL Depot

Cat 5B : BSBCL IMFL Beer Depot

3.1.2 Inflow of Raw Materials/Goods

For each selected category list of inflow of materials needs to be captured in a form along

with necessary permits/approvals for obtaining the raw materials. Below is an illustration

and shall be subjected to change as on when there is inflow of RAW material category

changes.

Category 1: Sugar Factory

The sugar industry is of a seasonal nature and operates for 120 to 240 days in a year,

beginning from early November and ending on May or June. The chief raw material for

sugar industry is Sugarcane.

Category 2: Distillery

Raw Material for Distillery can be broadly classified into Molasses/Gain/Mixed Grain

3.1.3 Stock of Raw Materials/Goods

Category 1: Sugar Factor

This shall capture total stock and change in stock of Sugarcane based on inflow outflow.

3.1.4 Production of Materials/Goods


This shall capture amount of Sugarcane moved from Raw material Stock to Production

and also from Production to Finished product as molasses, ethanol and Bagasse

Sugar industry is a major supplier of molasses for alcohol and ethanol as additive to fuel

(oil refineries are allowed to add 5% ethanol in fuel). Bagasse is used for power

generation as well as paper production

Category 2: Distillery

3.1.5 Stock of Finished Materials/Goods


Daily and Summary Stock details of Molasses, Ethanol and Bagasse


Volume II


3.1.6 Outflow of Materials/Goods


Daily and summary outflow details of Molasses, Ethanol and Bagasse needs to be

captured in the system. Each Tanker load of Molasses should be mapped to

corresponding process

Allotment of Molasses

Permit

Molasses Transport Pass

VMU validation

Sample attributes of Molasses

3.1.7 Sample attributes of Sugar Factory

Sample: Attribute form for Movement of Molasses, with geo tagging:

Sample: Attribute form for Allotment of Molasses:

3.1.8 Sample attributes of Distillery

Sample: Attribute form for receiving of Molasses at Distillery, with geo tagging


Volume II


Sample attributes of Fermentation at Distillery:

Sample attributes of Allocation of Rectified Spirit:

Sample attributes of Movement of Rectified Spirit:


Volume II


3.1.9 Sample attributes of IMFL/Beer:

Sample attributes of Receiving:

Sample attributes of Production of Liquor:

Sample attributes of Supply of Liquor:

Sample attributes of Movement of Liquor:

3.2 Core Excise Application

3.2.1 Master Data Build-up

1. TSSP as a vendor will be responsible for build-up of master data.

2. Currently no structured digitized data is available with the Department of Excise and

Prohibition, Government of Bihar.


Volume II


3. The Department will provide all the required data in the hard copy or in the digital form

to the TSSP. The TSSP will have to identify and filter such data with the help of Excise

department for associating the data as indexing parameters for the documents archived

in the repository.

4. TSSP is responsible to migrate and digitize the data necessary for successful running

of the new proposed system.

5. The TSSP will be responsible for safe handling of the documents back to the

department. TSSP is responsible for all the data feeding operation and maintenance of

records at its data centre for a period of 5 years.

6. Final validation should be done by department senior officers by authenticating the

checklist for migrated /created data.

3.2.2 Department of Excise and Prohibition, Government of Bihar Departmental

website

1. TSSP shall be responsible for creating the contents & complete functional attribute of

the Departmental website

2. TSSP shall maintaining Excise Departmental Website & content updating for the

contract period.

3. The Departmental website shall be integrated with SSDG “ State Portal”

4. Different Categories which shall be covered on Home Page:

3.2.3 Automation of Existing Processes

1. e permit

2. e import/export

3. e forms ( workflow based)

4. e- Supplier liquor license issue/renewal

5. e Registration

6. e Allotment

7. Case Management

8. BSBCL Depot Management

9. Recovery

10. Loss

The various allotments done by Department of Excise and Prohibition, Government of Bihar

shall undergo an e-allotment process, for example allotment of Molasses, Spirit, Mahua and

others.

3.2.4 MIS Reporting Modules (integrated with BSBCL)

Inter active Dash-boarding within build analytics on different KPI’s.


Volume II


3.2.5 Transactional Module

The transaction module should cover at least below parameters:

Field Description Description

Excise Tax Information

Excise Block The following information is related to Excise Registration for an Inventory

Organization Location which is of Manufacturing or Trading organization.

If No Values are entered in this block, then the Organization Location is

considered as Trading organization.

Excise Range Details of the Jurisdictional Excise Office of the Organization can be

entered in this block. Values given in this field will be taken while printing

all Excise related documents.

Excise Division Details of the jurisdictional Excise Division Office of the Organization can

be entered in this block. Values given in this field will be taken while

printing all Excise related documents.

Excise

Registration/License

Number

Excise Registration/License Certificate Number can be entered in this

field. This information will be taken while printing all Excise related

documents.

Excise Zone This is an additional field provided where in the user can record some

information which he needs to print in all excise related documents.

Excise Region This is an additional field provided where in the user can record some


Excise Circle This is an additional field provided where in the user can record some


Excise Collectorate Details of the jurisdictional office of the Excise Commissioner of the

Organization can be entered in this block. Values given in this field will be

taken while printing all Excise related documents.

Customized dashboards

•Executive dashboards can be quickly and easily customized to present just the information end users need.

KPIs

•Prepared and customized Key Performance Indicators (KPIs) provide valuable drill-down capabilities to fully examine data till last level

Gauges

•Gauges offer visual snapshots of performance at a global or local level.

Advanced tree map analysis

•Tree maps offer quick, easy-to-read, graphical representations of many areas of analysis such as highest and lowest profitable part produced.

Real-time interactive reporting

•Thousands of reports assist in evaluation of various areas of your business, including labor utilization, production hours, forecasting, cash analysis and more.

Business Activity Monitoring

• Business Activity Monitoring module can keep track of business critical data and automatically send notifications and exception messages.


Volume II


Field Description Description

EC Code Use this field to enter Excise Control Code of an Inventory Organization

Location. This would be printed on all the documents that are required

under Excise Rules.

Excise Invoice at

ECC Code

Check this field in case you wish to generate Excise Invoice at Master

Organization level.

In case you have multiple internal Inventory Organizations / Warehouses

existing within the same Excise registered premises and if you opt for

Excise Invoice number generation at the Master Organization level then,

check this option child organization location.

Sales Tax Block

CST Reg. No. Use this field to enter Central Sales Tax Registration Number of an

Inventory Organization Location. This would be printed on all the

documents that are required under Sales Tax Act.

LST Reg. No Use this field to enter State Sales Tax Registration Number of an

Inventory Organization Location. This would be printed on all the

documents that are required under Sales Tax Act.

Income Tax Block

PAN No Use this field to enter Permanent Account No of an Inventory Organization


under Income Tax Act.

TAN No Use this field to enter TDS Account No of an Inventory Organization


under Income Tax Act.

WARD No Use this field to enter Ward No of an Inventory Organization Location.

This would be printed on all the documents that are required under Income

Tax Act.

VAT Reg. No. Use this field to enter VAT Registration No of an Inventory Organization

Location.

Defining Accounting Information

These accounting information are necessary for an Inventory Organization through which

all the charges related to an item on taxes will charged to respective accounting flex fields.

The user needs to define separate accounting flex fields for OSP Excise a/c, Excise

expenses, Excise receivable, Raw Material, Capital Goods, Personal Ledger Account, Bill of

entry, Scrap cost, Reversal, Customs write off a/c ..etc.

Excise Invoice Generation

To generate Excise Invoices with pre-definable prefixes (Alpha/Numeric), with complete

Excise Invoice Generation Setup. Generate Excise Invoices such as Domestic Clearances,

Export Clearances and Import Clearances.

Tax Categorization

To enable Tax defaulting and automatic calculation at the transaction line level

Supply Chain, Vehicle Management and other modules transaction details need to be in

line with their specific requirements already covered

3.2.6 VMS Reporting

Following Reports are required to be generated and these reports and real-time data can

be seen on website or on Smart Phone.


Volume II


1. Fleet summary Report (Individual & Group-wise)

2. History Report

3. Start–End Report

4. Report consisting number of trips made by individual vehicle per shift / per day / per

month.

5. Speed Report

6. Latest Location Report

7. Travel Distance Report (date-wise)

8. Stoppage Report consisting unwanted stoppage for more than 5 minutes.

9. Geo-fence Report

10. Travelling Report with point of interest

11. Input history report (date-wise)

12. History of path

13. History of path with point of interest. Detailed report is to be sent automatically at

scheduled intervals through e-Mail, Excel, PDF etc.

3.2.7 SCM Reporting

SCM reporting shall have below high level attributes which can be drilled down to unit level.

1. Procurement & Supplier Management KPIs

Number of suppliers managed / purchasing FT

Suppliers Details

2. Inventory Management & Forecasting

Quantity of Line Items

Stock turn over - finished goods

Stock turn over - raw materials

Inventory obsolescence

Average inventory value

Raw material days (if relevant)

Work in progress days (if relevant)

Finished goods days

3. Warehouse

Number of order processed in warehouse per day

Time product availability before sales after receipted

Time product availability after sales after receipted

Order picking accuracy rate

Inventory items incorrectly located

Inventory items with incorrect stock balances

Warehouse shrinkage

Total warehouse time lost

How many times is product handled

Picking productivity by pickers

Inventory accuracy rate at Item level

Average lead time in Warehouse

Number of Warehouse in network

4. Transport KPIs


Volume II


Number of order despatched per day at different level

How often trucks are fully loaded

Amount of back loading

On time deliveries

5. Products

Number of order processed per day / FTE

Average lead time for all orders

Order entry accuracy

Percentage of customer claims

Product returns

Product Damage

Invoice accuracy

Accounts receivable days

Stock Outs

3.2.8 CEA Reporting

The CEA reporting module developed by TSSP should address below performance

Indicators at least, TSSP may propose additional KPI to increase profitability/performance.

1. Revenue collections for the year/quarter/Month/Week

2. Type of fee/levy and payments made

3. KPI’s on service delivery

4. Outcome of the e-filing/eForm strategy

5. Challenger models to demonstrate change rate structure Table

6. Assessment by tax types

7. Objections and appeals for the year/quarter/Month/Week Table

8. Recovery actions Table

9. Molasses/Spirit/Alcohol seizures

10. Real-time Workforce profile by age, gender, Years of experience, designation by

District, block, Division, Sub-Division.

11. Resource Mapped to Training and development programmes

12. Budgeted collections Vs Actual Collection Vs Campion Vs Challenger forthe

year/quarter/Month/Week

13. Summary by economic categories

14. Capital estimates (Rs million) Table

15. Check gate efficiency List of Charts

16. Excise duties by items

17. Comparable economies rank based on items

18. Cost of revenue collection

19. New registration by business activities

20. refunds Chart

21. Investigation achievement Chart and Investigation by business activities Chart

22. Collectible debts

23. Trends in arrears collection


Volume II


3.2.9 Retail Inventory Management System for BSBCL owned Shops

The department is under the process of getting a retail shops management and point of sale software

designed. The software shall provide the functionality of 2D barcode based sales and inventory

management system along with MIS and Financial reporting and reconciliation. The same would need

to be integrated with IEMS.

3.2.10 Mobile Application

1. Prioritize functionality on iPhone/Android platforms

2. Must be secure, requiring IEMS member login to access information in the app

3. Manage and update existing member profile information currently accessed through the

IEMS website (e.g. My Account)

4. Schedule of lookup/alerts/approval/Informational update - Data to be provided by

Department of Excise and Prohibition, Government of Bihar.

5. Browse a categorized list of detailed lookup/alerts/approval/Informational update based on

role and Geographical area of the user

6. Access a calendar of events

7. Personalized IEMS newsfeed with user control over types of content shown

8. Static checklist based on user role.

9. Push notification of time sensitive or important information.

10. Analytics on app usage

11. Customizable dashboard/home screen that allows sorting and hiding of features based on

user preference

12. IEMS ownership of on-going content updates/management

13. Opportunity for future app expansion

14. Integration of all module of IEMS:

a. MIS

b. VMS

c. CEA

d. SCM

3.2.11 Call Centre & Grievance Module

General Features

1. The Call Centre/help desk service will serve as a single point of contact for all incidents and

service requests for the user departments. The service will provide a Single Point of Contact

(SPOC) and also escalation / closure of incidents for the user departments for the installed

gap infrastructure. The activities shall include:

2. Provide Help Desk facility during agreed service period window for reporting user

department incidents / issues / problems.

3. Real-time Stats: The general real time stats such as call duration, the caller’s number, name

(if second time caller) and so on should be available.

4. The proposed solution should have Call Back Function

5. The Solution proposed by TSSP should be VOIP based and IVR enabled.

6. The Solution should have Call routing facility, so if calls may be routed to different field

levels if required.

7. The solution should have Auto Call logging with System generated ticket for every call.

8. It should have a workflow based Grievance Management system, integrated with Ticketing

System.


Volume II


9. Provide necessary channels for reporting issues to the help desk. The incident reporting

channels shall be the following:

a. Specific e-Mail account

b. Telephone Line (Min 3 with Telephone Sets)

c. SMS

10. Implement a call logging system in line with the defined incident types as per the SLAs.

11. Creation of knowledge base on frequently asked questions to assist user departments in

resolving basic issues themselves

12. Track each incident / call to resolution

13. Provide feedback to callers.

14. Analyse the call statistics

15. Creation of knowledge base on frequently asked questions to aid users.

16. Continuous monitoring of the gap infrastructure at the DC to ensure availability as per

agreed SLAs.

17. Day-to-day monitoring shall be done with the manpower to be deployed at the various

divisions by selected TSSP.

18. Escalate the calls, to the appropriate levels, if necessary as per the escalation matrix

agreed between the TSSP and the user department. The escalation matrix shall be

developed by the TSSP in discussion with the Nodal Agency.

19. Coordinate with respective stakeholders for closure of calls.

20. Analyse the incident / call statistics and provide monthly reports including but not limited to:

a. Type of incidents / calls logged

b. Incidents / calls resolved

c. Incidents / calls open


Volume II


CRM

Call Centre software application should have a built in CRM and should have the following

features:

1. Create an exhaustive customer database, with Customer/user classification

2. Assists the agents in providing better service to customers on the basis of customer history.

3. Enabling call centre agents to assist customers with online/offline transactions, status

updating and others.

4. Reducing call handle time through built in intelligence for inbound call centre enquires.

5. Answering customer questions through an online knowledge base solution.

6. Help the call centre collaborate with different verticals of Department of Excise and

Prohibition, Government of Bihar for better operations and increased productivity.

Automated Dialler

The solution should have a good and automated call dialler and ensures every agent is provided

with a sufficient and bearable workload. Hence, a good dialler is imperative for greater

productivity of a call centre.

Monitoring and Alerting Feature:

One of the most important requirements of call centre software is that it must come with a

monitoring and alerting feature. Under this feature, the call centre manager is allowed access

to the agent’s calls and he or she can monitor them in different forms either explicitly or covertly.

Therefore, the monitoring feature helps get the best out of the agents in terms of quality and

performance.

All escalation matrix to be integrated with alert mechanism which shall be assigned to

responsible person on real-time.

3.2.12 SLA Management Tool

Predictive Analytics Module

1. Predictive analytics takes the operation data within IEMS system and turns it into actionable

business intelligence which can be used to mitigate risk, optimize future decisions and

create a “smarter” supply chain, Vehicle Management, Loss prevention, Recovery and

others.

2. The technology should provide Department of Excise and Prohibition, Government of Bihar

with a clearer view into their operations and market activity so they can foresee challenges

and respond to them proactively instead of reactively, increasing both efficiency and

profitability.

3. Predictive analytics, should give the advanced perspective that allows Department of

Excise and Prohibition, Government of Bihar to understand the past, present, and future.

With this type of data insight, Department can improve forecasting accuracy, optimize

performance, reduce costs/losses and increase revenue.

4. Need to cultivate a predictive analytics strategy to focus on higher accuracy in inventory

visibility to know which product will move in which channel/godowns to anticipate future

trend shifts.


Volume II


Integration with BSBCL

The bidder shall identify all the integration points with existing applications at BSBCL for data

interoperability. To identify the integration point Nodal agency shall facilitate between BSBCL

and the bidder, but the responsibility of identifying the integration points shall reside with bidder.

All the integration points shall be listed as CR’s and submitted to the Nodal Agency before

Integration Testing of IEMS.

1 CR No

2 CR Description

3 Criticality Submitted by TTSSP

4 Criticality Approved by Consultant/Nodal Agency

5 Duration for incorporation Submitted by TTSSP

6 Duration for incorporation approved by Consultant/Nodal Agency after consultation with BSBCL

7 Committed date by Nodal Agency & BSBCL

8 CR Closer Date

9 CR Days in Slippage

10 Slippage <= 20% : Escalate to Nodal Officer

Slippage >20% &<= 40% : Escalate to MD, Nodal Agency

Slippage >40% &<= 60% : Escalate to Commissioner of Excise

Once the CR is submitted it shall be the responsibility of Nodal Agency & Bidder to bring it to

closure without slippage.

Criticality

C1 – Very Critical (Maximum resolution time from day of submission: 5 working days)

C2 – Critical (Maximum resolution time from day of submission: 10 working days)

C3 – Normal (Maximum resolution time from day of submission: 15 working days)

3.2.13 Surveillance System for Check Post

1. Surveillance is required at all check posts in Bihar. Currently there are 5 check posts where

the manpower needs to be deployed by the TSSP.

2. This objective would be achieved by using IP cameras, E-Lock and GPS at various

locations by TSSP. IP cameras would initially operate in offline mode with a provision to

connect it to HQ control room live feed and even to trap live event from the control room.

3. The cameras would be activated through IEMS solution when the ENA/RS/alcohol is in link

with receipt record. At dispatches end the images would be trapped once the truck is at

check post and E-pass is made from the system. Again the truck image would be stored

linked with respective dispatch in the database.

4. Apart from that the camera would also capture random events which would be stored in

Local NVR, which can be downloaded by control room to control the functioning at

manufacturing end by the department. The event up to 48-72 hours would be stored in

NVR, depending on the hard disk capacity of the same.

5. Images of driver and truck number plates are to be stored in the database.

6. Live recording of each unit would be stored at local NVR which would be archived in central

database at the interval not exceeding 15 days for reference/ evidence of the department.

TSSP may plan the storage capacity at local end according to the requirement.

7. The control room should be able to visualize, monitor and store the different activities at

different check gates. The control room should be able to locate positions of vehicles as


Volume II


and when required apart from a continuous monitoring through screen blips. The TSSP

should do the necessary integration as part of the project.

3.2.14 Control Room Setup at HQ

1. The TSSP is required to setup a control room at Excise head quarter in Bihar for monitoring

of liquor movement at the Check posts of various manufacturers& monitoring activities.

2. Department of Excise and Prohibition, Government of Bihar will provide requisite space to

TSSP for set up of control room. All other arrangements and equipment to set up control

rooms would be on account of TSSP

3. Minimum 1 no of 65” LED TV should be installed at HQ, Department of Excise and

Prohibition, Government of Bihar

4. The control room would be connected to State Data centre/ DC on a min 8 Mbps

communication link.

5. Proper maintenance and adequate number of UPS and DG Set to be proposed for control

room.

6. The requisite surveillance software for viewing all check posts and its activities on single

screen should be provided by TSSP.

7. The TSSP would be responsible for maintaining at least 45 days recording of activities in

live database for each distillery and hence should plan its storage accordingly.

8. At the end of the month the backup of recording should be handed over to excise

department for their archived record and future reference

3.2.15 Roles & Responsibility:

Every user who shall access the system should privileges based on their responsibilities. A

tentative role mapping is shown below, however the TSSP is expected to submit final Roles-

Access mapping list to Nodal Agency. Based on this list Department of Excise and Prohibition,

Government of Bihar Nodal Officer shall populate various departmental & external Users.


Volume II


Tentative Roles Categorization:

Sl

No

Role Acces

s

Right

s

Access

Coverage

Approving

Authority

Software

Security

Validation

Web App

1 Departmental Roles

1.1 Controller of Excise L1 All DS IMEA

1.2 Deputy Controller of Excise L2 All L1 DS IMEA

1.3 Assistant Commissioner L3 All L2 or above DS IMEA

1.4 Superintendent of Excise L4 L3 or above DS IMEA

1.5 Inspector of Excise L5 Geographic

Area

L4 or above DS IMEA

1.6 Sub-Inspector of Excise L6 Geographic

Area

L5 or above DS IMEA

1.7 Asst. Sub-Inspector of

Excise

L7 Geographic

Area

L6 or above DS NA

1.8 Head Excise Constable L8 Geographic

Area

L7 or above DS NA

1.9 BSBCL L9 Application

Module

Specific

L3 or above DS IMEA

2 Stakeholder Roles ( ref

Section 6.5.1)

Category 1 : Sugar Factor DS

Category 2 : Distillery DS

Category 3 : Blending &

Bottling Plant CL

DS


Bottling Plant SCL

DS


Bottling Plant IMFL

DS

Category 6 : Brewing &

Bottling Plant for Beer

DS


Bottling Plant FMFL

DS

Category 8 : BSBCL Depot L9 or (L3 or

above)

11 External Entity Approved Public Information only NA NA

Sample Stakeholder Creation panel:


Volume II


Every Stakeholder identified shall have two logins

1. Owner Login – Verified by Owner’s DS

2. Authorised Representative – Verified by Representative’s DS

Sugar Mill Profile Creation:

Sample attributes of Sugar Mill Profile capture:

Distillery Profile Creation:

Sample attributes of Distillery Profile capture:


Volume II


IMFL/Beer Profile Creation

Sample attribute:


Volume II


3.2.16 Training & Capacity Building

Training program for departmental users will comprise of the below mentioned modules, with a

tentative duration for each training activity is elaborated below. The mode of imparting of all

trainings shall be electronic.

1. Core Excise Module ( 8 – 12 hrs)

2. Supply Chain Management( 8 – 12 hrs)

3. Vehicle Management Module( 12 – 24 hrs)

4. MIS Reporting Modules ( integrated with BSBCL) ( 8 – 12 hrs)

5. SLA Management Tool ( 8 – 12 hrs)

6. Call Centre &Grievance Module ( 2- 6 hrs)

7. Other Modules Training ( 2- 8 hrs)

8. Basic Computer Training( 8 – 16 hrs)

9. Content Management System for Department Site (State Head Quarter only) ( 4- 8 Hrs)

10. Tablet/PDA – Usability Training ( 4- 8 Hrs)

11. Tablet/PDA – IEMS Mobile App. ( 4- 8 Hrs)

12. The TSSP shall prepare and organize training programs to facilitate the user departments

in the efficient usage of the whole system.

3.2.17 Responsibility Matrix for Training:

Sl.

No

Task Details Responsibility

1 Content Creation for Training ( Soft Copy) TSSP

2 Content 1st Level Review Consultant

3 Content Approver Nodal Officer

4 Training Facilitation TSSP and Nodal Agency

5 Conducting the Training TSSP

3.2.18 Maintenance

The TSSP should define and indicate the preventive maintenance schedule and procedure.

Any special tools/ instruments/ equipment required carrying out the preventive and break down

maintenance of the system offered should be clearly indicated and offered to department by

the selected bidder at no extra cost.

3.2.19 Infrastructure at Field Office

Refer Annexure 5 for Hardware Specification

Site preparation and field infrastructure shall be implemented at:

Sl. No. Site ppn & Infra Details Units per

location

No of

Locations

Total Quantity

1. Check Post

Surveillance System

Box Camera 3 5 15


Volume II


Lens for Box camera 3 5 15

POE Switch 1 5 5

NVR of each Check post 1 5 5

Boom Solution 2 5 10

8- Port Managed Switch 1 5 5

1.1.1.1 Infrastructure at HQ

3.2.20 Infrastructure for Staging & Production DC

Refer Annexure 4 for Hardware Specification

The list is indicative only and not restricted to the below. This is to facilitate the bidder. Bidder should

do its own hardware sizing based on proposed solution architecture, based on Hardware sizing

details.

S. No. Item Quantity

1 Database Servers (x64) 2

2 Application Servers 2

3 Web Server 2

4 Reporting Server (x64) 1

5 Mail / Messaging Server 2

3.2.21 Indicative Project Plan and payment schedule

S No Activity /Task /Milestones

Time to

Completion

(in Weeks)

Phase I

1 Project Start T

2 Mobilization Advance to TSSP T + 1

3 Supply of Hardware required for VMS T + 3

4 Start field testing of VMS T + 4

5 Implementation of VMS T + 6

Phase II


Volume II


S No Activity /Task /Milestones

Time to

Completion

(in Weeks)

6 Requirement Study, Business Process re-engineering for best fit solution

and preparation of SRS T + 8

7 Finalization of Architecture Design of IEMS T + 8

8 Submission and acceptance of System Requirement Specifications T + 9

9 Finalization of Unit Test Plan T + 10

10 Finalization of Integration Test Plan T + 11

11 Completion of 50% Unit Test T + 12

12 Completion of 50% Integration Test T + 14

13 Completion of BSBCL Integration Test T + 14

14 Completion of 100% Unit Test T + 15

15 Completion of 100% Integration Test T + 16

16 Finalization of Staging System Test Plan T + 17

17 Completion of Staging System Testing T + 19

18 Commissioning of IT Infra at DC for FAT T + 17

19 Finalization of Production Environment readiness at DC T + 16

20 Completion pre FAT Training T + 19

21 Finalization of FAT Test Plan T + 19

22 STQC \ Govt. Empanelled Agency Quality& Security Certification T + 22

23 STQC \ Govt. Empanelled Agency Load Testing T + 24

24 Benchmarking of complete application for Hardware Sizing T + 26

25 Completion of pre FAT Validation T + 20

26 Start of Manpower Deployment T + 23

27 Completion of FAT T + 24

28 Completion of Manpower Deployment T + 24

29 Go Live T + 26

From the date of submission/completion of document/activity of by TSSP, Nodal agency has to get it

clarified and approve within 5 working days maximum. During this TSSP is expected to cooperate

with Nodal Agency.

S No Activity /Task /Milestones Payment

1 Mobilization Advance to TSSP 3% against BG of

equal amount

2 Supply of Hardware required for VMS 60% of Phase I cost

3 Implementation of VMS 35% of Phase I cost


Volume II


S No Activity /Task /Milestones Payment

4 Submission and acceptance of System Requirement

Specifications 5% of Phase II cost

5 Completion of 100% Unit Test 5% of Phase II cost

6 Completion of 100% Integration Test 5% of Phase II cost

7 Commissioning of IT Infra at DC for FAT

15% of Phase II

cost on

commissioning

certificate by

department

8 STQC \ Govt. Empanelled Agency Quality& Security Certification 5% of Phase II cost

9 Completion of FAT 5% of Phase II cost

10 Completion of Manpower Deployment 5% of Phase II cost

11 Go Live 5% of Phase II cost

12 Operation and maintenance phase

50% of Phase II

cost in QGRs

against fulfilment

of SLAs

3.2.22 Approvals

The TSSP shall be responsible for obtaining approvals for any Statutory and Regulatory requirements

(if any) from any of the authorities. Further, the TSSP shall be responsible to get required

documentation completed for obtaining such approvals from time to time. The TSSP shall undertake

to do all such acts and deeds as required to ensure that the approvals are obtained only with prior

approval of department. The State Nodal Agency shall extend all reasonable assistance to the TSSP

in this regard.

3.2.23 Post acceptance support

1. From the day when the system goes “live”, the Bidder must provide expert personnel at state

level for a period of five (5) years on a full time basis for providing post Acceptance support

to the implemented system.

2. At the end of 5 years, department will have the option of extending the Post Acceptance

support for any further periods, if the need arises so.

3.2.24 Standards

The metadata standards published by DeiTY have to be followed.

3.2.25 Non-Conformities

1. The TSSP shall rectify and/or take necessary action to overcome any

nonconformities/observations with respect to their work as reported by department as


Volume II


promptly as possible and at no additional cost to department if such rectification / action is

required to be undertaken during the contract period (that is, till the end of the O&M phase).

2. The TSSP shall provide the spares and service support for the entire IT infrastructure

supplied by them for the entire contract duration at no additional cost to department.

3.2.26 List of Deliverables

This is a suggested list of deliverables (but not limited to) from the successful bidder include–

1. Supply, Deployment and maintenance of Hardware Equipment

a. Servers at DC.

b. E lock and GPR tracker kit

c. Only GPS Tracker Kit

d. Check-gate Scanning System

e. Any other equipment required as per the proposed solution by TSSP.

2. System Requirement Specification (SRS) document containing detailed requirement capture

and analysis including functional requirement, integration with BSBCL software, Interface

Specifications and application security requirements.

3. High Level Software Design document including Software Architecture design, Logical and

Physical Database Design etc.

4. Low Level Software Design document including Programming Logic, Workflows etc.

5. Complete Source Code with documentation.

6. Test Plans and Test cases for

a. Unit Testing,

b. Integration Testing,

c. System Testing,

d. Final Acceptance Testing,

e. Security Testing,

f. Load Test Plan

7. Software Testing Documentation including complete defects/bugs/errors list , their

corresponding resolution and code impact for

g. System Testing

h. Final Acceptance Testing

8. Application to monitor the SLAs to be supplied by the TSSP.

9. Training Manuals and literature

10. Manuals- User manuals covering all areas like Systems Administration, Installation,

Maintenance and User level Operational issues and others as requesting by Nodal Agency

11. At least once a week Status, issues and Review Reports

12. Status reports- Integration with BSBCL applications

13. Support services during Implementation, Operations and Support stage

14. Internal review and testing documents of TSSP

15. Exit Management Plan

16. Escalation Mechanism on SLA’s

17. Standard Operating Procedure Document

The suggested activities to be performed for this project are explained below:


Volume II


i. Project Initiation

ii. Preparation of the Project Plan and the Inception Report

The TSSP needs to prepare an Integrated Project Plan for the entire assignment that

covers detailed tasks which are intended to perform as part of the assignment.

The roles and responsibilities for the project along with support arrangements that

are expected from the Department need to be jointly arrived at and has to be signed off

between the TSSP and Department.

The TSSP needs to prepare and submit an Inception Report, which will serve as the

foundational document for all activities related to the project. Additionally, the Inception

Report must cover the risks the TSSP anticipates and the plans they have towards Risk

mitigation.

The acceptance of the Inception Report is necessary before proceeding to the next stage

of the project.

iii. Requirement Analysis

A high-level analysis of processes has already been performed and functional

requirements have been identified. The Functional Requirement as envisaged for this

project shall be provided to the successful bidder. The TSSP needs to go through the

document, and may consult with the Department whenever necessary to get more details

on the requirements of the project. In case, TSSP needs to discuss with stakeholders

outside the Department to understand the processes better, they must intimate the

Department in advance for the same.

The TSSP must do a comprehensive discussion with the Department and subsequent

analysis to ensure that each of the requirements mentioned in the Functional Requirements

are covered in the requirement analysis they conduct and later captured in the Integrated

Excise Management System.

The TSSP must map the Functional Requirements to the proposed pre-integrated

packaged solution and analyse the existing gaps between the Functional Requirements

and the functionalities provided by package solution. The TSSP should estimate the

customization effort for the implementation and inform the same to Department.

Activities conducted as part of this task will result in the project deliverable

“Integrated Excise Management System Software Requirement Specifications”

(SRS) document, which shall detail the requirement of the complete solution up to the

minute level.

The SRS document should give the complete architecture of the proposed Integrated

Excise Management System. SRS should include, but not limited to:

- All Data base structure and detailed description of fields and tables.

- Naming conventions followed for the tables and fields.


Volume II


- Data flow diagrams (DFD) & entity-relationship (ER) diagrams.

- Details of validation rules and constraints like Integrity Checks etc. to be

applied.

- Format of all input screens including data entry requirements.

- Format of all reports that would be generated by Integrated Excise

Management System.

- Business logic used for all reports and functions.

- Access control mechanisms, data security and audit trails to ensure that

databases are not tampered or modified by unauthorized users.

The following guidelines need to be observed for security

- Build a complete audit trail of all transactions (add, edit and

delete) using transaction log reports, so that errors in data, intentional

or otherwise, can be traced and reversed.

- The most appropriate level of security commensurate with the value to

that function for which it is deployed must be chosen

- Access Controls must be provided to ensure that the databases are not

tampered or modified by the system operators.

- Implement data security to allow for changes in technology and business

needs.

iv. Definition & Design

Having conducted a comprehensive analysis of the requirements for the Integrated

Excise Management System, the TSSP would need to prepare an elaborate system design

for the Integrated Excise Management System.

Based on the requirements analysis conducted above, the TSSP must develop detailed

design of a normalized database for the Integrated Excise Management System.

The Integrated Excise Management System design must be such as to require the minimal

installation, if at all, at the user’s end, besides the Internet Browser. Moreover, all common

browsers (Internet explorer, Chrome, Mozilla etc) should be able to support the Integrated

Excise Management System suite of applications.

TSSP is encouraged to get users’ involvement in this stage when they are finalizing all

design components including the user interfaces, the mode of data entry, storage and

retrieval, outputs reports, queries and the application design as a whole.

The TSSP must consult a few portal designs of other organizations worldwide operational

in the excise sector and propose a progressive portal design for the project.


Volume II


The TSSP would be responsible for making sure that all the above pre-requisites are

adequately met.

Activities conducted as part of this task will result in the project deliverable “Integrated

Excise Management System Software Design Document” (SDD), which would include all

aspects of the design mentioned above

v. Procurement, Customization, Integration, Testing and Implementation of Pre-

integrated Package Solution

The Once the SDD is completed and signed-off, the TSSP should procure and customize

the pre- integrated package solution to take care of functional and design requirements as

defined in the Initiation phase.

The TSSP should deploy a dedicated team experienced in customization and deployment

of packaged solution.

The TSSP should deploy a team that is experienced in developing and integrating

applications with pre-integrated package solution.

The TSSP must deploy a software development methodology that ensures rapid

deployment of the applications in such a way that (a) the users are continually involved in

the development process, and (b) at least three cycles of iteration are allowed before

finalizing the components of the Integrated Excise Management System.

TSSP must specify the team structure as defined in the “key personnel” and “man power

requirements” sections and same should be adhered to while developing the solution.

From the integration perspective, the TSSP must take into account necessary interfacing

requirements (both at the application and data level) between the modules and the existing

information systems; should an interfacing need to be done with a module that is scheduled

for development in next phases, appropriate interfaces must be provided so as to effect this

integration as smoothly as is possible.

At every stage of the development process, the different components of the Integrated

Excise Management System must get thoroughly tested to make it bug-free.

Development shall be in three stages

Stage I: alpha version- TSSP would need to conduct (a) Acceptance testing of the

Integrated Excise Management System based on test cases developed and validated by

Department of Excise and Prohibition, (b) Master data migration or data entry so as to

facilitate the acceptance testing of all functionalities of the Integrated Excise Management

System, and (c) Training of the Department staff and other stakeholders on the continued

usage, maintenance and enhancement of the Integrated Excise Management System. Only

upon successful completion of the above mentioned three tasks, the implementation shall

move into the next stage.

Stage II: The beta version in which the Integrated Excise Management System will be made

available and restricted only to the users in the Department through an appropriate access

mechanism on the Web, and


Volume II


Stage III: Statewide rollout or the official launch of the portal and the Integrated

Excise Management System applications through the Internet in two phases

vi. Supply, installation, configuration and commissioning of central hardware &

installation of required system software for application hosting

a. The TSSP shall draw out and recommend detailed specifications for the central

hardware that needs to be used for hosting. Indicative Bill of Material is already given

in this RFP. However TSSP should propose any other hardware to host the

application at DC.

b. For any components/ equipment proposed by TSSP, the Specifications must be

futuristic with at least a five-year horizon to start with and recommended hardware

should be able to accommodate any scaling up requirements necessitated in future.

Indicative scalability requirements are mentioned in the solution description.

c. Based on the recommendations, TSSP must procure, install and successfully

commission the hardware in such a way that the implementation plan does not suffer.

d. TSSP will coordinate with the DC operator to co-host the Integrated Excise

Management System application and leverage the existing infrastructure at DC.

vii. Configuration and commissioning of user level hardware & the required system

software and other software

e. TSSP must therefore procure, install and successfully commission the suggested

hardware in such a way that the implementation plan does not suffer.

f. TSSP must also procure and successfully install all the system software such as

operating systems and any other software for using the Integrated Excise

Management System.

g. Supply of the hardware, software, networking equipment, UPS, inverter to the location

as per the requirements

h. Installation, Testing and Commissioning of UPS, Inverter

i. Physical Installation of Desktops, Printer, Scanner, MFD, Switch- Connecting

peripherals, devices, Plugging in

j. Operating System Installation and Configuration

k. Installation of Antivirus and other support software if any

l. Configuring the security at the desktops, switch and broadband connection routers

m. Network and browser Configuration


Volume II


n. Test accessibility and functionality of Integrated Excise Management System

application from the desktops

o. Ensuring all the systems required are supplied, installed, configured, tested

and commissioned and declaring the site to be operational.

p. At each of the location, acceptance certificate shall be issued to the TSSP

after the successful commissioning.

viii. Commissioning for all Project Locations

a. At each of the location, acceptance certificate shall be issued to the TSSP

after the successful commissioning.

b. Department can also arrange for site visits to assess the site preparation visits for 1-

2 locations for interested bidders.

ix. Training of the department users for effectively using the system

a. The TSSP shall impart training to the Department staff and other key stakeholders

on the usage and maintenance of the Integrated Excise Management System.

b. Department has already done detailed training needs analysis and has come out with

list of modules and user groups. The details of which are furnished below

Technical training for the Department of Excise and Prohibition central team of 3 members

End user training before Go-live, to be imparted through training a team of Trainers, whereby

about 2 Trainers will be trained for each module

All the end users (of about 1200 in number) through different batches (One time training)

x. The TSSP should provide the following in his bid:

a. Description of the approach and tentative plan for each type of training with the

tentative time frame;

b. Duration for each type of training;

c. Description of the training hand-outs/ manuals to be provided to the trainees.

xi. The TSSP will be responsible for:

a. Providing a Training Strategy, describing the proposed approach in providing training

to various categories of users;

b. Conducting separate training sessions for separate training types, each in suitable

batches;

c. Preparation of the training material and end user manuals covering “how to use”

concepts for all modules to be implemented.

xii. Operation and Maintenance of the Integrated Excise Management System application

and all associated hardware and network equipment


Volume II


a. On successful completion of above tasks and with the complete system going live,

the TSSP must extend Post Implementation Support till the end of contractual period.

b. The TSSP needs to provide the operational and maintenance support for all the

modules that are implemented and being used before the Go-Live. In other words,

the TSSP needs to provide operational and maintenance support of all the modules,

whenever they are completed and installed.

c. During the operational and maintenance support, the TSSP must

Propose a Post Implementation Team (PIT).

The said PIT team must ensure that all necessary measures are taken for the

smooth implementation of the Integrated Excise Management System

Although no further training at this stage is envisaged, the PIT team must ensure

that an Integrated Excise Management System support team is duly prepared

that will gradually takeover from the PIT team once the latter’s contractual term

is over.

The team must ensure that all necessary know-how is transferred to the Integrated

Excise Management System support team in such a manner so as to make for

a smooth transition. Performance metrics for the above transition will need to be

agreed between the TSSP and the Department to ensure successful conclusion of

this stage.

The TSSP must also establish the helpdesk for the users to contact in case of

any Integrated Excise Management System problems

d. Ensuring that the system is available as per the prescribed SLAs. The TSSP should

install/develop his/her own tools for monitoring the SLAs.

e. Re-installations, in the event of system crash/failures.

f. Develop Standard Operating Procedures (SOPs)

g. Over all monitoring and management of the systems implemented for Integrated

Excise Management System Project, which includes administration of Networks, UPS

and all other services ancillary to these facilities, in compliance with standards and

specifications.

h. Product Upgrades

i. Ensure overall security of the solution including installation and management of

Antivirus solution for protection of all the servers and systems implemented for the

project, application of updates/ patches etc. The antivirus patches and updates to be

applied from time to time, after appropriate testing of the patches in the staging area.

j. Backup of operating system, database and application as per stipulated policies.

k. Monitoring and enhancement of the performance of scheduled backups, schedule

regular testing of backups and ensure adherence to related retention policies.

l. Reactive maintenance that is intended to troubleshoot the system with sufficient

teams positioned at key places

m. Performance tuning of the system as may be needed to comply with SLA

requirements on a continuous basis.

n. Escalation and co-ordination with other partners for problem resolution wherever

required.

o. System administration tasks such as creating and managing users, taking backups

etc.


Volume II


p. Whenever a component has to be replaced because of technical,

functional, manufacturing or any other problem, it shall be replaced with a component

of the same make and configuration.

q. In case the component of same make and configuration is not available, the

replacement shall conform to open standards and shall be of a higher configuration

specifically approved by Department.

r. Produce and maintain system audit logs on the system for a period agreed in the

agreement. On expiry of the said period, the audit logs should be archived and stored

offsite.

xiii. Handholding Support

The TSSP will provide one qualified and trained person per location for a period of three

months to handhold the staff and ensure that the staffs in those locations are able to use

Integrated Excise Management System application on their own by the end of the

handholding period. TSSP must provide the project team as per details and eligibility

qualifications given in this RFP. Minimum 2 persons per division must be provided for

handholding

Handholding and project support would be required only after the successful

commissioning of Integrated Excise Management System application and the necessary

infrastructure and completion of capacity building and change management initiatives in

respective places.

Code of Conduct for Handholding personnel are as mentioned below:

The person to be engaged by TSSP for Handholding support should work as

six days per week.

Handholding personnel should give 100% availability on all working days.

The qualification required for handholding personnel is described man power

requirements section.

The scheduling and requirement for handholding personnel would be in line

with the implementation phases of the project roll out as described in deliverables

and timelines section.

xiv. Helpdesk support

The help desk service will serve as a single point of contact for all incidents and

service requests to the helpdesk. The service will provide a Single Point of Contact

(SPOC) and also escalation / closure of incidents for the user departments.

The activities shall include:

a. Deployment of sufficient manpower to attend the incoming calls/ complaints for extending

technical support to government users

b. Help Desk Team should consists of One Operational Manager and Two Help Desk

Resources.


Volume II


c. Deployment of web-based tool for the helpdesk

d. Provide Help Desk facility during agreed SLA for reporting user department incidents /

issues / problems with the Integrated Excise Management System application and network.

e. Provide necessary channels for reporting issues to the help desk. The incident reporting

channels could be the following:

Specific E-Mail account

Toll-free dedicated Phone Numbers

Portal

f. Implement a call logging system in line with the severity levels as per the SLAs. The Help

desk shall log user calls related to Integrated Excise Management System and assign an

incident/ call ID number. Severity shall be assigned to each call as per the SLAs.

g. Track each incident / call to resolution.

h. Escalate the calls, to the appropriate levels, if necessary as per the escalation matrix

agreed between the TSSP and the department. The escalation matrix shall be developed

by the TSSP’s in discussion with the Department of Excise and Prohibition.

i. Coordinate with respective OEM for closure of calls.

j. Coordinate with BSNL/ BSWAN/Private ISPs for closure of calls related to Network.

k. Analyze the incident / call statistics and provide monthly reports including but not limited

to:

Type of incidents / calls logged

Incidents / calls resolved

Incidents / calls open

l. Creation of knowledge base on frequently asked questions to assist user departments in

resolving basic issues themselves.

m. Provide feedback to callers.

n. Continuous monitoring of the system to ensure availability as per agreed SLAs.

o. Monitoring shall be done with the help of SAL monitoring tools and system logs / counters

and therefore the reports and alerts can be auto-generated.

xv. Documentation


Volume II


The TSSP must ensure that complete documentation of Integrated Excise Management

System is provided with comprehensive user manuals, and adhere to standard methodologies

in software development as per ISO standard and/or CMM models. The following documents

are the minimum requirements:

Communications Plan listing all stakeholders in the project, defining their roles

Quality Assurance Plan Documenting the planned and systematic pattern of all actions

necessary to assure confidence that the software developed will conform to the Integrated

Excise Management System functional and technical requirements.

Interface Control Document, documenting the interface characteristics of one or more

systems and documents agreements between interface owners.

Test Plan Containing information on the software test environment to be used for

independent testing, the test cases to be performed, and the overall testing schedule.

This includes methodology, schedule, resources, tools, procedures, environment

definition, test cases, and software test results.

Systems Manual Detailing the data structure, table, forms and report structures.

Operations Manual providing instructions for installing the application, troubleshooting,

interpreting message logs, and FAQs (Frequently Asked Questions).

User Manual (both online and paper copies) providing detailed instructions on how to use

the software. In addition, it describes how to access, submit inputs to, and interpret

outputs from the application.

A data dictionary listing out all the data elements shall be prepared.

3.3 Acceptance Testing and Certifications

The primary goal of Acceptance Testing and Certification is to ensure that the Project (including

all the project components as discussed in the scope of work) meets requirements, standards,

specifications and performance, by ensuring that the following are associated with clear,

quantifiable metrics for accountability:

− Functional requirements

− Infrastructure (Hardware and Network) Compliance Review − Availability of the project Services in the defined locations − Performance − Security − Manageability − SLA Reporting System − Project Documentation (Design, development, configuration, training

and

administratio

n manuals etc) − Data Quality Review

As part of Acceptance testing, performed through a third party agency, Department of Excise

and Prohibition shall review all aspects of project development and implementation covering

software, hardware and networking including the processes relating to the design of solution

architecture, design of systems and sub-systems, coding, testing, business process description,

documentation, version control, change management, security, service oriented architecture,

performance in relation to defined requirements, interoperability, scalability, availability and

compliance with all the technical and functional requirements of the RFP and the agreement.


Volume II


The procedures and parameters for testing will be laid down by the Third Party Agency after

approval from Department of Excise and Prohibition ; the solution deployed by the vendor has to

satisfy third party acceptance testing upon which the system shall go-live, subject to Department

of Excise and Prohibition approval.

Department of Excise and Prohibition will establish appropriate processes for notifying the

selected vendor of any shortcomings from defined requirements at the earliest instance after

noticing the same to enable the selected vendor to take corrective action. All gaps identified shall

be addressed by the vendor immediately prior to Go-live of the solution. It is the responsibility

of the selected Bidder to take any corrective action required to remove all shortcomings, before

the roll out of the project.

It is to be noted that the involvement of the third party for acceptance testing and certification,

does not absolve the vendor of his responsibilities to meet all SLAs as laid out in this RFP

document.

It is to be noted that:

Department of Excise and Prohibition may get the solution audited through a Third Party before

Go-Live and periodically after Go-Live in order to ensure the success of the project. Such third-

party agency for carrying out the acceptance testing and certification of the entire solution will be

nominated by the Department.

Following discusses the acceptance criteria to be adopted for the project as mentioned above.

The list below is indicative and the activities will include but not be limited to the following:

Functional Requirements Review

The solution developed/customized by selected Bidder shall be reviewed and verified by the

agency against the Functional Requirements signed-off between the Department of Excise and

Prohibition and the selected Bidder. All gaps, identified shall be addressed by the vendor

immediately prior to Go-live of the solution. One of the key inputs for this testing shall be the

traceability matrix to be developed by the vendor for the solution. Apart from Traceability Matrix,

agency may develop its own testing plans for validation of compliance of system against the

defined requirements. The acceptance testing w.r.t. the functional requirements shall be

performed by independent third party agency (external audit) as well as the select internal

department users (User Acceptance Testing) and system has to satisfy both third party

acceptance testing and internal user acceptance testing, upon which the system shall go-live.

For conducting the User Acceptance Testing, Department of Excise and Prohibition shall identify

the employees from respective divisions, who shall be responsible for day-to-day operations of

the functions automated through the project.

The system, during the functional requirements review, shall necessarily satisfy the user

acceptance testing process.

Infrastructure Compliance Review


Volume II


Third party agency shall perform the Infrastructure Compliance Review to verify the

conformity of the Infrastructure (both IT, non IT as well as Network in frastructure) supplied

by the selected Bidder against the requirements and specifications provided in the RFP

and/or as proposed in the proposal submitted by the selected Bidder. Compliance review

shall not absolve the vendor from ensuring that proposed infrastructure meets the SLA

requirements.

Security Review

The software developed/customized shall be audited by the agency from a security and

controls perspective. Such audit shall also include the IT infrastructure and network deployed

for the project. Following are the broad activities to be performed by the Agency as part of

Security Review. The security review shall subject the solution to the following activities.

Audit of Network, Server and Application security mechanisms

Assessment of authentication mechanism provided in the application

/components/modules

Assessment of data encryption mechanisms implemented for the solution

Asessment of data access privileges, retention periods and archival mechanisms

Server and Application security features incorporated etc

Application Security mechanisms should be accessed in compliance with the IT Act 2000,

2008 Amendment and IT rules 2011, such that it maintains data/information Integrity,

Confidentiality, Non repudiation

Audit of Security mechanisms so that they are in compliance with the latest Guidelines

by Controller of Certifying authority (CCA),IT Act, ISO27001.

Gap assessment of certain controls like say ISO 27001 and section 43, 47, 66, 69, 79,

84 and 87 of IT ACT amendment 2008 and decide how the sensitive data from a data

centric stand point is to be protected.

Performance

Performance is another key requirement for the project and the agency shall review the

performance of the deployed solution against certain key parameters defined in SLA. Such

parameters include request‐response time, work‐flow processing time, concurrent sessions

supported by the system etc, Disaster Recovery drill etc. The performance review also

includes verification of scalability provisioned in the solution for catering to the project

requirements.

Availability

The solution should be designed to remove all single point failures. Appropriate redundancy

shall be built into all the critical components to provide the ability to recover from failures.

The agency shall perform various tests including network, server, security, DC/DR fail‐over

tests to verify the availability of the services in case of component/location failures. The

agency shall also verify the availability of the project services to all the users in the defined

locations.


Volume II


Manageability Review

The agency shall verify the manageability of the solution and its supporting

infrastructure deployed using the Enterprise Management System (EMS) proposed by the

selected Bidder. The manageability requirements include requirements such as remote

monitoring, administration, configuration, inventory management, fault identification etc.

SLA Reporting System

The selected Bidder shall design, implement/customize the Enterprise Management System

(EMS) and shall develop any additional tools required to monitor the performance indicators

listed as per the SLAs mentioned the RFP. The Acceptance Testing and Certification agency

shall verify the accuracy and completeness of the information captured by the SLA monitoring

system implemented by the vendor and shall certify the same. The EMS deployed for the

project, based on SLAs, shall be configured by the selected Bidder to calculate the payment to

be paid by the department after deducting the necessary penalties.

Project Documentation

The Agency shall review the project documents developed by the selected Bidder including

requirements, design, source code, installation, training and administration manuals, version

control etc.

Any issues/gaps identified by the Agency, in any of the above areas, shall be addressed to

the complete satisfaction of the Department.

Data Quality

The Agency shall perform the Data Quality Assessment for the Data digitized by selected

Bidder and the data migrated by the vendor to the new system. The errors/gaps identified

during the Data Quality Assessment shall be addressed by the vendor before moving the

data into production environment, which is a key mile stone for Go-live of the solution.

3.4 Payment schedules

The selected TSSP (Bidder) shall be paid on completion of milestones that have been approved

and accepted by Director, Department of Excise and Prohibition and endorsed by Department

of Excise and Prohibition, Government of Bihar at the rates specified by the bidder and agreed

upon.

Department of Excise and Prohibition, Government of Bihar shall make a payment after the

successful completion of every milestone of any given phase when the bidder claims for payment

with the following supporting document:

1. Approval letter from the Department of Excise and Prohibition for the milestone achieved

2. Acceptance certificate for the sites accepted by Department of Excise and Prohibition ,

Bihar

3. All supporting documents like the bills, invoices etc.


Volume II


1.1.2 Other Payment Terms

All the payments to the TSSP will be made as per the Payment Schedule and Terms of

Payment set out in this RFP, upon submission of invoices along with relevant Sign Off from

the Department of Excise and Prohibition.

In the event of premature termination of the agreement prior to the launch of the Project, the

Supplying Agency shall not be eligible to receive any compensation or payment. Further,

appropriate penalty would be imposed on the Supplying Agency as decided by the Department

of Excise and Prohibition, Bihar

3.5 Acceptance criteria

The primary goal of Testing & Acceptance would be to ensure that the project meets

requirements, standards, specifications and performance prescribed by the RFP by

ensuring that the following are associated with clear, quantifiable metrics for accountability:

1. Functional Requirements

2. Availability

3. Performance

4. Security

5. Manageability

6. Project Documentation

7. Data Quality

The project is to be designed to meet all functional, non-functional and management

requirements as mentioned in the RFP

Department of Excise and Prohibition will accept the commissioning and project Go-

Live only after successful User Acceptance Testing confirmation from all respective

departments.

The departments will assess the functionality of the system along with the required

outputs and MIS reports based on requirements/solution proposed in FRS, RFP, SRS

and Software Design Document (SDD) documents to give final acceptance to the

system.

A team comprising of representatives from Department of Excise and Prohibition ,

TSSP and respective departments will verify satisfactory performance of all the

components of the solution with reference to requirements/solution in the FRS, RFP,

SRS and SDD documents.


Volume II


Any delay on account of Government side procedures such as issuance of Government

orders, logistics arrangement at site offices, personnel deployment, power supply,

network connectivity and bandwidth etc. should not be considered for acceptance.

In case such a delay occurs, the acceptance should be completed for those modules

where these procedures are not impacting.

The prorated payment for the delayed modules, if any may be made later at the

discretion of Department of Excise and Prohibition.

Security Audit of the IT Infrastructure - TSSP is also required to conduct security audit

of the entire IT infrastructure carried out by the third party and should be carried out

before the Operational go-live of the entire system.

Infrastructure Compliance Review - On receipt of hardware delivered by the TSSP,

Purchaser will physically check all packages & boxes to check that the items are

received as against the quantities & specifications indicated by the TSSP in its

Proposal. All System software being provided must be the latest & complete with all

manuals. They must include the licenses, media (CD ROM) and certificate of

authenticity. On establishment of the network, installation & integration of the various

components of the networks,

Purchaser will carry out acceptance testing of the network/ integrated system to verify

the conformity of the performance against the requirements and specifications provided

in the RFP and/or as proposed in the proposal submitted by TSSP. A burnout test for

the servers shall be carried out for 72 hrs.

CERT-IN certification for the services on central application, web-portal and other

modules has to be taken before the Go-Live of the project.

The Acceptance Test shall include unit test of each and every function and facility of

the Web-Portal, Core modules and other functionalities of the solution. The functional

requirement for the solution has been shared in Annexure VII of the RFP. The system

developed/customized by vendor shall be reviewed and verified by the third party

agency against the Functional Requirements signed-off between TSSP and

Department of Excise and Prohibition. Any gaps, identified as a severe or critical in

nature, shall be addressed by vendor immediately prior to Go-live of the system

The Acceptance Test shall include checks for all cross-functional and Inter-module

integration and data flow requirements

Acceptance of the system shall be based on the integrated performance of Hardware,

Software and Networking. The specification for Hardware and Networking shall be

carefully specified by the TSSP so as to ensure the desired level of performance of the

Solution. Networking equipment supplied should be compatible to IPV6.

Performance of the application is measured based on the throughput and latency of

the system. The performance test will include following components:


Volume II


Determination of performance metrics based on the Services level requirements

mentioned in RFP

Designing performance tests

Development of workload

Performance testing

Identification of bottlenecks and providing solutions

Determining final performance figures.

Communication of final results to all stakeholders

Final Acceptance Testing – Pre- requisites of Final Acceptance shall have the following:

Installation & commissioning of all hardware, software supplied under this RFP

including deployment of NMS , EMS , Helpdesk software

All documentation and relevant acceptance test document (including IT

Components, non IT components).

Installation and commissioning shall include installation and commissioning of

IT, non – IT components across project Department of Excise and Prohibition

offices / Client sites and at DC & DR Site

For both IT & Non-IT equipment / software manuals / brochures / Data Sheets /

CD / DVD / media for all the supplied components

Availability of all the defined services shall be verified and mutually agreed

between Department of Excise and Prohibition and the successful bidder

TSSP shall be required to demonstrate all the features / facilities / functionalities as

mentioned in the RFP.

Acceptance by Department of Excise and Prohibition is subject to satisfactory response

from respective departments for all Modules and core application. Only after the

satisfactory response from the entire stakeholder department, UAT report will be

accepted by Department of Excise and Prohibition and the UAT phase will be

considered completed.

3.6 Downstream work

Department of Excise and Prohibition would have all the rights with respect to the

Integrated Excise Management System solution and the Bidders are restricted to

carry out any downstream work resulting from this assignment.

3.7 General Requirements

I. Licensing Requirements

A. All system software, licenses, etc. have to be procured in the name of the <Specify

the appropriate name>

B. The licenses should be perpetual and enterprise wide for the core application and

other software unless otherwise stated. The software licenses shall not be restricted

based on location and the BSBCL should have the flexibility to use the software

licenses for other requirements, if required


Volume II


II. Asset Management

The selected Bidder will perform the following asset management functions with respect to

the infrastructure deployed at various locations:

A. Take periodic stock of, review physical inventory and maintain stock registers of

hardware at all locations covered under this Project. The selected Bidder would

maintain stock registers as per format agreed with the BSBCL.

B. Maintain documentation of the hardware assets, maintain asset Information for all

Project locations, on parameters to be mutually agreed between the BSBCL and the

selected Bidder, which shall include details like -

1. Product type, model number, version number

2. Manufacturer

3. Office location

4. Maintenance status, etc.

C. Update or correct the asset information following any new installations, movement,

addition, or change performed by the selected Bidder.

D. Produce periodic reports and machine readable files in agreed upon format

pertaining to some or all of the asset information.

E. Restrict movement of server/equipment/items in or out of SDC or any other location

under the Project without prior permission from the BSBCL.

III. Warranty and Support

A. The selected Bidder shall warrant that the IT Infrastructure supplied to the

Department for this Project shall have no defects arising from design or workmanship

or any act or omission of the selected Bidder. The warranty shall remain valid for the

Contract period on all the items supplied as per the Contract.

B. The selected Bidder shall replace any parts/ components of the IT infrastructure

supplied for the Project if the components are defective and during the entire

warranty period the selected Bidder shall apply latest upgrades for all the hardware

components after appropriate testing. The BSBCL will not pay any additional costs

separately for warranty and the overall IT infrastructure cost quoted by the selected

Bidder shall include the same.

IV. Since the Project aims to reuse the common infrastructure created under SDC, SWAN

Projects, the selected Bidder will also be required to coordinate with SDC, SWAN teams to

ensure that uptime and performance requirements of the RFP are met. However, the selected

Bidder shall be held solely responsible for performance and service levels of any

infrastructure deployed by the selected Bidder as part of this Contract.

V. Knowledge Transfer

A. At the end of the Contract period, the selected Bidder will be required to provide

necessary handholding and transition support to designated staff or any other agency

that is selected for maintaining the system post the Contract with the selected Bidder.

The handholding support will include but not be limited to, conducting detailed

walkthrough and demonstrations for the IT Infrastructure, handing over all relevant

documentation, addressing the queries/clarifications of the new agency with respect

to the working / performance levels of the infrastructure, conducting training sessions

etc.

B. Knowledge Transfer is an integral part of the scope of work of the selected Bidder.

This will have to be done even in case the Contract with the Bidder ends or is

terminated before the planned timelines.


Volume II


Please note that this is only an indicative list. Any other activity, over and above these, as may be

deemed necessary by the selected Bidder to meet the service levels and requirements specified in

this Contract are also required to be performed by the selected Bidder at no additional cost.


Volume II


3.8 Exit Management

4.6.1 Purpose

I. This sets out the provisions, which will apply on expiry or termination of the MSA, the Project

Implementation, Operation and Management SLA.

II. In the case of termination of the Project Implementation and/or Operation and Management,

the Parties shall agree at that time whether, and if so during what period, the provisions of

this Schedule shall apply.

III. The Parties shall ensure that their respective associated entities carry out their respective

obligations set out in this Exit Management Schedule.

4.6.2 Transfer of Assets

I. BSBCL shall be entitled to serve notice in writing on the TSSP at any time during the exit

management period as detailed hereinabove requiring the TSSP and/or its sub-contractors

to provide the BSBCL with a complete and up to date list of the Assets within 30 days of such

notice. BSBCL shall then be entitled to serve notice in writing on the TSSP at any time prior

to the date that is 30 days prior to the end of the exit management period requiring the TSSP

to sell the Assets, if any, to be transferred to BSBCL or its nominated agencies at book value

as determined as of the date of such notice in accordance with the provisions of relevant

laws.

II. In case of contract being terminated by BSBCL, BSBCL reserves the right to ask TSSP to

continue running the project operations for a period of 6 months after termination orders are

issued.

III. Upon service of a notice under this Article the following provisions shall apply:

A. in the event, if the Assets to be transferred are mortgaged to any financial institutions

by the TSSP, the TSSP shall ensure that all such liens and liabilities have been

cleared beyond doubt, prior to such transfer. All documents regarding the discharge

of such lien and liabilities shall be furnished to the <<‘State Designated Agency’>>.

B. All risk in and title to the Assets to be transferred / to be purchased by the BSBCL

pursuant to this Article shall be transferred to BSBCL, on the last day of the exit

management period.

C. BSBCL shall pay to the TSSP on the last day of the exit management period such

sum representing the Net Block (procurement price less depreciation as per

provisions of Companies Act) of the Assets to be transferred as stated in the Terms

of Payment Schedule.

D. Payment to the outgoing TSSP shall be made to the tune of last set of completed

services / deliverables, subject to SLA requirements.

E. The outgoing TSSP will pass on to BSBCL and/or to the Replacement TSSP, the

subsisting rights in any leased properties/ licensed products on terms not less

favorable to BSBCL / Replacement TSSP, than that enjoyed by the outgoing TSSP.

4.6.3 Cooperation and Provision of Information

During the exit management period:

I. The TSSP will allow the BSBCL or its nominated agency access to information

reasonably required to define the then current mode of operation associated with the

provision of the services to enable the BSBCL to assess the existing services being

delivered;

II. promptly on reasonable request by the BSBCL, the TSSP shall provide access to

and copies of all information held or controlled by them which they have prepared or

maintained in accordance with this agreement relating to any material aspect of the


Volume II


services (whether provided by the TSSP or sub-contractors appointed by the TSSP).

The BSBCL shall be entitled to copy of all such information. Such information shall

include details pertaining to the services rendered and other performance data. The

TSSP shall permit the BSBCL or its nominated agencies to have reasonable access

to its employees and facilities as reasonably required by the Chairman, PIU to

understand the methods of delivery of the services employed by the TSSP and to

assist appropriate knowledge transfer.

4.6.4 Confidential Information, Security and Data

I. The TSSP will promptly on the commencement of the exit management period supply

to the BSBCL or its nominated agency the following:

A. information relating to the current services rendered and customer and

performance data relating to the performance of sub contractors in relation to

the services;

B. documentation relating to Computerization Project’s Intellectual Property

Rights;

C. documentation relating to sub-contractors;

D. all current and updated data as is reasonably required for purposes of BSBCL

or its nominated agencies transitioning the services to its Replacement TSSP

in a readily available format nominated by the BSBCL, its nominated agency;

E. all other information (including but not limited to documents, records and

agreements) relating to the services reasonably necessary to enable BSBCL

or its nominated agencies, or its Replacement TSSP to carry out due diligence

in order to transition the provision of the Services to BSBCL or its nominated

agencies, or its Replacement TSSP (as the case may be).

II. Before the expiry of the exit management period, the TSSP shall deliver to the

BSBCL or its nominated agency all new or up-dated materials from the categories

set out in Schedule above and shall not retain any copies thereof, except that the

TSSP shall be permitted to retain one copy of such materials for archival purposes

only.

III. Before the expiry of the exit management period, unless otherwise provided under

the MSA, the BSBCL or its nominated agency shall deliver to the TSSP all forms of

TSSP confidential information, which is in the possession or control of Chairperson,

PIU or its users.

4.6.5 Employees

I. Promptly on reasonable request at any time during the exit management period, the

TSSP shall, subject to applicable laws, restraints and regulations (including in

particular those relating to privacy) provide to the BSBCL or its nominated agency a

list of all employees (with job titles) of the TSSP dedicated to providing the services

at the commencement of the exit management period.

II. Where any national, regional law or regulation relating to the mandatory or automatic

transfer of the contracts of employment from the TSSP to the BSBCL or its nominated

agency, or a Replacement TSSP ("Transfer Regulation") applies to any or all of the

employees of the TSSP, then the Parties shall comply with their respective

obligations under such Transfer Regulations.

III. To the extent that any Transfer Regulation does not apply to any employee of the

TSSP, department, or its Replacement TSSP may make an offer of employment or

contract for services to such employee of the TSSP and the TSSP shall not enforce


Volume II


or impose any contractual provision that would prevent any such employee from

being hired by the Chairperson, PIU or any Replacement TSSP.

4.6.6 Transfer of Certain Agreements

On request by the BSBCL or its nominated agency the TSSP shall effect such assignments, transfers,

licences and sub-licences as the Chairperson, PIU may require in favour of the Chairperson, PIU, or

its Replacement TSSP in relation to any equipment lease, maintenance or service provision

agreement between TSSP and third party lessors, vendors, and which are related to the services and

reasonably necessary for the carrying out of replacement services by the BSBCL or its nominated

agency or its Replacement TSSP.

4.6.7 Rights of Access to Premises

I. At any time during the exit management period, where Assets are located at the TSSP's

premises, the TSSP will be obliged to give reasonable rights of access to (or, in the case of

Assets located on a third party's premises, procure reasonable rights of access to) the BSBCL

or its nominated agency and/or any Replacement TSSP in order to make an inventory of the

Assets.

II. The TSSP shall also give the BSBCL or its nominated agency or its nominated agencies, or

any Replacement TSSP right of reasonable access to the Implementation Partner's

premises and shall procure the BSBCL or its nominated agency or its nominated agencies

and any Replacement TSSP rights of access to relevant third party premises during the exit

management period and for such period of time following termination or expiry of the MSA as

is reasonably necessary to migrate the services to the BSBCL or its nominated agency, or a

Replacement TSSP.

4.6.8 General Obligations of the TSSP

I. The TSSP shall provide all such information as may reasonably be necessary to effect as

seamless a handover as practicable in the circumstances to the BSBCL or its nominated

agency or its Replacement TSSP and which the TSSP has in its possession or control at any

time during the exit management period.

II. For the purposes of this Schedule, anything in the possession or control of any TSSP,

associated entity, or sub-contractor is deemed to be in the possession or control of the TSSP.

III. The TSSP shall commit adequate resources to comply with its obligations under this Exit

Management Schedule.

4.6.9 Exit Management Plan

I. The TSSP shall provide the BSBCL or its nominated agency with a recommended exit

management plan ("Exit Management Plan") which shall deal with at least the following

aspects of exit management in relation to the MSA as a whole and in relation to the Project

Implementation, and the Operation and Management SLA.

A. A detailed program of the transfer process that could be used in conjunction with a

Replacement TSSP including details of the means to be used to ensure continuing

provision of the services throughout the transfer process or until the cessation of the

services and of the management structure to be used during the transfer;

B. plans for the communication with such of the TSSP's sub contractors, staff, suppliers,

customers and any related third party as are necessary to avoid any material

detrimental impact on the BSBCL’s operations as a result of undertaking the transfer;


Volume II


C. (if applicable) proposed arrangements for the segregation of the TSSP's networks

from the networks employed by BSBCL and identification of specific security tasks

necessary at termination;

D. Plans for provision of contingent support to BSBCL, and Replacement TSSP for a

reasonable period after transfer.

II. The TSSP shall re-draft the Exit Management Plan annually thereafter to ensure that it is kept

relevant and up to date.

III. Each Exit Management Plan shall be presented by the TSSP to and approved by the BSBCL

or its nominated agencies.

IV. The terms of payment as stated in the Terms of Payment Schedule include the costs of the

TSSP complying with its obligations under this Schedule.

V. In the event of termination or expiry of MSA, and Project Implementation, each Party shall

comply with the Exit Management Plan.

VI. During the exit management period, the TSSP shall use its best efforts to deliver the services.

VII. Payments during the Exit Management period shall be made in accordance with the Terms

of Payment Schedule.

VIII. This Exit Management plan shall be furnished in writing to the BSBCL or its nominated

agencies within 90 days from the Effective Date of this Agreement.

4 Detailed Implementation and Roll-out Plan

I. TSSP shall prepare a detailed roll-out plan for each of the districts in the phase and get the

same approved by the BSBCL. TSSP is also responsible for conducting workshops for the

key officers of BSBCL and Department) of the Districts / State for presenting the District-Wise

roll-out plan and get the approval of the same.

II. Before getting the final approval of the State Nodal Officer, the TSSP shall also provide the

necessary assistance for the key stakeholder of the Districts / State during the design and

implementation of the project in the State. A detailed rollout checklist should be maintained

for migrating application to production as well as for location readiness.

III. One of the important factors that would determine the success of the the implementation in

the State is the continuous availability of domain experts like Project Manager, Solution

Architect, Network Administrator and System Administrator to the implementation team which

would be selected with the approval of Department. TSSP shall put together a team of domain

experts with relevant as detailed out in the RFP on a full time basis.

RFP for Selection of Total Service and Solution Provider (TSSP) for Integrated Excise Management System – Volume II

5 Specification of Components

i. E-locks

Electrical Specifications Input voltage +9V to +36V DC and input protected against reverse polarity & voltage surges.

Fuse Rating 1 Amp, 250V slow-blow type

Current Rating at 12V DC In Idle mode: 150 mA

In Data Transfer/Voice mode: 220 mA

GSM Device Specification Type Tri-Band (900/1800/1900 MHz)

GPRS Multi-Slot Class 10. Mobile Station Class B

GSM Phase 2/2+

RFID Module Full two way duplex Mountable and unmountable

Environmental Specification Full Operation Temp -10 °C to + 55 °C

Storage Temp -10 °C to + 60 °C

Humidity <95%RH

Software User memory 2048 MB Events memory: 50 events

Vibration and Shock MIL STD 810D

Tracking and Tracing Seal status in real time

SOS Emergency SOS Red Switch

I/O Digital Input 4 Input ( two positive trigger, two negative trigger)

Life 4 years minimum with 50 cycles per day

LED Indications PL VMU Pilot status

Weather proof IP 67

Standards FCC, CE and CCoE

ii. GPS devices

Electrical Specifications Input voltage +9V to +36V DC and input protected against reverse polarity & voltage surges.

Fuse Rating 1 Amp, 250V slow-blow type

Current Rating at 12V DC In Idle mode: 150 mA

In Data Transfer/Voice mode: 220 mA

GPS Specification Channel 12

Refreshment Rate 1 sec

Position Accuracy +10 meters

GSM Device Specification Type Tri-Band (900/1800/1900 MHz)

GPRS Multi-Slot Class 10. Mobile Station Class B

GSM Phase 2/2+

GPS Antenna Specification Type Roof mountable

GPS Antenna Gain 27dbi

Antenna Gain > 1dBi

Environmental Specification Full Operation Temp -10 °C to + 55 °C

Storage Temp -40 °C to + 85 °C

Humidity <95%RH

Macro Button Functional Specification

1 Preconfigured number 1 for voice communication


Volume II



SOS Emergency SOS Red Switch

I/O Digital Input 4 Input ( two positive trigger, two negative trigger)

Digital Output 2 Output (Additional Sensors)

LED Indications PL VMU Pilot status

GPS GPS Modulo Health Status

MT Message Transfer indication

N/W Network availability

Red LED Incoming call indication

iii. Web, Application Servers with LDAP and Database Servers - Data Centre

S. No. Features Specifications

1 Physical

Configuration

Physical Configuration: Servers in blade configuration

2 Server Blade Server having two Nos of latest eight core or higher 64bit

X86 processor with SPEC rating in the range of 441/460

Motherboard based associated chipset, SAS Controller with

support for RAID 0 & 1, 2x300GB Hot Swap SAS HDD, 256GB

DDRIII 1333MHz memory with ECC expandable up to 512GB,

Embedded hypervisor hardware based virtual machine support,

Dual FCOE 10Gbps ports, Dual Ethernet 1Gbps/10Gbps ports,

Dedicated hardware management port for remote access,

Certified for Windows 2012 & Linux, Three years onsite

comprehensive warranty support.

3 Architecture X86 as per OEM architecture

4 Operating System Latest version of compatible OS

5 System Software Latest version of proposed Enterprise Server

6 Main Memory The system should be configured with minimum 256 GB RAM

(DDR III, 1333MHz, ECC), scalable up-to 512 GB (ECC).

Minimum 2 free slots for future expandable capability

7 Industry

Benchmark

Should have published benchmarks for TPC-c or SAP or SPEC

available. If no published benchmark result for the offered server

& processor is available then the performance offered by the

server will be estimated by linear extrapolation of a published

result on a higher server model or a lower server model (with the

same processor).

If the OEM does not have particular benchmark on a specified

server, the OEM can use an Internal benchmark to build the

correlation between a benchmark and the proposed Server. The


Volume II


same has to be given in the OEM's letterhead and signed by an

authorized person

8 Clustering Server should be configured to support for OS level clustering.

9 Virtualization Server virtualization support

10 Network Interface Dual port 10/100/1000 Mbps Ethernet Adapter, with no single

point of failure

11 HBA 2 No. dual ported 10 Gbps Fibre Channel Adapter with external

fibre ports for redundant connectivity to external storage.

12 Removable drive One DVD-RW/CD-RW Combo drive per server.

13 Power Supply Dual Redundant Power Supply with cooling fans

All Items are to be Rack Mounted in Industry

14 Server Height Standard 42U

15 Hot Swap

Components

Hard Disk Drives, Drives, Power supplies and fans.

16 RAID Integrated RAID-0, 1

17 Server Management Firmware Update, Dynamic resource management & utilization

capability, Real time System Monitoring

18 Disk Management Suitable disk management software including Volume Manager

to manage the logical volumes

19 OS Compatibility Microsoft Windows Server Enterprise / Standard Edition (32 bit

and 64 bit)

Red Hat Enterprise Linux

SUSE LINUX Enterprise Server

Solaris

20 Warranty 3 years On-Site Comprehensive warranty and Maintenance

Support

iv. Tape Drives


1 No of Drives 2 Expandable up-to 4 Drives within box or by adding expansion

modules/Cascading


Volume II


2 Drive Technology LTO5 with up to 140 MB/s data transfer rate

3 No. of Slots 12 slots and expandable up to 24 slots by adding modules or

cascading

4 Drive Interface Fibre Channel, 8Gbps

5 Capacity 10 TB and expandable up-to 30 TB by adding modules or

cascading

6 Performance Native 500GB/hr per drive

7 Media 12 Blank Cartridges with bar code labels.

8 Consumables 2 Cleaning Tapes

v. SAN Switches

S. No. Specifications

1 Minimum 8 Active ports (each with minimum port speed 8Gbps)

2 Should have at least 4 numbers of 1Gbps ports for SAN extension over WAN

3 Switch shall support POST and online/offline diagnostics

4 All cable and accessories for connecting Servers /Devices to SAN

5 Should have capability of port trunking.

6 Should have optical transceivers for short wave / long wave

7 Should have Fans and power supplies

8 Should have GUI based management software for administration and configuration

9 Should be possible to configure the switches based on threshold values for temperature

fan status.

10 Should support zoning configuration, virtual SAN/ Virtual Fabric

11 Should support fabric routing to enable cross fabric connectivity

12 All other necessary fibre cables and racking accessory should be supplied

13 Should support RADIUS authentication or SSH


Volume II

vi. Router


1 Router Architecture:

The router

architecture should

have following

features

Modular design/architecture, the architecture should be based on

high performance, distributed forwarding architecture.

Should support Voice, Video, Security

It should support Single Operating System which includes all the

feature set

2 Interface Support Ethernet LAN Ports -> 2 x 10/100/1000 Mbps WAN port &

4x10/100 LAN Ports. It should support additional Gigabit Ethernet

modules i.e. both 10/100/1000 or SFP type (upgradable )

It should support the industries widest range of wired and wireless

connectivity options such as T1/E1, ISDN, T3/E3, xDSL,

3G,STM-1, copper and fibre GE

3 Performance &

Memory Required:

Performance Requirements for 64 byte packet -> Minimum 300

kbps

4 Hardware Should support minimum default RAM = 256 MB, maximum RAM

=1 GB

Two USB port

One Serial console port

Should support AC power supply and Should support external

RPS

Should have 2 encryption slot

Should have 6 WAN interface Slots

Should support 3G standards High-Speed Packet Access

5 Voice DSP support Voice DSP support

Support Voice interface i.e. FXS, FXO, PRI, BRI

6 Router Functional

Requirements

IPv6 routing functionality from day 1


Volume II


QoS -> ToS, CoS, Queuing, prioritizing, Resource Reservation

Protocol (RSVP)

NAT -> NAT, PAT

Access Control -> Required

7 Protocol Support

Required:

RIPv1 and RIPv2 routing, BGP4, IS-IS,OSPF, OSPFv3, BGP+,

IPv6 tunnelling, MPLS, MPLS L2 VPN , MPLS L3 VPN, Policy

based Routing, PPP, HDLC, OSPF Version 2, Support for

IPV6.Re-distribution of routes from on Routing protocol should

not be a bottleneck. All the above features should be provisioned

in the router from day 1.

8 Congestion

Management:

The router should have proper congestion management to

eliminate Network congestion when the link is overloaded.

Random Early Detection, Weighted Fair/priority Queuing,

IP precedence or DSCP.

IP Multicasting: Type Forwarding -> MBGP, PIM-DM, PIM-SM

9 Security

Requirements

Support supports powerful ACLs for both IPv4 and IPv6

Controlled SNMP Access through implementation of Access Lists

on the router to ensure SNMP access only to the SNMP manager

or the NMS workstation

Controlled SNMP access through the use of SNMP with MD5

authentication.

Multiple Privilege Levels for managing & monitoring

Support for Remote Authentication User Service (RADIUS) and

AAA

PPP CHAP support

Should have Embedded encryption, firewall, security features

Support enhanced Stateful packet inspection and filtering

Should support advanced VPN services with Triple DES (3DES)

and Advanced Encryption Standard (AES) encryption at high


Volume II


performance and low latency, Web content filtering, and

application prioritization and enhancement

10 Management

Features

The Router shall support Telnet, SSH, Console access.

The router shall support FTP or TFTP for easy software upgrades

over the network.

Network Management services shall be provided using open

standards based protocols like SNMP V2/V3

11 Configuration

Management

The Router shall support configuration management through the

command line interface. GUI based software configuration utility

shall be provided. Support of configuration on web interface shall

be available.

12 Event and System

logging

Event and system history logging functions shall be available.

The Router shall generate system alarms on events. Facility to

put selective logging of events onto a separate hardware where

the analysis of log shall be available.

13 Power Internal Power supply 230 V AC 50 Hz & support for redundant

power supply

14 Mounting The offered router should be 19" rack mountable

15 Accessories Should come with all necessary power cords, CDs, manuals,

brackets accessories etc., required for installation and

commissioning of the equipment.

16 Additional Features The router should be EAL-2 Certified

The manufacturer should be part of the Industry standard leader’s

quadrants in Magic Gartner report from last 3 years.

vii. Switches

Sl.

No.

Specifications

1 Twenty four ports (upgradable to forty eight ports) FCOE manageable layer L2 or higher switch with

minimum sixteen ports enabled with SFP+ module of 10Gbps or higher FCOE bandwidth for

downward connectivity to blade enclosure. Switch has minimum Quad 10Gbps Ethernet ports and

Quad 8Gbps or higher FC ports for uplink connectivity with core switch. Virtual network created out of

each FCOE port should support port channel. Switch should be quoted with multimode fibre cable of

at least one 15M for each downlink port and uplink FC port

2 The Switch should have minimum 24 nos. 10/100/1000Base TX ports and in addition, 4

SFP based uplink ports.

3 Fibre uplink ports should support SX/LX/T SFP interfaces


Volume II

Sl.

No.

Specifications

4 support Physical port redundancy, TDR, MDI/MDIX

5 The switch should have non-blocking architecture

6 The Switch should support redundant Power Supply

7 The Switch should support a minimum of 56 Gbps of non-blocking wired speed Switching

Fabric Capacity.

8 The switch should have forwarding rate of min 41 Mbps

9 The Switch should have at least

4 GB DRAM

2 GB Flash

10 It should support 8 hardware queues per port

11 Should support Classification criteria like DSCP/ToS, IP/MAC Source/Dest, Source/Dest

TCP/UDP Port, 802.1p, Port, VLAN

12 Switch should have basic routing capabilities like Static routing , RIP from day 1. Upgradable

to OSPF and PIM in future

13 Should support 802.1Q protocol

14 Should support minimum 512 active VLANs.

15 Should support No. of MAC Address Supported : 8000

16 Support for Port-based ACL (PACL),VLAN-based ACL (VACL) and Router-based ACL

(RACL)

17 Should support Voice VLAN for separating and prioritizing VoIP traffic

18 Switch should support IGMP v1,2,3 and IGMP snooping; PIM SM

19 Should support Telnet and console connectivity

20 Should support Syslog, SNMP v1, v2 and v3, RMON 1,2,3, and 9, SSHv2, telnet and web

management

21 should support Configuration rollback

22 Should support Config-backup via TFTP / FTP / Secure Copy

23 Switch should support Out-of-band management Ethernet port

24 The Switch should have USB port for OS and configuration uploading.

25 Should have support for RADIUS and TACACS + for authentication

26 Should support 802.1x with VLAN Assignment.

27 Should Support port mirroring features for monitoring network traffic of a particular port/

VLAN/group of ports/ entire switch.

28 Ethernet: IEEE 802.3z, IEEE 802.3ab, 100Base-T, 1000Base-T, 1000Base-X (mini-

GBIC/SFP), 1000Base-SX, 1000Base-LX/LH, 1000Base-ZX and SFP support

29 IEEE 802.1D 1S & 1W for Spanning-Tree Protocol

30 IEEE 802.3x Flow Control

31 IEEE 802.3ad Link Aggregation within and across switches

32 Switch shall support stacking

33 Should Support AC Power Supply- 100-240 V

34 Switch shall be minimum EAL 2 or higher Certified.

35 Switch shall have the following Certifications: UL60950, FCC Class A, EN 55022


Volume II

viii. SAN Storage


1 RAID Level RAID Array supporting Raid Levels 0, 1, 0+1, 5, 10 or equivalent.

The RAID Level should be Hardware based and should use dedicated

Hardware for RAID Calculation.

2 Availability &

Required Cache

Cache should be mirrored between Active-Active controllers on

dedicated, redundant paths / links between the controllers. In case of

power failure, the SAN array must be provided with cache protection

mechanism to ensure no loss of data in cache by de- staging to disks,

irrespective of duration of power outage, or for minimum 72 hrs. The

Proposed SAN Array should be configured with at least 8GB usable

data cache.

3 Reliability The Proposed SAN Array should be configured with No Single Point

of Failure Architecture with Dual Controllers for redundancy and

should support hot plug and hot swap of components online (including

controllers, disks, power supplies, cooling fans etc.). Should have

continuous system monitoring and shall support remote diagnostics /

error reporting feature. It should also allow the recovery of data in

transit in the event of failure.

4 Front End

Connectivity

SAN Storage should be configured with at least 4 numbers of 4Gbps

Fibre channel (FC) front end ports per controller (i.e. a total of at least

8 x 4Gbps FC front end ports across Dual controllers) for front-end

host connectivity.

5 Back End

Connectivity

SAN Storage should be configured with at least 4 numbers of 4Gbps

Fibre channel (FC) back end ports per controller (i.e. a total of at least

8 x 4Gbps FC back end ports across Dual controllers) for back-end

disk-shelf connectivity.

6 Disk Drives The SAN Array should be able to support a minimum of 95 disks in the

array supplied from Day One and should be expandable to 140 disks

in future with data in place upgrade. The SAN Array should support

intermixing of FC & FATA/SATA‐II Disks of various capacities and

speeds. It should support dual ported disks of 128 GB, 146GB and

300GB or higher with speeds of 10K rpm & 15K rpm

7 Required Disk

space

The Proposed SAN Array should be configured with minimum 10TB

Usable Capacity. Is required on RAID 10 (Strip and Mirror

Everywhere) with 128GB, 15K RPM SAS / FC HDD (min 4Gbps, Dual

Ported Drives) and with 1 hot spare per disk tray.

8 Self-Tuning The Storage System should provide ease of use capabilities –

customer replaceable components, including non-disruptive

replacement of disk drives, power supplies, fans and SFP optical

transceivers.

9 Volume

Expansion

The storage system should support dynamic online LUN/volume

expansion and shrink through striping/ concatenation Or any

equivalent means / feature, which can achieve similar functionality

with supporting whitepaper validation documents from third party

agencies


Volume II


10 RAID Level

Mixing

It should support a mix and match of RAID levels (including RAID 0,

1, 1/0, 5) within the same storage array serviced by a pair of

controllers.

If any of the above features are not supported by the NIC/OEM, then

kindly propose equivalent features, with supporting whitepaper

validation documents from third party agencies

11 Volume

Expansion

The SAN Management software should preferably be array- based,

easy to use with secure web-based GUI administration interface for

configuration, storage management.

12 Sparing Should have a pool of Global Hot Spare disks for the entire array, so

that if a disk fails anywhere in the array, global hot spares can be

invoked from the pool to reduce the risk of data loss.

13 OS support Support for industry-leading Operating System platforms including but

not limited to various flavours of LINUX / Microsoft Windows / UNIX

etc. As well as various High Availability cluster solutions. The detailed

interoperability matrix should be available on the public domain.

14 IOPS I/O performance should be greater than or at least equal to 150,000

IOPS from Cache and should have a sustained sequential throughput

of minimum 2000MB/sec.

15 Snapshots/ Full

Copies

The array should provide for functionality for pointer based snapshot

copies (which require a fraction of the space) as well as full physical

copies. It should support Writeable space optimized snapshots.

16 Performance

Monitoring

The storage should be provided with storage performance monitoring

software. The performance monitoring software should provide

graphical view of the through put, iops and other performance by host

or by controllers

17 Advance

functions

The storage should be provided with thin provisioning feature quality

of service and SSD caching or tiering software should be provided

ix. 24 Port Switch

S. No. Feature Specification

1 Model All the relevant product brochures and manuals must be submitted.

2 Standards 1. IEEE 802.1D

2. IEEE 802.1p

3. IEEE 802.1Q

4. IEEE 802.1s

5. IEEE 802.1w

6. IEEE 802.1x

7. IEEE 802.1ab

8. IEEE 802.1ad

9. IEEE 802.3

10.IEEE 802.3u

11.IEEE 802.3ab

12.IEEE 802.3z


Volume II

S. No. Feature Specification

13.RFC 854

14.RFC 951

15.RFC 1305 / RFC2030

3 Protocol CSMA/CD

4 Throughput Min 8 Gbps

5 Data Transfer

Rates

Non-Blocking Architecture

6 Network Cables

10BASE-T: UTP Cat. 3, 4, 5 (100 m) EIA/TIA-586 100-ohm STP

(100 m)

100BASE-TX: UTP Cat. 5 (100 m) EIA/TIA-568 100-ohm STP

(100m max.)

7 Number of Ports 10/100Mbps port x 24

8 Twisted-pair Rx

Reverse Polarity

Auto-correction for each port

9 MAC Address

Learning

Automatic update

10 RAM 512 MB

11 Power Supply 100 - 240 VAC, 50/60 Hz

12 Security Should support

a) 802.1x

b) AAA

c) SSH v1, v2

d) SSL

e) Host to Host and Switch to Switch authentication

13 Management Should have

a. IPv6 management capability

b. SNMP v1, v2, v3

c. RMON

d. RADIUS

e. CLI via console

f. Web interface

g. Provision of software and firmware upgrades with latest version

releases through admin login

14 Uplink Ports Switch should have 2 dual-purpose uplink ports (10/100/1000 or

SFP)

x. Leased Line Modem (pair)

S. No Feature Specification

1 Model Must be specified


Volume II

S. No Feature Specification

2 Modem V35 2-Wire, Standalone, V.35 Interface, Ethernet (UTP) Port for

Management, Supports 220 to 240V

3 Modem G703 2-Wire, Standalone, G.703 (Balanced) Interface, Ethernet (UTP)

Port for Management, Supports both 230V & 48V DC Power

Interfaces

4 USB cable The modems supplied should also work on bandwidth between

64 Kbps to 2 Mbps.

5 Certifications Should have TEC Certification


Volume II

xi. Router

S. No. Feature \Specification

1 Model Must be specified

2 Architecture a) Should be chassis based & modular architecture for

scalability and should be a single box configuration for ease

of management.

b) Should have support for IPSEC VPN.

c) Should have minimum of 256MB of RAM and 32 MB of

Flash Memory

3 Interface a) 2 x 10/100 Base interface.

b) At least 2 free additional slots for future

1. Note: These additional slots should support both the

following interfaces:

V.35 (2 Mbps) interface including necessary cables

10/100 Ethernet Base interface.

4 Performance a) Should support high performance traffic forwarding with

concurrent features like Security, Voice enabled

b) Should support variety of interfaces like V.35 Sync Serial (2

Mbps), E1, ADSL for remote office aggregation

c) Should support 3G USB modem for connectivity or support

external 3G modem

d) Should have USB 2.0 ports for storing OS images

5 High Availability a) Should support redundant connection to LAN

b) Should support Non-Stop forwarding for fast re-convergence

of routing protocols

c) Should support boot options like booting from TFTP server,

Network node

d) Should support VRRP or equivalent

6 Protocols a) Should support Routing protocols like RIP ver1

(RFC1058)&2, (RFC 1722 and 1723), OSPF ver2

(RFC2328), BGP4 (RFC1771), IS-IS (RFC1195), Telnet

(RFC854)


Volume II


b) Multicast routing protocols support : IGMPv1,v2, v3 (RFC

2236), PIM-SM (RFC2362), PIM-SSM and PIM-DM, M-

BGP/ MSDP

c) Should have full IPv6 features from day 1.

d) Should have RIPng and OSPFv3 for IPv6.

7 QoS Features a) Classification and Marking: Policy based routing, IEEE

802.1p

b) Congestion Management: WRED, Priority queuing, Class

based queuing

c) Traffic Conditioning: Committed Access Rate/Rate limiting

d) Bandwidth guarantee

e) Signalling: RSVP

f) Link efficiency mechanisms: cRTP, LFI, MLPPP

g) Per VLAN QoS. Time Based Shaping and Policing for QoS

h) Port mirroring

8 Security Features a) Support for GRE Tunnelling, NAT

b) Support for MD-5 / SHA-1/SHA-2 route authentication for

RIP, OSPF and BGP

c) Shall support multi-level of access

d) Support for SNMPv3 authentication, SSHv2

e) AAA support using Radius and/or TACACS+

f) Support for PAP and CHAP authentication for P-to-P links

g) Multiple privilege level authentications for console and telnet

access through Local database or through an external AAA

Server.

h) Time based & Dynamic ACLs for controlled forwarding

based on time of day for offices

i) IEEE 802.1x support for MAC address authentication

9 Management a) Shall have support for Web based management, CLI, Telnet

and SNMPv3


Volume II


b) Shall support Secure Shell for secure connectivity.

c) Shall support Out of band management through Console

and external modem for remote management

10 Certification a) Common Criteria Certified

b) FCC

c) Safety EMI/EMC

11 Power AC 200 – 240V

Note:

1. This is an indicative list of material, equipment, software and services which will be needed

for implementation and O&M of the project. The numbers of units have been estimated at

best effort basis and are subject to change.

2. In case a Bidder feels that its solution requires any component over and above the list

mentioned above, he/ she may add that component/ service to the above mentioned list

and provide per unit cost of the same. Such component should be clearly highlighted.

3. All licenses should be perpetual.

4. The department would compensate the bidder for any additional components during the

project like increase of terminals, networking components.

All ICT hardware as subject of this tender must support both the IPv4 and IPv6 protocols. Similar

performance must be provided for both protocols in input, output and/or throughput data-flow

performance, transmission and processing of packets. IPv6 support can be verified and certified by

the IPv6 Ready Logo certificate. Any software that communicates via the IP protocol must support

both protocol versions (IPv4 and IPv6). The difference must not be noticeable to users.


Volume II

5.1 Non-Functional Requirements

The non-functional requirements relating to performance, availability, deployment, implementation,

operations and others are listed in the subsequent subsection. Based on the assessment of the

requirements listed below, TSSP shall prepare System Requirement Specifications (SRS) and obtain

a formal sign-off before proceeding with the design and implementation of the solution.

# Non-functional Requirements

Technical Solution Architecture Requirements

1 The the solution needs to be architected using robust and proven software and hardware

technologies like Service-Oriented Architecture (SOA) and open industry standards.

2 The solution architecture should be built on sound architectural principles enabling fault-

tolerance, high-performance, and scalability both on the software and hardware levels.

Software Architecture Requirements

1 Software architecture must support web services standards including XML, SOAP, UDDI

and WSDL

2 Software architecture must support appropriate load balancing for scalability and

performance

3 Software architecture must support flexibility in adding functionalities or applications.

4 Software architecture components should utilize the high availability, clustering, and load

balancing features available in the proposed hardware architecture to increase system

performance and scalability features.

5 Software architecture must support trace logging, error notification, issue resolution and

exception handling.

Hardware Architecture Requirements

1 Hardware architecture at SDC must provide redundancy and high availability capabilities at

the hardware level; this includes servers, etc. However, the hardware infrastructure for the

DRC can be as per the SDC specifications.

2 All servers and systems must be configured with no single point of failure.

3 Hardware architecture should be capable of consolidating several applications / workloads

in a number of servers as required.

4 Servers must be placed within proper security infrastructure for the Solution.

5 Hardware architecture must support existing Storage Area Network (SAN) & backup

solution (at SDC)

6 The technical solution architecture for the should be sound and complete with high

performance, redundancy, and scalability.

Development, Testing, Staging, and Production Requirements

1 Appropriate development, test, and staging hardware environments should be provided and

explained how they are related to production environment. This must be supported by

explanations on how the development, test, and staging environment support the

implementation activities of the Solution.

2 Development and test environment should include configuration management capabilities

and tools for system configuration, versioning scheme, documentation, change control

processes and procedures to manage deployment of solution deployment.

3 The test, development, and staging environment should include required workstations,

desktops, and tools appropriate to support development, testing, and staging, and

deployment tasks.

4 The development, test, and staging hardware environments must include similar operating

systems, software components, products, and tools to those of production environment.


Volume II

5 The development, test, and staging environments should be independent logically and

physically from the production environment and of each other.

6 The development environment should be used for development and should be configured

to allow access for developers’ workstations.

7 The staging environment should be used for functional and user acceptance testing, stress

testing, and performance benchmarking.

8 The test environment should be used as a testing environment of the Solution and its

software components and products. The test environment should be a scaled-down

configuration of the production environment.

Security Requirements

1 A secure solution should be provided at the hardware infrastructure level, software level,

and access level.

2 Authentication, Authorization & Access Control

3 factors (User ID & Password, Biometric, and Digital Signature) security mechanisms

should be implemented to enable secure login and authorized access to portal information

and services.

3 Encryption Confidentiality of sensitive information and data of users and portal

information should be ensured.

4 Appropriate mechanisms, protocols, and algorithms necessary to protect sensitive and

confirmation data and information both during communication and storage should be

implemented.


Volume II

Monitoring and Management Requirements

The the Solution should provide monitoring and management of the entire Solution including

all software components and application.

The monitoring and management should monitor health of software and hardware

infrastructure running the the Solution covering operating system, database, software

components, applications, servers, and other related software and hardware components. It

should provide proactive monitoring, alerting and reporting.

Performance and Scalability Requirements

The design of the the Solution should be scalable to handle increasing number of users.

the Solution should provide measurable and acceptable performance requirements for users,

for different connectivity bandwidths.

The the solution should provide optimal and high performance Portal Solution satisfying

response time for slow Internet connections and different browsers.

Implementation Requirements

The TSSP will be required to deploy manpower and other project resources as per the terms

& conditions of the Contract

The TSSP will be required to work closely with the SDA and perform detailed functional

requirements and analysis of the Solution to confirm and document functional / system

requirement specifications for the portal and its applications to fulfil its objectives.

The TSSP will be expected to carry the complete implementation and deployment of the the

within the timelines specified in the RFP.

The TSSP is expected to develop, test, stage, and deploy all functional modules of the the

software and any hardware components of technical & functional requirements

Project Management

Selected bidder is required to provide an implementation plan illustrating all functional analysis,

development, testing, staging, and deployment activities.

Selected bidder is required to specify and describe the different phases and activities of the

project. It is very important for the SDA that the Selected bidder provide a quality

implementation plan covering all aspects of the project. The plan shall clearly specify the start

and end dates (relative to contract signing) of each of the project phases specifying key

milestones allowing visibility of project progress.

Selected bidder is required to use standard project management tools such as precedence

diagrams, critical path charts, etc. to create and manage implementation plan and schedule.

The table below shows the minimum stages and deliverables:

Stage Activities Deliverables

Functional &

Requirements

Analysis

Define Functional Requirements

Requirements management

Prototyping

Documentation

Data Migration Preparation

Software Requirements and

Specifications Document

Detailed Scope of Work

Work Breakdown Structure

Detailed Project Schedule

Data Migration Plan


Volume II

Design

Detailed Software Solution

Architecture design

Detailed Hardware Solution

Architecture Design

Data Schema design

User Interface Design

Integration & Interfaces Design

Prototyping design Validation

Documentation

Design Specifications Documents of

Software solutions

Design Specifications Documents of

Hardware solutions

User Interface Design Specifications

Integration Design Specifications

Data design and migration

Development Software installation,

configuration, and customization

Hardware installation and

configuration

Development

Unit Testing

Documentation

Development Plan

Updated Design Document

Installed software and hardware

Functional modules & Portal Solution

Problem reporting

Testing System Testing

Integration Testing

Stress Testing

User Acceptance Test Results

Completed Test Cases

Data Migration tests

Documentation

Complete Test Cases

Test Plan

User Acceptance Criteria

Problem reporting

Problem resolution testing

Data Migration Testing

Deployment Training courses and sessions

Operations Planning

User Manual

Operations Manuals

Knowledge Transfer and training plan

Operations Plan

Operations Policies and Procedures

Selected bidder is required to describe in detail project management processes, methodologies

and procedures.

Describe what SDA resources will be necessary for the project to succeed.

Describe how SDA management will receive up-to-date reports on project status.

Describe the change management procedures to handle such things as “out-of-scope”

requests or changing business needs of SDA while the project is underway.

Describe what procedures will be used to keep the project on track, and what escalation

procedures will be employed to address any problems with project progress.

Describe what quality assurance processes, procedures, formal reviews, etc. will be in place.

Describe the proposed conflict resolution / escalation process between the Bidder and SDA to

handle project or contractual disputes.

Selected bidder is required to describe the proposed project structure identifying all project

individuals including project manager, business analysts, software developers, QA engineers,

hardware / network engineers, administrators, Change Management experts, and others.

Selected bidder shall provide a comprehensive warranty that covers all components after the

issuance of the final acceptance of the. The warranty should cover all materials, licenses,


Volume II

services, and support for both hardware and software. Selected bidder shall administer

warranties with serial number and warranty period. Upon final acceptance of the SDA, all OEM

warranties will be transferred to the SDA at no additional charge. All warranty documentation

(whether expired or not) will be delivered to SDA at the issuance of the final acceptance

certificate.

Selected bidder is required to provide Premium Level warranty and support through the vendor

for all hardware and software used for the. Selected bidder’ warranty must cover all equipment

and work activities contained in the contract against all design, manufacturing, and environment

faults until the issuance of the final acceptance.

Selected bidder is required to commit to the following warranty terms:

All products / components / parts shall be covered under OEM warranty up to the

Implementation Phase and AMC support shall commence after successful implementation.

The warranty shall include the repair or replacement of the products / components / parts during

the warranty period by the bidder. The replacement products / components shall meet the

related specifications without further repair or modification.

Selected bidder shall be liable for all costs including, but not limited to, the costs of material,

labour, travel, transport and living expenses associated with the collection and return of the

units covered by the warranty.

The date of manufacture or assembly of any equipment, parts or consumables, shall not be

more than six months before delivery.

Selected bidder shall state the location of his repair Centre(s) for all items not being repaired

onsite.

SDA has the right to require a replacement if the repair is deemed to be impractical.

Selected bidder ensure that replacement components shall be available for any failed

component during the warranty period.

Selected bidder shall guarantee the availability of spare parts and technical assistance for all

components (or appropriate alternatives) to ensure the equipment would run for at least five (5)

years, without major changes, at the completion of final acceptance. Six months advance notice

is required on any discontinued part(s) with a suggestion for alternatives.

Selected bidder need to define the process & methodology in their proposal, for achieving the

response time of engineers to respond to an incident and also for resolving such incidents as

per the SLA.

Selected bidder is required to provide additional training if the satisfaction levels/ learning does

not reach 80% in evaluation/feedback from trainees, and expected to provide additional

training, if required.

The the application & infrastructure being provisioned by the bidder shall be insured. The

Goods supplied under the Contract shall be fully insured against loss or damage incidental to

manufacture or acquisition, transportation, storage and delivery for the entire project term.

Selected bidder is required to explain their warranty, maintenance procedures, and support to

meet the terms and requirements outlined above.

Operations Requirements

The selected bidder is expected to provide the following in support of the operations:

Selected bidder shall provide procedure documentation for all operations procedures,

and SLA’s (based on ITIL best practices) for all the hardware and applications provided

including backup procedures, system update procedures, security procedures, failure

recovery procedures, upgrade procedures, remote access procedures, user manual,

SOP’s, etc.

All such procedures and documents must be submitted for review and approval by the

SDA prior to adoption. Such documentation shall be updated by the during the project

term by the bidder as and when required along with the necessary approval.


Volume II

Selected bidder will be required to provide SDA with weekly statistics reports on the

various services provided to users a mechanism as well as track and log all related

statistical reports on the various delivery channels and access patterns.

Selected bidder will be required to provide SDA with weekly portal performance reports

showing health of system operations.

Selected bidder will be required to provide SDA with Helpdesk for recording all the day

to day problems and other technical incidents occur during the O&M phase. This shall

also record the resolution of such incidents & problems.

Selected bidder will be required to commit to Service Level Agreements (SLAs) that

show, among other metrics, appropriate escalation procedures and guarantee corrective

actions within a pre-determined time. Selected bidder is required to respond to required

levels of accuracy, quality, completeness, timeliness, responsiveness, cost-

effectiveness, productivity and user satisfaction that are equal to or higher than the SLA

system requirements.

Quality Assurance & Acceptance Requirements

Selected bidder is required to develop and implement quality assurance processes and

procedures to ensure that the the development and operations are performed to meet

the quality standards that are relevant to each area in all project phases.

Selected bidder is required to use various tools and techniques that can make tests run

easily and the results are automatically measured. In this way, testing tools provide a

more cost-effective and efficient solution than their manual counterparts. Plus, they

minimize the risk of human error during testing.

In order to ensure that such a QA mechanism is effective and acceptance of the, the

following tests are required for acceptance:

Unit Testing: Basic validation of developed components by developers.

Functional / Internal Integration Testing: Validation of developed components against

functional requirements and design specifications.

System Testing: Validation of both functional and technical requirements for the

integrated Solution. This could include external integration if required or it can be

separated into testing phases.

UAT: User Acceptance Testing (UAT) validation of the Portal Solution and assurance

that it meets both functional and technical requirements

Stress and Performance Testing: Load testing enabling understanding of performance

and behaviour of Portal Solution under large number of users and high-load conditions.

Selected bidder is required to describe their QA and testing approaches and procedures

as well as testing tools for conducting various tests in support of the acceptance of the

Portal Solution. Selected bidder is expected to follow CMMi level 5 processes.

Furthermore, Selected bidder to describe their documentation standards e.g.

Documentation description, documentation identification, content, nomenclature etc. as

well.

Sample documents to be enclosed as part of the technical proposal.