Investigation into the over payment of public funds by the university of sydney for security services (Operation Gerda)
- Findings
- 7
- Recommendations
- 24
- Published responses
- 2
- Report length
- 100 pages
Findings 7
Allegations are not findings. A commission's finding or opinion of corrupt conduct or misconduct is not a finding that a person is guilty of a criminal offence, and the commissions say so in their reports.
serious corrupt conduct
FindingThe Commission is satisfied that Emir Balicevac, an SNP employee, engaged in serious corrupt conduct in that his conduct impaired or could impair public confidence in public administration and could also involve obtaining or assisting in obtaining, or dishonestly benefiting from, payment of public funds for private advantage.
serious corrupt conduct
FindingThe Commission is also satisfied that Mr Balicevac engaged in serious corrupt conduct in that his conduct involved conduct that adversely affects, or could adversely affect, either directly or indirectly, the honest or impartial exercise of official functions by a public official.
serious corrupt conduct
FindingThe Commission is satisfied that Daryl McCreadie, also an SNP employee, engaged in serious corrupt conduct in that his conduct impaired or could impair public confidence in public administration and could also involve obtaining or assisting in obtaining, or dishonestly benefiting from, payment of public funds for private advantage.
serious corrupt conduct
FindingThe Commission is satisfied that George Boutros, an SIG security guard, engaged in serious corrupt conduct in that his conduct impaired or could impair public confidence in public administration and could also involve obtaining or assisting in obtaining, or dishonestly benefiting from, payment of public funds for private advantage.
serious corrupt conduct
FindingThe Commission is satisfied that Taher Sirour, the director and CEO of SIG, engaged in serious corrupt conduct in that his conduct impaired or could impair public confidence in public administration and could also involve obtaining or assisting in obtaining, or dishonestly benefiting from, payment of public funds for private advantage.
serious corrupt conduct
FindingThe Commission is also satisfied that Mr Sirour engaged in serious corrupt conduct in that his conduct involved conduct that adversely affects, or could adversely affect, either directly or indirectly, the honest or impartial exercise of official functions by a public official.
serious corrupt conduct
FindingThe Commission is satisfied that Mr Smith engaged in serious corrupt conduct in that his conduct involved conduct that adversely affects, or could adversely affect, either directly or indirectly, the honest or impartial exercise of his official functions.
Recommendations 24
Recommendation 1
That the University ensures that key tender documentation, such as procurement strategies, tender evaluation plans and tender evaluation committee (TEC) reports, include a realistic and detailed assessment of procurement and contract risks. This assessment should be conducted in a manner that incorporates operational risks and complies with the risk management principles in the International Standard on Risk Management ISO 31000:2018.
Recommendation 2
That the University amends its Guidelines for using the risk assessment tool to provide more detailed guidance on major contract risks.
Recommendation 3
That the University assesses contract assurance frameworks that cover key risks involved in the provision of services, such as a reliance on subcontracting, when assessing the capability and capacity of tenderers.
Recommendation 4
That the chief procurement officer formally reviews requests for tender (RFTs) for high-risk tenders and tender evaluation plans for significant procurement undertakings.
Recommendation 5
That the University should review its tender assessment criteria and weightings to avoid perceptions that unwarranted advantages are provided to a particular tenderer.
Recommendation 6
That probity walls and/or other safeguards should be established where there is a risk that someone connected to a tenderer could access confidential information about a tender process and tenderers’ submissions.
Recommendation 7
That the University should ensure consistency across its tender documentation concerning how tenders will be evaluated.
Recommendation 8
That the University should continue to assess all tenderers and, where relevant, their supply chains to ensure compliance with Awards.
Recommendation 9
That all TEC chairs and/or appointed probity advisers should ensure that tender scoring methodologies are clear to evaluators and that the tender assessment criteria have been followed.
Recommendation 10
That tender reports to the Finance and Audit Committee (FAC) and the tender board should contain adequate information to enable key issues to be understood. The information should include: tenders’ assessment criteria scores key contract risks and their mitigation key assumptions any significant probity concerns and the manner in which they were resolved.
Recommendation 11
That the University should ensure all future contracts for the provision of security services include adequate provisions covering: subcontracting terms contractor assurance frameworks right-to-audit clauses timesheet access technology requirements.
Recommendation 12
That security contractors should be required to provide evidence that they have properly implemented internal controls to ensure that security staff (including subcontractors) have completed their duties in accordance with the contract and work orders.
Recommendation 13
That the University should document its internal contractor controls. A report of the conduct of the controls, exceptions to the controls and the resolution of those exceptions should be given to relevant managers in CIS.
Recommendation 14
That the University should perform random checks that security guards are on duty. These could include GPS monitoring, reviewing CCTV and access records, and surprise visits to certain locations.
Recommendation 15
That there should be a regular rotation between at least two University employees who undertake contractor checks to ensure that security services are provided.
Recommendation 16
That the University should have access to guard timesheets. The University should also inspect the timesheets to ensure compliance with legislative requirements and the contract, and to help confirm charges on invoices.
Recommendation 17
That security contractors should be required to provide specimen signatures against which the signatures of guards should be checked.
Recommendation 18
That the University should have key performance indicators (KPIs) in place that cover the essential requirements for the provision of security services. It should also ensure KPI monitoring for security contracts is based on data that is trustworthy, measurable and relevant, and that reliance on contractor self-reporting is minimalised.
Recommendation 19
That the University should develop controls to identify when contract variations exceed 10% of the original contract amount. It should also clarify that a sufficiently senior delegate is required to scrutinise and approve cumulative ad hoc contract payments that exceed 10% of the contract value.
Recommendation 20
That the University considers sharing some contract management duties between internal staff, who are co-located with security contractors, and staff, who do not have day-to-day contact with security contractors.
Recommendation 21
That the University should develop a code of business practice or similar document and contractually bind major suppliers to comply with it. The document should include: a prohibition on suppliers or potential suppliers offering gifts and benefits a prohibition on actions that place University staff or other individuals in the supply chain in conflict of interest situations a requirement for suppliers to have comparable provisions in contracts with subcontractors or other companies in the supply chain details of where people can make reports (including anonymous reports) of breaches of the code of business practice.
Recommendation 22
That the University should establish a clear mechanism, and one that is clearly communicated, for the staff of suppliers and subcontractors to report corrupt conduct.
Recommendation 23
That the University adopts a fraud and corruption control plan that appropriately addresses the risks of fraud and corruption. Among other things, the plan should reflect the findings made in previous Commission investigation reports concerning universities and ensure that the corruption prevention issues are not dealt with in isolation, but that the cumulative implications are properly considered.
Recommendation 24
That all internal audit reports should be given to the director of internal audit and reported to the FAC. The internal audits should be reviewed by an internal audit manager to assess the implications of the report and whether there are red flags of possible fraud and corruption. If necessary, internal auditors’ working papers should also be obtained.
Published responses 2
Coverage
This publisher
- Reports on investigations made public before 2016 are not online: the ICAC keeps only a summary for each, and copies must be requested from the ICAC. Those records hold the ICAC's published summary; findings and recommendations are not extracted.
- The ICAC copyright statement reserves all rights (fair dealing aside). OPAX keeps short verbatim finding and recommendation passages with links to the original report.
- Findings are read from the summary chapter of each report PDF. Where a finding's particulars run past the cited page only the finding statement is kept, and reports whose layout could not be read confidently are marked not_extracted.
- Agency action plans and progress reports are listed as documents; their contents (implementation status for each recommendation) are not parsed.
- Report PDFs without a text layer (scanned images, for example Operation Scania) are not OCRed; their findings stay not_extracted.
- Many pre-2016 summaries give only the month a report was made public; those records carry no date and a note with the month, because the schema holds day-level dates only.