• Provide a secure, cloud-based mature COTS platform to replace/improve WeRemember.ABMC.gov.
• Support both a public-facing research portal and an internal records/case-management capability.
• Manage structured/unstructured data, with attachments (documents/images/media) and likely OCR support.
• Deliver robust search (facets, fuzzy, relevance tuning) and responsive performance.
• Enforce role-based access control, auditing, and vulnerability management in a federal environment.
• Enable ABMC staff to administer metadata, forms, branding, workflows, roles, and configurations to minimize contractor dependence.
• Provide reporting and export functions (e.g., Excel/CSV).
• Offer secure APIs (RESTful/OAI-PMH or equivalent), bulk ingestion, synchronization, authentication, logging, and rate limits.
• Integrate or interoperate with external systems, with explicit interest in VA’s Veterans Legacy Memorial (vlm.cem.va.gov).
• Migrate/ingest data from Knowvation’s Microsoft SQL, normalize metadata, resolve discrepancies, link records, and preserve audit history.
• Meet Section 508 accessibility and other federal usability/security requirements for public sites.
• Define implementation and support models: discovery, prototyping, migration, testing, training, cutover, help desk, SLAs, upgrades.
• Provide ROM pricing for licensing, implementation, migration, training, and O&M with cost drivers/assumptions.

• Domain fit: requirement centers on a mature COTS records/memorialization platform, not a Trace core area.
• Competitive pressure from specialized records/CMS vendors with stronger references.
• Data migration complexity from Knowvation SQL including metadata normalization and audit history preservation.
• Public-facing accessibility/usability (Section 508) and performance expectations.
• Integration uncertainty with external systems (e.g., VLM) and need for secure, well-documented APIs.
• Unknown acquisition path and evaluation criteria (Draft SOO/evaluation not provided here), adding capture uncertainty.

• COTS records/CMS platform OEM with proven federal/public-sector deployments and strong search/records workflows.
• Specialist data migration partner with Knowvation/MSSQL export experience and metadata normalization expertise.
• Accessibility/UX specialist for Section 508-compliant public portals and content design.
• Integration engineer(s) with experience integrating with VA’s VLM or similar memorialization/archival systems via secure APIs.
• FedRAMP-authorized hosting/cloud operations partner if ABMC requires FedRAMP-equivalent controls.
• Managed support/Help Desk with SLAs tailored to public portal uptime and content administration.

• Offer a proven COTS platform partner with configurable records workflows, advanced search, and staff-admin capabilities to reduce vendor lock-in.
• De-risk migration with a structured data profiling/cleansing and bulk ingestion approach preserving lineage and audit history.
• Demonstrate secure API integration patterns for external systems (e.g., VLM) with throttling, auditing, and standardized data exchange.
• Provide an O&M model with clear SLAs, 24/7 monitoring, vulnerability management, and seamless upgrades to ensure long-term stability.

• RFI stage only; no commitment to a solicitation or acquisition approach.
• Referenced Draft SOO and evaluation documents are not included here, limiting clarity on requirements and criteria.
• Requirement is centered on a mature COTS records/CMS solution—Trace does not list such a product in its core capabilities.
• Crowded market of specialized vendors likely to out-position a general integrator without a strong OEM partner.

No human notes yet.