Remember the old days of data mapping when phrases like “map magic” meant terrifying things about a logical or physical map? Those were the days when there was little confidence in even the expected operation of the EDI data flows – a time when asking the “what if” questions resulted in a brain-storm of negative outcomes.
There are daily challenges to EDI operations that stem from both the remnants of the dark ages of data mapping and the changing EDI landscape. KFG has conjured up three simple spells (data mapping ideas) for your consideration.
In this article we discuss how using the Composite Route Communication feature of our EDI Translation platform can a) Identify Sending systems, b) Notify ERP and Accounting Stations, and c) Consolidate legacy one-off data maps.
The Procurement Data Standard (PDS) was introduced to stem the tide of failing transactions and substandard electronic contracting processes. In its support of this initiative, several DoD agencies bear PDS-related responsibilities – chief of which is the aggregation of the PDS compliance data and monthly reporting to AT&L on the status and health of the PDS EDI end-to-end system. The DoD should not only have tools that function correctly, but tout a higher standard of usability.
In this article we discuss how creating a community-accessible PDS acknowledgement dashboard, one where users can see and filter their data by refined query options, will strengthen the PDS initiative. The benefits of easily tracking PDS performance via data visualizations and sending system partitions would spotlight the adopting agiencies as an invaluable focal point for PDS integration and compliance.
DCMA's role as the information broker to the services means the the agency is in the business of EDI integration. Changes in customer contract writing systems and updates to procurement policy means turning the cog of software development. It is here that the discerning eye of Quality Assurance faces its most formidable challenge. Reconciling Logical mapping updates via spreadsheets, tracking changes and revisions across logical prose and physical executable code, and properly prescribing the appropriate test plan for execution are the core components that need to be strengthened.
In the article we discuss how strong test plans that matriculate from Test Driven Development paradigms in software engineering and a distributed version control system called Git can have a substantial positive impact on DCMA's EDI process. Contact us to find out more...