Scout

74330226R0044

ABMC Human Resources Information System

AMERICAN BATTLE MONUMENTS COMMISSION > AMERICAN BATTLE MONUMENTS COMMISSION > ABMC

New Rejected
Actions
Open SAM.gov
Notice Type Combined Synopsis/Solicitation
Due 2026-05-29
Posted 2026-04-21
NAICS 541519
PSC DA10
Set-aside None listed
Scout Score 20

Quick analysis

ABMC seeks a COTS/configurable Human Resources Information System (HRIS) with multi‑country scope and integration to a separate global payroll provider (solicitation 74330226R0045).

Requirements emphasize HR functionality (core HR, performance, compensation, recruiting, time & attendance), heavy security/compliance (NIST 800‑53, 800‑63‑4, MFA, RBAC/ABAC, encryption), privacy/GDPR and data residency controls, Section 508, auditability, SLAs (99.9% uptime), DR (RTO/RPO), and export/portability.

RFP requests three similar references and may require product demonstrations—strong signal this is a COTS HRIS competition with experienced HRIS OEMs/implementers.

Trace’s documented core strengths (SATCOM/LEO, CDS/NSA TI, MPE/coalition C2, tactical edge, C5ISR, enterprise IT O&M) do not include HRIS product ownership or HRIS implementation past performance. No relevant ABMC or HRIS references are listed in the company profile.','Access is full & open via email submission (no vehicle barrier). Place of performance lists Paris, France (global/OCONUS context).

Scope summary

  • Provide a Human Resources Information System (HRIS) covering core HR, performance, compensation, recruiting, time & attendance/leave, org charts, reporting (PWS, Questions Matrix).
  • Integrate employee data with a separately awarded global payroll provider (ref RFP 74330226R0045) and align to ITS.gov payment file constraints (Attachment 3).
  • Support multi‑country workforce (~575 total; majority OCONUS; many without computer access; timekeeper proxy capability) and multilingual training (PWS).
  • Meet security/compliance: MFA; RBAC/ABAC; least privilege/SoD; encryption in transit/at rest; centralized logging/audits; vulnerability mgmt; SBOM/VDP; NIST SP 800‑53 rev5 alignment; NIST SP 800‑63‑4 for identity; Zero Trust, federation (PWS, Questions Matrix).
  • Privacy and data residency: GDPR/Privacy Act, minimize/cross‑border controls, field‑level visibility, retention/disposition/legal hold, export in non‑proprietary formats (PWS).
  • Hosting/continuity: If cloud, FedRAMP; define RTO/RPO; 99.9% availability target; DR; environment segregation; masking for non‑prod (PWS, Questions Matrix).
  • Accessibility: Section 508 conformance and accessibility testing (PWS, Questions Matrix).
  • Provide three similar references; be prepared for product demonstrations (RFP Instructions).
  • Contract structure: base year + four option years; primarily FFP; proposals due 29 May 2026 (RFP Instructions).

Dimension scores

Total - 20/100
Technical Fit - 3/20

Requirement is a COTS/configurable HRIS with multi‑country payroll integration and extensive HR functionality. Trace’s profile lists enterprise IT O&M and integrations but no HRIS product or implementation capability; this sits outside core lanes (PWS, Questions Matrix, RFP Instructions).

Past Performance - 3/20

No ABMC or HRIS implementation past performance in the company profile. RFP requires three similar references (RFP Instructions), which we do not evidence. New customer and new mission area.

Vehicles / Contract Access - 6/10

Full & open email submission; not restricted to a vehicle. No vehicle advantage for Trace, but no access barrier either (RFP Instructions).

Competitive Position - 1/15

Competition favors established HRIS OEMs and experienced implementers; demos and three similar references are expected (RFP Instructions, Questions Matrix). Without an HRIS product or references, Trace is an underdog.

Risk - 3/15

High execution/compliance risk without an HRIS OEM partner: FedRAMP (if cloud), GDPR/data residency, Section 508, NIST 800‑53/63‑4, OCONUS workforce/timekeeping by proxy, dependency on separate payroll vendor and ITS.gov formats (PWS, Questions Matrix, Attachment 3).

Strategic Value - 1/10

ABMC is outside Trace’s Tier 1 targets and the HRIS lane is not strategic per company profile. Limited upside beyond this contract.

Compliance - 3/10

Set‑aside: none. However, compliance expectations include FedRAMP (if cloud-hosted), Section 508, GDPR/data residency, NIST controls, SBOM/VDP (PWS, Questions Matrix). Trace lacks a FedRAMP‑authorized HRIS or documented HRIS compliance posture—significant gaps without teaming.

Concerns

  • Lack of HRIS OEM product/partnership makes us non‑competitive against COTS vendors expecting demos and references (RFP Instructions).
  • Compliance bar (FedRAMP if cloud, GDPR/data residency, Section 508, NIST controls) is substantial for HR data; unmet without a qualified HRIS platform (PWS, Questions Matrix).
  • Integration dependency with a separate payroll provider and strict ITS.gov payment file formats adds complexity and schedule risk (Attachment 3, RFP Instructions).
  • OCONUS operations, limited employee computer access, and multilingual training requirements increase rollout and change‑management risk (PWS).
  • Evaluation weighting on past performance may be disqualifying without three similar HRIS references (RFP Instructions).

Teaming opportunities

  • HRIS OEM partner (e.g., enterprise HRIS platform with multi‑country capability) with FedRAMP authorization or clear path if cloud-hosted.
  • Experienced HRIS implementer/integrator with multi‑country public sector/GDPR experience and references.
  • Data privacy/legal (GDPR) and Section 508 accessibility testing expertise.
  • Integration specialists for payroll interfaces and ITS.gov file generation/validation; API/ETL engineers.
  • Change management and multilingual training delivery for OCONUS workforce.

Competitive position

  • If teamed with a FedRAMP‑authorized HRIS OEM: emphasize security/compliance rigor (NIST alignment, Zero Trust), auditability, and data residency controls requested by ABMC.
  • Leverage Trace’s global OCONUS support and managed services experience to support rollout, training, and steady‑state operations across ABMC sites.
  • Integration strength: demonstrate robust interface monitoring/reconciliation and adherence to ITS.gov payment specs and Treasury controls.

Bid/No bid factors

  • COTS HRIS competition with expected product demos and requirement for three similar references—Trace lacks HRIS references (RFP Instructions).
  • FedRAMP expectation for cloud‑hosted HRIS; no Trace HRIS platform is documented (Questions Matrix).
  • GDPR/data residency and OCONUS execution complexity outside Trace’s core lanes (PWS).

Documents

Download all
743302226R0044 Attachment 3 Payroll ITS File Specifications.pdf Download
Summary

Machine-readable specification for payroll/payment file exchange with ITS (header, wire payment detail, and trailer records). Defines exact field layouts, validation rules, and required fields for domestic and foreign wire payments including TAS/BETC handling and record-count/totals in the trailer. Useful for technical integration work (file-generation, ETL, payment processing) rather than higher-level HRIS functional requirements.

  • Specifies file naming convention: XXMMDDYY.001 and matching current date validation (File Name, Current Date).
  • Header, wire payment detail, and trailer records with strict field positions and lengths (positional/flat-file format).
  • Wire payment fields include FXR indicator, :ALC: (Agency ALC), :SCHEDULE:, :30 VALUE DATE: which must be two business days from file date (YYMMDD).
  • Amount fields defined: :BASE AMT: and :FX AMT: require USD or 3-letter currency codes and decimals.
  • Bank/payment routing detail requirements: SWIFT address (:57D PAY THRU: 8 or 11 chars), bank name/address, beneficiary account/name/address up to 34–35 chars.
  • Special note: some foreign currencies require additional bank details populated in :72 RECEIVER INFO / BANK DETAILS fields.
  • TAS / BETC fields (lines 32–41) can repeat up to 100 times per payment to satisfy agency TAS/BETC needs — implies granular funding accounting per payment.
  • Trailer requires record count and file total USD (no punctuation), enforcing reconciliation controls.
  • Validation rules: many fields cause file rejection if missing/invalid (e.g., File Name, Current Date, :ALC:, key amount fields).
  • Document implies integration needs for payroll/payment processing, Treasury/financial compliance, and holiday/business-day logic for value dates.
74330226R0044 Attachment 1 HRIS PWS.pdf Download

Partially reviewed: Too large

Summary

Partial extract (sections 1 and 6) of the Performance Work Statement for ABMC solicitation 74330226R0044 describing a Human Resources Information System (HRIS). The document provides agency background and headcount by country, high-level objectives and scope (core HR, performance, compensation, recruitment, time & attendance, training, integration), a target go-live of January 2027, and detailed security, privacy, records, hosting, and performance requirements.

  • Agency: American Battle Monuments Commission (ABMC); PWS for HRIS solicitation 74330226R0044.
  • Workforce scope: ~575 full-time civilian employees (≈90 US citizens) and ~420 permanent + 50 temporary/seasonal foreign national employees across overseas sites; Appendix I lists country populations (France ~300 down to Mexico 2).
  • Geography / covered sites: Overseas office in Paris; installations in 10–11 countries (document references six European countries plus Tunisia, Philippines, Panama, Mexico; scope statement references 11 countries—flag for clarifying Appendix I).
  • Integration: HRIS must integrate with a separately awarded multi-country payroll contract (solicitation 74330226R0045); US citizen payroll explicitly excluded.
  • User constraints: Majority of employees lack computer access—system must support timekeepers managing timecards/time & attendance on behalf of other employees.
  • Required modules / functionality: Core HR, performance management, compensation, recruitment, time & attendance and leave management, organisational charts and reporting, configurable workflows, custom fields (e.g., exchange-rate at payroll disbursement), training in required languages, integration with agency service management.
  • Timeline: Agency goal to select provider for go‑live by January 2027 (selection/timeline to be agreed with payroll supplier).
  • Security & compliance requirements: Data sovereignty controls, controls on cross-border access/replication, role-based & attribute-aware access control, MFA, least privilege/SoD enforcement, encryption in transit & at rest, centralized logging/audit trails, vulnerability scanning/patch management, SBOM request, vulnerability disclosure policy, NIST SP 800-63-4 reference for identity, NIST SP 800-53 rev5 baseline question.
  • Zero Trust & federation: System should support Zero Trust model, modern federation, conditional access, segmentation, and tenant isolation.
  • Privacy & records: GDPR/Privacy Act handling, data minimization, field-level visibility restrictions, retention/ disposition/legal hold capability, exportability to non-proprietary formats, portability for transition.
  • Hosting / cloud: FedRAMP asked if cloud-hosted; shared-responsibility model; disaster recovery objectives and contractual RTO/RPO; question about where HR data, backups, and logs are physically stored.
  • Operational & performance SLAs: 99.9% production availability target (excluding maintenance), defined RTO/RPO and response-time targets, batch processing windows, monitoring for interface failures and transaction reconciliation.
  • Auditability: Full audit trails for payroll transactions (who/when/what changes), tamper-resistant/exportable logs.
  • Accessibility: Must conform to Section 508 (keyboard, assistive tech, color contrast, accessible documents), including accessibility testing.
  • Environment controls: Segregation of dev/test/prod, rules for copying production data to non-prod (masking/anonymization and approval process).
  • Training & sustainment: Live training for Administrators, Managers, and Users in required languages and steady-state operations included in scope.
  • Document review limitation: extraction is partial (sections 1 and 6 of 10 selected) due to file size; Appendix I, II, III and other sections not reviewed in this extract.
74330226R0044 Attachment 2 Questions Matrix.xlsx Download

Partially reviewed: Too large

Summary

Vendor questionnaire (Attachment 2 Questions Matrix) for the ABMC HRIS procurement. Review was partial (selected sections: section_1_of_8 and section_5_of_8) from a much larger workbook; the extracted sections show detailed functional HR requirements (organizational charts, compensation, absence management) and technical/security requirements (upgrade/testing, APIs, data residency, encryption, FedRAMP/NIST, Zero Trust, records management, accessibility).

  • Document type: vendor questions matrix — buyer expects written responses explaining functionality, integrations, and controls (COTS or configurable HRIS solutions are targeted).
  • Functional scope: detailed Human Capital Management requirements including organizational charting, reorganization handling, hierarchical history, workforce reporting, compensation features (salary history, bulk changes, country-specific pay rules), absence management and leave accrual rules.
  • Scale/operations: questions about mass reorganizations, international company limits, creation time for new cost centers/divisions, and supervisor self-service printing of org charts indicate multi-entity, multi-country support is required.
  • Integration requirements: requests for supported data feeds, APIs/secure batch interfaces to payroll, identity management, time & attendance, and third-party payroll vendors — interoperability is mandatory.
  • Security/compliance asks: multi-factor authentication, role-based/attribute-aware access control, least privilege and separation of duties, encryption in transit and at rest, centralized logging/audit trails, privileged access monitoring, and session controls.
  • Standards and baselines: explicit asks about FedRAMP certification (cloud-hosted), NIST SP 800-53 rev5 alignment, and NIST SP 800-63-4 for identity/authentication — indicates high federal security bar and likely cloud-hosting expectations.
  • Software supply chain and vulnerability posture: requests for Software Bill of Materials (SBOM), vulnerability disclosure policy/timeline, and patch/vulnerability scanning cadence.
  • Data residency & privacy: questions on physical storage location for HR data/backups/logs, controls for cross-border access and replication, data minimization, purpose limitation, and handling of privacy/GDPR/Privacy Act requests.
  • Environment & operations: asks about sandbox/testing environment, upgrade process and impact on personalization, costs for new versions/maintenance, and whether production data can be copied to non-prod with masking — indicates need for mature Dev/Test/Prod segregation practices.
  • Records management & portability: retention policies for payroll records, designation of official record copies, metadata preservation, legal hold, export in non-proprietary formats, auditability of record changes and support for transition to new platforms.
  • Accessibility & continuity: explicit Section 508 conformance question and backup/recovery/RTO-RPO options — buyer expects accessibility and continuity planning.
  • Procurement signal: comprehensive questionnaire suggests a formal RFP/competitive procurement seeking a fully-featured HRIS with strong security/compliance and multi-country capabilities.
74330226R0044 RFP Instructions.pdf Download
Summary

ABMC RFP instructions for a Human Resources Information System (HRIS) dated 21 Apr 2026. Document defines submission instructions, evaluation criteria, period of performance (base + 4 option years), intended contract type, integration requirement with ABMCs global payroll provider, and lists attachments (PWS, questions checklist, ITS file format).

  • Requirement: Human Resources Information System (HRIS) for ABMC (see attached PWS).
  • Must integrate employee data with ABMCs global payroll provider; references separate solicitation 74330226R0045 for payroll details.
  • Intended contract type: predominantly firm-fixed-price, but other contract types allowed.
  • Period of performance: 1 base year plus 4 option years.
  • Submission deadline: proposals via email to nerenga@abmc.gov by 29 May 2026, 4:00 pm EDT (given due date/timezone).
  • Question due date: 5 May 2026.
  • Product demonstrations: may be requested after proposal receipt at ABMCs discretion.
  • Proposal components required: Cover letter (must include RFP number, offeror contact, CAGE/UID if applicable), Technical Volume (exec summary, company profile, detailed scope response, 3 similar references, implementation timeline, SLA terms), Price sheet (currency flexible; include setup, licensing, ongoing support for base + 4 option years).
  • Pricing note: ABMC is exempt from taxes/VAT; copies of tax exemption agreements available on request (affects pricing).
  • Evaluation criteria (best-value): 1) Past performance; 2) Technical (capability, human capital mgmt functionality, compliance, management/implementation plan including key personnel, risk/QC/change mgmt, schedule, UI, customer support, data protection/legal compliance); 3) Price (cost-effectiveness & clarity).
  • Attachments listed: Attachment 1 - PWS; Attachment 2 - Questions Matrix Checklist; Attachment 3 - ITS Standard File Format.
  • Contracting officer contact: Anna Nereng (nerenga@abmc.gov).
ABMC Contracting Opportunities Open link

Restricted: Unreadable

Summary

Document could not be reviewed because access is restricted or controlled. Analysis continues using other available evidence.

Links.txt Unavailable

No current live SAM.gov attachment matches this stored row.

Summary

Contains a single authoritative link to the ABMC contracting opportunities page for RFP 74330226R0044 titled 'Human Resources Information System'. The file itself has no solicitation text—follow the URL to retrieve the full RFP and attachments needed for scoring.

  • URL: https://www.abmc.gov/rfp/74330226r0044-human-resources-information-system/
  • References RFP number 74330226R0044 and title 'Human Resources Information System' on ABMC site
  • Host is ABMC Contracting Opportunities page (official agency source)
  • This file contains no procurement details (scope, set-aside, PO/vehicle, due date, place of performance, clearances, incumbent, or attachments)
  • Action required: visit URL to extract full solicitation, requirements, and attachments for later Trace scoring
Technical details

Entry: sync

Review status: Up to date

Logical upstream opportunity: 46189

Notice lineage:

  • 84ff3092412746db9bd24b66393e6c67 (posted 2026-04-21) - current

Last synced: 2026-04-21T18:32:20.225345+00:00

Last analyzed: 2026-04-21T18:35:09.039126+00:00

Latest package fingerprint: a895c6f4b9668598d3a04c3c40ae496fffdd8ed5a1b894bc6d9d8aa6bb1c3e25

Latest package notice: 84ff3092412746db9bd24b66393e6c67

Latest package documents: 6

Evidence limitations
  • 74330226R0044 Attachment 1 HRIS PWS.pdf: partially reviewed (too large)
  • 74330226R0044 Attachment 2 Questions Matrix.xlsx: partially reviewed (too large)
  • ABMC Contracting Opportunities: restricted (unreadable)
  • Only partial document evidence was available from the upstream package.
Recent package history
  • 2026-04-21T18:32:20.227498+00:00: 84ff3092412746db9bd24b66393e6c67 with 6 docs

Labels

Human notes

No human notes yet.

Qualification Settings

Included notice types

Scope Filters

Use one code or phrase per line, or comma-separate.

System Settings

Runtime

Custom Search

Search time

These filters apply only to this run. Qualification settings stay unchanged.

Custom Search queries Fetchmesh and stores the results in Scout without mutating the default sync configuration.

Workspace visibility

All custom searches are public for now.

Included notice types

Scope Filters

Use one code or phrase per line, or comma-separate.

Browse Searches