Search the web
Sign In
New User? Sign Up
OAGI-CoreComponents · OAGI Core Components Work Group
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Message search is now enhanced, find messages faster. Take it for a spin.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
MINUTES: Jan 20 Core Components WG Conference Call   Message List  
Reply | Forward Message #457 of 467 |
Attendees:
 
David Connelly, OAGi
Satish Ramanathan, MRO Software
Sylvia Webb, GEFEG
Ron Schuldt, Lockheed Martin
Garret Minakawa, Oracle
 
Minutes:
 
Call was focused on mapping approved TBG17 ACCs to OAGIS 9.0 Core Components.
 
The file "TBG17-OAGIS Mapping.xls" (now available in Files) was used as the basis for this discussion.
 
Mapping process was divided into two phases:
  • Phase I identifies semantic matches at the ACC level (i.e. does the approved TBG17 ACC have an equivalent component in OAGIS based on the ACC name and definition)
  • Phase II analyzes the properties (BCCs) of the ACC to determine the level of compatibility between TBG17 and OAGIS
Scope included the original 19 ACCs in TBG17 v1.0 plus 18 additional ACCs approved at the TBG17 December meeting.
 
TBG17 ACCs that did not have a match in OAGIS included:
  • Account. Details (GL Account and Credit Card account info exist but no separate Account object)
  • Range. Details
  • Event. Details
  • Organization. Details (Information is currently included in Party object.  No separate object for Organization)
  • Country. Details (OAGIS uses a Country_ Code. Type datatype and a Country Code property term but no separate object for Country)
  • Country Sub-Division. Details (OAGIS uses a Country Sub-Division_ Code. Type datatype and a Country Sub-Division Code property term but no separate object for Country Sub-Division)
  • Business Profile. Details
  • Complete Work. Details
  • Construction Type. Details
  • Contract. Details
  • Document. Details
  • Examination Result. Details
  • Guarantee. Details
  • Metrics. Details
It was also determined that the OAGIS "AllowanceChargeCalculationType" could be generalized to just "CalculationType" to correspond with the TBG17 "Calculation. Details"
 
Similarly, the OAGIS "CoordinateType" could be named "GeographicalCoordinateType" to match with the TBG17 "Geographical Coordinate. Details"
 
In some cases, it was determined that the TBG17 definition was too ambiguous to determine whether a match existed or not.
 
Next call scheduled for Thursday, Jan 27 at 7:30 PST (14:30 UTC).  Agenda will be to complete Phase I of the TBG17 to OAGIS mapping and start with Phase II.
 
 


Thu Jan 20, 2005 8:11 pm

gminakaw
Offline Offline
Send Email Send Email

Forward
Message #457 of 467 |
Expand Messages Author Sort by Date

Attendees: David Connelly, OAGi Satish Ramanathan, MRO Software Sylvia Webb, GEFEG Ron Schuldt, Lockheed Martin Garret Minakawa, Oracle Minutes: Call was...
Garret Minakawa
gminakaw
Offline Send Email
Jan 20, 2005
8:11 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help