anova health institute · 5.1 general instructions 16 5.2 proposal format and content 16 cover...

Anova Health Institute RFP | ERP Systems and Implementation Services

P a g e 1 | 30

Anova Health Institute

Request for Proposal for Enterprise Resource Planning (ERP) System and

Implementation Services


P a g e 2 | 30

Table of Contents

1.0 RFP Overview 3

1.1 Purpose of RFP 3 1.2 Objectives and Scope 3 1.3 RFP Timeline 4 1.4 RFP Coordinator 4 1.5 RFP Amendment and Cancellation 5 1.6 RFP Questions 5 1.7 Proposal Submission 5 1.8 Duration of Proposal Offer 6 1.9 Evaluation of Proposals 6 1.10 Proposal Acceptance 6 1.11 Non-collusion, Conflict of Interest 6

2.0 Anova Health Institute Overview 7 3.0 Current Environment 8 4.0 ERP System Requirements 10

4.1 Required Modules 10 4.2 Key Functionality 14 4.3 Implementation Timeline 14 4.4 Requirements 14

5.0 Proposal Submission Requirements 16 5.1 General Instructions 16 5.2 Proposal Format and Content 16

Cover Letter 16 Table of Contents 17 Section 1 – Executive Summary 17 Section 2 – Company Background 17 Section 3 – Company Qualifications 17 Section 4 – References 17 Section 5 – Proposed Solution 18 Section 6 – Implementation Approach and Work Plan 18 Section 7 – Hosting and Support 21 Section 8 – Pricing/Cost Proposal 21 Section 9 – Software Licensing and Maintenance Agreements 21 Section 10 – BB-BEE Certifications 22

6.0 Proposal and Finalist Presentation Evaluation 23 6.1 Proposal Evaluation Criteria 23 6.2 Presentation Evaluation Criteria 24

7.0 RFP Terms and Conditions 25


P a g e 3 | 30

1.0 RFP Overview

1.1 Purpose of RFP Anova Health Institute has issued this Request for Proposal (RFP) to solicit responses from vendors offering proven integrated solutions to support Anova’s existing finance system, human resources, time and attendance, fleet management, travel and customized procurement workflow system. Anova seeks a qualified vendor (Proposer) who can demonstrate that they possess the organizational, functional, and technical capabilities, along with the experience, expertise, and qualifications necessary to provide a fully-integrated, proven Enterprise Resource Planning (ERP) solution along with the professional services specified to complete the ERP implementation and to support the system post-implementation.

1.2 Objectives and Scope With this RFP, Anova Health Institute intends to implement a proven ERP system. Anova’s goal is to take advantage of a modern, scalable ERP system that is designed around international development best practices, allowing Anova to streamline and improve processes that result in timely, accurate, and easy-to-access information. More specifically, the new ERP system should meet the following objectives:

• Consolidate information, link processes and functions, and eliminate separate departmental systems/spreadsheets in favor of a single system that connects Anova’s financial and non-financial applications through a common database.

• Streamline business processes to take advantage of best practices through automation, integration, and workflows.

• Provide a user-friendly and intuitive user interface to promote system use and productivity. • Eliminate or reduce redundant data entry. • Eliminate or reduce the need for manual input when preparing various financial documents

and reports. • Improve and/or provide necessary reports and reporting capabilities and access to data

through inquiry or drill down capabilities. • Provide interface capabilities with third-party systems (Oracle Cloud, Excel, etc.). • Reduce Anova’s reliance on supplementary systems and manual processes to support

reporting, budgeting, and financial forecasting needs. • Reduce the effort and costs associated with maintaining the ERP system’s physical

infrastructure, security, and system maintenance. • Reduce the effort, cost, and time to apply patches and upgrades that deliver new functionality. • Adopt a flexible technology platform with a high degree of usability. • Adopt a technology that provides users with the flexibility to access the system and

accomplish at least some work tasks via mobile platforms. • Ensure accessibility in low-bandwidth environments through various options, including

potential offline functionality.

In addition to the functionality identified above, Anova is seeking a Proposer to provide professional services (e.g., best practices guidance, training, project management, implementation, and integration) that will help ensure a successful implementation in a timely and professional manner.


P a g e 4 | 30

1.3 RFP Timeline Table 1. RFP Timeline

RFP EVENT DATE/TIME

Anova Issues RFP Wednesday, October 16, 2019

Deadline for Proposer Questions Monday, October 21, 2019 by 5:00 P.M.

Anova Provides Responses to Questions Wednesday, October 23, 2019

Deadline for Proposal Submission Monday, October 28, 2019 by 5:00 P.M.

Proof-of-Capabilities Demonstrations by Finalists

Thursday, October 31 and Friday, November 1

As identified in Table 1, finalist(s) may be required to participate in either a proof-of-capabilities (POC) demonstration to allow staff to fully understand the proposed solution or provide a testing environment for staff. This process will entail a demonstration using scenarios to evaluate critical product functionality rather than Anova viewing a generic product demonstration. Proposers must be prepared to invest the time and resources in the proof-of-capabilities demonstration / test environment to be successful in this procurement. Anova bears no responsibilities associated with the Proposer’s costs responding to this RFP. After the completion of the POCs, Anova intends to select a finalist that may be asked to participate in further solution demonstrations to ensure that all pertinent modules are reviewed prior to finalizing negotiations. Anova reserves the right, at its sole discretion, to adjust the RFP Timeline as it deems necessary.

1.4 RFP Coordinator All communications concerning this RFP must be submitted via email to the RFP Coordinator using

both email addresses identified below.

RFP Coordinator

Name: Traci Dixon

Title: Organizational Development Lead Advisor

Email: [email protected]

Email: [email protected]

The RFP Coordinator will be the sole point of contact for this RFP. Proposer contact with any person(s)

in Anova Health Institute other than the RFP Coordinator is expressly forbidden and may result in

disqualification of the Proposer’s bid. Any communications other than via email to the RFP

Coordinator will be considered unofficial and non-binding on Anova.


P a g e 5 | 30

1.5 RFP Amendment and Cancellation Anova reserves the unilateral right to amend this RFP in writing at any time. Anova also reserves the right to cancel or reissue the RFP at its sole discretion. If an amendment is issued, notification shall be provided to all Proposers. Proposers must respond to the final written RFP, including any exhibits, attachments, and amendments.

1.6 RFP Questions Questions concerning the RFP should be submitted via e-mail to the RFP Coordinators prior to the “Deadline for Proposer Questions” identified in Section 1.3 above. Proposer questions should clearly

identify the relevant section of the RFP and page number(s) related to the question being asked. The

email subject line should read: ERP System and Implementation Services RFP Q&A. Questions must be submitted in writing to both RFP Coordinator email addresses at [email protected] and [email protected]; phone calls will not be accepted. Questions and requests for clarification, and the responses thereto, that Anova believes may be of interest to other offerors will be circulated to all RFP recipients who have indicated an interest in bidding. Only the written answers issued by Anova will be considered official and carry weight in the proposal process and subsequent evaluation. Any verbal information received from employees of Anova or any other entity should not be considered as an official response to any questions regarding this RFP. Anova will respond to questions received by this date and time, consolidate questions and answers and redistribute the responses to bidders by 5:00 P.M. on Wednesday, October 23.

1.7 Proposal Submission Proposals are to be submitted in the requested format no later than the “Deadline for Proposal Submission” identified in Section 1.3. A Proposer's failure to submit a proposal as required before the deadline may cause the proposal to be disqualified. Proposers must submit via email: one (1) electronic proposal copy as a single PDF (.pdf) file containing all submitted material. The cost proposal should be submitted in one (1) separate Excel workbook. The proposal package shall be emailed to the RFP Coordinator listed in Section 1.4 above. The email should have a clear subject line as follows: “Proposal for ERP System and Implementation Services” and contain the following information in the body of the email:

Name of Proposing Firm Proposer’s Address Proposer’s Contact Person Proposer’s Telephone Number

All information must be received by Anova [email protected] and [email protected] on the date/time indicated in Section 1.3. Information received after this time and date may be unopened, and the Proposer may be disqualified from future consideration.


P a g e 6 | 30

1.8 Duration of Proposal Offer Proposals are to be held valid for 120 days following the closing date for this RFP. This period may be extended by mutual agreement between the vendor and Anova.

1.9 Evaluation of Proposals A contract award will be made to the responsible Proposer(s) whose proposal best meets the needs of Anova as determined by an evaluation committee. After considering the factors set forth in this RFP, the committee will make recommendations for the award of the contract to the vendor(s) whose proposal(s) is/are determined to be the most advantageous to Anova from a technical and cost standpoint.

1.10 Proposal Acceptance Anova reserves the right to accept or reject any and all proposals, in whole or in part, received as a result of this RFP, to waive minor irregularities, to negotiate in any manner necessary to best serve the interest of Anova. Further, Anova reserves the right to make a whole award, multiple awards, a partial award or no award at all. Proposers deemed not to be responsive will be disqualified. Anova reserves the right to increase or decrease the quantities of any materials, equipment, supplies or services.

1.11 Non-collusion, Conflict of Interest The proposal should contain certification regarding non-collusion and declarations of real or potential conflicts of interest with employees of Anova Health Institute.


P a g e 7 | 30

2.0 Anova Health Institute Overview Anova Health Institute (https://www.anovahealth.co.za) is a not-for-profit, non-governmental organization (NGO) that empowers people and changes lives. Good health and quality of life are what motivates us to provide healthcare solutions and support for those who need it most. With a specific focus on HIV, our work is built on a foundation of research to ensure that funds are focused where we can make the most difference. Much of our work has centred in South Africa, where Anova is a trusted partner of the Department of Health. We are committed to bolstering the public healthcare system through skills building, improved recordkeeping and monitoring, management training and improved client flow. By identifying opportunities to enhance public health, we are making significant contributions to sustainable healthcare infrastructure. Our teams throughout South Africa are also actively involved in community outreach, support, engagement and awareness, and educational campaigns. Our areas of medical expertise include surveillance in key populations, clinical and social research, elimination of mother-to-child transmission of HIV, TB and HIV care and treatment (including paediatric, adolescent and adult care), health systems strengthening (mHealth, supply chain management, quality improvement and management training), eye care and mental health. Anova supports the South African government’s bold initiatives through technical assistance and direct service delivery to ensure increased access and efficient and high quality services. Providing health systems strengthening support in: Regions A, B, C, D, E and G in the City of Johannesburg and Sedibeng (Gauteng), Mopani and Capricorn (Limpopo) and Cape Winelands (Western Cape), we support over 500 health facilities. Anova employs over 3000 people, more than 60% female and a broadly representative mix of South Africa’s race groups. We are expected to grow to over 4000 people in the coming year.


P a g e 8 | 30

3.0 Current Environment This section documents the state of the current environment to help Proposers prepare their proposal responses. Anova currently utilizes Pastel Evolution and SAGE VIP Premier for its financial and payroll operations. We are seeking an integrated product to provide more effective and efficient financial management, approvals and workflow management, procurement and human resources support. As noted below, we are looking for costing options that include sustaining our current use of Pastel Evolution and SAGE VIP Premier integrated with systems that allow for the capabilities outlined in this RFP. The proposed system must be compatible with Anova’s existing technical environment or accessible from it. Client machines are either MacOS or Windows, with most running a minimum of Windows 10/ Office 365. A few machines are running older versions of Windows. Anova’s work also includes roving teams which conduct work primarily on hand-held devices, cell phones, tablets and laptops. The Proposer’s affiliated vendors will be required to confirm conformance to these requirements or clearly articulate proposed alternatives. Performance in low-bandwidth environments is a key issue and must be tested to ensure reliability. The proposed system must be flexible enough to allow for integration with other systems that may be required or are already in use. Assumptions and Constraints Key Assumptions:

1. The ERP solution should be fully functional when launched; launching a “minimum viable product” and then improving it while in production will not meet the ongoing business needs of the Anova community. Although launching of different “modules” at different times would be acceptable, as agreed in advance with Anova. The Proposer should provide Anova options for module-specific rollout to ensure that we maximize timing with the tax year end. Please note the specified timeline noted in the key constraints section below.

2. Any new ERP software will be net positive or net neutral to Anova users and will not harm users by removing key functionality.

3. Anova currently, and will continue to, operate in a self-service environment for data and reporting, whereby users can readily export data from reports in formats that permit manipulation and/or produce customizable reports through the system.

4. Anova will require historical financial and HR data from October 1, 2019 to be migrated into the new system.

5. If the ERP system cannot replace all required functionality, a Platform-as-a-Service like solution may be included to enable Anova to develop, deploy, and maintain existing or future finance applications not included in the new system.

6. Anova will simultaneously work on identifying a biometric timesheet provider. Information on this service provider will be provided to all Proposer’s when the information is known. This should not preclude the Proposer from proposing an option for the biometrics time tracking requirements identified below.

Key Constraints:

1. Anova desires to acquire and implement the new ERP system during fiscal year 2020 with the first systems inclusive of payroll, finance and accounting implemented not later than January 1, 2020 and final systems in a phased approach implemented not later than July 31, 2019 to


P a g e 9 | 30

ensure full testing and refinement in the final two months of the fiscal year (August 1-31 and September 1-30, 2020).

2. Anova operates under South Africa’s and donor (US Government) financial rules, regulations, and operating procedures which directly affect its business processes, including 2 CFR 200; any new system must be able to conform to these regulatory requirements and prescribed timeframes.

3. Anova’s offices regularly experience low-bandwidth conditions, and any system must be able to operate in a low-bandwidth environment on multiple types of devices. Preference will be for systems that offer offline functionality.

4. The system must be able to address fund and multi-currency accounting needs. Implementation Approach The Proposer is encouraged to propose a phased launch, in which modules may be rolled out in phases to be completed in fiscal year 2020. As noted above, the Proposer should provide Anova options for module-specific rollout to ensure that we maximize timing with the end of the fiscal year, quarter end or tax year end.


P a g e 10 | 30

4.0 ERP System Requirements

4.1 Required Modules Anova is seeking a highly integrated system that can serve as many of Anova’s various department needs as possible. We have outlined below the mandatory solution modules. It is important to note that while Anova is interested in evaluating whether to transition to a new payroll and accounting system, we are also looking for costing options that include sustaining our current use of Pastel Evolution and SAGE VIP Premier integrated with systems that allow for the capabilities outlined in this RFP. All costing should include a cloud-based approach compared against a hard installation on Anova’s local server. Mandatory solution modules include the following: Finance

• General Ledger/Accounting · Robust Chart of Accounts that has multiple segments that can allow for tracking expense and

revenues by funding sources, program codes, subaccount categories, expense locations and other user defined fields.

· Electronic entry for typical entries such as Journal Entries. · Produce audit trails to ensure data integrity. · Transaction entry should have a large comment field. · Expenses should report in multi-currency throughout the trial balance so that balance sheet,

income statement and other reports appear in multicurrency. · Foreign currency conversion rates should be able to link to external real time data sources. · Transparent currency calculations and conversion rate data. · Features to appear in the ledger: vendor name, description, payment dates, subsidiary ledger

note, payment reference, procurement number as well as chartfield. • FX rates need to be flexible for each funding stream; some funding has a fixed rate for a period,

while other Anova funding streams are at a rate of conversion at date of receipt/ transfer. • Budgeting/Forecasting should be robust enough to allow for reporting over multi timeframes. • Vendor Management that allows for recording to multiple A/P account. • Procurement/Purchasing (Vendor Management). System should prompt for repeated purchase

order (PO) numbers and not allow for duplicate PO numbers. Similarly, vendor invoice numbers should be limited to a single use.

• Disbursements: Allows for easy payment request via file transfer to a bank. Prompts for duplicate invoice payment.

• Reporting on open PO balances and PO’s expiring in thirty and sixty and ninety days. • Fixed Assets managements that links from completed purchases. • Subcontractor Financials - either the subcontractor can upload their data and/ or their invoice is

uploadable. • Accounts Payable

· Detailed report that can show each line item for each PO and payment(s) applied to the bill and PO.

· Details roll into a subsidiary ledger. · Procurements roll into Payables reporting. · Allow for payments to be applied to a procurement and allows for direct invoice pay with

approvals.


P a g e 11 | 30

· Payments require approvals. · Reports done by Vendor by Time period in both Summary and Detail Format. · Reports done by Time Period - Summary/Detail/Vendor Vendor Fields – name, address, etc. · Payments/procurements cannot be changed via the general ledger.

• Payroll Processing · Controls and authorizations in place · Salary expense = Gross Pay. · Taxes are deduction entries from pay. · Tracks earnings and deductions by calendar year and then is easily reportable. · Tracks earnings by funding source. · Tracks tax, other statutory payments and allows for payment of same. · Project costing controls which allow us to split level of effort (LOE)/hours across various

projects, as needed, and costs are then posted accordingly. · Must be able to fund the payroll from various projects in line with the above.

• GPS-enabled biometric timesheets/ time and attendance clocking · Reporting by funding source (separate and distinct job codes) that can then track effort

worked against different projects. · GPS enabled biometric clocking in and out should identify location of clocking (fixed at

facilities and mobile for roving teams) in within an acceptable range of specific work locations. · Extraction and reporting options for HRID. · Timesheet workflow approval with auto-notifications to supervisors and senior managers

when timesheets and/or expenses must be reviewed/ approved; and escalation notifications if timesheets/ expenses are not reviewed/ approved within a 24-48 hour period.

· Generate approvals for leave (all categories) that need to be authorized electronically via delegation to the individual’s supervisor/ manager.

· Consultants must be able to bill hourly versus salaried. · The system should flag exceptions to the appropriate leadership/ supervisor/ manager. · All time and attendance elements need to be fully integrated with payroll system; to include

LOE splits. • Accounts Receivable and Billing

· Detail by person/ customer by advances summarizes into a subsidiary ledger; journal entries to A/R affect the detail A/R reporting by person/ donor.

· Automated invoicing to projects based on a predefined monthly % split that varies monthly/ by invoice type

· Invoices linked to POs for a consolidated record. · Multiple receivable subcodes.

Grants Management

• Award Setup. • Billing and Invoicing. • Grant Transactions (revenue recognition, F&A allocation). • Grant Reporting for multiple periods and periods that do not cross fiscal year. • Unique funder award number tracking. • Contract/ award management. • Grant reporting that is funder/ donor-specific, on a funder template, etc.


P a g e 12 | 30

Procurement • Robust integration with Accounts Payable. • Supplier Management:

· Need to be able to duplicate vendors. · Delineation between vendors where (a) Anova pays a deposit for work to commence or to

pay deposits for accommodations/ lodging. Here, Anova would not have a delivery note prior to these types of payments; and (b) Anova is processing an invoice after receipt of a delivery note. The system needs to provide for the (a) exception.

• Online Requisition entry (including attachments) with electronic approvals - ensure these move along for approval on a predetermined path.

• Quotes - source and receive quotes online. • Bid Analysis - users should be able to analyze bids using online forms such as the bid comparison

form. • Purchase orders - should be raised online and use forms with Anova Health Institute

requirements; the user should be able to email the purchase order/contract to the vendor; system should prompt for duplicate purchase orders.

• Approvals - all online, follow an electronic workflow • Delivery should happen online - receivers should have to receive the products through the

system, including by scanning a goods received note. Invoices should not be allowed to be marked for payment unless the goods have been received.

• Lead Time Tracking.

Asset and Inventory Management with automatic depreciation calculation. • Fully integrated fixed asset system with flexible reporting by site/ project/ category, etc. with

reminders to update the asset registers within the system on a quarterly basis.

Travel and Expenses • Travel orders begin with booking request and a travel authorization form with a unique trip

identifier. • Travel orders, once approved, allow for a travel advance that links to the travel trip identifier. • Disbursement requests link to the advance and authorization. • Process and approvals facilitated in an electronic workflow.

Human Resources

• Performance Reviews • Employee Personnel Database • Job Information • Benefits Administration • Leave Administration • Compensation • Onboarding • Separation/Off-boarding • Recruitment • Talent Management • Employee Self-Service • Manager Self-Service • Payroll Integration


P a g e 13 | 30

Logistics and Fleet Management • Vehicle registration management • Vehicle maintenance management tied to odometer tracking which notifies the fleet manager

when vehicles are due for service • Automatic odometer reading for travel expenses • GPS-enabled vehicle tracking and tracing, which can be drawn via mapped reporting • Fuel monitoring and anti-siphoning measures

Workflows Items should move through an online workflow, so that approvals can happen online in a mapped orderly manner. Workflows should be mapped for procurements, human resources, travel, and journal entries. Workflows should move from a requestor to a reviewer to an approver. Items in the workflow should be easily viewed in their stages by the key stakeholders and retain the history for record-keeping purposes. Reporting To deliver a modern business intelligence solution for repetitive and ad hoc reporting needs on historical and operational data.

• Business Analytics (dashboards, financial modeling) • Reporting Tools • Report Design, Development, and Management • Standard Reports (Institutional-level Reporting, Donor-level Reporting, Country-level

Reporting, Program-level Reporting) • Flexible Date Ranges • Printable • Data Export, Downloadable • Consolidated reporting across business entities

At a minimum, Proposers must propose a solution that includes the modules identified above and any other modules.

Technical To provide a stable, secure, scalable, flexible, and recoverable IT architecture to support Anova Health Institute.

• Application Integration • Archiving • Audit Trails • Authentication • Business Continuity and Disaster Recovery • Data Integration and Management • Document Management • Fixes/Upgrades • Job Scheduling and Processing • Application and Data Security

These will be done with minimal disruption to the normal business operations of Anova.


P a g e 14 | 30

4.2 Key Functionality Anova is interested in adopting modern, automated tools that support financial and human resource best practices. Key functionality in these areas would include, but not be limited to: dashboards, mobility, employee portal with electronic and biometric time reporting, workflow, reporting, etc.

4.3 Implementation Timeline Anova is seeking guidance from the Proposers based on their experience for the recommended module phasing and timing. Proposers should clearly communicate all key assumptions along with their proposed schedule. Anova is open to suggestions for how best to implement the Proposer’s solution. The Proposer’s recommended implementation timeline should be clearly articulated in their proposal response as Section 6 – Implementation Approach and Work Plan. The Proposer is encouraged to conduct a phased launch, in which modules may be rolled out in phases to be completed by end of September 2020.

4.4 Requirements This section will describe how Anova Health Institute would like the new ERP system to operate. All costing should include a cloud-based approach compared against a hard installation on Anova’s local server. System Architecture Anova Health Institute will need the following environments at a minimum:

• Development; • Test; • Quality Assurance; • Production; • Training; and • Sandbox (for new features).

Upgrades and Future Releases Anova desires the ability with its new ERP system to apply software upgrades faster and with less expense and planning than the current product. Anova requires tools and/or services to assist in evaluating new releases, testing new functionality against existing configuration and integration settings, and selectively applying new features and releases – as well as robust support for informing and training end users on the new features and functions included in each release/upgrade. Anova’s selection of an ERP system product requires that the creator be a software partner for the term of the contract including all exercised renewal options. Anova requires that all products, and the education/training and research institution components of the product, has a demonstrated track record of delivering new features and functions specific to the international development industry, and that the product has a published roadmap showing robust and continuing investment in new product features and enhancements that will be applicable to Anova. Anova requires that software comply with future federal regulatory changes.


P a g e 15 | 30

Security Anova requires layered security to accomplish the requirements specified in the RFP. The new ERP system should:

• Control access to the system based on the user’s identity, role, and needs (e.g., staff, system administrator).

• Provide security and access controls at the database level. • Provide a means for users to identify and protect personally identifiable information (PII). • Provide data encryption in transit and at rest. • Provide data security when users access the application from a mobile system (note: Anova

does not employ a mobile device manager). • Keep logs of changes to data made by users, administrators, and automated processes. • Remain current with the latest security patches and fixes at every layer (application, database,

operating system). • Admin Level: ability to set up, and define user rights; auto reminders for back-ups; login IDs and

passwords set up and disable . • User Defined Security by Module: each user to have a password for particular module; Super

user abilities to allow those with multifunctional access. • Security within Module: require approvals to make changes for 'abnormal' functions, e.g.,

delete. • Encryption: File encryption and decryption rights to be limited to Admin level; Ability to share

encryption keys securely through emails or tokens. • Password functionality – complex, requires updates, such as quarterly password changes;

passwords to have a combination/mix of numbers, symbols, capital letters, and lower-case letters with a minimum length of 8 characters.

A breach of security creates risks for Anova Health Institute; therefore, Anova requires timely disclosure to system administrators of software security defects and hosting incidents, as well as timely incident remediation. Recoverability Anova’s ability to restore function and data in the event of a failure is mission critical, and recovery time objectives will be agreed with the Proposer prior to signing of a contract or purchase order. Performance Anova requires a high degree of performance from the new finance system such that it can provide rapid, consistent response times across its environments and system performance monitoring tools for system administrator use. Data Retention Anova’s users require access to project financial data that is up to six years old with the occasional need to access data up to 15 years old. Features of data management include:

• All data beginning October 1, 2019 must be migrated to the new systems. • Data is archived by funding source, not necessarily time period. After data has been archived,

summary level reporting should be available. • Until a funding source has been marked for archive users should have the ability to see actual

detail reporting and source documentation support. • Prior financial fiscal periods should be marked closed and not be able to be affected without

reopening the period by administrator access.


P a g e 16 | 30

5.0 Proposal Submission Requirements

5.1 General Instructions Proposals should be prepared simply and economically and provide a straightforward, concise description of the Proposer’s company, qualifications, proposed solution, and capabilities to satisfy the requirements of this RFP. Emphasis should be on completeness and clarity of content. Proposals must be organized consistent with the outline provided in this section. Proposers must follow all formats and address all portions of the RFP set forth herein, providing all information requested. Proposers may retype or duplicate any portion of this RFP for use in responding to the RFP, provided that the proposal clearly addresses all of Anova’s information requirements.

5.2 Proposal Format and Content Information must be structured, presented, and labeled in the following manner:

• Cover Letter • Table of Contents • Section 1 – Executive Summary • Section 2 – Company Background • Section 3 – Company Qualifications • Section 4 – References • Section 5 – Proposed Solution • Section 6 – Implementation Approach and Work Plan • Section 7 – Hosting and Support • Section 8 – Pricing • Section 9 – Software Licensing and Maintenance Agreements Information should be prepared

on standard A4 paper. • Section 10 – BB-BEE status level of contribution

Failure to follow the specified format, to label the responses correctly, or to address all the subsections may, at Anova’s sole discretion, result in the rejection of a proposal. Cover Letter The proposal must include a cover letter that provides the following:

• Proposer’s legal name and corporate structure, including the location of incorporation. • Proposer’s primary contact to include name, address, phone, and email. • Solution name, and version, and confirmation the solution is a Software-as-a-Service (SaaS)

approach and/or an Infrastructure-as-a-Service (IaaS) or Platform-as-a-Service (PaaS) solution. • Identification of subcontractors (if any) and scope of work to be performed by subcontractors. • Identification of any pending litigation against the Proposer. • Disclosure of any bankruptcy or insolvency proceedings in last ten (10) years. • Statement indicating the proposal remains valid for at least 120 days. • Statement that the Proposer, or any individual who will perform work for the Proposer, is free

of any conflict of interest (e.g., employment by Anova Health Institute). • Statement of acknowledgement that Anova’s RFP documents have been reviewed and accepted

with or without exception. If exceptions are involved, those items requiring adjustment or modification must be identified and listed along with suggested modifications to the contract. If


P a g e 17 | 30

no exceptions are noted, Anova will assume that the Proposer can perform all normal tasks and services without reservation or qualification to the contract.

• Signature of a company officer empowered to bind the Proposer to the provisions of this RFP and any contract awarded pursuant to it.

The Cover Letter should be concise and brief and not exceed three (3) pages unless a Proposer’s exceptions to Anova’s legal documents require it. Table of Contents All sections should be identified and pages consecutively numbered. Section 1 – Executive Summary This section of the proposal should provide a brief and concise synopsis of the Proposer’s proposal and a description of the Proposer’s credentials to deliver the services sought under the RFP. This is to include the name and version of the solution proposed. The Executive Summary should not exceed three (3) pages. Section 2 – Company Background This section of the proposal should identify the following:

2.1 A brief description of the Proposer’s background. 2.2 Identify the location of headquarters, technical support, and field offices and the location

of the office that would service Anova. The Background section should not exceed three (3) pages. Section 3 – Company Qualifications In this section of the proposal, the Proposer should identify company qualifications and experience in implementing solutions like what Anova Health Institute is seeking:

3.1 Describe the Proposer’s familiarity with public sector ERP systems and associated business processes, and experience with the requirements of NGOs.

3.2 Identify the Proposer’s existing client base including the number of existing clients using the version/release of the software being proposed. Specifically identify experience with similar sized local organizations that receive USG funding.

3.3 Provide a list of all clients using the proposed solution The Company Qualifications section should not exceed three (3) pages. Section 4 – References The Proposer must provide at least five (5) references with at least three (3) of the references for systems that have been implemented in the last five years. References should be for the same product version/release as that being proposed. Anova prefers references from international development organizations of similar size and complexity to Anova. For each reference, Proposer must provide the following information:

4.1 Name and contact information (i.e., name, title, address, phone, and email) 4.2 Brief project description, including identifying the software version, modules, and interfaces

implemented 4.3 Implementation timeline, go live date, original cost, and actual cost


P a g e 18 | 30

Section 5 – Proposed Solution In this section of the proposal, the Proposer should describe the proposed solution by providing the following:

5.1 Solution Overview • Name and origin of solution • Release history and current release being proposed • Proposed modules • Mobile capabilities of the proposed modules • Roles and responsibilities of Proposer vs. Anova

5.2 Application Integration/Interface. Please describe the following for each specific integration/ interface: • Proposer’s integration/interface solution (web services, Application Programming

Interfaces (APIs), etc.) • Data availability/transfer (real-time, nightly, etc.) • How Proposer will ensure data security • The involvement, if any, that is required from the owners of the applications to be

integrated/interfaced to the ERP • The involvement, if any, that is required from Anova of the applications to be

integrated/interfaced to the ERP • If Proposer has previous experience developing/implementing the relevant

integration/interface 5.3 Data Storage and Backup

• Describe approach to data storage • Describe data backup process • Describe the network bandwidth required between Anova and hosting facilities • Describe what options are available for dedicated bandwidth (if available) • Describe scalability options for computing power (CPU, RAM, and storage)

5.4 Data Access and Security • Describe how data access is managed • Describe the environment (single or multi-tenant) • Describe how environment security is managed • If a multi-tenant environment, how is the data segregated? • If a multi-tenant environment, how is security managed?

5.5 Business Continuity and Disaster Recovery • Describe approach to business continuity & disaster recovery

5.6 Service Level Agreements (SLAs) • Describe supported SLA options (e.g. reliability, availability, performance, issues, requests,

system response time, etc.) 5.7 Transition

• Describe proposed exit strategy at contract transition

Section 6 – Implementation Approach and Work Plan The Proposer should describe the proposed implementation approach to include the following:

6.1 Provide a Project Schedule that identifies implementation tasks, activities, dates, durations, resources, deliverables, and milestones (ensuring that the development, testing, and implementation of all required integrations/interfaces are accounted for). Noting that Anova desires to acquire and implement the new ERP system during fiscal year 2020 with the first systems inclusive of payroll, finance and accounting


P a g e 19 | 30

implemented not later than January 1, 2020 to ensure full testing and refinement of the first systems prior to the end of the tax year on February 28, 2019 and final systems in a phased approach implemented not later than July 31, 2019 to ensure full testing and refinement in the final two months of the fiscal year.

6.2 Provide a project organization chart that identifies proposed staff – in response to this, also

include a discussion of how Proposer will address any issues Anova may have with staff needed to support the proposed solution.

6.3 Provide bios for key staff: Bios with CV inclusive for key staff should not exceed three pages for each staff member.

6.4 Provide a staffing matrix in the format of Exhibit 6 below that identifies the specific roles/ responsibilities to be filled by Proposer or subcontractor staff versus those to be filled by Anova staff. As part of this matrix, identify estimated level of effort for each staff person and when that person would be required (what part of implementation).

6.5 Describe Proposer’s project management methodology – this should be in the form of a Project Plan that addresses the Proposer’s approach to Change Management, Risk Management, Issues Management, Communications Management, etc.

6.6 Describe the roles and responsibilities of Anova staff during implementation and provide an estimated level of effort (%) for Anova versus the Proposer.

6.7 Describe the conversion strategy, including what data should be converted, the number of years of data to convert at a minimum going back to October 1, 2019 (beginning of fiscal year 2020), and the conversion methodology (extract, transform, and load).

6.8 Describe Proposer’s training methodology and how you ensure users are prepared to use the proposed solution; include description of approach to training for different learning styles (classroom, online, hands-on, etc.). Proposers must describe the training to be provided for each specific module being proposed.

6.9 Describe your testing methodology to include the criteria and methods to ensure successful completion of user acceptance testing prior to Go Live.

The Implementation Approach and Work Plan section should not exceed fifteen (15) pages (excluding the project schedule).


Table 2: Proposed Staffing Matrix

Task Phases (Task Start – Task End) Proposer Staff (Role) Anova Staff (Role) Task Hours Work Split

(% Vendor/% Anova)

P a g e 20 | 28


P a g e 21 | 30

Section 7 – Hosting and Support In this section of the proposal, the Proposer should address the following:

7.1 Describe ongoing hosting and support services including help desk processes and procedures,

support hours (in South African time), escalation procedures, and response time

commitments.

7.2 Describe the frequency that application patches and releases have been made available within

the past two (2) years, and how upgrades and patches are applied, specifically describing your

notification process and Anova’s ability to delay, test, accept, and/or deny applying changes.

7.3 Describe how you would complete a Post-Implementation Evaluation Report (PIER) that

evaluates whether project objectives were met, determines how effectively the project was

run, ensures that the organization gets the greatest possible benefit from the project, and a

full week of follow-up training for each separate implementation: Finance, HR/Payroll, etc.

7.4 Describe any solution user groups and/or conferences.

The Hosting and Support section should not exceed five (5) pages.

Section 8 – Pricing/Cost Proposal Anova Health Institute seeks a clear and comprehensive understanding of all costs associated with the

implementation and ongoing maintenance of the proposed system. The Cost Proposal should be

presented in Excel and attached along with the PDF proposal submission. The Proposer is responsible for

ensuring the integrity of their calculations, references, and formatting. All costing should include a

cloud-based approach compared against a hard installation on Anova’s local server.

Proposers must itemize all costs associated with the implementation and ongoing maintenance. In

addition to the evaluation criteria in Section 6 of this RFP, Anova will evaluate information based on

the “Total Cost to Implement (TCI)” and the “Total Cost to Operate (TCO).” TCI will include all costs

required for a successful implementation and should assume a fixed fee model. The TCO should be

calculated based on TCI plus five (5) years of annual maintenance and licensing fees.

Proposers must identify all costs required to complete a successful implementation to include:

• Licensing and Costs

• Services

• Project management

• Implementation, installation, configuration, and testing

• Data conversion and migration

• Interface development

• Training and documentation

• Travel

Proposer’s hosting costs should clearly identify the annual costs for five (5) years inclusive of:

• Hosting

• Support

• PIER and additional training

Section 9 – Software Licensing and Maintenance Agreements To address this section, the Proposer must provide any software licensing and maintenance agreements

that will be required to implement the Proposer’s solution.


P a g e 22 | 30

Section 10 – BB-BEE Certifications In this section, please provide a copy of your BB-BEE certification.


P a g e 23 | 30

6.0 Proposal and Finalist Presentation Evaluation 6.1 Proposal Evaluation Criteria An Anova Health Institute Evaluation Committee will review all information to determine which

Proposers have qualified for consideration. The evaluation will include at least an initial review and a

subsequent detailed review. The initial review will evaluate all submissions for conformance to stated

specifications to eliminate all responses that deviate substantially from the basic intent and/or fail to

satisfy the mandatory requirements. Only those that meet or exceed the intent of the mandatory

requirements will be further evaluated.

Submitted proposals will be evaluated on the following criteria:

• Quality, clarity, and responsiveness of proposal;

• Ability to meet the needs of Anova Health Institute;

• Well thought out timeline and roadmap to support go live with a phased approach;

• Proven technical ability to design, install, and support the proposed system;

• Demonstrated ability to work in a cooperative and collaborative manner with clients;

• Anticipated value and price;

• Perceived risk or lack thereof;

• References;

• Results of interviews and/or demonstrations;

• Ability to prepare and execute a contract in a timely manner;

• Commitment to continually evolving the system to remain current with evolving best practices;

and

• BB-BEE status level of contribution.

Proposals will be evaluated as follows: Quality and range of methods and tools used to assess and deliver

leadership and executive coaching services 20%

Timeline for service delivery 15%

Past-performance with one-on-one coaching and group coaching/

training 15%

Quality of Personnel CVs and staff approach proposed 10%

Value for money demonstrated in cost proposal 20%

BB-BEE status level of contribution 20%

Value for Money will be evaluated using the following equation: A maximum of 20 points will be

allocated to Price/Cost on the following basis:

Np = 20 {1 - (P - Pm)}

Pm

Where: Np = the number of bid adjudication points awarded for price

Pm = the price of lowest responsive bid, adjusted to a common base if applicable.

P = the price of the responsive bid under consideration, adjusted to a common base if applicable.


P a g e 24 | 30

Percentage points will be allocated as follows for the BB-BEE component: BBBEE Status Level of

Contribution Number of Percentage Points

1 20

2 18

3 16

4 14

5 8

6 6

7 4

8 2

Non-compliant contributor 0

Anova reserves the right, at its sole discretion, to request clarifications of proposals or to conduct

discussions for the purpose of clarification with any or all Proposers. The purpose of any such

discussions shall be to ensure full understanding of the proposal. Discussions shall be limited to specific

sections of the proposal identified by Anova and, if held, shall be after initial evaluation of proposal is

complete. If clarifications are made as a result of such discussion, the Proposer shall put such

clarifications in writing.

6.2 Presentation Evaluation Criteria Three to five finalists, depending upon the response received to this RFP, will be selected using the

proposal evaluation criteria in Section 6.1 above.

The presentation/ demonstration of each finalist will be evaluated using the following criteria:

Clarity of presentation and responsiveness to Anova’s ERP needs 35%

Organisation of the presentation 15%

Timeliness – you will be given 30 minutes to present followed by a 30-

minute session of questions and answers 15%

Responsiveness to questions 35%

The rubric for these criteria will be shared with finalists when scheduling the presentations.


P a g e 25 | 30

7.0 RFP Terms and Conditions A. Collusion By submitting a response to the RFP, each Proposer represents and warrants that its response is genuine

and not made in the interest of or on behalf of any person not named therein; that the Proposer has not

directly induced or solicited any other person to submit a sham response or any other person to refrain

from submitting a response; and that the Proposer has not in any manner sought collusion to secure any

improper advantage over any other person submitting a response.

B. Bribery No party or person will offer, give, or agree to give any Anova Health Institute employee or its

representatives any bribe, discount or offer of employment in connection with the award of contract

by Anova. No Anova employee or its representatives will solicit, demand, accept or agree to accept

from any other party or person a bribe, discount or offer of employment in connection with an Anova

Health Institute contract. No party or person will take any action that would cause any party to this

engagement to be in violation of any applicable anti-corruption and anti-bribery law, including the U.S.

Foreign Corrupt Practices Act.

C. Required Review and Waiver of Objections by Proposers Proposers should carefully review this RFP and all attachments. Comments concerning RFP objections

must be made in writing and received by Anova Health Institute no later than the "Deadline for Proposal

Questions" detailed in Table 1 - RFP Timeline. This will allow issuance of any necessary amendments and

help prevent the opening of defective information upon which contract award could not be made.

Protests based on any objection will be considered waived and invalid if these faults have not been

brought to the attention of Anova, in writing, by the Deadline for Proposal Questions.

D. Nondiscrimination No person will be excluded from participation in, be denied benefits of, be discriminated against in the

admission or access to, or be discriminated against in treatment or employment in Anova’s contracted

programs or activities on the grounds of disability, age, race, color, religion, sex, national origin, or any

other classification protected by law; nor will they be excluded from participation in, be denied benefits

of, or be otherwise subjected to discrimination in the performance of contracts with Anova or in the

employment practices of Anova’s contractors.

E. Proposal Preparation Costs Anova will not pay any costs associated with the preparation, submittal, or presentation of any proposal.

F. Proposal Withdrawal To withdraw a proposal submitted prior to the Deadline for Proposal Submissions, the Proposer must

submit a written request, signed by an authorized representative, to the RFP Coordinator (Section 1.4).

After withdrawing a previously submitted proposal, the Proposer may submit another proposal at any

time up to the Deadline for Proposal Submissions.


P a g e 26 | 30

G. Proposal Errors Proposers are responsible for all errors or omissions contained in their information. Proposers will not

be allowed to alter proposal documents after the Deadline for Proposal Submission.

H. Incorrect Proposal Information If Anova determines that a Proposer has provided, for consideration in the evaluation process or

contract negotiations, incorrect information which the Proposer knew or should have known was

materially incorrect, that proposal will be determined non-responsive, and the proposal will be rejected.

I. Assignment and Subcontracting The Proposer may not subcontract, transfer, or assign any portion of the contract without prior, written

approval from Anova.

Notwithstanding the use of approved subcontractors, the Proposer, if awarded a contract under this

RFP, will be the prime contractor and will be responsible for all work performed and will be responsible

for all costs to subcontractors for services provided by the Proposer.

J. Proposal of Additional Services If a Proposer indicates an offer of services in addition to those required by and described in this RFP,

these additional services may be added to the contract before contract signing at the sole discretion of

Anova.

K. Licensure Before a contract pursuant to this RFP is signed, the Proposer must hold all necessary, applicable

business and professional licenses. Anova may require any or all Proposers to submit evidence of proper

licensure.

L. Ethical Business Practices No employee, officer, or agent of the Proposer shall participate in the selection, award or administration

of any contract supported by Anova funds if a conflict of interest is involved. A conflict of interest will

also be deemed to exist if the Proposer or any of its agents, employees, officers, any immediate or

extended family members, partners, or an organization, which employs or is about to employ any of the

parties indicated herein, has a financial or other interest in the firm selected for an award.

The employees, officers or agents of the Proposer shall not give, directly or indirectly, any payments to

any business partner(s) or members of their immediate families, nor shall any employees, officers or

agents of the Proposer use any part of the Contract funds for payments to organizations in which the

Proposer, its employees, officers or agents or member(s) of their respective immediate families, have a

financial interest.

The remuneration of the Proposer shall constitute the sole remuneration in connection with the

Contract. The Proposer shall not accept for its own benefit any trade commission, discount or similar

payment in connection with activities pursuant to this Contract or the discharge of its obligations

hereunder. The Proposer shall ensure that any subcontractors, as well as the personnel and agents of

any of them, similarly, shall not receive any such remuneration.


P a g e 27 | 30

M. Contract Negotiations After a review of the information and completion of the demonstration and proof-of-capabilities (POC),

Anova intends to enter into contract negotiations with the selected Proposer. These negotiations could

include all aspects of services and fees. If a contract is not finalized in a reasonable period of time,

Anova will open negotiations with the next ranked Proposer.

N. Execution of Contract If the selected Proposer does not execute a contract with Anova within fifteen (15) business days after

notification of selection, Anova may give notice to that service provider of Anova’s intent to select from

the remaining Proposers or to call for new information, whichever Anova deems appropriate.

O. Right of Rejection Anova reserves the right, at its sole discretion, to reject any and all information or to cancel this RFP in

its entirety.

Any proposal received which does not meet the requirements of this RFP may be considered

nonresponsive, and the proposal may be rejected. Proposers must comply with all the terms of this RFP

and all applicable laws and regulations. Anova may reject any proposal that does not comply with all the

terms, conditions, and performance requirements of this RFP.

Proposers may not restrict the rights of Anova or otherwise qualify their information. If a Proposer

does so, Anova may determine the proposal to be a nonresponsive counter offer, and the proposal

may be rejected.

Anova reserves the right, at its sole discretion, to waive variances in technical information provided such

action is in the best interest of Anova. Where Anova waives minor variances in information, such waiver

does not modify the RFP requirements or excuse the Proposer from full compliance with the RFP.

Notwithstanding any minor variance, Anova may hold any Proposer to strict compliance with the RFP.

Q. Disclosure of Proposal Contents All information and other materials submitted in response to this RFP procurement process become the

property of Anova. Selection or rejection of a proposal does not affect this right. All proposal

information, including detailed price and cost information, will be held in confidence during the

evaluation process.

R. Proprietary Information Each Proposer may clearly label part of a proposal as "CONFIDENTIAL" if the Proposer thereby agrees to

indemnify and defend Anova for honoring such a designation. The failure to so label any information will

constitute a waiver of all claims for damages caused by any release of the information.

S. Severability If any provision of this RFP is declared by a court to be illegal or in conflict with any law, the validity of

the remaining terms and provisions will not be affected; and, the rights and obligations of Anova and

Proposers will be construed and enforced as if the RFP did not contain the particular provision held to

be invalid.


P a g e 28 | 30

T. RFP and Proposal Incorporated into Final Contract This RFP and the successful proposal will be incorporated into the final contract.

U. Proposal Amendment Anova will not accept any amendments, revisions, or alterations to information after the Deadline for

Proposal Submission unless such is formally requested, in writing, by Anova.

V. Consultant Participation Anova Health Institute reserves the right to share, with any consultant of its choosing, this RFP and

proposal responses in order to secure a second opinion. Anova may also invite said consultant to

participate in the Proposal Evaluation process.

W. Warranty The selected Proposer will warrant that the proposed software will conform in all material respects to

the requirements and specifications as stated in this RFP, demonstrated in both the software

demonstration and subsequent proof-of-capabilities. In addition, the selected Proposer will warrant

that it rightfully possesses the right, title, or interest to the intellectual property (IP) necessary for any

underlying technology implicated by or involved with their proposed technological solution. Further,

that the requirements as stated in this RFP will become part of the selected Proposer’s license and the

Proposer will warrant to the requirements. The selected Proposer must warrant that the content of its

proposal accurately reflects the software's capability to satisfy the functional/technological

requirements as included in this RFP. Furthermore, the warranty, at a minimum, should be valid for the

duration of the implementation and until final acceptance (as will be defined during the negotiation

process) of all application modules included in the implementation.

X. Rights of Anova Health Institute Anova reserves the right to:

• Make the selection based on its sole discretion;

• Reject any and all information;

• Issue subsequent Requests for Proposal;

• Postpone opening proposals, if necessary, for any reason;

• Remedy errors in the Request for Proposal process;

• Approve or disapprove the use of specific subcontractors;

• Negotiate with any, all, or none of the Proposers;

• Accept other than the lowest offer;

• Waive informalities and irregularities in the proposal; and

• Enter into an agreement with another Proposer in the event the originally selected Proposer

defaults or fails to execute an agreement with Anova.

An agreement will not be binding or valid with Anova unless and until it is approved by Anova and

executed by authorized representatives of Anova and of the Proposer.

Y. Indemnification The Proposer shall indemnify and hold harmless Anova, its directors, offices, employees, agents,

representatives, and their respective heirs, legal representatives, successors, assigns, and affiliates, from

and against any and all loss, damage, claims, causes of action, liabilities, and lawsuits whatsoever


P a g e 29 | 30

including all costs, expenses, and attorneys’ fees arising out of, or in any way related to the Proposer’s

(and Proposer’s employees and independent contractors) obligations or performance following from

this RFP. Proposer agrees to give Anova immediate notice of any claim, action, or lawsuit in any way

connected with this RFP. This provision shall survive the term of this RFP.

Z. Confidentiality The Proposer and Anova agree that verbal or documentary information shared by Anova with the

Proposer and/or its agents (including other organizations, entities, or individuals working with the

Proposer on this RFP) creates a relationship of trust and confidence between the parties. Proposer

agrees that it will not use or disclose, or allow anyone else to use or disclose any Confidential

Information relating to the activities, products, or business affairs of Anova, or any information created,

discovered, or developed by or for Anova, or acquired by Anova, that has commercial value in Anova’s

present or future business, except as may be necessary in the pursuit and performance of work related

to this RFP and pursuant to prior written authorization from appropriate officials of Anova. By way of

illustration, but not limitation, Confidential Information includes processes, formulas, data, know-how,

inventions, improvements, techniques, marketing plans, product plans, strategies, forecasts, donor lists,

fundraising tools, proposals, health information, and any other information Proposer has reason to

know Anova would like to treat as confidential for any purpose. Proposer agrees to keep confidential

information secret whether or not any document containing such information is marked confidential.

The Proposer recognizes and agrees that Confidential Information received from Anova shall remain

solely Anova’s property and constitute proprietary information. The parties acknowledge that failure to

comply with the terms of this Agreement may cause irreparable damage, and Anova may be entitled to

specific performance, injunctive relief, or other equitable relief to prevent such damage or further

damage regarding its Confidential Information.

Upon notification of selection of a vendor, the Proposer shall return to Anova any and all Confidential

Information in written or other tangible form that it has received or compiled and that is within its

possession or control. In addition, the Proposer shall destroy all copies of any analyses, notes,

memoranda, diagrams, compilations, studies, or other documents that it has prepared containing or

reflecting any Confidential Information.

AA. Compliance with Laws The Proposer is and will remain in compliance with all US and country laws, rules, and regulations

(including those in 2 CFR 200) applicable to and binding upon it and relating to its performance,

including without limitation, those of the United States and foreign jurisdictions, charitable solicitations,

if applicable, and such other regulations that are or may become applicable to this RFP.

BB. Governing Law The parties engaging in this RFP and any subsequent Contract agree that it shall be governed by the laws

of the Republic of South Africa.

CC. Preventing Terrorist Financing – Implementation of E.O. 13224 The Proposer represents and warrants that it is not an organization associated with, engaged in, or that

provides resources or support to individuals and organizations associated with terrorism, including

those individuals or entities that appear on the Specially Designated Nationals and Blocked Persons List

maintained by the U.S. Treasury or the United Nations Security designation list.


P a g e 30 | 30

DD. Debarment, Suspension, Ineligibility, and Voluntary Exclusion The Proposer certifies that neither it nor its principals is presently excluded or disqualified from

participation in this transaction by any U.S. federal department or agency.

anova health institute · 5.1 general instructions 16 5.2 proposal format and content 16 cover...

Documents