ADM Mat Remote Working

Home

Remote Working

Return To Work

Mental Health

Protective Measures

Leadership

Resources

Remote Working

The Defence Team is facing new ways of working during the COVID-19 Pandemic. A variety of tools, resources, and information are available for civilian employees, managers, and members of the military. New processes, products, and guidelines are being established to help all members of the Defence Team connect with their colleagues during this challenging time.

General Information

• DND/CAF Security Guide for Teleworking during the COVID-19 Response
• Leveraging communication and collaboration tools during COVID-19
• Working from a Remote Office (Quick steps for setting up your temporary laptop workstation - leaving the Government of Canada website)
• Setting up a Temporary Laptop Workstation (Youtube - leaving the Government of Canada website)
• How to Make Working Remotely a Success – For Managers and Employees (LifeSpeak)
• The use of personal peripherals on DWAN equipment when teleworking
• The Defence Team guide for managing and working remotely
• T-DVPNI Connectivity FAQ (link accessible only on the National Defence network)
• Working remotely – Guidance and resources for the Defence Team members

Maximize Reuse

• Leverage and reuse existing solutions, components, and processes
  • The use of Open Source software can ensure that other Departments reuse components developed, and vice versa.
  • SaaS, PaaS and IaaS solutions can leverage sharing of configurations when no code is involved such as the GC Accelerators (AWS, Amazon)
  • Opening up Communication with other Departments to identify if they've already developed a solution can enable further reuse.
• Select enterprise and cluster solutions over department-specific solutions
  • Focus on solutions that enable sharing with other Departments, do not focus just on individual mandates.
  • Costs can be setup to be shared across multiple departments, agencies etc...
• Achieve simplification by minimizing duplication of components and adhering to relevant standards
  • Focus on Separation of Concern by the development of Microservices, and use and reuse of APIs.
  • Consume APIs from the Government of Canada API Store if it exists, if it does not add it to the API store.
  • Follow the Government of Canada Standards on APIs
• Inform the GC EARB about departmental investments and innovations
  • Communicate with the GC-EARB Team early and frequently, sharing innovations and lessons learned so we can assistance in broadcasting them to others.
• Share code publicly when appropriate, and when not, share within the Government of Canada
  • Code should be shared in Public Repositories as described here.
  • When not able to, instead Code should be shared on GCCode.

Enable Interoperability

• Expose all functionality as services
  • Do not hide services under assumptions that someone would not find value in a service - often innovation can be bred from exposed services beyond it's original plan.
  • Follow the 'eat your own dogfood' mantra - in that all functionality should be a service that you consume.
• Use microservices built around business capabilities. Scope each service to a single purpose
  • Focus on smallest unit of purpose, and developing a single function.
• Run each IT service in its own process and have it communicate with other services through a well-defined interface, such as a HTTPS-based application programming interface (API)à
  • Ensure that services are accessible via common methodologies, and follow the Government of Canada Standards on APIs
• Run applications in containers
  • Ensure containers contain a single application, and build the smallest image possible.
  • Ensure containers are properly versioned and tagged.
• Leverage the GC Digital Exchange Platform for components such as the API Store, Messaging, and the GC Service Bus
  • Ensure APIs are discoverable on the API Store.