The road accident fund (raf) is issuing a request for information (RFI) to gather market information on cloud-hosted observability solutions that can provide enterprise-wide monitoring, analytics, and operational intelligence across its hybrid technology environment. This RFI is open to original equipment manufacturers (oems) and their accredited partners/resellers, and is a non-binding market research exercise to inform future procurement.
Key Requirements
Only OEMs or accredited partners/resellers of the OEM are eligible to respond.
Responses must be submitted via email to [email protected] by 26 August 2026, 11:00 am.
Must be registered on the National Treasury Central Supplier Database and have tax affairs in order.
Complete all capability matrices in Sections 6.1 to 6.8, selecting exactly one option per capability and providing explanations for Partial or Roadmap responses.
Provide the twelve core information items listed in Section 7.1, including fully completed capability matrices.
Provide indicative commercial information in South African Rand, inclusive of VAT, for a five-year period.
Be prepared to participate in a mandatory solution demonstration if invited, at your own cost.
REQUEST FOR INFORMATION: CLOUD-HOSTED OBSERVABILITY SOLUTION FOR THE ROAD ACCIDENT FUND (RAF) TO SUPPORT ENTERPRISE-WIDE MONITORING, ANALYTICS AND OPERATIONAL INTELLIGENCE ACROSS ITS HYBRID TECHNOLOGY ENVIRONMENT
Tender context
Return to this tender’s issuing organisation, province, or category.
Request for information: cloud-hosted observability solution for the road accident fund (raf) to support enterprise-wide monitoring, analytics and operational intelligence across its hybrid technology environment
Briefing Session
Date & Time
Wednesday, 26 August 2026 - 11:00
Venue
null
Requirements & Eligibility
Eligibility Criteria
Please email all responses to [email protected] Quoting the RFI numer RAF/2026/00048
Professional Services & Consulting Industry Profile
Regulatory Bodies
SAGCSAICA
Tenders in this industry often require registration with these bodies.
Typical Documents
5 items
Company Registration (CIPC)
Tax Clearance Certificate
B-BBEE Certificate
CSD Registration
Company Profile
Recommended Certifications
Having these can improve your winning chances: CA(SA) - Chartered Accountant, PMI-PMP (Project Management Professional), Prince2 Practitioner, Six Sigma Certification
Document read. The full tender notice and its supporting documents are read end-to-end. Key sections, requirements, dates, and contact details are identified and pulled into a working summary you can act on.
Compliance review. The working summary is checked against South African procurement standards — PFMA, PPPFA, B-BBEE, CIDB, local content, and preferential procurement — so nothing critical is missed before you start your bid response.
Procurement Rules & Compliance ContextThis tender may be governed by South African public procurement rules covering fairness, transparency, preferential procurement, anti-corruption, administrative justice and access to information.
7 rules
These references help suppliers understand the public-procurement framework around this opportunity. They are generated from the tender category, issuing organisation type and procurement context.
Core procurement rules
These rules commonly apply to South African public-sector procurement.
7
Broad-Based Black Economic Empowerment Act (B-BBEE Act)
Act 53 of 2003
high
Provides the empowerment-compliance context often used in public-sector supplier evaluation.
Relevant because this is a South African public-sector procurement opportunity.
Constitution of the Republic of South Africa, 1996 – Section 217
Act 108 of 1996 (s217)
high
This is general procurement context, not legal advice. Always verify requirements in the official tender documents and issuing authority notices.
The Road Accident Fund (RAF) is issuing a Request for Information (RFI) for a cloud-hosted observability solution to provide enterprise-wide monitoring, analytics, and operational intelligence across its hybrid technology environment (on-premises, AWS, Azure, Microsoft 365). The RFI is a non-binding market research exercise, not a formal tender. Only OEMs or accredited partners/resellers may respond. Respondents must complete detailed capability matrices across infrastructure, application, cloud, log, digital experience, AIOps, integration, and security domains. The process includes a mandatory solution demonstration for eligible respondents. The goal is to gather market information to refine future procurement requirements.
Not sure if your business is ready for this tender? Check CSD, CIDB, and B-BBEE requirements, run a readiness assessment, and move from opportunity to submission.
Based on 25 comparable awarded tenders. Companies with similar profiles typically bid near the median.
* Estimates are based on historical data and do not guarantee actual award values.
Bid-ready summary. The submission guidelines, evaluation criteria, technical, financial, and compliance sections are refined into professional, easy-to-scan prose. This is the final version you can rely on when preparing your bid or briefing your team.
We refine every tender document through these stages so you can brief your team and prepare your bid with confidence. Anything marked as "in progress" will be upgraded automatically — no action required from you.
Document read
Compliance review
Bid-ready summary
Publish date: 04 August 2026.
Closing date: 26 August 2026, 11:00 am.
Responses must be emailed to [email protected], Attention: Demand Management.
Only OEMs or accredited partners/resellers are eligible.
Bidding structure options: individual bidder, joint venture, consortium, using subcontractors, or other.
For each structure, provide full company details (name, registration number, VAT number, contact person, telephone, fax, email, postal and physical address).
Enquiries must be submitted via email to [email protected], referencing specific paragraph numbers.
The RFI is for a Cloud-Hosted Observability Solution for RAF's hybrid Technology and Digital environment.
RAF's environment includes on-premises infrastructure, AWS, Microsoft Azure, Microsoft 365, enterprise applications, databases, storage platforms, and network services.
The solution should provide comprehensive observability across all these areas through a unified platform.
Submit responses via email to [email protected], Attention: Demand Management.
Closing date: 26 August 2026, 11:00 am.
Only the Original Equipment Manufacturer (OEM) or accredited partners/resellers of the OEM are eligible to respond.
Tick the appropriate box to confirm OEM or Accredited Partner/Reseller status.
Indicate bidding structure: individual bidder, joint venture, consortium, using subcontractors, or other.
Provide full details for each structure: name, registration number, VAT number, contact person, telephone, fax, email, postal and physical address.
For joint ventures/consortia, complete details for each member; for subcontractors, complete details for each subcontractor.
Enquiries must be submitted in writing via email to [email protected], referencing specific paragraph numbers where appropriate.
All questions/enquiries must be forwarded in writing prior to the submission date.
Responses must include the twelve core information items in Section 7.1, including fully completed capability matrices (Sections 6.1 to 6.8).
Incomplete capability matrices (blank rows, multiple selections, or missing explanations for Partial/Roadmap) may result in the response being regarded as incomplete and not invited to the mandatory demonstration.
Optional information in Section 7.2 is not required for eligibility.
All costs of preparing and participating in the demonstration are borne by the respondent; RAF will not reimburse.
Use test, synthetic or anonymised data in demonstrations; RAF production data may not be used without written authorisation.
Failure to attend or complete the demonstration without approved alternative may result in the response not being considered further.
This is a Request for Information (RFI), not a scored bid. No points, weights, minimum thresholds or comparative ranking will be applied.
Eligibility: Must be the OEM or an accredited partner/reseller of the OEM.
Must be registered on the National Treasury Central Supplier Database, have tax affairs in order, and not be on the National Treasury Register for Tender Defaulters or Restricted Suppliers.
Review process is non-scored and consists of three stages:
Stage 1: Review each response for completion of the twelve core information items in Section 7.1, including every capability-matrix row.
Stage 2: Invite respondents that provided the required core information in sufficient detail to the mandatory demonstration.
Stage 3: Consolidate written responses and demonstration observations for market analysis.
A response that omits a core item, leaves a capability row blank, selects more than one response for a capability, or omits required explanation for Partial/Roadmap may be regarded as incomplete.
RAF may request clarification of already submitted information, but clarification may not introduce materially new response.
Optional information under Section 7.2 will not, by itself, affect demonstration eligibility.
Demonstrations are not scored or ranked and do not constitute competitive bid evaluation.
The solution must be a Cloud-Hosted Observability Solution supporting enterprise-wide visibility across RAF's hybrid Technology and Digital (T&D) environment.
Environment spans on-premises infrastructure, AWS, Microsoft Azure, Microsoft 365, enterprise applications, databases, storage platforms, and network services.
Required capabilities include: real-time telemetry, distributed tracing, application performance monitoring, service dependency mapping, business transaction monitoring, AI-driven analytics, predictive alerting, automated diagnostics, and cloud cost optimisation.
Mandatory capability matrices (Sections 6.1 to 6.8) must be completed with exactly one option per capability: Yes, Partial, No, or Roadmap.
For Partial or Roadmap responses, comments must explain functionality, limitations, modules, licensing, configuration, third-party dependencies, and expected availability date.
Application and Service Observability: APM, distributed tracing, service dependency mapping, business transaction monitoring, application diagnostics, root cause analysis, end-to-end service visibility.
Digital Experience Monitoring: RUM, synthetic transaction monitoring, end-user experience analytics, service availability, digital service performance.
AI and AIOps: anomaly detection, predictive analytics, alert correlation, root cause identification, incident prioritisation, trend analysis, automated insights.
Integration: with Azure, AWS, Microsoft 365, Active Directory, Microsoft Entra ID, SIEM, ITSM, PAM, open APIs, existing monitoring tools.
Security and Compliance: RBAC, MFA, SSO, audit logging, encryption in transit/at rest, compliance reporting, POPIA support, secure data management.
Respondents should indicate data residency options and location of hosted services and data centres.
Core information required (Section 7.1) includes: respondent details, OEM status with evidence, company capability, proposed solution details, functional capability matrices, deployment architecture, integration/telemetry, security/privacy, scalability/reporting, indicative commercial model, implementation approach, support approach.
Optional supporting information (Section 7.2) includes certifications, references, product roadmap, limitations, pricing breakdown, implementation plans, JV/consortium arrangements, brochures/diagrams.
Infrastructure Observability: monitoring of physical/virtual servers, storage monitoring and performance analytics, network performance monitoring, infrastructure health monitoring, capacity utilisation tracking and forecasting, resource consumption analytics, availability and performance monitoring.
Application and Service Observability: Application Performance Monitoring (APM), distributed tracing, service dependency mapping, business transaction monitoring, application diagnostics, root cause analysis, end-to-end service visibility.
Cloud and Hybrid Environment Monitoring: AWS observability, Microsoft Azure observability, multi-cloud monitoring and analytics, hybrid cloud visibility, cloud-native workload monitoring, resource utilisation analysis, cloud optimisation insights.
Digital Experience Monitoring: Real User Monitoring (RUM), synthetic transaction monitoring, end-user experience analytics, service availability monitoring, digital service performance visibility.
AI and AIOps: AI-driven anomaly detection, predictive analytics and forecasting, alert correlation, root cause identification, intelligent incident prioritisation, performance trend analysis, automated operational insights.
Integration: with Microsoft Azure, AWS, Microsoft 365, Active Directory, Microsoft Entra ID, SIEM platforms, ITSM solutions, PAM solutions, open APIs and third-party integrations, existing monitoring and operational management tools.
Security and Compliance: RBAC, MFA, SSO, audit logging and audit trail, encryption of data in transit and at rest, compliance reporting, POPIA compliance support, secure data management practices.
Where applicable, indicate data residency options and location of hosted services and data centres.
Must be the OEM or an accredited partner/reseller of the OEM, with evidence of current authorisation to market, implement, and support the solution in South Africa.
Provide a brief summary of local delivery capacity and relevant experience with comparable hybrid or multi-cloud observability implementations.
Optional: Provide relevant organisational, product, technical, security, or personnel certifications.
Optional: Provide one or more comparable customer references, including a brief description of the implementation, outcomes achieved, and contact details where permission has been obtained.
Optional: Provide product roadmap, lifecycle policies, planned enhancements, and known end-of-support or upgrade considerations.
Optional: Provide detailed solution limitations, dependencies, third-party requirements, data-portability options, and exit arrangements.
Optional: Provide joint-venture, consortium, or subcontracting arrangements, including proposed roles of participating parties.
Indicative commercial information must be provided in South African Rand, inclusive of VAT.
Figures are non-binding and used solely for market analysis, affordability assessment, and refinement of future requirements.
Pricing schedule includes:
Year 1: Implementation, configuration, integration and commissioning cost.
Years 1-5: Subscription and licensing for the solution (including infrastructure, application, network, database, log, digital experience, and cloud observability capabilities).
Years 1-5: Technical support, maintenance, upgrades and managed services.
Years 1 and 3: Training and skills transfer for 30 RAF resources.
Total per year and total indicative five-year cost, VAT inclusive.
Submission of commercial information does not constitute a formal quotation, bid, or offer.
Indicative commercial information must be provided in South African Rand, inclusive of VAT.
Figures are non-binding and used solely for market analysis, affordability assessment, and refinement of future requirements.
Submission of commercial information does not constitute a formal quotation, bid, or offer.
Pricing schedule (Section 10) requires:
Year 1: Implementation, configuration, integration and commissioning cost.
Years 1-5: Subscription and licensing for the solution (including infrastructure, application, network, database, log, digital experience, cloud observability).
Years 1-5: Technical support, maintenance, upgrades and managed services.
Years 1 and 3: Training and skills transfer for 30 RAF resources.
Total per year and total indicative five-year cost, VAT inclusive.
No bonds, guarantees, or payment terms are specified in the document.
Must be an eligible supplier duly registered in accordance with applicable South African laws.
Must be registered on the National Treasury Central Supplier Database.
Tax affairs must be in order when submitting responses.
Companies or directors listed on the National Treasury Register for Tender Defaulters or Database of Restricted Suppliers will be automatically disqualified.
Must be the OEM or an accredited partner/reseller of the OEM, with evidence of current authorisation to market, implement and support the solution in South Africa.
No specific B-BBEE, CIDB, CIPC, or local content requirements are stated in the document.
This is an RFI, not a contract. No contractual obligations are created.
RAF is a schedule 3A public entity established under the Road Accident Fund Act, 1996.
Participation in the RFI or demonstration confers no preferential right or advantage in a future procurement process.
RAF may amend, withdraw, or terminate the RFI process at any time without liability to respondents.
Confidentiality obligations apply during demonstrations: RAF information may only be shared with authorised personnel and approved subcontractors bound by equivalent confidentiality obligations.
Respondents must return or securely destroy RAF information upon request or completion of demonstration, except where retention is required by law.
Any actual or suspected loss, unauthorised access, use, disclosure, or compromise of RAF information must be reported immediately.
Respondents must not issue public statements about the RFI without RAF's prior written authorisation.
RAF may use information supplied under Sections 7 and 10, together with observations and clarifications from demonstrations, to refine business and technical requirements, determine suitable deployment and support models, develop evaluation criteria, compile specifications, and decide whether further market engagement or a proof of concept may be appropriate for a future competitive procurement process.
This RFI is issued solely for information-gathering and market-research purposes.
It does not constitute an offer, quotation, bid evaluation, pre-qualification, shortlisting, scoring process, or commitment by RAF to procure any product or service.
Participation in the RFI or a demonstration confers no preferential right or advantage in a future procurement process.
RAF may amend, withdraw, or terminate this RFI process at any time without liability to respondents.
Mandatory: Complete all capability matrices in Sections 6.1 to 6.8.
For each capability, mark exactly one option: Yes (fully available as standard), Partial (some functionality available or additional configuration required), No (unavailable), or Roadmap (planned but not currently available).
Do not leave any capability row blank.
For every Partial or Roadmap response, the comments column must explain the available functionality, limitations, modules, licensing, configuration, third-party dependencies, and expected availability date where applicable.
Completion of the matrices forms part of the Section 7.1 core information and the non-scored completeness review.
An incomplete matrix may result in the respondent not being invited to the mandatory solution demonstration.
Provide the twelve core information items in Section 7.1, including fully completed capability matrices.
Optional information in Section 7.2 is not required for eligibility.
Invitation to demonstration: Following the non-scored completeness review, RAF will invite respondents that have provided the twelve core information items in Section 7.1, including fully completed capability matrices, in sufficient detail.
Optional information under Section 7.2 will not, by itself, determine eligibility.
Invitations will be issued in writing and will specify date, format, duration, participants, scenarios, preparation requirements, technical prerequisites, data requirements, and administrative arrangements.
Demonstration purpose: validate capabilities, assumptions, and information in the submission.
Demonstration scope may include end-to-end observability, APM, distributed tracing, business transaction monitoring, service dependency mapping, hybrid/multi-cloud visibility, AI-driven analytics, dashboards, and cloud-cost visibility.
Demonstration requirements: demonstrate against RAF-defined scenarios, identify assumptions, limitations, configuration, licensing, additional modules, or third-party dependencies.
Demonstrations are not scored or ranked and do not constitute competitive bid evaluation.
All demonstration costs are borne by the respondent; RAF will not reimburse.
RAF may provide limited access to non-production environment, test data, or connectivity at its discretion.
Security, privacy, and confidentiality requirements apply; use test/synthetic/anonymised data; report security incidents immediately.
Failure to attend or complete demonstration without approved alternative may result in response not being considered further.
Participation in demonstration does not confer preferential treatment, pre-qualification, or any right or advantage in future procurement.
Sets the constitutional standard for fair, equitable, transparent, competitive and cost-effective public procurement.
Relevant because this is a South African public-sector procurement opportunity.
This tender has strong source evidence, including source metadata and supporting tender information synced from the government tender portal.
Tenders SA is not the issuing authority. All tenders are automatically synced from the official government tender portal. Always confirm final submission details, closing dates, briefing sessions, eligibility requirements, and documents on the official government portal before applying.
Get deep intelligence on Computer programming, consultancy and related activities. Unlock full pricing strategies, bid frequency, and historical win rates.