Carl Barlow kicked us off with an update of Symitar Efforts.
Here is a quick break down.
Member-Centric , 360 is working well and has been well reeived from the CU's. <since it was free the adoption rate has grown faster than many had thought imho>
Name Address project coming along <this still troubles me but not sure why, might be that I am just an old fuddy-dutty> It could be a big deal if the field changes are not well managed. So trying to move to a relationship style dataset. Non-Share and Non-Loan transactions (safe deposit, ticket purchases) SPRING RELEASE - Member work area to view a member without entering the account area. 2008.01 is the non-share/loan transactions will be available. might be useful for our HB enviroment. the release will creaet Member records for all our Name records, parameter for to trigger its usage. *Danger* fieldnumbers changing, all dates (lat updated) will be calculated fields. Name record area will change -if you are not using screen definitions-. Member work Area ... could be useful. FM History will be changing to Member Record (fall release for more clarity). WRG will need to be aware of this process as our products that create/revise Member Data might be greatly impacted if the Client changes to the new format. Some serious reading and analyst work might be needed. I volunteer Chopkins.
SQL extract they are updating the extract to make the mactro's better and allow 2005 usage <WRG has a great idea for this but we are stalled on a few items>
Symitar Explorer, Xperience, jXchange - Oh my. Where to start. Explorer .... moving on.
AIX 6.1, 5.3 etc on various harware platforms. pSeries, etc.
Single usage SQL across many products, Profit Stars, Yellow Hammer, etc. the mention of XML format instead of extracts out to macros? Odd
JHA and Symtitar sharing design and formating between roll outs of new products. Business services, teller capture, etc.
High Availability. I would love to see this dragged across the start line. Not even thinking about wishing for a finish, but really seeing a full plan, white paper on the vision and assumptions needed.