ACTION 3.12 -The SUWG was asked to develop a training plan and start work to plan a Launch event for the team.
The SUWG had recognised a need for early action to establish a firm, and widely accepted set of core concepts for Product Structure and Approval, which could act as the skeleton for linking other modules. This issue was wider than PLCS and may need several meetings to:
· Win agreement from other parties to co-operate
· Develop work plans and agree work sharing
· Develop the necessary technical products (e.g. Modules, Implementation Guides etc.)
There is lots going on in this area including work by Vendors. Known initiatives include – Mil Spec 2549, PDML, the PDM Schema, AP208, OMG “PDM Enablers”, AP232, AP203 Extension, AP214 and 212, NO CM Model, UK new CM Def Stan (00-57 Version 4), POSC Caesar, and Boeing work on DCAC. The ATA Tech Info Coordinating Committee has (or should have) a strong interest
There seems to be a widely recognised requirement for a core set of principles and concepts for defining and managing product structure (configuration) and approval (change) over the full life cycle.
Howard Mason noted that SC4 had addressed this topic at technical fora on Product Identification (Bad Aibling) and Product Structure (Beijing) but these had not resulted in specific follow-up actions. They would probably be willing to sponsor a “CM Summit” to develop a Statement of Requirement and a Roadmap for improved co-operation in this area.
It was agreed that PLCS should initiate this by developing a paper to define the problem and propose a way forward. Success would depend on clear support from the major industry and government players who “drive” the CM world. These include US DoD and other Defence Ministries, the major aircraft and equipment suppliers: Boeing, Airbus, Lockheed etc and the Shipbuilding community. This meeting would need careful preparation.
Nigel Shaw noted that PLCS might need to lead similar rationalization activities in the other PLCS business areas.
ACTION 3.13: John Dunford to develop a proposal for SC4 to call such a meeting, for review by PLCS sponsors and the SC4 Change Management Group.
This model is needed early to define the precise scope of PLCS, and hence to improve understanding of what interfaces and inter-operability PLCS will support. (The PWI Report and the STR both address this issue, but more work is needed).
ACTION 3.14: It was agreed to call a workshop to begin development of the PLCS AAM Target 2/3 June at EPM premises in Oslo (just before the next SC4 meeting in Lillehammer). Nigel Newling will lead, with help from RR. The session will be announced through the SC4 exploder.
Purpose of the session will be – to review inputs; to define a Scope, Viewpoint and Purpose for the PLCS AAM; to develop the “top box” and (at least) a first level of breakdown. The team should also consider updating the usage scenarios and begin to address the degree to which Vendor products can meet the emerging requirement.
The Oil and Gas Industry will also meet in Oslo - Friday 4th June – JD agreed to offer a PLCS update (through DNV).
A further meeting of the SUWG is needed to continue development of the TDP, SET Up Plan and Risk Register; to develop the Year 1 Work Plan and to prepare the project Launch event
ACTION 3.15: – Howard to call a further SUWG session, when resource information is provided.
BAe has the action on IMS through Jonathan Waite. It was noted that IMS offers more than just European funds - it is widely recognised and would strengthen PLCS credibility as a true International program. LSC were keen to help establish PLCS as an IMS program.
To become an International project PLCS will need support from IMS in US. Joan Wellington from NIST is the contact. Jim Crawford has already opened discussions.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.