Public tenders for printing in Gatineau Canada

Find all Printing tenders in the world.
Finding business opportunities has never been easier.

Results for printing. Make a new search!

ACAN - 2R008-13-0134 - distribution of public education materials through public libraries across Canada

The Office of the Privacy Commissionner of Canada | Published November 6, 2015  -  Deadline February 12, 2015
cpvs

Advanced Contract Award Notice - Services The Office of the Privacy Commissioner of Canada has a requirement for privacy public education by way of promotion and distribution of various materials through public libraries. The purpose of this Advance Contract Award Notice (ACAN) is to signal the government's intention to award a contract for these services to Wildcards Media Inc. of Edmonton, Alberta. Before awarding a contract, however, the government would like to provide other suppliers with the opportunity to demonstrate that they are capable of satisfying the requirements set out in this Notice, by submitting a statement of capabilities during the 15 calendar day posting period. If other potential suppliers submit a statement of capabilities during the 15 calendar day posting period that meet the requirements set out in the ACAN, the government will proceed to a full tendering process on either the government's electronic tendering service or through traditional means, in order to award the contract. If no other supplier submits, on or before the closing date, a statement of capabilities meeting the requirements set out in the ACAN, a contract will be awarded to the pre-selected supplier. Background The mission of the Office of the Privacy Commissioner of Canada (OPC) is to protect and promote the privacy rights of individuals. The OPC has a number of public education and outreach strategies to reach the public. Libraries have been identified as an important vehicle for reaching a number of our key audiences. As such, the OPC would like to distribute public education materials through public libraries across Canada. The work would involve printing of a bookmark designed and provided by the OPC, preparing and distributing the bookmark and publications provided by the OPC to the supplier’s list of public libraries, and courier and postage services. Public libraries on the supplier’s distribution list will have consented to receiving this service, and will have agreed to distribute the bookmarks and publications. The OPC would like to execute one campaign in FY 2015-16, and, allow the option of executing a second campaign in FY 2016-17. The decision to commit funds for a second campaign would not be made until FY 2016-17. The estimated value of the contract is an amount up to $50,000 plus applicable taxes (up to $25,000 in year one and up to $25,000 for the optional year two, for similar services). Minimum Essential Requirements Any interested supplier must demonstrate by way of a statement of capabilities that it meets the following requirements: 1. Current list of public libraries across Canada The supplier must demonstrate a listing of public libraries that meets the following criteria: a) updated and maintained within the last three years i) listing must include public libraries in every province and territory with a minimum of 10 libraries in each territory and a minimum of 30 libraries in each province b) The listing must have at a minimum the following information: i) Complete library name ii) Mailing address iii) Library Contact name iv) Library phone number v) Proof of consent from the library 2. Production and distribution of bookmarks The supplier must clearly demonstrate that they have the capacity to print in colour, on suitable paper stock within 3 weeks of receiving a signed digital proof from the OPC over 200,000 bookmarks and distribute, via courier, to its list of public libraries across Canada. Contacts on the list must include representation from public libraries in every province and territory and the supplier must have obtained consent from all the contacts on their list to receive these services. 3. Distribution of OPC print resources The supplier must clearly demonstrate that they have the capacity to handle, label and ship the softcover booklet provided by the OPC to its list of public libraries across Canada. Contacts on the list must include representation from public libraries in every province and territory and the supplier must have obtained consent from all the contacts on their list to receive these services. Justification for the Pre-Selected Supplier WildCards Media has a distribution list of over 2300 public libraries, in every province and territory in Canada, that have signed distribution agreements with WildCards. These public libraries have agreed to receiving materials distributed by WildCards Media and further distributing these materials to their patrons. By using the service WildCards Media provides, the OPC can distribute over 200,000 bookmarks promoting its public education resources, and distribute a limited number of OPC’s print resources as well to individual public libraries. Our past work with WildCards Media to distribute other print resources has demonstrated good audience reach and good value for money. Canada intends to retain ownership of any Foreground Intellectual Property arising out of the proposed contract on the basis that the main purpose of the contract is to generate knowledge and information for public dissemination (exception 4.1) Suppliers who consider themselves fully qualified and available to meet the specified requirements may submit a statement of capabilities in writing to the Contracting Authority identified in this Notice on or before the closing date of this Notice. The statement of capabilities must clearly demonstrate how the supplier meets the advertised requirements. The closing date and time for accepting statements of capabilities is December 2nd, 2015 14:00 EST. Inquiries and statements of capabilities are to be directed to: Contracting Authority: Mike Pignat Telephone: 819-994-5174 E-mail: mike.pignat@priv.gc.ca Please clearly identify the three (3) minimum essential requirements in your statement of capabilities and explain how you meet all the criteria in order for the Office of the Privacy Commissioner of Canada to evaluate your submission. Applicable Sole Source Justification 1. The following Exception to Soliciting Bids under the Government Contracts Regulations (GCRs) (Section 6) is being used (see below in bold): A contracting authority may enter into a contract without soliciting bids where: a) the need is one of pressing emergency in which delay would be injurious to the public interest; b) the estimated expenditure does not exceed i) $25,000, ii) $100,000, where the contract is for the acquisition of architectural, engineering and other services required in respect of the planning, design, preparation or supervision of the construction, repair, renovation or restoration of a work, or iii) $100,000, where the contract is to be entered into by the member of the Queen's Privy Council for Canada responsible for the Canadian International Development Agency and is for the acquisition of architectural, engineering or other services required in respect of the planning, design, preparation or supervision of an international development assistance program or project; c) the nature of the work is such that it would not be in the public interest to solicit bids; or d) only one person is capable of performing.

Multiple National Master Standing Offers (NMSOs) for Commercial Satellite Imagery Products or Data (Refresh)

Public Works and Government Services Canada | Published November 6, 2015  -  Deadline December 17, 2015
cpvs

THIS IS A REFRESH OF STANDING OFFER E60SQ-120001/XXX/XX. This refresh permits new suppliers to submit offers and potentially become Standing Offer Holders for Commercial Satellite Imagery Products or Data. New fully compliant Offerors will be issued Standing Offers on the condition that they meet all of the requirements of the Request for Standing Offer. This document also allows Existing National Master Standing Offer (NMSO) Holders to submit Offers to update pricing and products of existing NMSOs, and/or add new Satellite-Sensors or Constellation-Sensors and associated imagery products, either for inclusion in an existing NMSO or for issuance of an additional NMSO. All new Satellite-Sensors or Constellation-Sensors and all new products must comply with the requirements of this RFSO. Existing NMSO Holders are not required to re-qualify or re-submit for Satellite-Sensors and Constellation-Sensors and their corresponding imagery products or data for which they already have a NMSO and are not providing updates. If no Offer is received from an existing NMSO Holder by the closing date and time of this solicitation, the NMSO will be revised to incorporate the latest prices (up to March 31, 2015) for the following year. The Offerors are hereby advised that web-based services will not be considered under this solicitation. Canada has a requirement, on an "as and when requested" basis, for commercial satellite imagery products and data. The imagery, associated metadata and associated ancillary information for Satellite-Sensors and Constellation-Sensors is to be supplied from one of several Product Categories and according to one of several Priority Categories and License Classes. More information can be found in Annex A, Requirement, of the Request for Standing Offer (RFSO). The objective is to obtain satellite imagery Products from commercially available Product lists involving no customization by the Offeror. Both historical data from satellite operator archives and new acquisitions may be required. Mandatory and Optional Products It is mandatory that Offerors provide a minimum of one Basic Product for every Satellite-Sensor or Constellation-Sensor offered in accordance with Article 4, Product Categories, of Annex A Requirement. If the Offeror has a constellation of different operational satellites, then a minimum of one Basic Product must be provided for each satellite and associated sensor(s). Similarly, if the Offeror has a constellation of identical satellites, then a minimum of one Basic Product is required for the constellation. The Offeror may provide additional Basic Products and Optional Products in their offer. This RFSO allows an Offeror to be: (a) a Satellite Operator Agency (SOA): An SOA may name one or more Canadian Distributors in its offer. The SOA may also name the Distributor’s Canadian Reseller(s). Canada will only consider a Foreign Distributor or Foreign Reseller if a Canadian Distributor or Canadian Reseller does not offer the satellite imagery products or data. Or (b) a Distributor authorized by an SOA(s) with rights to license the distribution rights of the satellite imagery products or data: A Distributor may submit an offer for one or more Satellite-Sensors or Constellation-Sensors from one or more SOAs. Or (c) a Reseller authorized by the Distributor who has the rights to sublicense the distribution rights of the imagery products or data: A reseller may submit an offer for one or more Satellite-Sensors or Constellation-Sensors from one or more SOAs. PERIOD OF RESULTING STANDING OFFER Any resulting Standing Offer will be for an initial period of up to one (1) year from date of issue, with up to four (4) possible extension periods of one (1) year each. ANNUAL REFRESH On an annual basis, offers will be accepted for updates to pricing and products of existing NMSOs, and for new Satellite-Sensors or Constellation-Sensors, either for inclusion in an existing NMSO or for issuance of an additional NMSO. BASIS OF SELECTION To be declared responsive, an offer for a Satellite-Sensor or Constellation-Sensor must: (a) comply with all the requirements of the RFSO, (b) include at least one Satellite-Sensor or Constellation-Sensor that: (i) meets all Mandatory Technical Criteria in Attachment 1 to Part 4 of the RFSO; (ii) obtains the required minimum points overall for the Point-Rated Technical Criteria in Attachment 1 to Part 4 of the RFSO; and (iii) meets all mandatory financial criteria at Attachment 2 to Part 4 of the RFSO. All responsive offers will be recommended for issuance of a Standing Offer. Any resulting Standing Offer will include all Satellite-Sensors and Constellation-Sensors submitted by an Offeror that were found to be compliant with the applicable requirements of the RFSO. To be included in the Standing Offer, the Optional Product or additional Basic Product must: (a) be derived from a Satellite-Sensor or Constellation-Sensor, or a combination thereof, that has been declared responsive OR be derived from a Satellite-Sensor or Constellation-Sensor included in an existing NMSO #E60SQ-120001/XXX/XX; (b) obtain the required minimum points overall for the Point Rated Technical Criteria in Attachment 1 to Part 4 of the RFSO; and (c) meet the mandatory financial criteria as per Attachment 2 to Part 4 of the RFSO. TRADE AGREEMENTS The requirement is subject to the provisions of the Agreement on Internal Trade (AIT). This procurement consists of Satellite Data Processing and Related Services which are excluded from the application of NAFTA as per Annex 1001.1B-2, Class T, Communications, Photographic, Mapping, Printing and Publication Services, subclass T013, General Photographic Services – Still. This procurement is not covered under the World Trade Organization – Agreement on Government Procurement (WTO-AGP), in accordance with Appendix 1, Annex 4. All Comprehensive Land Claims Agreements (CLCAs) are applicable to this requirement as delivery may be to anywhere in Canada, including locations subject to a CLCA. STANDING OFFER AUTHORITY Adriana Crncan Supply Team Leader Science Procurement Directorate Public Works and Government Services Canada Place du Portage, Phase III, Floor: 11C1 11 Laurier Street Gatineau, Quebec K1A 0S5 Phone: 819-956-1353 Email: adriana.crncan@tpsgc-pwgsc.gc.ca ENQUIRIES All enquiries must be submitted in writing to the Standing Offer Authority no later than ten (10) calendar days before the RFSO closing date. Enquiries received after that time may not be answered.

Advisory Services for ESAP

Public Works and Government Services Canada | Published November 24, 2016  -  Deadline September 12, 2016
cpvs

Trade Agreement: WTO-AGP/NAFTA/AIT/Canada FTAs with Peru/Colombia/Panama Tendering Procedures: All interested suppliers may submit a bid Non-Competitive Procurement Strategy: Exclusive Rights Comprehensive Land Claim Agreement: No Vendor Name and Address:  Ever-Green Energy, LLC 345 St. Peter Street 1350 Landmark Towers Saint Paul Minnesota United States 55102 Nature of Requirements:   1. Advance Contract Award Notice (ACAN)   An ACAN is a public notice indicating to the supplier community that a department or agency intends to award a contract for goods, services or construction to a pre-identified supplier, thereby allowing other suppliers to signal their interest in bidding, by submitting a statement of capabilities. If no supplier submits a statement of capabilities that meets the requirements set out in the ACAN, on or before the closing date stated in the ACAN, the contracting officer may then proceed with the award to the pre-identified supplier.  2. Definition of the requirement   Background  The Department of Public Services and Procurement Canada has a requirement for business, technical engagement and marketing advice for the Energy Services Acquisitions Program (ESAP).  Public Services and Procurement Canada (PSPC) owns and operates six Central Heating and Cooling Plants (CHCP) that provide heating and/or cooling for more than 80 buildings in the National Capital Region (NCR) which make up to approximately 2 million rentable square meters of office space. These plants are the Cliff, Tunneys Pasture, National Printing Bureau (NPB), Confederation Heights, National Research Council (NRC) and Royal Canadian Mounted Police (RCMP).  Heating and cooling is distributed through five networks made up of 40 kilometers of pipeline most of which are contained in 12 kilometers of tunnels.  Some of the plants that provide the heating and cooling services were built almost a century ago.  The infrastructure is reaching the end of its life cycle and major investments will be required to modernize it and improve tis energy efficiency, provide access to more sustainable energy resources and reduce the environmental footprint.  The business of providing energy has changed significantly since these plants were built.  Consistent with PSPC Real Property Branchs (RBP), Corporate Real Estate Model (CREM) and the associated National Service Management Strategy (NSMS), the Energy Services Acquisition Program (ESAP) seeks to move from operating energy assets and delivering services towards service management, therefore becoming an ``informed buyer``. PSPCs strategy is to seek a solution that is cleaner, greener and more cost-effective through an innovative business arrangement.  The selected business arrangement will draw on the expertise of leaders in the field of district energy to obtain maximum value from existing assets, predictable capitalization and operating costs, best value when establishing generation and distribution capabilities and ultimately best value for the Canadian taxpayer.  At this time, the preferred method for implementing ESAP will be a Public-Private Partnership (P3) Project Agreement, whereby a private partner is engaged to Design, Build, Finance, Operate and Maintain (DBFOM) the district energy systems (DES), which consist of the CHCP and their associated distribution networks.  The private partner will carry out the conversion of existing infrastructure to modernize the system while contributing to the governments sustainability and greenhouse gas reduction objectives.  This contract will assist in establishing the parameters of the solicitation that will establish the eventual P3 Project Agreement.  Scope of Work  The contract is intended to be a long term contract covering three periods in the development of the ESAP process, including the following Phases:  * Provide advice and input to the submission requirements and evaluation criteria during the RFQ phase as well as input to the Project Specific Output Specifications (PSOS) during the RFP phase, to aid in the development of contract documents for both the RFQ and RFP processes to be completed by July 2018; * Advice during the evaluation period to select partners and final technical evaluations during the partnership selection process to be completed by February 2019; * Advice and guidance during the early period of work with a selected partner to consider implementation options, contracting options with existing and future customers.  The specific services required will be a function of the contracting approach, the business relationship and responsibility sharing with potential partners, the capacity of potential partners, and specific challenges. The following items are seen as suitable for early attention:  1. Modify existing buildings to operate on low temperature water; 2. Develop strategic and implementation plans for the modification of steam distribution to lowtemperature hot water; 3. Operational challenges with energy supply technologies; 4. Review and preparation of solicitation and contract documents as part of the P3 process;  5. Evaluation of proposals at the RFQ and RFP stages of the P3 process; 6.Development of rate structures and contracts with the P3 partner; 7. Review of implementation plans and scheduling for the transformation; 8. Workshops with local mechanical contractors for building conversions.  Note: (Specific projects can be appended as Addenda to the general contract as they are defined).      While many of the activities can be provided through discussion and the preparation of reports or provision of data and other material electronically, there will be some of these activities that will require the Contractors presence in the NCA for direct consulting, meetings, presentations, etc.  3. Criteria for assessment of the Statement of Capabilities (Minimum Essential Requirements)   Any interested supplier must demonstrate by way of a statement of capabilities that it meets the following requirements:   Senior Consultant  Education/Professional Qualifications:  o Must have a degree in any field of engineering from a recognized university or a degree in any field of business administration and management from a recognized university.        Experience: o Must have a minimum of five cumulative years of consulting experience within the past ten years in district energy systems business strategies, partnership arrangements, customer contracts and rate structures.        Senior Project Manager        Education/Professional Qualifications:  o Must have a degree in any field of engineering from a recognized university or a degree in any field of business administration and management from a recognized university or a professional designation in project management such has CAPM, PMP, PgMP.        Experience: o Must have a minimum of five cumulative years of Project Management experience within the past ten yearsin district energy systems technical advisory services.        Senior Engineer        Education/Professional Qualifications:  o Must have a degree in mechanical or electrical or civil engineering from a recognized university.        Experience: o Must have a minimum of five cumulative years of engineering experience within the past ten years in district energy systems technical advisory services.                  Project Manager        Education/Professional Qualifications:  o Must have a degree in any field of engineering from a recognized university.        Experience: o Must have a minimum of two years of Project Management experience.        Engineer        Education/Professional Qualifications:  o Must have a degree in mechanical or electrical or civil engineering from a recognized university.        Experience: o Must have a minimum of two years of engineering experience.  4. Applicability of the trade agreement(s) to the procurement   This procurement is subject to the following trade agreements:  o Agreement on Internal Trade (AIT) o World Trade Organization - Agreement on Government Procurement (WTO-AGP) o North American Free Trade Agreement (NAFTA)  5. Justification for the Pre-Identified Supplier   After a review of potential sources of advice and information, it has been determined that Ever-Green Energy is uniquely qualified to undertake the work required based on their specific & unique experience including:  * Providing comprehensive services forthe only utility in North America which has undertaken the transformation from high pressure steam to hot water technology in an urban centre that serves large heritage buildings (over 100 steam to hot water building conversions); * Operating and managing a now modern district energy system with diverse sources of energy, including biomass thermal boilers, biomass CHP (combined heat and power or cogeneration), industrial waste heat and solar thermal collectors.  (This is similar to what is contemplated for the PWGSC systems under ESAP); * Providing expert advice as the only operating district energy system that is set up with an integrated consulting/advisory service that can provide detailed information on their own technical, financial and business model experience;  * Being the only private not-for-profit district energy company in North America that has experience with both public and private (as well as hybrid subsidiaries) business models.  To support the sole source rationale, it should also be noted that  Ever-Green Energy has provided a diverse range of services to District Energy St. Paul which have contributed to the following activities:  * Acquisition of an old steam utility, consideration of ownership options for a municipal utility and development and implementation of a public not-for-profit company; * Transformation to a private not-for-profit company  the first in the USA; * Review of options for expansion and the development of subsidiaries to undertake different functions, including: o Renewable energy innovations, both within the City and externally.  They currently have a district cooling project in Honolulu, Hawaii.  This company is 100% owned by Ever-Green Energy. o St. Paul Generation, to focus on renewable energy cogeneration.  This is 50% owned by Duke Energy with whom they constructed a biomass CHP unit that produces 25 MW of electricity and 65 MW of heat. o Environmental Wood Supply to harvest, buy and process biomass for use in the CHP plant.  It is 50% owned by Ever-Green Energy. * Development of marketing and contract development tools with customers to ensure value for money and the development of customer contract templates; * Development of new sustainable energy sources including solar thermalcollectors on customer buildings and industrial waste heat recovery; * Cooperation with the municipality for combined construction of an LRT and major transmission line for district heating.  Such experience closely mirrors the specific needs of PWGSC and the ESAP project and there are no similar companies or utilities with this specific combination of technical, management, financing and customer relations experience in North America.  6. Government Contracts Regulations Exception(s)   The following exception to the Government Contracts Regulations is) invoked for this procurement under subsection 6(d) - "only one person is capable of performing the work".   7. Exclusions and/or Limited Tendering Reasons   The following exclusion(s) and/orlimited tendering reasons are invoked under the:  o Agreement on Internal Trade (AIT)  Article(s) 506.12b o World Trade Organization - Agreement on Government Procurement (WTO-AGP)  Article(s) XV.1b o North American Free Trade Agreement (NAFTA)  Article(s)1016.2b  8. Period of the proposed contract    The proposed contract is for a period of one year, with three one-year option periods.  9. Cost estimate of the proposed contract  The estimated value of the contract, including options, is $1,983,000.00 (GST/HST extra)  10. Name and address of the pre-identified supplier   Ever-Green Energy, LLC 345 St.Peter Street 1350 Landmark Towers Saint-Paul, Minnesota  11. Suppliers' right to submit a statement of capabilities   Suppliers who consider themselves fully qualified and available to provide the goods, services or construction services described in the ACAN may submit a statement of capabilities in writing to the contact person identified in this notice on or before the closingdate of this notice. The statement of capabilities must clearly demonstrate how the supplier meets the advertised requirements.  12. Closing date for a submission of a statement of capabilities   The closing date and time for accepting statements ofcapabilities is December 9 2016 at 2:00 p.m. EDT.   13. Inquiries and submission of statements of capabilities   Inquiries and statements of capabilities are to be directed to:   Amélie Hamann 11 Laurier Street, Building Portage III Gatineau, Québec K1A 0S5  E-mail: amelie.hamann@tpsgc-pwgsc.gc.ca    Delivery Date: Above-mentioned  You are hereby notified that the government intends to negotiate with one firm only as identified above. Should you have any questions concerning this requirement, contact the contracting officer identified above.  An Advance Contract Award Notice (ACAN) allows departments and agencies to post a notice, for no less than fifteen (15) calendar days, indicating to the supplier community that it intends to award a good, service or construction contract to a pre-identified contractor. If no other supplier submits, on or before the closing date, a Statement of Capabilities that meets the requirements set out in the ACAN, the contracting authority may then proceed with the award.  However, should a Statement of Capabilities be found to meet the requirements set out in the ACAN, then the contracting authority will proceed to a full tendering process.  Suppliers who consider themselves fully qualified and available to provide the services/goods described herein, may submit a statement of capabilities in writing to the contact person identified in this Notice on or before the closing date of this Notice. The statement of capabilities must clearly demonstrate how the supplier meets the advertised requirements.  The PWGSC file number, the contracting officer's name and the closing date of the ACAN must appear on the outside of the envelope in block letters or, in the case of a facsimile transmission, on the covering page.  The Crown retains the right to negotiate with suppliers on any procurement.  Documents may be submitted in either official language of Canada.

Emergency Notification Software Sol

Public Works and Government Services Canada | Published November 28, 2016  -  Deadline December 14, 2016
cpvs

Trade Agreement: NAFTA/AIT/Canada FTAs with Peru/Colombia/Panama Tendering Procedures: All interested suppliers may submit a bid Non-Competitive Procurement Strategy: Exclusive Rights Comprehensive Land Claim Agreement: No Vendor Name and Address:  ERMS Solutions Limited 2916 South Sheridan Way Suite 200 Oakville Ontario Canada L6J7J8 Nature of Requirements:   Please Note, for any additional information regarding this ACAN or to obtain copy of the criteria for assessment of the statement of capabilities, please contact the following Contracting Authority:  Brock Flemming 873-469-4653 Brock.flemming@pwgsc-tpsgc.gc.ca   EMERGENCY NOTIFICATION SOFTWARE SOLUTION (ENSS) - ERMS ADVANTAGE PLATFORM  An ACAN is a public notice indicating to the supplier community that a department or agency intends to award a contract for goods, services or construction to apre-identified supplier, thereby allowing other suppliers to signal their interest in bidding, by submitting a statement of capabilities. If no supplier submits a statement of capabilities that meets the requirements set out in the ACAN, on or before the closing date stated in the ACAN, the contracting officer may then proceed with the award to the pre-identified supplier.   DEFINITION OF REQUIREMENT  FOR NATURAL RESOURCES CANADA  Natural Resource Canada (NRCan) is responsible for many sites across the country and as such there is a requirement to effectively communicate with key contacts during an Emergency/BCP event. There is a risk that NRCans capacity to respond to catastrophic crises, including those related to natural and accidental hazards (e.g., disease, weather, etc.) may have consequences for the various sectors under NRCans mandate and/or to Canadians.  NRCan must implement an Emergency Notification Software Solution (ENSS) in order to broadcast notifications of such threats or events.  The ENSS provided by the Service Provider must be able to send out a mass notification to at least 5000 employees within Natural Resource Canada. The ENSS will be used within NRCan as a notification instrument for their own employees, students, contractors and for business continuity purposes.  Canada intends to enter into a sole source contract with ERMS Corporation for the purpose of procuring the ERMS Advantage Platform suite including associating maintenance and support service, training and professional services. Canada reserves the right to add additional clients to this contract at the same price, and under the same terms and conditions, as granted to NRCan.         CRITERIA FOR ASSESSMENT OF THE STATEMENT OF CAPABILITIES  Any interested supplier must demonstrate by way of a statement of capabilities that their product and services meet the following requirements:   Requirements:  NRCan has a requirement for the supply of an Emergency Response Management Solution (ERMS) that will deliver, allow and support the broadcast notifications of threats or Emergency/BCP Events. The ENSS is required to providing the following requirements;  ESSENTIAL  REQUIREMENTS:  M1. The software proposed to meet this requirement must beoff-the-shelf, meaning that each component of software is commercially available and requires no further research and development and is part of an existing product line with a field-proven operational history (that is, it has not simply been tested in a laboratory or experimental environment).  EXPERIENCE REQUIREMENTS:  M2. The Supplier must have delivered an ENSS as a Supplier's hosted application for at least three years.   SERVICE ARCHITECTURE REQUIREMENTS:  M3.  Service Design: The ENSS must be designed specifically for emergency notifications with the capability of broadcasting mass notifications via multiple methods either simultaneously or in a cascading sequence to multiple contacts within 5 minutes.  M4. Service Design: The ENSS must include the ability to send routine messages that are clearly distinct from any emergency messages.  M5. Call Throttling: The ENSS must have the ability to control the number of calls into an organization to avoid flooding the lines during a mass notification.  M6.  Proprietorship: All hardware, software and data (apart from Client's owned systems) must be hosted at facilities owned or leased, operated and secured by the Supplier in Canada.  M7. 2.5. Requirements for Client Operation: The Client must not be required to install any hardware or software to operate any facets of the ENSS. Database capacity, data channels and phone ports are not purchased by the Client.   SECURITY REQUIREMENTS:  M8. Industrial Security Standards: The selected Supplier must have the ability to handle and secure information up to and including PROTECTED A in accordance with Public Works and Government Services Canada's Industrial Security Standards. These standards apply to all facilities and equipment used to store and process Administrator, User and Contact information and all messages.  M9. Access Privileges: The ENSS must enable Administrators to control access privileges, such as access requests, requests for changes to personal information, and changes to passwords, provided that they have appropriate access control permissions.  M10. Password Change: The ENSS must permit each Administrator, User and Contact to change their password at any time.  M11. Password Strength: The ENSS must force eachAdministrator, User and Contact to configure a password in a predetermined manner with a minimum number of characters, including capitals, numbers and symbols.  RESILIENCY REQUIREMENTS:  M12. Recovery: Client data must be hosted in high-availabilityfacilities with zero failover time and automatic recovery.  M13. Disaster Recovery: If a Disaster, Emergency or Hazard renders the Supplier's primary data centre inoperable, Client data must be dynamically rerouted so that it functions without interruption.  M14. Back-Up Facilities and Services: The ENSS must have a multi-tier, multi-server fault tolerant architecture with full redundancy whereby the primary Contacts database server and all ENSS functions are housed in Canada and their back-up capability is housed in separate locations in Canada separated by a provincial boundary (at least 200 km) so that an Emergency that affects one facility will not affect the others.  M15. Location of Data Servers: The ENSS must ensure that the Client's database never resides outside of Canada's land boundaries.  M16. Permissions and Access Controls: The ENSS must enable and support the designation of a minimum of 10 Master Administrators with full access and Regional Administrators with limited access.   GENERAL OPERATION REQUIREMENTS:  M17. User Interfaces: The Supplier must ensure that the ENSS provides graphical user interfaces (GUIs) in both English and French for Administrators and Users.  M18. Browsers: The ENSS must be accessible to Administrators and Users on web browsers including Internet Explorer (min version 9.0), Apple Safari (min version 5.1), Google Chrome (min version 17.0) and Mozilla Firefox (min version 10.0) for Windows - and compatible with 128-bit encryption.  M19. Quick Launch: The ENSS must have a quick-launch feature that allows an Administrator to initiate a Message from a single screen after logging in to the ENSS.  M20. Practice Modes: The ENSS must have practice modes (i.e., a test environment) that allow the Administrators and Users to use any facet of the ENSS without affecting real-time content or capabilities of the ENSS and the database (i.e., the production environment).  M21.  Self-Registration: The ENSS must allow users to self-register and update their own profile information at any time.  M22. Mapping: The ENSS Application must have a map function that allows selection of a selected radius surrounding an event which allows notifications sent to only the selected geographic area.  OUTPUT  M23. Voice Messages: The ENSS must send local or long-distance voice Messages of up to 1 minute in duration (exclusive of dialing time, ringing time and voice-mail response time) to at least 6,000 registered Contacts within 5 minutes of being sent.   M24. Voice Message Language: Voice messages must be delivered in French and English with voices using contemporary Canadian accents.  M25. Text-based Messages: The ENSS must send text-based SMS Messages of a minimum of 140 characters or e-mail messages ofup to 500 words to at least 6,000 registered Contacts within 5 minutes of being sent.  M26. Reliability: The ENSS must be fully functional and operational 24 hours a day, 7 days a week, with at least 99.99% availability throughout the Contract period.In the event of an outage, the Supplier will advise the client of the outage and the impacts on the ENSS. In the event of a scheduled outage, the Supplier will advise the Client well in advance of the outage.  M27. Native SMS in Canada: The ENSS must use short code in order to allow for the sending of true SMS versus email-to-SMS.  DATABASE  M28. Data Recovery: The ENSS must enable Administrators to recover a Contact record that has been deleted for up to 5 days after deletion  M29. Database Backup: The ENSS must generate automatic database backups to one or more other locations in Canada at least once every 24 hours.  ADMINISTRATOR, USER AND CONTACT INFORMATION MANAGEMENT   M30. Administrator and User Profiles: The ENSS must allow for theestablishment and maintenance of a database of Administrator and User Profiles that include the following: (i). Full name (ii). Position (iii). Region (iv). Branch (v). An individual ID number (vi). Primary 24 hour emergency coordinates (vii). Secondary 24 hour emergency coordinates (viii). Cell phone number (ix). Business Fax number (x). Pager number (xi). E-mail address (xii). Designated alternate (xiii). Blackberry number (xiv). Permissions assigned. (xv). The ENSS must allow Master Administrators to have full access permissions and to perform all functions of the ENSS.  M31. Import Formats for Contact Information: The ENSS must securely import Contact information from existing databases (delivered to the Supplier in one or more electronic files) such as Microsoft Active Directory, PeopleSoft/Oracle HR, BCP Software, SQL, MS SQL Server, NetHris, HRIS database, and CSV (e.g. Excel), XML, MS Outlook and MDB files - without requiring manual (human) intervention - at intervals prescribed by the Client or as required. The Client must have the ability to import Contact information manually if so desired. This process is to be delivered through a web services Application Programming Interface using a standards-based Service-Oriented Architecture.  M32. Contact Data Fields: The ENSS must accommodate the creation of 45 data fields per record.  M33. Data Revision: The ENSS must enable Administrators, Users and Contacts to view and manually edit the information in their own profiles, directly within the ENSS, provided they have appropriate access control permissions.  M34. Data Revision: The ENSS must enable Administrators and Users to add, modify, and delete Contacts and Contact information, directly within the ENSS, provided they have appropriate access control permissions.  M35. Log-in Data: The ENSS must automatically assign a unique user ID for each Administrator and User. The Administrator must then be allowed to set a temporary password which can later be modified by the account holder.       CONTACT GROUPS   M36. Creation: The ENSS must enable Administrators and Users to create groups of Contacts based on variables such as Mode, Group, Region or other criteria identified in the data fields of each Contact's record.  M37. Hierarchical Groups: The ENSS must enable Administrators and Users to create hierarchical groupings so that groups include up to 50 levels of sub-groups in order to appropriately reflect an organization's structure.  M38. Number of Groups: The ENSS must allow Administrators and Users to define a Contact to be a member of up to 50 groups.  M39. Search feature: The ENSS must allow Administrators and Users to conduct a search or filter Contacts based on criteria identified in the data fields of each Contact's record. The ENSS must also have the capability to quickly create unique Groups using the results of the search function.  M40. Sort features: The ENSS must allow Administrators and Users to sort Contact lists alphabetically or, using any other criteria identified in the data fields of each Contact's record. The ENSS must also have the capability to quickly create unique Groups using the results of the sort function.  M41. Sorting Stakeholders' by Language: The ENSS must have the capability to list stakeholders by language of correspondence in order to allow the sending of only French messages to French speaking stakeholders and English to English speaking stakeholders.  MESSAGE INITIATION  M42. Service Access: The ENSS must enable Administrators and Users to access the service for Contact management , message creation (voice or text-based) or message transmission purposes via the following methods and Devices: (i). i. Computer (via the internet either through cable or WI-FI); (ii). ii. Landline telephone; (iii). iii. Cellular telephone; (iv). iv. Smartphone; (v). v. Personal digital assistant; (vi). vi. Telecommunications device for the deaf; (vii). vii. Voice over Internet protocol; and (viii). viii.Satellite telephone.   M43. Message Creation: The ENSS must enable Administrators and Users to create and record voice and text-based messages in French and English for present or future use.  M44. Customizing Messages: The ENSS must enable Administrators and Usersto customize pre-recorded messages by adding introductory and/or closing statements.  M45. Message verification: The ENSS must allow Administrators and Users to hear the voice message and/or to read the text-based message before it is sent.  M46. Time Zone Recognition: The ENSS must have the capability to recognize and understand time zones.  MESSAGE TRANSMISSION  M47. Media: The ENSS must send messages to Contacts via the following media: (i). i. Landline telephone; (ii). ii. Cellular telephone; (iii). iii. Smartphone, including telephone, text and e-mail communications; (iv). iv. Personal Digital Assistant; (v). v. SMS text message; (vi). vi. E-mail; (vii). vii. Facsimile; (viii). viii.Pager; (ix). ix. Telecommunication Device for the Deaf; and (x). x. Satellite telephone.  M48. Safeguards: The ENSS must have an effective safeguard (such as a prompt message) that prevents routine messages from being sent out as emergency notifications and requests if the Administrators or Users has sought approval prior to sending a notification.  M49. Phone Number Types: The ENSS must have the ability to make local and long distance calls within Canada and the United States. The ENSS must also have the ability to dial international numbers and phone numbers with extensions.  M50. Order of Contact Methods: The ENSS must allow Administrators and Users to set the default order of devices used to notify Contacts but also allow Users and Contacts to override the order if they have the appropriate permissions to do so.  M51. Language of Message and Contacts: The ENSS must allow Administrators and Users to select Messages in either French or English and to automatically transmit them in the Contact's pre-selected corresponding language.  M52. Simultaneous Transmission: The ENSS must allow Users to send a recorded voice message and a text message in a single notification to all selected Contacts for delivery through the  media listed in 11.1.  M53. Caller ID: Either globally or on a message-by-message basis, the ENSS must allow Administrators and Users initiating a message to customize the telephone number displayed (caller ID) for voice Messages and the e-mail addresses for text-based Messages.  M54. Escalation: The ENSS must escalatemessages when the intended Contact has not confirmed receipt of the correspondence (with 3 levels of person-to-person escalation) within a given period of time. If no confirmation of receipt is received within a given period of time, then the message will be redirected to an alternate point of contact if one has been designated see 11.12.  M55.  Delivery Attempts: The ENSS must allow Users and Administrators to select the number of delivery attempts through all Contact paths.  M56. E-mail Attachments: The ENSS must allow e-mails to attach multiple files (e.g. text, spreadsheet and images) and send them to an e mail device.    M57. Message Control: The ENSS must allow an Administrator or User to stop, recall or replace a Message initiated by themor another Administrator or User with the same level of permissions at any time during the Message sending process.   M58. Back-Up Contacts: The ENSS must automatically send messages to a back-up Contact if a primary Contact does not acknowledge receipt of the initial message within a period of time defined by the sender.   M59. First to Respond: The ENSS must have the capability to send notifications systematically until a predetermined number of affirmative responses are received.  M60. Roll Call: The ENSS must have the capability to send notifications for the purpose of soliciting a positive or negative acknowledgement from the recipient, such as "are you OK", "Not OK".   MESSAGE DELIVERY FEATURES  M61. Voice Message Repeat: The ENSS must allow Contacts to listen to a voice Message as often as desired with a single key press.  M62. Acknowledgements: The ENSS must seek and receive acknowledgements of Messages through the device types identified in 11.1, with the exception of facsimile and pager and SMS transmissions.  M63. Re-send: The ENSS must allow Administrators and Users to re-send a notification to only those Contacts who did not respond to the original notification.  M64.  Voice-Mail: The ENSS must leave a Message when a voice-delivered message reaches an answering machine or voice-mail. If a message is left, the ENSS must also contact the back-up Contact if the message was left on the primary Contact's voice mail box.  M65. Electronic Voice: The electronic voice transmitter must use Canadian (English and French) accents.  M66. Custom Response: The ENSS must allow Contacts to send custom text-based messages in response to messages.  MESSAGE MANAGEMENT  M67. Recurring Messages: The ENSS must allow Administrators and Users to set up recurring Messages.   M68. Scheduling: The ENSS must allow Administrators and Users to schedule a notification to be sent at a future date and time.  M69. Voice-Mail: The ENSS must distinguish when a live Contact is reached versus when an answering machine or voicemail has been reached on voice-delivered devices.  REPORTING  M70. Dashboard: The ENSS must provide a real-time dashboard for each active notification broadcast allowing Administrators and Users to view broadcast parameters (e.g. devices, start time, duration and number of cycles) and see status of broadcast results (e.g. confirmation and responses).  M71. History: The ENSS must allow Administrators and Users to view a history of Message results for the entire period of the contract.  M72. Audit Trail: The ENSS must produce real-time Message broadcast result reports using all application data which contains, but is not limited to, all of the following information: (i). i. Name, date and time of the Message; (ii). ii. Name of the Administrator or User who initiated the broadcast; (iii). iii. Number of redial attempts requested by initiator; (iv). iv. Summary statistics, including total notified Contacts, total confirming receipt/not (v). confirming receipt,percentage confirming receipt/not confirming receipt. If a polling Message, (vi). a total for each response. This information must be collated for individual messages and (vii). cumulatively; and (viii). v. Detailed calling information, including call-result of each attempt within the broadcast, the (ix). addresses and associated phone numbers attempted, the attempt number and the result (x). (e.g., confirmed with date and time, busy, no answer or voicemail).  M73. Export: The ENSS must export all types of report data in CSV, XLS, HTML, or PDF formats, as defined by an Administrator or User.   M74. Printing: The ENSS must allow Administrators and Users to print real-time reports of any data or statistics directly from the GUI.  M75. Reports: Upon request, the Service Provider must search and generate reports based on user-defined criteria and/or key words including wild card searches. In addition, the Service Provider must retain a permanent record of all reports.   APPLICABILITY OF THETRADE AGREEMENT(S) TO THE PROCUREMENT  Agreement on Internal Trade (AIT)  World Trade Organization - Agreement on Government Procurement (WTO-AGP)  North American Free Trade Agreement (NAFTA)   JUSTIFICATION FOR THE PRE-IDENTIFIED SUPPLIER  ERMS Advantage is a fully hosted, off-the-shelf, web-based emergency notification and management solution that is used by organizations for the purpose of managing their vital emergency processes, enabling effective communications and management of crisissituations and incidents. ERMS Advantage supports Natural Resource Canadas emergency notification requirements without any additional configuration to our IT infrastructure.  ERMS Advantage will allow NRCan to effectively manage and maintain its self-registered contact data and issue security threat notifications in fully redundant and secure hosting facilities.   ERMS Advantage fully satisfies AAFCs requirements for a Bilingual (English/French) Emergency Mass Notification System as per the criteria identified.  ERMS Advantage fully satisfies AAFCs security requirements for a hosted Protected A solution.   GOVERNMENT CONTRACTS REGULATIONS EXCEPTION(S)  Section 6 of the Government Contract Regulations is being invoked in this procurement as only one person or firm is capable of performing the contract.   EXCLUSIONS AND/OR LIMITED TENDERING REASONS  Annex 4.4 article 506.12(b) of the AIT is applicable on the basis of limited tendering where there is an absence of competition for technical reasons and the goods or services can be supplied only by a particular supplier and no alternative or substitute exists, respectively.  Article 1016.2(b) of NAFTA is applicable on the basis of limited tendering due to reasons where, for works of art, or for reasons connected with the protection of patents, copyrights or other exclusive rights, or proprietary information or where there is an absence of competition for technical reasons, the goods or services can be supplied only by a particularsupplier and no reasonable alternative or substitute exists.  Article XV(b) of the WTO-AGP is applicable on the basis of limited tendering due to reasons when, for works of art or for reasons connected with protection of exclusive rights, such as patents or copyrights, or in the absence of competition for technical reasons, the products or services can be supplied only by a particular supplier and no reasonable alternative or substitute exists.   OWNERSHIP OF INTELLECTUAL PROPERTY. Ownership of any Foreground Intellectual Property arising out of the proposed contract will vest in the Contractor.   THE PERIOD OF THE PROPOSED CONTRACT OR THE DELIVERY DATE(S)  The proposed contract is for a period of 1 years that includes 9 additional 1-year options. All delivery mentioned in the requirement shall be delivered within 10 days of Contract award.   NAME AND ADDRESS OF THE PRE-IDENTIFIED SUPPLIER:  ERMS Solutions Limited 2916 S Sheridan Way #300 Oakville, Ontario L6J 7J8   SUPPLIERS' RIGHT TO SUBMIT A STATEMENT OF CAPABILITIES  Suppliers who consider themselves fully qualified and available to provide the goods, services or construction services described in the ACAN, may submit a statement of capabilities in writing to the contactperson identified in this notice on or before the closing date of this notice.   THE STATEMENT OF CAPABILITIES MUST CLEARLY DEMONSTRATE HOW THE SUPPLIER MEETS THE ADVERTISED REQUIREMENTS.  The conditions of the developer's shrink-wrap license are not acceptable to the Crown. This software is proprietary, and the proposed Contractor must have the authority to negotiate the terms and conditions of the contract and the related software licensing terms including, but not limited to; limitation of liability, indemnification, transferability of license, termination/refund to the Crown. Documents may be submitted in either official language of Canada   INQUIRIES AND SUBMISSION OF STATEMENTS OF CAPABILITIES  Inquiries and statements of capabilities are to be directed to:  Brock Flemming Procurement Officer Public Works and Government Services Canada Gatineau, Québec, Canada (K1A 0S5) Brock.flemming@tpsgc-pwgsc.gc.ca Telephone 873-469-4653 Government of Canada  Delivery Date: Above-mentioned  You are hereby notified that the government intends to negotiate with one firm only as identified above. Should you have any questions concerning this requirement, contact the contracting officer identified above.  An Advance Contract Award Notice (ACAN) allows departments and agencies to post a notice, for no less than fifteen (15) calendar days, indicating to the supplier community that it intends to award a good, service or construction contract to a pre-identified contractor. If no other supplier submits, on or before the closing date, a Statement of Capabilities that meets the requirements set out in the ACAN, the contracting authority may then proceed with the award.  However, should a Statement of Capabilities be found to meet the requirements set out in the ACAN, then the contracting authority will proceed to a full tendering process.  Suppliers who consider themselves fully qualified and available to provide the services/goods described herein, may submit a statement of capabilities in writing to the contact person identified in this Notice on or before the closing date of this Notice. The statement of capabilities must clearly demonstrate how the supplier meets the advertised requirements.  The PWGSC file number, the contracting officer's name and the closing date of the ACAN must appear on the outside of the envelope in block letters or, in the case of a facsimile transmission, on the covering page.  The Crown retains the right to negotiate with suppliers on any procurement.  Documents may be submitted in either official language of Canada.

ACAN FOR AN EMERGENCY NOTIFICATIONS OFF-PREMISE SOFTWARE SOLUTION (ENOSS)

Agriculture and Agri-Food Canada | Published October 6, 2015  -  Deadline October 21, 2015
cpvs

Trade Agreement: NAFTA/AIT/Canada FTAs with Peru/Colombia/Panama Tendering Procedures: All interested suppliers may submit a bid Non-Competitive Procurement Strategy: Exclusive Rights Comprehensive Land Claim Agreement: No Vendor Name and Address: ERMS Solutions Limited 2916 South Sheridan Way Suite 200 Oakville Ontario Canada L6J7J8 Nature of Requirements: ADVANCE CONTRACT AWARD NOTICE (ACAN) - EMERGENCY NOTIFICATIONS OFF-PREMISE SOFTWARE SOLUTION (ENOSS) Please Note, for any additional information regarding this ACAN or to obtain copy of the criteria for assessment of the statement of capabilities, please contact the following Contracting Authority: Jonathan Vinet 819-956-2940 Jonathan.vinet@tpsgc-pwgsc.gc.ca EMERGENCY NOTIFICATION OFF-PREMISE SOFTWARE SOLUTION (ENOSS) - ERMS ADVANTAGE PLATFORM An ACAN is a public notice indicating to the supplier community that a department or agency intends to award a contract for goods, services or construction to a pre-identified supplier, thereby allowing other suppliers to signal their interest in bidding, by submitting a statement of capabilities. If no supplier submits a statement of capabilities that meets the requirements set out in the ACAN, on or before the closing date stated in the ACAN, the contracting officer may then proceed with the award to the pre-identified supplier. DEFINITION OF REQUIREMENT FOR AGRICULTURE AND AGRI-FOOD CANADA The Department of Agriculture & Agri-Food Canada (AAFC) is responsible for many sites across the country and as such there is a requirement to effectively communicate with key contacts during an Emergency/Business Continuity Planning (BCP) event. There is a risk that AAFC's capacity to respond to catastrophic crises, including those related to natural and accidental hazards (e.g. disease, weather, etc.) may have consequences for the agriculture, agri-based and agri-food sector and/or to Canadians. AAFC must implement an ENOSS in order to broadcast notifications of such threats or events. The ENOSS provided by the Service Provider must deliver, support and allow the broadcast notifications of threats or Emergency/BCP Events to at least 6,000 different stakeholders within AAFC. The ENOSS will be used within AAFC as a notification instrument for their own employees, students, contractors and for business continuity purposes. AAFC intends to enter into a sole source contract with ERMS Solutions Limited for the purpose of procuring the ERMS Advantage Platform suite including associating maintenance and support service, training and professional services. CRITERIA FOR ASSESSMENT OF THE STATEMENT OF CAPABILITIES Any interested supplier must demonstrate by way of a statement of capabilities that their product and services meet the following requirements: MANDATORY REQUIREMENTS: M1. The software proposed to meet this requirement must be "off-the-shelf", meaning that each component of software is commercially available and requires no further research and development and is part of an existing product line with a field-proven operational history (that is, it has not simply been tested in a laboratory or experimental environment). M2. The contractor agrees to supply Canada with an Emergency Notification Off-Premise Software Solution (ENOSS); that delivers, allows and supports a secure, authenticated and trusted computing environment located in Canada at all times; and that has, all pre-production, production and post production, in Canada, in a Protected A environment; for at least a three years period of time. SERVICE ARCHITECTURE REQUIREMENTS: M3. Service Design: The ENOSS must be designed specifically for emergency notifications with the capability of broadcasting mass notifications via multiple methods either simultaneously or in a cascading sequence to multiple contacts within 5 minutes. M4. Service Design: The ENOSS must include the ability to send routine messages that are clearly distinct from any emergency messages. M5. Call Throttling: The ENOSS must have the ability to control the number of calls into an organization to avoid flooding the lines during a mass notification. M6. Proprietorship: All hardware, software and data (apart from Client's owned systems) must be hosted at facilities owned or leased, operated and secured by the Supplier in Canada. M7. Requirements for Client Operation: The Client must not be required to install any hardware or software to operate any facets of the ENOSS. Database capacity, data channels and phone ports are not purchased by the Client. SECURITY REQUIREMENTS: M8. Industrial Security Standards: The selected Supplier must have the ability to handle and secure information up to and including PROTECTED A in accordance with Public Works and Government Services Canada's Industrial Security Standards. These standards apply to all facilities, subcontractors and equipment used to store and process Administrator, User and Contact information and all messages. M9. Access Privileges: The ENOSS must enable Administrators to control access privileges, such as access requests, requests for changes to personal information, and changes to passwords, provided that they have appropriate access control permissions. M10. Password Change: The ENOSS must permit each Administrator, User and Contact to change their password at any time. M11. Password Strength: The ENOSS must force each Administrator, User and Contact to configure a password in a predetermined manner with a minimum number of characters, including capitals, numbers and symbols. RESILIENCY REQUIREMENTS: M12. Recovery: Client data must be hosted in high-availability facilities with zero failover time and automatic recovery. M13. Disaster Recovery: If a Disaster, Emergency or Hazard renders the Supplier's primary data centre inoperable, Client data must be dynamically rerouted so that it functions without interruption. M14. Back-Up Facilities and Services: The ENOSS must have a multi-tier, multi-server fault tolerant architecture with full redundancy whereby the primary Contacts database server and all ENOSS functions are housed in Canada and their back-up capability is housed in separate locations in Canada separated by a provincial boundary (at least 200 km) so that an Emergency that affects one facility will not affect the others. M15. Location of Data Servers: The ENOSS must ensure that the Client's database never resides outside of Canada's land boundaries. M16. Permissions and Access Controls: The ENOSS must enable and support the designation of a minimum of 10 Master Administrators with full access and Regional Administrators with limited access. GENERAL OPERATION REQUIREMENTS: M17. User Interfaces: The Supplier must ensure that the ENOSS provides graphical user interfaces (GUIs) in both English and French for Administrators and Users. M18. Browsers: The ENOSS must be accessible to Administrators and Users on web browsers including Internet Explorer (min version 9.0), Apple Safari (min version 5.1), Google Chrome (min version 17.0) and Mozilla Firefox (min version 10.0) for Windows - and compatible with 128-bit encryption. M19. Quick Launch: The ENOSS must have a quick-launch feature that allows an Administrator to initiate a Message from a single screen after logging in to the ENOSS. M20. Practice Modes: The ENOSS must have practice modes (i.e., a test environment) that allow the Administrators and Users to use any facet of the ENOSS without affecting real-time content or capabilities of the ENOSS and the database (i.e., the production environment). M21. Self-Registration: The ENOSS must allow users to self-register and update their own profile information at any time. M22. Mapping: The ENOSS Application must have a "map" function that allows selection of a selected radius surrounding an event which allows notifications sent to only the selected geographic area. OUTPUT M23. Voice Messages: The ENOSS must send local or long-distance voice Messages of up to 1 minute in duration (exclusive of dialing time, ringing time and voice-mail response time) to at least 6,000 registered Contacts within 5 minutes of being sent. M24. Voice Message Language: Voice messages must be delivered in French and English with voices using contemporary Canadian accents. M25. Text-based Messages: The ENOSS must send text-based SMS Messages of a minimum of 140 characters or e-mail messages of up to 500 words to at least 6,000 registered Contacts within 5 minutes of being sent. M26. Reliability: The ENOSS must be fully functional and operational 24 hours a day, 7 days a week, with at least 99.99% availability throughout the Contract period. In the event of an outage, the Supplier will advise the client of the outage and the impacts on the ENOSS. In the event of a scheduled outage, the Supplier will advise the Client well in advance of the outage. M27. Native SMS in Canada: The ENOSS must use short code in order to allow for the sending of true SMS versus email-to-SMS. DATABASE M28. Data Recovery: The ENOSS must enable Administrators to recover a Contact record that has been deleted for up to 5 days after deletion M29. Database Backup: The ENOSS must generate automatic database backups to one or more other locations in Canada at least once every 24 hours. ADMINISTRATOR, USER AND CONTACT INFORMATION MANAGEMENT M30. Administrator and User Profiles: The ENOSS must allow for the establishment and maintenance of a database of Administrator and User Profiles that include the following: (i). Full name (ii). Position (iii). Region (iv). Branch (v). An individual ID number (vi). Primary 24 hour emergency coordinates (vii). Secondary 24 hour emergency coordinates (viii). Cell phone number (ix). Business Fax number (x). Pager number (xi). E-mail address (xii). Designated alternate (xiii). Blackberry number (xiv). Permissions assigned. (xv). The ENOSS must allow Master Administrators to have full access permissions and to perform all functions of the ENOSS. M31. Import Formats for Contact Information: The ENOSS must securely import Contact information from existing databases (delivered to the Supplier in one or more electronic files) such as Microsoft Active Directory, PeopleSoft/Oracle HR, BCP Software, SQL, MS SQL Server, NetHris, HRIS database, and CSV (e.g. Excel), XML, MS Outlook and MDB files - without requiring manual (human) intervention - at intervals prescribed by the Client or as required. The Client must have the ability to import Contact information manually if so desired. This process is to be delivered through a web services Application Programming Interface using a standards-based Service-Oriented Architecture. M32. Contact Data Fields: The ENOSS must accommodate the creation of 45 data fields per record. M33. Data Revision: The ENOSS must enable Administrators, Users and Contacts to view and manually edit the information in their own profiles, directly within the ENOSS, provided they have appropriate access control permissions. M34. Data Revision: The ENOSS must enable Administrators and Users to add, modify, and delete Contacts and Contact information, directly within the ENOSS, provided they have appropriate access control permissions. M35. Log-in Data: The ENOSS must automatically assign a unique user ID for each Administrator and User. The Administrator must then be allowed to set a temporary password which can later be modified by the account holder. CONTACT GROUPS M36. Creation: The ENOSS must enable Administrators and Users to create groups of Contacts based on variables such as Mode, Group, Region or other criteria identified in the data fields of each Contact's record. M37. Hierarchical Groups: The ENOSS must enable Administrators and Users to create hierarchical groupings so that groups include up to 50 levels of sub-groups in order to appropriately reflect an organization's structure. M38. Number of Groups: The ENOSS must allow Administrators and Users to define a Contact to be a member of up to 50 groups. M39. Search feature: The ENOSS must allow Administrators and Users to conduct a search or filter Contacts based on criteria identified in the data fields of each Contact's record. The ENOSS must also have the capability to quickly create unique Groups using the results of the search function. M40. Sort features: The ENOSS must allow Administrators and Users to sort Contact lists alphabetically or, using any other criteria identified in the data fields of each Contact's record. The ENOSS must also have the capability to quickly create unique Groups using the results of the sort function. M41. Sorting Stakeholders' by Language: The ENOSS must have the capability to list stakeholders by language of correspondence in order to allow the sending of only French messages to French speaking stakeholders and English to English speaking stakeholders. MESSAGE INITIATION M42. Service Access: The ENOSS must enable Administrators and Users to access the service for Contact management , message creation (voice or text-based) or message transmission purposes via the following methods and Devices: (i). Computer (via the internet either through cable or WI-FI); (ii). Landline telephone; (iii). Cellular telephone; (iv). Smartphone; (v). Personal digital assistant; (vi). Telecommunications device for the deaf; (vii). Voice over Internet protocol; and (viii). Satellite telephone. M43. Message Creation: The ENOSS must enable Administrators and Users to create and record voice and text-based messages in French and English for present or future use. M44. Customizing Messages: The ENOSS must enable Administrators and Users to customize pre-recorded messages by adding introductory and/or closing statements. M45. Message verification: The ENOSS must allow Administrators and Users to hear the voice message and/or to read the text-based message before it is sent. M46. Time Zone Recognition: The ENOSS must have the capability to recognize and understand time zones. MESSAGE TRANSMISSION M47. Media: The ENOSS must send messages to Contacts via the following media: (i). Landline telephone; (ii). Cellular telephone; (iii). Smartphone, including telephone, text and e-mail communications; (iv). Personal Digital Assistant; (v). SMS text message; (vi). E-mail; (vii). Facsimile; (viii). Pager; (ix). Telecommunication Device for the Deaf; and (x). Satellite telephone. M48. Safeguards: The ENOSS must have an effective safeguard (such as a prompt message) that prevents routine messages from being sent out as emergency notifications and requests if the Administrators or Users has sought approval prior to sending a notification. M49. Phone Number Types: The ENOSS must have the ability to make local and long distance calls within Canada and the United States. The ENOSS must also have the ability to dial international numbers and phone numbers with extensions. M50. Order of Contact Methods: The ENOSS must allow Administrators and Users to set the default order of devices used to notify Contacts but also allow Users and Contacts to override the order if they have the appropriate permissions to do so. M51. Language of Message and Contacts: The ENOSS must allow Administrators and Users to select Messages in either French or English and to automatically transmit them in the Contact's pre-selected corresponding language. M52. Simultaneous Transmission: The ENOSS must allow Users to send a recorded voice message and a text message in a single notification to all selected Contacts for delivery through the media listed in M47. M53. Caller ID: Either globally or on a message-by-message basis, the ENOSS must allow Administrators and Users initiating a message to customize the telephone number displayed (caller ID) for voice Messages and the e-mail addresses for text-based Messages. M54. Escalation: The ENOSS must escalate messages when the intended Contact has not confirmed receipt of the correspondence (with 3 levels of person-to-person escalation) within a given period of time. If no confirmation of receipt is received within a given period of time, then the message will be redirected to an alternate point of contact if one has been designated see M58. M55. Delivery Attempts: The ENOSS must allow Users and Administrators to select the number of delivery attempts through all Contact paths. M56. E-mail Attachments: The ENOSS must allow e-mails to attach multiple files (e.g. text, spreadsheet and images) and send them to an e-mail device. M57. Message Control: The ENOSS must allow an Administrator or User to stop, recall or replace a Message initiated by them or another Administrator or User with the same level of permissions at any time during the Message sending process. M58. Back-Up Contacts: The ENOSS must automatically send messages to a back-up Contact if a primary Contact does not acknowledge receipt of the initial message within a period of time defined by the sender. M59. First to Respond: The ENOSS must have the capability to send notifications systematically until a predetermined number of affirmative responses are received. M60. Roll Call: The ENOSS must have the capability to send notifications for the purpose of soliciting a positive or negative acknowledgement from the recipient, such as "are you OK", "Not OK". MESSAGE DELIVERY FEATURES M61. Voice Message Repeat: The ENOSS must allow Contacts to listen to a voice Message as often as desired with a single key press. M62. Acknowledgements: The ENOSS must seek and receive acknowledgements of Messages through the device types identified in M47, with the exception of facsimile and pager and SMS transmissions. M63. Re-send: The ENOSS must allow Administrators and Users to re-send a notification to only those Contacts who did not respond to the original notification. M64. Voice-Mail: The ENOSS must leave a Message when a voice-delivered message reaches an answering machine or voice-mail. If a message is left, the ENOSS must also contact the back-up Contact if the message was left on the primary Contact's voice mail box. M65. Electronic Voice: The electronic voice transmitter must use Canadian (English and French) accents. M66. Custom Response: The ENOSS must allow Contacts to send custom text-based messages in response to messages. MESSAGE MANAGEMENT M67. Recurring Messages: The ENOSS must allow Administrators and Users to set up recurring Messages. M68. Scheduling: The ENOSS must allow Administrators and Users to schedule a notification to be sent at a future date and time. M69. Voice-Mail: The ENOSS must distinguish when a live Contact is reached versus when an answering machine or voicemail has been reached on voice-delivered devices. REPORTING M70. Dashboard: The ENOSS must provide a real-time dashboard for each active notification broadcast allowing Administrators and Users to view broadcast parameters (e.g. devices, start time, duration and number of cycles) and see status of broadcast results (e.g. confirmation and responses). M71. History: The ENOSS must allow Administrators and Users to view a history of Message results for the entire period of the contract. M72. Audit Trail: The ENOSS must produce real-time Message broadcast result reports using all application data which contains, but is not limited to, all of the following information: (i). Name, date and time of the Message; (ii). Name of the Administrator or User who initiated the broadcast; (iii). Number of redial attempts requested by initiator; (iv). Summary statistics, including total notified Contacts, total confirming receipt/not confirming receipt, percentage confirming receipt/not confirming receipt. If a polling Message, a total for each response. This information must be collated for individual messages and cumulatively; and (v). Detailed calling information, including call-result of each attempt within the broadcast, the addresses and associated phone numbers attempted, the attempt number and the result (e.g., confirmed with date and time, busy, no answer or voicemail). M73. Export: The ENOSS must export all types of report data in CSV, XLS, HTML, or PDF formats, as defined by an Administrator or User. M74. Printing: The ENOSS must allow Administrators and Users to print real-time reports of any data or statistics directly from the GUI. M75. Reports: Upon request, the Service Provider must search and generate reports based on user-defined criteria and/or key words including wild card searches. In addition, the Service Provider must retain a permanent record of all reports. APPLICABILITY OF THE TRADE AGREEMENT(S) TO THE PROCUREMENT - Agreement on Internal Trade (AIT) - North American Free Trade Agreement (NAFTA) JUSTIFICATION FOR THE PRE-IDENTIFIED SUPPLIER ERMS Advantage is a fully hosted, off-the-shelf, web-based emergency notification and management solution that is used by organizations for the purpose of managing their vital emergency processes, enabling effective communications and management of crisis situations and incidents. ERMS Advantage supports Agriculture & Agri-Food Canada's emergency notification requirements without any additional configuration to our IT infrastructure. ERMS Advantage will allow Agriculture & Agri-Food Canada to effectively manage and maintain its self-registered contact data and issue security threat notifications in fully redundant and secure hosting facilities. ERMS Advantage fully satisfies AAFC's requirements for a Bilingual (English/French) Emergency Mass Notification System as per the criteria identified. ERMS Advantage fully satisfies AAFC's security requirements for a hosted Protected "A" solution. GOVERNMENT CONTRACTS REGULATIONS EXCEPTION(S) Section 6 of the Government Contract Regulations is being invoked in this procurement as only one person or firm is capable of performing the contract. EXCLUSIONS AND/OR LIMITED TENDERING REASONS Annex 4.4 article 506.12(b) of the AIT is applicable on the basis of limited tendering where there is an absence of competition for technical reasons and the goods or services can be supplied only by a particular supplier and no alternative or substitute exists, respectively. Article 1016.2(b) of NAFTA is applicable on the basis of limited tendering due to reasons where, for works of art, or for reasons connected with the protection of patents, copyrights or other exclusive rights, or proprietary information or where there is an absence of competition for technical reasons, the goods or services can be supplied only by a particular supplier and no reasonable alternative or substitute exists. OWNERSHIP OF INTELLECTUAL PROPERTY Ownership of any Foreground Intellectual Property arising out of the proposed contract will vest in the Contractor. THE PERIOD OF THE PROPOSED CONTRACT OR THE DELIVERY DATE(S) The proposed contract is for a period of 1 year that includes 4 additional 1-year options. All delivery mentioned in the requirement shall be delivered within 10 days of Contract award. NAME AND ADDRESS OF THE PRE-IDENTIFIED SUPPLIER: ERMS Solutions Limited 2916 S Sheridan Way #300 Oakville, Ontario L6J 7J8 SUPPLIERS' RIGHT TO SUBMIT A STATEMENT OF CAPABILITIES Suppliers who consider themselves fully qualified and available to provide the goods, services or construction services described in the ACAN, may submit a statement of capabilities in writing to the contact person identified in this notice on or before the closing date of this notice. THE STATEMENT OF CAPABILITIES MUST CLEARLY DEMONSTRATE HOW THE SUPPLIER MEETS THE ADVERTISED REQUIREMENTS. The conditions of the developer's shrink-wrap license are not acceptable to the Crown. This software is proprietary, and the proposed Contractor must have the authority to negotiate the terms and conditions of the contract and the related software licensing terms including, but not limited to; limitation of liability, indemnification, transferability of license, termination/refund to the Crown. Documents may be submitted in either official language of Canada INQUIRIES AND SUBMISSION OF STATEMENTS OF CAPABILITIES Inquiries and statements of capabilities are to be directed to: Jonathan Vinet Contracting Authority Public Works and Government Services Canada Gatineau, Québec, Canada K1A 0S5 Jonathan.vinet@tpsgc-pwgsc.gc.ca Telephone 819-956-2940 Government of Canada Delivery Date: Above-mentioned You are hereby notified that the government intends to negotiate with one firm only as identified above. Should you have any questions concerning this requirement, contact the contracting officer identified above. An Advance Contract Award Notice (ACAN) allows departments and agencies to post a notice, for no less than fifteen (15) calendar days, indicating to the supplier community that it intends to award a good, service or construction contract to a pre-identified contractor. If no other supplier submits, on or before the closing date, a Statement of Capabilities that meets the requirements set out in the ACAN, the contracting authority may then proceed with the award. However, should a Statement of Capabilities be found to meet the requirements set out in the ACAN, then the contracting authority will proceed to a full tendering process. Suppliers who consider themselves fully qualified and available to provide the services/goods described herein, may submit a statement of capabilities in writing to the contact person identified in this Notice on or before the closing date of this Notice. The statement of capabilities must clearly demonstrate how the supplier meets the advertised requirements. The PWGSC file number, the contracting officer's name and the closing date of the ACAN must appear on the outside of the envelope in block letters or, in the case of a facsimile transmission, on the covering page. The Crown retains the right to negotiate with suppliers on any procurement. Documents may be submitted in either official language of Canada.