Appointment of service provider for the supply, implementation and support of the enterprise architecture tool for a period of 60 months.

{"name":null,"email":"[email protected]","phone":null,"department":"that will be","address":"a.co.za, 3 days before the closing of the bid."}

Returnable Documents: 3.3. KEY PERSONNEL EXPERIENCE ........................................................................................................ 7

Eligible bidders must: submit all mandatory returnable documents (OEM letter, financial proposal); achieve a minimum functional evaluation score of 55/80; score 10/10 in the live demonstration of the ten core functionalities; possess tool’s out‑of‑the‑box functionality; provide proof of B‑BBEE status (certificate or compliant affidavit); be registered on the National Treasury Central Supplier Database; have no adverse listings (blacklisted, defaulters, or intelligence‑agency risks); ensure tax affairs are in order with SARS; avoid fronting, bribery, fraud, or corrupt practices; and, if bidding as a joint venture or consortium, submit a consolidated BBBEE certificate verified by a SANAS‑accredited agency. Bids must be received before the closing date and time, be valid for 120 days, and comply with all submission formatting requirements.

TCTA intends to appoint a reputable, well-resourced, experienced accredited ICT partner, to provide

TCTA with an enterprise architecture tool, including implementation, training and support for a period

of 60 months. The aim of an Enterprise Architecture (EA) tool is to provide a single, integrated, and

trusted view of the organization’s business capabilities, processes, applications, data, and

technology landscape to support informed decision-making, strengthen architecture governance,

and ensure alignment between IT investments and strategic objectives. The Enterprise Architecture

tool must provide a comprehensive, integrated platform to manage business, application, data, and

technology architectures, enabling governance, transparency, optimization, and strategic

transformation planning.

Page | 2

3.1. Scope of work

The appointed service provider shall be required to provide TCTA with an enterprise architecture

tool, including implementation training, support and operationalize the enterprise architecture

solution within TCTA.

The scope of work includes, but is not limited to:

Table 1: Functional Requirements

NO functional requirements

2.1.1 Enterprise architecture tool functional requirements

FR01 Repository and Metamodel

FR01.1 Centralized repository for business, application, data, and technology artefacts

FR01.2 Configurable meta-model (capabilities, processes, applications, interfaces, infrastructure)

FR01.3 Version control and history tracking – track versions of all artefacts with timestamps and

editor information.

FR01.4 Relationship mapping between artefacts (e.g., business capability → application →

technology)

FR01.5 The tool must support role-based access control (RBAC) to restrict access to repository

content based on user roles and responsibilities. It must allow administrators to define the

roles and assign permissions accordingly.

FR01.6 The tool must provide a repository search and reuse function for existing architectural

components

FR02 Modelling and Portfolios

FR02.1 Business Architecture Modelling - Capability mapping and heat mapping, value streams and

business process modelling, and strategic objective alignment to capabilities and initiatives

FR02.2 Application Portfolio Management - application inventory and classification, lifecycle

management, and application ownership tracking

FR02.3 Technology Portfolio Management - Technology standards catalogue, Technology lifecycle

tracking, infrastructure mapping, and risk exposure analysis due to outdated technologies

FR02.4 Data Architecture & Integration Mapping - Data entity modelling, application to application

integration mapping, interface catalogue, and data flow visualization

FR02.5 The tool must enable users to store, tag, and reuse custom patterns across teams and

repositories. And the reusable patterns must be searchable and classified

FR02.6 The tool must support object-level reuse, allowing a single definition (e.g., an application,

data entity, or capability) to appear in multiple diagrams without duplication.

FR03 Notifications

FR03.1 The tool must provide configurable notification and alert functionality to support governance

workflows, lifecycle management, compliance monitoring, and stakeholder engagement.

Page | 3

NO functional requirements

FR03.2 The tool must be able to send alerts to users and administrators.

FR04 Road Mapping

FR04.1 The tool must have an ability to define AS-IS and TO-BE architecture states

FR04.2 The tool must be able to provide gap analysis functionality

FR04.3 The tool must provide configurable lifecycle states for applications and technologies (e.g.,

Plan, Implement, Operate, Retire).

FR04.4 The tool must have an ability to visual timeline view of initiatives and transitions

FR05 Governance and Workflow

FR05.1 The tool must provide a configurable model approval workflow to manage the submission,

review, and approval of architectural models and artifacts.

FR05.2 The tool must automatically maintain a comprehensive audit trail capturing all user actions

(create, modify, delete, approve).

FR05.3 The workflow must support multiple approval stages (e.g., draft → review → approved →

published) with clearly defined roles and responsibilities

FR05.4 The tool must support RACI (Responsible, Accountable, Consulted, Informed)-based role

management within the repository.

FR06 Analysis and Reporting

FR06.1 The tool must provide standard dashboards and reporting templates

FR06.2 The tool must provide a flexible reporting engine that allows users to create and customize

reports and dashboards without coding.

FR06.3 The tool must provide risk visualization dashboards indicating technology currency, vendor

support status, and obsolescence timelines.

FR06.4 The tool must support alerts or indicators for technologies / application approaching end-of-

life or non-compliance with standards.

FR07 Audit Trail

FR07.1 The tool must maintain detailed audit trails of all actions within the solution

FR07.2 The tool must maintain a technology standards catalogue defining approved, tolerated, and

obsolete technologies across categories (infrastructure, applications, data, security, etc.)

FR08 Security Management

FR08.1 The tool must support data classification frameworks to categorize data assets (e.g., Public,

Internal, Confidential, Restricted).

FR08.2 The tool must support the capture and management of personal data attributes in line with

POPIA (Protection of Personal Information Act)

FR08.3 The tool data must be encrypted in transit and at rest. The tool must come with secure

authentication and role-based access control and protect TCTA’s data from being viewed or

accessed by unauthorized personnel

Page | 4

NO functional requirements

FR08.4 The tool must provide audit logging and tracking. It must maintain detailed audit trails of all

the activities. The tool must keep an audit trail of all activities performed in the solution

(includes but not limited to the following: who created, updated, and deleted (must be

authorized by super users) the record, with time and date stamp.

FR08.5 The tool must support Multi-Factor Authentication (MFA) for all user logins, whether SaaS or

on premises.

FR08.6 The tool must uniquely identify users and authenticate them. Administrator accounts must be

segregated from normal user accounts. The tool must enable users and/or role-based

permissions to be configured to control what solution features and data users can access.

FR08.7 Availability – the tool must be secured to prevent denial of service to TCTA’s users.

FR09 Integration

FR09.1 The tool should be able to integrate with other systems like Microsoft Active Directory, and

be able to use Open REST/GraphQL Application Programming Interface (API), Excel/CSV

for importing and exporting data; Single Sign-On (SSO) (SAML/OpenID Connect (OIDC));

Configuration Management Databases (CMDB) as a central store for all IT Infrastructure

sync

FR10 AI and Automation

FR10.1 The tool should have AI-assisted modelling or recommendations

FR10.2 The tool must automatically detect and flag duplicate objects within the repository based on

configurable criteria

FR10.3 The tool must leverage AI-driven impact analysis to suggest potential downstream or

upstream effects when modifying or retiring architecture components.

FR10.4 The tool should have the ability for automated diagram generation

3.1.1. Non-Functional Requirements

• The tool must be available 24/7 with a minimum availability of 99% and must cater for the

future growth of 10% of new users.

• The tool must maintain data integrity and quality to ensure a single source of truth in

terms of data integrity.

• The bidder must provide assurance that backups are done and that recovery point

objectives will be no longer than a day.

• Usability and Adoption

o The tool must provide a web-based, business-friendly portal that allows non-

technical stakeholders to easily browse and consume architecture information.

• The portal must support responsive design for access via desktop, tablet, and mobile

devices.

Page | 5

• The tool must include a powerful global search capability across all repository elements,

diagrams, and documentation.

• The tool must maintain a central glossary or dictionary of enterprise terms, definitions,

and abbreviation.

• The tool should include embedded onboarding materials, such as tutorials, guided tours,

or help documentation.

• The tool must allow users to comment on or annotate models, diagrams, or architecture

elements.

3.1.2. Implementation

• Implementation approach – the bidders must provide a detailed description of their

approach to implementing the project, covering at a minimum the following:

o Implementation methodology – outlining approach, governance, roles and

responsibilities.

o The detailed implementation plan outlining the project scope, objectives, timelines,

milestones, resource allocations, communication plan and risk management

approach.

• The successful bidder must provide:

o Tool solution design and present it to the enterprise architecture committee for

approval

o Provide comprehensive technical and operational documentation

o To capture, model and validate the As-Is architecture in the tool, not to develop the

As-Is architecture.

3.1.3. Training and Knowledge Transfer

The successful bidder must be able to provide:

• Provide comprehensive training to TCTA staff on the use of the software solution. The

approach should combine hands-on workshops, guided user sessions, and role-

based training.

• Training manuals and documentation to recipients of the training.

• Initial and ongoing training to the staff as and when needed.

3.1.4. Support and Maintenance

The successful bidder must be able to provide:

• TCTA a user manual to support TCTA in the use of the software solution.

Page | 6

• Technical and functional support for the use of the software solution during standard

business hours (08:00 – 16:30 South African time) through multiple channels, including

telephonic, email, remote, on-site, etc.

• A monthly report on support submitted to TCTA detailing issues logged and resolutions.

• Regular software updates, patches and maintenance of the solution and/or release of a

new version of the software during the contract period.

3.2. Company experience required

The bidder must demonstrate proven experience in the design, implementation, and support of the

enterprise architecture tool. The bidder must provide a minimum of three (3) contactable client

references, on official client letterhead for the enterprise architecture tool implementations

successfully completed.

References must include the client organisation name, contact person, designation, contact details,

nature and scope of work performed, technologies implemented, and the period of engagement

3.3. Key personnel experience

The bidder must provide resources that have technical experience in implementing the solution. A

minimum of seven (7) years of technical lead experience and five (5) years for project manager experience.

3.4. Contract duration

The contract duration is for a period of 60 months

3.5. Deliverables

• Successful tool implementation

• Implementation approach documentation

• Five (5) core user licenses – these licenses should be scalable for business use

• Support and maintenance services for 60 months

4. Stage 1: returnable documents (submission requirements)

All returnables are required for purposes of evaluation irrespective of

Whether they are designated mandatory or not.

Page | 7

Table 2: Returnable Documents

Section description submission requirement

Section 1 OEM letter for manufacturers or Mandatory

A valid Partner letter from the OEM which is within the

required annual renewal for the resellers of the tool.

Section 2 SBD 1: Invitation to bid terms and conditions for bidding Non-Mandatory

SBD 4: Declaration of Interest Non-Mandatory

SBD 6.1: Preference points claim form in terms of the Non-Mandatory

Preferential Procurement Regulations 2022

Section 2 National Treasury Central Supplier Database report Non-Mandatory

Section 4 A valid BBBEE Certificate issued by SANAS accredited Non-Mandatory

agency.

In the instance of an EME or QSE in which case they must

submit a commissioned affidavit which meets the minimum

requirements set out on Annexure H. Sworn Affidavits which

do not meet the minimum requirements set out in Annexure

H will not be awarded points.

Bidders must complete the Sworn Affidavit which is

applicable to their company.

QSEs that do not meet level 1 or 51% black ownership

thresholds are obliged to show compliance with all five of the

categories on the BEE scorecard therefore, a B-BBEE

certificates must be obtained from verification agencies

accredited by SANAS.

Or in case of Joint Ventures:

Consolidated BBBEE certificate issued by verification Agency

approved by SANAS.

Section 5 Company Track Record: Reference letters or alternatively Non-Mandatory

Annexure A – company experience

Section 6 Annexure B - Enterprise Architecture Tool Requirement Non-Mandatory

Matrix

Section 7 Key Personnel – CV or alternatively Annexure C Non-Mandatory

Section 8 Financial Proposal Mandatory

• Comprehensive financial proposal in line with the Pricing

Template provided by TCTA as Pricing Schedule.

Annexure D

Any bidder who fails to submit a mandatory document will be disqualified at this stage and not

evaluated further.

Any bidder who fails to submit/Complete a non-mandatory document where that document is linked

to specific evaluation criteria will not be awarded points.

Page | 8

5. Stage 2: functional evaluation

The evaluation criteria set out below in table 3 will be used to evaluate the bidder’s

functional requirements.

Table 3: Evaluation Criteria

Functionality evaluation

Section evaluation criteria points

COMPANY The bidder must demonstrate proven experience in the design, 20

EXPERIENCE implementation, training and support of the enterprise architecture tool. The

bidder must provide a minimum of three (3) contactable client references, on

official client letterhead for the enterprise architecture tool implementations

successfully completed.

Alternatively, complete Annexure A in respect of their experience in the

provision of an enterprise architecture tool, including implementation, training

and support.

Reference letters must be in the Company’s letterhead with contactable details

(name of the client, contact person, contact number or email address); the

description of the services offered and period the services were rendered (start

date and end date with month and year).

NB: Reference letters that do not meet the above-specified requirements

will not be considered.

Points will be allocated as follows:

• Less than 3 references = 0 points
• 3 references = 10 points
• 4 or more references = 20 points

TCTA reserves the right to contact the companies that are listed in Annexure

A to confirm the authenticity of the information provided.

TOOL The bidder must complete Annexure B and indicate which of the requirements 30

REQUIREMENT their tool addresses by marking “Yes” or “No” in the column. Each Yes equals

MATRIX one (1) point and No equals zero (0)

Bidders are required to identify any functional requirements not currently met

“out of the box” and must indicate whether these gaps can be addressed

through customisation or configuration.

For each shortfall, the bidder must clearly state “Customisation Required” or

similar in the Annexure B matrix next to the relevant item.

• The bidder’s solution covers less than 75% of the requirements = 0

points

• The Bidder’s solution meets 75% - 99% of the requirements with a

maximum of 25% of customisation = 25 points

• The Bidder’s solution meets all requirements as detailed in Annexure B

without customisation = 30 points

Page | 9

Functionality evaluation

KEY The bidder must provide resources that have technical experience in 30

PERSONAL implementing the solution. A minimum of seven (7) years of technical lead

experience and five (5) years for project manager experience in the previous

implementations of the related project.

The team need to consist of one technical lead and one project manager to

manage the project execution.

Bidders to submit Key Personnel – CV or alternatively Annexure C.

Points will be allocated as follows:

Technical Lead:

• Zero (0) – Six (6) years’ experience = 0 points
• Seven (7) – Ten (10) Years experience = 15 points
• Eleven (11) or more experience = 20 points

Project Manager:

• Less than five (5) years’ experience = 0 points
• Five (5) – Eight (8) Years experience = 5 points
• Nine (9) or more experience = 10 points

P total 80

A total of 80 points is allocated to this section. Bidders will have to achieve a minimum score of 55 points out of

80 points to proceed to the next stage of the live demonstration presentation.

Bidders scoring less than the 55 points thresholds will be disqualified at this stage.

6. Stage 3: enterprise architecture tool live demostration

Bidders will be required to select one of their clients from their references where they have

implemented the tool for the live demonstration.

Enterprise Architecture Tool Live Demonstration 10

Bidders who met the minimum points of 55 out of 80 points will be required to

select one of their clients from their references where they have implemented the

tool for the live demonstration. The aim of the demonstrations is for the bidder to

showcase that the out of the box functionality works according to Annexture B.

As part of the evaluation process, Bidders must demonstrate compliance across

ten core functionality features outlined in detail in Annexure B. Each functionality

area will be assessed independently.

A score of 1 point will be awarded for each core functionality feature where full

compliance is demonstrated on each core functionality features as listed below:

• FR01.1 Repository and Metamodel

Page | 10

• FR01.2 Modelling and Portfolios

• FR01.3 Notifications

• FR01.4 Road Mapping

• FR01.5 Governance and workflow

• FR01.6 Analysis and reporting

• FR01.7 Audit Trail

• FR01.8 Security Management

• FR01.9 Integration

• FR10 AI & Automation

Any Bidder not meeting the requirements of 10 points in this section of

the evaluation will be disqualified.

7. Stage 4: price and b-beee

TCTA will evaluate all Bid Submissions in terms of the Preferential Procurement Policy Framework

Act, No. (PPPFA).

Annexure D will be used for the evaluation of price. Bidders are required to provide a total fixed

price over the contract period as per the table in Annexure D.

Self-created templates not in line with Annexure D, will lead to bidders being disqualified.

7.1. B-bbee

7.1.1. A bidder who fails to submit proof of B-BBEE status level of contributor or a non-compliant

bidder will not be disqualified at this stage but:

7.1.1.1. May only score points out of 80 for price.

7.1.1.2. Scores 0 out of 20 for specific goals as per ANNEXURE G: SBD 6.1.

7.1.2. A joint venture or consortium must submit a consolidated B-BBEE certificate in order to earn

B-BBEE points.

7.1.3. All B-BBEE certificates must be obtained from verification agencies accredited by SANAS

unless the bidder is an EME or QSE in which case they must submit a validly commissioned

affidavit QSEs that do not meet level 1 or 51% black ownership thresholds are obliged to

show compliance with all five of the categories on the BEE scorecard therefore, a B-BBEE

certificates must be obtained from verification agencies accredited by SANAS.

7.1.4. An EME or QSE with 100% black ownership qualifies at a Level One.

7.1.5. An EME or QSE with more than 51% black ownership qualifies at a Level Two.

Page | 11

7.1.6. If black ownership of an EME is below 51%, it qualifies at a Level Four.

7.1.7. If black ownership of a QSE is below 51%, it is required to be measured in terms of the QSE

7.2. Price

7.2.1. If the price offered by the highest scoring bidder is not market related, TCTA reserves the

right not to award to that bidder in terms of the PPPFA.

7.2.2. Price must be reflected Excluding and Including VAT.

7.2.3. All prices must include disbursements.

Prices must be firm. Bidders are not allowed to submit multiple quotations

7.2.4. Price adjustments based on ROE fluctuations, would be allowed only on the imported

contents of the commodity and to meet only the suppliers’ additional costs of the imported

content. Bidders are required to submit proof of such fluctuations (receipts for goods

purchased at higher ROE as compared to the ROE at the time of submitting a tender) with

their application for ROE adjustment. TCTA will only consider such applications after 120 days

validity of the bid

7.3. Preferential points calculation

The weighting of the evaluation criteria is as follows:

Price = 80 Points

B-BBEE = 20 Points

Total = 100 Points

8. Stage: 5 supplier vetting

8.1. TCTA reserves the right to disqualify a successful bidder who/whose:

8.1.1. Submits fraudulent information or information that they do not have to authority to submit;

8.1.2. Is listed on National Treasury’s list of Blacklisted Suppliers or Defaulters or similar;

8.2. Poses a risk in terms of any vetting process conducted either by TCTA internally or the

National Intelligence Agency;

8.3. Has a director and/or shareholder who is employed by any organ of state. This does not apply

to any organ of state acting as a bidder. If a bidder has a director and/or shareholder who is

employed by an organ of state, they must submit a letter from the relevant organ of state

stating that they are allowed to do remunerative work outside of their employment contract

and that they are not prohibited from doing business with other organs of state; and

Page | 12

8.4. Tax affairs are not in order at the time of award after being requested to resolve the non-

compliance status with SARS within the prescribed period.

9. Conditions of bid

Any bid submission that does not meet the conditions of bid may be rejected and not evaluated

at all. Such a bid submission will not be acceptable.

9.1. Costs of bidding

9.1.1. Bidders shall bear their own costs, disbursements and expenses associated with the

preparation and submission of the Bid Submissions, including submission of any additional

information requested by TCTA or attending the compulsory briefing session.

9.1.2. TCTA shall not under any circumstances be liable nor assume liability to any Bidder for costs,

disbursements and/or expenses incurred by Bidders regardless of the outcome of the Bid

process or by virtue of cancellation and/or postponement of the Bid process. Where applicable

a non-refundable fee for documents may be charged.

9.2. Clarifications

9.2.1. All questions or queries regarding the Request for Bid must be directed to the person stated

on the front page of this document, stating the relevant Bid number in the subject field, at

least five business days before the stipulated closing date and time of the Request for Bid.

No e-mails, faxes and/or telephone calls should be directed to any other employees of TCTA.

9.2.2. TCTA shall not be liable nor assume liability for any failure to respond to any questions and/or

queries raised by potential Bidders.

9.2.3. Should a Bidder fail to submit and/or complete non-mandatory annexures, TCTA will call

upon the Bidder to complete and submit such annexures. TCTA reserves the right to request

clarity to remove any ambiguities in the documents that have already been submitted. If a

Bidder fails to submit any of the requested non-mandatory documents or schedules within 5

(five) working days of being called upon to do so, then the TCTA may disqualify the Bidder and

no mandatory annexures, mandatory documents and/or mandatory schedules shall be

requested after the tender closing date and time.

9.3. Amendments

9.3.1. TCTA reserves the right, in its sole and absolute discretion, to amend any terms and

conditions of the Request for Bid and/or to stipulate additional requirements, provided that

such amended terms and conditions and/or additional requirements are placed on TCTA’s

website at least ten (10) working days prior to the stipulated closing date and time.

Page | 13

9.3.2. Any amended terms and conditions and/or stipulation of additional requirements by TCTA

shall be deemed to form part of this Request for Bid.

9.3.3. TCTA shall not be liable, nor assume liability of any nature whatsoever, for the failure of a

Bidder to receive information if sent to the e-mail, fax or postal address supplied.

9.3.4. TCTA reserves the right to stipulate additional Bid requirements as it deems appropriate in its

sole and absolute discretion.

9.3.5. TCTA shall not be liable nor assume liability to any potential Bidder/s for any failure by such

Bidder/s to receive any request for additional information.

9.3.6. In the event that TCTA amends its Bid requirements or requests additional information, any

Bidder shall be entitled to withdraw its Bid Submission submitted by it prior to the stipulated

closing date and time and re-submit a replacement Bid Submission by not later than the

stipulated closing date and time.

9.4. Modification, alteration or substitution and/or withdrawal of a bid

1. Definitions, acronyms and abbreviations ......................................................................... 1

2. Preparation of bid submissions .............................................................................................. 2

3. Background .................................................................................................................................... 2

3.1. Scope of work ................................................................................................................................ 3

3.2. Company experience required ................................................................................................ 7

3.3. Key personnel experience ........................................................................................................ 7

3.4. Contract duration ...................................................................................................................... 7

3.5. Deliverables ................................................................................................................................... 7

4. Stage 1: returnable documents (submission requirements) .................................... 7

5. Stage 2: functional evaluation .............................................................................................. 9

6. Stage 3: enterprise architecture tool live demostration .................................... 10

7. Stage 4: price and b-beee ......................................................................................................... 11

7.1. B-bbee ............................................................................................................................................... 11

7.2. Price .................................................................................................................................................. 12

7.3. Preferential points calculation ......................................................................................... 12

8. Stage: 5 supplier vetting ......................................................................................................... 12

9. Conditions of bid ......................................................................................................................... 13

9.1. Costs of bidding .......................................................................................................................... 13

9.2. Clarifications .............................................................................................................................. 13

9.3. Amendments ................................................................................................................................... 13

9.4. Modification, alteration or substitution and/or withdrawal of a bid

Submission ...................................................................................................................................... 14

9.5. Validity period .............................................................................................................................. 14

9.6. Confidentiality ............................................................................................................................ 15

9.7. Right not to award .................................................................................................................... 15

9.8. Terms and conditions of contract .................................................................................... 15

9.9. Subcontracting after award ............................................................................................... 16

9.10. Cession of rights ........................................................................................................................ 17

9.11. Notification of unsuccessful bidders ............................................................................. 17

9.12. Prohibition of bribery, fraudulent and corrupt practices ................................. 17

9.13. Fronting .......................................................................................................................................... 18

9.14. Joint venture or consortium ................................................................................................ 18

9.15. Payment process......................................................................................................................... 19

Annexure a: company experience ..................................................................................................... 21

Annexure b: enterprise architecture tool requirement matric ..................................... 22

Annexure c: template for key personnel’s cv .......................................................................... 26

Annexure d – proposed pricing schedule .................................................................................... 27

Annexure e: sbd 1 – invitation to bid .............................................................................................. 28

Annexure f: sbd 4 – bidder’s disclosure ...................................................................................... 30

Annexure g: sbd 6.1: Preference points claim form in terms of the preferential

Procurement regulations 2022 ............................................................................................ 32

Annexure h – valid sworn affidavit requirements .................................................................. 37

Annexure i: request for access to tcta premises ................................................................... 38

Annexure j: bid receiving form .......................................................................................................... 39

• TCTA a user manual to support TCTA in the use of the software solution.

Page | 6

• Technical and functional support for the use of the software solution during standard

business hours (08:00 – 16:30 South African time) through multiple channels, including

telephonic, email, remote, on-site, etc.

• A monthly report on support submitted to TCTA detailing issues logged and resolutions.

• Regular software updates, patches and maintenance of the solution and/or release of a

new version of the software during the contract period.

3.2. Company experience required

nature and scope of work performed, technologies implemented, and the period of engagement

3.3. Key personnel experience

approved by SANAS.

Section 5 Company Track Record: Reference letters or alternatively Non-Mandatory

Annexure A – company experience

Section 6 Annexure B - Enterprise Architecture Tool Requirement Non-Mandatory

Section 7 Key Personnel – CV or alternatively Annexure C Non-Mandatory

Section 8 Financial Proposal Mandatory

• Comprehensive financial proposal in line with the Pricing

COMPANY The bidder must demonstrate proven experience in the design, 20

KEY The bidder must provide resources that have technical experience in 30

PERSONAL implementing the solution. A minimum of seven (7) years of technical lead

experience and five (5) years for project manager experience in the previous

implementations of the related project.

manage the project execution.

Bidders to submit Key Personnel – CV or alternatively Annexure C.

• Zero (0) – Six (6) years’ experience = 0 points

• Seven (7) – Ten (10) Years experience = 15 points

• Eleven (11) or more experience = 20 points

• Less than five (5) years’ experience = 0 points

• Five (5) – Eight (8) Years experience = 5 points

• Nine (9) or more experience = 10 points

P total 80

A total of 80 points is allocated to this section. Bidders will have to achieve a minimum score of 55 points out of

80 points to proceed to the next stage of the live demonstration presentation.

Bidders scoring less than the 55 points thresholds will be disqualified at this stage.

6. Stage 3: enterprise architecture tool live demostration

prior consent of the Employer.

9.15. Payment process

9.15.1. Monthly invoicing and payment of fees and disbursements will take place based on the actual

services rendered, and payment of invoices shall be affected within 30 days from date of

receipt.

9.15.2. Invoices must be submitted with supporting documents, where requested. No invoice shall

be accepted for goods/services that are not received unless otherwise stipulated in the

contract between the parties.

9.15.3. No payment shall be made unless the following information has been presented to TCTA to

its satisfaction:

9.15.3.1. VAT registration certificate, if the successful Bidder is a VAT vendor;

9.15.3.2. Without deduction of PAYE and/or SITE, if the successful Bidder is not registered

for VAT; or

9.15.3.3. Statement setting out details of services rendered, accompanying invoice.

9.15.3.4. Statement of account detailing cumulative costs claimed from contract inception

against the contract amount.

Page | 19

9.15.4. All invoices shall contain a Purchase Order number, TCTA and successful Bidder’s VAT

number, if registered for VAT, successful Bidder’s name, date of invoice, amount due,

services rendered, due date, and any other relevant details. TCTA’s VAT number is

4360104923.

9.15.5. Payment will only be made against original invoices which complies with the requirements of

the VAT Act. Failure to remit fully compliant invoice will result in late payment, without

forfeiture of any settlement discounts that may be due to TCTA.

Page | 20

Annexure a: company experience

SIGNATURE: ........................................... NAME OF BIDDER.....................................................(of person authorised to sign on behalf of the Bidder)

Page | 25

Annexure c: template for key personnel’s cv

Minimum functionality/qualifying score: 55

minimum score of 55

Central Supplier Database report Non-Mandatory

VAT registration certificate, if the successful Bidder is a VAT vendor

9.15.3.1. VAT registration certificate, if the successful Bidder is a VAT vendor;

B-BBEE Minimum Level: 1

B-BBEE Details: ......................................................................................................................... 7

4. Stage 1: returnable documents (submission requirements) .................................... 7
5. Stage 2: functional evaluation .............................................................................................. 9
6. Stage 3: enterprise architecture tool live demostration .................................... 10
7. Stage 4: price and b-beee ......................................................................................................... 11

7.1. B-bbee ............................................................................................................................................... 11

7.2. Price .................................................................................................................................................. 12

7.3. Preferential points calculation ......................................................................................... 12

8. Stage: 5 supplier vetting ......................................................................................................... 12
9. Conditions of bid ......................................................................................................................... 13

9.1. Costs of bidding .......................................................................................................................... 13

9.2. Clarifications .............................................................................................................................. 13

9.3. Amendments ................................................................................................................................... 13

9.4. Modificat

2.1. Bidders are required to comply fully with this Request for Bid including annexures and the

relevant appendix during submission to TCTA;

2.2. For a Bid Submission to be acceptable, it must:

2.2.1. Not be late and delivered to the address stated on the front page. TCTA shall not accept

nor be obliged to accept Bid Submissions submitted after the stipulated closing date and

time, notwithstanding that such late submission is as a result of circumstances beyond the

Bidder’s control;

2.2.2. Clearly reflect the Bid description and bid number on the outer packaging;

2.2.3. Bidders must submit 1 physical original copy in English and 1 electronic copy on an

unencrypted USB in pdf format. The information in the USB must be identical to the original

submission. TCTA will rely on the original physical submission for evaluation.

2.2.4. Contain a firm price;

2.3. TCTA reserves the right to reject bids that are not acceptable and to not evaluate them.

2.1.1 Enterprise architecture tool functional requirements

FR01 Repository and Metamodel

FR01.1 Centralized repository for business, application, data, and technology artefacts

FR01.2 Configurable meta-model (capabilities, processes, applications, interfaces, infrastructure)

FR01.3 Version control and history tracking – track versions of all artefacts with timestamps and

editor information.

FR01.4 Relationship mapping between artefacts (e.g., business capability → application →

technology)

FR01.5 The tool must support role-based access control (RBAC) to restrict access to repository

content based on user roles and responsibilities. It must allow administrators to define the

roles and assign permissions accordingly.

FR01.6 The tool must provide a repository search and reuse function for existing architectural

components

FR02 Modelling and Portfolios

FR02.1 Business Architecture Modelling - Capability mapping and heat mapping, value streams and

business process modelling, and strategic objective alignment to capabilities and initiatives

FR02.2 Application Portfolio Management - application inventory and classification, lifecycle

management, and application ownership tracking

FR02.3 Technology Portfolio Management - Technology standards catalogue, Technology lifecycle

tracking, infrastructure mapping, and risk exposure analysis due to outdated technologies

FR02.4 Data Architecture & Integration Mapping - Data entity modelling, application to application

integration mapping, interface catalogue, and data flow visualization

FR02.5 The tool must enable users to store, tag, and reuse custom patterns across teams and

repositories. And the reusable patterns must be searchable and classified

FR02.6 The tool must support object-level reuse, allowing a single definition (e.g., an application,

data entity, or capability) to appear in multiple diagrams without duplication.

FR03 Notifications

FR03.1 The tool must provide configurable notification and alert functionality to support governance

workflows, lifecycle management, compliance monitoring, and stakeholder engagement.

Page | 3

FR03.2 The tool must be able to send alerts to users and administrators.

FR04 Road Mapping

FR04.1 The tool must have an ability to define AS-IS and TO-BE architecture states

FR04.2 The tool must be able to provide gap analysis functionality

FR04.3 The tool must provide configurable lifecycle states for applications and technologies (e.g.,

Plan, Implement, Operate, Retire).

FR04.4 The tool must have an ability to visual timeline view of initiatives and transitions

FR05 Governance and Workflow

FR05.1 The tool must provide a configurable model approval workflow to manage the submission,

review, and approval of architectural models and artifacts.

FR05.2 The tool must automatically maintain a comprehensive audit trail capturing all user actions

(create, modify, delete, approve).

FR05.3 The workflow must support multiple approval stages (e.g., draft → review → approved →

published) with clearly defined roles and responsibilities

FR05.4 The tool must support RACI (Responsible, Accountable, Consulted, Informed)-based role

management within the repository.

FR06 Analysis and Reporting

FR06.1 The tool must provide standard dashboards and reporting templates

FR06.2 The tool must provide a flexible reporting engine that allows users to create and customize

reports and dashboards without coding.

FR06.3 The tool must provide risk visualization dashboards indicating technology currency, vendor

support status, and obsolescence timelines.

FR06.4 The tool must support alerts or indicators for technologies / application approaching end-of-

life or non-compliance with standards.

FR07 Audit Trail

FR07.1 The tool must maintain detailed audit trails of all actions within the solution

FR07.2 The tool must maintain a technology standards catalogue defining approved, tolerated, and

obsolete technologies across categories (infrastructure, applications, data, security, etc.)

FR08 Security Management

FR08.1 The tool must support data classification frameworks to categorize data assets (e.g., Public,

Internal, Confidential, Restricted).

FR08.2 The tool must support the capture and management of personal data attributes in line with

POPIA (Protection of Personal Information Act)

FR08.3 The tool data must be encrypted in transit and at rest. The tool must come with secure

authentication and role-based access control and protect TCTA’s data from being viewed or

accessed by unauthorized personnel

Page | 4

of-the-Box Available Required? (Yes/No) Customization (If required)

FR02.6 The tool must support object-level reuse, allowing a single definition (e.g.,

an application, data entity, or capability) to appear in multiple diagrams

without duplication.

FR03 Notifications

FR03.1 The solution must provide configurable notification and alert functionality to

support governance workflows, lifecycle management, compliance

monitoring, and stakeholder engagement.

FR03.2 The solution must be able to send alerts to users and administrators.

FR04 Road Mapping

FR04.1 The solution must have an ability to define AS-IS and TO-BE architecture

states. The solution must be able to provide gap analysis functionality

FR04.2 The solution must provide configurable lifecycle states for applications and

technologies (e.g., Plan, Implement, Operate, Retire).

FR05 Governance and Workflow

FR05.1 The system must provide a configurable model approval workflow to

manage the submission, review, and approval of architectural models and

artifacts.

FR05.2 The system must automatically maintain a comprehensive audit trail

capturing all user actions (create, modify, delete, approve).

FR05.3 The workflow must support multiple approval stages (e.g., draft → review

→ approved → published) with clearly defined roles and responsibilities

FR05.4 The tool must support RACI (Responsible, Accountable, Consulted,

Informed)-based role management within the repository.

FR06 Analysis and Reporting

FR06.1 The solution must provide standard dashboards and reporting templates.

at all. Such a bid submission will not be acceptable.

9.1. Costs of bidding

9.1.1. Bidders shall bear their own costs, disbursements and expenses associated with the

preparation and submission of the Bid Submissions, including submission of any additional

information requested by TCTA or attending the compulsory briefing session.

9.1.2. TCTA shall not under any circumstances be liable nor assume liability to any Bidder for costs,

disbursements and/or expenses incurred by Bidders regardless of the outcome of the Bid

process or by virtue of cancellation and/or postponement of the Bid process. Where applicable

a non-refundable fee for documents may be charged.

9.2. Clarifications

9.2.1. All questions or queries regarding the Request for Bid must be directed to the person stated

on the front page of this document, stating the relevant Bid number in the subject field, at

least five business days before the stipulated closing date and time of the Request for Bid.

9.2.2. TCTA shall not be liable nor assume liability for any failure to respond to any questions and/or

queries raised by potential Bidders.

9.2.3. Should a Bidder fail to submit and/or complete non-mandatory annexures, TCTA will call

upon the Bidder to complete and submit such annexures. TCTA reserves the right to request

clarity to remove any ambiguities in the documents that have already been submitted. If a

Bidder fails to submit any of the requested non-mandatory documents or schedules within 5

(five) working days of being called upon to do so, then the TCTA may disqualify the Bidder and

no mandatory annexures, mandatory documents and/or mandatory schedules shall be

requested after the tender closing date and time.

9.3. Amendments

9.3.1. TCTA reserves the right, in its sole and absolute discretion, to amend any terms and

conditions of the Request for Bid and/or to stipulate additional requirements, provided that

such amended terms and conditions and/or additional requirements are placed on TCTA’s

website at least ten (10) working days prior to the stipulated closing date and time.

Page | 13

9.3.2. Any amended terms and conditions and/or stipulation of additional requirements by TCTA

shall be deemed to form part of this Request for Bid.

9.3.3. TCTA shall not be liable, nor assume liability of any nature whatsoever, for the failure of a

9.3.4. TCTA reserves the right to stipulate additional Bid requirements as it deems appropriate in its

sole and absolute discretion.

9.3.5. TCTA shall not be liable nor assume liability to any potential Bidder/s for any failure by such

9.4.1. Any Bidder shall be entitled to withdraw or modify its Bid Submission at any time prior to the

stipulated closing date and time.

9.4.2. Any amendment or alteration to the Bid documents must be received before the closing date

and time of the Bid as stipulated in the Special conditions of Bid. The words “Amendment to

Bid” and the description of the Bid must be clearly reflected on the envelope containing the

documents or courier packaging as referred to in Condition 2.2.2.

9.4.3. No modification, alteration or substitution of Bid Submissions will be permitted after the

stipulated closing date and time.

9.4.4. TCTA reserves the right to request Bids for clarification needed to evaluate their Bids,

however, such request for clarification shall not allow or entitle Bidders to change the

substance or price of their Bids after Bid opening. Any request for clarification and the

Bidder’s responses will be made in writing.

9.5. Validity period

9.5.1. All Bid Submissions must remain valid for 120 days from the stipulated closing date and time

of the Request for Bid. Each Bid Submission will constitute an irrevocable offer which remains

open for acceptance by TCTA during the validity period.

9.5.2. If TCTA issues a request to extend the validity period, failure to respond to such a request

shall be deemed to be an approval to extend the bid validity period on the same terms and

conditions as per your original bid submission.

9.5.3. If a bidder rejects the extension of validity period with no further comments. The bidder’s

rejection shall be accepted as a withdrawal from the bid process.

Page | 14

9.5.4. If a bidder rejects the extension of the validity period and requests an adjustment to their bid

price. Such adjustment must be in line with the Consumer Price Index applicable at the time

of request for extension and/or a recognised industry pricing guide. Adjustments outside of

these parameters or for any other reason will not be acceptable and the bidders original bid

price shall be deemed to be applicable for the extended validity period.

9.6. Confidentiality

All Bid Submissions received by TCTA will remain in TCTA’s possession. Save as may be required

by law or by any court of competent jurisdiction or similar body having appropriate jurisdiction, no

information contained in or relating to any Bid Submissions will be disclosed to any other parties.

9.7. Right not to award

9.7.1. Due to changed circumstances; there is no longer a need for the goods or the services

specified in the invitation;

9.7.2. Funds are no longer available to cover the total envisaged expenditure;

9.7.3. No acceptable Bid is received; or

9.7.4. There is material irregularities in the Bid process

9.8. Terms and conditions of contract

9.8.1. Once the successful bidder is issued with a Letter of Award, a pre-liminary contract will be

deemed to have been concluded between TCTA and the successful Bidder, which contract

will include the following documents:

9.8.1.1. The contents of this Request for Bid, including all annexures hereto and any

additional requirements as may have been stipulated by TCTA;

9.8.1.2. The relevant Bid Submissions;

9.8.1.3. The letter of acceptance to the successful Bidder/s; and

9.8.1.4. Any correspondence between TCTA and the relevant Bidder/s including all

additional documents submitted by the relevant Bidder/s and accepted by TCTA for

clarification purposes; and

9.8.1.5. The terms and conditions of any agreement/s proposed to be entered into by TCTA

with the successful Bidder/s.

Page | 15

9.8.2. The Bidder will be deemed to have accepted the terms and conditions of an agreement and/or

terms of reference attached to and issued with this Request for Bid. The terms and conditions

of the attached agreement are non-negotiable.

9.8.3. In the event that TCTA and the relevant Bidder are unable to reach consensus on the terms

and/or conditions of the final written agreement, then TCTA reserves the right to cancel the

award of the Bid, without liability of any nature, and to conclude an agreement with any other

Bidder as may be necessary to meet TCTA’s requirements.

9.8.4. Variations

No variations to the contract price will be accepted within 6 months from the date of award, unless

otherwise stipulated in the Letter of Award.

9.8.5. Performance Management

9.8.5.1. This contract shall be subject to performance management in line with TCTA’s

and equitably in terms of a sound, written agreement.

9.14.2. The members of a joint venture or consortium formed in response to transformation policies

should share in at least the following aspects of the joint venture or consortium’s activities in

a meaningful and equitable manner:

9.14.2.1. Control

9.14.2.2. Management

9.14.2.3. Operations

9.14.3. The joint venture or consortium agreement:

9.14.3.1. Must clearly and comprehensively set out the contributions to be made by each

member towards the activities of the joint venture or consortium in securing and

executing the contract and should allocate monetary values to such contributions.

9.14.3.2. Must record the percentage participation by each member.

9.14.3.3. Must provide for meaningful input by all members to the policy making and

management activities of the joint venture or consortium;

Page | 18

9.14.3.4. Must provide for the establishment of a management body for the joint venture or

consortium;

9.14.3.5. Must provide measures to limit, as far as possible, losses to the joint venture or

consortium by the default of a member;

9.14.3.6. Must promote consensus between the members whilst ensuring that the activities of

the joint venture or consortium will not be unduly hindered by failure to achieve it;

9.14.3.7. Must provide for rapid, affordable and easy interim dispute resolution and for

effective final dispute resolution, if required; and

9.14.3.8. Must be sufficiently flexible to allow for joint venture or consortiums which differ in

nature, objectives, inputs by members, management systems, etc;

9.14.4. Right to review the joint venture or consortium agreement

4. Stage 1: returnable documents (submission requirements) .................................... 7
5. Stage 2: functional evaluation .............................................................................................. 9
6. Stage 3: enterprise architecture tool live demostration .................................... 10
7. Stage 4: price and b-beee ......................................................................................................... 11

7.3. Preferential points calculation ......................................................................................... 12

8. Stage: 5 supplier vetting ......................................................................................................... 12

FR03.1 The tool must provide configurable notification and alert functionality to support governance

FR04.2 The tool must be able to provide gap analysis functionality

FR05.3 The workflow must support multiple approval stages (e.g., draft → review → approved →

D for purposes of evaluation irrespective of

SBD 6.1: Preference points claim form in terms of the Non-Mandatory

H will not be awarded points.

categories on the BEE scorecard therefore, a B-BBEE

Any bidder who fails to submit a mandatory document will be disqualified at this stage and not

to specific evaluation criteria will not be awarded points.

5. Stage 2: functional evaluation

The evaluation criteria set out below in table 3 will be used to evaluate the bidder’s

Table 3: Evaluation Criteria

Functionality evaluation

Section evaluation criteria points

• The tool must maintain data integrity and quality to ensure a single source of truth in

Act, No. (PPPFA).

Annexure D will be used for the evaluation of price. Bidders are required to provide a total fixed

bidder will not be disqualified at this stage but

7.1.1.1. May only score points out of 80 for price.