Request for Proposals pur1608/15

2.1 Background and Objectives

Your sole contact for the purposes of the RFP is:

EBRD

London

Telephone: 020 7338 7661

Email: hays@ebrd.com

4.0 DESCRIPTION OF THIS RFP
4.1 Overview

Suppliers wishing to participate in this Tender will be required to make a submission (the ‘Submission’) comprising of the following documents in accordance with the timetable outlined in section 4.2:

• 
  a completed minimum requirements checklist (the “Checklist”) as defined in section 4.4;
  
• 
  a technical proposal (the ‘Technical Proposal’) as defined in section 4.4; and
  
• 
  a completed quotation file (the ‘Quotation File’) as defined in section 4.5.
  

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

The process for receipt and resolution of queries shall be as follows:

• 
  Suppliers will send queries by e-mail to the following address: hays@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.
  

The Technical Proposal shall consist of: a completed version of the Checklist attached to this RFP as Annex A – Minimum Requirements Checklist and a narrative response prepared with reference to Annex B – Scope of Services which at a minimum should provide the following:

1. 
   An implementation plan showing high level tasks, milestones and resources used across implementation and optional items. Please address
   

• 
  the resource expectations from the EBRD team indicating the type of resource (technical or business);
  
• 
  any assumptions that have been made during creating the proposal; and
  
• 
  any specific facilities or environmental requirements given that the assignment will take place at the Bank’s headquarters in London.
  London, Katta London - Buyuk Britaniya poytaxti, mamlakatning muhim siyosiy, iqtisodiy va madaniy markazi. Temza daryosining quyi oqimida, Shim. dengizdan 64 km masofada, London havzasi deb ataluvchi tekislikning markaziy qismida joylashgan.
  
  

2. 
   A description and detail of the experience of the proposed project team members, including CVs. This should include all proposed team members to include a Project Manager, all Technical resources. This should include an explanation of where 3^rd party resources are included in the Submission
   

3. 
   Between one and three case studies of recent implementations which demonstrate your experience of similar projects. Where possible these should include search engine optimisation and/or integration with Open Text and/or integration with a portal and/or implementation of WebCenter Sites 11g. Please also provide high level details of all upgrade projects you have completed in the last three years (versions included, project timeline and resources used)
   

4. 
   The Bank is interested in using content from a source external to WebCenter sites. Please provide examples of customisation of the WebCenter sites including but not limited to web services, XML feeds or databases. Please explain how you have implemented this in your past projects.
   

5. 
   The Bank anticipates that the new intranet will call for substantial use of user sign-in in order to deliver a customised and personalised experience. Please provide examples of work involving sign-in to allow interactivity, UGC, social features, tailored content presentation and so forth.
   

6. 
   The Supplier shall provide details of two customers for reference. References should be for customers with requirements similar to those of EBRD.
   

7. 
   Please provide company financial information for the past 3 years of filings with Companies House.
   

The Technical Proposal shall not exceed 30 pages excluding the Checklist and CVs.

Responses shall be submitted via e-mail to hays@ebrd.com in accordance with the timetable set out in section 4.2 of this RFP.
4.5 Quotation File

All Suppliers are required to complete the applicable quotation file (the ‘Quotation file’) attached as Annex D of this RFP. Prices are to be quoted in GBP net of VAT.

The Quotation File must be submitted:

• 
  on a CD or a USB drive by courier in a sealed envelope clearly identified as “PUR1608/15 – Provision of Professional Services to Support an Upgrade of the EBRD Intranet Site”;
  

• 
  in an envelope clearly bearing the Suppliers’ name; and
  
• 
  in accordance with the timetable set out in section 4.2 of this RFP.
  

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

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 majority of the TEP allocate it 70% (210 points) or higher of the maximum points available for the technical evaluation;
  
• 
  the mean of the combined TEP scores is 70% (210 points) or higher of the maximum points available for the technical evaluation; and
  
• 
  the Supplier scores the minimum qualifying mark for each element of the evaluation where one is specified in Table 1 above.
  

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 its proposal. The Supplier proposing the lowest total bid price will be given the maximum financial score available (700). Other Suppliers’ (higher) prices will be divided into the lowest price and the result multiplied by the maximum score given.

LP = the lowest evaluated financial proposal

EPa = the financial proposal of a.

5.3 Preferred Supplier

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

The Bank may contact the two 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.

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.

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.

The 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.

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 agree to terms that expressly contradict its special status and internal policies as an international organisation.

The contract awarded shall be performed in accordance with the contract sample contained in Annex D of this RFP.

EBRD 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.

EBRD 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.

Suppliers 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.

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.

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

Suppliers 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.

Please 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.

Incomplete 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.

ANNEX A – MINIMUM REQUIREMENTS CHECKLIST

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

1. 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.

2. 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.

3. 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: -

1. 
   Discovery – Analysis of existing requirements, discussion with internal subject matter experts SMEs and stakeholders.
   
2. 
   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.
  

3. 
   Governance - Review milestone and approval stage.
   
4. 
   Implementation – ‘Agile’ sprint delivery of functionality.
   
5. 
   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

• 
  Discovery / research / initial feature scoping
  
• 
  UX
  
• 
  User testing for frontend usability
  
• 
  Visual design
  
• 
  Content load
  

4. 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.

4.4 Search engine

The Lucene search engine, included with Oracle WCS, is currently in use on the ebrd.com internet website. The Bank’s preference is to use this for the new intranet, but the capability of this search engine would need to be validated, in the context of its ability to deliver a robust and fully featured search experience incorporating, for example, the following requirements.

1. 
   To explore options for configuration above and beyond the current simple ebrd.com implementation. In particular, autocomplete/suggestions for the search field, tolerance for minor misspellings and user access to own recent search history.
   

2. 
   Minimal ongoing maintenance.
   

3. 
   Implement analytics capabilities attached to the search engine, e.g. reports on search terms and behaviour.
   

4. 
   Explore the possibility of federated search, for example, returning hits from both the website, EDRMS (see below) and the directory at the same time (i.e. within one set of search results). The minimum requirement would be for an intelligent and complementary format, e.g. a set of tabbed results for intranet pages, document and directory results.
   

5. 
   Explore both technical and practical potential of having the search engine reference EDRMS content, to enable the major practical benefit of having all intranet documents housed within EDRMS.
   

6. 
   If federated search is not possible (i.e. prohibitively costly / risky / complex), investigate the possibility of providing ability for users to set a preference for which search results they'd like to see by default or to open other search aspects by means of one click on the appropriate tab.
   

4.5 Integration with the Bank’s EDRMS

As stated above, the Bank uses Opentext Content Server CS10.5 (formerly Livelink) as the EDRMS repository for official Bank records, but there is minimal integration between the intranet and the document management system. During this refresh, there is a desire to ensure that there is a closer integration between the two systems, in order to gain efficiency advantages such as reduction in duplication, improvements in workflow around authoring and more relevant return of search results.
The following capabilities should be considered and reviewed for implementation.

1. 
   The ability for content authors to drag/drop/include EDRMS documents to CKEditor.
   

2. 
   The ability for content authors to select one or more EDRMS documents to a content attribute to be presented on a page as a list of documents.
   

3. 
   The ability to make lists of links that include mix of EDRMS documents, internal and external links.
   

4. 
   Links to the EDRMS documents to have the file type recognised by the system and appropriate file type icon to be added to the document links automatically.
   

5. 
   Ideally other document meta-data will be added to the mouse over tooltip - for example: file size, version, author and a link to the EDRMS metadata screen.
   

6. 
   Where a link to a EDRMS document is created but a document has expired or deleted, the users will be presented with a friendly message that document is not available
   

7. 
   URLs of the EDRMS documents are not to be hard-coded in WebCenter Sites in case EDRMS base URL changes in the future.
   

8. 
   All that applies to the EDRMS documents should apply to the EDRMS folders. Created hyperlinks will take users to the EDRMS web interface showing contents of the folder.
   

4.6 Development of interactive, per user, features.

Most of the applications within the Bank currently have some form of active directory (AD) based single sign-on (SSO) or at least simplified (network password synchronisation) authentication of users. As per the current trend with both internal and external sites, there is a desire to exploit the capabilities of WebCenter Sites to provide more targeted and relevant content to users to improve business efficiency. The extension of this SSO facility to user intranet access should therefore be extended in order to enable the following potential advantages.

1. 
   Self-editing of a directory ‘profile’ page about the user, via the website and without needing any CMS access – see Appendix 2 – Figure 1.
   

2. 
   Configurable homepage based on user tastes; User can opt to show/hide elements, reorder parts of page, or add regularly used links to a favourites bar – see Appendix 2 - Figure .
   

3. 
   Configuration of news content to give additional weighting or reordering to content items based on particular tags that match user preferences
   

4. 
   Explore implementation of some sort of per user customisation on homepage to show a set of user specific relevant links perhaps five recent pages visited, or notification that a page they own was commented on, etc.
   

5. 
   Allow content authors to designate basic social interaction features to appear on certain pages (comments, ratings, votes, etc.), so that staff can once authenticated interact with the content.
   

6. 
   Introduce other social components such as ‘walls’ that can be embedded on departmental homepages for users to post news and updates in the familiar and simple context of a social feed.
   

7. 
   Possibly implement forum / message board functionality.
   

8. 
   Tailored homepage widgets, so that users see e.g. local time and weather forecast dependent on either their current location (if this can be detected) or their typical location, as specified in that user’s preferences.
   

4.7 Browser Compatibility

There is a push at the EBRD for web-based apps (including Intranet content pages) to be supported by both desktop and mobile browsers. There is therefore a requirement for multi-device support to be provided in general for the pages served by the WCMS:

• 
  multi-device UI framework across tablet, mobile, desktop; and
  
• 
  Supporting responsive design at both page and UI component level and UI components able to render themselves based on screen space allowed.
  

4.8 Authoring workflows

Due to the lack of usability of the Documentum CMS, current Intranet content authoring and publishing is largely centralised within the Communications team. As a result there has been no need to include any significant authoring workflow and approval process.
The Bank would like to take advantage of the move to the simpler and richer usability available in Oracle WCS to decentralise authoring to departmental teams, with the Communications team providing guidance and oversight. To that end, a role based setup and authoring workflow should be enabled for Intranet pages with the following considerations.

1. 
   Enable a system whereby CMS users have role-based publishing rights, with some subject to a simple workflow in order to publish, whilst others can publish directly.
   

2. 
   Create a mechanism for general staff (i.e. non-content authors) to submit basic content that is then delivered through workflow to an editor, for approval and publishing. For example, a user pastes some content into a web form in a generic template, then a new page containing that content is automatically generated in Sites, and a designated content author(s) is notified with a production ready page which they can then push live or edit.
   

4.9 Portal integration (optional)

The Bank is running a parallel project to implement an Enterprise Portal and there is an expectation that the intranet will ultimately be surfaced through the portal, and therefore some integration of Oracle WCS with the portal would be necessary. The level of integration will need to be discussed and determined during the discovery phase, largely to agree the best approach, both in the short and longer term for search performance and personalisation aspects of the intranet.
The use of key functionality within the portal will need to be balanced against the complexity and risk introduced to ensure the timescales for delivery of the Intranet project are not jeopardised.

• 
  Review potential integration with the chosen portal supplier – interface to be confirmed pending the output of the portal proof of concept (PoC) outcome, which is scheduled to complete Q4 2016.
  

• 
  Explore the feasibility of integration with the portal via WebCenter Sites REST API/ATOM/CMIS protocols.
  

• 
  Explore use of the identity and access management (IAM) within the portal.
  

4.10 System upgrade (optional)

The EBRD currently uses WebCenter Sites 11.1.1.8 patchset 8 and would like to explore the feasibility of upgrading to WCS 12c. The approach to carrying out this upgrade, potentially running two versions in parallel (temporary Oracle license costs permitting), identifying clearly the risks associated with the upgrade and there are no delays to the key deliverables identified.

• 
  Explore feasibility of doing the WCS 12c CMS upgrade, and implement if appropriate. This would be dependent on the ability to avoid causing a significant delay to development progress.
  
• 
  If decision is not to upgrade, ensure all development is as futureproofed as possible in light of deprecated features in known upgrades
  
• 
  The successful supplier will have a necessary technical team depth and dedicated resources available for the upgrade activity to work in parallel with the main Intranet Design and Development project.
  

4.11 Content migration (optional)

4.11.1 Departmental content

The approach to be adopted for content, especially around departmental sites, will be very specifically to focus on the creation of new content, or at a minimum to enforce a ‘deep dive’ review, rather than to default to the migration of existing content.
Whilst it is not expected to be a component of this RFP, which is concentrating on technical design and development, the Bank would like to understand the costs and potential approach for this in outline as an option to for further consideration.

4.11.2 Blueprint

Additional to departmental site content detailed above, the Bank has an internal weekly news bulletin called Blueprint of which there is an archive of around 6400 pages. The Bank will be looking for a means to import some or all of the content for Blueprint into the new site. It is likely this will be limited to the most recent 1-2 years of Blueprint archives, but clearly this is a balance between cost and functionality.
The Bank would expect the images and docs to link to static legacy archive.
The Bank will consider having historical Blueprint articles linked into the site and served from a separate web archive.
e.g. http://web-archive.ebrd.com:3039/news/blueprint/2016/160215/index.shtml

Annex B - Appendix 1 - Intranet metrics and details on current landscape

Documents on intranet

There are about 5.5k documents on current intranet of which 4k PDFs. Currently almost all the documents are managed in the Documentum.

Performance requirements

• 
  All the general content pages to be served from Satellite Server cache wherever possible.
  
• 
  All reference data to be cached and served from the application scope cache
  
• 
  Ability to sustain 9AM hits on home page.
  

Stats and the graph below show values of a typical month:

• 
  Total Hits: 19,160,521
  
• 
  Home page views: 575K
  

Please note: There can be several hits on each page. While the volume of hits reflects the amount of server traffic, it is not an accurate reflection of the number of pages viewed.

• 
  The core of the content on pages to load within 1-2 seconds, with full page load to be under 4 seconds.
  
• 
  A solution in the area of cache-ing of content listings and search and filter pages will be highly valued.
  
• 
  Content authors and administrators to have ability to flush the Satellite Server and the reference data cache (i.e. by means of appending “?flush=1” to the URL of the page).
  

Customisation and other code

The following customisations have been included in the setup and configuration of the existing ebrd.com internet site, managed within Web Center Sites, and as a minimum these, or similarly agreed functionality, should be included / provisioned within the intranet site.

• 
  Authentication - The contributor authentication is done via corporate Active Directory. WebCenter Sites has been configured to use AD as the authentication provider.
  

• 
  Search - Lucene search that comes as a part of WebCenter Sites has been extended to provide index for the main external website http://www.ebrd.com. A custom com.fatwire.search.lucene.AnalyzerFactory class is used to enhance the index and to link page modules to the page index.
  

• 
  Automated Data Import - Some custom CSElements and Java classes have been designed to handle data import from other data sources and systems within the bank, i.e. Project Summary Documents, Procurement Notices etc.
  

• 
  CKEditor - The CKEditor has been configured per site to allow the styles of the site to appear within editors formatting options.
  

• 
  Dual publishing - As shown on the existing infrastructure diagram there is dual publishing from the management server to the PROD and the DR web delivery servers. This is achieved by extending of following classes:
  
  • 
    com.fatwire.realtime.AbstractTransporter
    
  • 
    com.fatwire.realtime.messaging.AssetPublishCallbackImpl
    

• 
  Analytics - The Bank has used Webtrends (Currently version 9.2.4.35 in the past and would like to explore the possibility of developing site in such a way that it is possible to add analytics code to content on a per page basis, not per template.
  

Annex B - Appendix 2
Figure 1: Existing Web Center Sites Infrastructure

ACTIVE INFRASTRUCTURE

PASSIVE INFRASTRUCTURE /
DISASTER RECOVERY

DMZ

Internal LAN

WEB DELIVERY
PROD

WEB DELIVERY
DR

INTRANET DELIVERY
PROD

INTRANET DELIVERY
DR

MANAGEMENT
PROD

MANAGEMENT
DR

DATABASE
PROD

DATABASE
DR

DATABASE
PROD

DATABASE
DR

Firewall

Legend

Enabled publishing

Disabled publishing

Oracle JDBC

JDBC/1521

JDBC/1521

JDBC/1521

JDBC /1521

JDBC /1521

JDBC /1521

http/9280

http/9280

http/9380

http/9380

The following schematic show the Bank’s current setup of the Web Center Sites infrastructure, including business continuity provision
Figure - Personalised interactive features (1) - Self-edit of directory profile page



Figure - Personalised interactive features (2) - Configurable homepage




Annex C – Quotation File




ANNEX D – STANDARD CONTRACT

Download 0,69 Mb.