1 1

RETURN BIDS TO: Title - Sujet RETOURNER LES SOUMISSIONS À: Translation Management System proje Bid Receiving - PWGSC / Réception des Solicitation No. - N° de l'invitation Date soumissions - TPSGC EN966-172902/A 2017-06-14 11 Laurier St. / 11, rue Laurier Client Reference No. - N° de référence du client GETS Ref. No. - N° de réf. de SEAG Place du Portage, Phase III EN966-172902 PW-$$EE-019-31602 Core 0B2 / Noyau 0B2 Gatineau File No. - N° de dossier CCC No./N° CCC - FMS No./N° VME Quebec 019ee.EN966-172902 K1A 0S5 Time Zone Bid Fax: (819) 997-9776 Solicitation Closes - L'invitation prend fin at - à 02:00 PM Fuseau horaire Eastern Daylight Saving on - le 2017-07-14 Time EDT LETTER OF INTEREST F.O.B. - F.A.B. LETTRE D'INTÉRÊT Plant-Usine: Destination: Other-Autre:

Address Enquiries to: - Adresser toutes questions à: Buyer Id - Id de l'acheteur Azma, Najat 019ee Telephone No. - N° de téléphone FAX No. - N° de FAX (873) 469-3995 ( ) ( ) - Destination - of Goods, Services, and Construction: Destination - des biens, services et construction: DEPARTMENT OF PUBLIC WORKS AND GOVERNMENT SERVICES CANADA 70, RUE CREMAZIE Gatineau Quebec K1A0S5 Canada

Comments - Commentaires

Instructions: See Herein

Instructions: Voir aux présentes

Vendor/Firm Name and Address Raison sociale et adresse du fournisseur/de l'entrepreneur Delivery Required - Livraison exigée Delivery Offered - Livraison proposée See Herein

Vendor/Firm Name and Address Raison sociale et adresse du fournisseur/de l'entrepreneur

Telephone No. - N°de téléphone Facsimile No. - N° de télécopieur Issuing Office - Bureau de distribution Name and title of person authorized to sign on behalf of Vendor/Firm Systems Software Procurement Division / Division des (type or print) achats des logiciels d'exploitation Nom et titre de la personne autorisée à signer au nom du fournisseur/ 11 Laurier St. / 11 rue, Laurier de l'entrepreneur (taper ou écrire en caractères d'imprimerie) 4C1, Place du Portage, Phase III Gatineau Quebec K1A 0S5 Signature Date

Page 1 of - de 1

Request for Information

Regarding

Translation Management System

FOR

Translation Bureau

Page 1 of 59

Table of Contents

PART 1 – BACKGROUND AND PURPOSE 5 1.1 Background 5 1.2 Purpose 6 PART 2 - REQUEST FOR INFORMATION 8 2.1 Nature of Request for Information 8 2.2 Nature and Format of Responses Requested 8 2.3 Response Costs 8 2.4 Treatment of Responses 8 2.5 Content of this RFI 9 2.6 Format of Responses 9 2.7 Enquiries 10 2.8 Submission of Responses 10 2.9 Languages 11 2.10 Industry Consultation Session 11 PART 3: HIGH LEVEL OVERVIEW OF TMS SOLUTION REQUIREMENTS 12 3.1 Solution Build 12 3.2 Language 12 3.3 Security Management 12 3.4 Standards, guidelines, and specifications 12 3.5 Workflow Management 13 3.6 Workload Management 13 3.7 Translation Tools 13 3.8 System and Tool Integration 13 3.9 Content Management System 14 3.10 Business Intelligence 14 3.11 Portal and Dashboards 15 PART 4: QUESTIONS 16 4.1 Language 16 4.2 System Requirements 16 4.3 Page Layout 17

Page 2 of 59

4.4 Web Analytics 17 4.5 3rd Party Plugin (Add-in) 18 4.6 Web Service – Application Programming Interface (API) 18 4.7 Performance 19 4.8 Content Management System (CMS) 20 4.9 Content Relationship Management (CRM) 21 4.10 Web Content Accessibility 21 4.11 Crowdsourcing 22 4.12 Software Application 22 4.13 Host Environment 22 4.14 Vendor Profile 23 4.15 Database 24 4.16 Server Environment 25 4.17 Security 26 4.18 Log Files and Audit 29 4.19 Data Migration 30 4.20 Data – Import and Export 30 4.21 Reporting 30 4.22 Data Archival 32 4.23 Licensing 32 4.24 Backup and Restore 33 4.25 Business Continuity and Disaster Recovery 34 4.26 Implementation Details 35 4.27 Post Implementation Details 36 4.28 Support 37 4.29 Maintenance 37 4.30 Service Level Agreement (SLA) 38 4.31 Training and Documentation 39 4.32 Portal 40 4.33 Translation Environment Tools 41 4.34 Business Intelligence (BI) 47 4.35 Financial Management 49

Page 3 of 59

4.36 Workflow and Workload Management (Translation and Interpretation) 49 4.37 Metadata 54 4.38 Business Rule Management System 54 4.39 User Profile Management 55 Annex A : Government of Canada Security Categories 56 Annex B : Acronyms 57

Page 4 of 59

PART 1 – BACKGROUND AND PURPOSE

1.1 Background

The Translation Bureau (Bureau) became a Special Operating Agency (SOA) of Public Services and Procurement Canada (PSPC), formerly Public Works and Government Services Canada, (PWGSC), in 1995. The linguistic management and services program is mandated under the Translation Bureau Act (Revised Statutes of Canada, 1985).

The Bureau is:  a key component of the federal government's service delivery infrastructure,  the sole internal linguistic services provider which offers translation, revision, interpretation and other linguistic services to Parliament, the judiciary, to federal departments and agencies,  responsible for supporting the Government of Canada (GoC) in its efforts to communicate with and provide services to Canadians in the official language of their choice,  also the terminology authority within the federal government and has been mandated to develop terminology standards to ensure clear, uniform and quality communications within government.

With, some 1,300 employees, including more than 800 language professionals, 600 of which are located in the National Capital Region (Ottawa-Gatineau) and the rest across Canada with offices in Montreal, Quebec City, Toronto, Winnipeg, Moncton, Halifax, and Vancouver.

The Bureau offers its products and services in both official languages, in over 100 Aboriginal and foreign languages and in visual languages. It bills its clients for translation, terminology, linguistic and interpretation services. The Bureau translates upwards of 300 million words a year.

In addition, it is the largest employer of conference interpreters in Canada with approximately 70 staff interpreters and contracts work out to many freelancers (external resources). Staff interpreters work almost exclusively in Canada’s official languages, although some are also accredited in a third language. On average, the Bureau provides Parliament and Canadian government departments with over 18,000 days of interpretation services each year.

Over the past few years, the Bureau has looked at the efficiency and effectiveness of their programs and operations to ensure value for money, as well as to rethink business processes and service delivery platforms.

As part of the Blueprint 2020 roadmap and its four guiding principles;  An open and networked environment that engages citizens and partners for the public good.  A whole-of-government approach that enhances service delivery and value for money.  A modern workplace that makes smart use of new technologies to improve networking, access to data and customer service. Page 5 of 59

 A capable, confident and high-performing workforce that embraces new ways of working and mobilizes the diversity of talent to serve the country’s evolving needs.

The Bureau’s Strategic Business Reengineering group in close collaboration with the Chief Information Officer Branch (CIOB) of Public Services and Procurement Canada (PSPC), and Shared Services Canada (SSC) began a Transformation plan initiative in the summer of 2014 to modernize the Translation Bureau’s legacy systems and tools used to provide the Bureau’s products and services to the Government of Canada.

The Translation Bureau’s goals are to simplify and modernize its service offering by leveraging the technology to facilitate everyday work, increase efficiency and streamline business processes.

1.2 Purpose

The purpose of this project is to find a Commercial-Off-The-Shelf (COTS) Translation Management System (TMS) product that would satisfy Blueprint 2020 objectives and respond to the Bureau’s business requirement needs, both for the federal government clients across Canada and for the Bureau’s resources that process the client requests and contribute to the delivery of the products and services.

The Bureau is facing many challenges in providing and sustaining the quality of products and services that it offers to its clients with its current legacy request management system, the On-Line Ordering System, also known as IIS.

The On-Line Ordering System is an aging system that was developed in-house and has become complex to develop, enhance and expensive to maintain. Over time, many supporting tools have been developed to fill the gaps in its functionality which are isolated and non-integrated.

The Translation Bureau requires that the request management be optimized and automated to better distribute workload, increase productivity and efficiency, and make better use of internal and external resources to perform the work. The Bureau currently uses a mix of standalone internal and commercial tools to manage, track, and execute work involving too many manual interventions.

The organization is continuing to evolve and the conditions are there to enable the Bureau to move beyond service delivery as such and become a functional and technical authority in the fields of linguistic services and techno-linguistic tools.

The TMS project will replace the Bureau’s legacy On-Line Ordering System and supporting applications with COTS applications/solutions. The TMS project will integrate techno-linguistic tools into the Bureau’s work processes in order to increase efficiency in management of translation requests, client terminology, interpretation event scheduling, and improve the overall quality of services provided to clients. This strategy leverages digital technology to establish a modern approach to improve the operation and management of the translation, interpretation and terminology functions and support the financial sustainability and improved efficiency of the Page 6 of 59 program. These improvements will hopefully simplify and enhance user experience and facilitate the delivery of the products and services.

The goals of this product will be to replace and provide a comprehensive solution meeting the Translation Bureau’s requirements but not limited to:

 one that will have a suite of tools that are integrated or can be integrated seamlessly into one complete product thus allowing the decommissioning of many legacy systems,  improve the coordination, tracking, managing of the workflow and workload which now have numerous points of manual intervention,  provide business intelligence capabilities leading to better analysis and decision-making,  a solution that will provide the Bureau with the necessary security, reporting and measurement capabilities to identify deficiencies,  provide capabilities to assess and evaluate overall business performance, and operational effectiveness.

Page 7 of 59

PART 2 - REQUEST FOR INFORMATION

2.1 Nature of Request for Information

This is not a bid solicitation. This RFI will not result in any direct request for proposal or the award of any contract. As a result, potential suppliers of any goods or services described in this RFI should not reserve stock or facilities, nor allocate resources as a result of any information contained in this RFI. Nor will this RFI result in the creation of any source list. Therefore, whether or not any potential supplier responds to this RFI will not preclude that supplier from participating in any future procurement. Also, the procurement of any of the goods and services described in this RFI will not necessarily follow this RFI. This RFI is simply intended to solicit feedback from industry with respect to the matters described within this document.

2.2 Nature and Format of Responses Requested

Respondents are requested to provide their comments, suggestions, concerns and, where applicable, alternative recommendations regarding how the requirements or objectives described in this RFI could be satisfied, to the Contracting Authority identified in 2.7. Respondents are invited to respond to Canada’s questions and provide comments regarding the content, format of any draft documents included in this RFI. Respondents should explain any assumptions they make in their responses.

2.3 Response Costs

Canada will not reimburse any respondent for expenses incurred in responding to this RFI.

2.4 Treatment of Responses a) Use of Responses: The responses received may be used by Canada to develop or modify procurement strategies and/or any contracting documents, clauses, terms and conditions. Canada will review all responses received by the RFI closing date. Canada may, at its discretion, review responses received after the RFI closing date. b) Review Team: A review team composed of representatives of the Government of Canada will review the responses. c) Confidentiality: Respondents should mark any portions of their response that they Consider proprietary or confidential. Canada will handle the responses in accordance with the Access to Information Act. d) Follow-up Activity: Canada may, at its sole discretion, contact any respondents to follow up with additional questions or for clarification of any aspect of a response. e) One-on-one sessions: i) Canada may, at its sole discretion, contact any respondents to follow up with additional questions or for clarification of any aspect of a response during one- on- one industry sessions.

Page 8 of 59

ii) Canada will meet with each respondent u p o n request. Following the closing date, the Contracting Authority will follow up individually with all respondents who indicate in their responses that they wish to meet with Canada.

2.5 Content of this RFI

This RFI document consists of the following 4 sections:

Section 1: Background and Purpose This section provides a brief description of the context and the stakes behind this initiative; and the objective of this Industry Engagement process. Section 2: Request for Information This section provides information concerning the preparation, submission of responses to this RFI and the treatment of responses process. Section 3: High Level Overview of TMS Solution Requirements This section provides a high level description of the TMS solution requirements. Section 4: Questions This section includes specific questions to industry regarding the TMS Solution Requirements.

This document remains a work in progress and respondents should not assume that new clauses or requirements will not be added to any bid solicitation that is ultimately published by Canada. Nor should respondents assume that none of the clauses or requirements will be deleted or revised. Comments regarding any aspect of the draft document are welcome. If respondents feel a question or key area has been missed, we welcome comments or information to this fact in the response.

2.6 Format of Responses a) Cover Page: If the response includes multiple volumes, respondents are requested to indicate on the front cover page of each volume the title of the response, the solicitation number, the volume number and the full legal name of the respondent. b) Title Page: The first page of each volume of the response, after the cover page, should be the title page, which should contain: i. the title of the respondent’s response and the volume number; ii. the name and address of the respondent; iii. the name, address and telephone number of the respondent’s contact; iv. the date; and Page 9 of 59

v. the RFI number. c) Numbering System: Respondents are requested to prepare their response using a numbering system corresponding to the one in this RFI. All references to descriptive material, technical manuals and brochures included as part of the response should be referenced accordingly. d) Number of Copies: Canada requests that respondents submit 2 electronic copy and paper copies of their responses (the electronic file formats of the responses must be in either Adobe Portable Document Format (PDF) TM or in a file format that is readable by the MS Office 2007 minimum). 2.7 Enquiries

Because this is not a bid solicitation, Canada will not necessarily respond to enquiries in writing or by circulating answers to all potential suppliers. However, respondents with questions regarding this RFI may direct their enquiries to:

Contracting Authority: Najat Azma E-mail Address: [email protected] Telephone: 873-469-3995

2.8 Submission of Responses a) Time and Place for Submission of Responses: Suppliers interested in providing a response should deliver it to the following location by the time and date indicated on page 1 of this document:

Department of Public Works and Government Services Bid Receiving Unit Portage III, 0A1 11 Laurier Street Gatineau, Quebec K1A 0S5

Responses should not be sent directly to the Contracting Authority. b) Responsibility for Timely Delivery: Each respondent is solely responsible for ensuring its response is delivered on time to the correct location. c) Bid Receiving Unit Address Solely for Delivery of Responses: The above address is only for bid submission. No other communications are to be forwarded to this address. d) Identification of Response: Each respondent should ensure that its name and return address, the solicitation number and the closing date appear legibly on the outside of the response.

Page 10 of 59

2.9 Languages

Responses and consultation meetings are to be provided a n d held in one of the two Official Languages of Canada (English or French).

2.10 Industry Consultation Session

2.10.1 One-on-One Industry Sessions: A maximum of two (2) hours of One-on-One Industry Sessions, with representatives of Canada, will be held at the date and time provided by the Contracting Authority (agreeable to both Canada and the respondents).

It is the responsibility of the respondents to confirm the date and time of their meeting, as well as their attendance to the Contracting Authority.

These time-limited sessions will provide an opportunity for respondents to seek clarification and to present input for the upcoming requirement. Respondents are asked to please refrain from using their One-on-One Industry Sessions as a forum for marketing purposes.

Participation at the One-on-One Industry sessions is not required in order to submit a response to the RFI nor any follow-on RFP.

Following the submission of written responses to Canada, respondents may be invited to present their responses at One-on-One Industry Sessions with representatives of Canada.

Respondents may be invited to a One-on-One Session at Canada's discretion. Canada will meet with each respondent that requests a One-on-One Session.

2.10.2 Location of the One-on-One Industry Sessions: The One-on-One Industry Sessions will be occurring at government facilities within the National Capital Region of Ottawa/Gatineau, Canada and their location will be provided at time of registration.

Note: Sessions can be conducted by Teleconference and Videoconference.

Page 11 of 59

PART 3: HIGH LEVEL OVERVIEW OF TMS SOLUTION REQUIREMENTS The following table provides a brief high level function description of the key areas that the TMS solution should, provide:

Description Functionality 3.1 Solution Build Solution Build: The extent will be to specify On-prem and hosted (Cloud): Details should be the details on the options available to provided on but not limited to architecture, provide the solution and the suite of tools in infrastructure (components, hardware), terms of but not limited to architecture, software, scalability, performance, configuration, infrastructure and software. licensing, database, system requirements, security measures, and tools provided. 3.2 Language Language: The extent to which the solution French and English (Mandatory): The solution and suite of tools support both official and suite of tools must support and be languages at all levels. available in both of Canada’s official languages: French and English. 3.3 Security Management Security Management: The extent to which Access rights and permissions: The solution the solution can protect networks, must allow a user with the appropriate computers, programs and safeguard credentials to set access to but not limited to sensitive information such as protected and workflows, tasks, dashboards, portals, reports, classified documents (see Annex A for analytics based on type and role of user or description), support financial data and group of users. personal information including the systems that are used to process or store it from Profile definition capability: The solution attack and damage by unauthorized access. should deliver, enable and support manual and automated, rule-based, role-based and/or In addition, the solution and suite of tools group-based access control. should also incorporate identity and access Security: The solution and suite of tools should management capabilities to manage roles, include security features and functionalities such user access rights and permissions to the as but not limited to certificate-based digital interface and to the various components signatures, encryption, SSL/TLS secure network that make up the solution and tools. communication, and intrusion detection. 3.4 Standards, guidelines, and specifications Standards, guidelines, and specifications: Accessibility: Compliance with Web Accessibility The extent to which the solution and suite of Initiative (WAI), Web Content Accessibility tools comply with industry standards, Guidelines (WCAG) 2.0, ISO/IEC 40500:2012, guidelines, and specifications. WCAG 2.0 Conformance, and Standard on Web Accessibility.

APIs: SOAP, REST

Page 12 of 59

Security: Compliance with ISO/IEC 27001, 27002, 27017, 27018 standards and OCCI specification. 3.5 Workflow Management Workflow Management: The extent to Manual and automatic workflow: The solution which the solution should have or be able to should allow the flexibility to design and model integrate with a workflow engine in order to manual and automated workflows. define, execute and manage rules, conditions, dependencies, actions as well as Rules-based workflow: The solution should tasks to control the coordination and the allow rule conditions, dependencies and actions flow for either sequential or parallel to be defined for a single or set of tasks within a business processes. workflow.

Dynamic rules workflow adjustment: The solution should have the ability to adapt and allow adjustments within the workflow for new situations, unexpected difficulties, and failures. 3.6 Workload Management Workload Management: The extent to Dashboard: The solution should allow a user to which the solution can support the planning, but not limited to plan, schedule, assign, view, scheduling, assignment, coordination, notify, and report on the workload. distribution and management of resources, files, documents and data of an individual or Status Report: The solution should deliver, groups of individuals. enable and support the functionality to allow users to generate reports using predefined formats and ad-hoc formats. 3.7 Translation Tools Translation Tools: The solution should have Computer Aided Translation (CAT): The suite of a set of built-in tools or be able to integrate tools should include but not limited to termbases, with external systems and tools as required. term extraction, conversion (.tmx, .tbx, .xliff, pdf), corpus, translation memory, word count and match analysis, localization features, alignment, resource lookup (online and offline resources, dictionaries and reference materials), spelling and grammar checkers, quality assurance, machine translation, editor, metadata, and parallel text view. 3.8 System and Tool Integration System and Tool Integration: The extent to Web Service APIs: The solution and suite of tools which the solution can support integration should include APIs or provide the building blocks to existing Government of Canada (GoC) or to create them in order to facilitate integration to external systems and tools. and interaction with internal and external systems and tools.

Page 13 of 59

3.9 Content Management System Content Management System (CMS): The Document Development: The solution should extent to which the solution can support the deliver, enable and support the functionality to development, revision, versioning, create, update, archive, and provide version approvals, distribution, import and export, control for documents. archiving and storage, capture, retrieval (metadata), access rights and permissions, Document Automation: The solution should and administration of translation deliver, enable and support the functionality to documents. design and refine query for the selection of the appropriate document and/or template and the assembly of those documents using meta data applicable to a file (a grouping of related documents) to minimize data entry, reduce time spent proofreading and reduce risks associated with human error.

Metadata capture: The solution must capture control information such as but not limited to author, editor and escalation name, user role, creation, modification, expiry date, versioning, status and reason for change.

Control: The solution should allow distribution of documents for revision to specific people and/or groups of people with locked, non-editable portions of the documents.

Template Document Design: The solution should deliver, enable and support a template design tool that enables templates of any complexity to be developed (automated) by users for other users. 3.10 Business Intelligence Business Intelligence (BI): The extent to Reporting Capabilities: The solution and suite of which the solution and suite of tools have tools should allow but not limited to creating or can integrate with a business intelligence reports using data from any data source type, system that can perform but not limited to have web-based front end, be able to display and data mining, online analytical processing, view the data in various formats tabular, matrix, balanced scorecarding, querying and chart, and free-form report layouts in a reporting. dashboard, create and save ad hoc reports on the fly, support mobile devices.

Analytics: The solution and suite of tools should be equipped with but not limited to a range of

Page 14 of 59

filters, drop-downs, slicers and search functions, data discovery and retrieval, OLAP, data mining, interactive data exploration, balanced scorecarding, analytics and modeling. 3.11 Portal and Dashboards Portal and Dashboards: The extent to which Client, Internal and External Resources: The the solution can collect information from solution should allow the customization of any different sources and create a single point of inherent dashboard or portal. If no built-ins are access to display content and information available the solution should provide the tools to based on the intended user (client, Bureau develop and define the content, information and resource, Freelancer) and purpose. activities that can be performed by the intended user in their respective dashboard and portal.

Page 15 of 59

PART 4: QUESTIONS For response details, please refer to ”Format of Responses – section 2.6”.

4.1 Language ID CATEGORY REQUIREMENT LANG_1.0 Language What languages does your solution and suite of tools support? If other languages specify?

(This is a “Mandatory” requirement for Government of Canada (GoC) Translation Bureau (Bureau), the entire solution and suite of tools must be available in both English and French). LANG_1.1 Language Does the solution and suite of tools support but not limited to;  integrating English and French information in its database(s),  provide an English and French interface to access the solution and allowing for 'live toggling' between languages during a working session,  have the ability for users to broadcast English or French messages depending on their language of choice to other users,  allow certain fields to be entered in both official languages, regardless of the individual user’s language of choice Specify and describe including any other features and functionalities.

4.2 System Requirements ID Category Requirement SYS_REQ_1.0 System Which browser(s), and version(s) does the solution Requirement support on PC (desktop, laptop), mobile and tablet devices? Specify manufacturer, model and type.

(Minimum Internet Browser standard Microsoft IE 11, and two previous major versions for GoC).

Are there any additional requirements, limitations or potential issues with any of the browsers and versions? Indicate if any other software or plugin (add-in) is required to be installed on the user’s PC (desktop,

Page 16 of 59

4.2 System Requirements ID Category Requirement laptop), mobile and tablet devices besides the web browser. SYS_REQ_1.1 System Which operating system(s) and versions does the solution Requirement support on PC (desktop, laptop), mobile devices and tablets? Specify manufacturer, model and type.

Are there any additional requirements, constraints or potential issues with any of the operating systems and versions? Specify. SYS_REQ_1.2 System What is the minimum and recommended PC (desktop, Requirement laptop), mobile and tablet devices system requirements in terms of but not limited to;  CPU and RAM,  hard disk space,  OS and platform (x86, x64)

4.3 Page Layout ID Category Requirement PAG_LAY_1.0 Page Layout (for Specify and describe if web pages can be created and different users) customized for clients, suppliers and internal resources based on specific roles and groups such as but not limited to;  login page,  task/menu page,  context menu  search and filter capabilities.

4.4 Web Analytics ID Category Requirement WEB_ANA_1.0 Web Analytics Does the solution support web analytics? Specify whether it is in house developed, open source or 3rd party and describe how it can be used and applied. WEB_ANA_1.1 Web Analytics What are the metrics and how they are used? WEB_ANA_1.2 Web Analytics Does your solution allow demographic information to be retrieved and stored based on geo-location? Describe.

Page 17 of 59

4.5 3rd Party Plugin (Add-in) ID Category Requirement 3rdPTY_1.0 3rd Party (Plugin) Does your solution use plug-in (add-in)? Specify type and whether they are proprietary, open source or 3rd party and describe their use including the OS and version, browser and version to which it may apply. 3rdPTY_1.1 3rd Party (Plugin) How will the plug-in (add-in) be displayed in the solution to a user? 3rdPTY_1.2 3rd Party (Plugin) In what type of environment will plug-in (add- in) applications be executed? 3rdPTY_1.3 3rd Party (Plugin) Will plug-in (add-in) applications be hosted on servers external to the solution? 3rdPTY_1.4 3rd Party (Plugin) How do you certify and validate the authenticity and integrity of 3rd party plugins (add-in) for your product? Specify and describe. 3rdPTY_1.5 3rd Party (Plugin) How will your platform protect the end-user from malicious code? 3rdPTY_1.6 3rd Party (Plugin) How will you authenticate and authorize plug-in (add-in) applications?

4.6 Web Service – Application Programming Interface (API) ID Category Requirement WS_API_1.0 Web Service What types of Web Service Application Programming Application Interface (API) does your solution support and describe Programming how they could be used to integrate and interface to the Interface (API) Bureau systems but not limited to;  SIGMA (SAP - finance),  CMS (GCDOCS - Opentext),  CRM MS Dynamics,  Bureau Techno Linguistics tool box and  GoC security systems. WS_API_1.1 Web Service Describe the integration capability of the solution – is it Application possible to send or consume information from other Programming systems and how does the solution do this? Interface (API) WS_API_1.2 Web Service Are the Web Service (WS) APIs customizable? Specify and Application describe. Programming Interface (API) WS_API_1.3 Web Service Can multiple revisions of the WS API be supported Application simultaneously?

Page 18 of 59

Programming Interface (API) WS_API_1.4 Web Service Will the solution support deprecation of older versions of Application the WS API? Programming Interface (API) WS_API_1.5 Web Service Does the product have exposed WS APIs that can be called Application externally? Specify and describe. Programming Interface (API) WS_API_1.6 Web Service APIs designed without security in mind can provide an Application avenue for malicious threat actors to access sensitive Programming data. How would this be addressed for example but not Interface (API) limited to, do you maintain and provide a defined suite of applications and APIs preferably through the use of a white list, the use of RFC6749 (OAuth 2.0 Authorization Framework), RFC 6750 (OAuth 2.0 Authorization Framework: Bearer Token Usage)? Specify and describe.

4.7 Performance ID Category Requirement PERF_1.0 Performance What are the solution results and metrics used to measure the overall system performance in terms of but not limited to;  stability,  scalability,  load,  stress,  and capacity? Specify and describe how the results compare to other industry products and/or solutions. PERF_1.1 Performance Is there any additional hardware and/or software needed for proper performances of the solution and suite of tools at the server (in-house, hosted) and user (workstation) level? Specify and describe. PERF_1.2 Performance Does the solution and suite of tools have any known conflicts or incompatibilities with any software and/or hardware including but not limited to firewall products? Specify and describe. PERF_1.3 Performance How many simultaneous concurrent (office and teleworkers – remote access) users does the solution support?

Page 19 of 59

4.7 Performance ID Category Requirement PERF_1.4 Performance What performance best practices to you employ in the solution? Describe. PERF_1.5 Performance What type of performance testing do you do for baselines and benchmarking? Specify and describe. PERF_1.6 Performance In conjunction with "PERF_1.3", what is your recommended VPN configuration for maximium performance in terms of but not limited to; bandwidth requirements, VPN type (IPSec, PPTP, L2TP), protocol (tcp, udp)? Specify and describe any constraints and limitations.

4.8 Content Management System (CMS) ID Category Requirement CMS_1.0 Content Does the solution support an integrated or external CMS? Management Specify and describe including the type whether System (CMS) proprietary, open source, hybrid or 3rd party. CMS_1.1 Content What functions and features does the CMS have and how Management are they used? System (CMS) CMS_1.2 Content Does the CMS offer a customizable and configurable Management workflow process to track the requests (order), versions System (CMS) (iterations) and allow reverting to previous versions of the document or text? CMS_1.3 Content Does your CMS have a built-in search engine with but not Management limited to the ability to add keywords and tags, format System (CMS) headings, have alt tags for images that comply with accessibility guidelines and avoids duplicate content? Describe. CMS_1.4 Content Does the CMS have a dashboard to manage roles for Management editors, contributors and others, including notifications to System (CMS) files, administering multiple sites if necessary adding functionality through modules and plugins and keeping track of scheduled content and related assets? Specify and describe. CMS_1.5 Content Does the CMS allow integration with social media tools, Management to add social media sharing buttons for the most System (CMS) important sites to any page or piece of content to encourage people to share the content with their clients? Describe. CMS_1.6 Content What type of delivery mechanisms does your product Management support for partial and fully translated documents such System (CMS) Page 20 of 59

4.8 Content Management System (CMS) ID Category Requirement as but not limited to manual and automated email (single, distribution list), and FTP?

4.9 Content Relationship Management (CRM) ID Category Requirement CRM_1.0 Customer Does the solution support an integrated or external CRM? Relationship Specify and describe including the type whether Management proprietary, open source, hybrid or 3rd party. (CRM) CRM_1.1 Customer What functions and features does the solution CRM Relationship pport such as but not limited to; Management  API access capability to interface with various (CRM) platforms  being able to quickly and easily import data from existing databases  role-based views and access  ease of use,  adaptability,  scalability,  analytics, and  reporting? Specify and describe how they are used.

4.10 Web Content Accessibility ID Category Requirement WEB_ACC_1.0 Web Content What are the standards, domestic and international Accessibility guidelines that have been implemented in the solution to Guidelines accommodate persons with disabilities such as but not (WCAG) limited to;  Web Accessibility Initiative (WAI),  Web Content Accessibility Guidelines (WCAG) 2.0,  ISO/IEC 40500:2012,  WCAG 2.0 Conformance, and Standard on Web Accessibility? Specify and describe.

Page 21 of 59

4.11 Crowdsourcing ID Category Requirement CRWD_1.0 Crowdsourcing Does the product have collaborative tools that could be used to enable or facilitate crowdsourcing? Specify and describe.

4.12 Software Application ID Category Requirement SW_APP_1.0 Software - Specify and describe the client and server side Application programming languages and technology platform(s) used for building and rendering web pages such as but not limited to;  HTML 5,  CSS,  SVG,  Ajax,  Other that the solution supports or has been developed under? SW_APP_1.1 Software - Specify and describe the drivers behind the Application enhancements and evolution of your product in the past 2-3 years. SW_APP_1.2 Software - What percentage of your total employees is responsible Application for product development? SW_APP_1.3 Software - Describe the company’s policy regarding source code. Application SW_APP_1.4 Software - Specify details on your past and forecasted software Application release cycles, including hot fixes, patches upgrades and releases. SW_APP_1.5 Software - Describe the process by which application upgrades Application (patches) are performed. SW_APP_1.6 Software - How are requests for enhancements and customizations Application handled? SW_APP_1.7 Software - How are software and/or database updates provided to Application customers?

4.13 Host Environment ID Category Requirement HOST_ENV_1.0 Hosting What type of client-server options does the solution Environment support in terms of but not limited to on premise hosted, (On-prem vs standalone, hybrid, or externally hosted Cloud/SAAS? Hosted) Specify and describe.

Page 22 of 59

4.13 Host Environment ID Category Requirement HOST_ENV_1.1 Hosting Explain in detail the solution offering for a complete or Environment hybrid on premise solution indicating the impacts on but (On-prem vs not limited to changes to required staffing, costs, Hosted) schedules, project risks, training, support, SLAs, DRP, network configuration, server location, and redundancy. HOST_ENV_1.2 Hosting Explain in detail the solution offering regarding hosted Environment solution option(s) and types e.g. cloud computing such as (On-prem vs but not limited to; Hosted)  IaaS (Infrastructure-as-a-Service),  PaaS (Platform-as-a-Service),  SaaS (Software-as-a-Service) or,  Storage, Database, Information, Process, Application, Integration, Security, Management, Testing-as-a-service. HOST_ENV_1.3 Hosting Does the hosted solution comply with ISO/IEC 27001, Environment 27002, 27017, 27018 standards and OCCI specification? (On-prem vs Specify and describe. Hosted) HOST_ENV_1.4 Hosting For a hosted solution what are the bandwidth Environment specifications and configuration required for optimal (On-prem vs performance? Specify if there are any constraints and/or Hosted) limitations. HOST_ENV_1.5 Hosting What is the hosted solution uptime/availability SLA level? Environment Specify. (On-prem vs Hosted) HOST_ENV_1.6 Hosting In a hosted solution is the information and content stored Environment on your or 3rd party site in a secure isolated, segregated (On-prem vs database or on a shared database? Hosted) HOST_ENV_1.6 Hosting Is the SAAS solution governed by a Service Level Environment Agreement and/or Licensing Agreement? What are the (On-prem vs standard terms and conditions? Specify and describe. Hosted)

4.14 Vendor Profile ID Category Requirement VNDR_PROF_1.0 Vendor Profile Identify the company name, address, city, state/province, zip code/postal code, telephone, and fax numbers.

Page 23 of 59

4.14 Vendor Profile ID Category Requirement VNDR_PROF_1.1 Vendor Profile Identify the name, title, address, phone and fax numbers, and e-mail address of the primary contact person for this project. VNDR_PROF_1.2 Vendor Profile Identify any parent corporation and/or subsidiaries, if applicable. VNDR_PROF_1.3 Vendor Profile Give a brief description of the evolution of the testing solution software. Include the date of the first installed site and major developments which have occurred (e.g. new versions, new modules, specific features). Describe any previous ownership, if appropriate. VNDR_PROF_1.4 Vendor Profile Indicate the total number of installations in the last 3 years by the year of installation and the total number of current users for the proposed solution. VNDR_PROF_1.5 Vendor Profile Specify and describe if you provide consultancy services in the areas of Development, Capacity Planning, Deployment, Data Conversion, Configuration Management, Change Management, Training, Other (specify). VNDR_PROF_1.6 Vendor Profile Can you provide a short description of how your solution works for a client of similar scope and scale as ours?

4.15 Database ID Category Requirement DB_1.0 Database What database management platform and version does your product use? For example, ORACLE, MS SQL Server, Access, other - please specify. DB_1.1 Database What are the features and functionalities of your Corpus database and translation memory TM in terms of but not limited to management of the Corpus content and the memory data store? Specify and describe. DB_1.2 Database What is the maximum capacity of your internal Corpus (TM) storage? DB_1.3 Database Describe the scalability of the solution and any limitations DB_1.4 Database Name and describe the database management program utilized by the solution. DB_1.5 Database Specify if your solution supports importing or extracting information from a database? Describe the type(s) of database(s) and how this is accomplished.

Page 24 of 59

4.15 Database ID Category Requirement DB_1.6 Database As part of the solution can the frequency and time be customized for importing and exporting data from the database such as but not limited to once an hour, once a day, real-time (dynamically)? Specify and describe.

4.16 Server Environment ID Category Requirement SERV_ENV_1.0 Server Can the solution be hosted locally in a Virtual Environment Environment? Describe. Specify if there are any additional requirements, limitations or potential issues. SERV_ENV_1.1 Server Provide recommended best practices on storage Environment hardware and configuration for on-prem and hosted solution. SERV_ENV_1.2 Server Provide estimates on storage requirements, given the Environment volume of translated documents (for example: approx. 200,000 files occupying 1 GB daily and 40 GB monthly, with an estimated 30% growth per year). SERV_ENV_1.3 Server Specify and describe your server configuration and Environment architecture including but not limited to;  recommended OS and version,  RAM and CPU,  hard disk,  application servers,  web servers,  database servers,  virtual hardware equivalent specifications,  special network requirements (LAN or WAN),  cabling for communication to the server and to the existing network,  any other hardware and software requirements. SERV_ENV_1.4 Server Provide any recommendations and related supporting Environment documentation on solution redundancy/reliability. SERV_ENV_1.5 Server Specify which Enterprise Database backend is supported, Environment and which release version(s) is recommended. SERV_ENV_1.6 Server Provide detailed application installation Environment procedures/guidelines. SERV_ENV_1.7 Server Can this product work effectively on a multi-platform Environment network? Specify and describe.

Page 25 of 59

4.17 Security ID Category Requirement SEC_1.0 Security Describe the security features of the solution for on premise and hosted solution. SEC_1.1 Security The solution must conform to Security Certification & Accreditation established by Treasury Board and PSPC Security standards and GoC standards. Specify any Security Certification & Accreditation obtained by GoC or any other government and provide the type of C&A, details and client information that requested the C&A. SEC_1.2 Security Specify and describe what type of encryption would be used as part of your solution for on premise and hosted solution but not limited to;  Triple DES,  RSA,  Blowfish,  AES,  Twofish. SEC_1.3 Security Describe the type of data security that would be used to protect sensitive material based on GoC document security classifications such as Protected ‘C’, and Protected ‘B’ (see Annex A for description). SEC_1.4 Security Describe if your solution supports Token Based authentication (i.e. user login and a Token is passed to your application instead of a username and password for authentication). SEC_1.5 Security Describe how the solution provides secure storage of all client, internal and external resource information. SEC_1.6 Security Describe how the solution safeguards the confidentiality and privacy of client, internal and external resource related information and how the solution can control the access to functions and features? SEC_1.7 Security Specify if your application supports but not limited to;  LDAP Active Directory Simple Authentication and Security Layer (SASL)  either GSSAPI (Preferred) or  GSS-SPNEGO authentication mechanism. SEC_1.8 Security Specify the protocols and communication ports used between the servers. SEC_1.9 Security Provide all security details, including how the solution is tested for security vulnerabilities. Page 26 of 59

4.17 Security ID Category Requirement SEC_1.10 Security Describe all your security measures and procedures currently in place to prevent unauthorized access to the servers, applications and databases. SEC_1.11 Security Describe the user account management process. It must be able to create, modify, delete and suspend. SEC_1.12 Security What are the types of access rights and permissions available as part of the solution and how are they managed? SEC_1.13 Security Specify if an administrator with the proper credentials can modify the database parameters once the solution is live, without requiring programming knowledge. SEC_1.14 Security Specify the type of credentials required to access your solution and mechanism used to validate the user. SEC_1.15 Security Describe the process used to reset password SEC_1.16 Security Describe the procedure for the retrieval of lost credentials. SEC_1.17 Security Describe lock out rules for failed logins. SEC_1.18 Security How does the solution handle idle timeout (customizable) in terms of but not limited to;  initiating an application timeout (i.e. log off the user) after a specified number of minutes of inactivity by the user,  ensuring that no document, data or information that was being worked on is lost when a user gets locked/timed out,  requiring a user to provide their user ID and password to re-enter the application following a system-initiated lock or time-out ? Describe. SEC_1.19 Security How are the credentials (user ID and password, email information) stored e.g. encrypted? Specify and describe. SEC_1.20 Security Does the solution support "https" over TLS/SSL? Please describe. SEC_1.21 Security How does the solution work with hardware and software based security applications such as but not limited to Entrust PKI? SEC_1.22 Security Does the solution allow an authorized system administrator to but not limited to;

Page 27 of 59

4.17 Security ID Category Requirement  add, modify or cancel an individual user's access rights and permissions  grant and revoke access to various system functionalities based on an individual user's user profile? Describe. SEC_1.23 Security Does the solution allow the ability for a user to but not limited to:  change their own system access password after they have initially gained access to the application for the first time,  ability for a user to request that a temporary password be issued to them when they have forgotten or misplaced their current system access password,  requesting that a user provide their User ID and e- mail address when requesting that a temporary system access password be issued to them,  provide a user a temporary password only if the User ID and e-mail address supplied matches the information stored in the user profile ? Specify and describe. SEC_1.24 Security Does the solution support the use of digital / e-signatures for approval/authorization of various documents and does it provide the ability for users with the proper access rights and permissions to be able to remotely approve/authorize from a mobile device? Specify and describe. SEC_1.25 Security Can the solution and suite of tools accommodate different login access scenarios based on different user groups and/or role profiles? Describe and specify. SEC_1.26 Security What is the minimum connection speed required for optimal access and operation of the solution and suite of tools for remote access via secure VPN? Specify and describe. SEC_1.27 Security Can the solution be security configured to be accessible by external client, partners and suppliers via the GoC extranet over the internet and if so what type of extranet

Page 28 of 59

4.17 Security ID Category Requirement mechanism and security measures does your solution support? Describe. SEC_1.28 Security Is the user password reset (30, 60, 90 days) and password history retention (6, 12 months) customizable? Specify and describe.

4.18 Log Files and Audit ID Category Requirement LOG_ADT_1.0 Log Files and Specify and describe the types of log information that is Audit captured and stored by the solution such as but not limited to the following: LOG_ADT_1.0.1 Log Files and a) User system access by user ID with time stamp; Audit LOG_ADT_1.0.2 Log Files and b) Incorrect user ID or password; Audit LOG_ADT_1.0.3 Log Files and c) Number of login attempts; Audit LOG_ADT_1.0.4 Log Files and d) Add/Modify/Delete permission by user ID with time Audit stamps; LOG_ADT_1.0.5 Log Files and e) User activity Add/Modify/Delete of information by Audit user ID with time stamps; LOG_ADT_1.0.6 Log Files and f) Event, status, and/or error codes; Audit LOG_ADT_1.0.7 Log Files and g) Application account changes. Audit LOG_ADT_1.1 Log Files and Specify if the log files can be generated manually and Audit automatically. How is this done? LOG_ADT_1.2 Log Files and Specify and describe if the solution can allow the setup of Audit a distribution list to send the log information using on- demand, pre-determined distribution schedule(s). LOG_ADT_1.3 Log Files and In what format can the log files be exported in such as but Audit not limited to csv, and excel? LOG_ADT_1.4 Log Files and Does the solution allow the auditing data and information Audit being captured and reported on to be configurable or altered by authorized users in order to meet changing audit requirements? Specify and describe. LOG_ADT_1.5 Log Files and Does the solution support reporting or query functions for Audit auditing purposes that will provide information on the creation, modification, viewing, and deletion of data or data sets within the application, and by whom? Specify and describe.

Page 29 of 59

4.18 Log Files and Audit ID Category Requirement LOG_ADT_1.6 Log Files and Can the solution be configured to monitor transactions Audit and information sent and received between systems? Specify and describe.

4.19 Data Migration ID Category Requirement DTA_MIG_1.0 Data Migration Specify the recommended approach for a data conversion Services and data migration plan including a description of what the Bureau needs to do to prepare existing data for import and integrity validation into the solution database. DTA_MIG_1.1 Data Migration Specify the approach you would take relative to the Services conversion of existing Bureau data to the new solution. Consider the following in the response and explain in detail. DTA_MIG_1.2 Data Migration a) Database analysis and data mapping Services DTA_MIG_1.3 Data Migration b) Conversion program writing Services DTA_MIG_1.4 Data Migration c) Data integrity checking and audit methodology Services DTA_MIG_1.5 Data Migration d) Post-conversion clean up Services DTA_MIG_1.6 Data Migration e) Methodologies used to keep data in sync between the Services new and legacy systems during implementation.

4.20 Data – Import and Export ID Category Requirement DTA_IMPEXP_1.0 Data Import - What type of tools does the solution support natively for Export data import and export? Specify and describe DTA_IMPEXP_1.1 Data Import - What are the file format(s) that can be used for import Export and export? Specify.

4.21 Reporting ID Category Requirement RPT_1.0 Reporting Describe the solution’s reporting features, functionalities, and how they can be used. RPT_1.1 Reporting Are all the necessary components for reporting, querying and analysis included as part of the solution? Specify and describe.

Page 30 of 59

4.21 Reporting ID Category Requirement RPT_1.2 Reporting Can reports be generated from all the components that make up the solution? Specify if there are any constraints and/or limitations to the reporting. RPT_1.3 Reporting What type of reporting does your solution support such as but not limited to predefined (canned), user defined (customizable), exception based, executive level summary reports? Describe. RPT_1.4 Reporting What report delivery mechanisms does your product support such as but not limited to manual and automated email (single, distribution list), and ftp? RPT_1.5 Reporting Can the solution integrate with external tools such as but not limited to;  MS Dynamics (CRM),  Cognos,  SAP,  and Crystal reports? Specify and describe. RPT_1.6 Reporting What formats can the reports be exported in such as but not limited to xls, xlsx, csv, doc, and pdf? RPT_1.7 Reporting Can the reporting tool treat a spreadsheet or csv file as a data source and create reports based on queries to the spreadsheet? RPT_1.8 Reporting Does the reporting tool include an automated scheduler to enable unattended running and distribution of reports? RPT_1.9 Reporting Does the solution allow predefined and customized reports to be generated in real time, weekly, monthly and yearly? Specify. RPT_1.10 Reporting Does the solution support dynamic report template creation based on an industry standard such as but not limited Adobe PDF Forms or are the templates a proprietary format? RPT_1.11 Reporting Does the solution include report dashboard(s) that can be customized for clients, internal resources, external suppliers and executives? Describe. RPT_1.12 Reporting In what languages can the reports be generated in (English and French are mandatory for GoC)? Specify. RPT_1.13 Reporting Can the report dashboard be customized by the end user? RPT_1.14 Reporting Does the solution provide static and customizable report views to display the information in various forms such as

Page 31 of 59

4.21 Reporting ID Category Requirement but not limited to graphs and/or charts? Specify and describe. RPT_1.15 Reporting Where is the report data stored and in what format? RPT_1.16 Reporting Can the access and the level of customization to the reports be managed using user and/or role based access rights and permissions and to what level of granularity? Describe. RPT_1.17 Reporting Does the solution provide report search and filtering based on user defined parameters? Describe. RPT_1.18 Reporting Does the solution allow authorized users to generate, save and print pre-determined and/or ad-hoc operational reports based on any combination of information/data elements captured and stored within the application for a specified timeframe and can the operational reports that a user can generates be based on his/her user profile, access rights and permissions? Specify and describe.

4.22 Data Archival ID Category Requirement DATA_ARCH_1.0 Data Archival What are the business rules used by the solution for (On-prem vs archiving data? Specify and describe Hosted) DATA_ARCH_1.1 Data Archival Specify and describe if the archival rules can be modified (On-prem vs by administrator. Hosted) DATA_ARCH_1.2 Data Archival How long the data can be archived for? Specify and (On-prem vs describe Hosted) DATA_ARCH_1.3 Data Archival How can the archived data be retrieved? Specify and (On-prem vs describe. Hosted) DATA_ARCH_1.4 Data Archival What are the file purging/archiving methodology used by (On-prem vs the proposed solution? Describe. Hosted)

4.23 Licensing ID Category Requirement LIC_1.0 Licensing What is the solution licensing model and options available? Specify and describe. LIC_1.1 Licensing Based on the licensing model and on available options, how is the solution priced? Specify and describe.

Page 32 of 59

4.23 Licensing ID Category Requirement LIC_1.2 Licensing Does the licensing model and pricing differ for an on-prem vs hosted (Cloud -SAAS) solution? Describe. LIC_1.3 Licensing Are there any initial (one-time) costs for the solution? Describe. LIC_1.4 Licensing Does the cost remain static throughout the life of the contract or does the cost increase on an annual basis and at what rate? Specify and describe. LIC_1.5 Licensing Describe the method by which licenses are renewed and/or added to the original contract. Are there any administrative fees? Specify and describe. LIC_1.6 Licensing Are discounts offered for volume purchasing? What are the increments in which licenses are offered – e.g. 1-49, 50-99, 100-499, 500 to 999, 1,000 to 1,500, unlimited? LIC_1.7 Licensing What services do you provide as part of your licensing e.g. updates, technical support? LIC_1.8 Licensing If a 3rd party is used as part of the solution is the licensing included as part of the cost? LIC_1.9 Licensing Provide a cost for a stated number of concurrent users as well as a cost for an unlimited user site license for the software if these are part of your licensing model. Costs for both options must be included. LIC_1.10 Licensing Is there a guaranteed cost per user for any incremental user licenses which could be purchased in the future as a result of business growth?

4.24 Backup and Restore ID Category Requirement BCKUP_RSTR_1.0 Backup and What is your solution backup and restore strategy? Restore Describe. BCKUP_RSTR_1.1 Backup and Are there any backup and restore procedures built-in the Restore solution? BCKUP_RSTR_1.2 Backup and Are there any commercial backup agents and technology Restore used? Specify and indicate if there are any restrictions or limitation with the commercial backup agents and technologies provided. BCKUP_RSTR_1.3 Backup and What is the frequency and time of day of the backups? Restore Describe. BCKUP_RSTR_1.4 Backup and Describe the solution restore procedures, communication Restore plan and turn-around times. BCKUP_RSTR_1.5 Backup and Where are the backups stored e.g. on site, off site, 3rd Restore party? Specify and describe.

Page 33 of 59

4.24 Backup and Restore ID Category Requirement BCKUP_RSTR_1.6 Backup and Describe the ability of the proposed solution to support Restore fail-safe data storage in terms of but not limited to redundancy, and mirrored. BCKUP_RSTR_1.7 Backup and Does the solution support real time backups? Specify and Restore describe.

4.25 Business Continuity and Disaster Recovery ID Category Requirement BIZCON_DISREC_1.0 Business Does the solution include Business Continuity and Continuity and Disaster Recovery Plan? Specify and describe. Disaster Recovery (hosted solution only) BIZCON_DISREC_1.1 Business Does the Business Continuity Plan support any standards Continuity and such as but not limited to ISO 22301:2012? Specify. Disaster Recovery (hosted solution only) BIZCON_DISREC_1.2 Business Describe what type of disaster recovery support that Continuity and would be readily available as part of the solution. Disaster Recovery (hosted solution only) BIZCON_DISREC_1.3 Business In the event of data corruption what type of data recovery Continuity and utilities does the solution support? Describe. Disaster Recovery (hosted solution only) BIZCON_DISREC_1.4 Business Provide details on your recovery point objective (RPO) Continuity and and recovery time objective (RTO). Disaster Recovery RPO - up to what point in time could the Business (hosted solution Process’s recovery proceed tolerably given the volume of only) data lost during that interval? Example: If the last available good copy of data upon an outage is from 18 hours ago, and the RPO for this business is 20 hours then we are still within the parameters of the Business Continuity Plan’s RPO Page 34 of 59

4.25 Business Continuity and Disaster Recovery ID Category Requirement

RTO - how much time did it take to recover after notification of business process disruption? BIZCON_DISREC_1.5 Business Describe your proposed disaster recovery plan for the Continuity and Bureau to ensure that the proposed solution is Disaster recoverable in the event of a disaster and that the data is Recovery safe and secure. (hosted solution only) BIZCON_DISREC_1.6 Business For Hosted solution, are periodic data exports available so Continuity and that a copy of the Bureau’s data can be kept at your Disaster location? Specify and describe. Recovery (hosted solution only)

4.26 Implementation Details ID Category Requirement IMPLEM_1.0 Implementation Describe your recommended implementation Details methodology, approach and time required. IMPLEM_1.1 Implementation Specify the estimated Bureau staffing requirements for Details project implementation (Time required & tasks that will be assigned to systems analysts, end-users, administrator, etc.) IMPLEM_1.2 Implementation Provide details on the project implementation and Details transition plans for implementing the solution and for transitioning the responsibility of system operation from the proponent to the Bureau resources. This plan includes all the necessary activities to perform and procedures to follow to ensure a smooth and satisfactory hand-off. IMPLEM_1.3 Implementation Provide an outline of proposed implementation program Details including all high-level tasks, timelines, project milestones, communication plans, etc. IMPLEM_1.4 Implementation Describe the typical training program and knowledge Details transfer activities delivered pre implementation, if applicable.

Page 35 of 59

4.27 Post Implementation Details ID Category Requirement POST_IMPLEM_1.0 Post Specify typical internal resource requirement to support Implementation and maintain the solution after initial implementation. Details POST_IMPLEM_1.1 Post What type of technical knowledge and skill level is Implementation required from internal resources to support the solution? Details Specify and describe. POST_IMPLEM_1.2 Post Describe how the Bureau technical personnel would Implementation become familiar with the solution in the following areas Details but not limited to;  development tools,  utilities,  queries,  interfaces,  system administration especially in the initial stages of testing and implementation,  database administration during the initial stages of implementation and subsequent performance tuning later in the implementation,  workflow and GUI customization,  support release management,  and form (template) creation. POST_IMPLEM_1.3 Post What type of functional expertise would you provide to Implementation the Bureau resources to enable the understanding and to Details develop knowledge in the various aspects of your solution so it can best be utilized such as but not limited to;  assistance and guidance with development of the business rules and applying them to the solution,  fit ,gap and systems analysis of existing solution,  assistance in the development of data interfaces to and from external systems,  assistance in the conversion of existing data? Specify and describe.

Page 36 of 59

4.28 Support ID Category Requirement SUPP_1.0 Support What type of online and offline technical support and service do you provide with the solution but not be limited to;  support levels,  email,  Interactive Voice Response (IVR) and phone,  web conferences,  toll-free numbers,  weekdays and weekends (regular/extended business hours, 7/24 coverage),  knowledge base,  forums and blogs  any other form of technical support? Specify. SUPP_1.1 Support Provide details on your support structure and incident management process in terms of but not limited to;  prioritization,  escalation paths,  time to respond,  and time to resolve. SUPP_1.2 Support In what languages is your technical support provided in (this would apply to implementation, deployment and launch)? (must be available in both English and French) SUPP_1.3 Support Where is your technical support center(s) located? SUPP_1.4 Support What are the options and the cost structure for on-going solution support? What is included? SUPP_1.5 Support What type of warranty do you provide on the solution? Specify the type, duration, inclusions and exclusions of the warranty. SUPP_1.6 Support Are software upgrades provided as part of the support contract?

4.29 Maintenance ID Category Requirement MAINT_1.0 Maintenance Provide details on the software maintenance options Agreement such as but not limited to;  the supply of all patches,

Page 37 of 59

4.29 Maintenance ID Category Requirement  updates and upgrades released during the contract period,  on demand patches and fixes to correct any bugs or other malfunctions detected in the solution,  consultation and information support to improve the operation of the solution. Specify and Indicate if there are any limitations and restrictions. MAINT_1.1 Maintenance Specify and describe the pricing structure, duration, Agreement inclusions and exclusions for the available maintenance options. MAINT_1.2 Maintenance Specify the types, frequency, duration, notification (pre Agreement and post activities), and procedures (roll back) of your maintenance window schedule and when they are performed? MAINT_1.3 Maintenance Outline the service and maintenance costs for the Agreement solution as proposed. MAINT_1.4 Maintenance Approximately how often are major software updates Agreement offered for purchase? What other costs will contribute to the total cost of ownership of this product (for example: support, training and management)? MAINT_1.5 Maintenance For hosted solution what has been your average monthly Agreement downtime over the past 2 years? Differentiate between planned (maintenance window) and unplanned (outages)?

4.30 Service Level Agreement (SLA) ID Category Requirement SLA_1.0 Service Level What is your service level agreement (SLA) structure? Agreement (SLA) SLA_1.1 Service Level Explain your service level agreement (SLA) metrics. Agreement (SLA) SLA_1.2 Service Level Describe if there are any underpinning contracts with Agreement other vendors, or service providers that could impact your (SLA) (SLA). Please describe the under-pinning SLA contract agreement with these vendors and service providers. SLA_1.3 Service Level Describe your SLA commitment by providing details: Agreement (SLA) Page 38 of 59

4.30 Service Level Agreement (SLA) ID Category Requirement SLA_1.3.1 Service Level a) On standard service levels offered; Agreement (SLA) SLA_1.3.2 Service Level b) On customer service delivery methods; Agreement (SLA) SLA_1.3.3 Service Level c) On the number and locations of service support Agreement offices; (SLA) SLA_1.3.4 Service Level e) On usage limits (number of contact people on campus Agreement that can make use of the service). (SLA)

4.31 Training and Documentation ID Category Requirement TRNG_DOC_1.0 Training and In what languages are the help tools and documentation Documentation available (English and French is mandatory for GoC)? TRNG_DOC_1.1 Training and What are the types of help tools that are available such as Documentation but not limited to;  on-line help search,  context specific help within the application,  knowledge base,  forums and blogs,  user guides, tutorials, and job aids? Specify. TRNG_DOC_1.2 Training and Specify to what extent if any, the Bureau can modify and Documentation customize the help Information and documentation. TRNG_DOC_1.3 Training and Describe the training options offered and include a list of Documentation all training types and/or courses offered such as but not limited to;  self-serve (computer based),  webinars,  user conferences,  on site,  tutorials,  application training test site (on-line either web- based or intranet based) accessible to all users from their workstation mirroring the full current functionality of the live production environment. Page 39 of 59

4.31 Training and Documentation ID Category Requirement Specify. TRNG_DOC_1.4 Training and Specify how the documentation is provided such as but Documentation not limited to wiki based, CD-ROM, and hard copy. TRNG_DOC_1.5 Training and How often is the documentation and help tools updated? Documentation TRNG_DOC_1.6 Training and How much training is required in order to administer, Documentation manage and use the solution? TRNG_DOC_1.7 Training and Does the solution allow users to input, view, export and Documentation print all screens based on access rights and permissions? Describe. TRNG_DOC_1.8 Training and Does the solution provide the ability to manage the Documentation documentation and information requirements, guidelines and preferences of clients related to all services such as but not limited to the information and documentation provided by the client and those that would be produced on premise by the Translation Bureau staff? TRNG_DOC_1.9 Training and Does the solution allow managing the life cycle of Documentation information and provide the ability to pre-set reminders for revision of information to the resource in charge of defined data?

4.32 Portal ID Category Requirement PORTAL_1.0 Portals Does the solution have built-in web portal templates that can be used and customized for clients, suppliers (external resources) and internal Bureau resources? PORTAL_1.1 Portals What are the features and functionalities that are available or can be applied as part of the solution to the portals such as but not limited to;  enabling, disabling and customizing the type of information, content, views and functions based on user role and portal type  control permissions,  advanced file sharing,  client and supplier file upload and download,  file categories and filters,  remote file storage,  messaging,  private and secure portal and login,

Page 40 of 59

4.32 Portal ID Category Requirement  invoicing clients,  invoice details,  customize the design (create templates, colors, layouts, font size, menus, toolbar locations)? Specify. PORTAL_1.2 Portals If the solution does not have any built-in customizable portal templates for client, supplier (external resources) and internal Bureau resources can they be created? Specify and describe how this can be done.

4.33 Translation Environment Tools ID Category Requirement TOOLS_1.0 Translation Specify and describe the suite of tools inherent to your Environment solution such as but not limited to; Tools  machine translation,  terminology management,  spell checkers,  QA checks,  document conversion,  analyser (document and text),  editor TOOLS_1.1 Translation Does the solution provide document analysis and pre- Environment translation in terms of but not limited to; Tools  redundancy checks and calculations,  match rates (exact/fuzzy),  customisation of fuzzy match rate,  word count (setting and calculations),  repetitions,  display and customization of parameters,  setting scale (based on task, subtask, product or service)  and result exporting formats? Specify and describe the features and functionalities and how it is used. TOOLS_1.2 Translation What type of translation features and functionalities does Environment the solution support such as but not limited to; Tools  quick document translation,

Page 41 of 59

4.33 Translation Environment Tools ID Category Requirement  CAT translation (TM),  translation of documents (PDF, XML, MS-Office 2000-2016 Word, Excel, PowerPoint, and embedded objects),  websites (in different browsers IE, Chrome, Firefox),  emails in MS-Outlook 2000-2016, IM (ICQ, QIP Infium, Skype, Windows Live Messenger),  batch translation of documents,  translation editor interface,  WYSIWYG translation,  multiple (local, remote and offline synchronized) translation memories per project,  automatic insertion of 100 % and fuzzy matches, propose any available fuzzy matches even when an exact match is found,  prioritising multiple fuzzy matches, automatic recognition of the source text language, interface language selection: Russian <=> English,  language detection, modify the format of the target text? Specify and describe. TOOLS_1.3 Translation What type of terminology features and functionalities Environment does the solution support such as but not limited to; Tools  multilingual terminology management,  bilingual terminology extraction,  simultaneous searches through multiple terminology databases,  user-defined fields for terminology entries and filters, automation of terminology extraction and management processes,  terminology translation based on recognized terms in the content,  adding terms with one click,  definition and term information,

Page 42 of 59

4.33 Translation Environment Tools ID Category Requirement  check terminology against a predefined set of terms, integration with external terminology sources,  images stored with terms, prefix based term matching,  term extraction,  fuzzy terminology lookup,  multiple local term,  remote and offline synchronized term bases per project,  glossaries in text format,  glossary propagation,  import and exporting glossaries? Specify. TOOLS_1.4 Translation What type of CAT capabilities does the solution support Environment such as but not limited to; Tools  TM creation, import and export of TM content,  TM access management,  setting of filtering/cascading TM parameters,  global TM management features (search and replace, delete, undo changes),  simultaneous translations,  xLIFF support,  TMX support (version 1.4b),  metadata information on (resources, TM),  TM re-indexing,  target document post-processing,  contextual translation memories,  simultaneous searches through multiple TMs,  real-time updating of TMs,  creation and use of TM databases in the course of translation, view suggestions from the TM,  expanded features for TM databases (support of various formats and databases of various manufacturers),  format conversion,

Page 43 of 59

4.33 Translation Environment Tools ID Category Requirement  tool for machine translation efficiency evaluation,  TM editor,  fragment assembly,  duplicate removal from TM and term bases,  online sharing of TM? Specify and describe the features and functionalities and how they are used. TOOLS_1.5 Translation Does the solution CAT tool support the following segment Environment related features and functionalities such as but not Tools limited to;  confirm locked and proofread segments,  multiple comments to segments,  propagation of translated segments,  advanced highlighting,  tag management tools,  segment navigation,  identification and updates to segments,  segment history,  show/hide segments sources,  view all segments of the text or only those assigned to the user ? Specify and describe. TOOLS_1.6 Translation Does the solution's CAT tool support the following but not Environment limited to; Tools  translating tables,  text boxes,  footnotes and endnotes in context,  translating or handling headers, footers, graphics, cross-references, bookmarks, fields, hyperlinks, non-translatable text, special characters, hidden excel tabs, power point notes? Specify and describe. TOOLS_1.7 Translation What type of search capabilities does the solution Environment support such as but not limited to; Tools

Page 44 of 59

4.33 Translation Environment Tools ID Category Requirement  advanced search functions through filter definitions, simultaneous searches through local and server TMs and terminology databases,  fragment search,  target search and replace,  segmentation and consolidation of search results based on predefined criteria,  summary view of the search results content,  source and target language,  translation field,  client number? Specify and describe the search capabilities relative to the solution and suite of tools. TOOLS_1.8 Translation What type of QA features and functionalities does the Environment solution support such as but not limited to; Tools  fixing inconsistent translations, real-time (on-the- fly) quality assurance checks,  check terminology against a predefined set of terms,  enable and disable QA tasks,  punctuation and numbers check,  quality assurance report,  segment-by-segment checks,  linguistic quality assurance (LISA QA, SAE J2450 and TAUS DQF models),  detect and point out translation units where the source and the target segments are identical,  proofreading? Specify and describe. TOOLS_1.9 Translation What type of spell check and grammar checking does Environment your solution provide such as but not limited to; Tools  real-time spell and grammar checking,  right-click spelling and grammar suggestions? Specify. TOOLS_1.10 Translation Is the spell check and grammar checking proprietary, Environment open source, third-party? Specify and describe. Tools Page 45 of 59

4.33 Translation Environment Tools ID Category Requirement TOOLS_1.11 Translation What type of import, export and conversion formats does Environment the solution support? Specify and describe. Tools TOOLS_1.12 Translation What type of alignment tools does the solution support Environment such as but not limited to; Tools  automatic alignment,  on-the-fly validation and modification of alignment of imported texts? Specify and describe the features and functionalities. TOOLS_1.13 Translation Does the solution allow adding custom dictionaries to the Environment spell-checking and be able to update them, user Tools dictionary editing, comparison, merge of dictionaries, attachment of ready specialized dictionaries? Specify. TOOLS_1.14 Translation What other features and functionalities does the solution Environment and suite of tools provide such as but not limited to; Tools  global find and replace,  machine translation integration,  live preview,  auto Pick,  mark text for exclusion or review,  macro integration,  clean up scripts,  process Word documents without removing any comments, chat functionality for interconnected users,  export path rules,  merging files,  document history,  import and export many files or folders at once,  views,  package creation,  voice recognition for speech-to-text transcription, dictation and voice recognition for commands,  use of search wildcard, auto detect document format,  security level,  special characters,

Page 46 of 59

4.33 Translation Environment Tools ID Category Requirement  document splitting and reassembly,  auto saving of information/data entered,  identify, recognize and quarantine key words and/or segments that have a high security classification,  auto detect, display and record the document security classification level ? Specify and describe. TOOLS_1.15 Translation What type of versioning management capabilities does Environment the solution and suite of tools provide in terms of but not Tools limited to;  identifying and tracking successive iterations of a document across a given workflow including the type of convention and nomenclature used, retention? Specify and describe. TOOLS_1.16 Translation Describe the type of customization that is available as Environment part of the solution such as but not limited to; Tools  customizable appearance and interface,  keyboard shortcuts,  and segmentation rules. TOOLS_1.17 Translation Does the solution support Optical Character Recognition Environment (OCR) functionality? Specify and describe. Tools TOOLS_1.18 Translation What type of inside encoding does the solution and suite Environment of tools support such as but not limited to UTF-8, 16? Tools Specify.

4.34 Business Intelligence (BI) ID Category Requirement BI_1.0 Business Does your solution have Business Intelligence capabilities Intelligence and if so describe the features, functionalities and how it can be used? BI_1.1 Business Is your BI architecture proprietary or open? Specify and Intelligence describe. BI_1.2 Business What type of database or platforms does the BI support Intelligence such as but not limited to IBM DB2, MySQL, PostgreSQL, SQL Server, and Oracle? Specify.

Page 47 of 59

4.34 Business Intelligence (BI) ID Category Requirement BI_1.3 Business Does the BI support real-time data? Specify Intelligence BI_1.4 Business Does the BI allow self-service capabilities that lets end Intelligence users create their own BI and reporting applications? Describe. BI_1.5 Business Does the BI allow importing embedded data or charts Intelligence from other applications? BI_1.6 Business Does the BI allow interactive manipulation of data to be Intelligence displayed in different formats such as but not limited to graphs, and charts (gauge, line, bar)? Specify. BI_1.7 Business Does the BI support mobile devices? Specify. Intelligence BI_1.8 Business Does the BI support Data-Mart or Data-Warehouse Intelligence structures that would allow data to be pulled from other systems and used for adhoc reporting and analysis? Specify and describe. BI_1.9 Business Does the BI support operational reporting capabilities? Intelligence Describe. BI_1.10 Business Does the BI provide security to control user privileges Intelligence (parameters to control user-specific features), user specific data sources, application access on a per-user role, or per-user basis such as but not limited to displays different menu options based on role or user? Describe. BI_1.11 Business Does the BI support application activity auditing? Intelligence Describe. BI_1.12 Business Does the BI support the following but not limited to; Intelligence  ad hoc reports,  ranking reports,  executive dashboards,  interactive reporting,  pivot table/OLAP,  trend analysis and statistics,  what-if analysis,  intelligent alerts,  cloud ready BI,  collaboration,  built in ETL,  internal and external reporting? Specify and describe.

Page 48 of 59

4.34 Business Intelligence (BI) ID Category Requirement BI_1.13 Business Does the BI permit analytics on all data fields captured? Intelligence Specify and describe if there are any limitations and/or restrictions. BI_1.14 Business Does the solution support balanced scorecarding? If so, Intelligence how it is used (provide example). BI_1.15 Business Does the solution use 3rd party balanced scorecarding Intelligence tools? Specify and describe.

4.35 Financial Management ID Category Requirement FIN_1.0 Financial Does the solution support client billing and supplier Management payment? Specify and describe the features and functionalities FIN_1.1 Financial Does the solution provide the ability to create, modify and Management delete client request estimates? Specify and describe. FIN_1.2 Financial Does the solution provide the ability to generate, modify, Management delete and send the client billing and/or supplier payment? Specify and describe. FIN_1.3 Financial Does the solution provide the ability to bulk copy and Management create (e.g. clone) tasks and activities for billing? Specify and describe. FIN_1.4 Financial Does the solution support the ability to create and Management customize request (order) cost estimates and quotes that can be but not limited to;  providing summary (express) and/or detailed estimates and quotes,  manual and automatic distribution,  include approvers,  user and role based access rights and permission control, reporting? Specify and describe. FIN_1.5 Financial Does the solution support the ability to manage supplier Management and freelancer contracts? Specify and describe.

4.36 Workflow and Workload Management (Translation and Interpretation) ID Category Requirement WFWL_MGMT_1.0 Workflow and Does the solution include intelligent workflow Workload management? Specify and describe the features and Management functionalities and how it is used.

Page 49 of 59

4.36 Workflow and Workload Management (Translation and Interpretation) ID Category Requirement WFWL_MGMT_1.1 Workflow and Does the solution integrate with other external intelligent Workload workflow management applications? Specify and describe. Management WFWL_MGMT_1.2 Workflow and Does the solution provide a graphical or textual interface Workload for defining the business process flow and the activities for Management a given task(s)? Specify and describe. WFWL_MGMT_1.3 Workflow and Does the solution allow workflow simulation or the creation Workload of prototype and/or pilot versions of a particular workflow Management so that it can be tried and tested? Specify and describe. WFWL_MGMT_1.4 Workflow and Does the solution allow the flexibility to design and model Workload workflows in a variety of ways for scenarios that may Management consist of but not limited to;  multiple workflow processes working in parallel,  workflows that involve several tiers of processes that must be accomplished in a particular sequence,  or workflows have a mixture of process types? Specify and describe. WFWL_MGMT_1.5 Workflow and Does the solution support option to pre-fill forms to Workload automate repetitive processes? Describe. Management WFWL_MGMT_1.6 Workflow and Does the solution include easy to interpret visual Workload representation for a resource (Freelancers, Bureau's Management Translators and Interpreters) to check on task status at any time? Specify and describe what is available and how it can be used. WFWL_MGMT_1.7 Workflow and Does the solution allow business rules to be created, Workload modified and deleted to determine how workflow-related Management data is to be processed, routed, tracked, and controlled for a given task or activity? Specify and describe. WFWL_MGMT_1.8 Workflow and Does the solution include worklists (schedule) used to Workload identify but not limited to; Management  identifying a resource current tasks and workload along with request deadline,  date received,  priority,  calculations on task duration,  estimates when various tasks will reach an individual’s desk? Describe.

Page 50 of 59

4.36 Workflow and Workload Management (Translation and Interpretation) ID Category Requirement WFWL_MGMT_1.9 Workflow and Does the solution include manual and task automation such Workload as but not limited to creating all tasks or subtasks for each Management resource in the workflow based on a given product and service? Specify any limitations or restrictions. WFWL_MGMT_1.10 Workflow and Does the solution provide customizable event notification Workload for but mot limited to task completion, workload increase? Management Specify and describe. WFWL_MGMT_1.11 Workflow and Does the solution provide customizable distribution Workload (Routing) lists for messages/email, information sharing, Management collaboration and communication between users? Specify and describe. WFWL_MGMT_1.12 Workflow and Does the solution provide workflow process monitoring on Workload but not limited to information on current workload, future Management workload, bottlenecks (current or potential), turn-around time, missed deadlines? Specify and describe. WFWL_MGMT_1.13 Workflow and Does the solution provide access to Information over the Workload World Wide Web to supply workflow information to Management remote clients, suppliers, collaborators, or internal resources? Specify and describe how this could be done. WFWL_MGMT_1.14 Workflow and Does the solution provide tracking and logging of activities Workload about but not limited to each task, resources? Specify and Management describe how this could be done. WFWL_MGMT_1.15 Workflow and Does the solution have reporting features with strong Workload workflow analytics dashboard that could be used such as Management but not limited to;  show who is doing (or has done) what,  when the next task is likely to be accomplished,  what the workflow resources are still waiting on,  see the actual results of the work e.g. translation, interpretation? Specify and describe. WFWL_MGMT_1.16 Workflow and Does the solution provide workflow administration and Workload security to but not limited to identify the participants and Management their respective privileges as well as to administer routines associated with any application such as but not limited to file back-ups, archiving of logs? Specify and describe.

Page 51 of 59

4.36 Workflow and Workload Management (Translation and Interpretation) ID Category Requirement WFWL_MGMT_1.17 Workflow and How does the solution address workload management in Workload conjunction with workflows such as but not limited to; Management  task view and display request (order info),  planning and scheduling, generate schedules (create, modify, delete – on demand (instant) daily, weekly, monthly),  resource management (internal, external) and task assignment,  resource, task and time tracking,  search available resources for a task,  search task and resource information,  real time input to schedule by resources,  workload automation,  integration with calendar applications (MS Outlook, Google Calendar),  track and notify assignment change or cancellation,  validate assignments (under and over allocation),  distribution of schedule,  access rights and permissions,  customizable notification (user, context, system, event)? Specify and describe the features and functionalities and how they would be used. WFWL_MGMT_1.18 Workflow and What type of features and functionalities does the solution Workload provide to manage interpreters (internal or external Management resources) such as but not limited to;  identifying last minute event requests and be able to create one time or recurring events,  automatically suggest resources, assign and select one or more resources to an event based on availability,  assign and track resource activities (translation, training, and other),  for any activity manual and automatic resource time calculations such as but not limited to; for hours worked, under worked, owing, training, travel time, interpretation. Page 52 of 59

4.36 Workflow and Workload Management (Translation and Interpretation) ID Category Requirement  display and view calendar of planned events and identify which ones are fully and not fully assigned,  generate, display and view calendar containing planned events and assignment information,  tag an incoming document from the client with an event, distribution of calendar (schedule) and related documentation via email to resources,  manually and automatically create notification for upcoming events, for assignments, date and time changes,  flag if resource is double-booked or assigned to a past event, track and store changes to an event or assignment (time and dates of changes, what was changed, who made the changes, history of the communications),  reports on many of the items listed above,  store client event related documents? Specify and describe. WFWL_MGMT_1.19 Workflow and How are requests (order) deadlines (Due Date) managed as Workload part of the workflow in the solution? Management Specify and describe in terms of but not limited to;  tracking and flagging request deadlines,  auto and manually generating deadlines,  modifying and updating, calculating the deadline based on task, subtask, product or service. WFWL_MGMT_1.20 Workflow and What type of features and functionalities does the solution Workload provide to manage (suppliers - freelancers (external Management resources) in addition to WFWL_MGMT_1.17, 1.18 but not limited to:  real-time monitoring of daily translation and interpretation capacity including number of words/hours remaining in the contract,  manual and automatic preparation and distribution of a translation kit to the freelancer comprised of documents to be translated, relevant extracts from the Corpus, document analysis report, and

Page 53 of 59

4.36 Workflow and Workload Management (Translation and Interpretation) ID Category Requirement reference documentation, internal resource supplier translation evaluation and feedback? Specify and describe.

4.37 Metadata ID Category Requirement MTDT_1.0 Metadata What type of metadata does the solution and suite of tools support and how is it used?

Describe the features and functionalities such as but not limited to;  metadata creation and customisation,  metadata access rights and permissions,  indexing,  search engine  specify the set of metadata attributes, or elements and schemas that are available.

4.38 Business Rule Management System ID Category Requirement BRMS_1.0 Business Rules Does the solution and suite of tools include an integrated Management or 3rd party business rules engine that can be used for but System not limited to workflow and workload management? Specify and describe. BRMS_1.1 Business Rules Does the solution and suite of tools support but not limited Management to production and reaction rules? Specify and describe the System features and functionalities of the BRE such as but not limited to;  the ability to create, modify, delete, customize,  apply access rights and permissions based on user roles,  allow collaboration,  automatic rule validation,  major browser support,  reusable rules,  built-in help,  rule repository,

Page 54 of 59

 rule editor,  reporting, and audit capabilities.

4.39 User Profile Management ID Category Requirement USR_PROF_MGMT_ User Profile What types of user profiles does your solution support such Management as but not limited to local, roaming, mandatory, and temporary? Specify and describe. USR_PROF_MGMT_ User Profile What are the solution's user profile management features Management and functionalities? Specify and describe in terms of but not limited to;  defining profiles (client, supplier-freelancer, internal resources),  administering (creating, modifying, deleting) profiles,  setting up the user access,  user profile types,  user profile attributes,  business rules,  roles,  specifying what a user can and cannot change,  specifying workflow,  environment and interface settings,  user tracking,  auditing, reporting, querying.

4.40 Other Questions ID Category Requirement VARIA_1.0 VARIA Is there any question we forgot to ask that you would like to provide information about?

Page 55 of 59

Annex A : Government of Canada Security Categories

There are two main security categories, based on a document’s content:

Classified • Top Secret extremely sensitive information related to international affairs, law enforcement investigations and intelligence matters (cause exceptionally grave injury)

• Secret trade talks, minutes and memos to cabinet, enterprise planning, departmental input to national budget, draft legislation(cause serious injury)

• Confidential international affairs, administrative plans, audits, negotiations between departments and partners (cause injury)

Classified refers to information that, if compromised, may cause injury to the national interest. This information could cause injury to the country.

Protected • Protected C information about police agents and other informants (cause life threatening and/or extremely grave injury)

• Protected B law enforcement and medical records, personnel evaluations and investigations, financial records, solicitor-client confidence (particularly sensitive, cause serious injury)

• Protected A home addresses, dates of birth, SIN numbers, other personal information (low-sensitivity, could cause injury)

Protected refers to information that is not related to the national interest, but if compromised, may cause injury to private or other non-national interests. This information could cause injury to an individual or to a company.

Page 56 of 59

Annex B : Acronyms

Acronym Definition AES Advanced Encryption Standard API Application Programming Interface BI Business Intelligence C&A Certification and Accreditation CAT Computer Aided Translation CD-ROM Compact Disk-Read Only Memory CIOB Chief Information Officer Branch CMS Content Management System COTS Commercial Off The Shelf CPU Central Processing Unit CSS Cascading Style Sheet CSV Comma Separated Value CRM Content Relationship Management DOC Document, or an ASCII text file with text formatting codes in with the text; used by many word processors ETL Extract Transfer and Load FTP File Transfer Protocol GCDOCS Government of Canada Documentation GoC Government of Canada GSSAPI Generic Security Service Application Program Interface GSSAPI-SPNEGO Generic Security Service Application Program Interface-Simple and Protected Negotiation Mechanism GUI Graphical User Interface HTML HyperText Markup Language HTTPS Hypertext Transfer Protocol Security IAAS Infrastructure as a Service ICQ Internet Chat Query ID Identification IE Internet Explorer IEC International Electrotechnical Commission IIS Internet Information Service IM Instant Messaging IPSec Internet Protocol Security ISO International Organization for Standardization IVR Interactive Voice Response L2TP Layer Two Tunneling Protocol LAN Local Area Network LDAP Lightweight Directory Access Protocol LISA QA Localization Industry Standards Association Quality Assurance MS Dynamics Microsoft Dynamics Page 57 of 59

Acronym Definition MS Office Microsoft Office MS Outlook Microsoft Outlook MS SQL Microsoft Structured Query Language OCCI Open Cloud Computing Interface OCR Optical Character Recognition OLAP Online Analytical Processing OS Operating System PAAS Platform as a Service PC Personal Computer PDF Portable Document Format PKI Entrust Public Key Infrastructure Entrust PPTP Point to Point Tunneling Protocol PSPC Public Services and Procurement Canada PWGSC Public Works and Government Services Canada QA Quality Assurance QIP Quiet Internet Pager RAM Random Access Memory REST Representational State Transfer RFC Request for Comment RFI Request for Information RFP Request for Proposal RPO Recovery Point Objective RSA Rivest Shamir and Adelman RTO Recovery Time Objective SAAS Software as a Service SAE J2450 Society of Automotive Engineers (J2450 Task Force on a Quality Metric for Language Translation of Service Information) SAP System Applications and Products SASL Simple Authentication Security Layer SIN Social Insurance Number SOA Special Operating Agency SOAP Simple Object Access Protocol SLA Service Level Agreement SSC Shared Services Canada SSL Secure Socket Layer SQL Structured Query Language SVG Scalable Vector Graphics TAUS DQF TAUS Dynamic Quality Framework TBX Termbase Exchange TCP Transmission Control Protocol TLS Transport Layer Security TM Translation Memory

Page 58 of 59

Acronym Definition TMS Translation Management System TMX Translation Memory Exchange Triple DES Triple Data Encryption Standard UDP User Datagram Protocol UTF Unicode Transformation Format VPN Virtual Private Network WAI Web Accessibility Initiative WAN Wide Area Network WCAG Web Content Accessibility Guidelines WS Web Service WYSIWYG What You See Is What You Get XLIFF XML Localisation Interchange File Format XLS Microsoft Excel Spreadsheet XLSX Office Open XML Workbook (Spreadsheets) XML Extensible Markup Language

Page 59 of 59