Page Comparison

Status/General Discussion

• The teams are identifying redundancies, and looking at places where code can be re-used. Deb wants to avoid going back to teams about pieces until the overall OSS4ITS architecture is identified.

  • Ariel will be at TFHRC next week to discuss what makes sense going forward from the common architecture development. She would like us to be clear in the distinction between the project vision and what is actually built and implemented.  Her goal is to lose branded functionality and overlap all the projects to see which box things actually fit into.

• V2X Hub, CARMA, and ODE make sense together. , and SDC is the outlier. The vision

  overlaps

  is overlapping, but the built functionality may not

  which

  overlap and this needs to be investigated.

• Ariel would like us to be clear in the distinction between the project vision and what is actually built and implemented.

• Instead of building an ODE at Turner-Fairbanks, we will likely use the one that’s already been built by JPO.

• We will also re-use pieces of ODE in CARMA cloud and only build the specific pieces that are required for housing CARMA data.

  We should go into this process assuming that there are overlaps. Overlap CARMA and ODE and just look at what pieces are the same and where there truly is separate functionality.

  • Ariel’s goal is to lose branded functionality and overlap all the projects to see which box things actually fit into.

  • Clarifying what’s vision and what exists:

  • If something is just vision and doesn’t exist yet, Ariel wants to check if their there is an overlap so that we don’t develop things that have duplicate functionality in other projects. CARMA teams team’s goal is to document as is and not representative of future work. It’s not enough to have an overall diagram, it needs to be acted upon to clarify software functionality.

Ariel would like the teams to present on the best course of action. The timeline is critical for making decisions right now.

SET-IT diagrams merges

• V2X Hub has 4-5 overview layer 2 diagrams in SET-IT.

  • CARMA vehicles are not defined. Instead it shows as any vehicle with an On Board Equipment.Tom is going to look through SET-IT diagrams to correct issues

• SDC and ODE both have one diagram.

  • Some lines (information flows) have correct data but are displaying incorrect colors.

    • When we give this out to people, do we want to give them options or everything?

      Deb would like to give people just one diagram.

      We need one major high level diagram which aligns with the state standards which will force us to identify and address redundancies

      .And

      , and then it should be drilled down to a more specific one for each project.

      We need to have a stable number of diagrams in order to do merges.

    • Tony presented two options:

• Merge the diagrams together in SET-IT using one diagram as the baseline.

• Import the diagrams into RAD-IT and build them all together.

• Tom is going to look through SET-IT diagrams to correct issues. He believes the purpose of the project is to get SDC, ODE, CARMA, V2X Hub project teams to understand how their projects fit into the overall DOT architecture.

  He believes it would be easier to pick one project and use it as the underlying architecture rather than going through the process of building from the ground up in RAD-IT. Privacy and sanitation is already built into the diagrams.

  • The idea is for a state planner to take in a set of diagrams and

    upset

    update their infrastructure.

    Each project can be the scope of a single SET-IT project. If somebody used it, it could be imported into the regional architecture and used right away.

    The benefit to RAD-IT instead would be that it would help get all the definitions in cleanly and clearly.

• Sudhakar believes CARMA could have the diagrams ready in a few hours if they could agree on an ecosystem. There should only be 4 CARMA diagrams based on his estimate

  .

  SDC and ODE both have one drawing.

  Privacy and sanitation is already built into the diagrams

  .

• What mechanisms will be put in place to ensure changes always roll up and versions are controlled?

The zip file of the architecture is

uploaded to Confluence and then we’re manually coordinating through bi-weekly calls to ensure that only one person owns the overall architecture at a time.

Tom's recommendations

• Further changes to be made:

• Tom is comfortable with the changes that Tony has made.

• CARMA

  : Driver and basic vehicle need to be defined as elements.

  Both the CARMA platform and CARMA cloud are new physical objects.

  Vehicle location and motion should not be a user defined definition. It should be using the ARC-IT flow.

  Tom can massage it so that it works despite CARMA being the one sending the message.

• V2X Hub: Functional object is the only one that’s different. Tom has not had a chance to look in depth at the V2X Hub SET-IT diagrams yet.

• ARC-IT specifications says that if the data is the same, it should be the same flow.

  Instead of having say 20 new flows, you might have 5 new flows. Tom can also help work that out.

  Two major changes he has suggested is to:

• We can roll

  Roll some of these definitions together.

• We can use

  Use ARC-IT flows to make things easier.

• Tom wants to own the

  file

  architecture files for a day and he will send

  something

  updates needed tomorrow to Sudhakar.

• V2X Hub

  • Functional object is the only one that’s different.

  • Tom has not had a chance to look in depth at the V2X Hub SET-IT diagrams yet.

Next step is to put all of the diagrams into one place.