Scott finlayson

Ericsson | GlobalLogic

UI Design / UX Design

Circuit Layout Record
*Due to NDA restrictions, I am unable to show finished screens from within the application(s). The following examples are pre-implementation mockups or visual representations that closely resemble the final product if implemented.
Rebranded, unified styling, more compact

Leveraged the branding and styling cues from other endeavors within the Ericsson Adaptive Inventory application and applied them to the Circuit Layout Record (CLR) graphs.

  • consistent with new branding
  • consistency in data presentation of each object type
  • more evident when objects were not-yet connected
  • more information on screen due to more-efficient layout new core structure to accommodate proposed expansion features
Aggregate object expansion

I created & designed the ability to display aggregate objects within CLR, and the ability to expand them to show their nested child objects within the trail.

This allowed many users to finally utilize CLR to view their circuits containing nested objects and view their connectivity.

Nested aggregation & parallel connections

There were other challenges I needed to tackle to add functionality to CLR.

  • First was to solve for displaying nested aggregation; objects that were expandable within other objects that were expandable. This solution scaled very well.
  • Second was to solve for displaying parallel trails and/or redundant trails within an aggregate object, and again, any of those nested objects could also be expanded.
  • Lastly was the challenge of designing this expansion to visually work well as a first or last object within a trail. I worked with the developers to be sure we could deliver a meaningful structure that could consistently draw the virtual areas consumed by every object.
Site collapse

After solving for aggregate object expand/collapse, it seemed only fitting to add a similar feature to calculated site containers within CLR. This was problematic because a Site isn't technically a network object, but a common attribute of adjacent connected objects that is derived from the object data.

Working closely with the developers, my solution was to treat the collapsed collection of adjacent objects as a single virtualized object displaying a site icon in a rounded-square boundary - as opposed to the typical circle - and displayed a numeral above the collapsed site indicating the number of enclosed objects.

Errors & non-connections

Many users desired to see a differentiation between objects that had issues with the ability to be connected, and those which were just not-yet-connected.

Design specifications

Provided pixel-perfect mockups and specifications to the developers.