Slide 1
Content
1. ECSS objectives and policy 2. History and membership 3. ECSS organization 4. Type of ECSS documents 5. Hierarchy of documents
6. Production Cycle
7. Dissemination of ECSS documents
DATE 1st June 2012 Overview of the ECSS system ESA Information day to Slovakia Slide 2
Efficiency
Standards contribute to making the development, manufacturing and supply of products and services more efficient, reliable, safer and cleaner.
Trading facilitation
Standards allow trading between organizations to progress easier and fairer.
Knowledge transfer
Standards aid in transferring knowledge and enhancing engineering capabilities to smaller or developing organizations.
Education
Finally, Standards participate to the education of todays and future engineers when conforming to standards is secured, thus, for instance, avoiding designers "reinventing the wheel".
Slide 4
Slide 5
1993: Industry saw the need to align PA requirements 1993-1994: ECSS TOR signed, and K.O. meeting 1996: First documents
1999: Attempt to apply in Mars Express (not well specified requirements,
set the standards incomplete) 2000: Gibson report 2002: Organisational changes at management level- re-structuration (from Gibson report) 2004: Define implementation method 2005: Necessary set of standards nearly set up 2006: (April) User day showed the necessity to adapt the standards to the user needs 2006: (June) Conclusions of TF1 (for organizational aspects) and TF2 (for the content of the documents) set the basis for the new system: starting of the benchmarking phase 2010: end of benchmarking phase 2010 2012 : Maintenance phase
Overview of the ECSS system ESA Information day to Slovakia Slide 6
Slide 7
European Industry,
represented by
Some organization have an observer role on ECSS, e.g. CEN-CENELEC, EUMETSAT, EDA
DATE 1st June 2012 Overview of the ECSS system ESA Information day to Slovakia
3. ECSS Organization
ECSS structure
Steering Board Executive Secretariat Technical Authority
Network of experts
Slide 9
3. ECSS Organization
Steering board (SB):
Steering Board Executive Secretariat Technical Authority Mission:
Define the objectives, policy and strategy for the ECSS system and for providing overall leadership of the ECSS bodies. Not involvement in approval of standards.
Composition:
Voting members: One voting representative of each member organization, except Eurospace which has four. Non voting members: Chairman, Secretariat and invited observers
Network of experts
Meetings:
At least, twice a year.
Slide 10
3. ECSS Organization
Technical authority (TA):
Mission: Steering Board Executive Secretariat Technical Authority
Guided and monitored by the SB: - it is the approval authority for all changes to existing ECSS Documents, for the initiation and release of new ECSS Documents. - It is in charge to setup and implement the Workplan with the support of the ES. - Define the objectives, policy and strategy for the ECSS system and for providing overall leadership of the ECSS bodies.
Meetings:
Typically, 5 per year.
Slide 11
3. ECSS Organization
Executive Secretariat
Technical Authority
Dedication
Working on a permanent basis.
Network of experts
Composition:
ES is provided by ESA
Slide 12
3. ECSS Organization
Steering Board
Technical Authority
Support
It is expected that each organization gives support to his/her representative in the WG, e.g. by technical correspondents
Slide 13
3 ECSS Organization
The Working Group
Responsibilities and tasks
The Working Group is responsible to draft or update an ECSS Document. The WG is responsible for making the most effective use of the expertise of its members to achieve the best quality Document. In executing its responsibilities the WG shall: a) Agree the NWIP and propose the WG Work-plan (WP); b) Prepare regular progress reports; c) Provide deliverables and intermediate version(s) of the document as in the agreed WG WP; d) Prepare, in consultation with the ES, and submit the draft document to be processed in the TA; e) Review and disposition the comments during Public review and update the document; f) When updating a Document, provide traceability between the new and previous versions; g) Report any identified consequences of the standard on already published Documents; h) Submit the revised document with the report of comments disposition to be processed in the TA; i) Prepare a final report: detailing the results, and lessons learned; j) Prepare a draft article for the ECSS news letter promoting the new or updated Document; k) Nominate, at conclusion of the WG activity (i.e. when the document is published) a Documents Focal Point [name(s)/Organization] who will be in charge and commit to provide support to answer Users queries and analyse feedbacks.
Slide 14
3. ECSS Organization
Network of experts (NoE):
Steering Board Executive Secretariat Technical Authority Mission:
Pool of experts in the ECSS disciplines supported by the ECSS organization nominating them.
Composition:
- DiFP (Discipline focal points): One per discipline, 21 disciplines in total see next slide). - DoFP (Document focal points): For the ongoing documents, the convenor. For the disbanded WGs, a person proposed by the WG before disbanding. - Ad-hoc experts
Network of experts
Slide 15
3. ECSS Organization
Standardization point of contact in ESA
Discipline ESA Discipline responsible M Thomas.Deak@esa.int Q10/Q20 Roberto.Ciaschi@esa.int Q-30 Luigi.Bianchi@esa.int (Roberto.Ciaschi@esa.int) Q-40 Roberto.Ciaschi@esa.int Q-60 Ralf.de.Marino@esa.int Q-70 Mikko.Nikulainen@esa.int Q-80 Lothar.Winzer@esa.int (Roberto.Ciaschi@esa.int) E-10 Frederic.Teston@esa.int E-20 Henri.Barde@esa.int E-30 Michel.Lambert@esa.int E-40 Jean-Loup.Terraillon@esa.int E-50 Gian.Paolo.Calzolari@esa.int (ESOC) E-60 Alain.Benoit@esa.int E-70 Mario.Merri@esa.int (ESOC) U10/U20 Tomasso.Sgobba@esa.int
DATE 1st June 2012
TEC-QR
DIVISION HEAD: Roger.Jegou@esa.int STANDARDIZATION ENGINEERS: ECSS Secretary: Enrique.Gonzalez.Conde@esa.int ESA rep. in the ECSS TA: Joel.Asquier@esa.int Standardization officer engineers: Steve.Bury@esa.int Olga.Zhdvanovich@esa.int DOCUMENT CONTROL & ADMIN Klaus.Ehrlich@esa.int Brid.Samoylove@esa.int Nathalie.Reuze.Witasse@esa.int
Slide 16
S - system
Branches
Define the system of standardization documents, and specifies how to use it in Space projects The project manager is responsible for the achievement of the totality of the project objectives and specifically for quality organization and its timely and cost effective execution Product assurance is responsible for the implementation of the quality assurance elements of the project and other activities like dependability, safety, parts, material and processes, software, and audits Engineering is responsible for the definition of the end product, verification that customers technical requirements are achieved and in conformance with the regulation and company constraints The U branch is providing requirements and principles for a continuous sustainability of the space environment in order to ensure appropriate and safe present and future of space activities.
M - management Q - product
assurance
E - engineering
U - sustainability
DATE 1st June 2012
Slide 17
for direct use in invitation to tender which are documents for direct use in invitation to tender and business and business agreements agreements for implementing space related activities.
Their content is strictly limited to the statement of verifiable customer requirements, supported by the minimum descriptive text necessary to non-normative documents providing guidelines which are non-normative understand their context. documents providing background information, advice or recommendations and/or collection ofrelated datato a specific discipline or technique, technology, process or activity. Two which types are non-normative of handbooks are documents considered providing in ECSS: usefull (1) Guidelines information togood the non-normative documents providing usefuland info practices, space community and (2) Collection on a specific of data. subject. or data not yet mature for a data standard They are prepared to record and present which areor not handbook relevant for a standard or handbook, or not yet mature to be published as standard or handbook
Slide 18
Supplier Customer
Contractual relationship
Supplier
Customer
Slide 19
TWO types of handbooks: (1) guidelines and good practices, and (2) Collection of data
Technical Memorandum
A Technical memorandum is a specific document providing useful information to the space community on a specific subject. It is prepared to record and present non-normative data which are not relevant for a standard or for a handbook or not yet mature to be published as handbook or standard.
Slide 20
Slide 21
Slide 22
Slide 23
Slide 24
Slide 25
Slide 26
Slide 27
Home provides Organization provides Standards provides Discussion Forum: HBs and TMs provides ECSS Helpdesk: Facility for information on: information on: information on: Mechanism to exchange access to: providing guidance and The ECSS organization Latest ECSS News ECSS Architecture ECSS Handbooks ideas and information within assistance: The membership of the Current Year Agenda Access to ECSS published ECSS Technical the ECSS community: Frequently Asked Questions
ECSS background different ECSS bodiesstandards Contact details Links to other Standardisation ECSS Forms organisations Events Drafting rules and ECSS procedures How to develop standards Templates News archive Memoranda My Questions (mechanism Addition of new discussion to ask the webmaster topics and receive Participation in existing questions onanswers on a one-to-one going discussions Note: only information basis) relevant to ECSS is allowed
Slide 28
Any Questions?
Slide 29