PUR1510/11

Request for Proposal

------------------------------------------------------------Provision of a User Experience Platform (UXP)

------------------------------------------------------------

PUR1510/11

1.0 INTRODUCTIONThe European Bank for Reconstruction and Development (the "EBRD") is an international financial institution. The EBRD was established by treaty in 1990 to foster the transition towards open market oriented economies and to promote private and entrepreneurial initiatives in Central and Eastern Europe, the Baltic States and the Commonwealth of Independent States that are committed to and applying the principles of multiparty democracy, pluralism and market economics. The EBRD has 63 members (61 countries, the European Community and the European Investment Bank). Further information about the EBRD's roles and activities can be found on the EBRD's website: www.ebrd.com.

1.1 Definitions:

The terms ‘EBRD’ and ‘The Bank’ shall mean the European Bank for Reconstruction and Development.

The term ‘RFP’ shall mean Request for Proposal. The term ‘Supplier(s)’ shall mean a party that submits a proposal in

accordance with this RFP. The term ‘Proposal’ shall mean a combination of the documents defined

in section 4.4 of this RFP. Specifically the Technical Proposal and the completed Quotation File.

Throughout this document, the terms “user interface component” or “UI component” are used to refer to the smallest element of UI deployment and re-use on a UXP. Within the marketplace, terms such as “gadget”, “portlet” and “widget” are commonly used in this way; but these may imply particular technologies or standards. Accordingly, we employ “UI component” as an inclusive term to cover all those categories; any page displayed by the UXP is simply an arrangement of (one or more) UI components, each of which could in principle be re-used in other contexts.

2.0 PROJECT BACKGROUND

2.1 ObjectiveThe objective is to procure and implement an appropriate User Experience Platform software tool to support the Bank’s strategic IT architecture. In outline, the selected Supplier will be required to:

supply User Experience Platform (UXP) software to the Bank; provide expertise to install and configure the UXP to the Bank’s requirements; provide training to Bank staff in the configuration and operation of the UXP; provide professional services to migrate certain existing application UI

Components onto the UXP; and provide on-going support for the UXP.

The definition of such software, the nature of the strategic architecture, and the scope of the migration, training and support requirements are explained in the following sections.

1

PUR1510/11

2.2 BackgroundThe Bank is engaged in transforming its IT landscape from an architecture in which functions are concentrated in traditional “vertical” applications, linked by point-to-point interfaces, towards a modern architecture characterised by the flexible partitioning and distribution of functions across heterogeneous components, and the integration of those components via re-usable standards-based User Interfaces, to provide:

a consistent, joined-up user experience; a manageable set of technologies and protocols; and efficient and responsive realisation of our business processes.

The Bank believes that a fundamental technology platform required for such an architecture is a UXP. The UXP aims to provide the following.

Deliver a package of:

o technology;o tools; ando patterns.

To enable Business Systems to deliver application functions to users:

o wherever the applications are (on- or off-premise);o wherever the users are (inside or outside the Bank, employee or

external parties); ando whatever device they are using (Bank owned desktop, mobile,

tablet and BYOD).

In a manner that is:

o coherent (across applications and devices);o efficient (allowing quick and easy navigation);o aesthetic (recognising that clarity and visual appeal contribute to

function); ando secure (in accordance with Bank policy).

Using resources that are:

o in-house;o independent (of Vendor PS practices); ando responsive (to user demand).

Working in a practice that iso highly decoupled from back-end concerns;o not constrained to the pace of the slowest; and

2

PUR1510/11

o observes continuous integration and testing principles.

The business case for implementing such a platform depends largely on the benefits of the architecture it supports, and its effectiveness in that support. Those benefits are:

improvement in the quality of the users’ experience interacting with Bank systems.

improvement in the accessibility of Bank systems, both in mode (internal, external, mobile) and in reach (donors, clients, other partners).

improvement in the agility of the Bank’s IT landscape – the ability to deliver new functions rapidly in a joined-up way, in response to changing user requirements.

3.0 EBRD CONTACT DETAILSYour sole contact for the purposes of the RFP is:

Tom Gale – Senior ManagerCorporate Procurement UnitEBRDOne Exchange SquareLondonEC2A 2JNTelephone: 020 7338 6255Email: galet@ebrd.com

3

PUR1510/11

4.0 DESCRIPTION OF THIS RFP

4.1 OverviewSuppliers wishing to participate in this process will be required to make the following submissions in accordance with the timetable outlined in section 4.2:

a technical proposal (the ‘Technical Proposal’); a completed quotation file (the ‘Quotation File’).

4.2 Timetable

03 November RFP published10th November 2015 Deadline for requests for clarification13th November 2015 EBRD response to requests for clarification20th  November 2015 Deadline to submit proposals26th -7th December Demonstration/Presentation of proposal at the EBRD15th December 2015 Proof of Concept (PoC) Contract Award

The EBRD reserves the right to amend or change these dates at any time.

4.3 ClarificationsThe process for reception and resolution of queries shall be as follows:

suppliers will send queries by e-mail to the following address: galet@ebrd.com; there will be one round of queries; the deadline for queries is shown in the timetable set out in section 4.2 of this

RFP; the EBRD will circulate the responses to all queries to all participating Suppliers

in accordance with the timetable set out in section 4.2 of this RFP; and the clarification document will make no reference to which Supplier made any

particular query.

4.4 Technical ProposalThe Technical Proposal shall be prepared with reference to Annex A - UXP Requirements and shall be comprised of the documents listed below.

4.4.1 Core RequirementsThe Supplier shall provide a completed copy of Annex B – Core Requirements.

4.4.2 Narrative ResponseThe Supplier shall provide a narrative response (the “Narrative Response”) as outlined in Annex C of this document.

4

PUR1510/11

4.4.3 Technical Proposal SubmissionResponses shall be submitted to the EBRD contact on a CD or a USB drive and in an original hard copy by courier in a sealed envelope clearly identified as “PUR1510/11 – User Experience Platform - Technical Proposal” in accordance with the timetable set out in section 4.2 of this RFP.

4.4.4 Demonstration/PresentationIn addition to a written response, Suppliers will be requested to receive a representation for the Bank for a presentation. The presentation should last no more than 120 minutes and will cover the topics below identified. The visit/presentation is scheduled for week commencing 12th October 2015.

i) Introduction to the proposed User Experience Platform

Introduction of the key features of the User Experience Platform Demonstration of how the Platform will provide the requirements we have de-

scribed our requirements Scenarios Key benefits of the product for EBRD. Key differentiators to other UXP frameworks applicable to the EBRD

ii) Overview of the Implementation process and Product Support

Outline and description of the Implementation process Detail the quality and experience to the consultants to be used for the implemen-

tation Detail how the product is supported

4.5 Quotation FileAll Suppliers are required to complete the quotation file (the ‘Quotation file’) attached as Annex E of this RFP. Prices are to be quoted in GBP net of VAT. All of the cells in the Excel spreadsheet shaded in yellow must be completed by Suppliers.

4.5.1 Quotation File SubmissionThe Excel file must be submitted on a CD or a USB drive and in an original hard copy by courier in a sealed envelope clearly identified as “PUR1510/11 – User Experience Platform - Quotation File” in accordance with the timetable set out in section 4.2 of this RFP.

4.5.2 Quotation File Validity Quotes submitted shall be valid for ninety (90) days following date of receipt.

5

PUR1510/11

4.6 Additional Information

4.6.1 Supplier Profile and DemographicsSuppliers shall provide a statement giving a brief history of their company, how it is organised, and how its available products and resources will be used to meet EBRD's requirements. The Supplier shall submit the following information.

The company's official name and address. The vendor shall also indicate what type of entity it is — for example, a corporation or a partnership.

The name, address and telephone number of the person to receive correspondence, and who is authorized to make decisions or represent the vendor. Please state his or her capacity within the company.

The total number of years the vendor has been in business and, if applicable, the number of years under the present business name.

The number of years that the vendor has been providing UXP suite technology, including the date that the specific UXP suite products cited in the response to this RFP first became generally available, and the product’s lineage. That is, what prior major versions of the products have been available and what previous product generations or acquisitions contributed to the current flagship product’s capabilities.

How many customers are using the specific UXP suite cited in the response in terms of: 1) number of licenses sold; and 2) number of unique companies using the suite in production.

4.6.2 Financial InformationThe vendor shall provide a complete set of audited financial statements for the past three years. All financial statements should be prepared to generally accepted accounting principles.

4.6.3 ReferencesThe Supplier shall provide details of three customers for reference, preferably in the same sector (financial services) and country (UK). References should be for customers with requirements similar to those of EBRD. References should include information about the contract (specific products in use, date of contract execution, "go live" date and any services provided), as well as contact information for the client's project manager or other senior staff members familiar with the project.

4.6.4 Submission of Additional Information All of the required additional information should be supplied on the USB or CD containing the Supplier’s Technical Proposal.

6

PUR1510/11

5.0 EVALUATION METHODOLOGY

Element of the EvaluationMaximum

Score available

Minimum qualifying mark

A. Technical EvaluationCore requirements 140 90Planned-use cases 175 N/APresentation/Demonstration 175 N/AImplementation 105 N/AProduct Support 105 N/ATotals 700 525B. Financial EvaluationMaximum Financial Score 300 N/AOVERALL MAXIMUM SCORE 1000

5.1 Technical Evaluation Suppliers’ Technical Proposals will be evaluated and scored by a nominated Tender Evaluation Panel (TEP) of Bank staff selected from operational departments who are directly involved with the services to be provided.

A minimum technical threshold applies to this procurement process. A Supplier will be deemed to have passed this threshold on meeting all of the following three conditions:

a majority of the TEP allocate it 75% (525 points) or higher of the maximum points available for the technical evaluation;

the mean of the combined TEP scores is 75% (525 points) or higher of the maximum points available for the technical evaluation; and

a majority of the TEP allocate the Supplier the minimum qualifying mark for the “core requirements” element of the evaluation where one is specified in Table 1 above.

Only those Suppliers who’s Technical Proposals pass the technical threshold will have their Financial Proposals opened and evaluated.

5.2 Financial Evaluation Following the review of the Technical Proposals, the Quotation Files of those Suppliers who have passed the technical qualification threshold will be opened. The Bank will calculate a total bid price for each Supplier based on the costing provided. The Supplier proposing the lowest total bid price will be given the maximum financial score available (300). Other Suppliers’ (higher) prices will be divided into the lowest price and the result multiplied by the maximum score given.

FSa = LP EPa x Maximum Financial Score

FSa = financial score for proposal aLP = the lowest evaluated financial proposalEPa = the financial proposal of a.

5.3 Financial Errors

7

PUR1510/11

Mathematical errors detected by the Bank in the submitted Quotation Files will be corrected in the following manner:

if there are errors in the mathematical extension of unit price items, the unit prices prevail and the mathematical extension is adjusted accordingly; and

if there are errors in the additional of lump sum prices or unit price extensions, the bid is not rejected but the total is corrected and the correct amount reflected in the total bid price.

5.4 Preferred SupplierThe Supplier achieving the highest combined score following the technical and financial evaluations shall be nominated as the preferred Supplier (the ‘Preferred Supplier’).

5.5 Checking of ReferencesThe Bank may contact the three references provided by the Preferred Supplier. The Bank reserves the right to speak to any company which has dealt with the Preferred Supplier, whether provided as a reference or not, without prior notification to the Supplier.

In the event that the Preferred Supplier’s references prove unsatisfactory, the Bank will consider the next highest scoring Supplier to be the Preferred Supplier and will repeat the procedure described above.

5.6 NegotiationsUpon satisfactory conclusion of the reference checking, the Bank will move to negotiate a contract with the Preferred Supplier. In the event that a satisfactory conclusion to the contract negotiations cannot be agreed the Bank may consider the next highest scoring Supplier to be the Preferred Supplier and will commence the procedure described above.

6.0 CONTRACT

6.1 Status of the EBRDThe EBRD is an international organisation established by international treaty. As such, the EBRD possesses a special status under public international law which has been confirmed under English law through statute (Statutory Instrument 1991, No. 757, The European Bank for Reconstruction and Development (Immunities and Privileges) Order 1991), available at:

http://www.legislation.gov.uk/uksi/1991/757/contents/made.

Please also refer to the aforementioned establishment treaty of the Bank ("articles of incorporation") which lays out the immunities as found in Chapter VIII. These can be found at:

http://www.ebrd.com/pages/research/publications/institutional/basicdocs.shtml

The special status of the EBRD requires it to seek specific provisions relating to such status in all contracts with external suppliers and service providers. EBRD is unable to

8

PUR1510/11

agree to terms that expressly contradict its special status and internal policies as an international organisation.

6.2 Contract NegotiationSubject to the Bank’s status, see section 6.1, the Preferred Supplier’s standard terms for delivery of these services shall form the basis of any contract that may ensue. EBRD reserves the right to subject each proposal to final negotiations.

6.3 Proof of Concept (PoC)Prior to final purchase of the UXP the Bank will undertake a four week PoC exercise the parameters of which are provided as Annex D of this RFP. It is a minimum requirement for participation in this tender that the Preferred Supplier grant the Bank a trial version of all relevant software at no cost for the duration of the PoC. It is understood that Suppliers may require remuneration for any professional services rendered in the execution of the PoC. These costs should be reflected in the Supplier’s Quotation File.

In the event that the PoC is not successful, the Bank reserves the right to consider the next highest scoring Supplier to be the Preferred Supplier and may commence the procedure described above.

7.0 GENERAL TERMS AND CONDITIONS OF THIS RFP

7.1 AmendmentEBRD reserves the right to negotiate any or all terms and conditions, and to cancel, amend or resubmit this RFP in part or entirely at any time. None of the terms and conditions of this RFP can be revoked or amended in any way by Suppliers without the prior written agreement of EBRD.

7.2 Supplier CostsEBRD is not responsible for any Supplier costs associated with this RFP, Supplier responses or any contract discussions or negotiations. Nor is EBRD responsible for any indirectly related costs. No statement by EBRD should be viewed as a request by EBRD or justification for Suppliers to increase or change inventory, staff, facilities, business relationships with its suppliers, or internal business processes. All actions by Suppliers in response to this RFP or subsequent discussions or negotiations should be taken with the clear understanding that neither this RFP nor subsequent actions or omissions by EBRD obligate or commit EBRD to pay or reimburse Suppliers for any costs or expenses they incur. This RFP is not an offer to enter into a contract.

7.3 Professional CompetenceSuppliers shall absolutely rely on their own professional competence in evaluating and verifying the information contained in this RFP. Suppliers must take every opportunity to inspect and verify the information contained or referred to in this document or subsequent to it, subject to the confidentiality restrictions as detailed in section 7.6 of this RFP.

9

PUR1510/11

7.4 Intellectual Property The information contained in this RFP will remain EBRD’s intellectual property. Suppliers are granted a limited, revocable license to use the same for the purpose of responding to the RFP. By submitting a response to the RFP Suppliers grant EBRD a royalty free, irrevocable license to use the intellectual property in the proposal for its internal business purposes in relation to the procurement of the services required.

7.5 Sole ResponseSubmission of a response as part of this process shall be deemed to be the Suppliers’ only offer(s).

7.6 ConfidentialitySuppliers shall treat the RFP and EBRD's process of evaluating Suppliers as strictly private and confidential. The contents of this RFP, including specification, designs, drawings or other related documents shall be considered confidential and shall not be disclosed by the Supplier, the Supplier’s servants or agents to any persons, firm or corporation without the prior written consent of EBRD. Any such specifications, designs, drawings or other documents shall remain the property of EBRD and shall be returnable to EBRD within five (5) days of the Supplier receiving either, notification that it has been unsuccessful, or on written request from EBRD.

7.7 EBRD Logo ProtectionPlease be advised that EBRD logo is a registered service mark and as such should not be reproduced without the express written permission of the Bank.

7.8 GeneralIncomplete or inadequate responses, lack of response to an item or items, or misrepresentation in responding to this documentation may result in rejection of a Supplier’s Proposal.

After receipt of the RFP and until the award of any contract, neither information relating to the examination, clarification, evaluation and comparison of the submissions nor recommendations concerning the award of a contract shall be disclosed to the Supplier, or to any other outside parties, until the RFP process has been concluded and a contract awarded.

Any effort by a Supplier to influence EBRD in the process of examination, evaluation and comparison of the RFP, or in decisions regarding the award of a contract, shall result in the rejection of the Supplier’s Proposal.

Ownership of documentation or other information submitted in the RFP will become the property of EBRD unless otherwise requested at the time of submission. Any materials submitted in response to the RFP, which are considered to be confidential, should be clearly marked as such by the Supplier.

The Bank reserves the right to accept or reject any RFP response, or part thereof, and to annul the RFP process and reject all RFP responses at any time prior to award of contract without incurring any liability to the affected parties.

10

Annex A- UXP Requirements

1.0 EXISTING INFRASTRUCTURE

1.1 Primary Applications Involved in UI Projects

Data Source/Application Name and Version

Description

SAP ECC 6 EnPack 6 (SAP NetWeaver v7.3)

SAP ECC (previously R/3) part of the SAP Enterprise Central Component platform. Used for financial and accounting purposes including GL, integrated financial cost accounting, purchasing, travel and expenses accounting also used for HR purposes including payroll and staff records management. (Interfaces: direct SQL interfaces to underlying Oracle database but BAPI/RFC (ABAP) interface and also files (iDOC).)

Oracle WebCenter Sites 11gR1 WCMS

OpenText Content Server v10.x

Document Management system which currently has integration to our Business server bridge and uses an application API to consume document metadata from the BSB

Java applications (JBOSS) v5.1.0 GA

Java J2EE Application Server based bespoke applications with underlying Oracle databases

Cognos v10.1.1 Business Intelligence platform

Tibco BusinessWorks v6.2.1 ESB/EMS

SAP SuccessFactors SaaS

Cisco Jabber v10.6.2 IM and presence

1.2 Supported platforms and preferred versions

Type Vendor Name Preferred VersionUXP Application Container

ApacheRedhat

TomcatJBoss AS

7+7+

Operating Systems RedhatMicrosoft

Redhat Linux (64bit)Windows Server

6.5+2012 R2

Database platforms OracleMicrosoft

Enterprise DatabaseSQL server

12.12012

Virtual Environment Vmware Vsphere 5.1 (5.5)

11

2.0 HIGH-LEVEL REQUIREMENTSThe essential features required of an UXP to support the Bank’s strategic IT architecture can be grouped under the following five headings.

Core Requirements:

Requirement UXP role1. Lean UXP Modern, Web-oriented architecture (WOA) and client side-

based container model (browser)Standards based: Pages/UI Components are built using web-open standards HTML5, CSS3 and JavaScript 5+

2. Flexible deployment (App server) Must be deployable on Apache Tomcat and JBOSS JEE AS3. OOTB AJAX Proxy To avoid Cross-Origin Resource Sharing (CORS)

complexities4. Multi-device UI framework

across tablet, mobile, desktopMust support responsive design at both page and UI Component level, with multiple layout templates to organise pages depending on device type and/or orientation, and UI components able to render themselves based on screen space allowed

5. UI framework support for custom themes, page templates

Must provide a framework to design, create and deploy custom Themes AND Page templates

6. UI consistency in appearance, navigation and accessibility

UXP must provide support for a strong separation between styling and UI Component functionally at a UI Component level

7. UI Components Catalogue (App Store)

Allows users to search for (based on entitlements/roles), select and place pre-built UI Components on a page

8. UI Component re-use UI component re-use must be supported. UI component structure within UXP allows literal reuse of UI components within a single deployment framework supporting event-based cross-component integration

9. Inter-UI Component communication

UI component event-based cross-component integration (i.e. inter-UI Components communication) must be supported

10. Authentication/RBAC/SSO Must support authentication and Role-Based-Access-Control (page and UI Component level) via MS Active Directory (internal users) and LDAP or SaaS IdP (external users), and facilitate Single-Sign On (supporting Kerberos, SAML2, OAuth)

11. Auditing and accounting Must provide auditing of security related activity, such authentication, authorisation and administrative access that is compatible with leading SIEM solutions.

12. UI framework support for alerts and notifications

Must be able to channel “push” messaging

13. Multiple logical portals Must have a support for distinct logical portals with their own distinct address, authentication and access control model – (i.e. to allow internal/partner portals to be segregated)

14. Integration/Authentication with the back-end systems

UXP must support integration with back-end systems via RESTful Web Services with appropriate authentication mechanism for external and internal users

Development, Testing and Deployment. The provision of an integrated development environment, including graphical and code-based design tools, testing and debugging facilities, and tools to manage deployment of developments between environments.

12

Management and Monitoring. The ability to monitor and analyse run-time performance and manage the platform to identify problems and exceptions and take remedial actions.

Security. Capability supporting common authentication, encryption and signing standards, combined with a platform authorisation and access model. Includes support for secure network access across DMZs using proxies. Must not introduce vulnerabilities into EBRD networks; software components should be designed in accordance with industry security best practices, to be validated by independent security assessment.

Non-functional characteristics. Usability and productivity, especially of the design and deployment tools; supportability (in terms of mix of technologies and skills); cohesion (overall simplicity of the product architecture); orthogonality (cross-applicability of independent features); scalability, configuration for availability, etc.

Specific questions about the proposed UXP platform are set out under these headings in Annex B – Core Requirements.

13

3.0 SCOPE OF PLANNED USE-CASES AND NON-FUNCTIONAL SCENARIOSResponses to the questions in the following section should be submitted as part of the Supplier’s Narrative Response a template for which is provided as Annex C of the RFP.

3.1 Intranet

Target state: We want the intranet homepage to become a collaborative hub for EBRD staff, along the following lines:

Target layout mock-up

The home page divides into three logical zones: a Bank zone, managed by Communications; a Department zone, managed by individual departments; and a Personal zone, managed by each user for themselves. A similar model would be used by departments and teams to create their own home pages. Potential features include:

Standard navigation header and footer, with EBRD styling. An enterprise search function, allowing rapid federated search of enterprise

resources (static pages, OpenText Livelink, ebrd.com, other documents and indexed application content) in one place. This would include staff directories (“Who’s who”).

An EBRD news area, similar to the current intranet homepage’s news section. This could also include alerts and notices when necessary.

A departmental news area, with content relevant to and managed by the user’s department.

A team links area for links to common resources relevant to the department. A universal task list, showing workflow tasks for the user drawn from a range

of back-end systems (SAP, Appian…); see section 3.2 below. A universal calendar, showing events and task deadlines drawn from a variety

of systems which are relevant to the user.

14

A personalised apps area containing links to the user’s commonly used applications

A personal feed area showing latest updates from discussions and other collaborative fora to which the user has subscribed.

Embedded presence indicator linked to the Bank’s unified communications platform.

Customisation – the ability for users to rearrange the layout of their homepage, prioritising or hiding content in their personal zone as they see fit.

Additional application content – if a business application is particularly important to a team or department, it may be possible to integrate core content (beyond tasks and events) from that application into a ‘widget’ to be included in hub pages for those users.

Responsive design should be used to make the homepage easy to access on handheld devices:

All content will be delivered as UI Components that can be placed in a particular zone within a page template. Page templates will respond (change layout) based on the available space; UI Components may also respond to the size of the zone they are located in. For example, the My tasks widget above may show more detail when displayed across the full width of a desktop browser, but a more summarised view when in a more constrained space.

To achieve the target state described would require a range of technical capabilities: Web content management (Oracle WebCenter Sites) – will be needed to create

and manage the static content which will remain at the heart of the intranet. Collaboration tools (SAP Jam) – to support collaborative content and

messaging. Identity Management (TBC) – to support and manage personalised

presentation of content by users’ team and role. Enterprise search (TBC) – to support the federation of search queries across

multiple repositories, and aggregation of results into a common format. Unified communications (Cisco Jabber) – to support instant messaging,

presence and other personal communications.

15

Integration services (via RESTful Web Services) – to bring together content from a wide range of source systems for the task list, calendar, feed etc.

Describe how your product can support this use case, interoperating with the other software capabilities just described.

3.2 Universal Task List Description: As an end-user, I want to be able to view tasks summary/details/linked documents and manage

1. My employees’ Leave Requests (ECC MSS)2. My employees’ Service Request approvals (ServiceNow)3. My Tasks triggered by other Business Applications (i.e. Appian BPM, bespoke

systems)from my mobile device (via Blackberry, iOS and Android browser) and PC (via desktop browser).

3.3 Universal Calendar Description: As an end-user, I want to be able to view summary/details of events/meetings

1. Bank-wide2. Department-wide3. Team-wide4. Triggered by other Business Applications (i.e. bespoke systems)5. Personal

and configure the appearance of calendar by day/week/month/year and set calendars’ sources. Assume that the ESB provides publish-subscribe services to share all relevant events, filterable by User ID.

3.4 Who’s Who (Employee Directory)Description: As an end-user (Employee), I want to be able to (on any type of device):

1. Search the EBRD employee directory (typeahead search) 2. View Employee details (including pictures)3. View organisation chart 4. View employee’s online presence status (Cisco Jabber)5. Initiate a chat session, share a screen or place a call (via Cisco Jabber client)6. View employee’s activity stream (via SAP Jam: blog posts, published wiki

pages, documents, videos, comments, etc.) ESB-published web services support querying of employee data from the HR system. Pictures are held in MS AD.

3.5 ExtranetDescription: As a client/partner (Non-Employee), I want to be able to

Upload documents. Make disbursement applications online. Receive statements and notifications. An alert system notifies interested parties

whenever new items are added or changed. View reports and simple content derived from back-end systems. Initiate requests (for disbursements, waivers, prepayments, etc.) which trigger

workflow items to the relevant internal teams to respond via their Universal Task List.

16

3.6 Single-Page Application (SPA)Description: As a UXP Administrator/Developer, I want to be able to

Incorporate a standalone SPAs built with well-known JavaScript frameworks (i.e. AngularJS, Ember, React, Polymer) as widgets on UXP pages.

Non-functional scenarios:

3.7 Identity PropagationWe have a set of workflows processes, based on a BPM platform, which would be shown as a Universal Task List UI Component on UXP page and need to carry out fetch and update operations against our project management system (based on SAP ECC). The typical sequence would be an approval of a project element: fetch of project details, followed by update of project status to “approved” or “on hold”. SAP ECC exposes SOAP web-services to the ESB to support these fetch and update operations, which are in turn exposed as SOAP services to the BPM platform. For audit and authorisation purposes, it is important to us that all operations are carried out in the SAP ECC system under the user ID of the person who executed the relevant process step on the BPM platform. The BPM platform supports Kerberos SSO for user sign-on, and supports SAML subject confirmation via SOAP using the “sender vouches” profile to assert the identity of its users to the UXP when consuming RESTful web services. How can your UXP propagate user identities between UXP and BPM, and ECC back-ends?

3.8 Co-ordinated DeploymentThe Bank uses Apache Subversion for source management and version control. A typical scenario would involve the simultaneous deployment to a test or production environment, of changes to UI components together with changes to integration features which serve those components. Describe how your UXP can integrate with Subversion or use other techniques to facilitate orchestrated deployments of related UI and integration changes. If a major failure of one change package requires reversion of the whole deployment, describe how your UXP could support this roll-back.

3.9 Retracing our stepsA sequence of hard-to-diagnose intermittent errors occurs in background integration activities involving several systems which serve the UXP. In order to understand the cause, we need to start detailed logging and tracing of integration operations, targeted at those systems and certain specific UXP operations we believe are involved. Describe how we can configure your product to provide such detailed and targeted message logs and activity traces, security logging and integration with SIEM; and the tools to analyse such logs and traces after the fact in order to support diagnostic work.

3.10 Business ContinuityThe Bank has business continuity provision involving replication of key systems in near real-time at a remote “disaster recovery” site. The UXP would be part of our critical infrastructure and would be included in this provision. Please describe how your UXP failover architecture could provide a scalable, fault-tolerant business continuity solution during a disaster event.

17

3.11 Scalability for Throughput and LatencyPerformance of the User Experience Platform will be a critical factor in the overall performance of applications using services. Please describe the ability to scale the components to manage the throughput performance of your UXP.

3.12 High Availability As a critical infrastructure component, we will need to configure our UXP to be highly available with redundancy and seamless failover provision. Please describe the configuration options for your UXP to ensure availability.

Variant: how can we exploit these same options to provide combined throughput AND availability benefits without excessive redundant provision?

Variant: How can these options support the business continuity requirement described above.

3.13 Provision of Test Systems We will need to incorporate an UXP instance in our regression and other test landscapes. Accordingly, ease of creation and reconfiguration of copies of our production UXP for use in testing is an important requirement. Please describe the steps by which you would recommend we create such test instances, paying particular attention to the range of components that need to be created or copied, and the configuration steps needed to connect them both to each other and to corresponding test instances of the other systems in the test environment.

18

Annex B – Core Requirements

With reference to the Bank’s requirements as described in Annex A, Suppliers are required to score themselves for each of the questions in the attached document using the following scale.

0 Product does not meet the Bank’s requirements.1 Product partially meets the Bank’s requirements/requires customisation or

integration with a third party product to meet the Bank’s requirements.2 Product fully meets the Bank’s requirements with out of the box functionality

(subject to standard configuration).3 Product exceeds the Bank’s requirements and offers a degree of innovation that

differentiates it from other available products.

Suppliers are required to provide a description and justification for each of their responses.

Please note that the TEP will be scoring the Supplier’s response based on this information.

Should the TEP be satisfied with the justification, suppliers may not be penalised for meeting a requirement through the use of third party products or by customisation of their base product. However, any related costs (additional licensing, professional services etc.) must be clearly indicated in the Suppliers’ Financial Proposal.

19

Annex C – Narrative Response

1.0 PLANNED USE-CASES AND NON-FUNCTIONAL SCENARIOS This template is to be used for Vendor responses to the narrative questions set out in section 3.0 of Annex A – UXP Requirements of the RFP document.

Suppliers shall enter their response in the response section under each question title. Refer to the RFP document for the full question text.

Suppliers should focus on how their products can support the scenarios the Bank have described, emphasising the most appropriate features of both the design and run-time environments for the purpose. If there are several viable approaches, please do include them.

The suggested length of responses is up to one page per question, extending to two pages for the most complex questions. Diagrams may be used. Note that concision and relevance of the response to the specifics of the question are important evaluation factors; the inclusion of generic support or marketing material is discouraged. Suppliers should not repeat material between questions; a reference to the previous instance will suffice.

For status of components used, please list the product components alluded to in your response, and for each one, detail (a) if it is your own, or a third-party product; and (b) if custom development beyond the standard configuration options offered by the product is required to support any aspects of the scenario covered.

Title 1. IntranetResponseStatus of components used

Title 2. Universal Task ListResponseStatus of components used

Title 3. Universal CalendarResponseStatus of components used

Title 4. Who’s Who (Employee Directory)ResponseStatus of components used

20

Title 5. Single-Page Application (SPA)ResponseStatus of components used

Title 6. ExtranetResponseStatus of components used

Title 7. Identity PropagationResponseStatus of components used

Title 8. Co-ordinated DeploymentResponseStatus of components used

Title 9. Retracing our stepsResponseStatus of components used

Title 10. Business ContinuityResponseStatus of components used

Title 11. Scalability for ThroughputResponseStatus of components used

Title 12. High AvailabilityResponseStatus of components used

Title 13. Provision of Test SystemsResponseStatus of

21

components used

22

2.0 IMPLEMENTATION2.1 Project Implementation Timeline

Phase 1 – Design / PreparationPhase 2 – Commissioning of the trial UXP software in to the EBRD environmentPhase 3 – PoCPhase 4 - Adoption of the UXPPhase 5 – Further strategic development of the UI layer utilising the UXP (as described in the potential use-cases)

2.2 Implementation ServicesThe Bank requires that Suppliers provide professional services to implement phases 1-3 of the above timeline. The Suppliers Narrative Response will include the following:

Proposed approach, methodology and project governance. CVs of the Project Team which the Supplier is proposing to deliver the

implementation, identifying their experience of implementation of (e.g. a “lead” consultant), their contract status (permanent or subcontracted staff), and their length of time with the company.

Work Plan and Team Assignment, detailing key milestones. Include any training necessary for Bank staff to administer, configure and

operate the software. This may include shadowing the implementation consultants and/or some formal training

Describe any commitments that would be made to address a situation where a key member of the Implementation team (that your firm supplied) unexpectedly became unavailable.

Outline of the capacity to draw on resources when necessary from other areas of the Supplier’s organisation.

The cost of this implementation should be included in the quotation file

3.0 Architecture and Product SupportThe Bank requires that Suppliers provide the following information as part of their Narrative Response.

The Supplier must identify the technical skills/training required to maintain and manage the solution.

The Supplier must provide details of its upgrade/patching release policy and approach to product upgrades.

The Supplier must provide an overview of the proposed development roadmap for the products under their control which are used in the solution.

The Supplier must show a clear development path for the solution, demonstrating commitment to support the latest and future versions of MS Windows and MS Office.

The Bank requires full technical support during UK office hours (09:00-17:00, Mon-Fri). The Supplier must provide the details of its support offering which most closely matches this requirement.

23

The Supplier must identify whether any support will be provided by a third party and if so how this will be delivered in accordance with the Bank’s requirements.

Describe at an overview level the complete lifecycle of a support call – from the point the Bank initiates the call to its resolution, specifically indicating:

o The method of call logging

o Standard SLAs

o Integration of SLAs into the call logging system.

o Internal escalation procedures

o External escalation procedures

o Remote support capability

o Capability to provide on-site resources as requested

o Describe any methodology, quality control system and/or “good” practice” initiatives that you would employ to facilitate the delivery of high quality support.

Specify any technical infrastructure that will be required at the Bank to facilitate support. Any additional costs that will be incurred by the Bank i.e. telecoms costs, licensing must be reflected in Annex D – Quotation File.

Describe the process for providing professional services to the Bank. Professional services.

Describe the level of flexibility in dealing with issues that may require consultants on-site and when responding to ad-hoc requests.

24

Annex D – Scope of Proof of Concept

25

Annex E – Quotation File

26