Hiring.Camp

Computer Application Support

Turtle Island Staffing

·

Yesterday

Location
CA
Type
Contract
Department
Customer Service
Source
PCRecruiter

Description

CONFIRM WHITE POSITION (developer, data analyst or Quality Assurance)

Please review the requirements and update your resume accordingly, clearly addressing all mandatory requirements . Make sure your resume explicitly demonstrates the relevant experience, responsibilities, and duration of experience required for each criterion.

R1 - Developer:

  • Scope of work

Canada requires temporary senior application support and development services for THE ARMY RECORDS CENTER, with emphasis on secure application logic, Protected B access-control analysis, and Power Platform development. The resource will support analysis of current ARMY RECORDS CENTER security and permissions behaviour, assist with implementation activities authorised by Canada, test configured access-control behaviour, and record application-support notes required to assist sustainment by Canada.

Tasks
The Contractor’s resource will perform tasks in support of THE ARMY RECORDS CENTER. These tasks may include, but are not limited to, the following:

  • Analyse the current ARMY RECORDS CENTER access-control model, including SharePoint Online permissions, lists, libraries, site collections, Azure/Entra security groups, Power Apps logic, Power Automate flows, and related D365 dependencies. Note – The Contractor’s resource must not make tenant-level configuration changes or security-policy decisions unless explicitly authorised through the appropriate DND authority. The resource may support analysis, testing, configuration within approved application scope, and technical observations for consideration by Canada.

  • Identify gaps, risks, or weaknesses in the current Protected B access-control logic, including unnecessary access, permission inheritance issues, group-based access issues, service-account risks, or logic that does not support need-to-know access.

  • Design and recommend an enduring Protected B access-control approach for THE ARMY RECORDS CENTER that supports authorised access, least privilege, operational sustainment, and future release to CA HQ and Level 2 organisations.

  • Develop, configure, and enhance THE ARMY RECORDS CENTER Power Apps, Power Automate flows, SharePoint Online lists, libraries, metadata, views, and permissions required to implement the approved access-control approach.

  • Test THE ARMY RECORDS CENTER Protected B access-control behaviour to confirm that users can access only the records, repositories, functions, or views they are authorised to access.

  • Troubleshoot THE ARMY RECORDS CENTER issues related to permissions, security groups, service accounts, workflow execution, connector behaviour, declaration logic, search, metadata, or user access.

  • Support THE ARMY RECORDS CENTER release preparation by resolving priority defects, validating fixes, preparing configuration notes, and recording technical decisions required for sustainment.

  • Assist with secondary ARMY RECORDS CENTER development work where capacity permits, including bilingual application behaviour, declaration workflow improvements, Correspondence Tracker integration, or other ARMY RECORDS CENTER features authorised by Canada.

  • Provide technical observations and recommendations to the Technical Authority concerning THE ARMY RECORDS CENTER risks, implementation options, dependencies, and sustainment considerations.

R2 - Data Analyst:

  1. Scope

This section succinctly summarizes the entire SOW via the following sub-sections:

Canada requires temporary senior computer application support services for THE ARMY RECORDS CENTER, with emphasis on database analysis, reporting, application usage monitoring, metadata management, search analytics, data quality review, and application sustainment activities.

The resource will support THE ARMY RECORDS CENTER by examining available application, list, metadata, search, feedback, and usage information; assisting with the organisation and interpretation of application-support data; supporting reporting and dashboard-related activities; reviewing metadata usage and data quality; and providing technical observations to Canada concerning application performance, metadata capture, search behaviour, user adoption, and sustainment considerations.

Tasks
The Contractor’s resource will perform tasks in support of THE ARMY RECORDS CENTER. These tasks may include, but are not limited to, the following:

  • Analyse the Army Records Center (ARC) database, list, library, metadata, and app-generated information structures within SharePoint Online, Power Apps, Power Automate, and related D365 services.

  • Assist with the organisation, review, and interpretation of THE ARMY RECORDS CENTER application data, including records declaration data, validation status, application usage data, search-related data, user feedback, and related application-support information.

  • Support the review of THE ARMY RECORDS CENTER metadata fields used for declaration, search, filtering, reporting, validation, records management, lifecycle management, and user experience.

  • Assist with identifying metadata gaps, inconsistencies, duplicated values, missing values, field-use issues, data quality issues, or reporting limitations affecting THE ARMY RECORDS CENTER searchability, discoverability, governance, lifecycle management, or business decision-making.

  • Support application monitoring activities, including usage trends, active-user indicators, declaration volumes, validation trends, search behaviour, frequently used search terms, user feedback trends, and other indicators authorised by Canada.

  • Support reporting and dashboard-related activities using Power BI, SharePoint list reporting, Excel-based analysis, Microsoft 365 reporting sources, or other authorised reporting tools and methods.

  • Assist with testing, validation, troubleshooting, and refinement of reporting, filtering, search, metadata, dashboard input, application monitoring, and related application-support functions across THE ARMY RECORDS CENTER Development, UAT, and Production environments, as authorised by Canada.

  • Provide technical observations to Canada concerning THE ARMY RECORDS CENTER database structure, metadata usage, reporting gaps, application metrics, search analytics, data quality risks, and sustainment considerations.

  • Work within approved DND/D365 environments and authorised tools only, and handle all information in accordance with applicable security, privacy, information management, and records-management requirements.

R3 - Quality Assurance:

Scope of work

Canada requires temporary computer application support services for the Army Records Center, with emphasis on quality assurance, test execution, defect validation, user acceptance testing support, Protected B access-control testing, and release readiness support.

The resource will support the Army Records Center by reviewing application behaviours, preparing and executing test scenarios, validating user flows, recording issues, retesting fixes, supporting user acceptance testing, and providing testing observations to Canada concerning functionality, access behaviour, workflow performance, usability, metadata, search, records declaration, and release readiness.

Tasks
The Contractor’s resource will perform tasks in support of ARC. These tasks may include, but are not limited to, the following:

  • Review Army Records Center business rules, user flows, known issues, test scenarios, and release priorities to support quality assurance activities

  • Prepare and execute test cases for Army Records Center functions, including records declaration, search, linking, viewing, metadata, navigation, and user-facing application behaviour.

  • Test Power Apps screens, Power Automate flows, SharePoint Online lists, libraries, views, metadata, and permissions-related behaviours used by the Army Records Center.

  • Validate Army Records Center Protected B access-control behaviour to confirm that users can access only authorised records, repositories, views, functions, or content.

  • Record, classify, and track defects, issues, failed test cases, user acceptance testing findings, and retest results.

  • Retest fixes provided by the development team and confirm whether identified issues have been resolved.

  • Support user acceptance testing activities by preparing test scenarios, recording findings, consolidating feedback, and identifying recurring issues.

  • Identify usability, workflow, access, metadata, search, declaration, or functional issues that may affect Army Records Center release readiness.

  • Provide testing observations and issue summaries to the Technical Authority to support Army Records Center release and sustainment activities.


R1 - Developer

Number

\Additional mandatory criteria

M1

The Bidder must demonstrate that the proposed resource has a minimum of three (3) years of experience within the last five (5) years developing, configuring, testing, troubleshooting, or supporting application solutions using Power Apps, Power Automate, and SharePoint Online lists or libraries.

The experience must include hands-on configuration or development of application functions, workflows, or SharePoint Online information structures.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

M2

The Bidder must demonstrate a minimum of two (2) years of experience within the last four (4) years analysing, designing, configuring, implementing, testing, or troubleshooting access-control models for Microsoft 365, SharePoint Online, Power Platform, or comparable enterprise application environments.

The experience must include permissions, role-based access, security groups, Microsoft Entra ID or Azure security groups, restricted repositories, least-privilege access, protected information, or need-to-know access.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

M3

The Bidder must demonstrate that the proposed resource has, within the last four (4) years, supported or troubleshot Power Automate workflows involving service accounts, connection ownership, connection references, connector behaviour, workflow permissions, auditability, or operational sustainment.

The Bidder must provide at least one (1) project example demonstrating how the proposed resource identified, analysed, or resolved an issue involving authentication, connection ownership, permissions, connector behaviour, or workflow continuity.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

M4

The Bidder must demonstrate a minimum of one (1) year of experience within the last four (4) years supporting Microsoft 365, SharePoint Online, Power Platform, or comparable application solutions in a protected, regulated, privacy-sensitive, or restricted-access enterprise environment.

The experience must include applying or supporting access controls designed to limit information or application access to authorised users.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

R2 - Data Analyst

Number

Additional mandatory criteria

M1

The Bidder must demonstrate that the proposed resource has a minimum of two (2) years of experience within the last four (4) years using Microsoft 365, SharePoint Online, Power Platform, Power BI, Excel, or comparable tools to support reporting, dashboards, application monitoring, data extraction, or analysis for enterprise applications.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

M2

The Bidder must demonstrate that the proposed resource has a minimum of two (2) years of experience within the last four (4) years supporting reporting, dashboarding, business intelligence, database analysis, application usage analysis, or data quality review for enterprise applications.

The experience must include interpreting application data and identifying findings, trends, gaps, inconsistencies, or reporting requirements.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

M3

The Bidder must demonstrate a minimum of one (1) year of experience within the last four (4) years analysing or supporting metadata, data quality, taxonomy, records-management metadata, or information-management data structures.

The experience must include identifying missing, inconsistent, duplicated, incorrectly structured, or insufficiently used metadata or data values.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

M4

The Bidder must demonstrate a minimum of one (1) year of experience within the last four (4) years analysing or supporting search, filtering, information retrieval, application monitoring, user feedback, or usage trends for an enterprise application.

The experience must include using available information to identify application behaviour, user needs, search or retrieval issues, adoption patterns, or opportunities for improvement.

For each relevant project, provide the client and project description; timeframe by month/year; the resource’s role and responsibilities; detailed examples demonstrating the required experience; and reference name, telephone number and email address.

R3 - Quality Assurance

Number

Additional mandatory criteria

M1

The Bidder must demonstrate that the proposed resource has a minimum of two (2) years of experience within the last four (4) years performing quality assurance testing, user acceptance testing support, defect validation, or release testing for Power Apps, Power Automate, SharePoint Online, Microsoft 365, or comparable enterprise application solutions.

The Bidder must identify each relevant project and provide:

• client organisation and project description;

• timeframe, from-to, by month/year;

• the resource’s role and responsibilities;

• detailed examples demonstrating the required experience; and

• reference name, telephone number and email address.

M2

The Bidder must demonstrate that the proposed resource has a minimum of one (1) year of experience within the last four (4) years testing application functions that use SharePoint Online lists, libraries, metadata, views, forms, search, or document workflows.

The experience must include validating expected system behaviour, identifying issues, and confirming test results.

The Bidder must identify each relevant project and provide:

• client organisation and project description;

• timeframe, from-to, by month/year;

• the resource’s role and responsibilities;

• detailed examples demonstrating the required experience; and

• reference name, telephone number and email address.

M3

The Bidder must demonstrate that the proposed resource has a minimum of one (1) year of experience within the last four (4) years testing permissions, role-based access, restricted repositories, security groups, protected information access, or need-to-know access behaviour.

The experience must include confirming that users could access only the information, repositories, views, or application functions for which they were authorised.

The Bidder must identify each relevant project and provide:

• client organisation and project description;

• timeframe, from-to, by month/year;

• the resource’s role and responsibilities;

• detailed examples demonstrating the required experience; and

• reference name, telephone number and email address.

M4

The Bidder must demonstrate that the proposed resource has a minimum of two (2) years of experience within the last four (4) years recording, classifying, tracking, retesting, and validating defects or issues during application testing, user acceptance testing, or release support activities.

The Bidder must identify each relevant project and provide:

• client organisation and project description;

• timeframe, from-to, by month/year;

• the resource’s role and responsibilities;

• detailed examples demonstrating the required experience; and

• reference name, telephone number and email address.

M5

The Bidder must demonstrate that the proposed resource has a minimum of one (1) year of experience within the last four (4) years performing quality assurance or user acceptance testing in a public-sector, protected, regulated, privacy-sensitive, or restricted-access enterprise environment.

The Bidder must identify each relevant project and provide:

• client organisation and project description;

• timeframe, from-to, by month/year;

• the resource’s role and responsibilities;

• detailed examples demonstrating the required experience; and

• reference name, telephone number and email address.

M6

The Bidder must demonstrate experience within the last four (4) years independently reviewing application requirements or user workflows, identifying test scenarios, executing tests, and reporting findings without relying solely on pre-existing test scripts or detailed task-by-task direction.

The Bidder must provide at least one project example demonstrating how the proposed resource identified testing requirements or application issues beyond following pre-existing test scripts.

The Bidder must identify each relevant project and provide:

• client organisation and project description;

• timeframe, from-to, by month/year;

• the resource’s role and responsibilities;

• detailed examples demonstrating the required experience; and

• reference name, telephone number and email address.

Skills

AzureExcelPower BI