Language Translation
  Close Menu

IOT Application Development Success Stories

The IOT Application Development Team is proud to highlight the successes we've achieved in collaboration with our partner agencies through the Application Development program. The success stories reflect our commitment to designing, building, supporting, and securing scalable, citizen-focused solutions that empower Indiana's state agencies to deliver efficient, transparent, and innovative public services. Below, you'll find a collections of our shared accomplishments.

DNR Wildlife Health

The DNR Wildlife Health system is a comprehensive web-based application designed to manage wildlife health cases, laboratory testing, animal tracking, and disease surveillance for the Department of Natural Resources (DNR). The system enables wildlife health professionals to document sick or deceased animal cases, track laboratory test results, manage banked biological samples, coordinate with interested parties, and monitor disease patterns across wildlife populations.

Business Value

  • Centralized Case Management: Consolidates all wildlife health case data in a single system, eliminating fragmented spreadsheets and paper records
  • Disease Surveillance: Enables early detection of disease outbreaks and trends through comprehensive data analysis and reporting
  • Laboratory Coordination: Streamlines communication between field staff and laboratories, tracking samples from collection through final results
  • Public Engagement: Provides a public portal for citizens to report sick animals, facilitating rapid response to potential disease events
  • Regulatory Compliance: Maintains detailed records for regulatory reporting and scientific research requirements
  • Improved Decision Making: Provides wildlife managers with timely, accurate data for population management decisions

CoE Use Case Overview

The DNR Wildlife Health system underwent a significant modernization initiative, marked by a complete architectural transformation during its migration from Azure DevOps (ADO) to GitHub Enterprise Cloud (GHEC). This transition was not merely a change in source control or CI/CD tooling—it represented a paradigm shift in how the system is designed, deployed, and maintained.

Previously, the system operated on a traditional on-premises, multi-tier architecture, which relied heavily on static infrastructure, manual deployments, and tightly coupled components. This model, while functional, posed challenges in scalability, maintainability, and compliance with modern security standards.

With the migration to GHEC, the system embraced a cloud-native, container-first architecture, leveraging modern DevSecOps practices and infrastructure-as-code principles. This transformation enabled:

  • Microservices-based design for modularity and scalability
  • Containerization for portability and consistency across environments
  • Automated CI/CD pipelines for faster, more reliable deployments
  • Improved observability and monitoring for proactive system health management

A critical enabler of this transformation was the adoption of paved paths within the Indiana Internal Development Platform (IDP). These paved paths are pre-approved, secure-by-default development and deployment patterns that align with state IT policies, including Executive Order 25-19 and NIST 800-53 Rev. 5 compliance.

By leveraging the IDP’s paved paths, the development team was able to:

  • Accelerate development by using preconfigured environments and reusable components
  • Ensure security and compliance through built-in controls, automated scans, and policy enforcement
  • Reduce operational overhead by standardizing infrastructure and deployment practices
  • Promote consistency across teams and projects, making onboarding and maintenance more efficient

The IDP also provided seamless integration with GHEC, enabling secure code management, automated testing, and deployment pipelines—all within a governed, enterprise-grade platform.

Detailed Legacy vs CoE Comparison

Backend Technology

Component

Legacy Version

CoE Version

Status

Notes

Authentication

Planned Azure AD

✅ Implemented AccessIN

🚀 Improved

Production ready

Containerization

Not mentioned

✅ Docker multi-stage builds

🚀 New

Modern deployment

Health Checks

Not implemented

✅ Built-in health monitoring

🚀 New

Production monitoring

API Versioning

No strategy

✅ URL path versioning

🚀 New

Better API management

Rate Limiting

Not addressed

✅ 1000 req/hour

🚀 New

Production security


Frontend Technology

Component

Legacy Version

CoE Version

Status

Notes

Hosting

Azure Static Web Apps (planned)

✅ Azure Static Web Apps

🚀 Improved

Implemented

Build Process

Standard Angular build

✅ Optimized with CDN

🚀 Improved

Better performance


Infrastructure & DevOps

Component

Legacy Version

CoE Version

Status

Notes

Development Environment

Local setup

✅ Docker-first

🚀 Improved

Consistent environments

CI/CD Pipeline

Basic planning

✅ Automated deployment

🚀 Improved

Production ready

Deployment Strategy

7-8 week migration plan

✅ Blue-green deployment

🚀 Improved

Automated & reliable

Monitoring

Planned Application Insights

✅ Azure Monitor + App Insights

🚀 Improved

Implemented

Logging

Elasticsearch (external)

✅ Azure Monitor integration

🚀 Improved

Cloud-native

Technical Features

Feature

Legacy Status

CoE Status

Implementation Gap

Technical Impact

Authentication

🔄 Planned

✅ Implemented

Major improvement

High - Security foundation

API Documentation

📝 Extensive specs

✅ Operational guide

Approach change

Medium - Developer experience

Containerization

❌ Not planned

✅ Production ready

New capability

High - Deployment reliability

Health Monitoring

🔄 Planned

✅ Implemented

Major improvement

High - Operational visibility

Automated Deployment

🔄 Basic planning

✅ Full automation

Major improvement

High - Release reliability

Security Framework

🔄 Planned

✅ Comprehensive

Major improvement

Critical - Production security


Authentication & Authorization

Security Aspect

Legacy Version

CoE Version

Security Level

Authentication Method

Planned Azure AD

✅ JWT + Azure AD

🔒 Production Ready

Authorization Model

Role-based (planned)

✅ Role + Permission based

🔒 Enhanced

Token Management

Not specified

✅ Bearer token implementation

🔒 Secure

Session Management

Not addressed

✅ Stateless JWT

🔒 Scalable

Password Policy

Not specified

✅ Azure AD policies

🔒 Enterprise Grade


Infrastructure Security

Security Component

Legacy Version

CoE Version

Security Maturity

Secret Management

Planned Azure Key Vault

✅ Azure Key Vault implemented

🔒 Production

Network Security

Planned WAF

✅ Web Application Firewall

🔒 Production

Data Encryption

Planned

✅ TLS + database encryption

🔒 Production

Container Security

Not applicable

✅ Security scanning + non-root user

🔒 Modern

API Security

Basic planning

✅ Rate limiting + validation

🔒 Production


Architecture Scalability

Scalability Factor

Legacy Approach

CoE Approach

Scalability Rating

Deployment Model

Traditional multi-tier

Container-based microservices

🚀 GitHub Superior

Database Scaling

Single Azure SQL

Azure SQL with read replicas

🚀 GitHub Superior

Caching Strategy

Planned Redis

Azure Cache for Redis

🚀 GitHub Superior

Load Balancing

Planned Application Gateway

Implemented with health checks

🚀 GitHub Superior

Auto-scaling

Not addressed

Container Apps auto-scaling

🚀 GitHub Superior


Development Velocity

Development Aspect

Legacy Impact

CoE Impact

Velocity Improvement

Environment Setup

2-3 days manual setup

2-3 hours with Docker

🚀 90% faster

Deployment Speed

Manual, error-prone

Automated, reliable

🚀 80% improvement

Documentation Maintenance

High overhead

Streamlined

🚀 60% reduction

Testing Environment

Complex setup

Container-based

🚀 75% faster

Code Review Process

Traditional

GitHub PRs + automation

🚀 50% faster


Cost Analysis - Development Costs

Cost Factor

Legacy Approach

CoE Approach

Cost Impact

Developer Onboarding

2-3 days @ $800/day

0.5 days @ $400/day

💰 $1,200 savings per developer

Environment Setup

Manual setup time

Automated setup

💰 75% time reduction

Documentation Maintenance

High manual effort

Streamlined process

💰 60% effort reduction

Deployment Process

Manual deployment effort

Automated pipeline

💰 80% effort reduction

Error Resolution

Complex debugging

Health checks + monitoring

💰 50% faster resolution


Cost Analysts - Operational Costs

Operational Aspect

Legacy Approach

CoE Approach

Cost Efficiency

Infrastructure Management

Complex manual processes

Automated scaling

💰 40% reduction

Monitoring & Alerting

Basic monitoring

Comprehensive observability

💰 Better ROI through prevention

Security Management

Planned implementation

Automated security

💰 Lower security risk

Maintenance Overhead

High manual effort

Automated processes

💰 60% reduction