[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS TC Call For Participation - OASIS PLCS TC
A new OASIS technical committee is being formed. The OASIS Product Life Cycle Support Technical Committee (PLCS TC) has been proposed by the following members of OASIS: Mike Newton, UK Ministry of Defence; Jerry Smith, US Defense Information Systems; Jim Crawford, Lockheed Martin; King Yee, Boeing; and Howard Mason, BAE Systems. The proposal for a new TC meets the requirements of the OASIS TC Process (see http://oasis-open.org/committees/process.shtml), and is appended to this message. The proposal, which includes a statement of purpose, list of deliverables, and proposed schedule, will constitute the TC's charter. The TC Process allows these items to be clarified (revised) by the TC members; such clarifications (revisions), as well as submissions of technology for consideration by the TC and the beginning of technical discussions, may occur no sooner than the TC's first meeting. As specified by the OASIS TC Process, the requirements for becoming a member of the TC are that you must 1) be an employee of an OASIS member organization or an Individual member of OASIS; 2) notify the TC chair of your intent to participate at least 15 days prior to the first meeting; and 3) attend the first meeting of the TC. For OASIS members, to register for the TC using the OASIS collaborative tools, go to the TC's public page at http://www.oasis-open.org/committees/plcs and click on the button for "Join This TC" at the top of the page. You may add yourself to the roster of the TC either as a Prospective Member (if you intend to become a member of the TC) or an Observer. A notice will automatically be sent to the TC chair, which fulfills requirement #2 above. You may join a TC at any time after the first meeting, but in order to be a voting member at the first TC meeting you must a) register at least 15 days before the first meeting and b) attend the first meeting. Note that membership in OASIS TCs is by individual, and not by organization. For non-OASIS members, a public comment list plcs-comment@lists.oasis-open.org is available for the public to make comments on the work of this TC; the public may subscribe to this list by going to the mail list web page at http://lists.oasis-open.org/ob/adm.pl. The archives of the TC's private and comment mail lists are visible to the public at http://lists.oasis-open.org/archives/ Further information about this topic may be found on the Cover Pages under the topic of "Product Life Cycle Support" found at http://xml.coverpages.org/productLifeCycle.html -Karl ================================================================= Karl F. Best Vice President, OASIS office +1 978.667.5115 x206 mobile +1 978.761.1648 karl.best@oasis-open.org http://www.oasis-open.org 1. Name of Technical Committee: OASIS Product Life Cycle Support (PLCS) Technical Committee 2. Statement of Purpose: The purpose of the OASIS Product Life Cycle Support TC is to establish structured data exchange and sharing capabilities for use by industry to support complex engineered assets throughout their total life cycle. These Data Exchange Sets (DEXs) are based upon ISO 10303 (STEP) Application Protocol 239 (Product Life Cycle Support). The OASIS Product Life Cycle Support TC will be responsible for defining, developing, testing and publishing of OASIS Product Life Cycle Support DEXs, and for liaison with ISO TC 184/SC4. The OASIS Product Life Cycle Support TC will coordinate these activities with relevant OASIS Technical Committees and promote the use of OASIS Product Life Cycle Support DE’s across industries and governments world-wide. The scope of the information content of STEP AP239 covers: * The identification and composition of a product design from a support viewpoint; * The definition of documents and their applicability to products and support activities; * The identification and composition of individual products; * Configuration management activities, over the complete life cycle; * Activities required to sustain product function; * The resources needed to perform such activities; * The planning and scheduling of such activities; * The capture of feedback on the performance of such activities, including the resources used; * The capture of feedback on the usage and condition of a product; * The definition of the support environment in terms of people, organizations, skills, experience and facilities This content relates to many of the transactions required to order, supply and pay for the necessary resources and activities required to operate and maintain the products. Individual DEX development teams will be encouraged to liaise with relevant OASIS TCs to ensure that consistent data definitions are generated. The business goal of the PLCS TC is to satisfy three significant requirements for owners/operators of complex products and systems such as aircraft, ships and power plants, namely: * Reduction in the total cost of ownership * Increased asset availability * Effective information management throughout the product lifecycle PLCS, Inc., a Delaware Corporation, has been the developer of the ISO 10303 Application Protocol 239 and has begun the development of several PLCS Data Exchange Sets. The members of PLCS, Inc. plan to close the corporate entity after October 31, 2003 and in accordance with their membership agreement intend to place all remaining intellectual property in the public domain. It is the intent of the proposers to continue the work of PLCS, Inc. on DEX development and DEX standardization in the OASIS PLCS TC, and we intend to make the appropriate contributions of existing work in accordance with the OASIS TC Process and IPR Policy. 3. Schedule of Deliverables (Year 1): The proposers have identified more than 30 candidate DEX specifications to meet particular industry needs. The current prioritisation for the development of those DEXs lead to the following proposed list of deliverables for the OASIS PLCS TC. D001: Product Breakdown for Support 1st Quarter 2004 D002: Functional Structure and Related Faults 1st Quarter 2004 D003: Tasks Linked to Product 1st Quarter 2004 D004: Work Schedule 1st Quarter 2004 D005: Maintenance Plan 2nd Quarter 2004 D006: Product as Realized 2nd Quarter 2004 D007: Task Set 3rd Quarter 2004 D008: Support Drivers 3rd Quarter 2004 D009: Failure Feedback 4th Quarter 2004 D010: Extended Task Set 4th Quarter 2004 Other possible DEXs include: System Requirements, Product Design, Part_definition_information, Part_with_state, Part_with_interface, Part_as_Individual, Variant Specification, Change Definition, Product Behaviour, Product Status Report, Role Configuration Option, Work management, Work Request, Work Order, Work Definition, Resource Schedule, Resource availability, Support Solution, Feedback Reports, Activity Report, Resource Report, Work Justification, Impact Assessment, Risk Assessment, Work Justification, Intended Product use, Actual product use, Support Resources, Support Personnel, Support Organisation, Support Facility, Allowance, Support Opportunity, Product Behaviour (Component), Product Behaviour (Assembly), Resourced_Task_Specification, Support Solution Justification, Support Opportunity Types, Actual Support Opportunity 4. Language in which the TC will conduct business: English 5. Date and time of first meeting: September 26, 2003, 9:00–5:00, in-person Lockheed Martin Facility in Manassas, Virginia 6. Meeting schedule: DEXs will be developed by subcommittees of the TC that will meet as required. The TC will conduct a monthly conference call for status updates and planning. The TC will conduct two in-person meetings in 2004 7. Names, electronic mail addresses, and membership affiliations of at least three Eligible Persons committed to the stated meeting schedule: Mike Newton, mn@modils.demon.co.uk, UK Ministry of Defence Jerry Smith, smith5j@ncr.disa.mil, US Defense Information Systems Jim Crawford, jim.r.crawford@lmco.com, Lockheed Martin King Yee, king.g.yee@BOEING.com, Boeing Howard Mason, howard.mason@baesystems.com, BAE Systems 8. Name of TC Chair: Chair: Howard Mason Vice Chair: Jerry Smith 9. Names of phone meeting sponsors: Jim Crawford Howard Mason 10. Names of in-person meeting sponsors: Jim Crawford Howard Mason
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]