transnet soc ltd contract number: 369 description of … · 2020-01-20 · transnet soc ltd...

TRANSNET SOC LTD CONTRACT NUMBER: 369 DESCRIPTION OF THE WORKS: CONFIGURATION AND TESTING OF SMART ELECTRICITY METERS & SUPPLY OF A SMART METERING ENERGY MANAGEMENT SOFTWARE SOLUTION AND MAINTENANCE AND SUPPORT FOR TRANSNET SOC LIMITED (REG. NO. 1990/000900/30) OPERATING AS TRANSNET PORT TERMINALS (HEREINAFTER REFERRED TO AS “TPT”), AT THE PORT OF DURBAN CONTAINER TERMINAL PIER 1 & 2, RICHARDS BAY, AGRI-BULK & MAYDON WHARF, DURBAN RORO, EAST LONDON, NGQURA, PORT ELIZABETH, SALDANHA AND CAPE TOWN TERMINALS, FOR THE PERIOD OF 3 YEARS.

Rev 0

T2.2 - 19 Eligibility

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Eligibility

Ref to Technical Evaluation No.

Reference Paragraph in Scope of Work

Item Comply (Yes/No) (Mandatory)

Evidence Required (Mandatory)

Comment (Mandatory)

1. 3.2.1 Is the smart electricity meters data validated in accordance with NRS049 (Advanced metering infrastructure for residential and commercial customer national regulation)

Required: Certification of Compliance

2. 3.4.4.1 The software solution is compatible (to interface and communicate) with IEC smart electricity meters, specifically: • Landis + Gyr E650, 3 Phase 4 Wire Meter ZMD405CT44.2407 S3 • Enermax E+MA – 454 000, 3 Phase Programmable Energy & Demand Meter • ISKRA MT830 and MT831 meters

Required: Letter of Compatibility

Mandatory Returnable


Rev 0

Proof of Experience (Configuration and Testing)

Proof of Experience (Systems)

Note to tenderers: A tenderer is required to demonstrate a track record of its experience in delivering similar works (minimum of 3 reference must be provided), and to this end shall supply – • A listing of marketplace (or similar) Configuration and Testing of smart electricity meters

(specifically configuration of all smart electricity meters for 4 quadrant power measurement, in order to measure regenerative power) that it (tenderer) has deployed, providing a brief description of each.

• For each of the Configurations and Testing of smart electricity meters (specifically configuration of all smart electricity meters for 4 quadrant power measurement, in order to measure regenerative power) indicated, sufficient reference details of the customer must be provided. Details to include:

o Customer name and contact details o Project description o Duration o Contract value

Note to tenderers: A tenderer is required to demonstrate a track record of its experience in delivering similar works (minimum of 3 reference must be provided), and to this end shall supply – • A listing of marketplace (or similar) Systems that it (tenderer) has deployed, providing a

brief description of each.

• For each of the Systems indicated, sufficient reference details of the customer must be provided. Details to include:

o Customer name and contact details o Project description o Duration o Contract value


Rev 0

Signed Name

Position

Date _______________________

Tenderer _______________________


Page 1 Rev 0

T2.2 – 20 System Functionality

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Compliance to Scope of Work – System Functionality

Ref to Tech Eval No.

Ref to SoW

No.

Item Comply (Y/N)

Comment (mandatory if non-compliant) and reference to returnable schedule

Main Characteristics 3.12.6 1. Does the system conform to GDPR and

POPI requirements?

3.12.6 2. Are all communication encrypted with latest standards (for example Transport Layer Security (TLS))?

Note to tenderers: ICT Systems are typically built up from collections of building blocks, where a building block is a package of functionality defined to meet a business need. In the interest of delivering the smart electricity solution timeously, the Employer's Programme seeks to leverage off solution components or solution building blocks that have already been deployed into the marketplace successfully. Key building blocks that the Employer is seeking to leverage include solutions in the marketplace that already cater for - * Smart Electricity Meter Data Process and Management * Billing & Finance * Reporting The service provider to indicate whether their existing solution/system has the below-mentioned characteristics/features and provides the below-mentioned functionalities.



Page 2 Rev 0

3.12.6 3. Are strong authentication mechanisms used (for example - Access Control/Passwords; No default credentials; Password Complexity (Password must have a minimal length, contain alphanumeric values, contain both upper and lower-case letters, and include special characters))?

3.12.6 4. Are audit trails of user authentication activity available (for example - User Log-Ons/Log-Offs, IP Addresses etc.)?

3.12.6 5. Is data stored in protected and encrypted databases?

3.12.6 6. Is data stored in protected and encrypted databases?

3.12.6 7. Are security patches are supplied and applied timeously (within 1 month of release)?

5 3.4.1.2

8. Is the system able to handle multiple geographic locations (for example across Southern Africa), hence is the software solution is scalable?

3.4.1.9 9. Can the system be configured by the users within the organisation that bought it, rather than having to revert to the service provider?

3.4.1.12 10.

Can data be extracted from the system for use by other systems and reporting?

3.12.6 11. Does the application security ensure that there are no segregation of duty conflicts?

3.4.1.18 12. Is user access integrated into Active Directory (where applicable)?

3.6.3.10 13. Are patches or updates applied without downtime - (for example, through clustering for 100% uptime)

3.4.1.19 14. Does the system have archiving ability?

2 15. Does the system enable a user to self-

manage their profile online?


Page 3 Rev 0

2 16. Does the system enable the online self-management of the accounts linked to a user's profile?

3.4.1.20

17. Does the system make use of mobile technology such as mobile phones (iOS, Android etc.)?

Smart Electricity Meter Data Process and Management Visualisation

5

3.4.2 18. Does the system perform accurate real time smart electricity meter data reading, capturing, monitoring, verification, analysis and storage of the data?

3.4.2 19. Does the system visualise accurate real time smart electricity meter data reading and live electricity consumption?

3.4.2 20. Does the system perform visualisation of energy data in concise graphs, tables and charts?

3.4.2 21. Does the system at a minimum visualise the following data: - Live kVA, PF, kVAr, KWh statistics; - Load profiles (indicating peak, standard and off peak hours); and - Energy consumption information as cost per kWh.

2 22. Does the system perform trend analysis on energy data, per smart electricity meter, per sites smart electricity meters, etc.?

Data Processing – EDI

5 3.4.5 23. Can the system handle (or other industry-recognised) format messages?

3.4.5 24. Is the solution able to handle new releases of standard message formats as they get formally revised over time?

3.4.5 25. Is the core system integrated (or interfaced) with 3rd party systems (via APIs for example)?

Document Storage/Archiving

5 3.6.4 26. Does the system store and archive documents?

3.6.4 27. Is version control included?


Page 4 Rev 0

Billing & Finance Tariff

5 3.4.2 28. How comprehensively is tariff analysis (calculation/capture/amendments) handled in the system?

29. Is the system configurable to the latest tariff structures applicable to the Terminal meters (mostly Incomers)

Billing 5 2 30. To what extent is bill verification handled

(calculated) in the system?

Reporting Management Information

5 3.5.2 31. Can data be extracted from the system for Data Warehousing purposes?

3.5.2 32. Can scheduled and ad-hoc Management reports be generated?

3.5.2 33. Are real-time and historical KPIs available?

Operational (Smart Electricity Meters) Information

5 3.5.1 34. To what extent does the system report on Operational (smart electricity meters readings/calculations/costs/consumption/disruptions/outages) information?

3.5.1 35. Can the system report on Operational (smart electricity metering readings/calculations/costs/consumption/disruptions/outages) per geographical site?

3.5.1 36. Does the system provide graphical information in regard to Node/POM Energy performance?

3.4.1 37. Can a user define/customise reports, rather than having to revert to the service provider?

Billing

5 3.5.1 38. To what extent does the system report on Billing and Finance information? Can a user/administrator create or modify report layouts?

3.5.1 Is it possible to produce reports in several formats? 39. a) printed copy


Page 5 Rev 0

40. b) pdf

41. c) csv, xlsx

42. d) xml

3.5.1 43. Does the system cater for audit reporting

requirements?

Signed Name Position Date

Tenderer _______________________


Page 1 Rev 0

T2.2 – 21 System Technology

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Compliance to Scope of Work – System Technology


Ref to SoW

No.

Item Comply (Y/N)


General 6 3.4.1.11 1. Has the service provider provided a system

Roadmap?

3.6.1.2 2. Is the system able to coexist with virus protection software?

3.4.1.1 3. Is the solution management of the system web based?

Note to tenderers: ICT Systems are typically built up from collections of building blocks, where a building block is a package of functionality and technology defined to meet a business need. In the interest of delivering the smart electricity meter solution timeously, the Employer's programme seeks to leverage off systems and technologies that have already been deployed into the marketplace successfully. Key building blocks that the Employer is seeking to leverage include solutions in the marketplace that are built on technologies that enable virtualisation, cloud deployment, mobile App operations; utilise secure methods of communication, and have a robust performance track record. The service provider to indicate whether their existing solution/system - • has been built on technologies that have the below-mentioned characteristics; • has the below-mentioned characteristics/features



Page 2 Rev 0

Training

6

3.9.7 4. Does the solution have a comprehensive “Help” facility, providing on-line assistance through popups, tool tips and similar methods?

3.9.7 5. Does the solution allow for this help text to be maintainable by Employer’s Super Users without the need to revert to the supplier?

Hardware Technology

6 3.6.2.4 6. Can the system/s run on VMware on prem?

3.6.2.1 7. Is the system (or component of the system) cloud

based?

3.6.2.1 8. Is the solution management of the system web based?

Software Technology

6 3.4.1.1 9. Is the system O/S agnostic?

3.6.3.2 10. Is the system database agnostic?

3.6.3.3 11. Do the system clients (end user) run on 64 bit

Windows 10 and above?

3.6.3.4 12. Do their systems support multi-monitor use?

3.6.3.5 13. To what extent do their systems integrate with MS

Office and Exchange 2010 where required?

3.6.3.6 14. Do their systems run on commonly used browsers (Safari, Firefox, Chrome, Explorer), at a minimum Microsoft Explorer 9 or above?

3.6.3.7 15. To what extent is user access role based?

Network 6 3.6.4.1 16. Does the solution support various network

protocols, including but not limited to IPv4 and TCP/IP?

3.6.4.1 17. Does the solution support network interfaces such as 10/100/1000 Ethernet?

3.6.4.1 18. Is the solution able to run under a virtualized network environment and accessible by two or more users?

Mobile Devices


Page 3 Rev 0

6 3.4.1.1 The system should be able to handle operations on any mobile device with a modern operating system (OS). Do the OS’s supported include (but not limited to):

19. Apple iOS 9 and above

20. Android 7.1 and above

3.4..1.1 21. To what extent have they developed mobile

(phone/tablet) apps with interfacing capability to back-end and other systems? (Android and iOS)

Technical Interfaces

6 3.6.6 22. Both internal and external interfaces ideally should be based upon industry-standard technologies. These standards (for example EDIINT) specify how to exchange business documents over the Internet in a secure, reliable, non-repudiable way, and support digital signatures, encryption, and signed receipts. Examples of secure protocols include SMTPS, HTTPS, FTPS, SFTP etc. Are such methods of interfacing used in your systems?

3.6.6 23. Does your system make use of, or supply secure web services?

3.6.6 24. Is the core system integrated (or interfaced) with internal, external, or 3rd party systems (via APIs for example)?

Performance

6 3.6.7.1 25. Does the system make data made available in real-time? In this context ‘real-time’ is defined as less than 15 seconds.

3.6.7.2 26. Does the system must support integration with Infrastructure Management & Monitoring Software for example (HP Intelligent Management Centre (IMC), Hyperic etc.) to provide the ability to monitor performance with real-time notifications. Notification types include, but not limited to:

a) Alerts for errors and warnings. b) Detection of critical situations such as the

retention of data in a queue. c) Monitoring of system processes.

3.6.7.2 27. Are system alerts available through a variety of mechanisms including, but not limited to, the following:

a) SNMP b) Web based monitoring portal


Page 4 Rev 0

c) Email d) SMS

3.6.7.4/5/6

28. Does the system provide audit trail functionality, showing at least the following elements when data is changed?

a) Information modifiers b) IP address c) Date and time of change d) Change made – original value – new

value

3.6.7.4/5/6

29. Does the system provide for the extraction and reporting of audit information?

3.6.7.7 30. Does the system have a high level of availability? For example, does it operate 24/7/365 with downtime events limited to no more than 15 minutes per occurrence?

3.6.7.8 31. Do you have a fast (less than 3 hours) and easy way to revert to a previous version of your solution or system component in the event of a failure after a system upgrade?

3.6.7.8 32. If any client hosted software is part of your solution, do you an automatic mechanism for the distribution of this software?

3.6.7.9 33. Is downtime for system restarts less than half an hour?

3.4.2.12 34. Is the system able to have multiple connectivity points (Wi-Fi/Ethernet/GSM)?

3.6.7.11 35. Is the solution fault tolerant to provide continued operation in the event of the failure of some of its components? In the case of network failure for example, does the solution reconnect seamlessly?

3.6.7.11 36. Is the solution fault tolerant to provide continued operation in the event of the failure of some of its components to ensure that in call cases, data is not lost?


Tenderer _______________________


Page 1 Rev 0

T2.2 - 22 Testing Strategy

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Compliance to Scope of Work – Testing Strategy


Ref to SoW

No.

Item Comply (Y/N)


Testing Strategy The service provider to submit a testing strategy that supports the following objectives:

7 3.7 1. Definition of testing approach for the smart electricity meters.

2. Definition of the testing approach for the software solution: Unit Testing, Data conversion testing, Integration Testing, Authorisation Testing, System Testing,

Note to tenderers: This testing strategy defines how the testing effort can be guided and controlled in such a way that resources are used in the most efficient way - to avoid overlapping work, to ensure that no crucial part of the individual project’s programs (Implementation, Integration, Infrastructure, Data Migration and Application Management & Support) are delivered untested, and to define what must be tested in each of the test phases. It also determines the tools and methods used to check that the system responds correctly, determines how and when the test will be performed and recommends how the approval process should occur. Testing should be considered and planned very early in an implementation project to setup additional tools (automated test tools), train the project team, and still have testing time to fit into the overall schedule.



Page 2 Rev 0

Load/Stress Testing, and User Acceptance Testing (UAT) and detailed descriptions thereof.

3. Define the activities required to prepare for and conduct testing and the sign-off from previous tests.

4. Definition of Testing Control Processes.

5. Definition of an approach for using Testing Tools.

6. Definition of an approach for using Issue Tracking system.

7. Define deliverables and responsible parties.

8. Presentation of the Testing Organisation and Roles & Responsibilities.

9. Communication to all responsible parties involved in all the Test phases (Unit, Integration and UAT).

10. Communicate to all responsible parties the various Dependencies and Risks.

11. Identify the required resources.

12. Define the training needs of the testing team.

13. Present the environments used in different testing phases.

14. Recommended review process for test plans, test cases and test results.

15. Inclusion of testing certification for the smart electricity meters testing.


Page 3 Rev 0


Tenderer _______________________


Page 1 Rev 0

T2.2 - 23 Training and Knowledge Transfer

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification.


Ref to SoW

No.

Item Comply (Y/N)


Training and Knowledge Transfer The service provider is to submit a sample of a deployed Knowledge Transfer and Training Plan that ideally addresses the following topics:

8 3.9 1. Knowledge Transfer and Training goals/standards and the specific plan for training technical personnel and end users.

2. Strategy for providing knowledge transfer and training early in the project to allow the training goals to be implemented throughout the project life cycle.

3. Tasks, deliverables and resources necessary to complete the knowledge transfer and training effort and identify tools and documentation that shall be

Note to tenderers: As part of the scope, the service provider shall develop and implement a Knowledge Transfer and Training Plan that describes the approach for bringing managers, end users, admin and technical personnel to a familiar level of understanding as to how the new system works.



Page 2 Rev 0

necessary to support proposed effort.

4. The different types of knowledge transfer and training, the specific courses and course materials, the training approach for both technical personnel and end users, and how training effectiveness shall be measured and addressed.

5. A description of deliverables to support initial and ongoing training including user manuals, system manuals, on-line help, and training materials for technical/non-technical personnel.

6. Knowledge Transfer to enable Employer personnel to operate, maintain, configure and modify the new systems including operation of the testing tools, supporting infrastructure, and security.

7. Metrics for tracking progress in achieving training and knowledge transfer objectives.

8. Reporting progress of training and knowledge transfer activities.

9. Approved recommendations for both training and knowledge transfer resulting from the organisational change readiness assessment.


Tenderer _______________________


Page 1 Rev 0

T2.2 - 24 Delivery Approach



Ref to SoW

No.

Item Comply (Y/N)


Delivery Approach

9

3.2.2 N/A The service provider to submit certifications (ISO, CMMI, IEEE) confirming the standards

Note to tenderers: Software product development, especially for larger software products, needs highly structured project management methodologies. The size and complexity of such projects typically require larger development teams. Oftentimes, to manage larger numbers, the product itself is broken down into many product components and the project team is divided into many smaller project teams; each team is responsible for the development of one product component. An informal and unstructured approach to manage complex projects or larger teams proves problematic. To manage such projects, a structured and well-defined process and project management is a must. The entire process should also be very formal. A formal, rigid, and structured approach prevents chances of miscommunication and errors. To facilitate such structures, organisations like the ISO, IEEE, and Software Engineering Institute at Carnegie Mellon University developed many process standards. These process standards define what process steps must be followed during planning and execution of projects. They also define how to keep improving the process so that better product quality and process productivity can be achieved continuously. On the other hand, on many projects, agility is required to take care of changing business requirements so that the software product being built takes these changes into its design instantly and fulfills the purpose for which it is being built. This concept is in direct contrast to the formal and rigid approach of a plan-driven methodology. Any software project must adjust itself between these two extremes. Depending on the requirements, it can be a purely plan driven project, a rather agile one, or something in between.



Page 2 Rev 0

it is guided by in the supply, development, operation and maintenance of computer software and related support services.

Alternatively, the service provider to detail its approach to: Project Management:

9 3.2.2 1. Project Management

a) Project Initiation Management b) Project Effort and Cost Estimation c) Risk Management d) Configuration Management e) Project Planning f) Project Monitoring and Control g) Project Closure

Software Life-Cycle Management:

9 3.2.2 2. Software Life-Cycle Management

Processes

3.2.2 3. Requirements Management

a) Software Requirements Development b) Software Requirements Management c) Requirement Life-Cycle Management d) Requirements Quality Control

3.2.2 4. Requirements Management

a) Software Requirements Development b) Software Requirements Management c) Requirement Life-Cycle Management d) Requirements Quality Control


Page 3 Rev 0

8 3.2.2 5. Software Design Management

a) Software Design Fundamentals b) Design Methods c) Design Version Control d) Design Techniques e) Design Quality control f) Design Life-Cycle Management

8 3.2.2 6. Software Construction

a) Coding Standards b) Coding Methods c) Reviews (Quality Control) d) Configuration Management e) Testing

8 3.2.2 7. Software Testing

a) Test Strategy and Planning b) Test Automation c) Testing Monitoring and Control d) Testing Organisation

8 3.2.2 8. Product Release & Maintenance

a) User Training b) Maintenance Types c) Maintenance Cost d) Maintenance Process e) Maintenance Life Cycle f) Maintenance Techniques

Software Engineering Management 8 3.2.2 9. Software Engineering Management:

Process Selection – Practical considerations for Plan-Driven vs Agile Methods


Page 4 Rev 0

Tools & Techniques

8 3.2.2 10. Project Management Tools

a) Configuration Management Tools b) Communication Management Tools

8 3.2.2 11. Software Life-Cycle Tools,

a) Software Design Management tools (e.g. CASE tools, modelling tools)

b) Software Build Management Tools (e.g. IDEs, Source Code Control tools, RAD etc.)

c) Software Testing Management Tools (e.g. Test Management, Defect Tracking, Automation tools)

8 3.2.2 12. Software Project Templates

a) Work breakdown structure b) Project planning c) Project Monitoring and Control


Tenderer _______________________


Page 1 Rev 0

T2.2 - 25 Support and Maintenance

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Compliance to Scope of Work – Support and Maintenance


Ref to SoW

No.

Item Comply (Y/N)


Service Level Agreement The service provider to a sample SLA’s that ideally comprises the following sections:

10 1. An introduction to the SLA, what does the agreement propose.

2. A Service description, what service the SLA supports and details of the service.

3. Mutual responsibilities, who’s responsible for what part of the service.

4. Scope of SLA.

Note to tenderers: A service level agreement (SLA) that formally documents and defines the working relationship between the Employer and Service Provider is required. The SLA will provide a measurable framework that will govern the support and maintenance of the solution once it has been deployed.



Page 2 Rev 0

5. Applicable service hours, from what time till what time is the service available according to the agreement.

6. Service availability, how much is the service available during the service window and outside of service window.

7. Reliability.

8. Customer support arrangements.

9. Contact points and escalation; a communication matrix.

10. Service performance.

11. Security.

12. Costs and charging method used.

13. Is 24/7/365 support available from the supplier?

14. Can they take snapshots of their systems?


Tenderer _______________________


Page 1 Rev 0

T2.2 - 26 Quality Assurance

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Quality Assurance


Ref to SoW

No.

Item Comply (Y/N)


Quality Assurance

The service provider to submit a Quality Management Plan (QMP) that supports the following objectives:

11 3.2.2 1. Define Quality Management Plan objectives;

2. Define Quality Management Plan principles;

3. Define Quality Management Plan roles and responsibilities;

4. Define Quality Management Plan processes, tools & suggested metrics for:

a) Quality Assurance. b) Quality Control. c) Quality Improvement.

Note to tenderers: The purpose of the Quality Management Plan is to define the objectives, processes, tools and roles and responsibilities required to implement an effective quality management program.



Page 2 Rev 0


Tenderer _______________________


Page 1 Rev 0

T2.2 - 27 Guarantees and Warrantees

Note that this schedule is cross-referenced and must be read in conjunction with the Technical Scorecard (Part T1) & Scope of Work (Part C3). Elements of this document not completed will be deemed as non-compliance to that particular clause. The Tenderer's sign-off at the bottom is deemed as confirmation that this document has been read in conjunction with the Technical Specification. Should the service provider provide warrantees and guarantees per item (configuration, testing and software solution). The points will be allocated according to the specified scoring principal per line item and the total will be averaged to determine the final points.


Tenderer _______________________

Note to tenderers: Service Provider will be required to meet an agreed upon guarantees’/warrantees’ time for the project. Configuration of Smart Electricity Meters Guarantees and Warrantees Y/N < 1 Month 0 points >or = 1 Month but < 3 Months 4 point >or = 3 Months but < 6 Months 8 points > or = 6 Months 10 points

Testing of Smart Electricity Meters Guarantees and Warrantees Y/N < 1 Month 0 points >or = 1 Month but < 3 Months 4 point >or = 3 Months but < 6 Months 8 points > or = 6 Months 10 points

Software Solution Guarantees and Warrantees Y/N < 1 Month 0 points >or = 1 Month but < 3 Months 4 point >or = 3 Months but < 6 Months 8 points > or = 6 Months 10 points



Page 2 Rev 0

Signed Name Position

Date _____________________

Tenderer _______________________


Page 1 Rev 0

T2.2 - 28 Lead Time



Tenderer _______________________

Signed Date

Name Position

Tenderer

Note to tenderers: Service Provider will be required to meet an agreed upon lead time for the project execution Lead time for Configuration and Testing Smart Electricity Meters, and detailed specification, development, supply, deployment, configuration, training, full testing and implementation of the solution in a production environment. Lead Time Y/N <3 Months 10 points = or > 3 Months but < 6 Months = 7 points 7 points

= or > 6 Months but < 9 Months 4 points >9 Months 0 points


transnet soc ltd contract number: 369 description of … · 2020-01-20 · transnet soc ltd...

Documents