1 / 23

ECP 811 for Telecom

ECP 811 for Telecom. Part 1. General Information. Title of Change Request: EDI 811 for Telecom Presented By (Agency/Submitter Name): Marine Corps/Defense Finance and Accounting Service Technical POCs: David Cartwright, DFAS 614-693-6510 david.cartwright@dfas.mil

keefer
Download Presentation

ECP 811 for Telecom

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ECP 811 for Telecom

  2. Part 1

  3. General Information • Title of Change Request: • EDI 811 for Telecom • Presented By (Agency/Submitter Name): • Marine Corps/Defense Finance and Accounting Service • Technical POCs: • David Cartwright, DFAS 614-693-6510 david.cartwright@dfas.mil • Mark Edmunds, DFAS 703-607-3813 mark.edmunds.ctr@dfas.mil • Functional POC: • Cathey Capozziello, USMC 918-361-0840 ccapozziello@caci.com • Principal Staff Assistant:

  4. Problem Description • What business problem exists, and what are the effects of this problem? Telecommunication invoices, whether for telephony charges or otherwise, are significantly different than any other type of existing WAWF accepted invoice. The Telecommunications Industry Standard for EDI is the 811, which WAWF does not currently accept. Most of the telco’s have refused to use WAWF and thus represent a large segment of today’s remaining DoD manual workload.

  5. Solution/Requirement • Provide a description of the solution Since the Telecommunications Industry Standard is the 811, not the 810 or 857, this ECP seeks to develop an inbound 811 to capture the telecommunications invoices. ECP 452 seeks to pilot the non-DITCO relatedUSMC contractual and non-contractual invoices, paid via CAPSW.

  6. Benefits • Summarize the benefits of the capabilities achieved by this ECP: The telco invoices are one of the last major communities of non-WAWFable invoices. Once they are WAWFable, we will realize significant savings in decreased interest, late fees and DFAS processing costs. These savings are in addition to the benefits of increased visibility and accountability of the telco invoices in general.

  7. Risks and Impacts • Summarize the risks and impacts of the capabilities achieved by this ECP: The industry does not currently capture key data elements within their billing systems, such as contract number, CAGE or DoDAACs. Their billing systems require restructuring to capture those elements, and for CLIN invoicing as well. Finally, even within the Telecommunications Industry Standards, there are multiple variations of the 811. Despite this, the industry is consistently requesting WAWF provide an 811 capability and they are currently evaluating how to modify their systems to capture the DoD requirements. AT&T Govt Solutions has volunteered to participate in the pilot and represent the industry.

  8. Link To Mission • How does this relate to the enterprise business plan? Please see U.S. Department of Defense Enterprise Transition Plan, 28 September, 2006: Appendix E, Table MV-E4-1, entry MV5 “Transform the Department’s supply chain information environment by: 1) improving data integrity and visibility by defining, managing, and utilizing item, customer, and vendor master data; and 2) reducing complexity and minimizing variability on the supply chain business transactions by adopting standardized transaction and business rules.”

  9. New Functionality/Enhancements • Does this ECP achieve new functionality, or is it an enhancement? • Is this ECP replacing existing capabilities? • Will this new functionality or enhancement require training for end users? If yes, please explain This is new functionality. Currently, EDI 811’s must be transmitted manually. This ECP would replace the manual process with an electronic process. No Vendors will initially require assistance transmitting 811s through GEX and how to use WAWF. Any telecom related government officials not currently using WAWF will require training. Update WAWF with EDI/FTP guide for inbound 811 transactions. Add detailed guidance for accepting telecom invoices within WAWF to the Software Users Manual (SUM). Add detailed training to the WAWF web-based training program. Add training scenarios to the WAWF training database.

  10. System Impacts • Is this ECP to satisfy a system failure issue? • Is this ECP to satisfy a system security issue? • Does this ECP address a data integrity issue? No No As with all WAWF invoices, by creating the Telecom invoices electronically, the chances of keying incorrect data decreases and the accountability and tracking of data increases.

  11. Alternatives • Could this problem be solved by changing your business process? While most telco contracts contain the WAWF invoicing instructions, a significant percentage of invoices remain manual. The industry has consistently asserted an inability to submit without the 811, due to the magnitude of the call detail associated with telephony invoices. The DFAR has forced many telcos to comply in spite of their obstacles, however non-contractual telco invoices do not have the same leverage. As a comprehensive solution, ECP 452 seeks remove these obstacles for a 100% WAWF solution.

  12. Part 2

  13. Data Elements • Are there any data elements being created, modified, or deleted? In addition to the data elements captured today within various WAWF documents, the telco invoices will also capture the complete call detail provided by the telco. This information is necessary for the government to ensure proper usage and billing, and is required to perform acceptance. Lastly, only the Acceptor DoDAAC will be mandatory at the vendor stage. All other DoDAACs will be added at the Acceptor stage. For contract invoices, a crosswalk to EDA will populate the captured DoDAACs as well.

  14. Dependencies • Is the ECP related to any other ECP(s)? • Is this ECP form dependent on any other business partner or component level milestone(s)? This ECP pilots the telco functionality. A follow-on ECP is anticipated for DITCO and non-CAPSW telco invoices. AT&T Government Solutions has agreed to partner with us on this pilot to ensure a complete end to end solution.

  15. Dependencies Cont. • Is this ECP dependant on any other resources? • Are there any related IRB assertions associated with this ECP? No No

  16. BEA • Is this requirement necessary to reach BEA compliance? • Is this requirement in compliance with the BEA process flow capabilities and business rules? No Yes

  17. Users Affected • What Components are affected by this change? • Will this requirement result in a volume increase in users or transactions? Initially, USMC and DFAS as the pilot. The Enterprise Solution will follow the pilot. Yes. Roughly 12,000 invoices annually for USMC alone. Overall potential DoD volume is significant.

  18. Strategy • Is this requirement part of the DoD strategy in the Enterprise Transition Plan? Yes. In accordance with the U.S. Department of Defense Enterprise Transition Plan, 28 September, 2006: Appendix E, Table MV-E4-1, entry MV5, ECP 452 seeks to “Transform the Department’s supply chain information environment by: 1) improving data integrity and visibility by defining, managing, and utilizing item, customer, and vendor master data; and 2) reducing complexity and minimizing variability on the supply chain business transactions by adopting standardized transaction and business rules.”

  19. Preclusions • Are there any other systems that could be changed that would preclude the need for this requirement? • Are there any policy changes that would preclude the need for this requirement? No No

  20. LRPs • Are there any Federal of DoD level statutes, regulations, or policy mandates requiring the implementation of this requirement? Yes. DFAR 252.232-7003

  21. DLMS • Does this change require submission of a proposed change to the Defense Logistics Management System (DLMS) in order to become or maintain DLMS compliance? No

  22. As Is Process Flow • Attach an As Is Process Flow Diagram Designated Billing Office Analyzes bill and determines if bill is contractual or Misc Pay Performs acceptance of quantities/dollar amounts to be paid –against CLINs for contractual Mails bill with associated acceptance documentation to DFAS DFAS Pay Office Inputs bill into appropriate entitlement system based on Acceptor’s determination/ instruction Vendor Prints bill & mails to the Designated Billing Office

  23. To Be Process Flow • Attach a To Be Process Flow Diagram Vendor Submits EDI 811 WAWF Determines if bill is contractual or Misc Pay Contractual, obtain DoDAACs (other than Acceptor) from EDA Non-contractual, Acceptor DoDAAC mandatory Capture/Display Detail Call Data Service Acceptor Contractual: Adjust qty/dollar amts Non-contractual: Input Accounting Identifier, LPO and Pay DoDAAC; Adjust qty/dollar amts EDA DFAS Pay Office Provides status of transmission DFAS Accounting

More Related