+ All Categories
Home > Documents > CAS RFP_Aug 6,2013

CAS RFP_Aug 6,2013

Date post: 09-Jan-2016
Category:
Upload: bharat-arora
View: 214 times
Download: 0 times
Share this document with a friend
Description:
CAS RFP

of 25

Transcript
  • Page 1 of 25

    Request for Proposal

    For

    Development of Indian Conditional Access System (CAS)

    RFP No.: 8(22)/2012-IPHW

    Department of Electronics and Information Technology

    Ministry of Communications & Information Technology

    Electronics Niketan, 6 CGO, Complex, New Delhi 110003

    Date of Issue Issued To

    Aug 6, 2013

    1. Tata Elxsi Ltd., Bangalore

    2. Webel Mediatronics Ltd., Kolkata

    3. Bydesign India Pvt. Ltd., Bangalore

  • Page 2 of 25

    Table of Contents

    1 Contents 1. INTRODUCTION 3

    1.1. Introduction ............................................................................................................................. 3

    1.2. Critical Information ................................................................................................................ 3

    1.3. Background & Rationale for the CAS .................................................................................... 4

    Components of a CAS .................................................................................................................... 6

    2. SCOPE OF WORK: SPECIFICATIONS OF INDIAN CAS TO BE DEVELOPED ..... 7

    3. TERMS OF REFERENCE 12

    3.1. Framework for development of Indian CAS .................................................................... 12

    3.2. Penalty for Non Compliance of Provisions of RFP/ Contract ......................................... 13

    3.3. Intellectual Property Rights Related ................................................................................. 13

    3.4. Release of DeitYs Support Amount .................................................................................. 14 3.5. Role of C-DAC 14

    4. Technical Proposal 15

    4.1 Technical Proposal Compliance Table .............................................................................. 15

    4.2 Project Execution Plan 15

    5. Financial Proposal 15

    6. Instructions to Bidders 16

    7. Award Criteria 21

    7.1 Evaluation Process 21

    7.2 Technical Evaluation of Bids 21

    7.3 Financial evaluation of Bids 22

    7.4 Combined and final evaluation .......................................................................................... 22

    7.5 Notification of Award 22

    Annexure 22 Annexure 1: Bid Submission Covering letter ................................................................................... 22

    Annexure 2: Technical Bid: Approach, Methodology and Work Plan ............................................. 23

    Annexure 3: Financial Proposal ....................................................................................................... 24

    List of Abbreviations

    Abbreviation Description

    MC&IT Ministry of Communications & IT

    DeitY Department of Electronics & Information Technology

    ESDM Electronics System Design and Manufacturing

    CAS Conditional Access System

    MSO Multi System Operator

    LCO Local Cable Operators

    ICO Independent Cable Operator

    DAS Digital Addressable System

    CAREL Core Advisory Group for Research & Development in Electronics Hardware

    DTH Direct to Home

    STB Set Top Box

    OTA Over-the-Air

    PPV Pay per view

    IPPV Impulse Pay per view

  • Page 3 of 25

    1. INTRODUCTION

    1.1. Introduction Department of Electronics & Information Technology (DeitY), Government of India invited

    eligible bidders to respond to the Expression of Interest (EOI) floated for development of Indian Conditional Access System (CAS). After evaluation of responses received to call for EOI, this Request for Proposal (RFP) is being issued to shortlisted bidders to submit their Technical and Financial Proposal

    for the development ofIndian Conditional Access System (CAS) in accordance with the conditions and manner prescribed in this RFP document.

    1.2. Critical Information A. Bidding agencies are advised to study this RFP document carefully before submitting their

    proposal in response to the RFP Notice. Submission of a proposal in response to this notice shall

    be deemed to have been done after careful study and examination of this document with full

    understanding of its terms, conditions and implications.

    B. This RFP document is not transferable. C. The response to this RFP should be full and complete in all respects. Failure to furnish all

    information required by the RFP documents or submission of a proposal not substantially

    responsive to the RFP documents in every respect will be at the Bidder's risk and may result in

    rejection of its Proposal and forfeiture of the Bid EMD.

    D. Bidding agencies are requested to attend a pre-proposal briefing meeting as per details provided below.

    S. No. Information Details

    1. RFP No. and Date RFP No. : 8(22)/2012-IPHW; Date Aug 6, 2013

    2. Last date for submission of written

    queries for clarifications

    Aug 12, 2013 at 17:00 hours.

    Department of Electronics and Information Technology,

    Electronics Niketan, 6,CGO Complex, New Delhi 110003

    3 Date of pre-bid briefing Aug 13, 2013 (11.00 Hrs)

    4 Release of response to

    clarifications on

    http://www.deity.gov.in

    Aug 19, 2013

    5 Last date (deadline) for submission

    of Bids

    Aug 29, 2013 at 15:00 hours

    7 Opening of Responses: Technical

    Bid

    Aug 29, 2013 at 15:30 hours

    8 Technical Presentation by Bidders Aug 30, 2013 in order as listed above. Each bidder will

    be given a one hour slot for the Presentation/

    discussions.

    9 Contact Person for queries Shri S.K. Marwaha

    Director

    Room No. 2078-79, Department of Electronics and

    Information Technology, 6, CGO Complex, New Delhi -

    110003; 91-11-24365940, [email protected]

    10 Addressee and Address at which

    proposal in response to RFP notice

    is to be submitted

    Shri Rajesh Suri

    Deputy Director, Department of Electronics and

    Information Technology, Electronics Niketan [Cabin No

    4216 (4th Floor)], 6,CGO Complex, New Delhi - 110003;

    011-24301922

    11 Bid Validity Period 120 days from the last date (deadline) for submission of

    proposals

    12 Place, Time and Date of opening of

    Financial proposals received in

    Will be intimated later

  • Page 4 of 25

    S. No. Information Details

    response to the RFP notice

    13 Earnest Money Deposit (EMD) in

    the form of a Bank Draft

    Rs.2,00,000/- (Rupees Two Lakhs Only)

    1.3. Background & Rationale for the CAS

    The Government of India has issued an Act to amend the Cable Television Networks (Regulations) Act, 1995 to provide for a Digital Addressable System (DAS). This amendment makes it obligatory

    for every operator to transmit or re-transmit contents from a provider in an encrypted form through

    a DAS. According to the said decision, all Cable operators have abandoned analog in the four

    metros by October 31, 2012 (Phase-I). Cities with a population of more than one million have been

    covered by March 31, 2013 (Phase-II). All other urban areas would be covered by September 30,

    2014 (Phase-III) while the entire country will be covered by December 31, 2014 (Phase-IV). The

    Government of India has already announced digitization implementation plan and its support in

    every respect to facilitate indigenization of the Set Top Box. As per industry reports out of total of

    approx. 138 million TV homes in the country, about 30 million are dependent on Doordarshans terrestrial broadcast services, approx. 73 million are covered by cable services and the rest by DTH

    (Direct to Home) and IPTV (Internet Protocol Television Services). Out of approx.73 million cable

    subscribers, by April 2013 after Phase I and Phase II of DAS implementation only about approx.15

    million are on digitized platform and rest of approx.58 million on analog system. Cable services are

    predominantly analog in nature. There are Multi System Operators (MSOs) who set up their own

    Headends for reception, aggregation and retransmission of Signals from Broadcasters to Local

    Cable Operators (LCOs). There are Independent Cable Operators (ICOs) who have their own

    headends and distribute directly to subscribers. As per industry reports, there are about 100 MSOs;

    approx.7,000 ICOs and approx.60,000 LCOs. LCOs do not have headends and about 6,000

    headends need to be digitized.

    A Conditional Access System is a system that is used to limit the access of TV signals to only authorized viewers. While a CA is not meant to operate for Digital TV only and it can be used for

    digital radio broadcasts, digital data broadcasts, and non-broadcast information and interactive services,

    it is mostly associated with the Digital TV and related operations. Conditional Access System (CAS) is

    a description used for a set of hardware devices and connected software (including a Set Top Box) used

    at different stages of distribution of a TV channel through which normally the pay channels are

    transmitted in encrypted form. The subscriber is given an authorization depending upon the request to

    view one or more of such encrypted pay channels of his choice. The subscriber will pay for only

    chosen pay channels for viewing.

    The authorization is given and controlled usually by a Multi System Operator (MSO) or an Independent Cable Operator (ICO), who owns the Conditional Access System in a Cable Television

    Network. An MSO is often assisted by the Local Cable Operators (LCO).

    Basically it is the protection of content by requiring certain criteria to be met before granting access to this content. The signal is encrypted to prevent unauthorized reception. A set-top box containing a

    conditional access module is used in the customer premises to receive and decrypt the signal.

    A CAS system must enable subscribed customers to view the content and must prevent unauthorized viewers from viewing the content at the same time.

    Some related terms used in the context are the following.

    Data Streams

    A CA system is highly compute algorithm driven and is used to operate on digital data. The content that is

    subjected to conditional access therefore must be converted into digital data. An individual program that a

    broadcaster provides is composed of many elements, such as video, audio and text. In digital television,

    these elements are converted into digital form using an MPEG-2 (or MPEG-4) encoder. The MPEG-2 data

    streams of multiple TV channels are encrypted and are carried multiplexed to the end subscriber. There are

    two kinds of data streams relevant to the CAS and Digital Video Broadcast. In order to enable multiplexing,

    the data stream is broken up into packets.

  • Page 5 of 25

    PES: The sum total of the data stream packets for a program (TV Channel) is called the Program Elementary Stream (PES).

    Transport Stream (TS): The PES for multiple TV channels are time-multiplexed (combined) together, into a Transport Stream (aka Digital Video Broadcast MPEG-2 Transport Stream). The

    Transport Stream is organized in 188-byte packets for transmission.

    A CAS may implement encryption on the PES or on the TS depending upon the needs,

    requirements and flexibilities offered.

    Keys

    The Conditional Access system works by using a set of secret keys for scrambling or encryption. These

    keys are protected and hidden by various methods and are securely carried between the two end points of

    the CAS, one being the end subscriber. The keys are used to scramble the signal, making it accessible only

    to authorized set-top boxes.

    CAS in DVB

    In India, we follow the European DVB (Digital Video Broadcasting) standard. DVB standards have been

    specified separately for the following.

    DVB-CA (Conditional Access),

    DVB-CSA (the Common Scrambling Algorithm) and

    DVB-CI (the Common Interface). These standards define the method by which a digital TV stream can be made un-viewable to all

    except those STBs with valid decryption smart cards.

    Scrambling and Encryption

    Making the TV signal un-viewable selectively, is achieved by a combination of scrambling and encryption.

    Scrambling Key: The data stream is scrambled with an 8-byte secret key, called the control word. Knowing the value of the control word at a given moment is of relatively little value, as under

    normal conditions, content providers will change the control word several times per minute.

    The Control Word (CW) is generated automatically in such a way that successive values are not

    predictable. The DVB specification recommends using a physical process for that. In order for the

    receiver to unscramble the data stream, it must be permanently informed about the current value of

    the control word. In practice, it must be informed slightly in advance, so that no viewing

    interruption occurs.

    Encryption: Encryption is used to protect the control word during transmission to the receiver. Encrypted information (the control word) is sent out using two separate methods (one for short term

    and the other one for long term use).

    o ECM: The control word is encrypted as an Entitlement Control Message (ECM). The Conditional Access (CA) subsystem in the receiver will decrypt the control word only when it

    is authorized to do so.

    o EMM: The authorization to decrypt is sent to the receiver in the form of an Entitlement Management Message (EMM). The EMMs are specific to each subscriber, as identified by the

    smart card in his receiver. New EMMs are issued much less frequently than ECMs; typically

    at intervals ranging from about every 10 minutes to up to once every 6 weeks.

    The Security of a CA System depends on the Algorithm used for ECM, EMM Encryption. The

    contents of ECMs and EMMs are not standardized and each Conditional Access System uses

    different ECMs and EMMs. In fact the security of a given CA system depends primarily on the

    efficiency of the algorithm used for ECM, EMM encryption. Such algorithms are closely guarded

    secrets of the company. The CA module in the STB carries relevant ECM, EMM decryption

    algorithms.

    SIMULCRYPT: The control word can be transmitted through different ECMs at the same time. This effectively creates and allows the use of several Conditional Access Systems at the same time. This

    technique is known as SimulCrypt. SimulCrypt uses multiple set-top boxes, each using a different CA

    system and saves communication bandwidth and encourages multiple operators to cooperate. DVB

  • Page 6 of 25

    SimulCrypt is widespread in Europe; some channels, like the CNN International Europe from the Hot

    Bird satellites, can use 7 different CA systems in parallel.

    The decryption cards are read, and sometimes updated with specific access rights, either through a

    Conditional Access Module (CAM) or a PC card format card reader meeting DVB-CI standards.

    MULTICRYPT: MultiCrypt allows multiple CA systems to be used with one set-top box by using a PC card with an embedded smart card for each CA system used. Each card is then plugged into a

    slot in the set-top box. Each card recognizes the ECM and EMM needed for authorization.

    Components of a CAS

    In summary, a typical Conditional Access system involves 3 basic blocks, viz.: The broadcast equipment or

    the transport system, the Set-Top Box (shown in a blue box), and the security module as shown in the

    following figure.

    The broadcast equipment generates the encrypted programs that are transmitted to the subscriber.

    The STB receives these signals and contacts the security processor, located inside the STB, asking which of

    all the received channels can be decrypted. The security processor dictates which channels can be decrypted

    and viewed by that particular STB / subscriber. The STB then decrypts / un-scrambles these permitted

    channels.

    A CA system consists of the following main operational blocks.

    Subscriber Management System (SMS): The SMS is a subsystem of the CA system that stores and manages details of each subscriber, and the TV channels that are subscribed to by the

    subscriber. Based on the channels that the subscriber has paid for, the SMS asks for Entitlement

    Management Messages (EMM) from the Subscriber Authorization System (SAS). An EMM

    provides general information about the subscriber and the status of the subscription. The ECM

    contains the key for decrypting the transmitted programs.

    Subscriber Authorization System (SAS): The SAS is a subsystem of the CA system that translates the information about the subscriber into an EMM, when the Subscriber Management System requests for

    it. The SAS also ensures that the subscriber's security module receives the authorization needed to view

    the programs. Further, the SAS acts as a backup system in case of failure.

    Security Processor: The security processor, usually in the form of a smart card, extracts the EMM and ECM necessary for decrypting the transmitted programs. The security processor is either

    embedded within the set-top box or in a PC Card that plugs into the set-top box.

    Set-Top Box: The set-top box (STB) houses the security module that gives authorization for decrypting the transmitted programs. The set-top box also converts the digital signal to an analogue

    signal so an older television can display the programs.

  • Page 7 of 25

    Middleware: No STB is complete without a middleware, a software program that is located in the middle of two programs or systems, and provides smooth exchange of data. For the STB consumer,

    the middleware provides the on-screen look and feel of the STB. Middleware can also provide

    interfaces in multiple languages. For example, two STBs may have identical hardware but their

    users may see completely different user interface screens as provided by their middleware. Also

    when an MSO decides to offer added services such as Pay per view, only the middleware needs to

    be updated.

    2. SCOPE OF WORK: SPECIFICATIONS OF INDIAN CAS TO BE DEVELOPED Conditional Access Systems are medium independent. They work on any transport, i.e., Cable,

    Satellite or Terrestrial medium. However, as this project has been envisaged to address the Cable TV

    market initially, the system will be proposed for Cable TV systems (DVB-C) in the offer.

    To make the system complete for the cable operators, the CAS system should include a SMS and billing system. However, the operator should have option to choose external SMS and billing

    system if they so prefer. All reporting of SMS should be as per TRAI guidelines.

    The proposed CAS system has to be tested for its integration and operation with DVB compliant Multiplexers and other Cable head-end components.

    The proposed system should incorporate Indian languages for Electronic Program Guide (EPG) for consumer and in the SMS for operator.

    Open source middleware may be proposed.

    CAS needs to be fully compatible to DVB Standards wherever applicable including DVB-C, DVB-CSA, DVB-CI, DVB Simulcrypt, DVB Multicrypt, DVB-SI.

    The broad specifications for the development of the CAS system to be incorporated at the STB

    and head-end systems are as follows:

    Conditional access system is to be designed to encode the transmitted video and/or audio stream to prevent its access by any unauthorized parties.

    System functions of CAS are to include control over encryption of traffic stream, management, access granting, authorization of users, management and delivery of encrypted code words and

    keys.

    CAS security should be provided by advanced encryption algorithm and multi-level key circulation system. Arbitrarily controlled update of keyword (5-10 sec) should be offered.

    Proposed CAS should support the management of authorization validity in order to prevent the viewing of programs beyond the allowed time period, including operational requirements like

    change in sequence of broadcast modes, pause during authorization and removal of current smart

    card number.

    Proposed CAS system should use advanced encryption mechanism with high reliability chipset.

    Proposed CAS should use various data-protection technologies to protect the privacy of transmitted data from SMS and other external modules.

    Proposed CAS should deploy security strategy to prevent hacking. Hack recovery mechanism should be built into the system.

    The detailed specifications of the proposed Indian CAS are as follows:

    1. DVB-CSA: The proposed CAS must be compliant to DVB-CSA. As DVB-CSA is being superseded by DVB-CSA 3 which is based on a 128 bit AES,DVB-CSA 3 compliance will be

    optional.

    2. DVB Simulcrypt: The proposed CAS should support Simulcrypt according to ETSI TS 103 197 as per diagram below:

  • Page 8 of 25

    3. Proposed system should support Multicrypt and DVB-CI: The proposed CAS should provide its own CAM module as per EN 50221 for DVB-CI slot of Set Top Box as per diagram below:

    4. Secure Boot Loader: The proposed CAS must ensure that STB Boot Loader, which is used to

    update the software on the STB, will only permit the change in the STB software strictly upon

    establishment of authenticity of the source of the software, genuineness of the software and must

    provide protection against the malicious software download. Boot-loader will not update the

    software on the STB on its own without validation.

    5. Over-the-Air (OTA) Download: The proposed CAS should have functionality of OTA download.OTA loader will be able to do the software update. The boot-loader will verify and

    allow a verified OTA application to effect a software update and authenticate the download of

  • Page 9 of 25

    new middleware images and CAS kernel images to the STB when upgrade /update of the STB

    software is necessary through OTA carousel delivery.

    6. Protection against Control Word sharing: The control words on the STB should be kept securely and must not be shareable. CAS must ensure protection against hacking through Control Word

    sharing. Advanced security processors recommended for the proposed CAS.

    7. Secure Chip: The proposed CAS with secure chip set for STB (specific keys embedded inside each chipset individually at the time of manufacturing of the chip) will be preferred.

    8. STB in Smart Card based CAS to use the smart card to decipher the control words. Card less CAS to use secure chipset to decipher the control word.

    9. Smart Card based STB must have provision for paring with the Card. 10. Combination of Software CAS with smart card option: STB with a Smart Card slot for future

    option of Smart Card use for a Soft CAS may also be offered.

    11. Finger Printing: The proposed CAS should have comprehensive finger printing functionality. The overt fingerprinting should be changeable through the head-end system. The fingerprinting

    location, presentation including background and foreground colours, fonts and orientation should

    be controllable by the head-end system.

    12. Both Overt and Covert: The proposed CAS should have both overt and covert finger printing functionality. The covert and overt channels should be available for handshaking the finger prints

    between head-end devices and viewing device.

    a. The finger printing should not be removable by pressing any key on the remote. b. The finger printing should be done on the top most layer of the video. c. The finger printing should be such that it can identify the unique STB number or the unique

    smart card / CAS number.

    d. The finger printing should appear on all screens of STB, such as menu, EPG, etc. e. The location of finger printing should be changeable from the head end and should be

    random on viewing device.

    f. The finger printing should be able to give the number of characters as to identify the unique STB and/or the smart card.

    g. The finger printing should be possible on global as well as on the individual STB and/ or smart card basis.

    h. The overt finger printing and on screen display(OSD) messages of the respective broadcasters should be displayed by MSO/LCO without any alteration with regard to time,

    location, duration and frequency.

    i. The OSD on STB should never be disabled. 13. Subscriber Management System (SMS): A SMS to be included in the proposed CAS. It should

    incorporate mechanisms so that they are not modifiable in an unauthorized manner. The proposed

    SMS should give all the reports required by TRAI format and including following key subscriber

    data:

    a. Unique Customer ID b. Subscription Contract Number c. Billing Address d. Installation Address e. Landline Phone number f. Mobile phone number / Email ID g. Service/Package Subscribed to h. Unique STB Number i. Unique Smart Card/ CAS ID

    The SMS should provide the following features:

    a. Viewing and printing historical data in terms of activations and deactivations b. Location of each and every Set Top Box unit (Inventory management)

    The SMS should be able to generate following reports at any point of time:

    (i) The total number of authorized subscribers (ii) The total number of subscribers

  • Page 10 of 25

    (iii) The total number of subscribers subscribing to a particular service at any point of time (iv) The details of channels opted by subscriber on a-la carte basis (v) The package wise details of the channels in the package (vi) The package wise subscriber numbers (vii) The ageing of subscriber on the particular channel or package (viii) The history of all above mentioned data.

    14. Option for external SMS: The proposed CAS should also provide interface for external SMS. 15. CAS system must support the following features:

    a. Support for business models. The STB along with the CAS should be able to support the following features

    i. A-la-carte selection. ii. Pay-Per-View (PPV) based selection. Impulse Pay Per View (IPPV) based selection

    should be optional.

    iii. Program packaging (bouquets-ability with same programs offered in different ways, different geographical areas and different pricing).

    iv. Subscription upgrade. v. Event pricing.

    b. The proposed CAS must provide Custom EMM generation and handling. c. Entitlement renewals: The STB must have mechanisms to handle re-entitlement process

    through the smart card ensuring protection against card blockers and smart card cloning.

    d. Addressing: EMM addressability in groups/individuals etc. should be achievable. The definition of the groups may be based on rules definitions such as geographic locations based

    on pin code, city, etc.

    e. PIN: Mechanisms must be provided to change PINs/Reset PINs f. The proposed CAS must provide Parental Control. g. CAS should have provision for black listing of smart cards or IDs.

    16. Smart cards based CAS should support the following features: a. Pairing: There should be a provision to get a smart card bound to a specific set-top-box. A

    smart card that is bound will get paired with the same set-top-box and will not work with

    another STB.

    b. Logical security protection against cloned cards or hacked cards should be provided. c. Smart card authentication is a must using strong cryptographic challenge-response techniques

    involving zero-knowledge proof systems. The protections must be provided against man-in-

    the-middle and eavesdropper hacking attempts.

    d. The EMMs must be authenticated using the smart cards only. For this purpose the smart cards must carry keys, known to the smart cards.

    17. Card less CAS should provide same degree of security as that of Smart Card based CAS: a. Set-top-box must get bound to an embedded number serialized by the security processor at the

    time of manufacturing. This process is called the "serialization" or "pairing" key in the CAS

    industry. It is the secret key that enables the STB electronics to encrypt all communications

    over a secure "pipe" (communication channel) to the STB chipset.

    b. Software CAS must use strong cryptographic challenge-response techniques involving zero-knowledge proof systems. The protections must be provided against man-in-the-middle and

    eavesdropper hacking attempts.

    c. The Card less CAS must provide security against cloned Set top box. d. The EMMs must be authenticated using strong cryptographic protocol.

    18. CAS/SMS Interface: Encrypted EMMs and ECMs may be sent and received using the TCP/IP protocol in a secured manner between the MUX and CAS if they are not physically collocated. The

    CAS and SMS will be secured by additional firewalls in the network.

    19. Message Queuing: The head-end must queue up the messages in case of non-successful transmission of messages due to network failure (for example, due to power failure) and must retry

    them at specified intervals using additive back off retrial timings. The life of the messages in case

    there are unsuccessful deliveries should be specifiable.

  • Page 11 of 25

    20. CAS Reports: On the head-end system, the CAS system should be able to generate various reports including the following:

    a. Channel and package subscriptions b. Active/suspended/deactivated subscribers c. System health and load profile d. Error reports (such as unsuccessful deliveries, failed authentication etc.) e. Processing Time reports for messages f. EPG upload errors

    21. Critical data on the head-end must be recoverable. The data should be backed up periodically. 22. Bmails: CAS system should support Bmails. The Bmails may be typed (persistent, one-time

    viewable, stored-until-deleted etc.). STBs must have storage to keep from 50 to 100 Bmails.

    23. Integration with requests handlings through mobile phone SMS, web interfaces and other such channels may be offered for PPV and IPPV services, optionally.

    24. EPG and its Local Language support: CAS system must support Local language display (Indian languages) on screen for EPG and other messages using Unicode character coding with at least one

    (preferably two) font for each Indian language. English must be supported using multiple fonts.

    EPG information should include Parental Ratings for shows.

    EPG should provide Synopsis for each program. The synopsis should also include information like Episodic for TV shows, Team details for Sports programs, Cast Information

    for movies etc.

    EPG should provide viewer with features of Program Series and Recordings across days. 25. Middleware: The proposed CAS may have functional basic middleware. The proposed CAS

    should also support integration of third party open source middleware.

    Middleware to be installed in STB should provide a clear view of program information playing on respective channels. It should also provide ability for viewer to navigate to

    programming information for future timings.

    Middleware should be able to group Program Information on EPG menu by Channel Genre. The EPG should provide customized Genre values for each Program.

    Middleware should be capable of supporting multiple Audio Feeds of channels.

    Middleware should provide a feature of allowing viewers to set reminders for programs.

    Middleware should provide feature where viewers are able to search for programs in EPG.

    Middleware should have inbuilt place holders for mini banners on various places like EPG Grid, Program Info Page, Channel List page.

    Middleware should provide a feature of Parental lock for Program Channels.

    Middleware should be compatible and adaptable to display program information in additional languages.

    26. Support for MPEG4 part 10 as HD MPEG2/4 must be provided. 27. The STB boot time should be 5 to 30 seconds. Faster boot time will be preferred. 28. Tamper resistant Hardware: The proposed CAS hardware should be Tamper resistant to protect

    it from any attack from the head-end terminals/ interfaces.

    29. Provision for Redundancy: The proposed CAS should have provision of built- in redundancy with hot changeover of hardware in case of failure of one system to other.

    30. The bidder must detail the following CAS performance criteria: a. Maximum number of subscriptions possible in the CAS system: million b. Maximum number of controlled channels: c. Number of events that can be managed: .. d. STB boot up time: .. e. Channel Zapping time: .. f. Support of multi-level authorization: g. Maximum number of program providers possible in one system: h. EMM Transfer rate: ............................... i. EMM bandwidth Requirement: .. j. ECM Transfer Rate: .. k. Number of Transport streams controlled by one ECMG:

  • Page 12 of 25

    l. Crypto period: . m. Is Crypto period selectable or fixed: . n. Is STB based on advanced security chip? .. o. Is the proposed CAS smart card based?................................. p. Is the proposed CAS cardless?................................... q. Is the proposed CAS combination of soft CAS with smart card option? r. SMS Interface Speed: s. Names of DVB compliant MUX suppliers the proposed CAS will be tested with: t. Names of the chipsets on which CA will be ported, validated and verified for STB:

    1. .. 2. .. 3. .. u. Minimum number of STB manufactures to be licensed in one year: .. v. Names of the Indian languages for which the system will be localized for EPG and SMS:

    .. 31. The CAS should be tested against the most common attacks on the security mechanisms

    including known plaintext attack. 32. The CAS will also need to be tested by third party security analysts and an independent report

    about robustness of key mechanism shall be submitted on completion of Development Stage III

    (refer para 6.21).

    33. CAS is not a one-time development activity of a standalone software. The Proposed System need to be ported in different chipsets, integrated in STB and Head ends and has to be maintained and

    supported. The bidder should elaborate the pans for the following:

    a. Porting, validation and verification on different chipsets b. Integration and Certification on chosen STBs c. Integration and Certification on Head end Systems d. Maintenance and Enhancements of CAS e. Enhancements of CAS on account of advancements in technology in Chipsets and associated

    hardware and software components

    f. Development Support during the development and integration of new Set top boxes g. Support Infrastructure for MSOs/LCOs including call centre to help at the time of

    deployment of CAS and during its life cycle for at least 10 years.

    34. Unlike many other software development projects, this project is extremely time critical for its success through capturing the opportunity window of Phase III & Phase IV deployment of Cable

    TV digitization. The time schedule needs to be shortened by running development processes in

    parallel so that by the one year time frame not only the proposed CAS software is ready, but also

    the software is ported into different chipsets and Set Top Boxes, integrated and validated. Bidder

    should give end-to-end time schedule for entire process till Set Top Box deployment. In the

    commercial section penalty for non completion of the project as per schedule is given.

    35. The source code of the developed software with all the keys will have to be handed over to DeitY if the project is not completed as per schedule.

    36. All liabilities including security liability towards the CAS developed will rest with the Successful Bidder.

    37. Indian CAS is presently required for one way as the DAS implementation is one-way. When the Indian cable business and relevant mandate moves to two way, the migration of Indian CAS will

    follow. Bidder needs to take care that the CAS so developed is scalable to two way network.

    3. TERMS OF REFERENCE 3.1. Framework for development of Indian CAS

    The objective is to develop; and maintain (with appropriate upgrades) a CAS which can be used

    by operators for Head-end and STBs. To support development of Indian CAS, DeitY will provide

    assistance to encourage industry to collaborate with the Centre for Development of Advanced Computing

    (C-DAC). Under this support, on lines of Multiplier Grant of Scheme, if the industry supports the

    innovation and commits an amount R, the Government (DeitY) would commit a financial support of n*R to the successful bidder, where n is less than or equal to 2. The salient features of the proposed

    Indian CAS should be as follows:

    1. It should meet all the technical requirements as per the Scope of Work (refer para 2 above).

  • Page 13 of 25

    2. The developer should be able to upgrade/develop updated versions and maintain the CAS on an on-going basis, so that the CAS remains relevant.

    3. The bidder would be required to commit the following: a. Make available the developed Indian CAS to all domestic manufacturers of STB or to the

    operators at not more than USD 0.5/licence(including Smart Card, if required) for a

    period of 3 years from completion of Development Stage III(refer para 6.21), and

    b. Integrate CAS for at least 5 operators using the developed Indian CAS for at least 250,000 end users, in any combination.

    4. Once the bidder has satisfied the above conditions, separately, he may be free to licence the developed Indian CAS at market price outside India and after 3 years from completion of

    Development Stage III in India also.

    5. The successful bidder should tie up with operators serving a minimum 10% of the market in the area of its operation.

    6. The bidder MUST support the CAS for at least 10 years. 7. The bidder must provide 24*7 customer support service. 8. The integration/validation fees must be included in calculation of the project financials. 9. The integration/validation fees charged to the STB manufacturer (or any other peripheral system

    developer/manufacturer) MUST be as per uniform guidelines, to be specified in the financial

    proposal.

    10. The integration/validation for starting of Implementation Phase (Year 1) must be completed within the Development Stage III (refer para 6.21) and should also be mentioned in the Project

    Execution Plan. Further, implementation/ validation timeline may also be indicated separately in

    the Project Execution Plan.

    11. The CAS must be able to integrate prevailing STB chipsets, which should be detailed in the bid. 12. CAS system is required to be built, tested and be ready for integration and deployment within 12

    months of award of contract.

    13. The bidder must indemnify DeitY for any direct or indirect loss arising out of this project in all cases.

    3.2. Penalty for Non Compliance of Provisions of RFP/ Contract 1. DeitY will constitute a Committee viz., Project Review and Steering Group (PRSG) which will meet

    on a regular basis to oversee the implementation of the project as per schedule and recommend the

    release of next instalment of DeitYs Support Amount. 2. In case of delay in execution by the successful bidder during the development stage, 10% of the

    DeitYs Support Amount instalment of the next release will be deducted for delay up to first 15 days and further 10% in case of delay up to next 15 days. In case of further delay, the successful bidder

    will be called for meeting with PRSG to explain the reasons for the delay to enable PRSG to make

    recommendations regarding the additional penalty, or otherwise. DeitYs decision will be final and binding on the bidder.

    3. On completion of Development Stage III, if the bidder is not able to meet the commitments of the post development stages, in the given timeframe, the bidder will have to return the DeitYs Support Amount released, back to DeitY and DeitY or its nominee may take over the project without paying

    any cost to the Successful Bidder.

    4. Before completion of Development Stage III, in case the successful bidder is not willing or unable to continue with the project as detailed in the RFP, a penalty of twice the amount of DeitYs Support Amount released will be levied on the successful bidder.

    3.3. Intellectual Property Rights Related 1. The successful bidder would hold rights to the CAS. 2. In case part of development work or the post development work is outsourced, the responsibility of

    meeting the commitments as per this RFP will lie with the successful bidder.

    3. The successful bidder cannot sell off the CAS so developed or work in progress to another entity. 4. After the start of project, in case the successful bidder is not willing or is not able to continue the

    work as per the purpose and scope of this RFP, residual rights, including all codes developed/ work

    in progress codes and IPR related documentation will be transferred to C-DAC.

  • Page 14 of 25

    5. Usage of CAS and its components, etc., developed as part of this process will be solely used for the purpose and scope of this RFP. Any other application (other than Cable TV, DTH or Terrestrial TV)

    of the developed CAS or its components will require DeitYs permission in writing. 6. The Successful Bidder will ensure that there is no violation of intellectual property rights, in any

    form, during the complete duration of this project. The Successful Bidder shall indemnify the DeitY

    and C-DAC and its employees from all actions, costs, claims, demands, expenses and liabilities,

    whatsoever, resulting from any actual or alleged infringement as aforesaid and at the expenses of the

    successful bidder and DeitY shall be defended in the defence of any proceedings which may be

    brought in that connection.

    7. The modules developed/ provided by C-DAC are proprietary to C-DAC only and would be provided to the successful bidder only for the purpose of development of Indian CAS. It does not warrant the

    successful bidder to use C-DACs IPRs for any other use. 8. The successful bidder will maintain all relevant records, reports, etc. pertaining to the project.

    3.4. Release of DeitYs Support Amount 1. The DeitYs Support Amount shall be spent for the project within the specified time and any portion

    of the DeitYs Support Amount, which is not spent for the approved purposes, shall be duly surrendered to DeitY.

    2. The successful bidder shall maintain an audited record of expenditure incurred and revenue earned on this project in the form of a register.

    3. No permanent or semi-permanent assets will be acquired out of DeitYs Support Amount. 4. Should at any time the Successful Bidder cease to exist, all the rights, including all codes developed/

    work in progress codes and IPR related documentation will be transferred to C-DAC.

    5. The Successful Bidder shall render progress-cum-achievement reports to DeitY and C-DAC on monthly basis on the progress made on all aspects of the project including expenditure incurred.

    6. The Successful Bidder shall render an audited statement of accounts to DeitY on an annual basis. 7. The utilization of grant for the intended purposes will be looked into by the Auditor of Successful

    Bidder according to the directives issued by the Government of India at the instance of the

    Comptroller and Auditor General and the specific mention about it will be made in the audit report.

    8. DeitY or its nominee(s) will have the right of access to the books of accounts of the successful bidder, pertaining to the project, for which a reasonable prior notice would be given.

    9. The Successful Bidder will make all efforts to protect intellectual property generated out of the project.

    10. IPR must also reside in India so that India has access and complete control to these rights in times of emergency to protect our national interest.

    11. Application by Successful Bidder for any other financial assistance or receipt of grant/loan from any other Agency/Ministry/Department for this project should have the prior approval of Department of

    Electronics and Information Technology.

    12. The Successful Bidder is not allowed to entrust the implementation of this project for which DeitYs Support Amount is received to another institution/organization and to divert the DeitYs Support Amount received as assistance to the later institution/organization.

    13. DeitY shall appoint a Project Review and Steering Group (PRSG) comprising of representatives from DeitY and other experts. PRSG will periodically monitor the project in all respects including

    technical and financial.

    14. In case of any dispute on any matter related to the project during the course of its implementation, the decision of the Secretary, DeitY, shall be final and binding.

    3.5. Role of Centre for Development of Advanced Computing (C-DAC)

    C-DAC will be responsible for design review, code review, monitoring of the entire project, testing and validation of the entire project.

    C-DAC will also assist the bidder in localization in Indian languages in EPG and SMS.

    C-DAC will also be responsible for coordination and liaison with DeitY for the entire project.

    C-DAC will receive 15% of the Total Project Cost (excluding taxes) as fee for above mentioned role from the Successful Bidder.

  • Page 15 of 25

    Successful Bidder may discuss with C-DAC on guarantee and timelines towards above services, to be rendered by C-DAC.

    If any other support from C-DAC is required by the successful bidder, it may be negotiated separately with C-DAC on bilateral basis.

    4. Technical Proposal 4.1 Technical Proposal Compliance Table

    The bidder must conform the extent of compliance of this bid for each and every clause of the

    scope of work as detailed in para 2 above. Following compliance matrix must be filled in for each point

    of the scope of work and included in the Technical Proposal.Details on exploration and execution

    pertaining to a particular topic may be detailed after this compliance table in the Technical Proposal.

    Point by point Compliance of the

    Scope of work (Para2)

    Fully Complies Partially Complies Comments

    ( if Any)

    4.2 Project Execution Plan a. Successful Bidder needs to submit a Project Execution Schedule/ Plan covering various stages of the

    project, including, Project overview, Development of Application Software, Roll out & Project

    implementation, Application of Developed CAS, Implementation of CAS on STB, Implementation of

    CAS on Headends, Development of Middleware/ Modification of any existing middleware,

    Development of EPG, Development of SMS/ adoption of existing SMS, etc. Successful Bidder would

    ensure that the Application Software is completely operational as per the DVB-C standards and all

    the required tests will be successfully concluded.

    b. During implementation of the project, the successful bidder will also provide all the documents required for various stages of implementation. Indicative list of documents include, Project

    Commencement Documentation, Equipment Manuals: Original Manuals from OEMs and Trouble

    Shooting Manuals, Training Material, User Manuals, System Manual, etc. This may also be included

    in the Project Execution Schedule/ Plan.

    c. As provided earlier, as part of post development activities, the selected bidder shall provide implementation support for at least 10 years and the Project Execution Schedule/ Plan must take note

    of this function also.

    d. A manpower deployment plan needs to be submitted, covering all aspects of the project. e. Details on equipment and infrastructure required (existing/ to be added) needs to be detailed. f. Estimation of cost and revenue elements with breakups needs to be provided, which should include

    all aspects of the RFP.

    g. There needs to be a Project Leader (Technical) and One Project Manager (Execution) who will lead and manage the project. Successful Bidder needs to ensure that these two key professionals do not

    leave the project in between before the completion of Development Phase, as this may adversely

    affect the project. In case any one of these professionals leaves the project (during development

    stages), as a standard procedure, 10% of the total DeitYs Support Amount will be deducted from the next release. Project Leader and Project Manager need to make all the Presentations and also be

    present at all important project related discussions.

    5. Financial Proposal Bidders may provide Financial Proposal in the format given below, appended in the Annexure 3

    provided.

    Particulars Indian Rupees Rupees in words

    Total project cost including taxes

    DeitYs Support Amount sought

  • Page 16 of 25

    6. Instructions to Bidders 6.1 Completeness of Response

    1) Bidders are advised to study all instructions, forms, terms, requirements and other information in the RFP documents carefully. Submission of the bid shall be deemed to have been done after

    careful study and examination of the RFP document with full understanding of its implications.

    2) The response to this RFP should be full and complete in all respects. Failure to furnish all information required by the RFP documents or submission of a proposal not substantially

    responsive to the RFP documents in every respect will be at the Bidder's risk and may result in

    rejection of its Proposal.

    6.2 Proposal Preparation Costs 1) The bidder is responsible for all costs incurred in connection with participation in this process,

    including, but not limited to, costs incurred in conduct of informative and other diligence

    activities, participation in meetings/discussions/presentations, preparation of proposal, in

    providing any additional information required by DeitY to facilitate the evaluation process, and

    in negotiating a definitive Contract or all such activities related to the bid process. DeitY will in

    no case be responsible or liable for those costs, regardless of the conduct or outcome of the

    bidding process.

    2) This RFP does not commit DeitY to award a contract or to engage in negotiations. Further, no reimbursable cost may be incurred in anticipation of award or for preparing this bid.

    3) All materials submitted by the bidder become the property of DeitY and may be returned completely at its sole discretion.

    6.3 Signing of Communication to the DeitY All the communication to DeitY including this RFP and the bid documents shall be signed on each page

    by the authorized representative of the bidder and authority letter should be attached with the bid.

    6.4 Pre-Bid Meeting 1) DeitY shall hold a pre-bid briefing meeting with the prospective bidders at DeitY, Electronics

    Niketan, 6, CGO Complex, Lodhi Road, New Delhi. The Bidders will have to send their queries

    to DeitY by post or email.

    2) All queries to be raised in the pre-bid meeting will relate to the scope of work alone. 6.5 Bidder inquiries and DeitYs responses

    1) All enquiries / clarifications from the bidders, related to this RFP, must be directed in writing exclusively to the contact person notified in this RFP document.

    2) The preferred mode of delivering written questions to the aforementioned contact person would be through mail or fax or email. Telephone calls will not be accepted. In no event will the DeitY

    be responsible for ensuring that bidders' inquiries have been received by DeitY. The queries by

    the bidders will be provided in the following format:

    S.

    No.

    Page Section Sub-

    Section

    Details Para of the RFP on

    which Clarification is

    required

    Clarification

    Required

    3) After distribution of the RFP, the contact person notified by DeitY will begin accepting written questions from the bidders. DeitY will endeavour to provide a full, complete, accurate, and

    timely response to all questions. However, DeitY makes no representation or warranty as to the

    completeness or accuracy of any response, nor does DeitY undertake to answer all the queries

    that have been posed by the bidders. The responses to the queries from all bidders will be

    distributed to all.

    6.6 Amendment of RFP Document 1) At any time prior to the last date for receipt of bids, DeitY, may, for any reason, whether at its

    own initiative or in response to a clarification requested by a prospective Bidder, modify the RFP

    Document by an amendment.

    2) The amendment will be published in the DeitY website www.deity.gov.in

  • Page 17 of 25

    3) In order to afford prospective Bidders reasonable time in which to take the amendment into account in preparing their bids, DeitY may, at its discretion, extend the last date for the receipt of

    Bids.

    4) The bidders are allowed resubmit their bid, if required, after such amendments. 6.7 Supplemental information to the RFP If DeitY deems it appropriate to revise any part of this RFP or to issue additional data to clarify

    an interpretation of provisions of this RFP, it may issue supplements to this RFP. Any such corrigendum

    shall be deemed to be incorporated by this reference into this RFP.

    6.8 DeitYs right to modify submission deadline DeitY may, in exceptional circumstances and at its discretion, extend the deadline for submission

    of proposals by issuing a corrigendum published in the DeitY website www.deity.gov.inin which case all

    rights and obligations of the project and the bidders previously subject to the original deadline will

    thereafter be subject to the deadline as extended.

    6.9 DeitYs right to terminate the process 1) DeitY may terminate the RFP process at any time and without assigning any reason. DeitY

    makes no commitments, express or implied, that this process will result in a business transaction

    with anyone.

    2) This RFP does not constitute an offer by DeitY.

    6.10 Negotiations, Contract Finalization and Award DeitY shall reserve the right to negotiate with the bidder(s) whose proposal has been ranked first

    by the evaluation committee on the basis of best value to the Project.

    6.11 Signing of Contract At the same time as DeitY notifies the Successful Bidder that its Bid has been accepted, DeitY

    shall enter into a separate contract, incorporating all agreements between DeitY and the Successful

    Bidder. Proforma for Contract will be released in the Pre-Bid Meeting

    6.12 Disqualification DeitY may at its sole discretion and at any time during the evaluation of proposal, disqualify any

    respondent, if the agency:

    a) Submitted the proposal after the response deadline; b) Made misleading or false representations in the forms, statements and attachments submitted

    in proof of the eligibility requirements;

    c) Exhibited a record of poor performance such as abandoning works, not properly completing the contractual obligations, inordinately delaying completion or financial failures, etc. in any

    project in the preceding three years;

    d) Submitted a proposal that is not accompanied by required documentation or is non- responsive;

    e) Failed to provide clarifications related thereto, when sought; f) Submitted more than one proposal; g) Was declared ineligible by the Government of India/State/UT Government for corrupt and

    fraudulent practices.

    6.13 Confidentiality 1) Information relating to the examination, clarification, comparison and evaluation of the proposals

    submitted shall not be disclosed to any of the responding agencies or their representatives or to

    any other persons not officially concerned with such process until the selection process is over.

    The undue use by any responding agency of confidential information related to the process may

    result in rejection of its proposal.

    2) A tripartite Non Disclosure Agreement (NDA) will be signed between DeitY, C-DAC and the Successful Bidder after the issue of Notification of Award.

    6.14 Earnest Money Deposit and its amount (EMD) 1) Bidders shall submit, along with their Bids, EMD of Rs.2,00,000/- (Rupees Two Lakhs only) in

    the form of a Bank Draft in favour of Pay and Accounts Officer, Department of Electronics and

    Information Technology, Government of India, payable at Delhi.

    2) The EMD shall be denominated in Indian Rupees only. No interest will be payable to the Bidder on the amount of the EMD.

  • Page 18 of 25

    3) Unsuccessful Bidders EMD will be discharged/ returned as promptly as possible, but not later than 30 days after the award of the contract to the Successful bidder

    4) The EMD may be forfeited: i) If a Bidder withdraws his bid or increases his quoted prices during the period of bid validity

    or its extended period, if any; or

    ii) In the case of a successful bidder, if the Bidder fails to sign the Contract or to furnish Performance Bank Guarantee within specified time in accordance with the format given in

    the RFP.

    5) The EMD shall be submitted with the technical bid in a separately sealed envelope as mentioned in this section. Bids submitted without adequate EMD will be liable for rejection.

    6) Proposals not accompanied by EMD shall be rejected as non-responsive. 7) No interest shall be payable by the DeitY for the sum deposited as EMD. 8) Forfeiture of EMD: The EMD shall be forfeited by the DeitY in the following events:

    (i) If the proposal is withdrawn during the validity period or any extension agreed by respondent bank thereof.

    (ii) If the proposal is varied or modified in a manner not acceptable to the DeitY after opening of proposal during the validity period or any extension thereof.

    (iii) If the bidder tries to influence the evaluation process. (iv) If the First ranked bidder withdraws its proposal during negotiations.

    6.15 Refund of EMD and Submission of Performance Security a) The Earnest Money Deposit (EMD) will be refunded as follows.

    i) In the case of those bidders whose technical bids do not qualify, the EMD will be refunded

    without any interest accrued within one month of the acceptance of TECs (Tender Evaluation Committee) recommendations.

    ii) For the successful bidder selected, the EMD will be refunded subsequent to submission of

    Performance Security and subject to entering into a contract with DeitY.

    b) The Successful Bidder shall be required to submit a Performance Security Guarantee for 10%

    of the DeitY Support Amount for the project duration period. c) The EMD will be returned to other bidders.

    6.16 Bid Submission Format The entire proposal shall be strictly as per the format specified in this Request for Proposal and any

    deviation from the formats shall be rejected.

    6.17 Venue and Deadline for submission 1) Proposals must be received at the address specified in para 1.2. 2) Any proposal received by the DeitY after the above deadline shall be rejected and returned

    unopened to the Bidder.

    3) The bids submitted by telex/telegram/ fax/e-mail etc. shall not be considered. No correspondence will be entertained on this matter.

    4) DeitY shall not be responsible for any postal delay or non-receipt/ non-delivery of the documents. No further correspondence on the subject will be entertained.

    5) Any default by the bidder in respect of tender terms & conditions will lead to rejection of the bid & forfeiture of EMD.

    6) DeitY reserves the right to (a) reject any / all proposals without assigning any reasons thereof, b) relax or waive any of the conditions stipulated in this RFP document as deemed necessary in the

    best interest of the Ministry and the objective of the scheme without assigning any reasons

    thereof and c) include any other item in the Scope of work at any time after consultation in the

    pre-bid meeting or otherwise.

    7) DeitY reserves the right to modify and amend any of the above-stipulated condition/criterion depending upon project priorities vis--vis urgent commitments.

    6.18 Submission of Bids 1) The bidders should submit their offers in two parts namely, Technical bid and Financial bid

    and in the format given in this document.

    2) Technical Bid Original One hard Copy 3) Financial Bid Original One hard Copy

  • Page 19 of 25

    4) The bidders should submit soft copy of technical bid on a non-rewritable CD media in a sealed envelope. Technical bid should be in a single file in PDF format.

    5) The CD media must be duly signed using a permanent Pen/Marker and should bear the name of the bidder.

    6) The hardcopy and softcopy of the technical proposal should be in a single sealed envelope, clearly marked as Technical Proposal from >.

    7) The hardcopy of the financial proposal should be in a separate sealed envelope, clearly marked as Financial Proposal from > and also marked to be opened only post Technical evaluation of bids.

    8) The bidder shall seal the response to the RFP, including Technical and Financial Proposals in an outer envelope marked Response to RFP for Development of Indian Conditional Access System (CAS). The envelope shall indicate the name and address of the bidder.

    9) The inner envelopes of response to RFP shall be sealed in an outer envelope marked "RFP Selection of Agency for Development of Indian Conditional Access System (CAS).

    10) The outer envelope shall indicate the name and address of the bidder to enable the proposal to be returned unopened in case it is declared late. Both inner and outer envelopes shall be addressed to DeitY at the address specified in para 1.2.

    11) The original proposal shall be prepared in indelible ink. It shall contain no inter-lineation or overwriting, except as necessary to correct errors made by the bidder itself.

    12) Any such corrections must be initialled by the person (or persons) who sign(s) the proposals. 13) All pages of the proposal must be sequentially numbered and shall be initialled by the Authorized

    Representative of the bidder.

    14) A Bidder is eligible to submit only one Bid for the Project.

    6.19 Documents Comprising the Bid/ Check List Bidders are required to ensure that content/ documents as mentioned in the table below will constitute the

    Request for Proposal. Incomplete submission will not be considered. The bids prepared by the Bidder

    shall comprise of the following:

    Particulars Annexure

    1) Bid Submission Covering letter Annexure 1

    2) Earnest Money Deposit (EMD) amount in the form of a Bank Draft --

    3) Technical Bid with all relevant documents required as evidence of meeting technical evaluation criteria.

    Annexure 2

    as per

    provisions of

    para2 & 3

    4) Financial Proposal including a power of attorney by the CEO or competent authority authorizing the Bidder to sign/ execute the proposal as a binding

    document and also execute all relevant agreements forming part of RFP

    Annexure 3

    5) RFP Presentation (of Technical Proposal) PPT on a non-rewritable CD with Technical Propsoal

    --

    6) Undertaking regarding Conflict of Interest Ref. para 6.23 (3)

    7) All pages of the RFP Submission are to be signed on each page --

    6.20 DeitY Rights to accept / Reject any or all Proposals DeitY reserves the right to accept or reject any proposal, and to annul the short listing process and

    reject all responses at any time without thereby incurring any liability to the affected Bidder or Bidders or

    any obligation to inform the affected bidder or bidders of the grounds for DeitYs action.

    6.21 Deliverables and Times lines Development part of the project may be divided into three stages. Deliverables and Times lines

    need to be mentioned in the following table as appended in Annexure 2 on Technical Propsoal. These

    stages are as under as per following deliverables and times lines from the date of award of contract:

  • Page 20 of 25

    # Phases Activities Month

    1 2 3 4 5 6 ........ ........ ........ ........

    1. Development Stage I

    2. Development Stage II

    3. Development Stage III

    4. Implementation Phase

    (Year 1)

    5. Implementation Phase

    (Year .)

    6. Implementation Phase

    (Year 10)

    Exact dates to be worked out on issue of Notification of Award. On completion of Development

    Stage III, the Developed CAS must be ready for deployment, after prototyping, field trials with

    developed STBs, Middleware, EPG and SMS.

    6.22 Payments Related: Release of DeitYs Support Amount DeitYs Support Amount will be released to the successful bidder in three instalments as per following details:

    1) 40% of the DeitYs Support Amount against Bank Guarantee will be released by DeitY as advance. Proportionate Amount is to be contributed by the bidder.

    2) 30% of DeitYs Support Amount will be released on satisfactory completion of Development Stage I of the project. Proportionate Amount is to be contributed by the bidder.

    3) 30% of DeitYs Support Amount will be released on satisfactory completion of Development Stage II of the project. Proportionate Amount is to be contributed by the bidder.

    4) On award of contract, the successful bidder will submit Performance Security in the form of Bank Guarantee, equal to 10% of the bid amount, to remain valid for a period of sixty days

    beyond the date of completion of all contractual obligations of the supplier including warranty

    obligations. Also the bidder will give Bank Guarantee against 40% advance issued as first

    instalment of DeitYs support amount.

    6.23 Miscellaneous 1) The Successful Bidder should not assign or sublet the selection or any part of it to any other

    agency in any form without written permission from DeitY. Any such eventuality shall result in

    termination of selection and forfeiture of the performance security.

    2) The Successful Bidder shall take out and maintain, at its own cost but on terms and conditions approved by DeitY, insurance against the risks, and for the coverage, as shall be specified by

    DeitY and in accordance with good industry practice.

    3) Conflict of Interest: The bidder must specifically indicate if there is any conflict of interest arising as a result of Bidder OR any consortium partner being a CA vendor OR the bidder or any

    consortium partner having business interest in a CA vendor. In case there is a conflict of interest,

    the bidder must give undertaking, indemnifying DeitY and confirming the following:

    a) If the Bidder or any Consortium Partner of the Bidder is a CA Vendor, the Bidding Consortium or any partner of the Bidding Consortium will not promote any other CAS other

    than the CAS developed under this project in India.

    b) If the Bidder or any Consortium Partner is a STB manufacturer, the Bidder/ Consortium Partner will manufacture STBs with Indian CAS only and will not promote any other STB in

    India.

    c) If the Bidder or any Consortium Partner has broadcasting business interest including DTH service through another group company, the group broadcasting business interest will not

    affect the project.

    d) If the Bidder or Consortium partner has customers who are CA Vendors themselves and/ or develop/ modify software modules for any CA Vendor, the relationship with CA vendors will

    not affect this project, in any way.

  • Page 21 of 25

    4) Force Majeure Clause: If at any time, during the continuance of the contract, the performance in whole or in part by either party of any obligation under the contract is prevented or delayed by

    reasons of any war, hostility, acts of public enemy, civil commotion, sabotage, fires, floods,

    explosions, epidemics, quarantine restrictions, strikes, lockouts or acts of God (hereinafter

    referred to as "events"), neither party shall, by reason of such event, be entitled to terminate the

    contract, nor shall either party have any claim for damages against the other in respect of such

    non-performance or delay, provided the performance and/or delivery is resumed as soon as

    practicable after such event has come to an end or ceased to exist. The decision of DeitY as to

    whether the performance or delivery has so resumed or not, shall be final and conclusive,

    provided further, that if the performance in whole or in part or any obligation under the contract

    is prevented or delayed by reason of any such event for a period exceeding 30 days, the DeitY

    may at its option, terminate the contract without any obligation to compensate.

    7. Award Criteria 1) DeitY will award the Contract to the bidder whose Bid has been determined to be substantially

    responsive and has been determined as the Best Value Bid and proposal qualifies as per the

    minimum marks set for the technical evaluation and obtains the highest score in combined and

    final evaluation of both Technical and Financial evaluation, provided further that the bidder has

    demonstrated that it is qualified to perform services required for the project satisfactorily.

    2) A substantially responsive Bid is one, which conforms to all the requirements, terms, conditions and specifications of the Request for Proposal.

    3) Any attempt by a Bidder to influence the bid evaluation process may result in the rejection of the Bidder's Bid.

    7.1 Evaluation Process 1) The Tender Evaluation Committee constituted by the DeitY shall evaluate the Bids. 2) The decision of the Tender Evaluation Committee in the evaluation of the Technical and

    Financial bids shall be final. Technical Bid evaluation is to ensure that the proposed solution by

    the bidder meets the functional/technical requirements as outlined in the RFP Document. No

    correspondence will be entertained outside the process of negotiation/ discussion with the

    Committee.

    3) Tender Evaluation Committee will evaluate and compare the bids determined to be substantially responsive. It is Tender Evaluation Committees intent to select the proposal that is most responsive to the project needs and each proposal will be evaluated using the criteria and process

    outlined in this section.

    4) To qualify the Technical Bid Evaluation the bidder must conform to all the requirements stated in the RFP document.

    5) Financial bids of only those bidders will be opened whose technical bid complies with the requirements mentioned in the RFP document and scores 70 per cent or above.

    7.2 Technical Evaluation of Bids 1) Tender Evaluation Committee constituted by the DeitY will carry out a detailed evaluation of

    responses to the RFP and all supporting documents/ documentary evidence. Technical Bids

    received will be evaluated to determine whether they are substantially responsive to the

    requirements set forth in the Request for Proposal. In order to reach such a determination, Tender

    Evaluation Committee will examine the information supplied by the Bidders, and shall evaluate

    the same as per the evaluation criteria specified in this RFP. In the event of inability to submit

    requisite supporting documents / documentary evidence, bid shall be rejected.

    2) Proposal Presentations: The Committee shall invite each bidder to make a Presentation. The purpose of such presentations would be to allow the bidders to present their proposed approach to

    the Tender Evaluation Committee and the key points in their respective proposals. Project Leader

    and Project Manager need to be present in this Presentation.

    3) The technical evaluation of Bids will be carried out to ensure technical and functional compliance with requirements mentioned in the RFP. For all technically qualified bidders the

    financial bids will be opened for further evaluation.

    4) The Technically qualified bidders shall be ranked as per score achieved by them, from the highest to the lowest Technical Score (ST).

  • Page 22 of 25

    5) The decision of the Tender Evaluation Committee in the evaluation of responses to the Request for Proposal shall be final. No correspondence will be entertained in this regard.

    6) The Tender Evaluation Committee reserves the right to reject any or all proposals on the basis of any deviations.

    7) Proposals will be evaluated on the following Criteria:

    # Details Weight

    Technical Proposal

    1. Evaluation of Technical Proposal Compliance Table 60%

    2. Evaluation of the Project Execution Plan 40%

    Total 100%

    7.3 Financial evaluation of Bids 1) A Technical Score (ST) of seventy (70) per cent or above will be declared as technically qualified.

    The technically qualified bidders shall be ranked as per score achieved by them, from the highest

    to the lowest Technical Score. Based on the technical evaluation, the Financial Bids of only the

    technically qualified bidders shall be opened by Tender Evaluation Committee. The Financial

    evaluation will take into account the information supplied by the Bidders in the Financial Proposal,

    and shall evaluate the same as per the evaluation criteria specified in this RFP.

    2) Financial evaluation of the proposal will be carried out after determining whether the Financial Proposals are complete, unqualified and unconditional. The Support Amount sought from DeitY

    indicated in the Financial Proposal shall be considered for this purpose. The project cost indicated

    in the Financial Proposal shall be deemed as final. Omissions, if any, in costing any item shall not

    entitle the firm to be compensated and the liability to fulfil its obligations as per the Scope of Work

    within the total quoted price shall be that of the bidder. Each Financial Proposal will be assigned a

    financial score (SF). The lowest financial proposal (FM) will be given a financial score (SF) of 100

    points. The financial scores of other proposals will be computed as follows:

    SF = 100 x FM/F, where F = Amount of Financial Proposal (DeitYs Support Amount sought) 3) The Financial bid price will be all inclusive and will include, inter-alia all taxes including service

    tax and incidentals like travel, stationery, telephone expenses.

    4) Any conditionality included in the financial bid will lead to summary disqualification of the entire bid and forfeiture of the EMD.

    7.4 Combined and final evaluation 1) Proposals will finally be ranked according to their combined score (S) based on their technical

    (ST) and financial (SF) scores as follows:

    S = ST x 0.5 + SF x 0.5

    2) The Selected Bidder shall be the first ranked bidder (having the highest combined score).

    7.5 Notification of Award 1) DeitY shall notify the successful bidder in writing by hand delivery, speed post or by fax, that its

    proposal has been accepted.

    2) Until a formal contract is signed, the notification of award along with the complete RFP document including all annexure and appendices will constitute a binding Contract between Successful

    Bidder and DeitY.

    ----------- End of RFP Document -----------

    Annexure

    Annexure 1: Bid Submission Covering letter

    Notice of Intent to submit proposal in response to RFP Notice

    (To be submitted on the Letterhead of the responding agency)

    {Place}

  • Page 23 of 25

    {Date}

    To

    Deputy Director

    Department of Electronics and Information Technology

    4th

    Floor, Electronics Niketan, 6, CGO Complex

    New Delhi 110003

    Ref: RFP Notification No.: 8(22)/2012-IPHW

    Subject: Submission of proposal in response to the RFP for Selection of Agency for Development of

    Indian Conditional Access System (CAS)

    Dear Sir,

    1. Having examined the RFP document, we, the undersigned, herewith submit our proposal in response to your RFP Notification No.8(22)/2012-IPHW dated . for Selection of Agency for Development of Indian Conditional Access System (CAS), in full conformity with the said RFP

    document.

    2. We have read the provisions of the RFP document and confirm that these are acceptable to us. We further declare that additional conditions, variations, deviations, if any, found in our proposal shall

    not be given effect to.

    3. We agree to abide by this proposal, consisting of this letter, the detailed response to the RFP and all attachments, for a period of 120 days from the closing date fixed for submission of proposals as

    stipulated in the RFP document.

    4. The EMD of Rs.2,00,000/- (Rupees Two Lakhs Only) submitted by us in the form of a Bank Draft may be enchased if we do not submit the requisite Performance Security as per the Contract

    amounting to 10% of the financial bid for Development of Indian Conditional Access System (CAS), on our bid being selected.

    5. We would like to declare that we are not involved in any major litigation that may have an impact of affecting or compromising the delivery of services as required under this assignment and we are not

    under a declaration of ineligibility for corrupt or fraudulent practices.

    Dated this Day of . 2013 (Signature)

    Duly authorized to sign the Bid Response for and on behalf of:

    (Name and Address of Company)Seal/Stamp

    Annexure 2: Technical Bid: Approach, Methodology and Work Plan

    Approach, methodology and work plan are key components of the Technical Proposal. You are suggested

    to present your Technical Proposal divided into the following chapters:

    a)Technical Approach and Methodology. In this chapter you should explain your understanding of the

    objectives of the Project, approach to the Project, methodology for carrying out the activities and

    obtaining the expected output, and the degree of detail of such output. Please refer to para 2 to 5 of the

    RFP. You should highlight the problems being addressed and their importance, and explain the technical

    approach you would adopt to address them. You should also explain the methodologies you propose to

    adopt and highlight the compatibility of those methodologies with the proposed approach.

    b)Work Plan. The agency should propose and justify the main activities of the Project, their content and

    duration, phasing and interrelations, milestones (including interim approvals by the Employer), resource

    planning to be deployed and delivery dates of the reports. The proposed work plan should be consistent

    with the technical approach and methodology, showing understanding of the RFP and ability to translate

  • Page 24 of 25

    them into a feasible working plan. A list of the final documents, including reports, drawings, and tables to

    be delivered as final output, should be included here.

    The responding form is to describe the work schedule for different tasks which the responding firm plans

    to start and accomplish as part of the project, using the following format:

    # Phases Activities Month

    1 2 3 4 5 6 ........ ........ ........ ........

    1. Development Stage I

    2. Development Stage II

    3. Development Stage III

    4. Implementation Phase

    (Year 1)

    5. Implementation Phase

    (Year .)

    6. Implementation Phase

    (Year 10)

    Exact dates to be worked out on issue of Notification of Award. On completion of Development Stage

    III, the Developed CAS must be ready for deployment, after prototyping, field trials with developed

    STBs, Middleware, EPG and SMS.

    The work schedule should reflect how and by when the responding firm is expected to complete the

    assignment for each of the component, as per the major deliverable in the scope of work of the bidder and

    the timelines for achieving the same as mentioned in the RFP.

    Annexure 3: Financial Proposal

    (To be submitted on the Letterhead of the responding agency)

    [Location, Date]

    To

    Deputy Director

    Department of Electronics and Information Technology

    4th

    Floor, Electronics Niketan

    6, CGO Complex, New Delhi 110003.

    Subject: Submission of proposal in response to the RFP for Selection of Agency for Development

    of Indian Conditional Access System (CAS) - RFP No.8(22)/2012-IPHW

    Dear Sir,

    1. We, the undersigned, herewith submit our Financial Proposal for Development of Indian Conditional Access System (CAS) in accordance with your Request for Proposal RFP No.

    8(22)/2012-IPHW dated ..... and our Technical Proposal.

    2. Our attached Financial Proposal to conduct this study is as follows:

    Particulars Indian Rupees Rupees in words

    Total project cost including taxes

    DeitYs Support Amount sought

    3. We hereby confirm that the financial proposal is unconditional and we acknowledge that any condition attached to financial proposal shall result in rejection of our financial proposal. Our

  • Page 25 of 25

    Financial Proposal shall be binding upon us subject to the modifications resulting from Contract

    negotiations, up to expiration of the validity period of the Proposal. Commissions and gratuities paid

    or to be paid by us to agents relating to this Proposal and Contract execution, if we are awarded the

    Contract, are listed below:.............................. 4. If our proposal is accepted, we will obtain necessary bank guarantees in the formats given in the bid

    document issued by a bank in India, acceptable to DeitY.

    5. We agree for unconditional acceptance of all the terms and conditions in the bid document and also agree to abide by this bid response for a period of 120 days from the date of submission of bids and it

    shall be valid proposal till such period with full force and virtue. Until within this period a formal

    contract is prepared and executed, this bid response, together with your written acceptance thereof in

    your notification of award, shall constitute a binding contract between us and DeitY.

    6. We confirm that the information contained in this proposal or any part thereof, including its exhibits, schedules, and other documents and instruments delivered or to be delivered to DeitY is true,

    accurate, and complete. This proposal includes all information necessary to ensure that the statements

    therein do not in whole or in part mislead DeitY as to any material fact.

    7. We agree that you are not bound to accept the lowest or any bid response you may receive. We also agree that you reserve the right in absolute sense to reject all or any if the products / service specified

    in the bid response without assigning any reason whatsoever.

    8. It is hereby confirmed that I/We are entitled to act on behalf of our corporation/company/agency/organization and empowered to sign this document as well as such

    other documents, which may be required in this connection.

    Dated:

    (Signature)

    Duly authorized to sign the Bid Response for and on behalf of:

    (Name and Address of Company)Seal/Stamp

    CERTIFICATE AS TO AUTHORISED SIGNATORIES I, certify that I am . of the ., and that who signed the above proposal is authorized to bind the company, pursuant to the resolution passed in the meeting of Board of Directors of the

    Company on _________(date).

    Date (Seal here)


Recommended