#DF140 discussing

. We will have a mobile app available with all the details, but here is a summary:

- Wearable Prototype Playground with 10 wearable devices integrated to Salesforce available to try on and experience. We will be taking pictures for fun as you wear the devices. North Hall Booth N1301

- Salesforce integrated eHealth device that monitors BP, blood oxygen, body temperature and has an accelerometer to determine if a patient has fallen. North Hall Booth N1301

- We are unveiling a new solution called SmartStore that leverages BLE, Beacon, Heroku and Salesforce for personalized in-store retail experiences. North Hall Booth N1228

- Get Smart: Drive New Business Value in a Connected World - speaking session Tuesday, October 14, 10:00-10:40 AM at the Yerba Buena Center for the Arts Forum

- Internet of Things Meet-up: Come talk shop and see demos about wearables in a casual setting with experts on Wednesday, October 15, 2:00 PM - 3:30 PM (PDT). Hotel Zetta, 55 5th St, Playroom (Second Floor)

- Wearables Meet-up: Come talk shop and see demos about IoT/IOCP in a casual setting with experts on

Tuesday, October 14, 11:30 AM – 1:00 PM (PDT), Hotel Zetta, 55 5th St, Playroom (Second Floor)

- Download our mobile DF14 app at the show. The app leverages IoT Beacon technology and as you swing by Acumen Solutions and partner booths, attend sessions and attend events you will earn points for prizes including a signed guitar from Bruno Mars!

Look forward to connecting next week. Going to be the best Dreamforce yet!

. The post includes his take on Salesforce data, metadata, and CIO-issued requirements.

You can read it here:

Some excerpts:

"Q: What kinds of requirements are you dealing with in terms of data/metadata integrity, completion, etc?

A: On the data side, history plays a big part. Field tracking may satisfy that for some customer information. But when there’s a financial aspect, organizations require integrity checks. They want to identify the originator of data, to account for its movement, and to detect when it’s modified outside of business processes.

In terms of metadata, engineers just want a normal life with environments for development, staging and production! Classical version control should apply, and the change management process itself shouldn’t be a pain in the ass.

Q: And who is handing down these requirements?

A: Typically CIO or CTO roles.

Q: What happens when these requirements are not met?

A: On a good day, internal staff get flamed for changes made by contractors and vice versa. On a bad day, the need for oversight is quietly forgotten, then data and processes grow more mission-critical. As they slip out of mind under other projects, the game of Russian roulette begins.

For engineers, no system (or a broken system) for metadata management has wide effects beyond environmental stability. Sidelining those requirements results in lack of agility that drives staff away. The ones that stay are treading molasses."

Matt Bingham Blog Post