This image introduces part of a second spoke. The lower part of the image displays four roles from left to right: Native Role, Translation Binding Role, Application Role, Transformation Binding Role, and Business Role. The Native Role has four role ports on its left side (two for incoming events and two for outgoing events) and four role ports on its right side (two for incoming events and two for outgoing events). The role ports are denoted with small boxes and the events are denoted by slanted rectangles. The Native Role has four steps inside. Each step is connected through data flows and step ports to a role port on the left side and a role port on the right side. The steps are denoted by circles, the data flows are denoted by solid arrows, and the step ports are denoted by narrow boxes. Control flows connect the four steps to each other inside the role. The control flows are denoted by dashed arrows.
The Translation Binding Role to the right of the Native Role also has four role ports on its left side (two for incoming events and two for outgoing events). There are two role ports on its right side. There are four steps inside. The top step, labeled TL has an outgoing data flow that it receives from a role port on its right side and passes to a role port on its left side. It connects with a control flow to a step below it called DS. DS has an incoming data flow, but no outgoing data flow. DS is connects with a control flow to a step below called TL. TL has an incoming data flow that it receives from a role port on its left side and passes to a role port on its right side. It has a data flow that it passes to a step below it called GN. GN passes the data flow to an outgoing role port. Each data flow connects to a step with a step port.
There are four events between the Native Role and the Translation Binding Role. Two incoming (NE_ACK and NE_CAA) and two outgoing (NE_CAR and NE_ACK).
The Application Role to the right of the Translation Binding Role has two ports on its left side and two on its right side. The incoming event on the left side is named AE_CAA. The outgoing event on the left side is named AE_CAR. The outgoing event on the right side is named AE_CAR. The incoming event on the right side is named AE_CAA. The role includes two steps. Each step is connected with a data flow on its left side and a data flow on its right side. The steps are connected to each other by a control flow. Each data flow connects to a step with a step port.
The Transformation Binding Role to the right of the Application Role has one incoming event named AE_CAA and on outgoing event named AE_CAR. There are two role ports on each side. There are two steps inside that are connected with a control flow. Each step is connected with a data flow on its left side and a data flow on its right side. Each data flow connects to a step with a step port.
The Business Role to the right of the Application Role has one incoming event named BE_CAA and on outgoing event named BE_CAR. There are two role ports on each side. There are two steps inside that are connected with a control flow.
The upper part of the image displays a second Native Role, Translation Binding Role, Application Role, and Transformation Binding Role that connect to the same Business Role as the other roles described in the lower part of the image. The events for these roles have an apostrophe appended to their name. That is the only difference between their names and the events for the roles in the lower part of the image. The roles in the upper part of the image each have two role ports on each side. There are two steps in each of these role, with a data flow and step ports connecting to the left and right sides of each role.
The legend at the bottom shows that straight rectangles with either solid or dashed borders identify roles, circles identify steps, solid arrows identify data flow, dashed arrows identify control flow, slanted rectangles identify events, boxes identify roles, and thin boxes identify step ports.