While attending Summit UG in Nashville TN in early October, a gentleman by the name of Derik who was an IT Director for a medical device manufacturing company stopped by our Scribe booth to learn more about Scribe Online. During our conversation, he touched on his company’s efforts to tighten up IT security and data governance processes so they would become SOX compliant. Their improvement efforts were focused on increasing enforcement of internal controls and organizational policies around data management and access.
Our discussion highlighted the challenges his organization faced to document their legacy SSIS integration jobs. With the amount of custom code required for these integrations, staying compliant is a challenge, and they were looking for technology that would help them move away from the hassle custom coding has created. Not only did the documentation need to include updates to legacy SSIS integrations, but it also needed to include how the integrations were built in the first place.
The conversation reminded me about my time as a BI consultant. I used SSIS on a number of projects when I had to integrate data from multiple systems to a data warehouse in the customer’s development space. Then I had to create extensive documentation for another user to move them to production, and then reset credentials for the now production systems. Unfortunately, in most cases the user moving my projects to production was not always familiar with SSIS which meant I had to document each step required to move the packages. That equated to hours upon hours of time spent on documentation.
I could relate to Derik’s challenges because of these days I spent custom coding integrations and spending hours documenting every detail about them. But things have changed and now we have platforms such as Scribe Online. Scribe Online does not require hours of time to document your solutions because it resolves these pain points in an automated away.
Scribe Online’s multi-tenant architecture allows companies to leverage a Test Org much like our Parent/Child features enables companies to segregate permissions and define organizational rules. For example, you can setup rules that ensure integration developers only work in development, and those people tasked with moving the jobs to production do not have to access to those parts of the system where development is done.
In this example, developers can build out Scribe integration maps based on the business requirements using a Scribe Dev\Test org and then export the maps ready for production to a TFS, GitHub, or SharePoint site to be imported. Afterwards, someone with production credentials can use Scribe’s interface to import the integration maps. Lastly with a few simple steps, they can reassign the connections to the production application endpoints.
Figure: Scribe’s Parent/Child Structure
This is just one of many great benefits the Scribe Online architecture offers companies of all sizes. IT can complete the integration development without ever having to access the production data, and business department analysts can easily import the maps into production without ever having to access development. With this approach, there is simply no need for dozens of pages of “how-to” documentation. Instead, anyone is just a few easy steps away from a web browser through Scribe Online’s interface and the task is complete.
Ah, but let’s not forget about documenting the procedures. How were the integrations created? When was it modified last, and who has access to them? At Scribe we pride ourselves on how visual and “self-documenting” our solution is, but even an easy to follow graphical map may not be enough to satisfy an auditor looking at SOX compliance. There is no way an auditor would be willing to sit next to you and watch as you click through the integration maps while you confirm who has access and what data is being integrated where. They want a document that spells all that out for them. So what are your options? You could either call in sick, spend a few hours taking screenshots of the Scribe maps, or just use our free Google Doc documentation tool in our DEV portal. Todd Bailey, our Scribe Platform Product Director, wrote a great blog about our Google Doc documentation tool that explains it in detail. Our Scribe Google Doc documentation tool makes it possible for you to reduce a tedious, hours-long documentation process to just a few minutes with the push of a button.
Fig: Before – A Visual Scribe Map Fig: After – The Output from Scribe’s Google Documentation Tool
By the time I finished showing Derik how Scribe can address his company’s IT security governance requirements, a person announced that the expo floor was closing. He thanked me for the demo and great conversation. He said he was excited to follow up with our sales team after the Summit. Scribe’s iPaaS, with its ability to segregate permissions for integrations projects as well its ability to generate fast and easy documentation of the project would meet his IT security governance requirements and audit needs.
To learn more about the solutions we offer visit www.scribesoft.com.