Content migration automation to Sharepoint Online or locally hosted Sharepoint 2016 for UN

Tender: Content migration automation tool and services for IBM Unite Connects & Microsoft Sharepoint

Contracting Authority: UN Procurement Division, NY

EOI deadline: Nov 16

The Organization has recently moved its email platform from Lotus Notes to Office365. OICT is looking to decommission legacy collaborative systems, such as IBM Connections or IBM FileNet and Sharepoint 2007/2010/2013, and deliver a more integrated and holistic set of tools using the O365 platform. One of the substantial technical challenges will be the mapping and migration of content and accounts from one platform to the other. To achieve this migration a web-based platform with an intuitive user interface is required that enables administrators to safely and effectiviely migrate IBM Connections and/or SharePoint 2007/2010/2013/ content to Sharepoint Online (Office365) or locally hosted Sharepoint 2016.

The gathered information will be used to determine the feasibility, scope, timeframe and resources required by the UN to undertake such a content migration and how the use of commercial tools and services could be used to expedite this activity.

The high-level requirements which must be demonstated in the response to this RFI are as follows:

Ease of use – Intuitive UI that supports identification of content for migration from legacy IBM Connections, IBM FileNet repositories or older versions of Sharepoint to SharePoint Online. The ability to script the migration of user accounts and their associated content is also highly desireable.

Links Resolution – Automatically converts links within source documents/pages to links to SharePoint Online

Filtering – Content classification allows filtering/archiving of content which is no longer required

Content re-structuring – Supports mapping of source content structure to SharePoint Online Information Architecture

Content Analysis – Detailed XLS (spreadsheet) reports on pre-migration analysis

Security – migration of user and document permissions and other IBM Connections elements that must be mapped in order to migrate successfully into SharePoint online.

Migration of content- Wikis, Blogs, Files, Libraries, Communities, Activites, Bookmarks, Forums and Profiles into pre-created Sharepoint sites and/or create sites automatically

Comparision – of legacy IBM connections content with SharePoint content. Map contents, metadata and permissions to associated SharePoint artifacts.

Identification – of duplicate, near duplicate, redundant, obsolete and irrelevant data by examining file content and metadata

Bulk Migration – Select all required content at one go and perform bulk migration

Metadata Migration – Transfer the attributes of every file, folder, email, contact and other items

SharePoint apps support using Nintex Mobile, Workflows and Forms for World Health Organization

Tender: SharePoint Support & Maintenance – MyHealth App and ESMP

Contracting Authority: World Health Organization, HQ in Geneva

The purpose of this APW is to provide IT support and maintenance for two applications based on SharePoint 2013 using Nintex Mobile, Workflows and Forms.

Background: Two applications have been recently developed based on SharePoint 2013: MyHealth App and Emergency SOP Management Platform (ESMP). Both applications are currently in Production and stable. However, due to their criticality, we need to ensure the maintenance, bug fixes, updates and change requests.

  • MyHealth App for Emergencies: A solution to monitor health from field workers deployed for emergencies. This is done by collecting health information, alerting doctors whenever needed and providing to doctors’ easy access to field worker health information. This application uses Nintex Workflows, Mobile and Forms. Custom coding involved in HTML and JavaScript.
  • Emergency SOP Management Platform (ESMP): Provide a solution to host Policies, Procedures(SOPs) and Guidelines, allowing lifecycle management and including versioning and security management. It includes the consumption of content via a mobile offline/online functionality. This application uses Nintex Workflows and Forms. Custom coding involved in HTML and JavaScript; SharePoint Client/Server code and SharePoint Search customized using modern web technologies.

Planned timelines – Start date:  October 2018. Total duration: 1 year (with the possibility of renewal)

Requirements – Work to be performed:

  1. Support and incident management:

Covers correction of bugs or any applicative dysfunction. Based on trends from the last 6 months, the time spent on incident management is in average 3 days per month for both applications.

  1. Level 2 & Level 3 Support. Service Desk and L1 Support will be covered by WHO team.
  2. Support for the roll-out of upgrades and packages should be included.
  3. Response time based on priorities in line with an agreed Service Level Agreement.

All tickets are acknowledged within half a day, subsequent fixes should be within 3 working days. As a minimum, for incidents classified as high priority, response time should be within 0-8 hours (during business hours). High priority is considered to have impact in the core functionalities of the applications such as blocking errors. Telephone support and email support: 8:00 A.M. to 6:00 P.M. Monday – Friday in GVA time.

  1. Extended support (GVA weekends, public holidays) is optional. Should be listed and costed as a separate option.
  2. Change requests:
  3. An estimated of 25 man-days per year for working on change requests. WHO would expect some unused days to “roll over” to the next year.
  4. For changes classified as high priority, implementation should be done within 48 hours.

iii.           Delivery Management:

  1. Logging Issues – a process must be provided for logging issues/requesting changes and subsequent tracking and management of issues.
  2. Reporting – a process for delivering management reports on the volume and type of issues/raised and processing times.
  3. KPIs – some basic metrics on service delivery to assess compliance with the target SLA.

Characteristics of the Provider – Experience in supporting IT projects based on SharePoint technology on Client and Server side – Experience in HTML, JavaScript through the Sharepoint API. – Expertise in Nintex solutions including Nintex Mobile, Workflows and Forms – Experience in troubleshooting applications, workflows, hosting, browsers and mobile issues. – Experience working with international organizations and ideally within the field of global health. – Excellent knowledge of English and preferably a good working knowledge of French.

Deadline: Oct 24

Backup, Archive and Recovery solution to Centre for Maritime Research and Experimentation (NATO)

Tender: The Provision of Backup, Archive and Recovery solution to STO Centre for Maritime Research and Experimentation (CMRE).

Contracting Authority: NATO Centre for Maritime Research and Experimentation (CMRE), La Spezia – Italy

Descriptions: CMRE requires an enterprise-grade data backup, archive and recovery solution for its unclassified data centre in La Spezia and for the smallerscale data centre installed onboard the NATO Research Vessel (NRV) Alliance. Both data centres use virtualization based on Vmware to provide Infrastructure as a Service (IaaS). The systems for data backup, archive and recovery shall be supplied as a turnkey solution, inclusive of professional services for system installation, configuration, training, testing, and transition to operations.

  1. Introduction: 1.1 This technical specification covers the data backup, archive and recovery systems to be utilized to safeguard CMRE’s data and information assets, to achieve the following objectives: 1.1.1 Update and improve the reliability of the CMRE unclassified data centre by implementing a state of the art data backup and archive solution at CMRE in La Spezia, Italy; 1.1.2 Implement a backup and archive system for the NATO Research Vessel (NRV) Alliance that is coherent and integrated with the backup and archive system covering the CMRE data centre, to address requirements related to CMRE’s work on the vessel. 1.2 Two components are envisioned, one to be installed at CMRE, one to be installed on NRV Alliance, to provide data backup and archive for data centres of CMRE and NRV Alliance, respectively. 1.3 The two components shall be interoperable, coherently engineered and integrated, as better detailed by the technical requirements below.
  2. Description of the CMRE data centres: 2.1 CMRE is currently operating an unclassified data centre at its premises in La Spezia, Italy, composed using the following technologies: 2.1.1 Virtualization environment based on Vmware, used to provide Infrastructure as a Service (IaaS); 2.1.2 DellEMC VNX storage, used within the IaaS framework; 2.1.3 DellEMC Isilon Network Attached Storage (NAS). 2.2 A smaller-scale data centre is operated on-board NRV Alliance, with virtualization also based on Vmware, and with interconnections to CMRE using bandwidth-limited satellite links and, potentially, cabled links when in port.
  3. General requirements: 3.1 This section provides an overview of general requirements applicable to the backup and archive solutions for CMRE and NRV Alliance. 3.2 A high-level diagram (Figure 1) is used to depict how the different elements tie together. An indication of the sizing of the two systems is also given, covering both the CMRE component and the NRV Alliance component. 3.3 The supplier shall provide a backup solution designed, built and implemented using elements from one single manufacturer/vendor, to minimize risks due to the integration and support of different products made by different vendors. 3.4 The backup and archive systems shall cover not only the IaaS components, but also the applications that are hosted within those infrastructure services. 3.5 The backup and archive system shall allow for backup, restore, verification and archiving of the IaaS components, to include the applications hosted on the IaaS components. 3.6 The backup and archive system shall provide periodic and ad-hoc data backup capability through a single user interface. 3.7 The backup and archive system shall provide reports and dashboards on overall backup system health, system activities and availability of the backups. 3.8 The backup and archive system shall provide replication capabilities to support continuous data protection, at the virtual machine level, to any point-in-time recovery (PITR). 3.9 The backup and archive system shall provide built-in capability to perform disaster recovery orchestration workflows. 3.10 The backup and archive system shall be composed of the following tiers: 3.10.1 Near-term (6 Months) (online); and 3.10.2 support to cloud tier solutions. 3.11 The backup and archive system shall be non-disruptive to the functionality and performance of the IaaS Components and of the backup target. 3.12 The backup and archive system shall have the capability of being integrated with IaaS Automation and Orchestration System for scheduling any job that can be executed in the backup and archiving system. 3.13 The backup and archive system shall provide reports on performance and capacity of the system. 3.14 The backup and archive system shall have the following functionalities: 3.14.1 Is managed and monitored centrally; 3.14.2 Has the ability to prioritize backup/restore tasks; 3.14.3 Has the ability to schedule full and incremental backups; 3.14.4 Has the ability to assign role based access for various admin roles; 3.14.5 Has the ability to do integrity checking, encryption, compression and deduplication; and 3.14.6 Supports compression. 3.15 The backup and archive system shall be able to process (i.e. backup, restore, verify and archive) all user data, applications data and system data, including but not limited to: 3.15.1 All operating systems (OS) supported by the Hypervisor component on a Virtual machine or running on a physical server; 3.15.2 All Virtual Machine (VM) and OS templates; 3.15.3 Databases such as Oracle, Microsoft SQL Server, MongoDB, Cassandra, etc., and Hadoop; 3.15.4 All User data hosted on any one of the nodes. 3.16 The backup and archive system shall ensure that data that is currently on-line and in use (open files, databases, information stores, running VM’s, etc.) can be backed up or archived while staying online. The back up operations shall not cause the application or user to lose the connection to the data source. 3.17 The backup and archive system shall provide the following granularity or Recovery Level Objectives (RLO): 3.17.1 File shares: single file; 3.17.2 Database: single record, log files, database; 3.17.3 OS: system state, log files and OS image. 3.18 Sizing – CMRE Data Centre 3.18.1 The solution for CMRE shall be dimensioned appropriately for the backup of 290 TB front-end capacity, divided as follows: 3.18.1.1 210 TB NAS (DellEMC ISILON) 3.18.1.2 20 TB RDBMS 3.18.1.3 60 TB Vmware 3.19 Sizing – NRV Alliance 3.19.1 The solution for NRV Alliance shall be dimensioned appropriately for the backup of 20 TB frontend capacity on a Vmware farm.
  4. Mandatory technical requirements for backup & archive solutions: 4.1 The systems for data backup and archive shall be supplied as a turnkey solution, inclusive of professional services for system installation, configuration, training, testing, and transition to operations. 4.2 Mandatory technical requirements are listed in the tables below. 4.3 Requirements falling in category “General Requirement” (“General Req.” in the table, IDs # 1.1-1.37) are applicable to both the CMRE and NRV Alliance systems, and both systems shall be compliant with those characteristics. 4.4 Additional requirements are given for the CMRE solution (IDs # 2.1-2.7) and for the NRV Alliance solution (IDs # 3.1-3.5), and the systems proposed for the two locations shall be compliant with those additional characteristics.

Deadline Nov 12 – 10:00