ANNEX A – MINIMUM REQUIREMENTS CHECKLIST

|
ANNEX A – MINIMUM REQUIREMENTS CHECKLIST
|
bet | 2/6 | Sana | 31.12.2019 | Hajmi | 0,69 Mb. | | #6778 | Turi | Request |
Please note only Suppliers who can answer “yes” to all of the following questions are eligible to participate in this tender,
Service Minimum Requirements
|
Yes/ No
|
The Supplier has a minimum of five years of experience of WebCenter sites.
|
Yes/No
|
The Supplier is a registered Oracle partner at Silver level or above.
|
Yes/No
|
The Supplier has implemented three WebCenter sites in last three years including at least 1 at 11g.
|
Yes/No
|
The Supplier has experience of legacy content management system migration.
|
Yes/No
|
The Supplier has experience of an implementation of at least 2000 users and at least 5000 pages
|
Yes/No
|
Minimum Contractual Terms
|
Yes/ No
|
The special status of EBRD requires it to seek specific provisions relating to such status in all contracts with external suppliers and service providers. EBRD is unable to agree to terms that expressly contradict its special status and internal policies as an international organisation. Suppliers are required to confirm that they understand and accept this.
|
Yes/No
|
The Supplier agrees that the basis of any contract will be the template attached to this RFP as Annex D.
|
Yes/No
|
ANNEX B – SCOPE OF SERVICES
BACKGROUND
The European Bank for Reconstruction and Development (the “EBRD” or the “Bank”) currently has a mature intranet website built using EMC Documentum as the Web Content Management System (WCMS) platform. Both the content and the CMS platform have been in place for some years now and are in need of a refresh. The Bank has consequently initiated a project (the “Project”) to upgrade the intranet site.
The Bank implemented a move for external facing content (ebrd.com) from the Documentum WCMS to Oracle Web Center Sites (WCS) in 2013/14 and the purpose of this engagement is to provide implementation assistance to the Project to upgrade the Bank’s intranet to the existing Oracle WCS platform.
The Intranet content is largely static, and consists of a number of departmental and function based sections in addition to some microsites, departmental news and bulletin feeds and general internal communication areas, including areas for HR, Communications, Admin and IT. There is a desire to renew the content during the refresh, rather than just migrate, in addition to creating more dynamic pages which are potentially personalised to individuals or at least functional or departmental personas.
The Bank also makes use of the Enterprise Document and Records Management (EDRMS) system Opentext Content Server CS10.5 (formerly LiveLink) from Open Text as a document repository for the Bank’s official archives and there is a desire to more closely integrate the rich management capabilities of this repository with the web content management system.
Additional information and metrics on the current Intranet landscape has been attached to this Scope of Services as Appendix 1.
OBJECTIVES
The scope of the assignment (the “Assignment”) is to provide technical design and development implementation services rather than a full end-to-end web product delivery.
This technical design and build will include the following aspects:
templates;
search engine configuration;
integration with the Bank’s EDRMS, Opentext CS10.5;
customisations and other code;
development of interactive, per user, features;
authoring workflows;
portal integration (optional);
system upgrade to WCS 12c (optional); and
content migration assistance (optional).
Note this will not include non-technical UI, design and offline scoping work. The Bank’s discovery phase has been ongoing for over a year and core requirements will be well established by the time the contractor (the “Contractor”) starts work.
The Bank requires a system which is compliant to latest Firefox version, and current IE build used by the Bank (Currently IE11).
The successful supplier will have a proven and demonstrable track record of extending and customising Oracle WebCenter Sites to integrate with data from alternative sources via attribute editors, filters and proxy assets as well as search configuration and general customisations.
ENGAGEMENT APPROACH
Although as stated, requirements analysis and discovery have been carried out over a period of time, there is an expectation that there will be a short discovery phase to review and firm up aspects of the technical design (detailed below) prior to commencement of implementation. Where indicated report(s) will be required detailing the discussions held, the conclusions of those discussions and final agreed decisions. While good project practice, this will also be required to provide traceability for project scope governance, and should be framed in this context.
In general then, the schedule will require the following: -
Discovery – Analysis of existing requirements, discussion with internal subject matter experts SMEs and stakeholders.
Reporting – Presentation of conclusions of discovery phase discussions of outstanding items for decision and options. Deliverables from this phase should include:
template book – list of agreed templates for development;
search – approach for optimised search;
EDRMS integration – recommended strategy;
personalisation – recommendation for the best long-term approach, including possible social features (i.e. comments, ratings, walls, etc) particularly in the context of enterprise portal integration.
authoring workflow – detailed process flows.
system upgrade – Potential upgrade option conclusions.
Governance - Review milestone and approval stage.
Implementation – ‘Agile’ sprint delivery of functionality.
Acceptance – Support during the testing and acceptance phase.
Assumptions
The project team based at the EBRD HQ
Testing done by the EBRD Testing team
Out-of-Scope
SCOPE OF SERVICES
4.1 Templates
The final template types shall be defined as part of the detailed design stage which is running in parallel with this procurement, however, it is envisaged that the templates would entail at least the following:
homepage;
general content page (with configurable components within it);
event page;
event calendar aggregating all events with filter controls;
image gallery;
video page or video asset that is dropped into a generic page;
sub-landing page (e.g. departmental homepages, in effect);
listing page (perhaps configurable through the general content page);
a reusable component to provide basic search, filtering and sorting, perhaps using a third party component such as this http://isotope.metafizzy.co/; and
news landing page.
4.2 Front end code implementation
The Bank is seeking a system which is compliant to the latest Firefox version, and current IE build used by the Bank (currently IE11). The front end code shall adhere to the HTML5 standard and assumes usage of the JavaScript. The final solution should be of a responsive design, so that the layout adapts when the browser is narrowed or the intranet is viewed on mobile devices. The Bank is assuming likely usage of the Bootstrap responsive framework.
4.3 WCS templates coding
All the templates shall be coded in such a way that would make it possible for the content authors to create/edit content through either form or the web view. The CKEditor shall be configured to include styles from site’s stylesheets in the menus and formatting within the editor shall, as far as possible, resemble finished web pages.
|
| |