ENTERPRISE MANAGEMENT SYSTEM (EMS) SOFTWARE 1.0 EMS SOFTWARE DELH
1.5 SERVICE DESK
Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications
1.5.1 Software Name andVersion Number Required 1.5.2 Update & close jobs /tickets Required 1.5.3 Place jobs / tickets on
“Hold” Required
1.5.4 Ticket auditing facility should provide by the “Service Desk tool”. (Will give a history of the ticket)
Required
1.5.5 Transfer & assign the jobs tickets to other location help desk person
Required 1.5.6 Assign priorities to Jobs /
Tickets. (This should assign as per the seniority & aggraded SLA model)
Required
1.5.7 Specify & track target job completion status based on various factors as, Dates, Priority etc.
Required
1.5.8 Services desk tool should have capability to
categories the jobs as per the structure of a problem ex: Server related problem should assign to
hardware team
Required
1.5.9 Service desk should have a “SLA” mapping /
monitoring &
tracking feature. (When a ticket is raised, Target Helpdesk calculates the most relevant service level agreement according to the contact and any asset identified).
Required
1.5.10 Service desk should record time duration spent on each ticket
1.5.11 Service desk should be able to provide role base access to users
Required 1.5.12 Service desk module
should have its own database (CMDB) which will incorporate as “Knowledge base search” (Kind of FAQ’s for L1 person)
Required
1.5.13 Service desk tool has to have inbuilt “Escalation Matrix” which help for the notification purpose to operators & users about their tickets
Required
1.5.14 The tool should maintain
Asset Information Required 1.5.15 The tool should have a
facility to link files (error, log files) to help desk tickets.
Required
1.5.16 License provided Required
1.6 The Enterprise Management System should provide a robust reporting system with all the standard reports and User can define their own reports and dashboards without having any additional cost implication to OTPC. OTPC shall not have any commercial implication for any kind of customizations and developments required to develop the customized reports as per the requirement of OTPC.
SECTION 2.14
TECHNICAL SPECIFICATION FOR
VIRTUALIZATION SOFTWARE (DELHI & PALATANA) 1.0 VIRTUALIZATION SOFTWARE
Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications
1.1 Software Name andVersion Number Required
1.2 Number of physical CPUs
per license. 1
Software that supports more than 1 CPU per license may be preferred 1.3 Number of Managed
Operating System Environment per license
Unlimited 1.4 Anti-virus / Anti-malware
protection Required 1.5 Database server licenses
for management databases
Required 1.6 Support for enterprise
operations monitoring and management of hosts, guest VMs, and application workloads running within VMs from day 1
Required
1.7 Support for private cloud
management capabilities Required 1.8 Web based management
console Required
1.9 Logical processors per
host 320
1.11 Active VMs per host 512 1.12 Virtual CPUs per VM 64 1.13 Host adjust virtual CPU
resources to VM Required 1.14 Virtual RAM per VM 1 TB 1.15 Hot-add virtual RAM to
VM Required
1.16 Dynamic Memory
Management Required 1.17 Guest NUMA (Non-
Uniform Memory Access) support
Required 1.18 Physical hosts per
cluster 32
1.19 VMs per cluster 4000 1.20 Virtual Machine
snapshots 32
1.21 Integrated application load balancing for scaling-out application tiers
Required
1.22 Bare metal deployment of new Hypervisor hosts and clusters Required 1.23 Virtualization of USB devices Required 1.24 Virtualization of serial ports Required
1.25 Boot from flash Required 1.26 Boot from SAN Required 1.27 Live migration of
running VMs Required 1.28 Live migration of
running VMs without shared storage between hosts
Required
1.29 Highly available VMs Required 1.30 Failover Prioritization of
Highly Available VMs Required 1.31 Affinity rules for highly
available VMs Required 1.32 Cluster aware updating
for orchestrated patch management of hosts
Required 1.33 Guest OS application
monitoring for highly available VMs
Required 1.34 VM guest clustering via
files
1.35 Intelligent placement of
new VM workloads Required 1.36 Automated load
balancing of VM workloads across hosts
Required 1.37 Power optimization of
hosts when load balancing VMs Required 1.38 Backup of VMs and Applications Required 1.39 Site-to-site asynchronous VM replication Required 1.40 Virtual SCSI hard disks
per VM 60
1.41 Virtual Hard disk size 62 1.42 Boot VM from virtual
SCSI disks Required 1.43 Hot add virtual SCSI VM
storage for running VMs Required 1.44 Hot-Expand virtual SCSI
hard disks for running VMs
Required 1.45 Storage QoS Required 1.46 Virtual Fibre Channels to
VMs Required
1.47 Live migration of virtual
storage for running VMs Required 1.48 Flash based read cache Required 1.49 Storage Via iSCSI, NFS,
Fibre Channel and SMB 3.0
Required 1.50 Storage Multipathing Required 1.51 VM storage provisioning
based on storage classification
Required 1.52 Dynamically balance and
re-balance load based on demands
Required 1.53 Distributed switches
across hosts Required 1.54 NIC Teaming Required 1.55 Private VLANs (PVLAN) Required 1.56 Virtual port ACLs Required 1.57 Trunk mode to VMs Required 1.58 Port monitoring Required
1.59 Port mirroring Required 1.60 Dynamic Virtual Machine
queue Required
1.61 Single Root IO
Virtualization (SR-IOV) Required 1.62 Virtual Receive Side
Scaling (Virtual RSS) Required 1.63 Network Quality of Service Required 1.64 Network virtualization / Software Defined Networking (SDN) Required 1.65 The Virtualization software should be based on hypervisor technology which sits directly on top of Hardware (Bare Metal)
Required
1.66 The Solution should be able to run various operating systems like windows client, windows server, linux.
Required
1.67 The Solution should have the capability for creating Virtual Machines templates to provision new servers
Required
1.68 The Solution should continuously monitor utilization across Virtual Machines and should intelligently allocate available resources among the Virtual Machines
Required
1.69 The Solution should allow for taking
snapshots of the Virtual Machines to be able to revert back to an older state, if required
Required
1.70 The Solution should be able to dynamically allocate and balance computing capacity across collections of hardware resources of one physical box aggregated into one unified resource pool
1.71 The Solution should provide support for cluster services between Virtual Machines
Required
1.72 The Solution should deliver above listed Hypervisor capabilities using standard server infrastructure from at least HP, DELL, IBM, Cisco and Oracle
Required
1.73 The Solution should allow Virtual Machines consume RAM
dynamically in such a way that if some of the VMs in Physical machine are not utilizing the RAM, this RAM can be utilized by some other VM in the same physical machine which has a requirement
Required
1.74 The Solution should be able to use power saving features like, in case of off-peak hours, if not all servers are required to be powered on, the solution should shut down to save power. There also need to be reporting associated with this capability.
Required
1.75 The Cloud Automation framework should provide capability for Role based Access for performing specific tasks
Required
1.76 The Solution should have the ability to develop highly customized workflows and easy user interface.
Required
1.77 The Orchestration Solution should be open and interoperable and has rich integration capabilities that support interfaces from
command line interface and web services
1.78 The Solution should be capable of extending entire functionality to virtual environment utilizing existing components of SDC such as Enterprise Management System (EMS) Required
1.79 The Solution should provide support for cluster services between Virtual Machines
Required
1.80 The Solution should have the capability for moving Virtual Machines from Primary site to the Secondary site.
Required
1.81 The Solution must offer Identity, Authentication and Role based access to User Departments Infrastructure - Machines (Virtual or Physical),
Required
1.82 The Solution must offer Policy based
administration by putting User Departments Machines (Virtual or Physical) in logical groups and apply relevant policies
Required
1.83 The Solution should have the ability to not just enforce policies but also track and report non-conformance to access
Required
1.84 The Solution should automate provisioning of new and changes to existing infrastructure (Virtual, Physical, Application or Common Services) with approvals
Required
1.85 The Solution should have capabilities to create workflows to automate common admin challenges
Required
have the ability to develop highly customized workflows and easy user interface.
SECTION 2.15
TECHNICAL SPECIFICATION FOR