This page provides links to some useful resources that help OMG members conduct OMG business. It includes information on subgroup chair responsibilities, the technology adoption process, chartering subgroups, documents and communication.
Topics covered include:
- Chartering OMG Subgroups
- Forming RFP submission evaluation teams
- FTF and RTF Reports
- RFPs and RFP Submissions
- RFIs and RFI Responses
- Meeting Planning
- OMG Email
- Reporting Subgroup Activity at the TC Plenary Meeting
- Tips on accessing OMG documents
- OMG Specifications
- OMG RTF/FTF issue management with JIRA tutorial
Training in using JIRA tools to run your RTF or FTF desktop:
The Ultimate Sources
The ultimate source of information on OMG's process is, of course, the Policies and Procedures of the OMG Technical Process(affectionately known as P&P).
A quick reference to chairing meetings is the vade mecum (produced by our resident Latin scholar). For those so inclined, there is a publicly-available electronic copy of Robert's Rules of Order. (The 11th edition of Robert's is available in your favorite bookstore.)
An additional resource for FTF and RTF chairs can be found in presentation format as OMG document omg/2007-12-01.
Chairs are asked to provide OMG staff with meeting room requirements well before each meeting; use this online form. Chairs must also provide a meeting agenda to OMG staff no later than three weeks before the start of a TC Meeting. Agendas should be posted to firstname.lastname@example.org, which ensures that they will be posted on the OMG Technical Meeting Agendas page. See all events listed here.
Confused about proxies? Click here to learn more.
Reporting Meeting Activity
It is the responsibility of a chair to report his or her group's activity during the week of an OMG Technical Meeting at the appropriate plenary meeting on Friday. A slide template for subgroup reports is available with explanations or without explanations.
OMG Technology Adoption Process
The OMG Hitchhiker's Guide is a useful guide to the OMG technology adoption process. While it was specifically written for those responsible for managing the process, it provides a useful interpretive tool for everyone who participates at OMG.
TC Meeting And Work In Progress Information
A reference page is available for information on future and past Technology Committee meetings and Technology Committee work in progress.
RFPs And RFP Submissions
A template for RFPs is available on the OMG document server. An abbreviated version is available for distribution for AB and Task Force review only. Draft RFPs should be sent electronically to email@example.com. RFP submissions must be mailed to the OMG. The correct mailing address must be specified in the RFP.
A checklist of guidelines to help navigation through the RFP process can be found here.
Several years ago, OMG decided to submit the majority of its specifications to ISO to become ISO standards using either ISO JTC1ís PAS process or ISOís Fast-Track. For a specification from OMG to become an ISO standard, it is highly desirable that it be in a format closely approximating the ISO format. (If it is not in an ISO-like format when the standard comes up for its five year review in ISO, it will be withdrawn). Two templates in regular FrameMaker format and FrameMaker MIF format are available for formatting submissions in the ISO PAS format.
RFIs And RFI Responses
RFI responses must be mailed to the OMG. The correct mailing address must be specified in the RFI.
Business Committee Requirements And Questionnaire
Although not the responsibility of the issuing Task Force, submitters often inquire about two OMG Business Committee (BC) documents related to RFP submissions. The first is the Business Committee RFP Attachment, which identifies the criteria the BC uses when evaluating submissions. This document is included in the RFP template (see above). The second is the Business Committee Questionnaire, which accompanies a RFP submission and is a statement by a submitter of their intention to provide a commercially-available implementation of the adopted specification.
Evaluating RFP Submissions
Guidelines are available to assist Task Forces in forming the work groups (called evaluation teams) that are tasked with evaluating RFP submissions issued by the Task Force and to assist these teams in performing those evaluations.
By policy, neither a Task Force nor Technology Committee can vote to recommend a Revised Submission until at least the second OMG meeting following the due date of the final Revised Submission. However, a vote to recommend at the meeting immediately following this due date may occur provided that the following conditions are met:
- At least one of the submitters makes a formal request in writing (letter or fax delivered to OMG headquarters), at least four weeks before the beginning of the Task Force meeting in question, that the evaluating Task Force conducts a vote to recommend at that meeting. (A template for that request may be found here.)
- The discussion and Task Force vote to consider an adoption recommendation vote appears on the published agenda along with the exact, correct time during which the discussion (and possible vote) will be held (before the plenary meetings).
- The motion to consider voting upon an adoption recommendation passes with at least 3/4 of the Voting List present (or 3/4 of those present and eligible to vote if there is no closed Voting List.) If the motion to consider passes, then the Task Force proceeds with an adoption recommendation vote as normal. If it fails, then the Task Force must wait until its next meeting at the earliest to conduct a vote to recommend.
Normally, a Task Force will wait a meeting cycle before engaging in the vote to recommend in order to adequately digest the submission(s). The intent of the Vote-to-Vote, which is the exception, is to accelerate the adoption process when ìtime to marketî for the specification is a critical factor. The Task Force must weigh this criticality against the quality of the proposed specification.
AB-endorsed guidelines for RTFs and FTFs
Click here for document.
FTF And RTF Final Reports
Click here for a template for FTF and RTF final reports.
Other Forms And Templates
A useful resource for acquiring templates and forms used in various technology adoption processes can be found on the Template Downloads page.
It is the responsibility of a nominated chair organizing a Task Force, Special Interest Group, Subcommittee, Finalization Task Force (FTF) or Revision Task Force (RTF) to make a motion to charter the subgroup at the appropriate plenary meeting on the Friday of a OMG Technical Meeting. Forms are available to assist in making such a motion:
|Task Force, Special Interest Group, Subcommittee||with explanation||without explanation|
|Finalization Task Force (FTF)||with explanation||without explanation|
|Revision Task Force (RTF)||with explanation||without explanation|
The two major means of communications among OMG members and with industry at large are:
- The Internet (OMG's web site and the Technology Committee Subgroup homepages).
- Email (mail lists for subgroups, related activity and individual email).
Some of the more widely used mail lists and their intent include:
- firstname.lastname@example.org - communications with the Architecture Board
- email@example.com - communications with the Domain Technology Committee
- firstname.lastname@example.org - communications with the Platform Technology Committee
Subgroups. Unfortunately, a convention has not been established for subgroup mail list names. Consult the Mail Lists page on OMG's site for the correct spelling of the mail list name for the subgroup you wish to contact.
Mail list subscription / un-subscription is handled by sending email to email@example.com.
OMG members and staff with electronic mail access may be reached by sending email to FIRSTNAME_LASTNAME@omg.org.
Subgroup Chairs may be contacted by appending "-chair" to the subgroup's email list name.
Email requests to OMG staff is an effective (and, in some cases, required) means of conducting business. Some of the more widely used addresses and their intent include:
- firstname.lastname@example.org - Andrew Watson
- email@example.com - submission of meeting agendas
- firstname.lastname@example.org - request for OMG documents
- email@example.com - requests involving demonstration setup at OMG Technical Meetings
- firstname.lastname@example.org - requests for subgroup meeting support at OMG Technical Meetings
- email@example.com - submission of documents (e.g., draft RFPs, RFI responses) to Juergen Boldt
- firstname.lastname@example.org - requests related to the technology adoption process (e.g., LOIs) to Juergen Boldt
- email@example.com - requests to the OMG of a general nature
- firstname.lastname@example.org - communications with Linda Heaton, the OMG's Technical Editor
A few, quick notes about accessing OMG documents.
OMG documents are identified by a document number, which takes the form prefix/yyyy-mm-nn, where:
|prefix:||an abbreviation for the issuing subgroup or a topical area (e.g., "realtime", "omg", "pp")|
|yyyy:||the year of issue (prior to 2000, yy)|
|mm:||the month of issue|
|nn:||the order of issue within the issuing month|
For example, the Business Rules in Models RFI is assigned document number ad/2002-09-13. This means that the issuing group was the Analysis and Design PTF ("ad"); the document was issued September ("09"), 2002; and it was the thirteenth document that A&D PTF issued that month. For a complete listing of subgroup prefixes, consult the OMG TC White Pages.
A complete list of all available OMG documents, updated daily, can be obtained as a text list (WARNING: extremely lengthy.)
Finally, OMG documents may be accessed via URL. To form the correct URL, append the document prefix and number to "http://doc.omg.org/" For example, http://doc.omg.org/ad/2002-09-13 for the example above. This will direct you to a page with links to a choice of formats for the document (e.g. PDF, Word, Zip, etc). Remember that some documents may be not be accessible to non-members.
A Catalog of OMG Specifications exists on the OMG web site for accessing recently adopted and formal (publicly available) specifications.