NATIONAL HEALTH LABORATORY SERVICES INVITATION FOR BID YOU ARE HEREBY INVITED TO SUBMIT BIDS FOR THE REQUIREMENTS OF NATIONAL HEALTH LABORATORY SERVICES BID NUMBER: RFB 023/13-14 CLOSING DATE: 13 AUGUST 2013 CLOSING TIME: 11:00AM PUBLIC TENDER OPENING 11:30 BID VALIDITY PERIOD: 90 days (commencing from the RFB Closing Date) IMPORTANT: NO BRIEFING SESSION WILL BE HELD All questions must be sent per e-mail to on or before 08 AUGUST 2013. DESCRIPTION: APPLICATION FOR PERFORMANCE MONITORING SYSTEM FOR A PERIOD OF THREE (3)YEARS BID DOCUMENTS MUST BE MARKED WITH THE FOLLOWING: OR DEPOSITED IN THE BID BOX SITUATED AT: Procurement Controller: MS A Shusha RFB: 004/13-14 Bidders Name: ______________________ RFB: Enclosed-Regret (delete N/A) Closing Date: _______________________ NHLS MAIN RECEPTION 1 Modderfontein Road, Sandringham, Johannesburg. Bidders should ensure that Bids are delivered in time to the correct address. If the bid is late, it shall not be accepted for consideration. ALL BIDS MUST BE SUBMITTED ON THE OFFICIAL FORMS – (Please note that no changes on the content of this document is allowed) THIS BID IS SUBJECT TO THE GENERAL CONDITIONS OF THE BID, THE GENERAL CONDITIONS OF CONTRACT (GCC) AND, IF APPLICABLE, ANY OTHER SPECIAL CONDITIONS OF CONTRACT.
11.1.7 NHLS reserves the right to; cancel or reject any proposal and not to award the proposal to the lowest bidder or award parts of the proposal to different bidders, or not to award the proposal at all. Accept Do not Accept 11.1.8 Where applicable, bidders who are distributors, resellers and installers of network equipment are required to submit agreements and service level agreements with their principals. Accept Do not Accept 11.1.9 By submitting a proposal in response to this RFB, the bidders accept the evaluation criteria as it stands. Accept Do not Accept 11.1.10 Where applicable, NHLS reserves the right to conduct benchmarks on product/services offered during and after the evaluation. Accept Do not Accept 11.1.11 NHLS reserves the right to conduct a preaward survey during the source selection process to evaluate contractors' capabilities to meet the requirements specified in the RFB and supporting documents. Accept Do not Accept 11.1.12 the bid calls for commercially available solutions, bidders who offer to provide future based solutions will be disqualified. Accept Do not Accept 11.1.13 Accept Do not Accept
3.5. Cross tiers tracing: The Software shall perform across tiers diagnosis (i.e. Application Server - Application Server; Application Server - Database) Comply Not Comply 3.6. Performance analysis: The Software shall analyze performance issues on transaction, application and function level Comply Not Comply 3.7. Cross application server tracing: The Software monitor transaction spans all interacting tiers and applications beyond a single application server Comply Not Comply 3.8. Business transaction search: The Software shall support comprehensive searching on Business content & context e.g. customer name, time range and specific faults Comply Not Comply 3.9. Define Transaction: The Software shall allow to define the transaction to assess the performance of business transactions Comply Not Comply 3.10. Auto and manual correlation: The Software shall allow to define the values to correlate the transaction automatically and manually Comply Not Comply 3.11. Performance metrics Dashboard: The Software shall provide graphic view of transaction performance metrics over time Comply Not Comply 3.12.
6.2. 32-bit and 64-bit Java support: The Software shall support 32-bit and 64-bit JDK Comply Not Comply 6.3. CPU profiler: The Software shall show CPU usage in different granular view (e.g. call tree, hot methods) Comply Not Comply 6.4. Garbage collection profiling: The Software shall show garbage collection statistics (e.g. GC count) Comply Not Comply 6.5. Thread profiler: The Software shall show thread usage in different granular view (e.g. hot threads, top blocking threads) Comply Not Comply 6.6. Deadlock detection: The Software shall show deadlock effortlessly Comply Not Comply 6.7. Memory leak detection: The Software shall determine the potential memory leak and the size of the leak effortlessly Comply Not Comply 6.8. Export data: The Software shall export profiling and performance data in different format (e.g. Excel, CSV) Comply Not Comply 6.9. Real time and historical data support: The Software shall support query on real time and historical data Comply Not Comply
6.10. Identify stalled component: The Software shall identify stalled Java components and methods proactively Comply Not Comply 6.11. Dynamic Instrumentation: The Software must provide easy dynamic instrumentation of application code, i.e. be able to enhance monitoring by adding definitions without having to restart application or JVM Comply Not Comply 6.12. Measurement of Response Time in components: The Software shall provide response time of individual backend server components, e.g. Servlet, JSPs, EJBs etc. Comply Not Comply 6.13. Exceptions Monitoring: The Software shall monitor any handled or unhandled J2EE exceptions/errors and produce error stack trace Comply Not Comply 6.14. SQL monitoring: The Software shall capture the SQL that trigger by user transactions and send to database Comply Not Comply 6.15. Performance analysis: The Software analyze performance issues on transaction, application and function level Comply Not Comply 6.16. Measurement of SQL execution time: The Software should be able to collect the SQL execution time Comply Not Comply
6.32. Command line tool: The Software shall support issue management command without graphical user interface Comply Not Comply 6.33. Availability Dashboard: The Software shall display different service availability (e.g. Web application) Comply Not Comply 6.34. Resource Dashboard: The Software shall provide views of different resources (e.g. memory and heap utilization) in real time Comply Not Comply 6.35. Socket and NIO monitoring: The Software must be able to identify socket and file (including Java NIO) activity from the application Comply Not Comply 6.36. Support EJB 3.0: The Software shall support EJB 3.0 and above Comply Not Comply 7. Mandatory: Middleware Management 7.1. Metrics monitoring: The Software shall provide detailed middleware metrics for robust monitoring and troubleshooting Comply Not Comply 7.2. SLA capabilities: The Software shall define and monitor SLA to meet the business expectation (performance & throughput) and monitor deviations from standards Comply Not Comply
8.10. Memory leak detection: The Software shall determine the potential memory leak and the size of the leak effortlessly Comply Not Comply 9. Mandatory: Database Management 9.1. Different database system monitoring: The Software shall monitor Oracle database, Sybase Database, Microsoft SQL Server and Access, Cache database Comply Not Comply 9.2. Performance monitoring: The Software shall provide detail performance and response time monitoring Comply Not Comply 9.3. Dashboard customization: The Software shall display real-time and historical KPI for trend analysis Comply Not Comply 9.4. SLA capabilities: The Software shall define and monitor SLA to meet the business expectation (performance & throughput) and monitor deviations from standards Comply Not Comply 9.5. and notification support: The Software trigger alerts based on “baseline” metrics performance and notification when thresholds are exceeded Comply Not Comply 9.6. Top problem analysis: The Software shall display top problems in the database (e.g. Top SQL) Comply Not Comply 10. Mandatory: APM Repository Management