36C10B19R0009-0001005.docx

DOCX document 29 KB Posted

Attached to
TAC 19-53538 Enterprise Telecommunications Expense Management software platform Federal contract opportunity
Solicitation number
36C10B19R0009
Issued by
Department of Veterans Affairs Technology Acquisition Center Austin

About this file

36C10B19R0009 0001 Attachment eTEMS RFP Questions and Answers 38 and 39.docx

View the file

Other files for this federal contract opportunity

Other files attached to TAC 19-53538 Enterprise Telecommunications Expense Management software platform, newest first.
File Type Posted
36C10B19R0009-0006005.docx DOCX document
36C10B19R0009-0006004.docx DOCX document
36C10B19R0009-0006005.docx DOCX document
36C10B19R0009-0006004.docx DOCX document
36C10B19R0009-0001008.docx DOCX document
36C10B19R0009-0001008.docx DOCX document
36C10B19R0009-0001007.docx DOCX document
36C10B19R0009-0001006.docx DOCX document
36C10B19R0009-0001007.docx DOCX document
36C10B19R0009-0001006.docx DOCX document
36C10B19R0009-0001004.docx DOCX document
36C10B19R0009-0001005.docx DOCX document
36C10B19R0009-0001004.docx DOCX document
36C10B19R0009-0001003.docx DOCX document
36C10B19R0009-0001002.docx DOCX document
36C10B19R0009-0001003.docx DOCX document
36C10B19R0009-0001002.docx DOCX document
36C10B19R0009-0001000.docx DOCX document
36C10B19R0009-0001001.docx DOCX document
36C10B19R0009-0001001.docx DOCX document
36C10B19R0009-0001000.docx DOCX document
36C10B19R0009-002.docx DOCX document
36C10B19R0009-001.docx DOCX document
36C10B19R0009-003.xlsx XLSX spreadsheet
36C10B19R0009-004.pdf PDF
36C10B19R0009-004.pdf PDF
36C10B19R0009-002.docx DOCX document
36C10B19R0009-001.docx DOCX document
36C10B19R0009-003.xlsx XLSX spreadsheet
Show all 29

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Q &A 38 and 39

38.
5.2.1.4
78-79
Billing disputes
Is it a requirement to provide automated adjudication of errors identified and, if so, are the rules either identified in the solicitation and if not, can they be made available?
Per PWS Pages 78 & 79, Section 5.2.1.4, “The Contractor shall include functionality for carrier billing dispute creation tracking and management.” And 5.2.1.4b., “The eTEMS shall flag and provide an automated notification to VA for all invoices with variances and prepare disputes to carriers to be executed by VA personnel. The disputes shall be trackable and reportable within the eTEMS.”
39.
5.2.2.2
85
E-Bonding
It concerns us that only 3 of the EIS vendors have ATO’s at this time and may not be able to provide eBonding. If a particular carrier does not support eBonding, how does the VA envision these exceptions will be addressed and intend to ensure that the carriers will comply? Will the contractor be expected to work with the carrier to resolve any eBonding related issues?
Per PWS Page 85, Section 5.2.2.2, “eBonding [also] refers to the business-to-business (B2B) software interface that automates the data exchange between two business applications, reducing the amount of manual intervention that's usually required. To support this implementation, the Contractor shall furnish an E-Bonding integration framework capability, utilizing open industry standards and interfaces to facilitate bidirectional automated B2B type transactions.”

File details come from the government source that posted it.