Page 13 - RC18-EDGE Spring.FINAL

Connected Data: Design Process Technical System Integration

Based on anecdotal conversations we started to analyze and custom application interfaces to address our bidirec-
a broad spectrum of roles and responsibilities. It became tional and unidirectional data exchanges.
apparent many daily tasks had become disconnected and During our development cycle, the intrinsic value of prepar-
layered with unnecessary duplication. As we assessed the ing detailed workflow process blue prints, with accompa-
way people worked, our end users struggled to visualize nying swim-lane diagrams, became evident. It guided our
the possibilities and were becoming increasingly uncom- strategic in-depth review of each application’s ERD (Entity
fortable with change. This dilemma is one every agent of Relationship Diagram), focusing on table indexes and field
change has faced, knowing without stakeholder’s support, attributes essential to successful data mapping. Further-
moving forward is fraught with risk and uncertainty. more, the creation of custom staging tables facilitating
field level transformation based on business process trig-
To rebuild confidence and trust in technology, we turned gers were developed to maintain system integrity.
to a new digital approach to illuminate our vision: story-
boarding. Through a series of meetings with key employ- With disparate data silos now connected, our employ-
ees, we delved into current processes, pain points, system ees had the ability to see trends and behavioral patterns
usability, and reporting requirements. The result utlized across the entire lifecycle, building a foundation for
a graphical UX / UI approach that brought our findings strategic engagement. Through an intuitive graphical
to life in a simple, intuitive fashion. Through a “Business interface, managers and analysts could also visualize
Lifecycle Storyboard,” our end users were able to clearly data from different viewpoints empowering them to make
visualize how technology would enhance their daily tasks more accurate and timely business decisions. Over time,
and interactions with prospects and clients. as historical data points are collected, new patterns will
emerge allowing dynamic decision making to drive reve-
A supplemental “Technical Workflow Storyboard” provided nue increases and operating efficiencies.
programmers with a roadmap to accomplish our goals.
These detailed design specifications translated each task Cyber security risks are growing daily, and with propri-
into four main components, system touch points, pro- etary data, intellectual property, and perhaps a firm’s
cess inputs, process outputs and reporting parameters. competitive advantage traversing the cloud our vulnerabil-
Through the visualization process, we were quickly able ities grow as well. When constructing system interfaces
to discern no single integration method would satisfy and data connections, always incorporate a few simple
our comprehensive application integration requirements. precautionary cyber guidelines:
After reviewing each platform’s architecture, we blended
Application Program Interfaces (API), SaaS Integration • Require VPN connections for data exchange;
Platforms, JavaScript Object Notation (JSON), Apex code • Whitelist traffic using firewall rules;

11