EAS Connect I Data Transformation
Connectors, Channels, and Content Types
The modern enterprise leverages a number of platforms to communicate internally and externally, with the aim of improving productivity and collaboration. While email still remains a dominant form of communication, companies such as Slack are working to change enterprise behavior and displace email as the predominant platform for electronic communication. Microsoft [Skype, Yammer, Teams], Google [G-Chat], Zoom, and many more companies are joining the enterprise collaboration arms race with their own platforms to respond to increased demand for specialized instant messaging platforms.
While there are synergies across these platforms, customers have often expressed the need to maintain several different applications to operate their enterprise. In recent discussions with several enterprise customers, they have indicated they have over 50 such platforms in operation today, all of which serve a specific purpose for various lines of business.
Historically, PremCloud has supported these connectors, channels, or additional content types [depending on your preferred designation] through third-party providers to deliver our unified archive services [where we could not directly integrate non-email based channels into EAS]. However, with the growth in popularity of these new collaboration tools, and with increasing regulatory pressures to govern these tools, it has become apparent that we must have our own solution to directly integrate these third party communication platforms into EAS. We are proud to introduce, EAS Connect.
Introducing EAS Connect
EAS Connect simplifies the process required for organizations to ingest data from their various instant messaging platforms into their EAS archive. With our proprietary solution, we have eliminated the need for third-party connectors; furthermore, we have developed a user-friendly interface for connecting to a new source, scheduling the extraction of data from the source, and ingesting that data into EAS for unified preservation. Once the data has been archived, enterprises can execute federated retention, search, discovery, and supervision on all of their enterprise-wide content types.
Connecting to a New Source
EAS Connect offers a seamless connection and ingestion experience, and it provides a simple workflow consisting of five steps to set up a new data source in minutes.
Connect to Database. After inputting server information, EAS Connect, via API, will reach out to the database of the source platforms to collect data for ingestion.
Select Filters. EAS Connect allows admins to configure users for archive capture, either via manual input or uploading a CSV file with the list of targeted users for data collection. Furthermore, if the source system stores historical data, admins can configure Connect to pull historical data for ingestion into EAS.
Set up Schedule. To ensure that networking speeds are not compromised during the collection process, EAS Connect provides a robust scheduling mechanism to determine when collection occurs and how the large batches of information can be.
Select Mailbox. EAS Connect will route data after its collection from the source to any number of mailboxes designated for ingestion into the EAS archive.
Activate. After the initial configuration, EAS Connect provides the ability to activate immediately or to save the connector and its settings for later use.
Industry analysts predict that by 2020, 90% of all regulated organizations will preserve messaging content other than email, up from less than 50% today. As the demand for retaining data generated from additional instant messaging sources increases, our software development team will continue to expand the extensibility of the EAS Connect connector suite. We are actively working with customers to determine which enterprise data sources are in need of long-term preservation, so we can offer the most comprehensive archive experience possible. For more information on EAS Connect, or for suggestions on connectors to add to our roadmap, please contact your dedicated account manager today.
The built-in workflow provides a simple step by step guided implementation.
Ability to retroactively go back and capture historical messages or archive from a point in time forward.
Status monitoring, while supported manually today, will produce automated notifications in future releases.
Messages are routed to an Exchange journal mailbox. This mailbox will be flushed on a scheduled basis using EAS Archive tasks.
EAS will apply a customer x-header to the mailbox, thus enabling the enterprise to clearly identify all messages coming in from the source connector. This can enable custom archive policies by the connector as well as the ability to search on this specific content.
Future roadmap includes Microsoft Teams, Yammer, Bloomberg, etc.