Horse Racing Management System

The vendor is required to provide horse racing management system (HRMS) application is built using a Microsoft .net backend, an angular frontend, and MSSQL databases.
- IT is comprised of four main modules:
1. Licensing: 
•    This is the core of the application. 
•    It handles user profiles, license entries (both manual and online), notes for communication, regulatory issues (rulings), and links between employers and employees. 
•    It also manages financial records for licensed individuals. 
•    Most reports generated refer to the licensee profile for additional details.
•    Includes a public portal for licensees to submit applications and manage their accounts.
2. Investigations: 
•    This section is crucial for tracking individuals under scrutiny for rule violations in racing. Investigators create cases linked to licensing profiles. 
•    All case reports and investigation metrics, such as searches (vehicles, rooms, and tack rooms), drug tests for humans, and other confidential matters, are managed here. 
•    This module requires strict user permissions.
3. Equine medical: 
•    This section stores all horse medical information, including dead horse reports, equine drug test positives, and out-of-competition testing. 
•    Medical reports for registered horses (vet lists, steward lists, and bleeder certificates) are entered and stored here, generating reports for staff to monitor horse health. 
•    It is integrated with the investigations module.
4. Breed development: 
•    This section manages breeding information, including registrations, nominations, and entries for mares, stallions, and foals. 
•    It also records race data and distributes award monies. 
•    Although focused on horses, it links to the license profile for stables, caretakers, and trainers.
- Technology stack
1. Frontend
•    Framework: angular 15.2.6
•    Language: typescript 4.9.5
•    UI components: bootstrap 4.3.1, ng-bootstrap 11.0.1
2. Backend
•    framework: asp.net web API 2 (.net framework 4.7.2)
•    Language: c# 8.0
•    Authentication: owin, oauth 2.0, azure active directory
•    ORM: entity framework 6.4.4
•    Reporting: active reports 13.2
•    Document generation: aspose.words, aspose.cells
•    Error logging: elmah, nlog
•    API documentation: swagger and swash buckle
3. Database
•    Database: Microsoft SQL server
•    ORM: entity framework 6.4.4 (code-first approach)
•    Migration strategy: EF migrations with seed data for code tables
4. Dependencies
•    Azure services: azure ad (authentication), azure blob storage (file storage), azure key vault (secrets management - planned)
•    Email: send grid for transactional emails and notifications
•    Monitoring: appdy namics agent for application performance monitoring
•    File processing: epplus 4.1.0 for excel generation
•    Utilities: newtonsoft.json, crypto-js, uuid, moment.js
5. Build tools
•    Frontend: angular cli 15.2.6, web pack (bundled with cli)
•    Backend: msbuild, nuget package manager
•    CI/CD: azure devops pipelines (current), migrating to github actions
•    Package management: npm (frontend), nuget (backend)
6. Development tools
•    IDE: visual studio 2022 (backend), vs code (frontend)
•    Testing: jasmine and karma (frontend), nunit (backend - unit tests exist)
•    Linters: tslint (frontend - deprecated, needs eslint migration), editor config
•    Version control: git (azure devops repos, migrating to github).