Rfp dolci v1.0
Upcoming SlideShare
Loading in...5
×
 

Rfp dolci v1.0

on

  • 1,116 views

RFP digitaal platform van branche organisaties KBb en GAU bevat de 130 requirements die uitgevers en boekverkopers hebben opgesteld om te bepalen welke diensten het digitaal platform (aangeduid met de ...

RFP digitaal platform van branche organisaties KBb en GAU bevat de 130 requirements die uitgevers en boekverkopers hebben opgesteld om te bepalen welke diensten het digitaal platform (aangeduid met de naam DOLCI) moet kunnen leveren. Op basis van deze 130 requirements zijn partijen geselecteerd om het platform te realiseren en te beheren.

Statistics

Views

Total Views
1,116
Views on SlideShare
873
Embed Views
243

Actions

Likes
0
Downloads
24
Comments
0

4 Embeds 243

http://boekeman.blogspot.com 195
http://boekeman.blogspot.nl 43
http://paper.li 3
http://boekeman.blogspot.be 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Rfp dolci v1.0 Rfp dolci v1.0 Document Transcript

  • Request for Proposal DOLCI (distributie, opslag, levering, clearance informatie)RFP e-bookplatform, version 1.0 August 2011 Page 1
  • Change history Date Version Author(s) Changes May 24th 2011 0.1 PR / JvdN / FD Start of document May 25th 2011 0.2 PR / JvdN /FD Structure reshuffled May 27th 2011 0.3 PR / JvdN /FD Discussion with G. Noorman th June 17 2011 0.9 PR / JvdN / FD Adding non functionals, finalizing document st August 1 2011 0.91 FD Merge with KBb documents nd August 2 2011 0.95 FD / PR Merged RFP / RFI and title catalogue separated th August 4 2011 0.96 FD / PR Discussion with MK and MvE th August 10 2011 0.99 MvE / PR Final update / input MvE / MK / PRDocuments referencedName ReasonAuthorizationName, function Place, dateRFP e-bookplatform, version 1.0 August 2011 Page 2
  • Contents1 RFP PROCESS / SCHEDULE OF EVENTS .......................................................................................... 5 1.1 CONTENTS OF THE RFP ..................................................................................................... 5 1.2 PRE-PROPOSAL CONFERENCE .............................................................................................. 6 1.3 QUESTIONS FROM THE SUPPLIER .......................................................................................... 6 1.4 TERMS AND CONDITIONS ................................................................................................... 6 1.5 SCHEDULE OF EVENTS ....................................................................................................... 72 GENERAL INFORMATION ............................................................................................................. 8 2.1 DEFINITIONS.................................................................................................................. 8 2.2 PURPOSE...................................................................................................................... 8 2.3 BACKGROUND ................................................................................................................ 8 2.4 OBJECTIVES AND SCOPE OF THE PLATFORM .............................................................................. 9 2.5 OVERVIEW OF THE PLATFORM ........................................................................................... 10 2.6 PHASING OF PLATFORM IMPLEMENTATION ............................................................................ 133 REQUIREMENTS ....................................................................................................................... 14 3.1 RELEASE OF NEW TITLES .................................................................................................. 14 3.1.1 Phase 1 requirements ......................................................................................... 14 3.1.2 Phase 2 requirements ......................................................................................... 15 3.1.3 Phase 3 requirements ......................................................................................... 15 3.2 CONTRACT MANAGEMENT / COMMERCIAL PROPOSITIONS ........................................................... 16 3.2.1 Contract management ........................................................................................ 16 3.2.1.1 Phase 1 requirements .............................................................................................................................................16 3.2.1.2 Phase 2 and 3 requirements ...................................................................................................................................17 3.2.2 Commercial propositions ................................................................................. 17 3.2.2.1 Phase 1 requirements .............................................................................................................................................17 3.2.2.2 Phase 2 requirements .............................................................................................................................................17 3.2.2.3 Phase 3 requirements .............................................................................................................................................18 3.3 ASSORTMENT MANAGEMENT ............................................................................................ 18 3.3.1 Phase 1 requirement ........................................................................................... 18 3.4 ORDERING DIGITAL PRODUCTS ........................................................................................... 18 3.4.1 Phase 1 requirements: Buying/selling digital products ............................................ 18 3.4.2 Phase 2 requirements: Subscriptions and temporal licenses .................................... 19 3.5 DOWNLOAD AND READ / DELIVERING DIGITAL PRODUCTS............................................................ 19 3.5.1 Phase 1 requirements: On-line delivery ................................................................. 19 3.5.2 Phase 1 requirements: Connect to outlets with their own delivery solution ............... 20 3.5.3 Phase 1 requirements: Sales and Delivery in physical outlets ................................... 20 3.6 CLEARANCE & BILLING .................................................................................................... 21 3.6.1 Reporting and KPIs .......................................................................................... 21 3.6.1.1 Phase 1 requirements .............................................................................................................................................21 3.6.1.2 Phase 2 and 3 requirements ...................................................................................................................................21 3.6.2 Financial clearance .......................................................................................... 22 3.6.2.1 Phase 1 requirements .............................................................................................................................................22 3.6.2.2 Phase 2 and 3 requirements ...................................................................................................................................22 3.7 PLATFORM SERVICES ...................................................................................................... 22 3.8 ADDITIONAL SERVICES FOR OUTLETS .................................................................................... 23 3.8.1 Phase 1 requirements: white label webshop .......................................................... 23 3.8.2 Phase 2 requirements: Cloud reading .................................................................... 23RFP e-bookplatform, version 1.0 August 2011 Page 3
  • 3.8.3 Phase 3 requirements: User profiling services ........................................................ 23 3.8.4 Phase 3 requirements: Single sign on (Digi-D like) .................................................. 23 3.8.5 Phase 3 requirements: Book shelf services ............................................................. 23 3.8.6 Phase 3 requirements: Search and target .............................................................. 24 3.8.7 Phase 3 requirements: Experiences ....................................................................... 24 3.9 ADDITIONAL SERVICES FOR PUBLISHERS................................................................................. 24 3.9.1 Phase 2 requirements: Conversion services ............................................................ 244 TECHNICAL DESIGN / NON-FUNCTIONAL REQUIREMENTS ............................................................ 25 4.1 ARCHITECTURAL GOALS AND CONSTRAINTS ........................................................................... 25 4.2 PRINCIPLES ................................................................................................................. 25 4.3 USABILITY ................................................................................................................... 26 4.4 SECURITY & PRIVACY ..................................................................................................... 26 4.5 SCALABILITY AND PERFORMANCE ........................................................................................ 27 4.6 SOURCING & TECHNICAL AVAILABILITY ................................................................................. 27 4.7 INTEGRATION............................................................................................................... 28 4.8 FLEXIBILITY ................................................................................................................. 28 4.9 DATA INTEGRITY ........................................................................................................... 295. APPENDIX 1: USE CASES ............................................................................................................ 30RFP e-bookplatform, version 1.0 August 2011 Page 4
  • 1 RFP process / schedule of eventsThe purpose of this RFP is to solicit competitive, sealed, proposals and a demo-version to establisha contract for the development, maintenance & support and running of an Infrastructure (System)or a Service for the distribution, delivery and clearance of digital products.The RFP for this digital / ebook platform (working title DOLCI) consists of 2 separate parts: 1. High level functional requirements for the catalogue and related functionality (formal RFP will be released separately on a later date) 2. RFP for the distribution of digital products, access to digital products and clearance and billing of corresponding transactions.This RFP focuses on the distribution, access and clearance. Taking into account that the functionalrequirements for the catalogue are in progress, the platform needs a seamless integration ofcatalogue and other functionality.This RFP is sent to LGCNS / DNAML, Libreka, ePagine and eBoekhuis. Vendors are free to worktogether and submit a combined proposal if seen fit.1.1 Contents of the RFPThe requested information concerning this RFP consists of the following elements: 1. Offerer’s view / ideas on the ideal demand-supply (publisher / retailer – offerer) operating organization for the digital ebook / product platform and the leadership role you would like to fulfill. Please explain how you would like to lead GAU-KBb on innovation and enable them to stay competitive in an ever faster changing world. 2. Detailed functional and technical description of the solution at hand including the development roadmap. 3. A statement of compliance for every single requirement stated in this document (see chapter 3 and 4). Please state either ‘fully compliant’, ‘partially compliant’, ‘custom’ or ‘non compliant’ together with a further explanation. 4. The basic shape of a project, implementation & test plan for the development of this e-book platform outlining the breakdown of activities, products and required workforce (both on a timescale and as milestones) plus the proposed way to organize this project and what preconditions are to be met. The basic shape of the Test Plan should give the outline of a Test Strategy, Test Design, Test Execution and Test Reporting. 5. A cost proposal / business – pricing model consisting of a. The project costs stated in separate items with a distinction in design, build, test and implementation. Project management is to be listed separately.RFP e-bookplatform, version 1.0 August 2011 Page 5
  • b. Investments being any costs for items (not being licenses) that run for longer than 1 year (e.g. specific hardware) c. Operating / running costs per item (e.g. licenses, hosting costs, maintenance (of hard- and software), support, fee per downloaded item, costs of FTE to run Operations) 6. A demonstration of vendors’ ability to meet the requirements stated in this RFP. To this end Use Cases are given in Appendix 1. The demonstration is meant to be a live display of functionality on existing components Offerer has available.Offerer is kindly requested to submit items 1, 2, 3 and 4 by the end of August.The RFI responses given earlier will be part of the vendor evaluation. Offerer is free to elaborateon this.1.2 Pre-Proposal ConferenceA mandatory pre-proposal conference is scheduled in the week of August 29 th. Each potentialofferer may send a maximum of two (2) representatives. Specific questions concerning the RFPshould be submitted in writing prior to the pre-proposal conference. Additional questions may beentertained at the conference; however, responses may be deferred and answered at a later date.Written copies of all questions and official responses will be supplied to all potential offerers.1.3 Questions from the supplierIf you have any questions, please contact Pieter Ruempol, pruempol@orangeswan.nl (mobilephone: +31 651 56 74 29).1.4 Terms and ConditionsThe contents of this RFI document and your response is both by you and by the KBb / GAUconsidered confidentially. It is prohibited to use information from this document for otherpurposes than answering this RFI.Any cost made by a supplier due to this request for information will not be compensated in anyway.RFP e-bookplatform, version 1.0 August 2011 Page 6
  • 1.5 Schedule of EventsEvent Date(s) / timeRFP Release Date August 10 - 2011Deadline for Receipt of Written Inquiries August 29 - 2011Pre-proposal conference August 29 to September 9 - 2011Demonstrations September 13 and 14 - 2011Evaluation Period September 18 to 30 - 2011Anticipated Contract Award October 15 – 2011Anticipated start of project October 16 - 2011RFP e-bookplatform, version 1.0 August 2011 Page 7
  • 2 General Information2.1 Definitionsterm definitionBISG Book Industry Study GroupDRM Digital Right Management (e.g. Adobe for e books)DOLCI Working Title for digital platforme book Electronic version of a book. Also: all kinds of digital productsISBN International Standard Book Number (ISBN) is a 13-digit number that uniquely identifies books and book-like products published internationallyISTC International Standard Text Code (ISTC) is a numbering system developed to enable the unique identification of textual works.KBb Koninklijke BoekverkopersbondNUV Nederlands UitgeversverbondGAU Groep Algemene Uitgevers (part of NUV)Offerer the company (or consortium of companies) that makes a proposal to this RFPONIX 3.0 the international standard for representing and communicating book industry product information in electronic formKPI Key performance indicators both for system performance and all business transactionsPrincipal any natural or legal person for whom a project is carried out; here: KBB / GAURFP Request for ProposalsWebsite/websh Online marketing and sales platform of the retailer.op2.2 PurposeThe purpose of this RFP is to solicit competitive, sealed, proposals and a demo-version to establisha contract for the development, implementation, maintenance and operation of an Infrastructure(System) or a Service for the distribution, delivery and clearance of digital products.2.3 BackgroundThe market of booksellers and publishers is changing rapidly. The growth of e-books and otherdigital forms of content (digital products) are a main driver for these changes. Major internationalplayers enter the market. To cope with these challenges and to strengthen the position of theDutch book market, book sellers (associated in the KBb) and publishers (associated in the GAU)want to offer a facilitating “digital e-book / product platform” to their members. This platform willbe called DOLCI in the remaining of this document.RFP e-bookplatform, version 1.0 August 2011 Page 8
  • 2.4 Objectives and scope of the platformThe main objective of the e-book platform is to facilitate: “To realize one, unambiguous digital platform for digital publications in The Netherlands, which enables publishers and booksellers to establish their own course in the distribution of digital products and enables them to manage and use all possible digital distribution channels in selling products and services at prices in conformity with the market.”And in more general terms: “To realize one unambiguous digital platform that supports and helps customers (end-users) in an attractive and simple way to find, buy, use and read digital products.”To facilitate these goals, the scope of the platform includes: a complete and correct database with all available Dutch titles in all appearances (including the physical books) including a set of collectively shared metadata an online distribution facility for the digital appearances of these products (the digital “e-book” files) o This also includes magazines, apps and other digital products a number of basic functionalities to facilitate the correct use of content (download, streaming) and the related transactions (clearance between retailer and publisher/author)In addition to the basic and fully shared functionalities and content of the platform: KBb’s intention is to offer a set of additional services which are optionally available as modular “white label services” (at a certain additional cost). These services are meant as an (integrated) add-on to the retailer’s/bookseller’s own website and may offer the retailer competitive advantage against other booksellers, while the central platform functionalities should not influence the competition between KBb-members and users of the platform. GAU’s intention is to offer a set of additional services which are optionally available for smaller publishers to convert conventional products to digital products.Out of scope are:  The customer sale and financial transaction between customer and retailer is out of scope of this platform and takes place “at the retailer (web)site”.  The creation of digital products themselves. These take place at the publisher infrastructure.RFP e-bookplatform, version 1.0 August 2011 Page 9
  • 2.5 Overview of the platformThe landscape DOLCI is in, can be depicted as follows:This overview shows different types of publishers, some with their own internal systems forcataloguing, storage and conversion, others lacking these facilities. The platform should be able toconnect all types of publishers.The platform should be able to connect to all kinds of retailers (or outlets). These include KBbretailers but also other outlets, some without an infrastructure for selling electronic products,others with a complete eco-system for selling en delivering electronic products to their customers(e.g. Amazon, Apple and Google).The platform acts in between these parties realizing one unambiguous digital platform thatsupports and helps customers (end-users) in an attractive and simple way to find, buy, use andread digital products.”RFP e-bookplatform, version 1.0 August 2011 Page 10
  • The processes of DOLCI and their required support are shown in the next picture.Release of new titles / Digital products and Catalogue(+)The platform should host a catalogue that can be fed by publishers, authors, retailers and externalfeeds according to an industry set standard to offer a rich, complete and correct catalogue thatcan be used by retailers as a basis for their websites.Contract Management / Commercial propositionsPublishers and retailers can subscribe to the platform and the platform should facilitate inestablishing, registering and enforcing these contracts.Publishers and retailers want to be able to combine titles, both electronic and physical, DRM formsand pricing models in commercial propositions. The platform should facilitate these.Assortment managementFrom the entire collection of ‘all’ publishers, a subset is made available to a retailer (based on thecontractual agreements). Within this subset the retailer can select titles to include in his ownassortment/online catalogue. Sales prices, subscription forms and prices, retailer-ownedmetadata, upselling and cross selling logic et cetera have to be added in retailer’s web platform (orthrough a white label service) and not in the central platform.RFP e-bookplatform, version 1.0 August 2011 Page 11
  • On-line orderingThe actual purchase of an e-book (or better: of content rights) takes place at the retailer’s website.Based on this sale, the retailer website requests the central platform to provide the consumer with“an access key” to the digital distribution facility. This key and/or the downloaded file mustcontain all relevant protections and rights, based on the (social) DRM requirements as described indetail later. The key must be valid for the customer “forever” (digital locker functionality)Consumer download and reading / delivery of digital productsWith the “access key” the consumer can download or ‘stream’ the purchased content from thecentral distribution service in the requested format, the decision if the content is available fordownload or in a streaming format is made by the publisher and retailer. Customer reactions(reviews, user generated content et cetera) will be stored and owned at the retailer’s site.Clearance and billingAll transactions of the platform are logged. The platform facilitates publishers, retailers and theplatform manager with relevant reports and KPIs. These reports respect the agreement aboutinformation sharing made between publishers and retailers.The provision of the “access key” to the consumer is also the trigger to update the financialclearance administration, based on the contractual pricing agreements between publisher/authorand retailer. These and other platform activities have also to result in an update of the platformservice administration (to facilitate the clearance between “platform” and retailers) and in anupdate of relevant management information reports as defined.Platform managementTo technically operate the platform, functionality and technical reporting is required to supportplatform management in their daily operation.Publishers and retailers not always use the same terminology. The following glossary of terms canbe used for differences in terminology. Both terms will be used in this RFP:Publisher RetailerSubset of the entire collection of all publishers Assortment managementfrom which a retailer selects his ownassortment / online catalogueDelivery of digital products to the customer Consumer download and readingOutlet RetailerOrdering of digital products Consumer purchaseRFP e-bookplatform, version 1.0 August 2011 Page 12
  • 2.6 Phasing of platform implementationFor the implementation of the digital platform there are currently 3 phases defined: 1. DOLCI Basic: this phase focuses on the initial implementation of the platform supporting basic transactions and propositions between consumer – retailer - publisher 2. DOLCI Complete: supporting more complex commercial propositions (more digital formats, DRM, temporarily licenses) and adding specific functionality for retailer (white label webshop components) and publisher (conversion services) 3. DOLCI additional functionality: more complex commercial propositions (folio and digital products), digital shelf, tbd.RFP e-bookplatform, version 1.0 August 2011 Page 13
  • 3 RequirementsFor the sake of intelligibility the specifications are numbered continuous. As mentioned in chapter1 Offerer is requested to provide a statement of compliance for every single requirement stated inthis document.3.1 Release of new titles3.1.1 Phase 1 requirementsThe platform should support all types of digital products including:1. EPub, please specify the versions supported including DRM.2. PDF, please specify the versions supported including DRM.3. Other. Please specify other digital products that are supported by the platform.As mentioned in chapter 1 the detailed requirements on the information, metadata, content andfunctionality of the catalogue are in progress and will be released in a separate RFP. The platformshould be able to integrate seamlessly with the catalogue and the phase 1 requirements asmentioned below.4. The National product database / catalogue+ needs to be maintained in a decentralised manner (each publishers and /or retailer delivers its information) and maintained centrally (consistent view on all data).5. Publisher and retailer deliver digital product information to DOLCI in ONIX 3.0 format or using a simple graphical user interface.6. Publisher and retailer can deliver digital products in any format that needs to be supported.7. Publisher and retailer can also publish products that are accessible on-line and do not have a digital file.8. The catalogue should support every possible digital format.9. The catalogue should support all folio format related metadata such that folio can also be included in the catalogue.10. Subsets of the catalogue can be made available to outlets in both ONIX 3.0 format and in a simple format.11. The catalogue should implement the ONIX for books release 3.0 standards (both the catalogue structure as the interchange formats and ftp interface) for digital products. New developmentsRFP e-bookplatform, version 1.0 August 2011 Page 14
  • within the ONIX community relevant to the sales and distribution of digital products need to be adapted. (http://www.editeur.org).12. <<discussion / your ideas >> The BISG guideline for the identification of digital products should be implemented.13. Data quality. The quality of the information in the catalogue should guaranteed, both syntactical as semantical. This can be done either by automated or manual means.14. Capacity and scalability. The initial size of the catalogue is <<100.000>> products. It should be possible to scale up to <<10.000.000>> products. Pricing should be included for scalability.15. Catalogue information can be made available to outlets in a restricted way (as defined by the publishers and retailers). This includes both the products themselves as the metadata that is made available. It should be possible to differentiate at publisher, outlet and product level.16. The Catalogue should support product variants (grouping of product). This includes different media, different formats and different languages of a product.17. Specify the conditions for integration of third-party catalogue and product store.18. Specify the differences between using a third-party catalogue or using the platform’s native catalogue and product store.3.1.2 Phase 2 requirementsThe platform should support all types of digital products including:19. BLIO, please specify the versions supported including DRM.20. Adobe Digital publishing, please specify the versions supported including DRM.In addition to the title feeds of Dutch publishers title feeds from foreign publishers need to besupported by the platform.21. Please specify the additional feeds that are supported by the platform.3.1.3 Phase 3 requirementsThe platform should support all types of digital products including:22. Mobile apps. Both Apple and Android apps.RFP e-bookplatform, version 1.0 August 2011 Page 15
  • 3.2 Contract management / commercial propositions3.2.1 Contract managementPublishers and retailers must subscribe to DOLCI. The agreements between a retailer and apublisher are recorded in a contract. A contract (according to the platform) is a pricing, deliveryand information agreement per digital product / commercial proposition.3.2.1.1 Phase 1 requirements23. Publishers and outlets need to register at DOLCI. For this, a set of basic information needs to be registered.24. A manual acceptance of an outlet or publisher is required before an outlet/publisher is activated on DOLCI.25. Only activated publishers can distribute digital products using the platform. Only activated outlets can sell digital products using the platform.26. The publisher determines what outlet can sell which products on which conditions. For this, an efficient interface using defaults and exceptions is required. These conditions include pricing, payment, reporting, delivery and catalogue information.27. The platform must be able to handle company hierarchies (both on publisher and retailer site). a. Purchasing combinations in which one company makes the deals for its franchise retailers b. One main pricing agreement with a company, but additional agreements with individual franchise retailers28. Agreements between retailer and publisher have a starting date in the past or in the future. A contract can contain agreements (also on title level) that are not valid right now, but from a predefined date in the future.29. The contracting feature must be able to support different prizing propositions, including:  Margin based on a fixed sales price (agency model))  Profit based on a fixed purchase price  Several prizing possibilities for subscription models30. The retailer is able to view the prizing agreements per title, category, nur code, etc. of all publishers he has contracts with. Agreements can be made on single products or commercial propositions.31. The retail is able to find all contract information per contract with a publisher. This information is at minimum:  Purchase and sales prices (including promotions)  Type of appearance and corresponding handling (e-book via the platform, physical book several possibilities based on contract, POD several possibilities based on contract, etc)  Publisher and retailer actions on title level  Contract end date / period.RFP e-bookplatform, version 1.0 August 2011 Page 16
  • 32. The retailer can search from its own back-end using a web service or directly on the platform via the GUI33. Publishers and outlet information, including the conditions between publishers and outlets, are maintained within DOLCI and control the other services of DOLCI.34. Registration and maintenance of this information is done using a user-friendly and easy accessible interface.35. The information is secured such that publishers and outlets only have access to the subset of information that is relevant to them.36. The information is secured such that unauthorised users never can access this information.37. DOLCI should be able to host 500 publishers and 2500 outlets.38. Enable the general platform manager (technical and functional support), retailer and publisher to change a contract on the platform or to create a new one.3.2.1.2 Phase 2 and 3 requirementsThe contract management functionality must grow with the features added to the platform inphase 2 and phase 3. In order words what makes the contract management module flexibleenough to support new functionality against reasonable costs?3.2.2 Commercial propositionsBoth retailers and publishers should be possible to define and handle proportions of combinedproducts on the platform.3.2.2.1 Phase 1 requirements39. The platform must be able to handle packages for individual retailers but also for purchasing groups  Selling a book give the right to download the e-book for a discounted price  Buy 2 e-books and get a third for free40. Registration and Maintenance of propositions must be possible on different levels: a. product level : modification of proposition is valid for all outlets that have product b. outlet level: modification of proposition is valid for all products carried by one outlet c. product-outlet level: modification of proposition is valid for one product of one outlet only3.2.2.2 Phase 2 requirementsRFP e-bookplatform, version 1.0 August 2011 Page 17
  • 41. It should be possible for publishers and retailers to define proposition based on temporary licenses to digital products.42. It should be possible for publishers and retailers to easily define propositions consisting of different digital products, both sell and temporary licenses.3.2.2.3 Phase 3 requirements43. It should be possible to define propositions on part of the content of digital propositions.44. It should be possible to differentiate in price for digital products in different commercial propositions.45. It should be possible to define propositions consisting of both digital products and physical books (taking into account the fixed book price on folio)3.3 Assortment management3.3.1 Phase 1 requirement46. The retailer is able to see which content he can sell, and select the ones he wants to sell on his webshop.3.4 Ordering digital products3.4.1 Phase 1 requirements: Buying/selling digital productsDigital products can be bought by customers through the retailers web shop. To this end, theplatform enables a web-service to support the ordering transactions.47. Outlets can place orders at DOLCI for digital products through a web-interface or other easy to implement API.48. Orders are authorised by DOLCI (is the outlet authorised for the specific digital product).49. All relevant information regarding an order (needed for handling, administration and reporting) is administered in DOLCI.50. Publishers are not allowed to access information about individual customers of digital products.51. Only after successful authorisation, access may be granted to the digital product.52. Each relevant status of an order is maintained (received, authorised, delivered, …)RFP e-bookplatform, version 1.0 August 2011 Page 18
  • 53. The order service should be able to process 25.000 orders per day with peaks of 10.000 orders per hour.54. The order service should be scalable to support an increase in the amount transactions.55. Order transactions have to be completed within a maximum response of 1 second.56. The order information should be encrypted on the interface.57. Illegal access to the order interface should be detected, notified and blocked.58. The atomicity of order transactions should be guaranteed, also in cases of failure.3.4.2 Phase 2 requirements: Subscriptions and temporal licensesBesides buying digital products it should be possible to subscribe to a series of digital products orobtain a digital license to (a part of) a product.59. It should be possible to obtain a temporal licence to a product which is valid for a specified period of time.60. If required by the publisher, the temporal license needs to be enforced using DRM or in the cloud reading application.61. It should be possible to subscribe to a series of digital products.62. Subscriptions will be handled on the retailer platform commercially. The consequential rights need to be supported by the platform.3.5 Download and read / delivering digital products3.5.1 Phase 1 requirements: On-line deliveryAfter a successful order transaction, a customer can get access to a digital product. This meansthat he can download the product, download a DRM-ed version of the product or that he isgranted access to a product on-line (cloud reading).63. DOLCI needs to support different types and formats of digital products with different forms of security of DRM.64. Adobe DRM should be supported.65. Social DRM should be supported, including watermarking.RFP e-bookplatform, version 1.0 August 2011 Page 19
  • 66. Microsoft DRM should be supported.67. The publisher is able to determine which forms of DRM need to be applied.68. Digital products can be delivered to the customer directly.69. Digital products can be delivered to the customer on his digital shelf.70. Delivery of a digital product should be secured. Only the customer that has bought the product may receive the product with the appropriate DRM applied.71. Delivery of a digital product to the customer should be guaranteed.72. The delivery service should be able to process 25000 deliveries per day with peaks of 10000 deliveries per hour.73. The platform manager is able to set the DRM rules3.5.2 Phase 1 requirements: Connect to outlets with their own delivery solutionRetailers with their own ecosystem for delivery and DRM have to be supported by the platform aswell. These retailers get access to the “naked files” and report back to the platform on their sales74. It should be possible to sell and deliver digital products through outlets with their own ecosystem.75. It should be possible to sell and deliver through the Apple ibook/app store.76. It should be possible to sell and deliver through the Google store.77. It should be possible to sell en deliver through the Amazon and KOBO bookstore.78. It should be possible to quickly add support for another outlet with its own eco-system.79. Each publisher can control if he connects to these outlets and which products are made available to which outlet.80. DOLCI receives and integrates the reports of the outlets real-time in the integrated reporting functionality of the platform to the publishers (as far as these are available).3.5.3 Phase 1 requirements: Sales and Delivery in physical outletsBesides sales from web shops, it should also be possible to sell electronic products in physicaloutlets.81. The consumer should be able to buy electronic products on a physical carrier (e.g. usb, coupon) in physical outlets (bookstore).RFP e-bookplatform, version 1.0 August 2011 Page 20
  • 82. Consumer should be able to gain access to the digital product through DOLCI.83. Each sale and delivery through a physical outlet needs to be administrated by DOLCI. Which information will be shared between publisher and retailer is to be decided.3.6 Clearance & billing3.6.1 Reporting and KPIs3.6.1.1 Phase 1 requirementsThe platform must be able to report all financial transactions for the publisher and the retailer thathas been done between them in case of an e-book subscription / sale.It must be able to report all financial clearances. There also needs to be strict authorizationpolicies in place so the retailers and publishers can only see their own transactions.84. Several reports with all data, or one file that can be used in several reporting tools (including Excel) to do the data analysis.85. All transactions (# sales in period x, sales per author / title / etc) need to be available for reporting in such a way that the retailer or publisher can make every possible report from this data.86. DOLCI has real-time reporting on all transactions to Publishers and Outlets.87. Real-time reporting should include at least order information with product/proposition, quantities, order status and pricing.88. The retailer can sell his sales trends to a publisher. The publisher can use this to make its books more attractive. This is based on a contract between the retailer and the publisher.89. DOLCI can report in real-time / monthly / quarterly and yearly about all information that is needed to determine the financial position between publisher and outlet, publisher and DOLCI and DOLCI and outlet.90. DOLCI can report about marketing relevant statistical information on products/propositions (this concerns aggregated information, not consumer-specific information).3.6.1.2 Phase 2 and 3 requirementsThe reporting/KPI functionality must grow with the features added to the platform in phase 2 andphase 3.RFP e-bookplatform, version 1.0 August 2011 Page 21
  • 3.6.2 Financial clearance3.6.2.1 Phase 1 requirementsEnable the financial clearance between the retailer and the publisher (the financial transactionbetween customer and retailer is done on the site of the retailer)The financial clearance module counts the transactions of e-books (including streaming) betweenone retailer and one publisher. Based on the sold / temporary licensed e-books and the financialagreements a monthly invoice is created.Remark: The clearance between customer and retailer is handled on the retailer side. The platform must beable to interact with the retailer platform to send the link when the transaction on the retailer web shop isapproved91. DOLCI should act as a financial clearing-house in between the outlets and the publishers.92. DOLCI registers the financial agreements (contracts) between publisher and outlet. This can be done on a publisher/outlet level (defaults) but also at a product/proposition level (specific conditions).93. It must be possible to financially handle package deals from within the platform, combining electronic products and physical books. An example is “buy a physical book and get a 50% discount on the same e-book”. The clearance of the physical book is handled at the retailer. A solution to provide this can be discount coupons.3.6.2.2 Phase 2 and 3 requirementsThe financial clearance functionality must grow with the features added to the platform in phase 2and phase 3.3.7 Platform services94. Please specify the available reports and functions for platform management.RFP e-bookplatform, version 1.0 August 2011 Page 22
  • 3.8 Additional services for outletsThe optional modules are the connections in the platform for white label services that can beobtained by the retailer if necessary. <<This functionality is available from phase 2/3.>>3.8.1 Phase 1 requirements: white label webshop95. The platform has to support a white label webshop which can be used by smaller retailers to easily implement their webshop.3.8.2 Phase 2 requirements: Cloud readingRetailers want to be able to offer cloud-reading to their customers.96. The platform should be able to connect to cloud reading environment. Please specify how this can be done.97. The platform should be able to provide a cloud reading environment to be used by web shops. Please specify the available functionality of the cloud reading feature.3.8.3 Phase 3 requirements: User profiling services98. It should be possible to collect user data which can be used for up- and cross selling, targeted e-mail marketing, better search results, etc. The information is used to increase the relevance search results and to facilitate targeted marketing.3.8.4 Phase 3 requirements: Single sign on (Digi-D like)99. Single sign on from the retailer site to the platform should be supported to enable an easy integration of the secure environment of the retailer (used for buying books) to the books, bought via the platform.100. When the user logs in to the site of the retailer, there is direct access to the platform for looking at its shelf.3.8.5 Phase 3 requirements: Book shelf services101. It should be possible to easily implement a single retailer book shelf in the outlet’s web shop. On the Bookshelf, the customer can see all the books purchased from one retailer102. It should be possible to implement a multi retailer book shelf. The customer can see all the books purchased of all retailers that participate in the “multi retailer book shelf” service.RFP e-bookplatform, version 1.0 August 2011 Page 23
  • 103. Customers should always be able to access digital products, even when they lose their local copy or switch device.104. The conditions for re-delivery of a digital product can be configured by the publisher.105. Digital shelf is accessible on-line on all common browsers.106. An API is provided such that readers can integrate the DOLCI digital shelf in their reader software.3.8.6 Phase 3 requirements: Search and target107. A basic platform search on the catalogue should be supported within retailer assortment that can easily be integrated in the retailer’s website. This service facilitates the consumer to execute basic search queries. These queries will be input for the central platform search service. The results are presented to the consumer via the retailer website.3.8.7 Phase 3 requirements: Experiences108. A webshop can use this functionality to offer services to customer to find and view digital content (limited) to support the sales process. Please specify the features available for this purpose. For instance, read first chapter or table of contents or search book content.3.9 Additional services for publishers3.9.1 Phase 2 requirements: Conversion servicesSmaller publishers need support in converting their conventional products to electronic products.109. The platform should provide conversion services. Please specify the available conversion services (input format, output format, conversion quality).RFP e-bookplatform, version 1.0 August 2011 Page 24
  • 4 Technical design / non-functional requirements4.1 Architectural Goals and ConstraintsThe overall architecture goal of DOLCI is to provide a highly available and scalable online platformfor the “consumers” of the platform.A key Architectural goal is to leverage industry best practices for designing and developing ascalable, enterprise-wide application. To meet this goal, the design of DOLCI need to be based onproven design patterns as well as industry standard development guidelines.Standards and principles provide a starting point to describe the target architecture for theplatform. Some of the guiding principles that should be applied for DOLCI will be followed duringthe design and development are outlined below.4.2 PrinciplesBest practices and design principles need to be applied in different areas: 1. The diversity of applications and techniques must be limited a. to support a uniform integration between the (functional) domains b. to improve manageability and flexibility 2. Model Driven architecture is the preferred application development framework a. Applying abstract models with translations to more detailed models b. Where models are executed instead of code creation of code generationRFP e-bookplatform, version 1.0 August 2011 Page 25
  • 3. Business Rules (engine) should be applied within the application development framework a. Business rules will need to be separated from the presentation and database frameworks b. Server applications are based on event-based systems. c. Standard frameworks for encoding business rules and events will need to be used d. Adoption of a component based framework needs to be considered to promote reuse of information objects 4. Presentation Services to devices or desktops should be uncoupled: a. Presentation services are delivered to web browsers. Support for modern browsers and devices is required b. A common look and feel for DOLCI and the DOLCI user interface must be designed in such a way that common user interface functionality will be implemented in a similar manner across the platform.110. The platform services will comply with established industry standards. The standards- compliance will not only apply to application development but also to design, platform/infrastructure and other parts of the platform. Examples of standards include HTML, XML, J2EE, Database standards (modern, up-to-date, industry standardized DBMS) et cetera.4.3 UsabilityUser interfaces of the platform should be consistent, uniform and easy to use to facilitate aseamless operation of the platform.111. Attractiveness and user friendliness: for acceptance of the system by various groups of users, the systems front-end is attractive (for both ‘the eye’ and functionality) and easy to use.112. Usability: for the usability of the system by all kinds of end-users the front-end of the system is clear and understandable; all functionality is found and understood intuitively by the users; there are no long (or steep) learning curves for people using the system.113. Multilingual: the system must support multi languages both at the front-end of the system as well as for digital products themselves.4.4 Security & PrivacyDOLCI will be used by different target groups; authors, publishers, retailers et cetera. This requiresa proper security model that “Chinese walls” are present that ensure that users can never accessthe information from another user. Strict security and authorization roles need to be applied.Besides this requirement information that contains privacy information needs to be encrypted.114. Authorization: it is guaranteed that access to information is restricted to users and groups that are authorised to access this information.RFP e-bookplatform, version 1.0 August 2011 Page 26
  • 115. Authentication: each user needs to authorise him / herself to gain access to the services, unless specified otherwise. It should be possible to integrate the authentication system with that of Publishers and Outlets (Single Sign On).116. Security. DOLCI should be protected against unauthorised access to information including hackers and DOS attacks.117. Security. Publishers should not be able to access consumer-specific information.118. Security. DOLCI should be protected against unauthorised access to information including hackers and DOS attacks.4.5 Scalability and performanceScalability is the ability of the platform to scale both up and down to support varying numbers ofusers or transaction volumes without performance penalties. The application should be able toscale horizontally (by adding more servers) or vertically (by increasing hardware capacity orsoftware efficiency).119. Capacity and scalability: In the next few years to come the scale of implementation will grow from x products and y transactions to xx products and yy transactions. The scalability of the solution should be specified in terms of quantities and pricing.120. Performance: The solution has to meet the following performance requirements.  User interface functions directly response to the user. Maximum response time (user experience) is 2 seconds.  Order transactions have to be completed within a maximum response of 1 second.  Delivery of digital products to the customer has to be completed within <<x>> seconds.121. Performance: Users experience no degradation of service when publishers upload or modify their information and/or products.122. Performance: Users experience no degradation of service as long as the load is within the required limits. These limits need to be specified by the vendor.4.6 Sourcing & technical availabilityDOLCI will be outsourced to a professional data centre or service provider to ensure that the highavailability requirements can be met. The technical availability concerns the availability of thecomplete platform including hardware and connectivity. No Single Point of Failures should existthat could cause failures.DOLCI will contain different functions or modules that can require different performance orservice levels e.g. access to media, transactions and contract will require high availabilityguarantees while portal service to maintain master data could require normal availabilityguarantees. The platform should support that availability guarantees on individual modules,(Web)services or functions can be made and that this is reported on a monthly basis.RFP e-bookplatform, version 1.0 August 2011 Page 27
  • 123. Availability: Availability of the outlet-facing services should be 7x24 @ 99.95%. The publisher-facing services should also be available close to 7x24 @ 99.95%.124. Availability: The platform services should be accessible from any location world-wide (internet).125. Disaster recovery. In case of disaster the service should be recoverable within <<xx>> hours with a maximum data loss of <<yy>> hours.4.7 IntegrationDOLCI integrates with publishers, authors and retailers. Integration with consumers or publisherswill be applied using modern integration methods like web services, rest as well as traditionalmethods and transports like file-based and ftp. This level of flexibility to map documents todifferent formats and using different transports should be foreseen by applying an EnterpriseService Bus (ESB) and or Service Orient Architecture (SOA).The following characteristics are expected from the platform:  Reliability and flexibility in integration solutions  Support for Business Process Management and Business Activity Monitoring  Routing and mapping of messages or information across different applicationsAn important subject of the platform is to adopt, develop and implement Web ServicesDescription Language (WSDL) standards. The exact of operations or services will be based on theadopted market standards and processes that need to be supported.126. Interfaces of the platform should be based on SOA and ESB principles.127. Traditional file-based interfaces should be supported where relevant.128. Each interface of the platform should be defined in terms of protocol used, capacity, reliability, monitoring and reporting features.4.8 FlexibilityThe market and technology for digital products is changing rapidly putting new demands to DOLCIevery year.Flexibility is the ability of the application to adapt and evolve to accommodate new requirementswithout affecting the existing operations. This relies on a modular architecture, which isolates thecomplexity of integration, presentation, and business logic from each other in order to allow forthe easy integration of new technologies and processes within the application.RFP e-bookplatform, version 1.0 August 2011 Page 28
  • 129. Flexibility: the architecture and implementation should be setup in such a way that the platform can easily adopt new developments. These developments include but are not limited to: a. New types of digital products b. New forms of DRM c. New industry standards relevant to the Platform like ONIX d. New business models4.9 Data integrityDOLCI will handle a large amount of business transactions. These should be handled in a secureand reliable way. Integrity of the information should be guaranteed at any time.130. Reliability: The atomicity of transactions and integrity of data should be guaranteed, also in cases of failure.RFP e-bookplatform, version 1.0 August 2011 Page 29
  • 5. Appendix 1: Use casesUse Cases, GeneralFor the different use cases the following information is available / should be used: Publisher A with e-books 1 and 2 Publisher B with e-books 3 and 4 Outlet Y Outlet ZUse Case 1 Basic functionalityAs described in chapter 3 and 4 DOLCI must be able to support all known and future digital product formats(for e-books currently ePub and PDF) and types of DRM (currently Adobe, all sorts of social DRM, DRMfree). Furthermore DOLCI should support the BISG guidelines for the identification of propositions (ISBN /ISTC) and ONIX 3.0 for the definition of the commercial propositions.Web-based registration of publishers and outlets a. Demonstrate how publishers and outlets can be identified and registered b. Demonstrate how the different terms and conditions between publisher and outlet can be registered.Conversion to digital products c. The digital platform should be able to support the conversion of books to e-books. Demonstrate how this can be done.DRM d. Demonstrate how the different types of DRM can be registered to an e-book.Ordering, distribution and clearance e. Demonstrate how an order for an e-book is authorized by the digital platform (is this transaction by this outlet allowed?) and demonstrate how this order is registered. f. Only after authorization access is granted to an e-book / digital product. Demonstrate how this is registered. g. Demonstrate how the status of an order (ordered, authorized, delivered, …) is visible. h. Demonstrate how both the relevant logistic and financial data is registered in detail and made available as input for the clearance process (both order- and financial handling).RFP e-bookplatform, version 1.0 August 2011 Page 30
  • Use case 2 National title catalogueThe current title catalogue needs improvement in order to support the sales of digital products. The mainareas for improvement with the current catalogue are either a result of insufficient data maintenance andinsufficient tools and functionality to guarantee data consistency and integrity. 1. Inconsistent data field entry a. Title, author and other basic meta data is not consistent throughout the database b. Book covers are not uploaded or the resolution is too low c. Book descriptions are not uploaded, or not ready to use for webshop use d. In the current catalogue not all data fields contain the same content. 2. Lack of feedback when entering new data, e.g. your cover has the wrong dpi, or did you mean this author who is already in the database? 3. Lack of “superISBN” or works structure, where the title can be found in its different varieties by the consumer, such as hardcover, softcover, e-book, audiobook, English edition etc 4. The lack of useful NUR-codes a. In a lot of cases the NUR-code is semi-randomly entered, or manipulatively entered to let the book appear in a more popular category b. The NUR is still a level too high, sub NUR is wished for by booksellers, or a different solution (e.g. tagging) to achieve a finer category management 5. The search possibilities a. The current file is not designed to support extended searches b. Many consumer searches do not generate the right result or no results at all, which nega- tively influences sale and consumer experience c. No smart or semantic search possibilities, with suggestions….”did you mean…..”Search on author a. Demonstrate how all (available) books (physical and digital) of this author and other information (for example co-author, biography, movies from the book, etc.) can be found (despite the fact that the author name is not uniform)Search on work b. Demonstrate how all its expressions (hardcover, paperback, ebook, audiobook, English edition) and other information (for example co-author, biography, movies from the book, etc.) can be found.Search on publisher c. Demonstrate how all available books of this publisher, concerning this tag, (physical and digital) and other information (for example co-author, biography, movies from the book, etc.) can be foundHow would you import current book data and clean up all the data field and data entry errors?RFP e-bookplatform, version 1.0 August 2011 Page 31
  • Use Case 3 Maintenance and differentiated distribution of the catalog with digital productsThe goal is to create a national catalogue, ONIX 3.0 based, for all digital products and to start with e-books.For e-books a distinction is made between changing (or subjective) and non-changing (or objective)metadata. Typically the non-changing metadata originate at the publishers, and the changing metadataoriginate during the distribution and marketing & sales process. The aim is to organize the maintenance ofthe catalog as decentralized as possible whereas the control (consistency check) is centralized.Typical non-changing metadata for an e-book are (list is not limited): - Author - Title - ISBN - Publisher - Volume, issue, issue date - NUR codeTypical (potentially) changing metadata for an e-book are (list is not limited): - Table of content - Summary - Ratings and reviews - Author bibliography - DRM - PricingMaintenance of this catalog should be differentiated (different owners of the different metadata) as well asthe distribution of the metadata (not all outlets are granted access to all the metadata). a. Demonstrate how the different (enriched) catalog elements can be registered and how a distinction can be made between the different owners of this information. b. Demonstrate how outlet A gets all the available data elements in the catalog and outlet B only a designated subset of this information. c. Demonstrate how this information can be provided via ONIX and via a web interface and delivered via ONIX and a simple format (e.g. Excel). d. Demonstrate how the maintenance of this catalog can be as much automated and decentralized as possible, taking into account that a permanent (central) consistency check is a must.RFP e-bookplatform, version 1.0 August 2011 Page 32
  • Use case 4 Commercial propositionsThe guiding principle is that digital products must be combined as flexible as possible into commercialpropositions as regards to product, access / type of DRM as well as price. This means that the digitalplatform must support commercial propositions between 1 publishers and 1 outlet as well as between Npublishers and M outlets. a. Demonstrate how the commercial proposition between publisher 1 and outlet A is registered for e- books X, Y and Z with social DRM based on a fixed price of € 25,- b. Demonstrate how the commercial proposition between publisher 1 and outlet A is registered for e- books X, Y and Z with social DRM on a 3 for the price of 2 basis. c. Publisher 1 decides to add another e-book W to the proposition as mentioned under b. Demonstrated how this change is applied. d. October is thriller month: any 3 thrillers independent of the publisher sold by multiple outlets. Demonstrate how this commercial proposition is registered.Use case 5 Virtual bookshelfThe guiding principle is that publishers and outlets have to make sure that a customer at all times can use /have access to the digital products he bought. This means also when he has bought a new device, lost hisaccess code (to his original purchase) or wants to view his product on a different device. The goal is to havea virtual bookshelf per user independent of the outlet and / or publisher and / or reader and type of DRM. a. Demonstrate how this virtual bookshelf could work.RFP e-bookplatform, version 1.0 August 2011 Page 33