Cyma Systems

 System Architect

onsite

Tallahassee, FL .

The scope of this Requirement will include assisting the Division of Agricultural and Environmental Services in accomplishing its data processing, system maintenance, modernization, and data migration goals. Scope responsibilities include, but are not limited to assisting in the maintenance and enhancement of all AES information systems, including LIMS, DIVAS, ICOMS, and any additional legacy or future applications 

•         Performing updates resulting from operating system changes, security requirements, infrastructure updates, or business needs identified by the Division, Department, or Legislature

•         Maintaining and updating database structures, queries, data tables, functions, and related components supporting LIMS, DIVAS, and ICOMS

•         Assisting with the Department’s cloud migration strategy, including transitioning systems and data away from Oracle platforms

•         Assisting with or performing data migration activities during technology transformation projects •       Supporting application development, updates, and module enhancements built with .NET Framework, ASP.NET, C# .NET, AngularJS, Bootstrap, JavaScript, Oracle, and other appropriate middleware

•         Maintaining and supporting all necessary links, data exchanges, and interfaces between AES applications and any enterprise systems, external services, or third‑party applications to ensure proper integration, data flow, and system functionality

•         Assisting with the installation and maintenance of .NET components, development tools, and other utilities required for system support

•         Maintaining Development, Test, and Production environments for AES systems, including database and application components

•         Assisting with or performing promotion of code between Development, Test, and Production environments

•         Providing technical consultation and coordination with internal AES staff, other FDACS divisions, and third‑party vendors to support integration, modernization, and cross‑system data needs

•         Maintain forms, reports, scripts, and modules across AES applications

•         Support decommissioning of outdated or legacy systems as directed by the Division

•         Comply with all Department Administrative Policies and Procedures (AP&P)

SKILLS

To accomplish the work outlined above, an experienced Systems Architect with the following skills and experiences listed below. Technical Skills, written and verbal communication.

•         Minimum 10 years of experience with .Net and Visual Studio;

•         Minimum 10 years of experience in programming in Microsoft ASP.NET and MS Framework 4.0 or higher;

•         Minimum 10 years of experience in programming with Oracle Web Forms and Reports;

•         Minimum 5 years of experience working with AES LIMS application and database components;

•         Experience with AES DIVAS components and program areas;

•         Experience with AES ICOMS components and program areas;

•         Experience and ability to work independently;

•         Experience working in a multi-development group;

•         Experience with object-oriented development techniques is required;

•         Excellent verbal and written communication skills;

•         Ability to communicate effectively with technical and user staff;

•         Ability to communicate effectively with management;

•         Candidate must follow FDACS standards and guidelines for application development.

•         Documentation of the solution for each item, with a narrative explaining what modifications were made, shall be reported weekly. 

•         Testing will be scheduled and coordinated by the Division Information Officer or designee with users for gathering information, testing, task verification and other aspects that require interaction with Division staff.

•         Testing will incorporate a test plan in advance of asking the user to test the application, to provide the test steps the user is to take for testing each scenario of the corrected feature, form, report or functionality.

•         All code behind the forms, procedures, packages or other objects where code is written or modified will be documented as comments above or within the code and will include, at a minimum, the following:

o name of developer affecting code; o date code was affected; o explanation of what change was made and for what reason.

•         Change log requests will include a description of the events represented or actions taken on data by the scripts, packages or procedures in the request.