01

Introduction

The COVID-19 pandemic showed how quickly an infectious disease can disrupt daily life, businesses, and healthcare. For this project, I propose the Pandemic Early Warning System (PEWS), a Canadian surveillance network that could help public health officials recognize new outbreaks sooner. PEWS would start with a pilot in the Fraser Valley and then expand to participating regions across Canada. Its job is to collect information, look for unusual patterns, and send warnings. It would not make decisions about lockdowns, vaccinations, or other public health responses.

02

Proposed Solution and Scope

PEWS would combine wastewater monitoring, environmental measurements, laboratory results, and approved aggregated healthcare data in one custom-built software platform. Wastewater monitoring can help identify infectious disease activity at the population level and complement other public health surveillance methods (Public Health Agency of Canada, 2026). The system would check incoming data for unusual trends, display findings on secure dashboards, and notify authorized public health officials when a possible threat needs attention. Important alerts would be reviewed by qualified staff to reduce false alarms. Privacy, data quality, and security would be considered from the beginning.

The project includes software development, monitoring equipment, data connections, facilities, cybersecurity, training, testing, and handover. It does not include running hospitals, distributing vaccines, contact tracing, or directing government interventions. Limiting the scope to detection, analysis, and warning gives the project a clearer purpose and more realistic acceptance criteria.

03

Project Schedule and Milestones

The proposed project runs from January 2027 to December 2029. A detailed Gantt chart would track overlapping software, procurement, installation, and testing tasks. The main milestones are:

MilestoneTarget
Charter and project approvalMarch 31, 2027
Architecture, privacy requirements, and design approvalJune 30, 2027
Initial software platform ready for testingJune 30, 2028
Fraser Valley pilot evaluatedDecember 31, 2028
National deployment to participating regionsSeptember 30, 2029
Final acceptance and project closureDecember 31, 2029
PROJECT ROADMAP

PEWS Gantt chart · 2027–2029

36 months

Workstreams overlap as the software, equipment, and pilot are developed. Bars reflect the detailed project schedule workbook.

202720282029
WorkstreamQ1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4
Charter & requirements
Architecture & design
Facilities & procurement
Core software
Monitoring devices
Data integrations
Detection & alerts
Fraser Valley pilot
National rollout
Testing & security
Handover & closure
PlanningDevelopmentDeploymentValidation
Source: PEWS project Gantt workbook. Schedule bars represent planned activity windows; milestone dates in the table above are separate review targets.

Some tasks depend on others. For example, data-sharing agreements are needed before live data integration, and the pilot must show acceptable detection and alert performance before national expansion. Procurement delays or unsuccessful pilot tests could affect the critical path. The project manager would update the Gantt chart and report major schedule changes to the steering committee.

04

Project Charter, Management, and Communication

The project charter would authorize the $1 billion investment, name the project sponsor and manager, define the scope, and establish the December 2029 deadline. During preinitiation, the team would assess feasibility, identify possible partners, review existing surveillance programs, and develop initial cost and risk estimates. The project would then follow the main project-management process groups: initiating, planning, executing, monitoring and controlling, and closing.

The project manager would coordinate the schedule, budget, staffing, procurement, and reporting. A steering committee would approve major changes and review progress. Proposed stakeholders include the Canadian public, federal and provincial public health organizations, participating laboratories, Fraser Health, equipment suppliers, technical staff, and UFV. These are proposed relationships, not confirmed partnerships. A public health leader from a participating organization would be an appropriate project champion because they could explain the value of early warning and help secure cooperation.

Weekly team meetings would address technical work and blockers. Monthly progress reports would summarize completed milestones, budget versus actual spending, major risks, and decisions needed. The steering committee would receive quarterly reviews, while data-sharing partners would be contacted before changes affecting their systems. Sensitive information would only be shared with authorized users.

05

Procurement and Resources

PEWS would need a central facility, three regional hubs, monitoring devices, networking equipment, cloud services, and specialist staff. Major purchases would use competitive procurement with requirements for compatibility, reliability, cybersecurity, maintenance, and vendor support. Contracts would define deliverables, acceptance tests, warranties, and service levels. Equipment would be tested before acceptance, and suppliers would be evaluated for their ability to meet the deployment schedule.

The team would include developers, systems architects, cybersecurity specialists, data scientists, epidemiologists, infrastructure technicians, project managers, and support staff. Internal labour costs would be recorded under personnel, while external software contracts and tools would be recorded under software development to avoid double-counting.

06

Financial Plan

Costs

The proposed capital budget is CAD $1 billion. These amounts are planning estimates, not vendor quotations. More detailed research and procurement bids would be required before approval.

Budget categoryCAD millions
Facilities and regional hubs134
Software development150
Personnel196
Monitoring devices170
Cloud and data infrastructure110
Cybersecurity60
Data integration and research90
Training and deployment40
Contingency50
Total1,000

The $50 million contingency reserve would be used only for approved unexpected costs. After the project closes, the system would still need funding for equipment maintenance, staff, cloud services, and software updates.

Return on Investment

PEWS is not meant to earn sales revenue. Its possible return would come from reduced economic disruption if earlier warnings help public health officials respond more effectively. Canada’s real GDP fell about 5.2% in 2020 (Statistics Canada, 2021), illustrating how serious pandemic-related economic losses can be. However, PEWS cannot claim to prevent all or even most of those losses.

For an illustrative calculation, I use a $50 billion reference outbreak loss, assume 2% could be avoided through earlier action, and assume a 20% annual probability of an outbreak of comparable economic significance. Expected annual benefit = $50 billion × 2% × 20% = $200 million. After assumed operating costs of $50 million, annual net benefit would be $150 million. Over ten operating years, total gross benefits would be $2 billion and total costs would be $1.5 billion, including the initial investment. ROI = ($2 billion − $1.5 billion) ÷ $1.5 billion × 100 = 33.3%. The probability and avoided-loss percentages are hypothetical, not research-established forecasts.

Payback Analysis

Simple payback = $1 billion ÷ $150 million = approximately 6.67 years of operation. If the system starts full operation in January 2030 and the assumed benefits occur consistently, payback would fall in 2036. In reality, outbreaks and savings would be irregular. The calculation also ignores the time value of money. Before funding approval, PEWS would need a more detailed sensitivity analysis and discounted cash flow assessment.

COST ALLOCATION

Where the $1 billion goes

CAD
Planned project budget$1,000,000,000
Budget allocated100%
People$196M19.6%
Monitoring devices$170M17%
Software$150M15%
Facilities$134M13.4%
Cloud & data$110M11%
Integration$90M9%
Cybersecurity$60M6%
Contingency$50M5%
Training & rollout$40M4%
Source: PEWS $1 billion budget workbook. All amounts are illustrative estimates, not supplier quotes or approved expenditures.
07

Three Spheres of Systems Management

Schwalbe (2019) describes three connected areas that influence IT projects: business, organization, and technology. For PEWS, the business sphere asks whether the system provides enough public value to justify its cost and future operating expenses. The organizational sphere concerns staffing, responsibilities, communication, and agreements with public health organizations. The technology sphere covers monitoring devices, software, databases, detection algorithms, cloud infrastructure, and cybersecurity.

These areas depend on one another. A detection model could work technically but still be useless without permission to access reliable data. Similarly, a well-funded project could fail if its software gives unreliable warnings. The project manager needs to consider all three spheres when making decisions.

08

Four Frames of Organizations

Bolman and Deal (2017) describe four ways to look at organizations. The structural frame concerns roles, procedures, and reporting lines. PEWS would use a project sponsor, steering committee, project manager, and technical leads with clear responsibilities. The human resource frame focuses on people’s needs, training, and motivation; PEWS would need to retain skilled staff throughout development and operations.

The political frame recognizes that organizations have different interests and authority. Provinces, laboratories, and federal agencies may disagree about data access, funding, or responsibilities, so PEWS would need formal agreements and negotiation. The symbolic frame concerns shared values and organizational identity. PEWS would promote the message “Detect Early. Warn Quickly. Protect Communities,” emphasizing scientific honesty, privacy, and public trust. UFV could potentially contribute student research or internships if a partnership were approved.

09

Project Deliverables and Quality

The main deliverable is a working, custom-built surveillance platform supported by physical infrastructure and documentation. The planned deliverables are:

DeliverableWhat will be handed over
FacilitiesCentral operations facility and three regional hubs
SoftwareSecure data processing, detection models, dashboard, and alert system
Monitoring networkProposed 600 wastewater packages and 1,200 environmental stations
Data integrationApproved interfaces, data standards, and data-sharing documentation
Fraser Valley pilotTest results, user feedback, and corrected issues
Security and qualityPrivacy assessments, security tests, performance and accuracy reports
Operations packageUser training, manuals, maintenance plans, and handover documents

The equipment counts are preliminary targets, not confirmed requirements. Quality would be measured through functional tests, integration tests, model accuracy checks, user acceptance tests, and security assessments. Important acceptance criteria include working connections at contracted sites, successful delivery of validated alerts, acceptable false-positive and false-negative rates, and no unresolved critical security issues. Exact performance thresholds would be approved during planning.

Preventing defects is generally preferable to fixing them after deployment. PEWS would invest in code reviews, automated testing, sensor calibration, and security testing to reduce the cost of rework, failed equipment, or unreliable warnings. Final acceptance would require documented evidence that approved requirements were met.

10

Software Development Lifecycle: Spiral Model

I would use the Spiral Model for software development because PEWS is complex and its biggest technical risks need to be tested early. Boehm (1988) describes an iterative approach in which each cycle sets objectives, evaluates risks, develops and tests a solution, and reviews the results before the next cycle.

The first cycle would build a prototype that accepts simulated surveillance data. The second would add detection models, alerts, and early device integrations. The third would test the system in the Fraser Valley, and the fourth would improve the platform and support national rollout. Each cycle would check risks such as inaccurate alerts, poor data quality, and security problems. Facility construction and equipment procurement would follow more fixed milestones. This hybrid approach provides flexibility without losing track of the deadline or budget.

11

SWOT Analysis

StrengthsWeaknesses
Dedicated $1 billion budget; custom software; multiple data sources; continuous monitoringComplex integrations; high maintenance costs; dependence on outside data; need for extensive testing
OpportunitiesThreats
University and research partnerships; improved detection methods; broader surveillance capacityCyberattacks; privacy restrictions; funding changes; emerging pathogens; limited agency cooperation

The SWOT analysis suggests that a phased rollout is essential. Starting in the Fraser Valley would allow the team to test equipment, data-sharing arrangements, and detection performance before committing to wider deployment.

12

People Motivation Methodology

PEWS would rely on a mix of technical and scientific staff, so keeping employees motivated would matter as much as hiring them. Maslow’s hierarchy suggests that basic needs, security, belonging, recognition, and personal growth all affect motivation (Maslow, 1943). PEWS would address these through fair pay, reasonable workloads, teamwork, recognition, and professional development.

Herzberg’s theory separates factors that prevent dissatisfaction, such as pay and working conditions, from factors that encourage motivation, such as achievement and responsibility (Herzberg et al., 1959). McGregor’s Theory Y also supports giving skilled employees some independence and trust rather than managing every task closely (McGregor, 1960). In practice, PEWS would give teams ownership of components, offer training, recognize completed milestones, and collect anonymous staff feedback. Turnover, workload concerns, and survey results would help management identify problems early.

13

Top Ten Risks

The project manager would maintain a risk register and score risks by probability and impact. Risk owners would review major risks monthly, with critical issues reported to the steering committee. The initial top ten risks and responses are:

RiskResponse
CyberattackEncryption, restricted access, security testing, incident plan
False or missed warningsModel validation, multiple data sources, human review
Budget overrunCost tracking, change approval, contingency reserve
Integration failureCommon data standards, phased testing
Privacy noncomplianceLegal review, privacy assessments, data minimization
Equipment failureCalibration, preventive maintenance, replacement stock
Schedule delayCritical-path tracking, milestone reviews
Staff shortageEarly recruitment, training, retention plans
Agency nonparticipationEarly consultation and formal agreements
New pathogens outside model capabilityModular models, research, and ongoing validation

The biggest risks are inaccurate detection, cybersecurity problems, and failure to secure data-sharing agreements. They could affect the value of the entire project even if development stays within budget. The Spiral Model helps by making risk review part of each software cycle.

14

Closing Processes

By December 31, 2029, PEWS should have completed testing, documented its results, and transferred responsibility to a designated operating organization. The project manager would compare each deliverable with its approved acceptance criteria. Unresolved defects would be recorded, and critical issues would need to be fixed before sign-off.

Financial closure would involve reconciling actual spending against the $1 billion budget, paying outstanding invoices, and accounting for unused contingency. Procurement staff would confirm that suppliers met their contracts and transfer warranties, licences, and maintenance agreements. The operations team would receive software repositories, system documentation, equipment records, training, and support procedures.

Finally, the team would write a lessons-learned report covering budget accuracy, schedule changes, technical problems, stakeholder communication, and the effectiveness of the Spiral Model. The sponsor would formally close the project only after acceptance and handover. PEWS would then continue operating as a surveillance and warning service, not as a government response agency.

15

Conclusion

PEWS is an ambitious proposal, but it addresses a real problem: public health officials need reliable information as early as possible when infectious diseases begin to spread. The project combines custom software, monitoring equipment, and cooperation among organizations. Its success would depend on careful scope control, accurate detection, secure data sharing, and a realistic plan for ongoing operations. A Fraser Valley pilot followed by phased national expansion would give PEWS a way to test these assumptions before full deployment.

16

References

Boehm, B. W. (1988). A spiral model of software development and enhancement. Computer, 21(5), 61–72. https://doi.org/10.1109/2.59

Bolman, L. G., & Deal, T. E. (2017). Reframing organizations: Artistry, choice, and leadership (6th ed.). Jossey-Bass.

Herzberg, F., Mausner, B., & Snyderman, B. B. (1959). The motivation to work (2nd ed.). John Wiley & Sons.

Maslow, A. H. (1943). A theory of human motivation. Psychological Review, 50(4), 370–396. https://doi.org/10.1037/h0054346

McGregor, D. (1960). The human side of enterprise. McGraw-Hill.

Public Health Agency of Canada. (2026, August 20). Wastewater monitoring. Government of Canada.https://www.canada.ca/en/public-health/services/emergency-preparedness-response/wastewater-monitoring.html

Schwalbe, K. (2019). Information technology project management (9th ed.). Cengage Learning.

Statistics Canada. (2021, November 9). Provincial and territorial economic accounts, 2020. The Daily. https://www150.statcan.gc.ca/n1/daily-quotidien/211109/dq211109a-eng.pdf