RFI: cloud and edge computing deployment and cybersecurity for ESKOM ntcsa operational technology

• For system difficulties, contact the buyer responsible for the published tender.
• Automated submission emails may originate from [email protected].

• Submit tender documents electronically via the Eskom eTendering system.
• Access the system via https://tenderbulletin.ntcsa.co.za or https://eTendering.eskom.co.za.
• You must have a CSD number to register and gain access.
• Registration requires a valid email address and cell phone number; an OTP will be sent to both.
• Upload documents by selecting the correct file type (e.g., Technical, Commercial, Finance).
• Individual file size must not exceed 50MB; total submission must not exceed 900MB.
• Verify all required documents are uploaded before clicking 'Finalize Submission'.
• After submission, save the confirmation email with submission ID for future reference.
• If you encounter difficulties, contact the buyer responsible for the published tender.

• Upload required tender documents by naming the file, selecting the correct type (Technical, Commercial, Finance), and choosing the file.
• Ensure documents are uploaded under the correct category.
• Verify all required documents are uploaded before finalizing submission.
• File size limits: individual files ≤50MB, total submission ≤900MB.
• After submission, you can view and verify uploaded documents via 'My Submissions'.

• The eTendering system is a web-based platform for electronic submission of tender documents.
• It replaces manual submission at Eskom tender offices.
• Suppliers must register with details including CSD number, email, and cell phone.
• OTP (one-time pin) authentication is sent to registered contact points.
• The system is accessible via Tender Bulletin Public website or eTendering website.
• Recommended browser: Microsoft Edge.

• A CSD (Central Supplier Database) number is mandatory to access the eTendering system.

• For closed tenders, suppliers are selected based on meeting the buyer's selection and evaluation criteria.

• Closing date for submission: 22 July 2026 at 10:00 AM South African Standard Time.

• Procurement contact: Claire Gontse Sennelo, Assistant Officer Procurement.
• Telephone: 011 800 8111.
• Email: [email protected].

• Submit electronically via Eskom E-tendering site (NTCSA Tender bulletin). Do not submit physical files.
• Deadline: 22 July 2026 at 10:00 AM South African Standard Time.
• Ensure submission is complete before the closing date and time.
• Upload documents in PDF and Excel formats only. Maximum 50MB per file, 900MB total per submission.
• Do not upload Zip/compressed files.
• If resubmitting, only the latest version will be accepted; previous submissions become null and void.
• Check submission status is marked as complete.
• Refer to the supplier help manual and video on Eskom E-Tendering page for assistance.

• Provide company physical address.
• Provide sender's full name and designation.

Open to suppliers with relevant experience in ICT/OT solutions for power utilities. Must provide company registration number and details of previous experience. Must demonstrate capability to address the technical requirements for mission-critical utility environments.

• This RFI seeks to identify Cloud and Edge Computing technologies deployment and cybersecurity implementation approaches, strategies, and architectures for Eskom NTCSA Operational Technology (OT) environment.
• Responders must address detailed questions covering:
• Contact information and company details.
• Previous experience with ICT/similar solutions for power utility OT.
• Maturity of cloud/edge technologies within EPUs for OT applications.
• Supported architectures (cloud, edge, cloud-edge) with high-level design.
• Cloud deployment architectures (service and deployment models).
• Cloud-edge architecture for mission-critical environments and workload placement criteria.
• Grid control allowance and low-latency performance.
• Data partitioning and processing across edge/cloud layers; real-time vs batch analytics.
• Integration with legacy OT systems/protocols (SCADA, EMS, DMS) and performance in live environments.
• High availability, fault tolerance, and mechanisms during cloud connectivity loss.
• SLAs for uptime, failover, recovery; testing and validation of disaster recovery.
• Contractual definition, testing, validation, and auditing of SLAs.
• Secure and resilient edge-to-cloud network architectures; handling intermittent connectivity.
• Cybersecurity architecture for critical infrastructure (Zero-trust, Purdue model).
• Scalability across multiple substations/grid regions; performance benchmarks and handling demand spikes.
• Vendor interoperability, avoiding lock-in; use of open standards/proprietary frameworks.
• Partnerships with cloud providers; data migration and business continuity.
• End-to-end observability tools; incident detection/response; 24/7 support model; root cause analysis.
• Pricing models (CAPEX/OPEX/subscription); hidden/indirect costs.
• Required infrastructure (hardware, data centre) with bill of materials and indicative pricing.
• Incorporation of emerging technologies; roadmap for smart grids and DER integration.
• Required skills for design, implementation, operation, and maintenance.
• Case studies of previous EPU deployments covering architecture, standards, drivers, data processing, compliance, hardware, lifecycle management, orchestration, monitoring, and timelines.
• Ability to present/demonstrate solutions in a live or simulated environment.
• Responders are encouraged to expand on requirements, indicating assumptions, deviations, or value-added capabilities.

• Address maturity of cloud/edge technologies within EPUs for OT applications and prevalent applications.
• Specify supported architectures (cloud, edge, cloud-edge) with rationale and high-level design.
• Detail cloud deployment architectures (service and deployment models).
• Define cloud-edge architecture model for mission-critical environments and workload placement criteria.
• Explain grid control allowance and low-latency performance.
• Describe data partitioning/processing across edge/cloud layers and strategies for real-time vs batch analytics.
• Detail integration with legacy OT systems/protocols and performance in live environments; ensure minimal disruption.
• Design for high availability and fault tolerance at edge/cloud layers; mechanisms during cloud connectivity loss.
• Specify secure/resilient edge-to-cloud network architectures; handling intermittent/constrained connectivity.
• Explain solution scalability across substations/grid regions; performance benchmarks and handling demand spikes.
• Ensure vendor interoperability and avoid lock-in; indicate use of open standards/proprietary frameworks.
• Incorporate emerging technologies and roadmap for smart grids and DER integration.
• Explain data processing locality (local vs central) and rationale.
• Detail remote lifecycle operations (provisioning, updates, patching).
• Specify orchestration tools (Kubernetes, containers, edge-specific variants).
• Monitor and manage distributed edge nodes.
• Provide implementation timelines and deployment approach (phased vs full).

• Provide contact details and company registration number.
• Provide a brief description of previous experience with ICT/similar solutions for power utility OT.
• Detail partnerships with cloud providers and how data migration and business continuity are handled.
• Specify skills required for designing, implementing, operating, and maintaining cloud and edge technologies.
• Submit case studies of previous EPU deployments covering:
• Reference architecture implemented.
• Role of standards (IEC 61850, IEC 60870-5-101/104, DNP3, Modbus).
• Key drivers for adopting cloud/edge.
• Supported edge hardware platforms (ruggedized, substation-grade).
• Top lessons learned, biggest challenges, and mitigation strategies.

• Provide pricing models (CAPEX vs OPEX, subscription-based) and disclose hidden/indirect costs.
• Submit a bill of materials (BOM) with indicative pricing for required infrastructure (hardware, data centre).

• Provide pricing models offered (CAPEX vs OPEX, subscription-based).
• Disclose any hidden or indirect costs (e.g., connectivity, data egress, maintenance).
• Provide a bill of materials (BOM) with associated indicative pricing for required infrastructure (hardware, specifications, data centre) to enable a cloud and edge ecosystem in an EPU OT environment.

• Describe cybersecurity architecture for cloud-edge deployments in critical infrastructure.
• Specify enforced security principles (e.g., Zero-trust, Purdue model).
• Explain management of identity, access control, and device authentication at scale.

• Provide SLAs for uptime, failover, and recovery; explain testing and validation of disaster recovery scenarios.
• Explain how SLAs are contractually defined, tested, validated, and audited over time.
• Detail management of data sovereignty and regulatory compliance.
• Specify adherence to compliance frameworks (e.g., NIST, ISO standards).

Closing Date: 22 July 2026 at 10:00 AM (SAST). No briefing session, site visit, or clarification deadline dates are stated in the document.

Two signatories are named on the document: 1) Oscar Ngwenya, Chief Engineer Prof Engin; 2) Njabulo Mazibuku, Learner Intern Grad Engin. No email addresses, phone numbers, or physical addresses are provided in this RFI document.

This is a Request for Information (RFI), not a formal tender submission. No specific submission method, required forms, or returnable documents are stated in the document. Tenderers are requested to provide detailed written responses addressing the 9 requirement categories outlined in the NTCSA User Requirements section. Responses should enable NTCSA to make informed decisions on future architectures, security, cost, and operational integration. No submission address, portal, or email is provided in this document.

Qualified vendors, OEMs, cloud service providers, and system integrators with demonstrable, relevant experience in Cloud and Edge solutions for OT environments, particularly in the Electrical Power Utility (EPU) or Transmission System Operator (TSO) sector. Solutions must be proven in production, not conceptual.

NTCSA requires market information on Cloud and Edge computing technologies for their Operational Technology (OT) environment. Key requirement categories: 1) Technology Capability: Architecture overview, deployment models (on-prem, hybrid, private/public cloud, edge devices), real-time performance (latency, deterministic behaviour), high-availability and redundancy. Supported OT protocols: IEC 61850, IEC 60870-5-101/104, DNP3, Modbus. Compatibility with digital substations, process bus, and virtualised OT protection/automation required. 2) Use Cases: Grid monitoring and situational awareness, predictive maintenance analytics, asset performance management, virtualised protection and automation on digital twins, SCADA or historian augmentation, DER coordination. Evidence of successful EPU OT implementations with performance metrics or case studies required. 3) Integration: Must integrate with SCADA/EMS/DMS platforms, substation automation systems, operational historian systems, and legacy OT devices. APIs, middleware, gateways, or integration tools must be described. 4) Operations and Support: Skills, roles, and competencies required for design, deployment, operation, and maintenance. Support model including response times, on-site support, maintenance agreements, and firmware/software upgrade management. User training, documentation, and change-management support. 5) Performance and Scalability: Ability to scale with increased OT data, growth of substations/renewables/DERs, and large analytics workloads. Edge resilience during WAN outages, network degradation, and loss of cloud connectivity. 6) Cost and Commercial: Cost models including licensing/subscription models, consumption-based pricing, CAPEX vs OPEX expectations, and cost drivers. Indicative implementation timelines, phases, and prerequisites. 7) Migration: Cloud provider partnerships, data/workload migration approach, business continuity during migration, and vendor lock-in mitigation. 8) Maturity: Technologies must be proven in production environments (not lab/prototype only), demonstrate industry adoption in critical infrastructure, with available documentation and support. Must comply with IEC, IEEE, IETF standards.

No specific methodology, approach, or execution plan requirements are stated in this RFI. The document requests information on deployment architectures, implementation approaches, and migration strategies but does not prescribe a specific methodology for respondents to follow.

Respondents should be qualified vendors, OEMs, cloud service providers, and system integrators with relevant experience in Cloud and Edge solutions for OT environments, particularly in the Electrical Power Utility (EPU) sector. The document requests evidence of successful implementation of Cloud/Edge solutions in EPU OT environments, including performance metrics or case studies. Technologies must be proven in production environments with multiple operational deployments in critical infrastructure settings. Reference installations should be available.

No specific financial requirements, pricing format, bonds, guarantees, or payment terms are stated in this RFI. The document requests indication of cost models including licensing/subscription models, consumption-based pricing, CAPEX vs OPEX expectations, and expected cost drivers for Cloud/Edge adoption. No financial capacity requirements or bonding requirements are specified.

This RFI focuses on cybersecurity and data sovereignty compliance rather than standard procurement compliance. Required security controls: Identity and Access Management (IAM), Network Segmentation, Encryption (in transit, in use, and at rest), Zero-Trust Architecture, Monitoring and threat detection, Patch and update mechanisms. Data sovereignty requirements: Data residency within South Africa, secure handling of sensitive OT data, support for localised cloud zones. Required framework alignment: ISO 27001, NIST SP 800-82, POPIA, MISS (Minimum Information Security Standards), National Policy on Data and Cloud, IEC 62443, and critical infrastructure protection practices. Note: Standard procurement compliance requirements such as CSD registration, B-BBEE certification, CIDB grading, CIPC registration, or local content requirements are NOT mentioned in this document.

No specific environmental requirements, sustainability targets, or environmental impact assessments are stated in this RFI document.

No contractual terms, contract duration, termination clauses, penalties, or special conditions of contract are stated in this RFI document. This is a market intelligence exercise only and does not constitute a binding procurement commitment.

Two signatories are named: Oscar Ngwenya (Chief Engineer Prof Engin) and Njabulo Mazibuku (Learner Intern Grad Engin). No contact details (email, phone, address) are provided.

• Closing date and time: As per Tender Data. All references to time are South African Standard Time (SAST).
• Compulsory site visits or clarification meetings: Details stated in Tender Data; failure to attend leads to disqualification.
• Tender validity period: Tenders must remain valid for acceptance within the period after closing; Eskom may request an extension.
• Clarification deadlines: Requests for clarification must allow Eskom reasonable time to respond before closing.
• Addenda: Published on Eskom Tender Bulletin and NT e-Tender Portal; tenderers must check regularly for updates.

• All communication must be in writing to the Eskom Representative only, as specified in the Invitation to Tender.
• No specific contact details provided in this document; refer to Tender Data for Eskom Representative details.

• Submit the complete original tender plus one hard copy to the address and tender box specified in the Tender Data by the closing time.
• For e-tendering, upload and finalize via Eskom Tender Bulletin site on the Eskom E-tendering page by the closing time.
• Ensure documents are accessible, not corrupt, and submitted before closing. Proof of posting/courier is not proof of delivery.
• Mark packages as "ORIGINAL" and "COPY". Seal them together in an outer package marked "Confidential" with Eskom address, tender number, tenderer details.
• Submit all mandatory tender returnables completed by the closing time. Missing mandatory documents leads to disqualification.
• Tenders received late will not be accepted. E-tendering system blocks submissions after closing.
• Attend compulsory site visits or clarification meetings; failure results in disqualification.
• All communication must be in writing to the Eskom Representative only, in English.

Unable to extract eligibility criteria

• Scope: The tender is for Cloud and Edge Computing technologies’ deployment and cybersecurity implementation approaches, strategies, and architectures applicable to Eskom NTCSA Operational Technology (OT) environment.
• Communication: All communication between Eskom and tenderers must be made to or from the Eskom Representative only, in writing, in English.
• Tender documents: Include Invitation to Tender documents, annexures, and any additional requirements stated in Tender Data.
• Addenda: Published on the same platform as the Invitation to Tender; tenderers must check regularly.

• Cost of tendering: Eskom does not compensate for preparation, submission, testing, or negotiation costs.
• Tender submission: Check Invitation to Tender documents on receipt; notify Eskom representative of discrepancies.
• Acknowledgement Form: Must be completed and submitted, stating if tender is for whole or part of works/services.

• Pricing inclusion: Rates and prices must include all duties, taxes (VAT), and levies applicable 14 days prior to closing.
• Fixed prices: Prices are fixed for contract duration unless price adjustment is provided for.
• Currency: State in South African Rand unless instructed otherwise.
• Alterations: Only allowed to comply with Eskom instructions or correct errors; must be initialed by all signatories.
• Alternative tenders: Only permitted if a main tender is submitted and allowed by Invitation to Tender.
• Clarification: Eskom may request clarification during evaluation, but mandatory returnables cannot be submitted after closing.
• Financial analysis: Eskom assesses financial risk; mitigating factors may be required.
• Price evaluation: Based on Tender Data criteria, considering factors like CPA, FOREX, discounts, technical adjustments.
• Arithmetical errors: Corrected by Eskom with tenderer confirmation; discrepancies favor amount in words.
• Specific Goals: Missing proof results in zero points under 90/10 or 80/20 allocation.
• Ranking: Combined pricing and Specific Goals scores ranked per PPPFA.
• Objective criteria: May apply if stipulated; excludes functionality and B-BBEE elements.

• Pricing: Include all duties, taxes (including VAT), and levies applicable 14 days prior to closing in rates and prices.
• Prices must be fixed for contract duration unless price adjustment is provided for in the Invitation to Tender.
• State rates and prices in South African Rand unless instructed otherwise.
• Arithmetical errors: If discrepancy between figures and words, amount in words prevails. Eskom will correct errors and request tenderer confirmation.
• Financial analysis: Eskom assesses financial risk; tenderers may need to meet mitigating factors.
• Insurance: Eskom may not provide full cover; tenderers should seek qualified advice.

• B-BBEE: Provide proof of B-BBEE level via CSD report or certificate/affidavit at closing if a pre-qualification criterion; otherwise, may score zero points.
• CIDB registration: If stipulated, proof of registration or application must be submitted by closing; actual registration proof may be required by contract award.
• Legislative compliance: Comply with National Treasury instructions, CIDB regulations, PPPFA, B-BBEE Codes, COIDA, OHS Act, Eskom SHEQ requirements.
• SHEQ proof: Provide proof of safety, health, environmental, and quality systems, policies, and capabilities at closing and/or contract award.
• Contract Skills Development Goals (CSDG) and Contract Participation Goals (CPG): Apply if contract meets duration and value thresholds; contractor must achieve these goals.
• Fraudulent information: Misrepresentation or falsification leads to disqualification and reporting to B-BBEE Commission, with possible suspension and legal action.
• SDL&I Undertaking: Complete and submit by contract award.

• Legislative compliance: Comply with OHS Act, Eskom SHEQ requirements, and other applicable legislation.
• SHEQ proof: Provide proof of safety, health, environmental, and quality systems, policies, and capabilities at closing and/or contract award.
• CIDB registration: If required, proof of registration or application must be submitted by closing; actual proof may be required by contract award.
• Contract Skills Development Goals (CSDG) and Contract Participation Goals (CPG): Apply if contract meets duration and value thresholds; contractor must achieve these goals.
• Fraudulent information: Misrepresentation leads to disqualification and reporting to B-BBEE Commission.
• Communication: Clarification requests and addenda are published on Eskom Tender Bulletin and NT e-Tender Portal; tenderers must check regularly.
• Tender opening: For e-tendering, no public opening; names published on Eskom platforms.
• Grounds for rejection: Proof of influence, collusion, bid rigging, or fraudulent activity leads to rejection.
• Reverse e-auction: If used, tenderers submit a tender without prices.

• Liability: Eskom, its representatives, and affiliates are not liable for losses from participation, amendment, termination, or exclusion from the tender process.
• Negotiation: Eskom reserves the right to enter into mandated negotiations with selected tenderers per its procurement policies.
• Disclaimer: Eskom disclaims liability for accuracy or completeness of tender documents.
• Tender validity: Tenders must remain valid for acceptance within the period after closing; Eskom may request an extension.
• Confidentiality: Treat all procurement matters confidentially; use Eskom documents only for tender preparation.
• Compulsory meetings: Attend site visits or clarification meetings if stipulated; failure leads to disqualification.
• B-BBEE evaluation: Scoring based on CSD report or certificate/affidavit; pre-qualification requires proof at closing.
• Specific Goals: Scored with supporting documentation; missing proof results in zero points.

• Functionality scoring: If used, tenderers are scored against criteria and must meet a minimum threshold.
• Financial risk assessment: Eskom evaluates tenderers’ financial statements for risk; mitigating factors may be required.
• Price evaluation: Based on Tender Data criteria, considering factors like CPA, FOREX, discounts, technical adjustments.
• B-BBEE scoring: Using CSD report or certificate/affidavit; if pre-qualification, proof required at closing.
• Specific Goals: Scored with supporting documentation; missing proof results in zero points under 90/10 or 80/20 allocation.
• Ranking: Combined pricing and Specific Goals scores ranked highest to lowest per PPPFA.
• Objective criteria: May apply as per PPPFA if stipulated; excludes functionality and B-BBEE elements.
• Reverse e-auction: Electronic system using preference points for competitive pricing; tenderers submit without prices if used.