36C10D26Q0139 0003.docx

DOCX document 17 KB Posted

Attached to
R408--MAIL MANAGEMENT SERVICES ANSWERING VENDOR QUESTIONS
Solicitation number
36C10D26Q0139
Issued by

About this file

This file is a Questions and Answers document addressing vendor inquiries regarding a Mail Management Services contract modification (Solicitation Number 36C10D26Q0139) issued by the Department of Veterans Affairs Veterans Benefits Administration Acquisition Directorate. The response date for submissions is July 21, 2026, at 3:00 PM Eastern Time, with archival 99 days after the response date. The contract falls under Product Service Code R408 (Mail Management Services) and NAICS Code 518210.

The Q&A clarifies operational and technical requirements for mail processing services handling an estimated 46,000 mail packets and 1 million images per day. Key operational parameters include a 12-hour turnaround time (6:00 AM to 6:00 PM EST) for routing mail packets to the Digitized Mail Handling Service, with average monthly volumes of 70,000 returned mail packets that require envelope opening and scanning. The contractor must provide and maintain a FedRAMP Authorized helpdesk ticketing tool (ServiceNow, Jira Service Management, or Microsoft Azure DevOps are approved examples), develop the DMHS service, and handle indexing of documents with standard metadata fields including veteran name, file number, document type, and date of receipt. Government-furnished equipment includes storage boxes from the Records Management Services vendor, postage reimbursement for unscannable mail returns, and potential cloud-based LLM services through approved GovCloud providers. The contractor is responsible for verifying GovCloud model availability, ensuring security compliance, and assuming risk for CSP model availability changes. No physical restoration of original mail binding (re-stapling, re-clipping, or re-binding) is required; loose bundling within original envelopes is sufficient.

View the file

Other files

File Type Posted
36C10D26Q0139 0005.docx DOCX document
36C10D26Q0139 0004.docx DOCX document
36C10D26Q0139 0002.docx DOCX document
36C10D26Q0139 0001.docx DOCX document
36C10D26Q0139.docx DOCX document
Mail Management Services PWS 6-22-26 - Updated.docx DOCX document

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

Modification to a Previous Notice Modification to a Previous Notice

SUBJECT*
MAIL MANAGEMENT SERVICES ANSWERING VENDOR QUESTIONS

GENERAL INFORMATION

CONTRACTING OFFICE’S ZIP CODE*
20006
SOLICITATION NUMBER*
36C10D26Q0139

BASE NOTICE TYPE

RESPONSE DATE/TIME/ZONE
07-21-2026 3PM EASTERN TIME, NEW YORK, USA
ARCHIVE
99 DAYS AFTER THE RESPONSE DATE
RECOVERY ACT FUNDS
N

SET-ASIDE

PRODUCT SERVICE CODE*
R408
NAICS CODE*
518210
CONTRACTING OFFICE ADDRESS
Department of Veterans Affairs

Veterans Benefits Administration Acquisition Directorate 1800 G Street NW Washington DC 20006

POINT OF CONTACT*

Contract Specialist Gregory Stevens gregory.stevens@va.gov 313-354-2194

PLACE OF PERFORMANCE

ADDRESS
Department of Veterans Affairs

Veterans Benefits Administration

Acquisition Division

1800 G Street NW

Washington DC

POSTAL CODE
20006
COUNTRY
US

ADDITIONAL INFORMATION

AGENCY’S URL

URL DESCRIPTION

AGENCY CONTACT’S EMAIL ADDRESS
gregory.stevens@va.gov

EMAIL DESCRIPTION

DESCRIPTION

Q1.What is the estimated average number of mail packets processed per day?
A1.Estimated average 46,000 packets per day (digital and paper).
Q2.What is the estimated average number of pages processed per day?
A2.Estimated average 1M images per day (digital and paper).
Q3.Will cloud-based LLM providers be part of the GFE?
A3.Cloud-based LLM services may be available through VAEC's approved Cloud Service Providers (CSPs) as part of the GFE infrastructure; however, model availability is determined solely by the CSP and not VA, and any LLM proposed by the Contractor must be available within an approved GovCloud region (e.g., AWS us-gov-east-1 or us-gov-west-1), receive written COR approval prior to use, and be a submitted AI use case to the OIT Chief AI Officer (CAIO). Contractors are responsible for independently verifying GovCloud model availability, ensuring compliance with all VA security requirements, and assuming all risk associated with model availability changes made by the CSP during the period of performance.
Q4.Will the vendor need to provide the ticketing tool, or is there an existing VA ticketing tool? If a vendor is provided, is there a list of approved tools?
A4.The Contractor is responsible for providing, funding and maintaining their own VA-approved helpdesk ticketing tool. The proposed tool must operate within a FedRAMP Authorized boundary, provide VA personnel with read access to all tickets and reporting. Some examples:
•ServiceNow (FedRAMP Authorized)
•Jira Service Management / Jira Cloud (FedRAMP Authorized)
•Microsoft Azure DevOps / GitHub Issues (FedRAMP Authorized)
Q5.Section 5.8 discusses post-conversion de-preparation. To what extent must the physical paper mail be restored to its original state? Specifically, are mailroom operators required to physically re-staple, re-clip, or re-bind documents that were separated for scanning, or is it sufficient to keep grouped documents loosely bundled together inside their original mail packet envelopes?
A5.No, they do not have to re-staple, re-clip or re-bind documents. They should be grouped together so they can easily be recalled in the future and clearly identify which documents were part of the same submission.
Q6.Section 5.4.5 states that the contractor must make a reasonable effort to return all unscannable mail to the sender. How will shipping and return postage costs for these items be handled? Will the Government reimburse these postage costs directly as pass-through operational expenses, or must they be fully accounted for within the contractor's firm-fixed-price (FFP) labor rates?
A6.VA will provide a postage account or reimburse the contractor for shipping of unscannable mail.
Q7.Section 5.10 states that physical paper documents must be stored in boxes before shipment to the RMS long-term storage facility, utilizing NSN 8115-00-117-8249 boxes. Will these storage boxes be provided by the Government or the RMS vendor as Government Furnished Equipment (GFE), or is the contractor responsible for purchasing and maintaining an inventory of these specific boxes?
A7.The RMS vendor will provide boxes.
Q8.To assist in scaling and training the indexing team, can the Government provide a complete list of the unique form numbers and document types that the mailroom is expected to encounter and index? Please clarify if there are custom indexing or metadata fields required for specific forms, or if the four standard index values (Veteran name, file number, document type, and date of receipt) apply uniformly.
A8.There are 1,000+ commonly received source material items. Specific processing rules would be provided with a formal solicitation.
Q9.The Q&A identifies 'returned mail' (undeliverable VA outbound letters) as a frequently received item. Could the Government provide the estimated daily or monthly volumes for returned mail? Furthermore, what are the specific operational processing steps required—are envelopes required to be opened and scanned, or should they only be indexed and routed via envelope-level barcodes?
A9.On average, we receive around 70,000 packets of return mail per month. This can vary widely across months when bulk mailers are sent. Envelopes are opened and scanned. Rules based upon type of returned mail.
Q10.What are the expected daily operating hours for physical mail receipt and check-in? Section 5.13.3 defines a six-hour turnaround time (TAT) SLA for routing mail packets to the Digitized Mail Handling Service (DMHS). Please clarify if this six-hour window runs continuously after normal business hours (requiring 24/7/365 staffing) or if it pauses at the close of the daily mailroom operations and resumes the next business morning.
A10.TAT runs based upon a 12-hour period, 6am to 6pm EST.
Q11.For submissions received via the Direct Upload Service, does the metadata captured at upload include the required indexing values (document type, date of receipt)? Is the Contractor required to perform or validate indexing on direct-upload submissions, or is uploader-supplied metadata authoritative? Where document type is not supplied, is the Contractor responsible for classifying those submissions?
A11.Contractor is responsible for indexing.
*= Required Field
Modification to a Previous Notice

Modification to a Previous Notice

File details come from the government source that posted it. Updated .