Tim Bauer’s Running Thoughts

Semi-daily webcast summaries/insights

MSFT: Sharepoint Collaboration

Watched this webcast this morning

Building Collaborative Applications with the Next Version of Microsoft Windows SharePoint Services

A very interesting discussion of enablers that are coming w/ SP 2.0. I was curious in that we have seen a build in interest in pipeline around our collaboration framework which, while not focused on a specific product, definitely has strong ties to SP as part of the ways an organization can change the interaction dynamics of thier teams.

The keys I heard was:

    1. Alot of focus around the usability of the application. Which is interesting in that that is the core of how we approach defining collaboration models for clients. If it isn’t perceived as usable by the users you have built a monument not a tool. SP had some gaps. Features outlined below make strides to closing those.

    2. Great to see email integration. Clients have been hardwiring this in to thier collaboration solutions. Making it native is awesome.

    3. The change tracking of all list items at a FIELD level is another great feature to enable collaboration. People want to know what changed and filter on specific types of change. The older versions were to global (library or doc level) and didn’t tell you in the alert (w/o customization) what changed.


Here are my rough notes from the webcast.

Quote:
Mike Morton - Lead Program Manager

…………○ Next version of Windows Sharepoint Svcs (WSS)
…………
…………○ WSS sit in middle of all O12 systems
……………………§ BI
……………………§ Collab - Email, EPM, Workflow, Blog, Wiki
……………………§ Portal - Sharepoint
……………………§ Search
……………………§ Content Mgmt
……………………§ Business Process - Infopath
…………○ 1:20 — This talk focused on collab
…………○ 1:50 — Tracking Investment by MSFT in Sharepoint (why)
……………………§ Version history
……………………§ RSS
……………………§ Email intg
……………………§ Outlook intg
……………………§ Dist support
……………………§ Alert
…………○ 3:07 - List History / Versioning
……………………§ All items (not just docs) now
……………………§ Shows, by field, change
……………………§ Append only fields (notes)
……………………§ Issue Tracking template
……………………§ Big investment in workflow (Windows Workflow Foundation)
…………○ 5:30 - Project Tasks Lists
……………………§ Lightweight PM functionality
……………………§ Simple Gantt
…………○ 6:50 - Demo of Above Items
……………………§ Example of add on (comments)
……………………§ Create a Project Task List Page. Some nice drag and drop features on the Gannt chart
……………………§ Code discussions and how to extend
……………………§ 13:50 examples of Versions Object Model
…………○ 14:00 Email Integration
……………………§ Sharepoint lists can RECEIVE email
……………………§ Email list for disc board, doc lib, etc
……………………§ Calendars can take in iCal emails and post to emails (so include as invite and it gest updated)
……………………§ Developers have support to map portions of email to various lists
……………………§ 16:30 example email handler code
……………………§ Sharepoint site groups can have an associated distribution list. All mail sent to that distribution list gets archived on the SPS site associated to it
………………………………□ 20:16 list of directory services webservices
………………………………□ 20:40 directory services example snippet
…………○ 21:30 - Demo of Email Intg
……………………§ 23:00 Show how email and forums (disc boards) can both post to same thread
……………………§ 25:00 Create a site and show integration of distribution list w/ email lists
……………………§ 28:40 Example of how calendar items can hit site lists for email
……………………§ 30:30 Email Handler workflow. Off task list.
…………○ 32:15 Outlook Intg and Synch APIs
……………………§ Outlook and Groove use the Synch APIs
…………○ 34:30 Demo of Intg/Synch
……………………§ Connect w/ outlook command in SP (new)
……………………§ Then you can add in either and it refreshes / synchs calendards …
……………………§ Same for tasks, discussions, etc
……………………§ Personal calendar / team calendar … side by side or overlay
…………○ 37:00 Some Investment In RSS / Alerts
……………………§ All SP lists provide RSS feeds
……………………§ Alerts Filter for specific content (not just alert at library level)
……………………§ Alerts include what changed on list
……………………§ 38:45 Alert Template Snippet … allows you to tailor what users can check off for filters on their alerts
…………○ 41:45 UI and Navigation
……………………§ Breadcrumbs
……………………§ Security Trimmed (view tailor by user)
…………○ 42:20 Demo of UI / Nav
……………………§ Ajax embedded in lists
…………○ 44:45 Summary
……………………§ Release @ end of 2006
……………………§ More in 012 server
……………………§ Recommended links
………………………………□ Msdn.microsoft.com/sharepoint
………………………………□ Gotdotnet.com/team/sharepoint
…………○ 46:00 - Q&A
……………………§ Exchange required? No. If you want the shared site list / email list you do need AD.
……………………§ Groove Integrated? Does have some. Not shown. Rich two way synch of doc to doc lib in SP. Could use that to have 1 person in SP … rest in groove
……………………§ WIKI/Blog? Wasn’t demo’d
……………………§ Mail enabled public folders go away? Yes. Move to SP.
……………………§ Any server (64bit or 32bit).
……………………§ Master pages supported? Yes. SP page is based on master page. Great way to customize a site.
……………………§ Beta 2 Available? Shortly. Part of longhorn server. Also separate. Beta 1 now for key partners only. G&R has this by the way (see Rebecca Marino).
……………………§ Virtual Labs/SOA? Webservices is core to product. Mike Morton - Lead Program Manager

…………○ Next version of Windows Sharepoint Svcs (WSS)
…………
…………○ WSS sit in middle of all O12 systems
……………………§ BI
……………………§ Collab - Email, EPM, Workflow, Blog, Wiki
……………………§ Portal - Sharepoint
……………………§ Search
……………………§ Content Mgmt
……………………§ Business Process - Infopath
…………○ 1:20 — This talk focused on collab
…………○ 1:50 — Tracking Investment by MSFT in Sharepoint (why)
……………………§ Version history
……………………§ RSS
……………………§ Email intg
……………………§ Outlook intg
……………………§ Dist support
……………………§ Alert
…………○ 3:07 - List History / Versioning
……………………§ All items (not just docs) now
……………………§ Shows, by field, change
……………………§ Append only fields (notes)
……………………§ Issue Tracking template
……………………§ Big investment in workflow (Windows Workflow Foundation)
…………○ 5:30 - Project Tasks Lists
……………………§ Lightweight PM functionality
……………………§ Simple Gantt
…………○ 6:50 - Demo of Above Items
……………………§ Example of add on (comments)
……………………§ Create a Project Task List Page. Some nice drag and drop features on the Gannt chart
……………………§ Code discussions and how to extend
……………………§ 13:50 examples of Versions Object Model
…………○ 14:00 Email Integration
……………………§ Sharepoint lists can RECEIVE email
……………………§ Email list for disc board, doc lib, etc
……………………§ Calendars can take in iCal emails and post to emails (so include as invite and it gest updated)
……………………§ Developers have support to map portions of email to various lists
……………………§ 16:30 example email handler code
……………………§ Sharepoint site groups can have an associated distribution list. All mail sent to that distribution list gets archived on the SPS site associated to it
………………………………□ 20:16 list of directory services webservices
………………………………□ 20:40 directory services example snippet
…………○ 21:30 - Demo of Email Intg
……………………§ 23:00 Show how email and forums (disc boards) can both post to same thread
……………………§ 25:00 Create a site and show integration of distribution list w/ email lists
……………………§ 28:40 Example of how calendar items can hit site lists for email
……………………§ 30:30 Email Handler workflow. Off task list.
…………○ 32:15 Outlook Intg and Synch APIs
……………………§ Outlook and Groove use the Synch APIs
…………○ 34:30 Demo of Intg/Synch
……………………§ Connect w/ outlook command in SP (new)
……………………§ Then you can add in either and it refreshes / synchs calendards …
……………………§ Same for tasks, discussions, etc
……………………§ Personal calendar / team calendar … side by side or overlay
…………○ 37:00 Some Investment In RSS / Alerts
……………………§ All SP lists provide RSS feeds
……………………§ Alerts Filter for specific content (not just alert at library level)
……………………§ Alerts include what changed on list
……………………§ 38:45 Alert Template Snippet … allows you to tailor what users can check off for filters on their alerts
…………○ 41:45 UI and Navigation
……………………§ Breadcrumbs
……………………§ Security Trimmed (view tailor by user)
…………○ 42:20 Demo of UI / Nav
……………………§ Ajax embedded in lists
…………○ 44:45 Summary
……………………§ Release @ end of 2006
……………………§ More in 012 server
……………………§ Recommended links
………………………………□ Msdn.microsoft.com/sharepoint
………………………………□ Gotdotnet.com/team/sharepoint
…………○ 46:00 - Q&A
……………………§ Exchange required? No. If you want the shared site list / email list you do need AD.
……………………§ Groove Integrated? Does have some. Not shown. Rich two way synch of doc to doc lib in SP. Could use that to have 1 person in SP … rest in groove
……………………§ WIKI/Blog? Wasn’t demo’d
……………………§ Mail enabled public folders go away? Yes. Move to SP.
……………………§ Any server (64bit or 32bit).
……………………§ Master pages supported? Yes. SP page is based on master page. Great way to customize a site.
……………………§ Beta 2 Available? Shortly. Part of longhorn server. Also separate. Beta 1 now for key partners only. G&R has this by the way (see Rebecca Marino).
……………………§ Virtual Labs/SOA? Webservices is core to product.

April 28, 2006 Posted by bauertim | Uncategorized | , , | No Comments

PSOFT Fusion Upgrade

Listened to a webcast by IBM this morning around their offering to help PSOFT clients plan for their movement to ORCL Fusion from PSOFT. Here is a direct link:

WEBCAST

If that doesn’t work you can reach it here after registering:

http://www.bitpipe.com/detail/RES/1143675922_604.html

I watched it because ORCL’s Fusion model is based on java (a core compentency of ours, as well as PSOFT and ORCL) and we have been helping clients see the migration path for thier people (JDE to Java, PSOFT to Java) for the last year or so.

Some interesting tidbits were:

    1. They see the risk of the people side as well. Point out PSOFT pool will dwindle and cause 3rd party support costs to rise

    2. They have a free assessment much like we have to help clients lay down a roadmap when making major system decisions like this. We actually are doing the 2nd phase (billable) on one of these right now up in APL/GB.

Just validates our efforts, that started last year, to align our Java team and ORCL/PSOFT teams. Should be an interesting next 2-5 years for PSOFT and JDE clients.

Quote:
4/13/2006
–IBM Applications on Demand
–Mike Connelly (16 yr PM) -mconnolly@us.ibm.com

…………○ 2:00 — Review of 2005 acquistion of JDE and PSOFT in 2005
……………………§ 8000 psoft customers
……………………§ 3000 jde customers
…………○ 3:30 — If your customers are thinking Fusion is their path then they need to upgrade to 8.8 for PSOFT to leverage fusion migration tools
…………○ 4:00 — Project Fusion — Two Pieces
……………………§ Middleware (enhancement of current version)
……………………§ Application
……………………§ Full Suite release in 2008
……………………§ 8000 engineers on this, 90% of PSOFTs team
…………○ 6:00 — Grid, Middleware, Applications
…………○ 7:00 — How to get to Fusion
……………………§ Liscenses can be traded
……………………§ Migration tools will be provided
…………○ 8:00 — Consider
……………………§ Investment in PSOFT tools
……………………§ Investment in Resources that know PSOFT
……………………§ Note PSOFT current apps will continue to 2013
……………………§ Could swap for ORCL modules now or ORCL Fusion products later
…………○ 10:00 — Types of Business
……………………§ Stable - Current ERP works. 2006 to 2007 get to an upgrade capable version . Affter 2008 Move to ORCL Fusion or SAP or Web Services Model.
……………………§ In Flux. ERP solution is evolving and being heavily invested in. Replace w/ ORCL eBusiness Suite in 2006 and 2007. In 2008, outsource application magmt and/or move to ORCL Fusion.
…………○ 13:00 What is your companies software philosphy
……………………§ Early Adopter (go in w/ ORCL now - to fusion in 200 8)
……………………§ Stablized (start inl 2009)
……………………§ Laggard (stay on PSOFT till 2013)
…………○ 15:00 How protect and plan to protect your investment
……………………§ Stay current on releases
……………………§ Use 3rd parties to maintain applications
……………………§ Investigate BPO
…………○ 17:30 Factors for evaluating Impact
……………………§ Business Case
………………………………□ Existing Investment in Applications & Tech
………………………………□ Functional needs matched in 3-5-10 years
……………………§ Key Drivers of Business Case
………………………………□ Reduce IT cost
………………………………□ Upgrade
………………………………□ Lack of functional fit
………………………………□ PSOFT Skill Pool Declines
………………………………□ Migration will come sooner or later
………………………………□ 3rd party support (could reduce risk / cost)
……………………§ Investment in ERP is higher than you think
………………………………□ Research shows true ongoing cost is 75 * liscensing ocst
………………………………□ Integration to legacy system costs
………………………………□ Customizations (UI, Process, DW, Reporting etc)
………………………………□ Support team and End user skills on product
…………○ 21:00 — PSOFT Still Rocks In
……………………§ CRM B2C for Fin Svcs & Comm
……………………§ Campus / Student Reg Systems
…………○ 22:00 — IT Budget and PSOFT (for PSOFT Customer)
……………………§ 15% is POSFT Support
……………………§ 25% is PSOFT New
……………………§ Net: Big $ are here … need to watch and plan
…………○ 23:00 — 1st Step — ERP Software Assessment
……………………§ Define Strategic Goals of Company
………………………………□ Risk reduction, growth, scale, cost reduce, productivity gains, it alighnment w/ strategy for IT Overall
……………………§ Define Current Status of ERP and Supporting Systems
………………………………□ Funcitonality implemented, customization level, current arch, fucnt and tech challenges, current support
……………………§ Outline Migration Plan Decision Criteria (which may lead to none)
………………………………□ Skills Retention, low liscense cost, increase functionalty, reduce downtime, reduce support
……………………§ Evaluate short and long term options
……………………§ Deliver Recommendations
…………○ 26:30 — Guided Discovery
……………………§ Free. Client commitment 1/2 Day, Total Duration about two weeks.
……………………§ Step 1 - Current State Assessment
……………………§ Step 2 - Value Creation (cost reduce, svc levels up, ops capabiliiteis up)
……………………§ Step 3 - Assess Goals for Future State
……………………§ Step 4 - Recommendations
…………○ 29:30 - Reasons Why You Should Do a Guided Discovery
……………………§ Current State Snapshot
……………………§ Performance Improvements (costs, SLA)
……………………§ Etc
…………○ 30:00 - 34:00 IBM LOVE IN (why IBM)
…………○ 34:00 - Q&A
……………………§ Gartner PSOFT to Fusion = PSOFT to SAP .. Should SAP be considered
………………………………□ No. ReImplementation <> Migration … but close yes.
……………………§ Stay on DB2 ok?
………………………………□ Stance is ORCL DB. No promise for DB2.
……………………§Future of SQL, PeopleCode, etc
………………………………□ J2ee open. That is going away.

April 27, 2006 Posted by bauertim | Uncategorized | | No Comments

MSFT: Visual Studio Team System Extensibility

I would give this webcast around extending Team System relative to system model a ‘3′ … not sure if its because I didn’t like the information and/or style of presentation … or if my ongoing feeling that this topic isn’t core to us colors my opinion. Probably more of the later since the concept of System Definition Models isn’t a hot topic with most of our middle market clients (any counter thoughts on that opinion?). In my early read, this aspect of Team System (System Models and customizing them) is about large production environments that need complex configuration and deployment management. Still it is part of the Team System story so I was curious to get a bit more detail ….

That said, if you are curious as well you can view the webcast here WEBCAST

Some of the notes I took as I tinkered as listened … are as follows.

Quote:
MSDN: Visual Studio Team System Extensibility: Creating & Extending System Definition Modules
–Dmitriy Nikonov, Program Mgr
–Erbil Yilmaz, Erbil Yilmaz

…………○ 1:50 - Goals
……………………§ Review SDM SDK (part of vs 2005 sdk)
……………………§ Steps to extend VSTESA
…………○ 2:30 - System Definition Model
……………………§ Formal model of a system
□ Application
□ Hosts
□ Network
□ Hardward
…………○ 4:00 Key Persona’s In System Definition Model
……………………§ Application Designer - config settings
……………………§ System Designer - config for deploy
……………………§ Deployment Designer - binds to data center comm err
……………………§ Logical Data Center Desiger -
…………○ 7:15 Using SDM SDK to extend VSTESA
……………………§ Add custom settings to delivered models (ie security, app health, etc)
……………………§ Add new application & logical server models
……………………§ Write new validators (security, threat models, sla models, app health, etc)
…………○ 11:30 - Talk about steps to extend
……………………§ Edit in notepad (XML)
…………○ 13:00 - What you get w/ the product (pieces)
……………………§ “System” Abstract Definitions
……………………§ “System” Prototypes
……………………§ Constraint Managers
…………○ 15:30 - How to create new models - Files
……………………§ Source SDM file (.sdm)
……………………§ Compiled SDM file (.sdmDocument)
……………………§ Manager Assembly (.dll)
……………………§ Prototype (.adPrototype or .lddPrototype)
……………………§ Bitmaps (optional)
……………………§ Setup (optional)
…………○ 16:30 - cmd lines tools
…………○ 17:30 - demo
……………………§ VS Design Surface
……………………§ 20:30 - Example of SDM XML file
……………………§ 29:00 - end demo
…………○ 29:30 - Creating Custom Validators
……………………§ Five steps (define, gen c# class, implement, compile, install)
……………………§ 32:00 - Complex traversal path to do this
…………○ 34:00 - Demo
……………………§ Discuss error msging back out of validators
…………○ 42:00 - End of Demo
…………○ 43:00 to 52:00 - Q&A

April 26, 2006 Posted by bauertim | Uncategorized | , | No Comments

MSFT: Workflows in Office / Sharepoint

Nicely done webcast. Worthy review for system analysts and business analysts that are wanting to be aware of one way of automating processes that are primarily manual today in clients. Here is a link:

WEBCAST LINK

That said here are my rough notes as I watched and ran:

Quote:
Eilene Hao - Program Mgr Office
George Hatoun - Program Mgr Office

• Workflow authoring scenarios
• Sample business processes
• Demo
• Describe Dev Steps
• How to build out in Visual Studio

• 2:30 — Workflow authoring solutions
…………○ Out of box -
……………………§ Routing & Approval: Review/Approve, Sig Collection
……………………§ Office Server Features: List Moderation, Publish Process, Doc Expire
……………………§ Tracking Apps: Issue Tracking
…………○ MSFT Office Sharepoint Designer 2007 Workflow (not in this presentation)
……………………§ Info Workers … simple flows …
……………………§ Custom tracking apps: Service Requests, Asset Track
……………………§ Custom forms actions: Email Notification, Exception Handling
……………………§ Doc Processes: Spec Review, Wkly Status
…………○ MSFT VS & Workflow Software Dev Kit (SDK) (Focus of this presentation)
……………………§ LOB Integration
……………………§ Industry Specific Processes-PO, Prod Life Cycle Mgmt
• 4:30 - Sample Approval Process
• 6:00 - Demo Workflow (User Experience)
…………○ In Sharepoint Site
…………○ Start a workflow, based on an infopath form data
…………○ Shows how you open doc and have a workflow ‘tab/task’ in doc. Also can do in server (not in doc).
• 9:30 Steps to Build
…………○ Model in VS
…………○ Create & Bind InfoPath Forms
……………………§ Association Form
……………………§ Initiation Form
……………………§ Task Completion Form
……………………§ Modification Form
…………○ Deploy to Sharepoint
…………○ Debug running workflow
• 15:00 - Entry points to trigger 4 steps above (infopath forms) reviewed (o12 and sharepoint)
• 18:30 - Deployment Process
…………○ Webpart process used (WSP files)
…………○ Full deployment (not shown here) is to use the solution/feature mechanism vs batch file.
…………○ Activate in sharepoint or in cmd line
…………○ Restart IIS, use
• 21:30 - Debug Overview
• 22:00 - Demo of Building
…………○ Model in VS
……………………§ Windows Workflow Foundation
……………………§ GUI or Code based steps
……………………§ Schedule it in Designer
…………○ Create & Bind InfoPath Forms
……………………§ Template designer in Infopath
……………………§ Drag and drop functionality
……………………§ Ability to interact w/ server, XML files, DB much like standard ASP forms
……………………§ Create a class on form to enable access to data of form
……………………§ Workflow post puts data into workflow properties bag … create a handler for that activity
……………………§ 44:10 - Deploy
……………………§ 46:30 - Debug
• 48:30 - Additional Resources
…………○ WS310 - Next Step Class
…………○ From Lendl
……………………§ Beta1 Refresh
……………………§ Office BetaPlace Access
Eilene Hao - Program Mgr Office
George Hatoun - Program Mgr Office

• Workflow authoring scenarios
• Sample business processes
• Demo
• Describe Dev Steps
• How to build out in Visual Studio

• 2:30 — Workflow authoring solutions
…………○ Out of box -
……………………§ Routing & Approval: Review/Approve, Sig Collection
……………………§ Office Server Features: List Moderation, Publish Process, Doc Expire
……………………§ Tracking Apps: Issue Tracking
…………○ MSFT Office Sharepoint Designer 2007 Workflow (not in this presentation)
……………………§ Info Workers … simple flows …
……………………§ Custom tracking apps: Service Requests, Asset Track
……………………§ Custom forms actions: Email Notification, Exception Handling
……………………§ Doc Processes: Spec Review, Wkly Status
…………○ MSFT VS & Workflow Software Dev Kit (SDK) (Focus of this presentation)
……………………§ LOB Integration
……………………§ Industry Specific Processes-PO, Prod Life Cycle Mgmt
• 4:30 - Sample Approval Process
• 6:00 - Demo Workflow (User Experience)
…………○ In Sharepoint Site
…………○ Start a workflow, based on an infopath form data
…………○ Shows how you open doc and have a workflow ‘tab/task’ in doc. Also can do in server (not in doc).
• 9:30 Steps to Build
…………○ Model in VS
…………○ Create & Bind InfoPath Forms
……………………§ Association Form
……………………§ Initiation Form
……………………§ Task Completion Form
……………………§ Modification Form
…………○ Deploy to Sharepoint
…………○ Debug running workflow
• 15:00 - Entry points to trigger 4 steps above (infopath forms) reviewed (o12 and sharepoint)
• 18:30 - Deployment Process
…………○ Webpart process used (WSP files)
…………○ Full deployment (not shown here) is to use the solution/feature mechanism vs batch file.
…………○ Activate in sharepoint or in cmd line
…………○ Restart IIS, use
• 21:30 - Debug Overview
• 22:00 - Demo of Building
…………○ Model in VS
……………………§ Windows Workflow Foundation
……………………§ GUI or Code based steps
……………………§ Schedule it in Designer
…………○ Create & Bind InfoPath Forms
……………………§ Template designer in Infopath
……………………§ Drag and drop functionality
……………………§ Ability to interact w/ server, XML files, DB much like standard ASP forms
……………………§ Create a class on form to enable access to data of form
……………………§ Workflow post puts data into workflow properties bag … create a handler for that activity
……………………§ 44:10 - Deploy
……………………§ 46:30 - Debug
• 48:30 - Additional Resources
…………○ WS310 - Next Step Class
…………○ From Lendl
……………………§ Beta1 Refresh
……………………§ Office BetaPlace Access
* 50:00 Q&A.

April 25, 2006 Posted by bauertim | Uncategorized | , , | No Comments

MSFT: Biztalk (BTS) and Business Activity Monitoring (BAM)

Watched “MSDN Webcast: Using the Business Activity Monitoring Tracking Profile Editor (TPE) Tool and APIs in BizTalk Server 2006 (Level 200) this morning. Here is the link

http://www.microsoft.com/events/EventDetails.aspx?CMTYSvcSource=MSCOMMedia&Params=%7eCMTYDataSvcParams%5e%7earg+Name%3d%22ID%22+Value%3d%221032292405%22%2f%5e%7earg+Name%3d%22ProviderID%22+Value%3d%22A6B43178-497C-4225-BA42-DF595171F04C%22%2f%5e%7earg+Name%3d%22lang%22+Value%3d%22en%22%2f%5e%7earg+Name%3d%22cr%22+Value%3d%22US%22%2f%5e%7esParams%5e%7e%2fsParams%5e%7e%2fCMTYDataSvcParams%5e


In short, I continue to refresh my understanding of where MSFT is around this specific enabler because we have a building set of clients that are assessing automation of business processes that includes the ability for management to have visibility into the process. That is where the BAM module comes in. Nothing more than a packaged set of functions (TPE), tables and services that you could build custom … but probably cheaper and more powerful via the product.

My high level notes are as follows:

Quote:
MSDN Webcast: Using the Business Activity Monitoring Tracking Profile Editor (TPE) Tool and APIs in BizTalk Server 2006 (Level 200)

Pasted from <http://www.microsoft.com/events/webcasts/calendar/MonthView.aspx?audience=Developer>

• 1:50 — Again the visibility slide to drive automation in process
• 3:22 — Tools / Roles
…………○ BA - Observation Model
…………○ Tech - Map Model to API’s
• 5:17 — BAM API’s — 4 layers
…………○ Direct (visibility, no latency)
…………○ Buffered (high throughput, some latency)
…………○ Message (high throughput, pipeline participation, logical unit of work commit / tracking .. Avail since biztalk server 2004 sp1 )
…………○ Orchestration — similar to msg but only avail in biztalk envir
• 10:50 — EventStream API detail
…………○ Begin, Update, End, Add, Enable Continue, Add reference, Flush
• 14:18 — Sample Activity Overview (PO)
…………○ 3 milestones (recv, approved, ready)
…………○ 2 data items (customer name, product)
• 15:36 — Sample of code you would do to send events to BAM to track (from the native process)
• 17:51 — Overview of the BAM tables updated
• 19:00 — Demo of BAM API
…………○ Not so good
• 23:45 — Shipping Demo
…………○ Example of continuation (corralate events from multiple applications / orchestrations). In short parent child relationships relative to what are seens as distinct processes in the org
• 32:30 — Tracking Profile Editor (TPE)
…………○ TPE — In 2006 how to get away from code
…………○ GUI Tool
• 34:20 — Demo of TPE (create a TPE Profile)
…………○ In BizTalk
…………○ Select events to use in the flow
…………○ View assemblies / and pipelines and select various steps to make them into milestones
…………○ Tracking pipeline, schedules, and orchestrations, and orchestrations (can BAM across all)
…………○ 44:00 — Discuss how data pulled from message payload for bam (to continuation created) out of schema
…………○ 46:00 — relate activities in BAM (just name them similar, and map keys together)

April 20, 2006 Posted by bauertim | Uncategorized | , , , | No Comments

MSFT: Biztalk (BTS) - New Features

Watched this webcast this morning:

Quote:
Whats New in the Biz Talk Server 2006 Messaging Engine — Richard Seroter - MSFT — http://blogs.msdn.com/RichardBPI

Was a pretty good webinar 49 minutes w/ q&a after that. Looks like BizTalk is coming of age in the EAI space (TIBCO, WBI, Webmethods, etc). We have seen a larger volume of customers embracing it as thier message bus for key apps in the last six to nine months.

Here is the link:

WEBCAST LINK

Here are my detail notes:

Quote:
Whats New in the Biz Talk Server 2006 Messaging Engine — Richard Seroter - MSFT — http://blogs.msdn.com/RichardBPI

• 2:44 — Overview of notable new features in biztalk 2006 (vs 2004)
Messaging Engine
…………○ Orchestration Engine
…………○ Pipelines
…………○ Adapters (available in the box to MF and other notable 3rd party systems)
• 4:27 — Race conditions (ordered processing) … to insure messages are ordered based on packet info
• 6:00 — Demo (ordered processing)
• 13:22 — Demo ends. Talk of how ordered processing can do clustered for high avail
• 14:00 -0rchestration (convoy’s) discussed
• 16:00 - Discuss interchange processing
…………○ In 2004 fail on batch (all or none)
…………○ In 2006 can process around bad transactions (suspend queue) in batch file
• 17:43 - Demo of interchange procesing
…………○ 20:01 - Shows (in demo) integration of email/infopath/and sharing of messages (not bad)
…………○ 23:00 — Shows pipeline and how you can change @ run time (in visio vs in 2004 had to change files) .. Adds suspend queue to his demo to handle bad transactions
…………○ 25:45 — Shows how to debug and view transactions and actually have re-processing occur (to fix known problems)
• 28:00 - Failed message routing
…………○ In 2004 couldn’t subscribe to that message (to fix) .. Just notification
…………○ In 2006 can subscribe for certain msg failures for resolution (and filter based on data - like xyz customer)
…………○ 29:59 - Demo of this
…………○ 37:02 - Demo ends … review key points hit … key point ability to resume a suspend msg (04 could do outbound only)
• 38:30 - Large Msg Handling
…………○ Note, recommendation to use sqlserver 2005 x64 when get frequent out of locks on this type of work
…………○ Ability to map large files to disc (used to be 1Mb standard in 04) to not swamp memory
• 42:23 - Ability to throttle not buried in registry and now just for all or none … can now do host level throttling.
• 44:30 - Discussion of how to prioritize msgs from specific systems
• 48.21 - Review of materials biztalk focused resources should subscribe to

April 16, 2006 Posted by bauertim | Uncategorized | , , | No Comments

MSFT: Biztalk (BTS) - Business Activity Monitoring (BAM) Overview

A slow presentation (set it to 2* speed and it works well Wink … seriously … a nice feature you should leverage in playback) but towards the end the business value of this technology became more self evident.

Specifically the value of Business Activity Monitoring (BAM) for business management is the ability to dynamically setup of alerts (that they can change w/ a couple clicks) on monitored processes in thier org. Think about all the manual processes (or semi manual) that flow through an org today. Where does management want insight? Where do they think there is risk of unethical behavior? What is the $ risk of that occuring.

Here is the link to the discussion:

https://www118.livemeeting.com/cc/_XML/partners1/view?id=3330&fmt=dll&pw=f48dc8

If that doesn’t work goto partner central and search for this in training:

    Event Title: BizTalk Server 2006 Business Activity MonitoringRecorded Date: 12/13/2005Duration: 60 minutes

Here are my notes from the discussion:

Quote:
Business Activity Monitoring

(BAM) - BizTalk 2006 (BAM).

MSFT Webinar.

**BAM 2004 vs BAM 2006, biz talk orchestration and msging covered.
**claims (interesting angle) that there is process automation in the typical org (xls macros, sas, etc)

**Visability
**4:36 — Basics of a value proposition is value of visibility of a process can drive automation (BAM)
**Example of process that crosses divisions, systems, and branches … but how does business owner see where a process is for a given transaction … manual intensive issue
**BAM instruments all processes (small changes in each system state). KPI metrics from that tied to business focused questions on state of transactions.

–BAM is to Business Events what OLAP is to Reporting. Viewing complex data on current business events.
–Create views of BAM Activity by Role in org.

–BAM 2004 overview — business resource activities created (and views) created in xls. IT rsrc used BAM utilitiy to create BAM infrastructure to track that in Database. Then the business resource views via a live xls.

–BAM 2006.
–1–Data can be viewed via webparts and/or ODBC integration.
–2–Alerts on significant event or data point
–3–Out of box dashboard (webparts). 2004 had a basic webpart.
–4–Native integration to Biztalk messages (no changes required for apps that base on BizTalk). Add instrumentation step into Biztalk pipeline (config vs code).
–5–(coming) integration to SQL Reporting Services.

–Business User .. Viso/Excel still used to create observation model. Called ODBA.

–demo 24:50
–issue on 29min … so skip to 30 minutes.
–31:40 samples of xls reporting … how to create a view by a business owners.
–BAM Manager is still command line to deploy (interesting).
–Deploy produces XML config script in effect … based on xls workbook def

–Nice feature (self service on alers)
–39:13 portal view in sps viewed … allow you to to search all transactions being tracked in BAM… filter by fields on transaction … can also create on the fly different alerts or subscribers. Nice.

–43:00 another snafu … didn’t have data yet … doh!

–44:00 detail discuss of alert functionality. Using SQL Analytic Services to drive this. For example alert on PO > $100.

–Again here is business value … management visability to transactions that they are concerned about … slippage, high $, etc. Key is figuring out what the business mgmt would like to know about processes that are going on (could change over time) and enable BAM to watch for it on thier behalf.
–POS is best example …

–53:00 … alerts continued … instance query alerts ..

April 14, 2006 Posted by bauertim | Uncategorized | , , , | No Comments

Demand Planning Case Study

Here is an example of a bad egg (webcast) focusing on how Cole Industries moved to a forecasting solution over 2002 to 2004. Demand planning solutions is always of interest in the manufacturing space (BI/Tech riddle) so it seemed to be something worthy of looking into.

Unfortunately the webcast was too slow, too little critical thinking about what they did and how it translates to the audience, etc. So, I wouldn’t rate it too high. However, I did hear two notables:

  1. Good Case Study: Cole Industries is a good example for manufacturers that are considering how they focus more on their retail (or partner) channels. In effect, pondering how to begin to behave more like a retailer and less like a mfg.
  2. Good Baseline: For the layman it is a very detailed, entry level discussion of drivers around replenishment and demand planning drivers.

If you are interested here is the link:

WEBLINK

I also uploaded the associated white paper … Synchronizing Store-DC/Warehouselet me know if you have thoughts.


*** RAW NOTES ***
Synch Store / WHSE DemandJohn Broemman - Cole - Sr Dir IT
Gene Alvarez - VP Tech Research / Sales Strat - META
Bob Stoffko - Cole - Dir DW & Fin SysSlide 1 - META
…………○ Economic Uncertainty = Inventory Uncertainty
…………○ Predict spending demand
…………○ Move from supply to demand focus
…………○ “Sense & Reply” environment
• Slide 4 - CPG View of Demand (cg company/retailer)
…………○ Each link in supply chain adds safety stock to the true end customer demand … which drives need to see the end need throughout the chain (Collaborative Demand Planning)
• Slide 5 - Understanding Customer Demand
…………○ Engage / Transact / Fulfill is the chain META talks to
…………○ Need multiple views of demand
• Slide 6 -
…………○ Discuss variables that drive customer demand patterns. Behaviors, placement, regional demographics, etc
…………○ Shipping information is being used as a parm for demand models but it shouldn’t be
• Slide 7 -
…………○ Demand response cycle shortens to 1wk by 2010 (per META) … versus 6 months in 1995 or 1 month today. This is supported by Dell, for example, investing in their MFG plant agility (build to order in days). Not a one size meets all but you get the jist.
…………○ RFID could play a role in early communication from customer end of demand chain … sense capability … change mix upstream since there could be days just in shipping time starting in end mfg (stop or start)
• Slide 8
…………○ Shipping forecasting is only for transportation .. Not for demand
…………○ Don’t do demand forecast w/ one or two variables (like promotions, product, location, season, demographics, trend, weather patterns, etc)
…………○ Focus on ship levels could create service level illusions (sell out in wk1, 100% service level, but if you cant ship by wk2 … you miss 1 wk of demand … even though svc level stays @ 100% … if you focus on shipments … you might believe you are meeting demand … so you need to see demand at a lower granularity (days) which then impacts turns, lift and out of stock metrics
• SKIP to slide 14 (too slow) - COLE SEGMENT
…………○ Cole National -
……………………§ Cole Managed Visions (PBM)
……………………§ Things Remembered (Retail)
……………………§ Retail Optical - Vision providers primarily (sears, target, bj’s, pearle, cole managed vision). Started making keys.
…………○ Why did they invest — Shift from MFG to RETAILER (and what does that mean)
……………………§ Why shift? If they didn’t sell well their MFG capability and associated stats (turns, out of stock, etc) would be underperform
…………○ Guiding Principles
……………………§ Common Solution for all business lines.
……………………§ Single version of report truth.
……………………§ Best of Breed Solutions (not 1 ERP)
……………………§ Pkg focus (no mods)
…………○ Core Business Impacts and Benefits
……………………§ Lab Replenishment was focus … nice detail slide (but not covered)
……………………§ Teradata DCM solution was picked and Microstrategy … and JDA for retail Item Hierarchy
…………○ Slide 25 - Nice roadmap … showing how 3 pieces above (DCM etc) rolled out
…………○ DCM Overview
……………………§ Contribution Analysis (units, $, GM $)
……………………§ Seasonal Profile
……………………§ Rate of Sale (Weekly Demand Rate)
……………………§ Forecasting and Replenishment

April 4, 2006 Posted by bauertim | Uncategorized | , , | No Comments