Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
🔓 Public Page
Date:
27 Aug
| Info |
|---|
ANTITRUST STATEMENT As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds. |
Agenda
Welcome
Antitrust
Complete 2024R1
Work through EMStoBMStoCAPIS Conversion DocumentEMStoBMStoCAPIS (Last 225)
Webinar
Meeting Minutes
Work through EMStoBMStoCAPIS Conversion Document
In previous weeks we have worked on grouped items, but we have ran the course on what we believe is group and will start to work alphabetically (We made it through A and B )
Dan presented list of fields that are strings in BMS that were always intended to contain numeric properties, so striking "Desc" suffix from property names and some also ran afoul of the "BlahBlahsNum" vs. "BlahBlahQry" rule.
6.6.0 BMS element name | CAPIS proposal |
AxlesNumDesc | axleQty |
BedroomLengthDesc | bedroomLength |
BerthsNumDesc | berthQty |
ClosedBoxLengthDesc | closedBoxLength |
DriveAxlesNumDesc | driveAxleQty |
EngineHorsepowerDesc | engineHorsepower |
EngineSizeDesc | engineSize |
FrontTireSizeDesc | frontTireSize |
FuelCapacityDesc | fuelCapacity |
FuelTanksNumDesc | fuelTankQty |
HeightDesc | height |
LengthDesc | length |
LiftCapacityDesc | liftCapacity |
MainLengthDesc | mainLength |
MaxLiftHeightDesc | maxLiftHeight |
NumSlideOutRoomDesc | slideOutRoomQty |
RearAxlesNumDesc | rearAxleQty |
RearTireSizeDesc | rearTireSize |
ReeferHoursDesc | reeferHours |
SailsNumDesc | sailQty |
SeparatorHoursDesc | separatorHours |
SlidingAxleNumDesc | slidingAxleQty |
TagAxlesNumDesc | tagAxleQty |
TireSizeDesc | tireSize |
TotalSqFtDesc | totalSqFt |
WeightCapacityDesc | weightCapacity |
WeightDesc | weight |
WidthDesc | width |
WindowsNumDesc | windowQty |
These were reviewed in the meeting at a high level and we want to make sure these are intended to be numeric
Paulette will mark in the master document, and we can review next meeting.
Fields with Code List naming. We have a number of code list that end with Code, some Type and some no description.
Paulette is assigned to look through the Code List and determine the method of naming that is used.
Great Job
Up Next
Welcome
Antitrust
Meeting Minute Review
Homework Review
Review Dan’s proposal for Desc to numeric values
Values were added and proposals made to keep existing values if the new name duplicated.
Review fields with code list method.
There is no method
Codes may be description, type, code or a mix of everything.
If it really is a Code do we need to have code or should it be dropped, we have a mix now.
If we have Type and they are types do we leave it type or remove type, we have a mix now.
Do we Need Num or Number
We have 109 values that have Num in CAPIS, This would be an individual review because some can have the num or number removed with no impact and others sound better with it.
Memo, Desc, Notes
We have 39 Memo
Most Memo are Character Infinity, the ones that are not, I would change to be the same or change the name
We have 13 Note/Notes
Due to the BMS Appendix A stating we would consolidate Memo/Notes/Comments/Remarks to Memo, I would recommend changing these to memo or a different name.
Previously we changed ErrorNotes to errorDocuments, ConditionalNotes to conditionalDocuments and StatusNotes to statusDocuments.
We have 4 comment/Comments that can be changed to memo
We have 105 Desc
Description or Desc is not part of the BMS Appenix A consolidation
Some Desc or Description can be removed with no impact, there are others that need it to identify its more details on another field.
Individual research
We have 3 remarks that were changed to Memo
Work on EMStoBMStoCAPIS Conversion Document, Starting with CComplete 2024R1
CAPA Tier 1 parts Code List
Last week Architecture discussed adding a new code list in Party Type
Mitchell meet and decided it was not a rush and not a request Michell will make
Intertech should request this code
Another Committee can propose this and bring it to Architecture if needed
How are we going to include the EMStoBMStoCAPIS document to the webpage
This should be part of a release in the future (BMS or CAPIS or High Level)?
For this release it will be added to the Top of the Release page.
It will need a version
Process to add BMS to CAPIS Code List
We need to sync the ones we have added from the first release
Others will be added as we go
EMStoBMStoCAPIS
Aggregate Column to show if the name is for an Aggregate vs a field.
Currency Needs Amt, Amt move to end to make it sound better
Abbreviation of DT for Date was removed and the fields that ended in DT was changed to Date
ListPrice is a critical item, the name is fine for CAPIS but the BMS comment is not correct. (Moved to Parking Lot)
Need a more specific rule for the abbreviations list, do we always end with abbreviation, do we always use abbreviation.
Webinar
Reviewed PowerPoint and made some changes and allocated who was speaking to each slide
Great Job
Up Next
Welcome
Antitrust
Meeting Minute Review
Finish EMStoBMStoCAPIS
Get Rule on Abbreviation
Action items
Decisions
Reference
Participants
Paulette Reed
Dan Webster
Chris Martinez
Jeff Schroder
Paul Barry
Phil Martinez
Mike Hastings
Andy Bober