20 December 2019
2019-12-20T17:00:00.0000000 2019-12-20T17:00:00.0000000 Europe/Malta IT Network Operations Centre AIOps Solution IT Network Operations Centre AIOps Solution - Request for Information Malta

Deadline for submission of responses extended to Friday 20 December 2019

MITA is issuing a Request for Information (RFI) for an AIOps solution to enhance the 24x7 visibility of the Network Operations Centre (NOC) across Government IT systems and services. The main objective is to instil predictive analysis within the day-to-day operations while also improving proactivity, embracing automation and expediting root cause analysis.

The scope of the solution being sought is the end-to-end Government IT infrastructure comprising of various components which include hardware, software applications, networks, appliances, and other physical and virtual components. The solution is required to provide insights into each individual component while also correlating data from various repositories to realize the aforementioned objectives.

More information is available from the RFI document that may be downloaded from this link.

Click here for a .DOCX version of the RFI document.

This RFI and the prices being requested are for market research only. The scope of this RFI is neither exhaustive nor conclusive of the requirements that may be published in subsequent call for tenders or expressions of interest.

Submissions are to reach MITA by not later than Friday 20 December 2019. Submissions of responses to the RFI are to be made via email quoting the RFI title and reference number.

Economic Operators may subscribe to receive notifications related to this RFI by filling in the details below.

 

 

 

 

 

Clarifications

 

#

Query

Answer

Date of Publication

1

Section C: Question 1F – We would like to understand what do you mean by “Autonomous visibility”.

This question is referring to whether the tool is capable of gathering the necessary information from separate components which forms a particular service, with the tool being intelligent enough to be able to link components together autonomously without having to set models/ links/ topology manually, whilst also correlate logs/metrics/events etc. between them. It is important that such is capable to provide visibility on all tiers of the infrastructure. A Topology view / service map should then follow automatically.

13 November 2019

2

In Section "Objectives and Scope" of the RFI it is said that the solution should include "hardware, software applications, networks, appliances, and other physical and virtual components".

Our question is if the response should include details or estimated effort:

-  for the installation and deployment of the solution

-  for customizing/extending the solution for specific use cases in 4.D.

MITA is currently evaluating options. To this extent the AIOps solution may be cloud-based, on-premise, or a technology using both. To this extent, MITA is not requesting any specific configuration of hardware, software, appliances or other.

In continuation, with reference to the Objectives and Scope of RFI, the solution should be able to monitor various layers of technology, including hardware (servers, routers, switches, firewalls, etc), software applications (including and not limited to operating systems, logs, databases, etc), appliances, networks and other components as normally involved in the delivery of an IT service.

 

The response may also include estimated effort in terms of time as well as cost for the installation, deployment and customization of the solution to a live environment, as well as for any training that may be given to MITA.

 

21 November 2019

3

Is it possible to get a list of the current/planned ITSM solutions within the scope of the RFI?

Marval - https://www.marval.co.uk/

 

21 November 2019

4

In respect of Cloud solution vs On premise solution: is a cloud service a preferred solution in respect of on-prem installation? Is a hosted or managed cloud solution considered better than a on-prem solution?

At this phase, we are open to all options. Therefore, the solution can be a Cloud Solution, on premise one or hybrid.

 

21 November 2019

5

Do [we] also to propose a Network and/or Application/Infrastructure monitoring solution, or do we have only to integrate with existing monitoring tools?

We are evaluating options at this phase. The main focus is the implementation of an AIOPS for real proactive and preventive monitoring. The document makes reference to the current tools which the tools has to integrate with, however if one believes that apart from the AIOPS solution, addition of other tools would benefit for a better proactivity and prevention, we are open to all information at this phase.

 

21 November 2019

6

Is the solutions required to replace existing solutions stated in Section C Clause 1a – PRTG, SolarWinds?

As described in Point n.5, at this phase we are open to all options with the main focus being AIOPS. For instance, if specific tools provide more insight / proactivity / prevention with the inclusion of other solutions other than the current ones already in-place, other tools can be recommended for our consideration.

 

21 November 2019

7

Size of network to be monitored – number of devices, average number of interface/ports per device, number of SNMP performance metrics monitored per port/interface

Typical SNMP polling period – e.g. 5 minutes

Is NetFlow monitoring required?

Is Cisco IP SLA monitoring required?

Vendors and Types of networks devices: e.g. Cisco ISR G2 etc

Size of network to be monitored

·         Between 100 and 200

Average number of interface/ports per device

·         Average of 30

Typical SNMP polling period – e.g. 5 minutes

·         1 minute

Number of SNMP performance metrics monitored per port/interface

·         Between 5 to 10 per interface

Is NetFlow monitoring required?

·         Yes, would be good to have.

Is Cisco IP SLA monitoring required?

·         Yes, would be good to have.

Vendors and Types of networks devices: e.g. Cisco ISR G2 etc

·         Cisco, HP, Fortinet, Juniper

 

21 November 2019

8

In respect of question "C.1.g Does the solution have the ability to correlate service outages / degradation resulting from configuration changes while highlighting the said configuration changes to NOC?"

 Do  we  need  to  detect  the  configuration  changes?  Or  integrate  with  a  Change  Management system like ServiceNow or IBM Control Desk or Others?

The requirement is for the tool to be able to either detect configuration changes or make use of our ITSM, or both ideally. The aim is to outline anomalies or disruptions which might be incurred due to a configuration change.

 

21 November 2019

9

In respect of question "C.1.h: Have the ability to show the time stamp of the network configuration changes resulting in exceptional service trend?" Please, can you better explain this timestamp to which event is related? Which monitoring tool is providing it? Please, can you provide an example of the network configuration Changes that you are referring to?

This is in conjunction with Point n.8, where the network configuration change, if detected is depicted for example in a graph, which visually aids whenever an exceptional service trend is incurred after a configuration change. Conf change can for example be a new ACL being implemented which although does not hinder the availability of the device itself, it might be impacting a specific service / traffic towards a service. Currently we don’t have the capability to depict network changes in utilisation graphs with the current tools implemented.

 

21 November 2019

10

In respect of question "4.C.1.d Provide the capability to monitor at the hardware layer for servers and networking equipment?" are there any corresponding hardware vendor management tools deployed? If so, could these vendor tools send any type of alerts to external management systems?

Currently we make use of a number of OEM hardware monitoring tools (Dell OpenManage, HPOneView, Fujitsu ServerView). The new tool if supported can either integrate with such tools, or else have the capability to import MIBs and monitor the equipment without the need for such OEM tools.

 

21 November 2019

11

In respect of question "4.C.1.f Provide autonomous visibility and correlation across typical components on all tiers ofthe infrastructure, without support from other monitoring tools?" is then required to provide a mechanism or tool to collect the required data for such an autonomous visibility?

The tool can be autonomous in order to provide such requirement, otherwise if additional tools are required, we are open to all information at this phase.

 

21 November 2019

 

Register your Interest