PROPOSAL APPROACH AND RESPONDENT … · Web viewDescribe how the OMS system will trace network outages, group related outage events and calculate the outage impact. 3.1.3 Describe

Annexure L: RESPONDENT QUESTIONNAIRE

The following questionnaire must be completed and attached to the Respondent’s proposal. Responses to the questions should state the question number and repeat the question, and can consist simply of references to specific sections in the body of the Respondent’s proposal, where applicable. Any question which is based on a system’s size or configuration should be answered separately for each distinct system size or configuration being offered in the Respondent’s proposal. The answer to any such repeated question should unambiguously indicate to which system size or configuration it refers.

The information contained in reply to this questionnaire shall be contractually binding.

The sections below have a similar structure to the evaluation criteria, but there isn’t necessarily a one-to-one correlation between the evaluation criteria and the questions.

Where the same question is repeated under different headings, the Respondent may provide a reference to an earlier identical reply.

Questionnaire outline:

PROPOSAL APPROACH AND RESPONDENT COMPANY INFORMATION.................................................2

PROJECT MANAGEMENT.............................................................................................................................. 2

Approach to Project Management................................................................................................................. 2

Project Plan/Schedule................................................................................................................................... 3

Project Management Resources................................................................................................................... 3

SERVICE DELIVERY SPECIFICATION (SDS)................................................................................................3

Functional Capabilities: Create Outage Events.............................................................................................3

Functional Capabilities: Visualise Outages...................................................................................................4

Functional Capabilities: Calculate Outage Impact.........................................................................................4

Functional Capabilities: Dispatch and Manage Outages...............................................................................4

Functional Capabilities: Notify Customers via Contact Centre......................................................................5

Functional Capabilities: Report on Outages, Performance Management and Investigations........................5

Functional Capabilities: Mobile Outage Management...................................................................................5

Functional Capabilities: Training Simulator...................................................................................................5

Functional Capabilities: Create, Maintain and Display the Network Model...................................................5

Functional Capabilities: Data Acquisition and Data Exchange......................................................................7

Functional Capabilities: Create, Maintain and Display the SCADA Model....................................................7

Functional Capabilities: Analyze and Optimize SCADA Data.......................................................................8

Functional Capabilities: Operate, Analyze and Optimize the Network..........................................................8

Functional Capabilities: Monitoring, Visualisation and Reporting of the Power System, Control System and SCADA System Operating State, Health and Performance..........................................................................9

Functional Capabilities: Operator Training Simulator....................................................................................9

Functional Capabilities: Analyze Historical Data...........................................................................................9

Functional Capabilities: Intranet User Access.............................................................................................10

Functional Capabilities: System Monitoring and Configuration...................................................................10

Architecture................................................................................................................................................. 13

Interoperability (Integration)........................................................................................................................13

Data............................................................................................................................................................ 13

Performance............................................................................................................................................... 14

SOFTWARE PRODUCT AND SERVICE PROVIDER INFORMATION..........................................................14

Page 1 of 20 Revision 1

References.................................................................................................................................................. 14

OMS Software Vendor Information.............................................................................................................14

OMS Software Vendor Product Software Development Approach..............................................................14

Product Support and Maintenance Approach.............................................................................................15

Respondent’s OMS Product Implementation History..................................................................................15

Respondent’s Current Workload and OMS Implementation Capabilities....................................................16

Resources and Experience.........................................................................................................................16

Customer Documentation........................................................................................................................... 16

Approach to Product Installation................................................................................................................. 16

PROPOSAL APPROACH AND RESPONDENT COMPANY INFORMATION

1. Proposal Approach

Describe the approach your proposal adopts regarding the scope of supply/services, for example: are all aspects of your proposed solution based on an in-house OMS product and resources? Are you the OMS Software Vendor planning on out-sourcing the implementation aspects? Are you a system integrator performing the implementation utilising a third-party OMS product? Clearly describe the relationship between various parties involved, as well as scope and accountabilities assigned to each.

2. Respondent Company Information

Item Scope Reference

Description

2.1 Respondent Company Overview and History

2.1.1 Provide an overview of your company and its history.

2.2 Respondent Organisational Structure

2.2.1 Provide a description of your company organisational structure.

PROJECT MANAGEMENT

3. Project Management

Item Reference Description

3.1 Approach to Project Management

3.1.1 Describe the management methods used to control the timely completion of each milestone of the project.Will a formal recognised project management methodology be adhered to? Describe, with details (e.g. PMBOK).

3.1.2 Describe the tools and templates to be utilised to address work definition, progress monitoring, reporting, risk management and configuration management.


3.1.3 Describe the manpower commitment of the Employer recommended for the timely completion of the project.

3.2 Project Plan/Schedule

3.2.1 Describe your estimates for the duration and completion of all project activities.

3.2.2 Describe the milestones and deliverables associated with each activity above.

3.2.3 Describe what factors or requirements in the Invitation have the greatest risk of affecting the timely delivery of the system.

3.2.4 Describe the various tests that are performed before the system is implemented.

3.2.5 Describe the Employer inputs related to any of the activities above.

3.3 Project Management Resources

3.3.1 Provide the particulars of the proposed project manager, including qualifications and experience on projects of similar size and complexity.

3.3.2 Provide the particulars of other proposed project management related resources, including qualifications and experience on projects of similar size and complexity.

3.3.3 Describe where project management resources will be located for the duration of the project.

SERVICE DELIVERY SPECIFICATION (SDS)

4. SDS: OMS Functional Capabilities

Describe how the following functionality is achieved in the proposed OMS Solution. Functionality includes both the ability to perform a specific function and the manner in which the function is performed i.e. the business related operational impact.


Description

4.1 Functional Capabilities: Create Outage Events

4.1.1 3.1.1.1 Describe the interface with the DMS / SCADA systems in the Eskom NMCs and how an outage event will be initiated in the OMS, including details of the automatic capturing of events and the user interface for the NMC Controller to manually process a SCADA event.

4.1.2 3.1.1.1 Describe the interface with the CRM systems used in the Eskom Contact Centres and how an outage event will be initiated in the OMS, including details of the system interfaces and the user interface available to the contact centre agents.


4.1.3 3.1.1.2 Describe the interface with Maximo to process scheduled planned outages and the user interface available to the Outage Scheduler in the NMC to process planned outages.

4.1.4 3.1.1.2 Describe how the Outage Scheduler in the NMC will manage and approve planned outages.

4.1.5 3.1.1.3 Describe how the load shed schedules will be maintained and processed in the OMS and the user interface available to the NetOps personnel and NMC Controller.

4.2 Functional Capabilities: Visualise Outages

4.2.1 3.1.2 Describe the functional capabilities and user interface available to the Dispatchers and how outages and field crew locations will be visualised (“list” and “geo-spatial” views) and processed.

4.2.2 3.1.2 Describe the functional capabilities and user interface available to the Contact Centre Agents and how outages will be visualised (“list” view and “geo-spatial” view).

4.2.3 3.1.2 Describe the functional capabilities and user interface available to the NMC Agents and how schematic diagrams and outages will be visualised (“list” view and “geo-spatial” view).

4.3 Functional Capabilities: Calculate Outage Impact

4.3.1 3.1.3 Describe how the OMS system will trace network outages, group related outage events and calculate the outage impact.

4.3.2 3.1.3 Describe how the user can manually trace the customers that are affected by an outage and/or from a marker on the geo-spatial view.

4.3.3 3.1.3.5 Describe how the operator will prioritise forced outages

4.4 Functional Capabilities: Dispatch and Manage Outages

4.4.1 3.1.4 Describe how the Dispatchers will manage outages and dispatch resources with details of the user interface and a description of each functional capability required. This should include details of:

- How to manually group / ungroup outages- How to assign labour to an outage- How the work order is created in Maximo- How standby shifts and resource authorisations will be managed- How restoration progress will be updated and monitored- How to prioritise between events


4.4.2 3.1.4 Describe the interface with Maximo and define the work flow to initiate Work Orders in Maximo.

4.4.3 3.1.4.8 Describe how non-outage related dispatching events (e.g. urgent reconnections following disconnections) can be dispatched through the Services.

4.4.4 3.1.4.63.1.4.7

Describe how planned outages will be managed by the Scheduler and the NMC controller

4.5 Functional Capabilities: Notify Customers via Contact Centre

4.5.1 3.1.5 Describe the interface to the CRM systems and how Contact Centre Agents will be able to trace outage restoration progress and inform customers via campaigns through the CRM.

4.5.2 3.1.5.2 Describe the automated customer notifications

4.6 Functional Capabilities: Report on Outages, Performance Management and Investigations

4.6.1 3.1.6 Describe how the OMS will support and calculate all the required performance indices / KPIs, list all the KPI reports that will be available, and describe the data dependencies.

4.6.2 3.1.6 Describe the flash reports, performance dashboards, heat map displays and crew performance reports that will be available.

4.6.3 3.1.1.43.1.6.5

Describe how a Control Plant incident event (i.e. protection or telecommunication events) will be managed through the investigation process and accounted for in the KPIs.

4.6.4 3.1.13.1.6

Describe how the quality assurance processing will be managed to validate events and KPI measures.

4.7 Functional Capabilities: Mobile Outage Management

4.7.1 3.1.7 Describe your Mobile App provided and the interface with Eskom’s mobility platform and the mobile outage management capabilities provided.

4.7.2

Describe the hardware and software (Android / iOS) requirements for any mobile applications and clarify the scope included with your Services. Indicate how your mobile solution works in offline conditions (out-of-coverage)

4.8 Functional Capabilities: Training Simulator

4.8.1 3.1.8 Describe the capabilities of the OMS Training simulator


5. SDS: ADMS Functional Capabilities

Describe how the following functionality is achieved in the proposed DMS/SCAD Solution and in the integrated ADMS end-state solution The functionality includes both the ability to perform a specific function and the manner in which the function is performed.

5.1 Functional Capabilities: Create, Maintain and Display the Network Model

5.1.1 6.1.1.1 To6.1.1.14

Describe in general how the network model (i.e. network data and diagrams/schematics) is developed and maintained for the ADMS and what tools are available to assist the data administrator.

5.1.2 6.1.1.1 What IEC standards and standard CIM formats are supported for exchange of network data, SCADA data and/or market data (e.g. IEC61970, IEC61968)

5.1.3 6.1.1.1 Describe whether the system provides support for customized CIM profiles?

5.1.4 6.1.1.1 Describe how the system supports bulk import and/or export of network data and diagrams and/or schematics.

5.1.5 6.1.1.16.1.1.5

Describe how the system supports incremental updates on network data and diagrams/schematics and the recommended approach to perform these on the system.

5.1.6 6.1.1.5 Describe the process of modelling a portion of a network and how the network model should be maintained for the entire lifecycle (i.e. planned network, getting network ready for commissioning, commissioning network, getting network ready for decommissioning, decommissioning network, dismantling network etc.)

5.1.7 6.1.1.2 Describe the interfaces and/or services that are supported for network data exchange (e.g. web services such as SOAP, UDDI, WSDL and/or other HTTP services, WCF)

5.1.8 6.1.1.2 Does the system provide any OOTB APIs that can be used for data exchange? Describe the functions that these APIs may offer.

5.1.9 6.1.1.3 Does the system provide OOTB integration with a Geographical Information System (GIS)? Describe the integration that is provided and any prerequisites to configure such integration. Describe the limitations (if any) of the integration offered OOTB.

5.1.10 6.1.1.4 Does the system provide OOTB integration with any of the other systems listed in the SDS (section 6.1.1.4). Describe the integration provided and any prerequisites to configure such integration. Describe the limitations (if any) of the integration offered.

5.1.11 6.1.1.5 Describe the various tools and methods that the system provides for Quality Assurance of network data and associated diagrams/schematics.

5.1.12 6.1.1.5 Describe the processes and/or tools that provide version control of diagrams / schematics.


5.1.13 6.1.1.6 Describe the various tools available to create, maintain and display schematics for substations, Single-Line-Diagrams and overview diagrams for LV, MV and HV networks.

5.1.14 6.1.1.7 Describe how network schematics are linked to the network and SCADA data.

5.1.15 6.1.1.6 Describe what symbols are available to display electrical networks and how these symbols may be customized and/or how additional symbols may be added.

5.1.16 6.1.1.86.1.1.9

Describe in general what network devices are supported by the ADMS (e.g. lines, transformers etc.) and what simplified models are used for non-supported devices (e.g. lines used to model Current Transformers or similar)

5.1.17 6.1.1.86.1.1.9

Provide the minimum data requirements for the various functions provided by the ADMS and describe the interdependencies of the various modules.

5.1.18 6.1.1.86.1.1.9

Describe in general the electrical model used for the advanced functions in terms of the model complexity (e.g. simplifying assumptions) for the various equipment types (e.g. lines, transformers etc.).

5.1.19 6.1.1.86.1.1.9

Describe the zero-sequence equivalent models used for the various equipment types

5.1.20 6.1.1.86.1.1.9

Are voltage regulation setpoints and dead-bands considered by the various functions (e.g. state estimation, load flow etc.) for devices such as shunt compensators, tap changers, voltage regulators etc. and do these models support reactive power control, power factor control and voltage control modes.

5.1.21 6.1.1.86.1.1.9

Does the network model consider transformer vector groups and are phase shifting transformers supported?

5.1.22 6.1.1.86.1.1.9

Does the network model consider voltage dependency of loads and frequency dependency of loads?

5.1.23 6.1.1.86.1.1.9

Does the system provide support for the consideration of dynamic line ratings? Describe the data requirements for this feature and how these are calculated.

5.1.24 6.1.1.126.1.1.136.1.1.14

Describe the interdependency of the functions offered by the OMS on the DMS functions and/or data and vice versa (i.e. is there a dependency on switch order management for some of the OMS functions and do some DMS functions require OMS functions to work?)

5.2 Functional Capabilities: Data Acquisition and Data Exchange

5.2.1 6.1.2.1 To6.1.2.6

Describe in general the features offered by the Front-End system and the support offered for the various communication protocols.

5.2.2 6.1.2.1 Describe any support offered for high availability telecommunications methods (e.g. Parallel Redundant Protocol) on both serial and Ethernet ports

5.2.3 6.1.2.1 Describe any Data Concentrator functionality available in the front-end system that would for example allow multiple RTU I/O to appear as the I/O of a single virtual RTU.


5.2.4 6.1.2.5 Describe in detail the OOTB real-time data exchange capabilities and associated configuration and management tools provided

5.3 Functional Capabilities: Create, Maintain and Display the SCADA Model

5.3.1 6.1.3.1To6.1.3.7

Describe in general how the SCADA model is developed and maintained for the ADMS and what tools are available to assist the data administrator.

5.3.2 6.1.3.2 Describe any functionality offered for intelligent / adaptive polling of RTUs

5.3.3 6.1.3.26.1.3.5

Describe how the SCADA model is linked to the network model and represented on diagrams/schematics? What tools are available to the data administrator to maintain this model?

5.3.4 6.1.3.3 Describe in general how derived and calculated data points can be defined and maintained on the system? What arithmetic, logical and conditional operands are available to be used? Are any programming languages available?

5.3.5 6.1.3.4 Are there any limitations on the amount of calculations that can be defined for a particular object and/or for the system in total?

5.3.6 6.1.3.6 Describe in general how events are configured in the ADMS and what features are available

5.3.7 6.1.3.7 Describe in general how alarms are configured in the ADMS and what features are available

5.3.8 6.1.3.7 How many alarm limits can be configured per measurement?

5.3.9 6.1.3.7 Does the alarm limit manager support seasonality variations (i.e. different limits per season / time of year)

5.4 Functional Capabilities: Analyze and Optimize SCADA Data

5.4.1 6.1.4.1 To 6.1.4.3

Describe in general the features offered by the ADMS to monitor and manage real-time SCADA data and to report on the performance of the system.

5.4.2 6.1.4.1 Describe reporting capabilities offered on accuracy and integrity of SCADA data (e.g. reporting on quiet RTUs / telemetered points, control success rate, breakers/isolators stuck in transit, bandwidth usage of specific communication lines, RTUs not responding to polls etc.)

5.4.3 6.1.4.1 Describe the functions and metrics available to check quality of SCADA data and what actions the system may take when these checks fail (e.g. limit checking, plausibility checks, completeness checks etc.)

5.5 Functional Capabilities: Operate, Analyze and Optimize the Network

5.5.1 6.1.5.16.1.5.26.1.5.7

Describe in general the features that are available to display alarms / incidents to the Controller in such a way as to improve his situational awareness


5.5.2 6.1.5.3 Are there any limitations on the amount of tags that can be applied per object and/or in total for the system?

5.5.3 6.1.5.4 Describe in general the various ways in which a Controller can operate a device via the ADMS (e.g. from diagrams, from event lists, from composite command windows etc.)

5.5.4 6.1.5.5 Describe in general the features offered by the ADMS for mobility integration and the various safety and cyber-security mechanisms that are included.

5.5.5 6.1.5.6 Describe the process of placing a temporary device in the ADMS and the various features offered to place, track, report on and remove these temporary devices. Describe how these temporary devices affect other calculations and functions within the ADMS.

5.5.6 6.1.5.7 Describe in general the user interface features offered to the Controller to navigate between networks, SCADA data and results from ADMS modules.

5.5.7 6.1.5.146.1.5.15

Describe in general the features offered for the forecasting of loading and generation for a given network.

5.5.8 6.1.5.18 Describe the various features available to the Controller to red-line and yellow-line diagrams and capture discrepancies on network data as reported from the field.

5.5.9 6.1.5.8To 6.1.5.26

Describe in general the various ways in which the results of the advanced functions are displayed to the Controller and how it can be used to make informed decisions.

5.5.10 6.1.5.8To6.1.5.26

Describe the robustness of the advanced functions to typical problems found in modelling of real-world systems. Can the system handle zero-impedance meshes? Are the advanced functions affected in terms of accuracy and/or performance when evaluating networks with a large amount of small impedance lines (e.g. large MV networks)? Is the system capable of solving only portions of the network that are observable?

5.5.11 6.1.5.8To6.1.5.26

Describe how the advanced functions are configured and what tools are available to continuously monitor their performance and/or accuracy?

5.5.12 6.1.5.166.1.5.176.1.5.196.1.5.206.1.5.236.1.5.24

Describe the various objective functions available for each of the optimization functions (e.g. FLISR, Contingency Analysis, VVO etc.)

5.5.13 6.1.5.12 How does the system handle the failure of a command during an automatic switching sequence?

5.5.14 6.1.5.19 Describe how the FLISR module evaluates equipment as faulted, faultless and/or suspicious and how this is shown to the controller.

5.6 Functional Capabilities: Monitoring, Visualisation and Reporting of the Power System, Control System and SCADA System Operating State, Health and Performance


5.6.1 6.1.6.1 To 6.1.6.3

Describe in general the various dashboards and reporting features offered by the ADMS on the overall power system, control system and SCADA system operating state, health and performance.

5.7 Functional Capabilities: Operator Training Simulator

5.7.1 6.1.7.1 To 6.1.7.4

Describe in general the features offered by the Operator Training Simulator

5.7.2 6.1.7.1 To 6.1.7.4

Describe how scenarios are set up and managed for the Operator Training Simulator and what tools are available to assist with this.

5.7.3 6.1.7.1 To 6.1.7.4

Describe which functions are available in the Operator Training Simulator and the minimum requirements to get them operational in the simulator.

5.8 Functional Capabilities: Analyze Historical Data

5.8.1 6.1.8.1To6.1.8.8

Describe in general the features offered by the Operational Historian, how it is configured and how the data can be extracted from it.

5.8.2 6.1.8.1 Describe whether it would be possible to integrate the ADMS with the Wonderware eDNA Enterprise Historian. Describe the requirements to achieve this integration and any limitations in terms of what data would be available to the Enterprise Historian.

5.8.3 6.1.8.3 Describe the various configuration options available on how data should be stored (i.e. retention periods, snapshots, store on change etc.)

5.8.4 6.1.8.4 Describe in detail the various ways in which data can be extracted from the Operational Historian (e.g. time-range, snapshots, APIs etc.)

5.8.5 6.1.8.5 Describe the tools available to archive and restore data to and from the Operational Historian

5.8.6 6.1.8.66.1.8.7

Describe the features available in the ADMS from the data stored in the Operational Historian (e.g. Post Disturbance Review functions, saving snapshots for later analysis etc.)

5.9 Functional Capabilities: Intranet User Access

5.9.1 6.1.9 Describe in general the various ways in which users on the Eskom Intranet may be able to securely access the various DMS applications.

5.10 Functional Capabilities: System Monitoring and Configuration

5.10.1 6.1.10 Describe in general the tools available to monitor the ADMS system processes and health.

6. SDS: Non-functional Requirements: OMS Services


Describe how the following non-functional requirements will be met.


Description

6.1 Architecture

6.1.1 Describe your Service solution architecture. Indicate all the components of the system with details of the location of the hosting; centralised and de-centralised (regional) components; redundancy of components and indicate all interfaces and integration paths with existing Eskom systems.

6.1.2 Describe the thin/thick client architecture of the OMS terminals and define the minimum hardware and operating system requirements for the OMS workstations in the Resource Management Centres (Dispatchers and Supervisors), Contact Centres (Agents and Supervisors), Network Management Centres (Controllers and Outage Schedulers) and other users. (Refer to Appendix 4).

6.1.3 Describe the telecommunications latency and bandwidth requirements between the core system and the regional offices in order to meet the User Experience performance requirements listed in section X.Y.Z

6.1.4

Noting that Eskom uses the DMS for sub-transmission (HV) and distribution (MV) visibility, describe how the OMS Service will cater for HV, MV and future LV visibility.

6.1.5

Noting the reporting and work flow requirements stated in section 3.1.6, described all the Services and/or capabilities which are not OOTB (Out-of-the-box) and will required customisation to meet Eskom requirements

6.1.6

Noting that the Services must be inclusive of all infrastructure, software and licences required, list any exclusions which will not be provided as part of the Services offered (note: Ideally this should be zero). Indicate any existing Eskom licences which will be utilized.

6.2 Interoperability (Integration)

6.2.1 Described all the integrations (information flows) that you have provided for between the Services offered and the existing Eskom systems. Clearly indicate the point-of-interface of the Supplier / Eskom responsibility and the type of connection.The following interfaces must be described in detail as a minimum including details of the synchronisation of information sources:

Network Information System (SmallWorld) and how the Network Model will be established and maintained in the OMS.

Eskom Maximo system Eskom DMS / SCADA systems in each region Eskom Mobility system Eskom Contact Centres (CC&I) Eskom Customer to Network Link (CNL) Eskom MDMS

6.3 Data


6.3.1

Describe your data structures (models) that are relevant to the integration with Eskom systems.

6.3.2

Describe all the data dependencies and indicate if there are any known gaps in Eskom’s data which will affect your Services.

6.3.3

Indicate your previous experience with data migration involving similar scope and technologies to Eskom, with special reference to network data (Smallworld source), CNL, work management /work order data (Maximo), CRM data (Kana), SCADA/DMS event data (GE and ABB Network Manager).Provide details regarding migrations performed successfully.

6.3.4

Described how extendable your data model is for configuration and customisation and how this is done. List and describe the expected changes.

6.3.5

Describe how the Services will perform the outage analysis / tracing function and the data dependencies on the Network Model, real-time SCADA data and others.

6.3.6

Describe how the real-time network visibility (from Eskom DMS / SCADA systems) will be interfaced with the OMS Service. Clearly indicate the data dependencies and any modelling required.

6.3.7

Describe how visibility of an outage event from a Smart Meter (from MDMS) will be integrated and considered in the outage analysis / tracing function. Indicate any data dependency and clarify the scope of the Services offered. (Refer to section 3.1.1)

6.3.8

Describe how visibility of an outage event from a Smart Meter Data Concentrator (situated at the MV/LV transformer and obtained via the MDMS) will be interfaced with the DMS so that it can be used by the DMS FLISR tool. Indicate any data dependency and clarify the scope of the Services offered. (Refer to section 3.1.1)

6.4 Infrastructure Provision Requirements

6.4.1 1.6.1 Reference is made to the provision of the Infrastructure for the OMS implementation Option B (i.e. the solution implemented on infrastructure delivered as Infrastructure-as-a-Service) which Eskom may choose to provide to the Respondent from the “Eskom Hybrid IT infrastructure provider”.

Define all the infrastructure requirements (i.e. servers, VMs, network, OS etc.) that Eskom has to provide if the option to provide IaaS by the Respondent is not selected (i.e. Eskom to provide the required Infrastructure).

6.5 Network Communication

6.5.1 Provide details of the internal Eskom network bandwidth and external Internet bandwidth to access cloud services that is required by each type of user. (Refer to section 3.3.1.1). Indicate the minimum and typical bandwidth required under various uses and provide a calculation of the total bandwidth required to each Operating Unit (OU) / site considering the number of users and diversity factor.

6.6 Security


6.6.1 Describe how you manage system security across all layers of the solution.

6.7 Performance

6.7.1 Describe the expected and guaranteed availability of the Services. Indicate each group of capabilities with different availability separately and provide substantiating calculations.

6.7.2 Considering the network bandwidth requirements stipulated above, describe the expected and guaranteed performance of the OMS terminals deployed in the following areas:

- Resource Management Centres (RMC)- Network Management Centres (NMC)- Contact Centres

Indicated the expected and worst-case delays to perform specific tasks.

6.8 Client Workstations

6.8.1 5.2.5.3 Specify the minimum hardware and operating system requirements for the OMS workstations in the Resource Management Centres (Dispatchers and Supervisors), Contact Centres (Agents and Supervisors), Network Management Centres (Controllers and Outage Schedulers) and for other users.

7. SDS: Non-functional Requirements: ADMS Solution

Describe how the following non-functional requirements will be met using your product solution when Eskom in future (as a next step) evolves to an integrated ADMS end-state solution.


Description

7.1 Architecture

7.1.1 Describe your solution architecture for a future integrated ADMS end-state solution for all Eskom NMC sites as described considering the OT resilience requirements. Indicate all the components of the system that will be centralised and de-centralised (regional); redundancy of components and indicate all interfaces and integration paths with existing Eskom systems.

7.1.2

Describe the roadmap to evolve from the point of having the OMS Services active to the end-state ADMS solution. Include details of how the OMS Services contract will be affected and your proposed strategy.

7.1.3

Describe the strategy to migrate the existing Eskom DMS systems to the ADMS end state described.

7.1.4 Describe the thin/thick client architecture of the DMS terminals and define the minimum hardware and operating system requirements for the various types of DMS workstations in the Network Management Centres and other users.


7.1.5 Describe the telecommunications latency and bandwidth requirements between various Eskom sites (i.e. between centralized and decentralised / regional offices.

7.1.6

Noting that Eskom uses the DMS for sub-transmission (HV) and distribution (MV) visibility, describe how the DMS will cater for HV, MV and future LV visibility.

7.2 Interoperability (Integration)

7.2.1 Described all the additional integrations (information flows) that will be established with implementation of an ADMS Solution (Refer to question 6.2.1). Clearly indicate the point-of-interface of the Supplier / Eskom responsibility and the type of connection.All interfaces required in addition to the interfaces addressed in question 6.2.1 must be described in detail including details of the synchronisation of information sources.

7.3 Data

7.3.1

Describe your data structures (models) that are relevant to the integration with Eskom systems.

7.3.2

Describe all the data dependencies and indicate if there are any known gaps in Eskom’s data which will affect your Services.

7.3.3

Indicate your previous experience with data migration involving similar scope and technologies to Eskom, with special reference to GE Power-On and ABB Network Manager SCADA/DMS and Smallworld as Network Information System.Provide details regarding migrations performed successfully.

7.3.4

Describe how visibility of an outage event from a Smart Meter Data Concentrator (situated at the MV/LV transformer and obtained via the MDMS) will be interfaced with the ADMS so that it can be used by the DMS FLISR tool. Indicate any data dependency and clarify the scope of the Services offered. (Refer to section 3.1.1)

7.4 Performance

7.4.1 Describe the expected and guaranteed availability of the platform based on your architecture proposed. Indicate each function with different availability separately and provide substantiating calculations.

SOFTWARE PRODUCT AND SERVICE PROVIDER INFORMATION

8. Software Vendor / Product Viability

Note: Software Vendor refers to a commercial organization that acquires or develops software to sell/license to end users.



Description

8.1 References

8.1.1 Provide a list of all OMS installations utilising the product offered. Provide the following details for each installation:

Customer details, including contact persons (contact names, positions and telephone numbers).

Implementation area, e.g. power generation (specify coal, nuclear, renewables, etc.), power delivery (transmission, sub-transmission and distribution), etc.

Hardware/software configurations. Functional modules in operation. System sizing information. Maintenance and support arrangements in place.

8.1.2 Highlight the details of the 5 largest OMS implementations listed in the question above.

8.2 OMS Software Vendor Information


8.2.1 Provide a description of the OMS Software Vendor company history.

8.2.2 Provide a description of the OMS Software Vendor company organisational structure.

8.2.3 Provide a description of the history of the proposed OMS software.

8.2.4 Describe your position as industry leaders in the OMS software field and provide a view of the industry standing of the proposed OMS product.

8.3 OMS Software Vendor Product Software Development Approach

8.3.1 Describe your approach to Quality Assurance and the methods of ensuring that the OMS proprietary software, that is ready for customer delivery, has been quality assured and tested.

8.3.2 Describe the level of adherence to international software engineering standards, and cite the standards where referenced.

8.4 Resources and Experience

8.4.1 Describe the nature of the resources with respect to OMS software development, including resources based in the Republic of South Africa (e.g. staff compliment, development facilities, test environments, etc.).

8.5 Approach to Product Development

8.5.1 Describe the OMS development facilities.

8.5.2 Provide a list of all standards used in the system.

8.5.3 Describe the software standards for code production and the level of adherence to international standards. List the programming languages that are used.

8.5.4 Describe the envisaged OMS product plan for the next ten years.

8.5.5 Describe the functioning of the User Group and its influence on the product development. Provide a copy of the minutes of the most recent meeting.

8.5.6 Describe associated products envisaged for development, which may impact on the OMS environment.

8.6 Software Development Tools

8.6.1 Describe the software “debugging” tools that are provided with the system.

8.6.2 Describe the change management systems provided.


8.7 Approach to Product Testing

8.7.1 Describe the formal approach to verification and validation during development of products, as well as integration of systems.

8.8 Product Support and Maintenance Approach

8.8.1

Describe your approach to support and maintenance and the methods of ensuring that the Services will meet the specified requirements.

8.8.2

Describe the support and maintenance capabilities based locally and internationally that will manage the Services and confirm the response times for the various activities.

9. Service Provider / Proposal Suitability: Design / Build / Test / Deploy


Description

9.1 Respondent’s OMS Product Implementation History

9.1.1 Provide a list of all OMS installations performed by the Respondent. Provide the following details for each installation:

Customer details, including contact persons (contact names, positions, telephone numbers).Implementation area, e.g. power generation (specify coal, nuclear, renewables, etc.), power delivery (transmission, distribution), etc.Hardware/software configurations.Functional modules in operation.System sizing information.

9.1.2 For the implementations above (7.1.1), highlight the implementation details of the 5 largest OMS implementations performed in the past 5 years.

Describe the scope of workDescribe the planned and actual delivery dates.Describe the commissioning dates.Describe the reasons for the delivery delays for those OMS implementations that were delivered more than three (3) months behind the original delivery schedule.Describe the project organisation and resource details pertaining to each implementation.

9.2 Respondent’s Current Workload and OMS Implementation Capabilities

9.2.1 Describe the number of OMS projects that are currently in progress or planned for commencement up until end 2019. What number of technical staff is directly involved with the rollout of OMS Systems? Describe their roles.

9.2.2 Describe the sizes and capacities of the OMS development, staging and testing facilities (in South Africa and internationally).


9.3 Resources and Experience

9.3.1 Describe the nature of your resources with respect to OMS product implementation, including resources based in the Republic of South Africa.

9.3.2 Provide details of the technical resources to be employed on the proposed application solution activities related to this Invitation (names, qualifications, experience). Where resources are not permanent employees, indicate this clearly.

9.3.3 Provide a resource plan, indicating the proposed utilisation details for each resource.

9.4 Customer Documentation

9.4.1 Define all project documentation to be supplied with the solution.

9.5 Approach to Product Installation

9.5.1 Describe the standard approach to internal testing.

9.6 Approach to Support

9.6.1 Describe the technical support available for the solution in South Africa.(support strategy)

9.6.2 Describe the support methodology. Do you assign a single technical account manager to the account or do you use a contact centre approach?

9.6.3 Describe the availability of the technical support, and the access methods (08h00-17h00, 24 hour, Help Desk, Web Site, etc.).

9.6.4 Should you be a reseller of the products, describe in detail the support provided to you by the product vendor, including training, technical support, escalation support and direct access to the vendor by Eskom.

9.6.5 Describe the guaranteed support turnaround time.

9.7 Approach to Software Maintenance

9.7.1 Describe the procedures used to distribute system field modification updates to the SaaS Service Provider.

9.7.2 Describe the Software Vendor’s methods to update, maintain and document revisions to the OMS software products.

9.7.3 Life cycle maintenance plan – Describe the major and minor software release strategy.

9.7.4 Does the mechanism exist in the product for logging and automatically forwarding system errors to the appropriate systems management person for analysis?


9.7.5 Describe the areas that have required the most software maintenance field efforts in previous OMS implementations.

9.7.6 Describe the Software Vendor’s escrow arrangements.

9.8 Approach to System Maintenance

9.8.1 Describe the recommended staff / skills requirements for OMS software maintenance.

9.8.2 Describe the recommended staff / skills requirements for database management and commissioning.

9.8.3 Describe the maintenance policy for the system, both during and after any warranty period.

9.8.4 Does the mechanism exist in the product for logging and automatically forwarding system errors to the appropriate systems management person for analysis?

9.8.5 Describe the tools used to facilitate support (e.g. fault and configuration management).

9.9 OMS Services Pricing Model

9.9.1 Describe the OMS services pricing model.

9.9.2 Provide details of any third party licenses used (included in the services pricing).

9.10 Training

9.10.1 Describe all software and system training proposed, including the following information:

List of modules.Duration of each module.Training equipment to be utilised.Cost per module (indicate in the Price Schedule).Maximum number of trainees per module.Availability of courses.Trainee prerequisites.Venues.

9.10.2 Describe any specialised training courses that could be optionally provided.

9.11 Documentation

9.11.1 Provide copies of existing “functional specification” documentation for every software product in the system, and “design” documentation where available.


9.11.2 Describe the user documentation provided with the solution.

9.12 Lifecycle Approach

Describe how the proposed OMS configuration will combat system obsolescence.


Documents

PROPOSAL APPROACH AND RESPONDENT … · Web viewDescribe how the OMS system will trace network outages, group related outage events and calculate the outage impact. 3.1.3 Describe