BuildingServicePerformance: BSP Pre-kickoff Conference Call - Fri 2008-05-30    (1I7H)

Conference Call Details:    (1I7I)

Attendees    (1I7Q)

Proposed Agenda Ideas    (1I4W)

(please insert your suggested agenda items below)    (1I4X)

Agenda & Proceedings    (1I7R)

1. Meeting called to order:    (1I7S)

2. Roll Call:    (1I7W)

3. Agenda:    (1I7Y)

A lot of thoughts and discussions in the last few days    (1IDS)

Michelle takes the chair, Deborah taking notes    (1IC4)

Agenda today: Kick-Off meeting, getting pressure from Ontolog to be open for business Talk about mission and charter Take bullets in order - see insertions above Clarifying the charter has to be the first big thing    (1IC5)

Mission Statement and Charter, see link above    (1IC6)

Mission as it reads now (see other page): Correcting grammar Information resources connection focused on service performance Describe performance requirements    (1IDT)

Need reference to primary clients Business, standards organizations, subsets of those, others not identified    (1IDU)

Who we deliver this to and who needs to be involve to make it happen?    (1IEE)

Because BIM and surrounding information are lifecycle, clients could be anyone within lifecycle which is broad Helps to have some target within that mirrored matrix    (1IDV)

One possability is to scope on services within a specialty area Or to scope on the types of data to interact with Opposed to particular phase of lifecycle, for example, Honeywell is services after construction Other services are not part of the building itself Some exchanges are based on people doing actual construction    (1IDW)

General idea of integrated lifecycle model and ontologies - drives the data and Q&A    (1IDX)

Early decisions made in design ripple through the entire process    (1IDY)

Think local and global, allows you to have layers that can be prioritized Better precision at entry to the design process, saves cost Get decisions made early, intelligently, smartly Have to be decisions that are made in terms the owner can make In terms the owner can understand, talk about things the owner cares about    (1IDZ)

Overlaid on the foundation is a secondary concept that systems are in flux Radically different technologies, may be low bid vendor, No way to tie what we're asking for to what is actually provided - YET    (1IE0)

Most building owners don't care about sustainability unless can get higher rent, if it can't do that, doesn't matter Has to be expressed in value transferred from the tenants to owner also    (1IC7)

Three Legs -    (1IC8)

Design has to talk to the Owner, about business services where they can harvest value and the tenant has to want whatever it is,    (1IC9)

Clean purpose at early design phase (Architect)    (1ICA)

Fire prevention and safety management not quite as stark. Feds for example want to contract based on performance across the board but don't know how to describe it. Use business words to describe - hence the ontology requirements and means of communicating.    (1ICB)

Does the Owner have a new role? Cx agents are very important, create the right words for people to talk about and problems go away. Nobody commissions the front door or walls standing up. Its only the complex systems that need to be measured.    (1ICC)

Need the terminology of services - Healthy Office Building Index - reapplied and made more real so it can be touched by higher level abstracts.    (1ICD)

Its a well known fact a government agency in an office building there are too many file cabinets - Government building? OK more structural support but today can't talk about responding to breathing or other performance qualities the same way.    (1ICE)

Actual data types we need:    (1IEF)

Pathways to pre-established to answer questions, benefit public interest, what we need to understand    (1IEG)

Performance - and the 3 takes off from there - have a definition of the purpose for any stage of lifecycle    (1IEH)

Is it performant? What is its purpose? Need purpose definition Need to show that its performant and therefore talk about those benefits Benefit measurements, way to describe the measurement of the benefit If going to talk to real people in real roles need to report those metrics back to them.    (1IEI)

Provide metrics reporting    (1ICF)

Purpose Definition Benefit Measurement Method Metric Reporting    (1ICG)

All of that is to get at being able to define what is performance.    (1IEJ)

Define what the purpose and benefit of the service, then be able to show if you have or have not met that benefit    (1ICH)

Rex and Peter have just joined.    (1ICI)

Got to be careful about locking in on the metrics which is a constant temptation Assume a healthy building is a good thing, can think about aspects of it, features of a space and ventilation, temperature and humidity index - how to swallow a new measurement? ASHRAE should engage that subject.    (1ICJ)

Not down to level of defining every one, what we are doing is creating ontological framework for defining    (1IEK)

First goal is to create the framework to hold things for benefit measurement    (1IEL)

Not always looking at from abstraction point of view Realistic example populated with real service/real data    (1ICK)

Use framework to create IDMs - that would be a successful result    (1ICL)

Reference information model in emergency management technical committee in OASIS Be careful to define level of abstraction you are working at.    (1ICM)

Define a category in there, so many metrics fall into that    (1IEM)

Necessary in charter or statement of work is to identify that level correctly Concrete measurements can be used, compiled and measured    (1ICN)

Beyond the model of what those categories are Tie that back to the purpose of the service Automatically include in the structure those relationship From a category, has some characteristics    (1ICO)

Use OmniClass, do not reinvent the wheel to say what things are The framework is not out of thin air, some structures do already meet our needs Have we investigated whats there?    (1ICP)

For purpose of this discussion of just mission statement, then moving into the charter    (1ICQ)

Connecting the information resources for building service Define how to describe the performance requirements to develop simple ontologies and code/classification templates - actual text will be entered on wiki after meeting - Will be on a page by itself on wiki, the project mission is a link from main page The working statement, other than grammar, just talked ourselves back through. Has been out there for 3 weeks.    (1ICR)

As far as the charter, has anyone done a draft charter page? Bob added some last night. Toby, says project mission is lacking, describes how to develop and classify, but need to include recognizing success What is the purpose of the performance metrics? Recognizing and rating Performance requirements and.....results    (1ICS)

Rex - this is 3rd or 4th group with idea of ratings based on some kind of feedback and objective standard Should look at - Integrated response services consortium - Open Ontology Repository for gate - new OASIS technical committee end to end planning to provide evaluation criteria    (1ICT)

Go look at these other frameworks    (1ICU)

Focused on one space which is buildings and facilities Quality of service evaluations    (1ICV)

Talking about the tenant understanding later    (1ICW)

Describing the performance requirements, metrics, and quality of service    (1ICX)

Developing simple and ontology and code classification templates    (1ICY)

Next step is to try and use in a lot of really hard ways.    (1ICZ)

Peter - is mission kept to ontology and classification or should take first step and redefine mission to larger scope? Recommended process for bulk of ontolog forum is just a discussion group. Within discussion there are particular projects. For example the core component type representation on CCT-Rep was an exercize to build and map ontology    (1ID0)

Leave as this is our high level mission, a sub task group could be spawned also    (1ID1)

PPY continues - you can spawn subprojects that are task oriented, or a standards group, which actually continues to mapping into standards. Not under Ontolog, became and OASIS standard, then OOR gets incubated at Ontolog, from Day 1 sees itself as outside because it has to perpetuate and maintain itself. Ontolog provides incubation space and discussion to foster and spin off into separate efforts.    (1ID2)

As long as you are within the Ontolog infrastructure CWE, have to be open, transparent, inclusive    (1ID3)

So we get to the open, we need to get to kick off - take draft charter page to work offline? Setting up when the kick-off should be?    (1ID4)

As long as there is a charter and mission for people to look over and decide if they want to participate. Not as formal as OASIS. We use similar process but do not have to stick to letter, keeping spirit    (1ID5)

Bob's design thought in draft charter, looked at Ontolog charter, announcement for emergency response at OASIS - see references tried to put threads with important distinctions and instance announcements The four bullets at top start with same words from 2002 to kick off Ontolog, minor changes to move towards our mission and charter Enhancement and extension, based on the same principles References on ENT did on their announcement    (1ID6)

BSP is an open forum to....    (1ID7)

Covers the basics, discussing practical issues but going toward the development of a formal ontologies and looking at all the different levels. Not publishing drawings and standards. The focus is benefiting related forum Helping to tie together, catalyzing, integrating, benefit from participation by....    (1ID8)

At the end - is a reference number 04? Is an artifact and will be removed.    (1ID9)

The benefit of having a published resource that can be referenced - not sure how to say - but Deborah getting at genuine benefit for the Owner they can refer to in community planning or emergency but a resource you can get to and use    (1IDA)

Strengthening - publish documents not standards.    (1IDB)

Discuss online over the next week to tweak.    (1IDC)

We are small enough can do consensus via email    (1IDD)

Next meeting will be the kick-off, commit enough time for the mission, charter, and agenda    (1IDE)

Toby to send a preamble in email    (1IDF)

Reaching out to people who feel uncomfortable with the word Ontology - vocabulary of value    (1IDG)

In two weeks from today to have - use the draft charter page - when were ready will create a charter page    (1IDH)

Use the wiki to flesh out what we are doing and why but the bare bones are there - send email so folks know to look BSP list to notify But use wiki and working pages to keep everything in one place    (1IDI)

Other folks may want to join in, announce the meeting    (1IDJ)

PPY - question and suggestion - the OOR people, if there is a lot of overlap because they have that date....OOR uses Friday as regular meeting time. Either meet every other Friday with light agenda or every Friday if there is alot. Having panel sessions is an effective way to get people engaged. Changes are OOR could be 3 of 4 Fridays that are at least 2 hours.    (1IDK)

Will be some of the resources we want to be tapping in the OOR, hoping the areas we're looking at could be one of the first domains to start providing material.    (1IDL)

Have committed to Mondays.    (1IDM)

Time is a good slot, so commit to this time and 55 minutes. issue    (1IDN)

Every other week.    (1IDO)

Set for the 16th then.    (1IDP)

4. New Issues:    (1I82)

5. Schedule Next Meeting & Adjourn:    (1I88)

 notes taken by: DeborahMacPherson / 2008.05.23 11:15 pm PDT
 All participants, please review and edit to enhance accuracy and granularity  of the documented proceedings.    (1I8C)

Resources    (1I8D)