Incite Agpro - Cost Itemization.xlsx
XLSX spreadsheet 190 KB Posted
- Solicitation number
- 124065 O5
- Issued by
- Blaine County, Nebraska
About this file
This cost itemization spreadsheet documents the development activities and pass-through costs for Incite AgPro LLC's proposal to the State of Nebraska Department of Water, Energy, and Environment (NDWEE) for RFP 124065 O5, which seeks to develop and implement the ONE RED Ag Data Bank and Grants Program. The proposal itemizes 83,890 hours of development labor organized across seven primary platforms: the CI Data Bank Platform (1.1-1.7), the Grant Program Interface Platform (2.1-2.7), and Program Support services (3.1-3.7). Major deliverables include system design and development (1.1, 2.1), data security and privacy controls (1.2, 2.2), payment processing integration (1.3, 2.3), system validation and quality assurance (1.4, 2.4), user training and support resources (1.5, 2.5), reporting and analytics capabilities (1.6, 2.6), and ongoing platform support and maintenance (1.7, 2.7). Key platform features encompass CI score microservices, producer and ASP portals, admin dashboards, document intake workflows, payment status tracking, API design with OpenAPI specifications, OAuth 2.0 authorization flows, role-based access controls, and comprehensive audit logging. The contract term runs through September 30, 2029, with options to renew for two additional six-month periods, and the cost structure reflects three years of sustained operations and enhancements post-beta launch in 2026.
The total labor cost is calculated at $12,583,500 based on 83,890 hours at a blended rate of $150 per hour, with pass-through costs totaling $774,312 across three years covering security audits and compliance ($360,000), identity verification via ID.me ($72,500), payment processing through PayPal Hyperwallet ($43,000), cloud infrastructure on Microsoft Azure ($43,200 for app hosting), data warehousing and ML inference services ($28,800 each), ticketing and helpdesk solutions ($32,400), and supplementary services including SIEM/security monitoring ($18,000), Entra ID licensing ($13,500), dependency scanning ($12,960), on-call incident management ($10,800), GitHub Enterprise security ($9,072), and various other cloud, observability, and document processing services. The itemization demonstrates substantial investment in security controls, with dedicated cost line-items for annual penetration testing, continuous vulnerability scanning, application security testing, audit compliance, and security operations. The proposal assumes producers and ASPs as primary user constituencies with distinct workflows, field data integration requirements, and support needs, and includes baseline provisions for geospatial components (field/CLU selection), multi-tenant document management, event-driven architecture with OpenTelemetry instrumentation, and capacity planning for peak periods around grant application windows and payment cycles.
View the file
Other files
Show all 43
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Development Activities
| RFP 124065 O5 – ONE RED Ag Data Bank and Grants Program - Incite AgPro LLC (“incite.ag”) - Itemized Development Activities By Deliverable | |||||||
| Deliverable | Cost ID | Cost Item | Sub Cost ID | Activity | Resources | Hours | Description |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.01 | Project kickoff, scope decomposition, preliminary architecture, and requirements elaboration (Data Bank) with NDWEE sponsors | Project Manager; Business Analyst; Solution Architect | 300 | Translate 1.1 requirements into an implementable backlog (user stories + acceptance criteria), identify dependencies with 1.2-1.7, and confirm beta-critical workflows. Supports: ASP uploads, producer access to scores/history, and scalable storage |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.02 | Release planning and delivery roadmap (beta + 3-year evolution) | Project Manager; Solution Architect | 110 | Define phased releases (beta in 2026 → GA hardening → feature expansion), align milestones to NDWEE stakeholder checkpoints, and maintain integrated roadmap across deliverables. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.03 | Target architecture and non-functional design (scalability, resiliency, modularity) | Solution Architect; Cloud Architect; DevOps Engineer | 240 | Produce/maintain architecture decisions for private-network deployment, service boundaries, scaling model, and failure modes. Align with data-flow diagrams for auth + data plane endpoints. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.04 | Solution design workshops and diagram refinement (end-to-end Data Bank flow) | Solution Architect; Project Manager | 120 | Run stakeholder design reviews to validate user journeys: producer login, ASP delegated authorization,cCrop data & CI score submission, and producer dashboard consumption. Update data-flow diagrams as requirements evolve. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.05 | Core data model & domain schema design (scopes, users, fields, CI score) | Data Architect; Backend Engineer | 180 | Design transactional schema for producer accounts, fields, CI scores, and immutable history; define versioning/idempotency strategy for repeated submissions. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.06 | API spec/contract design (OpenAPI) for Data Bank user & ASP integrations | Backend Engineer; Solution Architect | 190 | Define/maintain REST API contracts / spec for CI score upload/retrieval, field resources, and user-scoped access patterns; publish OpenAPI spec and example requests. Example Python & NodeJS application workflows published to Github |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.07 | ASP delegated authorization flows (OAuth 2.0) + token issuance foundations for Data Bank | Backend Engineer; Solution Architect | 260 | Implement OAuth 2.0 authorization endpoints and token issuance behavior required for ASP access to producer-scoped APIs (per diagrammed OIDC+OAuth flow). Includes app registration metadata handling for ASP clients (non-payment). |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.08 | Versioned CI Score microservice (core engine supporting score validation & scenario modeling) | Backend Engineer; Solution Architect; Agronomy SME | 340 | Codification of USDA FD-CIC latest release to scalable runtime (FastAPI, ExpressJs server). Categorical emissions breakdown using proprietary CI calculation knowledge; USDA grounded nutrient budget determination. Variable change requirement based on unanounced (yet expected) USDA model release schedule. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.09 | CI score ingestion service (ASP upload → validation → persistence → audit trail) | Backend Engineer; Data Engineer | 400 | Build ingestion pipeline to accept verified CI scores from ASPs, validate payloads, enforce schema/version rules, handle retries/idempotency, and write to transactional store with audit metadata. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.10 | Producer portal UI shell (navigation, account context, score dashboard scaffolding) | Frontend Engineer; UX/UI Designer | 440 | Design and implement producer-facing portal foundation and IA (information architecture) enabling access to CI scores, payment status placeholders, and historical data views. Design mockups produced in Figma/Miro, and validated with NDWEE stakeholders. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.11 | Producer CI score experience (score views, history timeline, discrepancy handling, status tracking, CI scenario modeling environment) | Frontend Engineer; Backend Engineer | 440 | Implement end-user features: view current/previous CI scores, track statuses, and browse immutable history with drilldowns, experiment with scenario modeling differentials from current crop profile. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.12 | Admin search & filtering capabilities (baseline) for CI score data | Backend Engineer; Frontend Engineer; Data Engineer | 360 | Deliver baseline search/filter over CI score and field history (time range, geography, program, status). Advanced analytics/reporting deepening is costed under 1.6. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.13 | Producer exports (baseline CSV/PDF) for personal records and downstream workflows | Backend Engineer; Frontend Engineer | 160 | Provide basic exports for producer-facing records (score history summaries) and supportability. Complex program analytics and NDWEE reporting are covered in 1.6. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.14 | AI Driven Producer Property Ownership Validation | Backend Engineer; Solution Architect | 480 | Develop AI orchestration for extraction of property ownership from FSA 578 (or equivalent supporting records), and validation against producer provided crop data, with failsafes resulting in human escalation. Regular model testing to mitigate model drift & reincorporate new training data for enhanced model learning. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.15 | NDWEE reviewer/admin views (Data Bank): flagged items & manual resolution workflows (foundation) | Frontend Engineer; Backend Engineer | 230 | Implement initial admin/reviewer UI + APIs needed to inspect flagged producer/field/score anomalies for Data Bank operations (e.g. crop-field mismatch, invalid submissions). Full QA/security/support are covered in other cost IDs. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.16 | Document intake touchpoints for Data Bank (uploads + metadata; non-security implementation) | Backend Engineer; Frontend Engineer | 200 | Build user-facing upload workflows and metadata persistence for documents supporting CI records (e.g., validation artifacts). Malware scanning/security controls are costed under 1.2; QA under 1.4. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.17 | ASP integration sandbox + test harness (developer experience) | Backend Engineer; DevOps Engineer | 160 | Provide sandbox environment/config and automated harness for ASPs to validate OAuth and CI score upload integration during onboarding; includes seeded test data and example scripts. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.18 | Technical documentation for Data Bank architecture + APIs (non-training) | Technical Writer; Solution Architect; Backend Engineer | 130 | Maintain architecture overview, developer onboarding, OpenAPI usage notes, and integration guidance for NDWEE and ASP API integration stakeholders. End-user training materials are costed under 1.5. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.19 | Performance engineering for beta (query design, caching strategy, scale testing readiness) | Backend Engineer; DevOps Engineer | 140 | Optimize core read paths (score/history/search) for responsive UX and prepare for peak-load conditions; coordinate with formal QA validation in 1.4. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.20 | Accessibility + responsive UX hardening for producer portal (baseline) | Frontend Engineer; UX/UI Designer | 120 | Ensure UI components meet accessibility and responsive requirements for common devices/browsers; incorporate feedback loops prior to beta. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.21 | Operational readiness features needed by core platform (health endpoints, structured logs, feature flags) | Backend Engineer; DevOps Engineer | 160 | Implement baseline platform operability needed for beta: health/ready endpoints, request correlation IDs, feature-flag wiring for incremental releases. Full monitoring/SLA operations are costed under 1.7. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.22 | Enhancement backlog delivery (Years 2–3): feature expansion & UX iteration for Data Bank | Frontend Engineer; Backend Engineer; Solution Architect; Project Manager | 1300 | Ongoing enhancements after beta: improved workflows, additional producer dashboard capabilities, iterative UX improvements, and support for evolving program needs (excluding dedicated maintenance/SLA in 1.7) |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.23 | Evolving data standards + schema evolution support (e.g., ADAPT payload changes) | Data Engineer; Backend Engineer | 300 | Maintain compatibility with evolving field/crop data standards used by ASPs; manage schema migrations, version negotiation, and backward-compatible transformations. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.24 | Dashboard visualization integration points (optional connectors / embedding scaffolding) | Frontend Engineer; Backend Engineer | 120 | Implement scaffolding for integration with third-party dashboards (e.g. Power BI) or internal dashboards to surface CI score summaries. Deeper analytics/reporting is costed under 1.6. |
| CI Data Bank Platform | 1.1 | System Design and Development | 1.1.25 | Environment setup + infrastructure-as-code (IaC) baseline for Data Bank applications | DevOps Engineer; Cloud Architect | 290 | Provision dev/test/prod environments for Data Bank services with repeatable IaC, including deployment automation hooks and configuration management. Detailed security hardening is costed under 1.2; ongoing ops under 1.7. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.01 | Security program kickoff + threat modeling for Data Bank | Security Architect; Solution Architect; Project Manager | 140 | Establish security objectives, data classification (PII/crown-jewel), threat models for producer/ASP/admin flows, written information security plan (WISP), and security backlog aligned to 1.2. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.02 | Network isolation architecture (VNet, subnets, no-public-endpoint posture, NAT & VPN gateway) | Cloud Security Engineer; DevOps Engineer; Cloud Architect | 270 | Design/implement private-network boundary for apps and data-plane services, including subnet segmentation and deny-by-default ingress/egress patterns. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.03 | Private endpoints/PrivateLink + private DNS configuration for data stores | Cloud Security Engineer; DevOps Engineer | 210 | Implement private endpoints for CosmosDB/Storage/Key Vault (and other dependencies), private DNS zones, and routing validation to ensure no public data-plane exposure. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.04 | Edge ingress hardening (WAF / reverse proxy policy, TLS posture) | Cloud Security Engineer; DevOps Engineer | 170 | Configure controlled ingress, WAF rules, rate-limits, bot protections, and enforce TLS 1.2+ end-to-end for client→edge→app gateway→service traffic. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.05 | Identity & access controls (IAM, managed identity, RBAC, least privilege, JIT elevation) | Security Engineer; DevOps Engineer; Backend Engineer | 350 | Implement managed identity patterns for services, least-privilege RBAC on apps/databases, and JIT elevation workflow for developers/admins (time-bound access). |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.06 | Key management (Key Vault), secret/cert rotation policies, and signing key governance | Security Engineer; DevOps Engineer | 290 | Implement centralized key management (Key Vault), automate certificate and secret rotation, key versioning, and strict RBAC on key operations (sign/decrypt). |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.07 | Encryption in transit + at rest (platform-wide implementation + validation) | Security Engineer; DevOps Engineer; Data Engineer | 220 | Configure/enforce encryption at rest for CosmosDB, Blob/DFS, backups and queues; validate transport encryption for all endpoints and internal calls, including automated tests/alerts for regressions. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.08 | Application-layer envelope encryption for crown-jewel fields (PII, identity artifacts, payment tokens) | Security Engineer; Backend Engineer | 300 | Design and implement envelope encryption (e.g. RSA wrapped AES-GCM data keys protected by Key Vault/HSM keys) for sensitive fields and documents; include key rotation and re-encryption strategy. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.09 | Secure software supply chain (dependency scanning, container scanning, Software Bill of Materials (SBOM) ) | DevOps Engineer; Security Engineer | 260 | Implement CI/CD security controls: dependency and base-image scanning, SBOM generation, secrets scanning, and policy gates for promotion to UAT/prod. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.10 | SAST/DAST + penetration testing program (automation + vendor coordination) | Security Engineer; QA Security Tester; Project Manager | 360 | Operationalize SAST/DAST pipelines, schedule annual (and pre-GA) penetration tests, track findings through remediation verification. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.11 | Security logging & audit trails surfacing (end-to-end request lifecycle, access logging) | Backend Engineer; DevOps Engineer; Security Engineer | 300 | Implement structured immutable logs, request correlation IDs, and tamper-evident audit logs for producer/ASP/admin actions; define retention for security logs and evidence collection. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.12 | API security hardening (OWASP, injection defenses, rate limits, abuse controls) | Backend Engineer; Security Engineer | 270 | Implement OWASP-aligned controls: input validation, parameterized SDK queries, authZ enforcement (Entra ID, JWTs), request size limits, throttling, and abuse detection for CI score uploads and portal APIs. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.13 | Data privacy compliance design (policy mapping, data minimization, consent boundaries) | Privacy/Compliance Lead; Security Architect; Business Analyst | 210 | Map applicable federal/state requirements and NDWEE policies to platform controls; define data minimization rules and access scope boundaries (producer vs ASP vs admin). |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.14 | Retention, deletion, and records management workflows for PII and confidential data | Privacy/Compliance Lead; Backend Engineer; Data Engineer | 330 | Define and implement retention schedules, deletion workflows, and legal hold/recordkeeping constraints for identity artifacts, ownership documents, crop-year submissions, and payment metadata. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.15 | Data access reviews + periodic RBAC recertification (operational control) | Security Engineer; Compliance Lead | 140 | Run quarterly access reviews for privileged roles, recertify RBAC assignments, validate JIT process effectiveness, and archive evidence for audits. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.16 | ASP verification & authentication controls (approved vendor registry + allowlists) | Security Engineer; Backend Engineer; Program Manager | 250 | Implement controls ensuring only approved/verified ASPs can upload CI scores: vendor registry, client credential lifecycle, redirect URI allowlists, environment separation (UAT vs prod), and scope-limited consent policies. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.17 | Producer identity verification integration security posture (ID.me flow hardening) | Security Engineer; Backend Engineer | 140 | Harden and validate producer identity verification flows (token handling, redirect safety, session integrity, replay protection) and logging for producer auth events. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.18 | Document malware scanning + quarantine workflow (event-driven security control) | DevOps Engineer; Backend Engineer; Security Engineer | 210 | Implement file upload scanning pipeline (issue short-lived SAS URL → blob created event → malware scan → review status update), including quarantine and reviewer notification. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.19 | Incident response plan + tabletop exercises + runbooks (security operations) | Security Engineer; DevOps Engineer; Project Manager | 210 | Create IR plan, severity matrix, on-call/security escalation runbooks, and perform annual tabletop exercises; store evidence and improve procedures over 3 years. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.20 | Continuous posture management (Defender/SIEM signals, config drift detection, hardening backlog) | Security Engineer; DevOps Engineer | 380 | Enroll infra in posture management, monitor vulnerability/configuration signals, manage remediation backlog and drift detection, and produce periodic security posture reports. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.21 | Annual cybersecurity & privacy audit execution + reporting (CISA/CISM/CISSP team) | Security Engineer; Compliance Lead; External Auditor (CISA/CISM/CISSP) | 360 | Plan, support, and report annual audits (SOC 2/ISO 27001/NIST-aligned scrutiny), including evidence preparation (logs, access reviews, diagrams, policies) and remediation tracking. |
| CI Data Bank Platform | 1.2 | Data Security and Privacy | 1.2.22 | Security + privacy documentation (policies, data handling standards, evidence packages) | Technical Writer; Compliance Lead; Security Architect | 170 | Maintain security & privacy documentation sets: data handling standards, retention/deletion policy docs, audit evidence templates, and architecture/security posture updates as system evolves. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.02 | CI score validity confirmation service (re-scoring + delta detection gate) | Data Engineer; Backend Engineer | 290 | Implement automated CI re-scoring validation using the codified FD-CIC model; detect deltas vs submitted score and route to 'In Review' workflow with ASP notification prior to disbursement. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.03 | Payment calculation engine (business logic defined config) | Backend Engineer; Data Engineer | 40 | Build rules engine to compute incentive amounts once CI score is confirmed (config-driven parameters, versioning, auditability). Includes rule simulation for admins and reproducible calculations stored with each payment record. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.04 | Payment provider selection support + integration architecture (ACH, digital wallets, direct deposit) | Solution Architect; Payment Integration Engineer; Compliance Lead | 170 | Translate payment rails needs into provider capabilities; Consider PayPal Hyperwallet and Plaid; Design integration for a third-party payout provider supporting ACH/direct deposit and wallet options. Includes spec/contract/API review and integration plan. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.05 | Producer payout account onboarding (provider OAuth 2.0 + consent redirect flows) | Backend Engineer; Frontend Engineer | 270 | Implement producer OAuth redirect to payment provider for bank connection consent, success/failure callback handling, and UX for 'Connect payout account' and re-auth. Store only tokenized references to banking details (no raw routing/account numbers). |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.06 | Token lifecycle management for payment provider (secure storage, refresh, rotation) | Backend Engineer; Security Engineer | 210 | Implement secure handling of provider-issued access/refresh tokens, rotation, revocation, and scoped usage for payment status checks and payouts. Align token custody with platform security posture. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.07 | Escrow/disbursement account integration (NDWEE-controlled funds release via provider payout APIs) | Payment Integration Engineer; Backend Engineer; Finance Ops Analyst | 300 | Implement payout execution from an Incite.ag/NDWEE-controlled escrow/disbursement account using provider APIs after CI confirmation and rule evaluation. Includes batching strategy and internal authorization workflow for release. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.08 | Event-driven payment state sync (webhooks/callback ingestion) | Backend Engineer; DevOps Engineer | 210 | Build webhook receiver + validation to ingest provider callbacks ('deposit initiated', 'deposit completed', failures/returns/holds) and synchronize payment state into CosmosDB producer metadata for real-time UX and exception workflows. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.09 | Payment ledger & reconciliation data model (CosmosDB source of truth) | Data Architect; Backend Engineer | 90 | Design and implement payment/reconciliation metadata store (amount, program, CI model version, timestamps, status, references) as source of truth for producer + admin reporting. Includes immutable audit records and idempotent write patterns. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.10 | Producer payment UX (real-time status + transaction history) | Frontend Engineer; Backend Engineer | 360 | Expose participant views for payment status lifecycle (Queued → Submitted → Processing → Paid/Failed/In Review) and transaction history drilldowns with timestamps and explanations. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.11 | Admin payment operations portal (batches, exceptions, audit trails, filters) | Frontend Engineer; Backend Engineer; Program Manager | 420 | Deliver admin tooling for disbursement batch review, exception queues, holds/release decisions, resolution notes, and filtering/search by producer/status/program. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.12 | Exception handling workflows (returns, rejected deposits, holds, retries) | Backend Engineer; Finance Ops Analyst | 300 | Implement automated and manual remediation paths for ACH returns, rejected deposits, compliance holds, and retry policies. Includes producer notification hooks and admin resolution tracking. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.13 | Reporting feeds (real-time + periodic): NDWEE status reporting + metrics aggregation | Data Engineer; Backend Engineer | 270 | Build reporting extracts/aggregations for NDWEE oversight: counts by status, payouts by program/crop year, exception rates, and reconciliation summaries. Supports quarterly/weekly automated reporting flows where applicable. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.14 | W-9 and tax-year compilation workflow (event-driven eligibility list + delivery) | Backend Engineer; Data Engineer; Technical Writer | 170 | Implement annual producer W-9 compilation workflow (e.g. February) for producers who received incentives during tax period; generate export packages and automated delivery triggers consistent with event-driven reporting design. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.15 | Provider sandbox + automated integration tests (payout rails + webhook replay) | Payment Integration Engineer; QA Engineer; DevOps Engineer | 220 | Stand up provider sandbox environments, implement end-to-end tests for OAuth onboarding, payout creation, webhook callback replay, and reconciliation consistency. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.16 | Auditability + evidence packaging for payment actions (who/what/why) | Security Engineer; Backend Engineer; Compliance Lead | 180 | Ensure payment actions are fully auditable (approvals, holds, overrides, final settlement outcomes) with immutable logs and evidence exports supporting annual audits and dispute resolution. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.17 | Provider change management (multi-provider support, failover strategy, contract evolution) | Solution Architect; Payment Integration Engineer | 210 | Design for provider substitution and optional multi-provider support (e.g., add second payout provider), including abstraction layer, migration plan, and operational playbooks. |
| CI Data Bank Platform | 1.3 | Payment Processing Integration | 1.3.18 | Ongoing enhancements (Years 2–3): new programs, additional payout rails, UX iteration | Frontend Engineer; Backend Engineer; Program Manager; Data Engineer | 400 | Post-beta enhancements to support new NDWEE programs, expanded payout rails, improved participant transparency, and iterative admin operations tooling (excluding general platform support/SLA in 1.7). |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.02 | Test environment architecture + data seeding (dev/test/UAT/prod parity) | DevOps Engineer; QA Engineer; Data Engineer | 300 | Provision/maintain test environments and realistic seeded datasets for CI scores, payments, and documents; enable safe replay of flows without touching production PII. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.03 | Automated unit test coverage baseline (backend services) | Backend Engineer; QA Engineer | 330 | Implement/maintain unit tests for API handlers, validation, rules engine boundaries, and error paths; enforce coverage thresholds in CI. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.04 | Automated unit/component test coverage baseline (frontend) | Frontend Engineer; QA Engineer | 300 | Implement UI component tests for producer portal and admin views (e.g. Selenium); verify state transitions, accessibility hooks, and error states. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.05 | Integration test suite (API ↔ DB ↔ storage ↔ auth) | QA Engineer; Backend Engineer; DevOps Engineer | 310 | Build integration tests spanning ID.me login, ASP OAuth, CI score ingestion, document uploads, and payment state sync (mocked provider in test). Include negative tests and idempotency checks. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.06 | End-to-end (E2E) test automation for critical user journeys | QA Automation Engineer; Frontend Engineer; Backend Engineer | 320 | Automate beta-critical journeys: producer onboarding → view scores/history → connect payout account → view payment status; admin review queues; ASP upload flow using sandbox credentials. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.07 | Data validation and integrity checks (schema, referential integrity, versioning) | Data Engineer; QA Engineer | 300 | Implement automated checks for schema conformance, version compatibility, referential integrity (producer↔fields↔scores↔payments), and immutable history guarantees. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.08 | Performance and load testing (read paths + ingestion paths) | Performance Engineer; DevOps Engineer; Backend Engineer | 390 | Define load profiles and execute tests for score/history reads, search/filtering, CI ingestion bursts, and payment webhook spikes. Produce tuning backlog and re-test cycles. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.09 | Resiliency testing (fault injection, retry behavior, partial outage handling) | DevOps Engineer; Backend Engineer; QA Engineer | 250 | Validate retry, backoff, circuit breaking, and degradation behavior across dependencies (storage, DB, auth, payment callbacks). Verify no data loss and correct recovery states. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.10 | Disaster recovery validation, backup/restore drills and RPO (Recovery Point Objective) and RTO (Recovery Time Objective) verification | DevOps Engineer; Data Engineer; QA Lead | 220 | Execute scheduled backup/restore drills for Cosmos/Storage, validate DR runbooks, and measure RPO/RTO against platform objectives; incorporate improvements. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.11 | Accessibility and cross-browser/device validation (producer + admin portals) | QA Engineer; UX/UI Designer | 90 | Validate HTML/W3-aligned accessibility behaviors, keyboard navigation, screen-reader support, and mobile responsiveness for core workflows; track and verify fixes. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.12 | Security QA validation (verification of 1.2 controls + regression checks) | QA Security Tester; Security Engineer | 180 | Verify implementation of security controls from 1.2 (authZ enforcement, encryption settings, scanning pipelines, WAF rules) through repeatable test cases and regression suites. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.13 | Payment integration QA (sandbox payouts, webhook replay, exception scenarios) | QA Engineer; Payment Integration Engineer | 160 | Execute test matrix for payout onboarding, payout execution, webhook ingestion, returns/retries/holds, and participant/admin status consistency. Includes scripted webhook replays and reconciliation assertions. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.14 | ASP integration UAT testing support (partner coordination + certification) | QA Lead; Backend Engineer; Program Manager | 340 | Support ASPs through UAT certification: validate OAuth flows, payload conformance, error handling, and data correctness; issue integration sign-off and manage remediation cycles. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.15 | User acceptance testing (NDWEE) planning + facilitation (beta and post-beta) | QA Lead; Project Manager; UX Researcher | 200 | Plan and facilitate NDWEE UAT sessions, collect feedback, triage defects/enhancements, and verify closure. Includes beta UAT and periodic UAT for major releases. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.16 | Defect triage, root cause analysis, and quality gates (release readiness) | QA Lead; Engineering Lead; Project Manager | 380 | Operate defect triage process, prioritize fixes, enforce release quality gates, and maintain release notes and known-issues logs. Includes ongoing regression cycles during years 2–3. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.17 | Regression testing automation maintenance (suite upkeep across releases) | QA Automation Engineer | 450 | Maintain and extend regression suites as features expand (1.1/1.3/1.6), including flaky test remediation and pipeline optimization. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.18 | Data migration and schema change validation (forward/backward compatibility) | Data Engineer; QA Engineer; Backend Engineer | 220 | Validate schema migrations, backfills, and version upgrades; test backward compatibility for producers/ASPs during transition windows; verify no corruption or loss of history. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.19 | Operational monitoring validation (alerts, dashboards, synthetic checks) | DevOps Engineer; QA Engineer | 210 | Validate monitoring coverage: synthetic checks for login and key API endpoints, alert thresholds, dashboard correctness, and runbook links; revalidate after major releases. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.20 | Documentation validation (testable runbooks + user-facing help correctness) | QA Engineer; Technical Writer | 170 | Validate correctness of operational runbooks, troubleshooting guides, and key user-facing help content as features evolve; ensure documentation matches system behavior. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.21 | Compliance evidence packages from QA (traceability, test results, sign-offs) | QA Lead; Compliance Lead | 210 | Produce evidence artifacts required for audits and NDWEE oversight: traceability matrices, executed test results, UAT sign-off packages, and release approval records. |
| CI Data Bank Platform | 1.4 | System Validation and Quality Assurance | 1.4.22 | Post-beta quality hardening cycles (Years 2-3): continuous validation of new scope | QA Engineer; QA Automation Engineer; Engineering Lead | 360 | Dedicated QA cycles for post-beta enhancements: new workflows, expanded reporting, new ASP integrations, and new payment/program rules (excluding general maintenance in 1.7). |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.02 | End-user onboarding content (producer): guided tours, quick-starts, FAQs | Technical Writer; UX/UI Designer | 300 | Produce producer-focused quick-start guides for login/ID verification, viewing CI scores/history, connecting payout account, and understanding payment status. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.03 | Help Center / Knowledge Base build-out (searchable articles + versioning) | Technical Writer; Frontend Engineer | 330 | Implement and populate an in-product help center (search, categories, versioning per release) with articles for producers, ASPs, and admins. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.04 | Video tutorials + microlearning modules (producer + admin) | Training Lead; Technical Writer; Multimedia Specialist | 360 | Produce short videos and microlearning modules for core workflows; maintain updated versions for major releases. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.05 | Train-the-trainer program for NDWEE internal support staff | Training Lead; Program Manager | 190 | Develop playbooks and run live sessions to enable NDWEE staff to support producers/ASPs, including escalation paths and common issue diagnostics. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.06 | ASP integration enablement package (docs + samples + webinars) | Developer Advocate; Backend Engineer; Technical Writer | 340 | Provide ASP onboarding materials: OAuth integration guide, payload examples, sandbox usage, error code catalog, and quarterly enablement webinars. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.07 | Support workflow design (ticketing taxonomy, SLAs, escalation, triage) | Support Operations Lead; Project Manager; QA Lead | 210 | Design support processes: ticket categories, response SLAs, escalation criteria (security/payment), and triage playbooks; align with on-call/operations in 1.7. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.08 | In-product contextual help + guided flows (tooltips, checklists, error remediation) | Frontend Engineer; UX/UI Designer | 370 | Implement contextual help components, guided checklists for onboarding, and actionable error messages for common failures (identity verification, payment onboarding, ASP submission issues). |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.09 | Admin/reviewer operations handbook (queues, holds, overrides, audits) | Technical Writer; Program Manager; Compliance Lead | 210 | Create and maintain detailed admin handbook covering review queues, payment holds/releases, evidence collection, and audit-ready workflows. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.10 | Accessibility-friendly documentation + multilingual readiness (baseline) | Technical Writer; Accessibility Specialist | 170 | Ensure training content meets accessibility needs (captions, alt text, readable layouts). Establish translation-ready workflows; produce baseline Spanish versions for high-traffic pages if required. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.11 | Office hours + live onboarding sessions (beta launch + periodic) | Support Specialist; Training Lead; Program Manager | 310 | Run weekly office hours during beta ramp and monthly thereafter; provide live onboarding sessions for ASPs and NDWEE staff at key milestones. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.12 | Release communications + change notes for users (producer/ASP/admin) | Technical Writer; Product Manager | 170 | Publish release notes and change communications per deployment, including “what changed” guidance and any required user actions; align with release management in 1.7. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.13 | Support analytics + continuous improvement loop (top issues, deflection, user satisfaction rating) | Support Operations Lead; Data Analyst | 210 | Track support metrics (volume, time-to-resolution, deflection via help center), identify product fixes that reduce tickets, and report quarterly. |
| CI Data Bank Platform | 1.5 | User Training and Support Resources | 1.5.14 | Annual training refresh for new features/program rules (Years 2–3) | Training Lead; Technical Writer; Product Manager | 200 | Update curriculum and content annually to reflect new program rules, new reporting, and portal UX changes; retire outdated content and re-record key videos. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.01 | Reporting requirements + KPI framework (NDWEE oversight + program outcomes) | Product Manager; Business Analyst; Data Analyst | 130 | Define KPI taxonomy (participation, payments, CI improvements, exception rates) and reporting cadence (weekly/monthly/quarterly). Map KPIs to data sources and access roles. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.02 | Analytics architecture (lakehouse/warehouse model + data contracts) | Data Architect; Solution Architect; DevOps Engineer | 220 | Design analytics zone(s) separated from transactional stores; define data contracts, partitioning, retention, and governance patterns for reporting workloads. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.03 | ETL/ELT pipelines from transactional systems (scores, payments, docs metadata) | Data Engineer; DevOps Engineer | 280 | Build batch and incremental pipelines to move curated datasets into analytics store; include idempotency, schema evolution handling, and lineage metadata. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.04 | Semantic layer / metrics model (standardized definitions + reusable measures) | Analytics Engineer; Data Analyst | 390 | Create standardized metric definitions (payments, adoption, score deltas), reusable dimensions (program, crop year, geography), and versioning for metric changes. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.05 | NDWEE executive dashboards (participation, payments, program health) | BI Developer; Data Analyst | 440 | Build interactive dashboards for NDWEE oversight: participant counts, CI outcomes, payment throughput, exception/hold queues, and trends. Includes iterative design with stakeholders. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.06 | Operational dashboards (SLA, latency, ingestion throughput, webhook health) | DevOps Engineer; BI Developer | 290 | Create operational dashboards for system health and operations that complement 1.7 monitoring; focus on data-plane metrics and business process flow (ingestion, payments). |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.07 | Self-serve reporting exports (scheduled reports, CSV/PDF, email delivery) | Backend Engineer; Data Engineer; Frontend Engineer | 390 | Implement scheduled report generation, export endpoints, and delivery mechanisms; support NDWEE and producers where applicable with role-based access. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.08 | Geospatial reporting & mapping (county/state views, program coverage, outcomes) | Geospatial Engineer; BI Developer; Data Engineer | 410 | Enable map-based reporting of participation and outcomes by geography (county/state/region) using aggregated data; include privacy-preserving thresholds for small counts. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.09 | Privacy-preserving aggregation + disclosure controls for reporting | Privacy/Compliance Lead; Data Engineer | 260 | Implement reporting suppression rules, k-anonymity style thresholds, and role-based redaction to prevent disclosure of sensitive producer info in aggregated outputs. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.10 | Data quality monitoring for analytics datasets (freshness, completeness, drift) | Data Engineer; QA Engineer | 340 | Build automated checks for dataset freshness/completeness, reconcile totals vs transactional truth, and alert on anomalies; maintain as schemas evolve. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.11 | Audit-ready reporting packs (annual summaries + evidence exports) | Compliance Lead; Data Analyst; Technical Writer | 250 | Generate standardized annual reporting packs for oversight and audits: program summaries, payout totals, exception handling evidence, and methodology notes |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.12 | Advanced analytics: CI improvement attribution + scenario analysis | Data Scientist; Data Analyst | 480 | Develop analytical models and scenario tools to evaluate program effectiveness (practice adoption → CI outcome), including cohort analysis and sensitivity views; iterate with NDWEE. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.13 | Data access layer for analysts (secure query endpoints / notebooks) - foundation | Data Engineer; Security Engineer; DevOps Engineer | 300 | Provide controlled analyst access paths (read-only roles, approved query workspaces) without exposing raw transactional systems; integrate with access controls defined in 1.2 |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.14 | API for reporting data products (aggregations + partner feeds) | Backend Engineer; Data Engineer | 340 | Implement APIs for NDWEE reporting data products (aggregated views, status feeds), enabling downstream systems to consume standardized metrics. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.15 | Dashboard governance (certified metrics, access policies, version control) | Analytics Engineer; Compliance Lead | 210 | Establish governance: certified datasets, metric/version change approvals, access policies, and dashboard lifecycle management across years 2–3. |
| CI Data Bank Platform | 1.6 | Reporting, Data Products, and Analytics | 1.6.16 | Enhancements (Years 2–3): new reports, new dashboards, expanded geographies/programs | BI Developer; Data Engineer; Data Analyst; Product Manager | 960 | Post-beta expansion of reporting catalog: new program reports, deeper drilldowns, expanded geospatial/outcome views, and iterative improvements driven by stakeholder feedback. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.01 | Operations model + SLA definition (support tiers, uptime targets, maintenance windows) | SRE Lead; Project Manager; Program Manager | 210 | Define support tiers and SLAs (response times, availability), maintenance windows, and release governance for 3-year operations period. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.02 | incident response readiness (on-call rotations, escalation, runbooks) | SRE; Backend Engineer; DevOps Engineer | 960 | Operate on-call coverage and incident response readiness, including triage, coordination, and post-incident review cadence. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.03 | Monitoring/observability operations (dashboards, alert tuning, synthetic checks) | SRE; DevOps Engineer | 720 | Maintain monitoring stack: dashboards, alert tuning, synthetic probes for login/API/payment flows, and runbook links; continuous refinement as platform evolves. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.04 | Routine maintenance (patching, dependency updates, OS/container base image upgrades) | DevOps Engineer; Security Engineer; Backend Engineer | 840 | Monthly patch cycles, dependency upgrades, container base image refreshes, and compatibility testing; coordinate with 1.2 vulnerability scanning and 1.4 regression suites. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.05 | Release management & deployment operations (CI/CD, change windows, rollback) | Release Manager; DevOps Engineer; QA Lead | 620 | Operate release cadence: deployment coordination, change approvals, rollback/rollback testing, and release notes packaging; support frequent updates over 3 years. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.06 | Platform capacity planning + performance tuning (scale forecasts, hotspots) | SRE; Performance Engineer; Data Engineer | 480 | Quarterly capacity planning, cost-aware scaling decisions, performance tuning for read/search/ingestion paths, and load test re-runs as usage grows. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.07 | Backup/restore operations + DR posture maintenance (scheduled drills) | DevOps Engineer; Data Engineer | 390 | Maintain backup policies, verify restore points, perform scheduled DR drills, and update runbooks as architecture evolves. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.08 | Security operations support (vuln triage, remediation coordination, posture reporting) | Security Engineer; DevOps Engineer | 560 | Triage vulnerability findings, coordinate remediation releases, manage security exceptions, and produce periodic posture reports; complements 1.2 but represents ongoing operational workload. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.09 | Data operations (pipeline monitoring, backfills, reconciliation support) | Data Engineer; SRE | 560 | Monitor ETL/pipeline runs, execute backfills, reconcile discrepancies between transactional and analytics/reporting outputs, and address data incidents. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.10 | Payment operations support (payout exceptions, provider escalations, reconciliation) | Finance Ops Analyst; Backend Engineer; Support Specialist | 620 | Ongoing support for payout exceptions, provider escalations, reconciliation questions, and participant inquiries tied to payment status. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.11 | ASP partner support (integration issues, version changes, sandbox upkeep) | Developer Advocate; Backend Engineer; Support Specialist | 480 | Support ASP partners through integration issues, version changes to payloads, sandbox stability, and certification renewals. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.12 | User support execution (ticket handling, triage, escalation, knowledge base updates) | Support Specialist; Support Operations Lead | 880 | Operate user support queue, triage issues, escalate to engineering, and keep help content current based on recurring issues. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.13 | Change management + stakeholder communications (maintenance notices, incidents, releases) | Project Manager; Release Manager | 290 | Maintain change calendar, send maintenance notices, coordinate stakeholder communications during incidents, and publish ongoing operational updates. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.14 | Cost management + FinOps (cloud spend monitoring, reserved capacity, optimization) | FinOps Analyst; Cloud Architect; SRE | 80 | Monitor cloud spend, optimize storage/compute, implement budgets/alerts, and evaluate reserved capacity/savings plans; quarterly optimization reviews. |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.15 | Minor enhancements/bug fixes as part of operations (non-feature scope) | Backend Engineer; Frontend Engineer; QA Engineer | 960 | Operational engineering work: bug fixes, small usability improvements, and minor changes required for stability/compliance (distinct from major feature work in 1.1/1.3/1.6). |
| CI Data Bank Platform | 1.7 | Ongoing Platform Support, Operations, and Maintenance | 1.7.16 | Annual operational readiness review + audit support (runbooks, evidence, controls) | SRE Lead; Compliance Lead; Security Engineer | 310 | Annual review of operational controls, runbooks, SLAs, and evidence required for audits; validate that operational practices meet NDWEE expectations. |
| Grant Program Interface Platform | 2.1 | System Design & Development | 2.1.01 | Program discovery & requirements elaboration (PI & CI grants) | Project Manager; Product Manager; Solution Architect | 290 | Facilitate workshops with NDWEE stakeholders to confirm grant program scope, producer/ASP/admin workflows, decision points, eligibility gates, and reporting needs; translate into epics/user stories, acceptance criteria, and beta vs. post-beta backlog for the 3 year delivery plan. |
| Grant Program Interface Platform | 2.1 | System Design & Development | 2.1.02 | Architecture refinement for Grant Interface Platform (microservices + data stores) | Solution Architect; Cloud Architect; Backend Engineer | 260 | Refine target architecture for grant application + incentive workflow services (application intake, document handling, review workflow, payment status, notifications) aligned to overall platform patterns; define service boundaries, integration contracts, and data ownership. |
| Grant Program Interface Platform | 2.1 | System Design & Development | 2.1.03 | UX research + accessibility baseline | UX/UI Designer; Product Manager | 210 | Design research interviews + journey mapping for producer, ASP, reviewer, and admin personas; produce accessibility-informed IA/navigation patterns (WCAG-oriented) and establish design system components for consistent grant workflows. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .