You won't find "Savoir-Faire GNU/Linux Certification" in any official Canadian government procurement documentation. Why? Because it doesn't exist as a formal requirement. This appears to be a misconception—possibly conflating vendor qualifications around open-source expertise with a specific branded certification program. What you will find in federal IT procurement are requirements for open standards, interoperability, and vendor experience with Linux and open-source platforms, but not mandates for particular third-party certifications.
How It Works
Here's the thing: Canadian procurement policy does emphasize open-source solutions where feasible. The Treasury Board's Directive on Service and Digital, which came into effect April 1, 2022, encourages departments to prioritize open standards and consider open-source alternatives during technology acquisition. But this doesn't translate into requiring vendors to hold certifications from private entities like Savoir-Faire Linux (a Quebec-based open-source services company) or any similar organization.
In practice, when PSPC or individual departments evaluate IT vendors for standing offers or specific contracts, they assess experience and capability through past performance, case studies, technical proposals, and sometimes technical interviews or live demonstrations. The Government of Canada Supply Manual—the authoritative source for federal procurement procedures—outlines vendor qualification processes but makes zero reference to this or similar branded certifications as prerequisites.
What sometimes creates confusion is that RFPs may ask vendors to describe their team's qualifications with specific technologies, including GNU/Linux distributions. Vendors might voluntarily cite industry certifications (Red Hat Certified Engineer, Linux Professional Institute credentials, etc.) or training from organizations like Savoir-Faire Linux to strengthen their bids. That's vendor strategy, not government requirement. The evaluation criteria focus on meeting technical specifications and demonstrating actual competence, not checking boxes for specific certification programs.
Key Considerations
- No section in the Supply Manual addresses this certification because it's not a government-recognized credential. Always verify requirements against official Treasury Board policies and the specific RFP language rather than assumptions about what might be required.
- Open-source requirements in Canadian procurement relate to standards and interoperability—ensuring systems can work together and avoiding vendor lock-in—not mandating particular commercial training programs or certifications.
- Departments like Shared Services Canada (SSC) increasingly specify open-source technologies in their technical requirements, but vendor qualification still flows through established processes: PSPC registration, supply arrangements, and proposal evaluation based on experience and technical merit.
- If you're a vendor preparing a bid and see language about Linux or open-source expertise, respond with your actual experience, qualified personnel, and relevant industry certifications if you hold them—but don't assume you need a specific credential unless it's explicitly listed in the solicitation.
Related Terms
Open Standards, Standing Offers, Supply Arrangement, Technical Evaluation Criteria, Vendor Qualification
Sources
- Government of Canada Supply Manual - Official federal procurement policy and procedures
- Treasury Board Directive on Service and Digital (2022) - Policy framework for government IT and digital services
- Treasury Board Policy on Service and Digital - Overarching policy on technology acquisition and standards
Bottom line: focus on demonstrating real open-source capability and meeting the specific technical requirements in each solicitation. The government cares about what you can deliver, not which branded certification programs you've attended.