Wow! That was fast! 2015 and the year end holidays were a blur and are over. We are now full speed ahead into 2016. Many organizations spent the end of 2015 wrapping up their initiatives so that they could approach 2016 with a clean slate and start to plan for all of the new projects and challenges that a new year brings. Many organizations are also evaluating the previous year and taking stock of where they are starting out 2016.
We have just passed the mid-year point. This can be a very busy time of year for all of us with companies focusing on vacation coverage, re-assessing their budget and wrapping up 3rd and 4th quarter projects by the end of the year. This is also the time of the year that most of our clients are reflecting on how the first six months has impacted their business in order to propel them to greater heights in the remainder of the year, so they can finish strong!
When I came to REMEDI this past summer, I was excited for the opportunity to work in a professional setting and do meaningful work for the first time in my career. Cleaning tables and preparing food was about to be a thing of the past, and I wasn’t complaining. I had a very basic understanding of EDI and how it impacted the economy and business world, but I was interested to see exactly what REMEDI’s role in the process was. I can remember looking through the CRM my first day and seeing a lot of company names I recognized. As I continued to scroll through the list, more and more brands popped up, including some that I use a lot in my life. When I realized REMEDI played a big role in the EDI department of so many impactful brands, I knew what I was doing could actually make a difference.
When REMEDI started as a business twenty-one years ago, our focus was solely on EDI - integrating data from/to a trading partner from/to a company's business software. EDI software basically did what data integration software does today, but on a limited basis and it was strictly business-to-business. As companies began choosing software packages instead of developing applications in-house, the need for internal data integration grew and software developers answered the need with, what was then called, middleware. These days integration software satisfies the needs of business-to-business and application-to-application data exchange.
