ENTERPRISE MANAGEMENT SYSTEM (EMS) SOFTWARE 1.0 EMS SOFTWARE DELH
1.2 SERVER MANAGEMENT Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications
1.2.1 Software Name andVersion Number Required 1.2.2 Number of servers to be managed System Integrator to propose as per the solution and requirement mentioned in the RFP. 1.2.3 System Integrator need
the licenses to manage the number of servers as per solution and RFP requirement and additional 10% buffer. 1.2.4 This module is primarily
used to ensure that the performance of heterogeneous servers and operating systems are being monitored through agent based / agent less on a 24 X 7 basis. The module should have capability that in case of any problem, suitable preventive and corrective actions can be initiated.
Required
1.2.5 It should ensure the availability of the system resources and service independent of the machine location, collect performance data for capacity planning and alert generation of potential problems.
Required
1.2.6 The module should have capability to generate problem summary for a day to show the systems which generated maximum number of exceptions during the previous day along with details on resource utilization, including but not limited to, run queue, CPU utilization, memory utilization, swap utilization, page outs per second and number of processes, exception details and grade of service for these systems.
Required
1.2.7 The module should have capability to provide online and historical graphs and reports of
system health. It should provide for a web-based health console display that includes robust and flexible graphing capabilities for multiple metrics simultaneously, provides comparative and trending analysis. 1.2.8 ESM should be able to
run OS flavours such as Windows, HP-UX, IBM AIX, Sun Solaris, Red Hat™ Enterprise Linux, Suse Linux Enterprise Server, Debian Linux
Required
1.2.9 Service discovery Required 1.2.10 Should provide
comprehensive event management, proactive performance monitoring, automated alerting, reporting and graphing for operating systems, middleware and
applications.
Required
1.2.11 Should a web browser interface that can be accessed from anywhere using industry-standard web browsers.
Required
1.2.12 Each operator should be provided with a specific user role based view, restricting what they see and what they can do within the managed environment.
Required
1.2.13 Integrated scheduled and operational maintenance modes for managed systems to prevent operations staff from seeing false alarms during authorized outages
Required
1.2.14 Flexible architectures including support for high availability cluster architectures (Microsoft Cluster Server) and disaster tolerant
distributed architectures with multiple Management servers (failover, competence centers, etc.)
1.2.15 Should use intelligent filtering, duplicate suppression and correlation, the agents manage by exception only forwarding actionable events to the Management server.
Required
1.2.16 Should support for monitoring Data Centre technologies such as virtualization and clusters
Required
1.2.17 Auditing and logging of
operator activities Required 1.2.18 Accelerate root cause
analysis through advanced analytics and problem resolution
Required
1.2.19 ESM must filter, correlate, process, and respond to the thousands of events that are created daily from systems, databases, and applications.
Required
1.2.20 ESM must provide a centralized point of control that offers operations staff close and efficient control of events happening across the managed systems, creating a "mission control" centre for the distributed environment.
Required
1.2.21 ESM must include very powerful event management and correlation services technology, providing correlation capabilities on the intelligent agents in addition to the central manager station
Required
1.2.22 Secured communication
server and Managed nodes
1.2.23 ESM must support the backup server concept, which enables switching management
responsibility from one management centre to another in case of system failure. This eliminates single points of failure in the management system.
Required
1.2.24 ESM should notify through alerts, events, email alerts, SMS etc
Required 1.2.25 Automated policy deployment with detailed, intelligent monitoring Required
1.2.26 Predefined policies that include event log, service monitoring, metric collection, thresholds, alarms with meaningful message text, instruction text, operator / automatic actions / linked graphs, duplicate message suppression
Required
1.2.27 Predefined
graphs/reports Required 1.2.28 Predefined tools (for
troubleshooting) Required 1.2.29 Web Application Servers Required 1.2.30 Out of the box reporting
templates available for performance and availability of managed servers
Required
1.2.31 Should provide reports that can prove IT service quality levels, such as application response times and server resource consumption
Required
1.2.32 Reports should be accessible via web browser
Required 1.2.33 Reports can be Required
scheduled to publish automatically or they can be produced on demand
1.2.34 Reports can be applied to all systems, to a group of systems, to a customer group of systems, or to a single system. Required 1.2.35 Should be possible to send reports via email from the GUI
Required 1.2.36 Automated report generation and publishing Required 1.3 DESKTOP MANAGEMENT Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications
1.3.1 Software Name andVersion Number Required
1.3.2
Software should maintain minimum 200 desktops which could spread across multiple locations.
Required
1.3.3 The solution should support maintains the status of the desktop with respect to software installed and OS, patch levels as per
organization policy.
Required
1.3.4 The solution should include inventory management (hardware and software inventory), software management
(push and pull), patch management, usage management and OS management. 1.3.5 The software should
have a single agent which is capable of inventory as well as software management (software pull / push) and including patch management.
Required
1.3.6 The software should be capable of bandwidth throttling and other features which use the network efficiently. Please describe the features your software offers for efficient usage of network bandwidth.
Required
1.3.7 The software should
support MS SQL Server Required 1.3.8 Solution should support
multiple levels of administrative
delegation. The system should be able to define multiple levels of administrative domains and regions so that each administrator is assigned certain resources for which they are responsible for managing the application from the business perspective.
Required
1.3.9 The solution should support a distributed architecture with centralized or distributed management capabilities. Required
1.3.10 The Software should support multi-tiered architecture as well as bandwidth optimization techniques to optimize the WAN usage and for faster deployment of software.
1.3.11 The agents required for the solution should be deployed on all the desktops to be monitored
Required
1.3.12 It should provide out-of- the-box reporting capabilities for general reporting requirements in the form of printable table views, graphical views, explorer-type views, and list views.
Required
1.3.13 The solution should combine advanced hardware and software scanning technology with efficient and open database design, and provide comprehensive information needed to manage IT assets
Required
1.3.14 The software should have capability to discover software and hardware inventory across all computing devices enterprise-wide and have accurate, up- to-date IT asset information to more effectively meet IT project planning, auditing, compliance reporting and configuration management needs. Required
1.3.15 The software should collect hardware and software inventory across multiple platforms. It should have the capability to collect information from every desktops and notebooks.
Required
1.3.16 It should have the capability to be able to discover the hardware and the software configurations of elements, including but
not limited to, Processor type, Memory, Hard Disk, I/O ports, I/O cards, Operating System, etc.
1.3.17 It should integrate with help desks and other system management tools for seamless operations and CMDB updates.
Required
1.3.18 It should support policy- based model that allows IT administrators to efficiently and concisely define entitlements, controlling the
deployment of software and content to PCs, authorized users and subscribers.
Required
1.3.19 The software should ensure that subsequent changes to policies and entitlements cause software and content to be automatically
installed, changed or de- installed for all affected users and PCs.
Required
1.3.20 The agents should store a local copy of the inventory for comparison on next scan and send only the differential data on inventory scan.
Required
1.3.21 The module should have capability to track software usage
throughout the Microsoft windows environment so as to effectively manage the risk of unauthorized usage or under-licensing of software.
Required
1.3.22 The software should be effective, reliable and scalable for software delivery and distribution, particularly for patch distribution and management.
1.3.23 It should provide increased flexibility to define and initiate the update by push or pull interfaces and should support Multicast distribution.
Required
1.3.24 It should provide facility to increase efficiency of network bandwidth usage by using intelligent network conserving capabilities Required
1.3.25 The software should accelerate deployment and automate the maintenance of applications and
content, personalized for individual end users or groups as prescribed by policies.
Required
1.3.26 The software should automatically prepare an application package and ensure deployment compliance
Required
1.3.27 The software should have capabilities to target individual PCs, workgroups or entire populations of PCs for deployment and maintenance of software and content according to policies.
Required
1.3.28 The module should have capability to track the software that is deployed on a PC
Required
1.3.29 It should have the capability to automatically repair damaged software on any managed desktop.
Required
1.3.30 Any and all software on the managed desktops should be automatically discovered and reported. It should be able to capture inventory information from various
sources on the desktop including Add/Remove programs, WBEM, Registry, etc.
1.3.31 Inventory reports should be available to be viewed over the Web and should be able to be extracted in various formats. Required 1.3.32 It should be able to collect WBEM information which provides a vast repository of inventory. It should be capable of using multiple collection techniques for full file, path and registry information scanning.
Required
1.3.33 Application Management Required 1.3.34 The software
maintenance should be policy-based and not list-and-script i.e. The software configuration on the managed desktops and servers should be maintained automatically based on policies set in the central configuration server or Active Directory server.
Required
1.3.35 It should allow integration with Active Directory server such that changes to policies in the AD are
automatically reflected and enforced in the configuration
management software as well.
Required
1.3.36 The solution should provide capability of enabling deployment of applications along with all the pre-requisites.
Required
1.3.37 It should have a built-in reporting system that provides extensive reports of hardware and
software inventory. 1.3.38 It should allow you to
group and sort the resulted based on more than one field.
Required
1.3.39 It should have the provision to summaries the report in terms of spread of various values like I3 - 4 machines, I5 - 6 machines etc. or give a total count of
machines in the report
Required
1.3.40 The administrator should have the flexibility to scheduling each and every module independently viz. hardware , software, template inventory, reporting etc. Required 1.3.41 Configuration Management components should be designed for flexibility during deployment and ongoing operations. They could all be installed on one server or the components can be distributed across various servers. Virtually any component could be put almost anywhere in the network. Each component should be designed to have minimal impact on the computers on which it resides.
Required
1.3.42 Patch Management Required 1.3.43 The Patch Management
module should manage the entire lifecycle of patches, hot-fixes, updates and service packs from automatic discovery, download and collection, through testing, conflict analysis, and vulnerability
assessment, to policy- based targeting and deployment and on- going management to ensure that patches stay applied as prescribed by policy.
1.3.44 The patch management module should be able to deliver updates on the test computers to check conflicts
Required
1.3.45 The Patch management module should be able to automatically download patches from the vendor support site, automatically package the patches and deploy the patches based on policy defined.
Required
1.3.46 The Patch Management software should
automatically ensure the maintenance of all the deployed patches. I.e. if a certain patch is deleted or de-installed from any desktop by the user, it should
automatically be repaired / re-installed without the intervention of the Administrator.
Required
1.3.47 The Patch Management module should support automatic download and deployment of patches for MS Windows platforms
Required
1.4 MANAGEMENT AND MONITORING OF VIRTUALIZED SERVERS