# AI workability — Virtual Software Applications Environment

*Buyer: Dalhousie University · Source: canadabuys · Closes: 02 Sep 2026 00:00 UTC*

**AI workability: 60%** (majority AI-deliverable) · notice-only read · bid call: **MAYBE**

- Effort: 700 h total · 423 h AI · 277 h human (low confidence)

## Verdict

AI agents can perform the majority of the software engineering, configuration, documentation, and testing work, but human effort is required for procurement, stakeholder workshops, security review, and acceptance.

## Bid call

**MAYBE** — AI workability is high and the project fits a small AI-first shop, but the solicitation is too thin to confirm compliance, evaluation, and security requirements. Proceed only after clarification and a go/no-go check on mandatory terms.

## Deliverables

| Deliverable | Mode | AI share | Hours |
| --- | --- | --- | --- |
| Requirements discovery and solution architecture | ai_assisted | 50% | 60 |
| Virtual lab platform implementation | ai_assisted | 75% | 200 |
| User access and device compatibility layer | ai_assisted | 70% | 120 |
| Automated testing and QA | ai_assisted | 65% | 80 |
| Documentation and training materials | ai_agent | 85% | 60 |
| DevOps, monitoring, and handover | ai_assisted | 70% | 80 |
| Procurement, legal, and contract compliance | human_only | 0% | 20 |
| Stakeholder workshops and project management | human_only | 0% | 80 |

## Risks

- **[medium]** Vlab usage is below expectations; raising awareness is important if it is to remain available. — *Include adoption/communication plan and training materials in proposal.*
- **[medium]** Most surveyed students are either unaware of Vlab or choose not to use it. — *Design UX with student input and provide easy onboarding.*
- **[high]** Performance varies based on the user's device and internet quality. — *Use adaptive bitrate/HTML5 client and scalable cloud resources.*
- **[high]** Thin solicitation documents may hide mandatory requirements. — *Submit clarification questions before closing; keep solution flexible.*
- **[medium]** No evaluation criteria or pricing model published. — *Price competitively and structure bid to be compliant with standard university terms.*
- **[medium]** Integration with university identity/network may require on-site or security-cleared work. — *Confirm remote access and security requirements early; partner if needed.*

## Human roles

- **Contract signatory / legal accountability** (7%): Contract signature, insurance, and legal/financial accountability cannot be delegated to AI.
- **Stakeholder workshops and requirements facilitation** (21%): Client workshops and stakeholder facilitation need a person to build trust and interpret needs.
- **Solution architecture decisions and approvals** (14%): Final architecture choices and production approvals require human judgment and accountability.
- **Security and integration review** (18%): University security, identity, and network integration require human review and sign-off.
- **User acceptance testing** (14%): Students and faculty must validate the environment in real usage scenarios.
- **Project management and relationship management** (18%): Ongoing communication, status reporting, and relationship management need a human owner.
- **Production cutover and change management** (8%): Deploying to production and managing institutional change requires human coordination.

## Why not more AI

- AI cannot sign contracts or take legal/financial accountability.
- AI cannot facilitate in-person workshops or build trust with faculty and students.
- AI cannot perform physical installation or cabling if required.
- AI cannot obtain security clearances or professional certifications.
- AI needs human oversight for production access, security compliance, and final acceptance.
- AI cannot interpret vague procurement requirements without human clarification.

## Requirements & compliance

| Ref | Requirement | Status |
| --- | --- | --- |
| Description | Solution must be easy to use. | met |
| Description | Solution must have the features that students and faculty need. | unclear |
| Description | Solution must provide the ability to access the lab environment from anywhere and from any device regardless of device specs. | met |

## Evaluation criteria

- **Not specified in available documents** (N/A): No evaluation criteria were published; proposal should still address usability, features, and anywhere/any-device access.

## Key dates

- 2026-08-12 — Published
- 2026-09-02T13:00:00-04:00 — Closing
- 2026-08-13 — Date modified

## Gaps in source documents

- No detailed technical specification or RFP attachments.
- No evaluation criteria or weighting.
- No pricing model or budget.
- No existing Vlab architecture details.
- No integration or security requirements.
- No service level agreement or support expectations.
- No information on licensing/resale requirements.
- No clarification whether this is custom development, COTS deployment, or managed service.

## Assumptions

- Project is primarily a cloud-hosted virtual lab environment, not physical hardware.
- Buyer will provide access to existing identity management and network.
- No security clearance is required unless specified later.
- AI agents can operate in a sandboxed dev environment and produce code/config.
- Human effort includes procurement, workshops, security review, UAT, and project management.
- 60-month contract implies ongoing support; support can be AI-assisted but human on-call is required.

---

*Generated by GovContract from public tender documents. Human review required before acting on bid decisions.*