Ocean Salmon Project Data System

The Vendor is required to provide the new online system must be able to manage ocean salmon project (OSP) data, provide statistical analytics, and support critical internal and external reporting processes.
- For nearly three decades, OSP has conducted its data management and analysis activities within the Microsoft Visual FoxPro (VFP) environment, a system which has served the project well given its user-friendly and integrated database design, management, and analysis features. 
- However, the language is no longer supported by Microsoft and has not been for some time, meaning that at some unknown point in the future it may become inoperable.
- The unsupported system also poses a security risk to the State’s information systems in a broader sense.
- By migrating our databases and applications to a modern platform, we will:
•    Improve data accuracy
•    Enhance reporting capabilities to enable faster decision-making
•    Reduce manual data entry time
•    Increase system stability to support future growth and prevent downtime
•    Database development and migration of existing historical datasets 
•    Creation of a data entry user interface, migration of existing data processing and estimation programs to a new programming language, and normalization of datasets
- Outdated and hard-to-navigate user interface: 
•    The current data system, built on Visual FoxPro (VFP), is outdated and features a hard-to-navigate user interface that hinders workflow efficiency. 
•    Its legacy design lacks the intuitive functionality expected in modern software, making routine tasks cumbersome for users. 
•    Additionally, VFP has a steep learning curve, requiring significant staff time to train new hires. 
•    This extended onboarding process diverts resources from core program activities and highlights the need for a more user-friendly, modernized solution. 
•    Compounding these challenges, the absence of comprehensive Standard Operating Procedures (SOPs) for some processes means they are not fully understood and can create significant knowledge gaps when veteran staff leave the Department. 
•    A modernized system with readily available SOPs would help ensure consistency, reduce training time, and safeguard institutional knowledge across all processes.
- Reliance on Manual Workarounds: 
•    The current Visual FoxPro (VFP) system relies on manual workarounds due to its outdated, non-normalized data structure. 
•    Tables are not relational and do not communicate efficiently with one another, making data management inefficient. 
•    There is no user interface for bulk edits, so updates require frequent programmatic changes, increasing staff workload and risk of errors. 
•    This dependence on manual coding for updates increases the risk of errors and slows down critical data processing workflows. 
- Security and Support Risks of an Unsupported Platform: 
•    Visual FoxPro (VFP) is no longer supported by Microsoft, creating security and compatibility risks. Its lack of updates and limited integration with modern systems restricts scalability and underscore the need for a more secure, sustainable platform.
- Manual Data Transfers and Limited System Integration: 
•    The current data system cannot directly consume data from other agency systems, requiring staff to manually upload transactional data. 
•    This process is time-consuming and increases the risk of errors or omissions. 
•    Additionally, tracking changes to recently edited records must be done manually, adding to staff workload and reducing overall data accuracy and efficiency.
- Lack of Edit Tracking and Metadata Capture: 
•    The current Visual FoxPro (VFP) system lacks the ability to capture metadata related to data edits, such as who made a change and the reason for the update. 
•    While full versioning of records is not required, the ability to view basic edit history is important for transparency, accountability, and quality assurance. 
•    This limitation makes it difficult for the team to audit changes or understand the context behind data modifications.

- Intent to respond (optional) Due Date: October 17, 2025
- Questions/Inquires Deadline: October 17, 2025