AppleCare OS Support for Cellular Devices

Normalized category

Executive summary

This document (Version 1.4, dated April 1, 2019) provides comprehensive standard instructions that apply to all Shared Services Canada procurement documents. It establishes uniform rules for bidders across all types of solicitations including RFPs, RFQs, Invitations to Qualify, Requests for Standing Offers, and Requests for Supply Arrangements. The instructions cover mandatory procedural requirements such as question submission protocols, bid submission formats, evaluation methodologies, security clearance requirements, and conflict-of-interest determinations. It includes detailed certifications that bidders must provide (off-the-shelf products, employment equity compliance, former public servant disclosure, OEM certifications, software publisher authorizations, and code of conduct attestations). The document also establishes Canada's general rights during procurement (bid rejection, negotiation, electronic auctions, cancellation) and specifies evaluation procedures including discretionary rights such as clarification requests, facility surveys, customer reference checks, demonstrations, and sample submissions. Special provisions address telecommunications procurements subject to CRTC regulation, with distinct regulatory forms (A, B, C, D) for different tariff scenarios. The instructions emphasize bid integrity, financial capability assessment, and protection against conflicts of interest or unfair advantage.

Mandatory requirements

1. 01Bidder must have legal capacity to contract; sole proprietorships, partnerships, and corporate bodies must provide registration/incorporation documentation if requested
2. 02Procurement Business Number (PBN) required before award of any contract or resulting instrument
3. 03For joint venture bidders: clearly indicate joint venture status, provide name of each member, PBN of each member, name of representative member, and name of joint venture if applicable
4. 04Bids must not be assignable or transferable; substitute bidders will not be accepted
5. 05All equipment and software bid must be 'off-the-shelf' unless otherwise stated—no further research or development; if fully compatible extension, must be publicly announced by closing date
6. 06All systems bid must be 'off-the-shelf' with field-proven operational history; all equipment and software components must be standard and commercially available
7. 07Bidder certifies all proposed individual resources will be available to perform the work as required by Canada at the time specified
8. 08Bidder has verified all information in résumés and supporting material (education, achievements, experience, work history) to be true and accurate
9. 09If resources are not employees of bidder, bidder must have written permission from those individuals to propose their services and submit their résumés
10. 10For non-employee resources: bidder must provide written confirmation signed by individual confirming permission and availability upon request
11. 11All bids must include mandatory requirements compliance attestations; any bid expressing non-compliance with mandatory requirements will be declared non-compliant
12. 12Bids must be signed by bidder or authorized representative; joint venture bids must be signed in accordance with joint venture provisions
13. 13Bids must be submitted in English or French; supporting information may be in either official language
14. 14Bids must include title page for each section with title, date, solicitation number, bidder name and address, and contact information
15. 15Bids must include table of contents for each section
16. 16For joint venture bids: all members may be required to sign bid and resulting contract unless one member appointed as representative
17. 17Financial bid must include all costs for entire contract period including any option years; identification of all necessary equipment, software, peripherals, cabling, and components is bidder's sole responsibility
18. 18Prices must be single, firm, all-inclusive price per line item unless solicitation indicates otherwise
19. 19Unless solicitation contemplates foreign currency, all prices must be in Canadian dollars
20. 20Prices must exclude applicable taxes and be evaluated on that basis
21. 21Prices must be FOB destination, Canadian customs duties and excise taxes included
22. 22Bidder must meet security clearance requirements as specified (on closing date or before award); timing depends on solicitation specification
23. 23For joint venture bidders with security clearance requirements: each member must meet security requirements unless otherwise specified
24. 24Proposed equipment must be products in current production unless otherwise specified; future upgrades/releases not yet available will not be considered
25. 25Bidder certifies by Code of Conduct for Procurement compliance certification included in bid submission form
26. 26Federal Contractors Program for Employment Equity certification must be provided by respondent (or each joint venture member) before contract award
27. 27Bidder certifies not named on 'FCP Limited Eligibility to Bid' list; Canada may declare bid non-compliant if bidder or joint venture member appears on list at award
28. 28For former public servants receiving pension: required information must be disclosed including name and termination/retirement date
29. 29For former public servants with lump sum payment: detailed information required including name, payment conditions, dates, amounts, and restrictions on total fees ($5,000 maximum including taxes)
30. 30If bidder is OEM for hardware: written confirmation required that bidder is OEM for each item
31. 31If bidder not OEM: OEM certification signed by OEM (not bidder) required confirming bidder's authority to provide and maintain OEM hardware
32. 32If bidder is Software Publisher: written confirmation required that bidder is Software Publisher
33. 33If bidder not Software Publisher: proof of Software Publisher's authorization signed by Software Publisher required
34. 34For equivalent products: bidder must clearly designate brand name, model, part number; demonstrate full compatibility; provide complete specifications; substantiate mandatory requirement compliance; clearly identify equivalence areas
35. 35If bidder proposes equivalent products, must submit sample and/or demonstration if requested during evaluation
36. 36Certifications are deemed provided by virtue of bid submission; if bid indicates certification is untrue or expresses non-provision, bid will be non-compliant
37. 37Any certification made by bidder (knowingly or unknowingly found untrue during evaluation or contract period) renders bid non-compliant and subject to contract termination for default
38. 38For telecommunications procurements: bidder responsible for identifying CRTC regulations, obtaining all approvals, and raising conflicts during question period
39. 39For bids under non-regulated or forborne services: Regulatory Form A certification required
40. 40For bids under existing CRTC tariffs: complete tariff copy and Regulatory Form B certification required
41. 41For bids under unapproved CRTC tariffs: complete tariff copy and Regulatory Form C certification required; tariff must be submitted to CRTC before closing date
42. 42If highest-ranked bid requires CRTC tariff approval: bidder must obtain interim approval within 45 FGWDs (ex parte) or 60 FGWDs (public process); failure to do so results in non-compliant bid
43. 43For customer reference checks: references must be customers of bidder itself (not affiliates or subcontractors); if unavailable, bidder may provide alternate contact only once per customer; original contact must be unavailable (not unwilling)
44. 44Previous experience must have been obtained by bidder itself; work by subcontractors or affiliates not evaluated unless corporate predecessor that amalgamated or assets/personnel acquired
45. 45Previous experience work must be completed by closing date
46. 46Previous experience submission must include minimum name of individual from customer reference who will act as reference
47. 47Educational requirements must have successful completion by closing date; credentials from outside Canada require CICIC assessment
48. 48Professional designations/memberships must be held by closing date and maintained in good standing throughout evaluation and contract period
49. 49Work experience cannot be counted from educational programs except formal co-operative programs at post-secondary institutions
50. 50Work experience requirements must include relevant dates (month and year); only actual duration of individual's work counted, not overall project dates
51. 51Work experience to be considered must demonstrate responsibilities and work performed, not merely job titles
52. 52Overlapping work on multiple concurrent projects: overlapping time counted only once toward experience requirements
53. 53For proposed resource substitution: reason must have substantiating documentation, replacement qualifications and experience provided, proof of required security clearance if applicable
54. 54No more than one substitute per original resource permitted prior to contract award

Suggested win themes

1. —Exceed mandatory requirements with well-documented, field-proven, commercially available off-the-shelf solutions; avoid any future releases or unproven technologies
2. —Demonstrate strong financial capability through 3+ years of audited financial statements, positive cash flow, and bank credit availability; if newly established, provide parent company guarantees if applicable
3. —Secure customer references early and ensure they are actual customers of your organization (not affiliates/subcontractors) who will respond quickly and enthusiastically within 5 FGWD reference check windows
4. —For technical/experience requirements, provide clear resource résumés with detailed work descriptions (not just job titles), documented dates, and readily-available references; ensure all proposed individuals can commit availability for full contract period
5. —For equivalent product offerings, provide comprehensive technical documentation, compatibility matrices, specification comparisons, and be prepared with samples/demonstrations; clearly map equivalence to original specifications; obtain any necessary OEM/Software Publisher certifications proactively