Business Analyst

Business Analyst

Reviews, analyzes, and evaluates business systems and user needs. Formulates systems to parallel overall business strategies. Experienced with business process reengineering and identifying new applications of technology to business problems to make business more effective. Familiar with industry standard business process mapping, and reengineering. Prepares solution options, risk identification, and financial analyses such as cost/benefit, ROI, buy/build, etc. Writes detailed description of user needs, program functions, and steps required to develop or modify computer programs.

The Compliance and Quality Control (CQC) Division is undertaking a project involving transforming the existing Solicitation Review System from its current architecture—built using Microsoft PowerAutomate, Microsoft Forms, Excel-based data storage, and PowerBI visualizations—into a redesigned workflow and data management system built on Jotform.

The contractor will serve as the Business Analyst, providing structured requirements gathering, documentation, gap analysis, validation, and testing support. The contractor will be responsible for coordinating and leading any requirements gathering meetings with CQC staff. The project involves collaboration with the Senior Systems Advisor, who will be responsible for system design and development.

The current Solicitation Review System uses:

• Microsoft Forms for data entry
• PowerAutomate for workflow automation, email generation, and PDF creation
• Excel files as the underlying data store
• PowerBI dashboards for data visualization

The system must be migrated to Jotform, which will replace Microsoft Forms and PowerAutomate as the workflow, email, and PDF generation platform. Data structures will change, requiring a strategy for blending historical Excel based data with new Jotform-based data. A redesigned PowerBI dashboard will be built by the Senior Systems Advisor.

The project includes redesigning forms, restructuring workflow logic, supporting reporting redesign, and ensuring legacy and new data can coexist for unified analytics.

The Business Analyst (BA) performs business analysis work to support the Compliance and Quality Control Division's Solicitation Review System's re-write project. This role partners with business owners throughout product planning, requirements definition, and delivery cycles. Responsibilities include analyzing complex technical and business processes, identifying efficiencies, and prioritizing needs. The BA coordinates the gathering, development, documentation, and verification (testing) of requirements and works under limited supervision with considerable latitude for initiative and independent judgment.

Essential Job Functions:

• Elicit and document business requirements for the existing Solicitation Review System, ensuring accuracy and effective communication with stakeholders and the development team. Responsible for coordinating, scheduling, and leading all requirements-gathering meetings. (40%)
• Conduct gap analysis of existing system functionality against desired system functionality for the Solicitation Review System, including workflows and reporting through PowerBI. (20%)
• Collaborate daily with the Senior Systems Advisor to track the development and implementation of requirements and test new and existing system functionality for adherence to business requirements for the Solicitation Review System. Update and maintain requirements documentation throughout the life of the project. (30%)
• Report weekly to the Director of Contract Compliance Unit regarding progress, potential issues, and overall status. (10%)

Knowledge, Skills and Abilities:

• Knowledge of BABOK Guide principles, including elicitation, requirements analysis, and validation.
• Knowledge of gap analysis methodologies—comparing current state vs. desired state and identifying missing capabilities.
• Knowledge of the capabilities and limitations of computer systems or management information systems.
• Knowledge of process or systems analysis and design work.
• Knowledge of the Software Development Lifecycle (SDLC)
• Skill in defining all types of requirements, functional specifications, and other deliverables.
• Skill in policy interpretation and translating regulations into system requirements.
• Skill in requirements elicitation techniques such as interviews, workshops, document analysis, observation, and surveys.
• Skill in working collaboratively and cooperatively with colleagues and in building consensus.
• Skill in interpersonal relationships, including the ability to work with people under pressure, negotiate among multiple parties, resolve conflicts, and establish and maintain effective working relationships with various levels of personnel in governmental entities.
• Skill in troubleshooting, performance tuning, and problem-solving.
• Skill in verbal, written, and presentation communication.
• Skill in Microsoft Excel.
• Ability to create clear, complete, and actionable requirements documentation.
• Ability to build consensus across multiple teams.
• Ability to ensure accuracy in documenting system functionality and regulatory requirements.
• Ability to identify compliance gaps and propose feasible solutions.
• Ability to adapt effectively to evolving regulations and system complexities.
• Ability to build trust and maintain relationships across technical and business teams.

Deliverable Requirements:

• Requirements Documentation Package – Solicitation Review System (SRS)
• Current-State Documentation, including:
• Process maps of existing workflows (from Microsoft Forms to PowerAutomate to Excel to PowerBI).
• Field inventory documenting all data fields used across Forms, Excel files, PowerAutomate flows, email templates, and PDF outputs.
• User roles and permissions, including who submits, reviews, approves, and receives communications.
• Catalog of notifications, triggers, and automated actions in the current PowerAutomate setup.
• E-mail Templates used for automated system e-mails.
• Future-State Requirements
• Functional Requirements Document, which must include:
• Step-by-step workflow description for each stage of the Solicitation Review process.
• Required form logic, branching, validation, and conditional workflow steps.
• Email triggers, recipients, templates, timing, and conditions.
• PDF generation requirements (content, formatting, data fields, branding).
• Data capture requirements, including revised field definitions.
• Requirements traceability matrix, which must link business needs to functional requirements to test cases.
• Updated e-mail templates for automated system e-mails.
• Reporting Requirements, which must include a clear definition of:
• Required metrics, KPIs, filters, and drill-downs.
• Required alignment rules between legacy Excel data and new Jotform submissions.
• Data transformation and mapping specifications.
• Data quality rules and business logic.
• Gap Analysis & Recommendation Report
• Gap Identification, which must include:
• Workflow discrepancies (e.g., PowerAutomate actions that must be replicated or redesigned in Jotform).
• Data field gaps between old Excel model and new Jotform model.
• Reporting gaps between current and desired PowerBI capabilities.
• Process pain points identified during interviews.
• Recommendations, which must include:
• Proposed solutions for each gap.
• Required form modifications.
• Suggested workflow improvements.
• Risks, assumptions, and dependencies.
• Recommended approach for combining legacy AND new data in PowerBI.
• Implementation Support & Collaboration Deliverables
• Requirements Change Log, which is a running, version-controlled log that must document:
• New requirements
• Modified requirements
• Requirements removed or deferred
• Stakeholder approvals
• Weekly Collaboration Artifacts, which must include:
• Meeting summaries
• Action items
• Clarifications to technical requirements
• User manual covering the new system for all user roles.
• Testing Assets & Validation Deliverables
• Master Test Plan, which must define the approach for validating both systems, including:
• Testing scope
• Test methodology
• User acceptance testing (UAT) roles
• Environments and prerequisites
• Test Cases & Scripts, which must validate all requirements including:
• Jotform workflow paths
• Form field validation
• Email triggers and PDF output checks
• Data exports
• PowerBI logic and metrics
• Integration of legacy and new