2022-05-10 Architecture Meeting Minutes

Public Page

Date: May 10, 2022

Agenda

• Antitrust

• Committee Welcome

• Meeting Minutes Review

• Committee Goals Review

  • Wrapping up vehicle object this month

  • Claim and parties completed by summer

• nodejs version issue

• Continue review vehicle object starting with engine and transmission

Meeting Minutes

• Antitrust Accepted

• Welcome

• Meeting Minutes Reviewed and Accepted

• Nodejs version issue

  • Dan was working on a clone of the BMS and ran into issues due to him using a new version of nodejs than the current CIECA Build has.

  • Andy worked with Dan and when dan changed his version of nodejs, the issue was resolved

  • To fix the problem, Andy has made changes to the build process

    • Updated Action nodejs version to 14.x

    • updated sqlite and sqlite3 packages for nodejs 14.19

    • ensure the data parameter to writeFileSync() is a string

• GitHub use by the team to share proposals

  • Vehicle model schemas can be shared in GitHub to allow individuals to analyze the proof of concepts before the meetings.

  • Using GitHub would be more effective than searching through emails and meeting minutes to find the documentation.

  • We could use GitHub to prepare for future meetings.

• Confluence Work Documents page.

  • The working documents of the committees are stored in Confluence. https://cieca.atlassian.net/l/c/nBST9D32

  • The Confluence page has a link that will take you to the ZoHo Workdrive that stores the documents.

    • This is a good place for information that is not part of our build. Such as Word and Excel documents used for analysis and Proof of Concept.

• Excel to XML spy drops “quotation” marks. This causes rework when you use the copy and paste option.

• Committee Goals Review

  • Wrap up schema for vehicle this month. This gives us 3 weeks till the end of May.

  • Want to start working on Claim and Party to be concluded by summer.

• Next Steps for vehicle

  • We need examples using vehicle schema.

    • Create Instances using the schema

• History of the BMS creation

  • The BMS was the work of combining the XML and EDI and it took a few years to complete, but we don’t know how long it took to get one section, such as vehicle completed.

• Review of Excel document for engine and transmission and remaining aggregates in the vehicle object.

  • Jeff showed an example of a hybrid car that had 2 engines and 2 transmissions, but each engine and transmission had one option.

    • 2019 BMW i8 has two transmissions which are both covered in the interchange. The same vehicle also being a hybrid as two interchange numbers under the 300 part code. One for the electric motor and one for the gasoline motor. You would have more than one option code for each part.

      • Part TRA Model: BMWI8 Year: 2019

        • AT

          • 1 2 speed (front)……..#####

          • 2 6 speed (rear)………######

      • Part ENG Model: BMWI8 Year 2019

        • 1 Electric…………………….……######

        • 2 gasoline (1.5L, turbo)……######

  • Proposal was made to make the engine and array and have an engine code and engine description and to make transmission an array with transmission code and transmission description, since we can have multiples of the engine and transmission and one code.

  • The example that we have shows that the current BMS does not work with the hybrid car.

  • Transmission has type and speed, should the values of type and speed be added under transmission instead of code and description.

    • Reviewed the Master Code List for Transmission type and the Speed and the Type or combined in the code.

      • Do we want to revamp the Code list or just use the code list and format that we already have to stay backward compatible.

        • There is no decision on this except that we would not want to remove any values and we would have to stay backward compatible, but the committee agrees that we need new values to keep up with the EV.

        • The Transmission Type Code List is an Open Enum and trading partners can add values to their implementation with customers.

  • Do we need a new aggregate for the EV battery because it is more than a part and falls more in line with the options under the Powertrain?

    • The homework for the members of the committee is to bring BMS examples of vehicles today that are hybrid or electric car to see how systems are processing them today.

  • Condition will remain an aggregate with 12 elements.

  • Valuation will remain an aggregate.

    • In the example we flattened the Valuation to be valuationType and valuationAmt, however, with the industry today, the valuation amounts are changing quickly and it has been determined that the vehicleDateTime is a benefit and maybe some other values from the BMS.

      • Dan will do analysis on the impacts of the changing valuation and see what fields he recommends being added back.

Great Meeting Everyone! We let out a few minutes early so everyone could start on homework.

Up Next

• Antitrust

• Committee Welcome

• Meeting Minutes Review

• Review the BMS examples of vehicle to determine the powertrain aggregates of engine and transmission.

• Review analysis on valuation fields.

Action items

Decisions

Participants

• Paulette Reed

• Dan Webster

• Mike Hastings

• Jeff Schroder

• Paul Barry

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. https://cieca.atlassian.net/wiki/spaces/ARCH