Category

Tasks for Contractor

HPC administrator tasks

- Maintain a HPC cluster (hardware, image management, local networking, scheduler, backups).

- Troubleshoot the environment when an incident occurs to ensure a quick return to normal operations.

HPC Analyst Tasks

- Meet with scientists and evaluate their requirements for HPC support.

- Develop a task plan to meet scientists' needs and consult the technical authority for approval.

- Application builds and installs, runtime troubleshooting (GNU, Intel, Fortran, Nvidia).

- Support for open-source and commercial off-the-shelf (COTS) software, including: o Python and Anaconda installs.

o Bash scripts, build/make tools, EasyBuild, and Spack.

o MPI implementations (MPICH, OpenMPI, IntelMPI, HPMPI).

- Assist with in-house developed applications (compilation and runtime).

Other General Tasks

Management of:

- Operating system (patching schedule, reliability for Linux distributions).

- Accounts (creation, deletion).

- Configuration via Git, MS DevOps, Ansible Playbooks.

- RPM/DEB Packages.

- Environment modules.

- ThinLinc troubleshooting.

Troubleshoot & Hardware

- Troubleshooting jobs on schedulers (PBS Pro/Torque, SLURM, SGE).

- Ensure reliable CUDA installs, troubleshoot GPU failures and other CUDA software/driver issues.

- Hardware support (memory upgrades, storage arrays, power and network cabling, ILO).

Documentation

- Document each process for every task to ensure enterprise knowledge continuity.

M1

High Performance Computing Experience

The bidder must demonstrate that the proposed resource has five (5) years’ experiences within the last ten (10) years in administrating HPC (High Performance Computing) systems and performing HPC analyst tasks, as per Statement of Work Section 3.1 Tasks – HPC Administrator Tasks.

The bidder must demonstrate via project description and must provide the following for each project:

• Organization for which the work was performed;
• Name of the Project(s) and/or Reference number;
• Duration of work (start and end dates in MM/YY format);
• Roles and responsibilities;
• Tasks performed demonstrating the relevant experience;

To substantiate this experience, the Bidder must provide the following details for each relevant project:

1) A Short Project Description with scope, tasks, and deliverables

2) Organization for which the work was performed;

3) Contract number, Reference number or Project Title;

4) Duration of Work (start and end dates in MM/YY format)

5) Roles, responsibilities and detailed tasks of the proposed resource(s) demonstrating the relevant experience

6) Project experience must have been completed or ongoing;

7) Project Authority/Technical Authority name and title from the Organization which the work was performed;

8) Contact information (email address and phone number) for Project Authority/Technical Authority from the Organization which the work was performed;

a) Can be omitted when there is a specific criterion for references only

M2

References

The Bidder must provide reference(s) for two (2) distinct HPC system administration projects or HPC analyst projects on which the proposed resource has worked for more than twelve (12) months. Each reference provided must have been in a role of supervision of the proposed resource.

The bidder must demonstrate via project description and must provide the following for each project:

1) A Short Project Description with scope, tasks, and deliverables

2) Organization for which the work was performed;

3) Contract number, Reference number or Project Title;

4) Duration of Work (start and end dates in MM/YY format)

5) Roles, responsibilities and detailed tasks of the proposed resource(s) demonstrating the relevant experience

6) Project experience must have been completed or ongoing;

7) Project Authority/Technical Authority name and title from the Organization which the work was performed;

8) Contact information (email address and phone number) for Project Authority/Technical Authority from the Organization which the work was performed;

a) Can be omitted when there is a specific criterion for references only

M3

Security

At contract award, the Bidder must demonstrate that the organization holds a valid Designated Organization Security (DOS) clearance and that all proposed resource(s) have Secret Security Clearance status at the time of contract award. Documentation must be provided.

Other

Client References

R2

Experience with HPC Cluster Administration

The Bidder should demonstrate that the proposed resource has a minimum of five (5) years of experience performing HPC cluster administration and analyst functions, as described in the tasks listed in Section 3.1 "Tasks" of Statement of Work, within the last fifteen (15) years.

The bidder must demonstrate via project description and must provide the following for each project:

1) A Short Project Description with scope, tasks, and deliverables

2) Organization for which the work was performed;

3) Contract number, Reference number or Project Title;

4) Duration of Work (start and end dates in MM/YY format)

5) Roles, responsibilities and detailed tasks of the proposed resource(s) demonstrating the relevant experience

6) Project experience must have been completed or ongoing;

7) Project Authority/Technical Authority name and title from the Organization which the work was performed;

8) Contact information (email address and phone number) for Project Authority/Technical Authority from the Organization which the work was performed;

a) Can be omitted when there is a specific criterion for references only

R3

The Bidder should demonstrate the proposed resource’s experience in HPC administration within a research environment, including direct interaction with scientists or research officers, within the last ten (10) years.

Definition of Research Environment:

A research environment refers to the physical, digital, and organizational setting in which scientific research activities are conducted.

With respect to Information Technology, it encompasses the infrastructure, platforms, resources, policies, governance frameworks, and networking that enable and support the creation, sharing, and application of knowledge.

Experience in a research environment may include, but is not limited to, work performed for organizations engaged in fundamental and/or applied scientific, technological, or academic, where IT strategies and roadmaps are developed to support research operations, data management, or innovation initiatives.

The bidder must demonstrate via project description and must provide the following for each project:

1) A Short Project Description with scope, tasks, and deliverables

2) Organization for which the work was performed;

3) Contract number, Reference number or Project Title;

4) Duration of Work (start and end dates in MM/YY format)

5) Roles, responsibilities and detailed tasks of the proposed resource(s) demonstrating the relevant experience

6) Project experience must have been completed or ongoing;

7) Project Authority/Technical Authority name and title from the Organization which the work was performed;

8) Contact information (email address and phone number) for Project Authority/Technical Authority from the Organization which the work was performed;

a) Can be omitted when there is a specific criterion for references only

9) Research Environment

Description on how specific technologies were used and applied in the project experience.

R4

The Bidder should demonstrate the proposed resource’s experience in HPC system administration and/or analyst functions, within the last ten (10) years for a Public Sector Organization.

“Public Sector Organizations” includes, but is not limited to:

• Federal government department or agency
• Federal Crown corporation
• Provincial or territorial government department or agency
• Provincial Crown corporation
• Municipal or regional government
• Public university or college
• Public health authority or hospital
• Indigenous governing body (band council, tribal council, self-governing nation)
• Port or airport authority

The bidder must demonstrate via project description and must provide the following for each project:

1) A Short Project Description with scope, tasks, and deliverables

2) Organization for which the work was performed;

3) Contract number, Reference number or Project Title;

4) Duration of Work (start and end dates in MM/YY format)

5) Roles, responsibilities and detailed tasks of the proposed resource(s) demonstrating the relevant experience

6) Project experience must have been completed or ongoing;

7) Project Authority/Technical Authority name and title from the Organization which the work was performed;

8) Contact information (email address and phone number) for Project Authority/Technical Authority from the Organization which the work was performed;

a) Can be omitted when there is a specific criterion for references only

R5

The bidder should demonstrate that the resource has experience working with technologies listed in 3.2 “Technologies Associated with Tasks” Statement of Work.

Technologies

· Compilers and interpreters (e.g. GNU GCC, Intel oneAPI, Python)

· Anaconda

· Bash scripts

· Build/make tools (e.g: GNU Make Tools)

· EasyBuild

· Spack

· MPI implementations (MPICH, OpenMPI, IntelMPI, HPMPI)

· Git

· MS DevOps

· Ansible Playbooks

· RPM/DEB packages

· Environment modules

· ThinLinc

· PBS Pro/Torque

· SLURM

· SGE

· CUDA

The bidder must demonstrate via project description and must provide the following for each project:

1) A Short Project Description with scope, tasks, and deliverables

2) Organization for which the work was performed;

3) Contract number, Reference number or Project Title;

4) Duration of Work (start and end dates in MM/YY format)

5) Roles, responsibilities and detailed tasks of the proposed resource(s) demonstrating the relevant experience

6) Project experience must have been completed or ongoing;

7) Project Authority/Technical Authority name and title from the Organization which the work was performed;

8) Contact information (email address and phone number) for Project Authority/Technical Authority from the Organization which the work was performed;

a) Can be omitted when there is a specific criterion for references only

Description on how specific technologies were used and applied in the project experience.