ADMIN 4.1 Proposing a Product

Transcription

1 ADMIN 4.1 Proposing a Product Version 9. Paul Daly CEO RISSB 18 February 2016

2 DOCUMENT CONTROL Identification Document Title Number Version Date Proposing a Standard ADMIN /07/2007 Proposing a Standard ADMIN /10/2009 Proposing a Standard ADMIN /05/2012 Proposing a Standard ADMIN /08/2012 Proposing a Standard ADMIN /04/2013 Proposing a Standard ADMIN /11/2013 Proposing a Standard ADMIN /02/2016 Proposing a Standard ADMIN /06/2014 Proposing a Product ADMIN /02/2016 Document History Publication Version Effective Date Page(s) Affected Changes 1 23/07/2007 All Document Creation review and update 2 10/10/2009 All Review and update 3 03/05/2012 All Review and update 4 28/08/2012 All Review and Update 5 05/04/2013 All Review and Update 6 15/07/2013 All Review and update 7) 07/11/2013 All Review and update 8 27/06/2014 All Review and update 9 18/02/2016 All Review and update

3 Proposing a Product 1 Purpose The purpose of this document is to set out the request, evaluation, approval and confirmation processes for the initiation of a new RISSB Product. This procedure applies to the development of a Guideline, Rule, Code of Practice or a Standard. The term Product will be substituted for the aforementioned documents types where development requirements are common to all. 2 References All Terms, abbreviations and acronyms used in this document are defined in the RISSB Glossary 3 Process 3.1 Overview The following information defines the process to be followed for evaluating and prioritising requests for a proposed product. 3.2 Project Request RISSB Product development requests may originate in two ways; (a) (b) Interested Party Requests; initiated by any person, providing that the request is genuine and in the interests of the Australasian Rail Industry (see dot points below). The request must be made in writing to the Chief Executive Officer RISSB using T-01 Request for Development Template. RISSB Standing Committees Requests; arising from SC business, can be initiated by SC without the need to complete a request for development template. Proposal is made in consultation with relevant RISSB Project Manager and recorded in RISSB s stakeholder s initial project list. 3.3 Request Processing All requests received by the Chief Executive Officer (CEO) based on the following criteria: All new projects shall address a hazard or hazards in RISSB s hazard guideline and must be cited in any proposal. RISSB s hazard guideline is located on the RISSB website at The proposed product shall fall with RISSB s objects to develop, manage, and promote a suite of standards (including safe work rules), guidance materials, and other documents (including the ACOP) to assist the rail industry to manage rail safety and improve efficiency Proposed Standards need to also fall within RISSB s scope of accreditation with ABSDO.

4 Development of Standards shall have regard for the General Provisions of the WTO Agreement on Technical Barriers to Trade. Standards should not be developed where International Standards might be adopted, and must not create any unnecessary barriers to trade. Note: If International Standards on the same subject exist, justification is required if these are not adopted or used as the basis for the proposed standard. The proposed product shall provide a value or benefit to the Australian community that exceeds the costs likely to be imposed on suppliers, users and other parties in the community as a result of its development and implementation. Products shall be consistent with the national interest and public benefit. Products should be able to be prepared in a reasonable timeframe considering their nature and complexity, the needs of the specific user groups, industry, government and the community, and with regards for the resources available If the CEO accepts the proposal for development, the CEO will; Determine if the product to be developed will be a Standard, Guideline, Rule, Code of Practice (COP) or Guideline. Identify the appropriate RISSB functional area to oversee development Advise the relevant Project Manager (PM) of proposal acceptance The Project Manager shall inform the proposer that it has been accepted for further consideration at the annual project priority meeting. If the proposal is rejected, a response in writing will be forwarded to the proposer stating the reasons for its rejection. This written advice will be placed on file. 3.4 Future Projects Listing The relevant Project Manager will insert detail of accepted projects into RISSB s future project list Initial Prioritisation The PM will assign each product in the Future Projects List a priority number of 1 to 5, with 1 being the highest priority and 5 being the lowest priority. Priority Priority 1 Priority 2 Priority Consideration A priority 1 product is one which will have a direct impact on the Australasian Rail Industry. It must start development in the next FY. A priority 2 product is one that attracts a very high priority but its impact on the rail industry is not as great as a priority 1 product. Nonetheless if money is available it should commence development in the next FY.

5 Priority Priority 3 Priority 4 Priority 5 Priority Consideration A priority 3 product is one which will have a medium impact on the rail industry. It is relatively important but recognises that it may not attract funding in the next FY. A priority 4 product is one which is defined as nice to have ; it is attracts a medium priority. It is unlikely to attract any funding within the foreseeable future. A priority 5 product is one which attracts a low priority for development but needs to be recorded as a future potential project. In February each year RISSB Standing Committees (SC) consider all projects on the project list that is within their particular domain. The SC will either confirm the priority assigned the project by RISSB s Program Manager or assign the product another priority in accordance with the priority definitions noted above. This list will be considered by a priority setting workshop in March each year. 3.5 Project Prioritisation Workshop RISSB will advertise the project priority setting workshop and seek active participation from the Rail Industry, ONRSR, Governments and the Rail Unions. RISSB will arrange the workshop such that it immediately follows RISSB s Safety Conference in March each Year. The conduct of the workshop is attached at Annex A. The output from the workshop is a stakeholder agreed list of project priorities. On completion of the workshop CEO RISSB will insert a budget line in the list of projects. All projects above this line will be funded. Any project below this line will be held in reserve and will be funded as more resources become available. Projects that do not receive funding will be reconsidered at the next workshop. The National Rail Safety Regulator s endorsement will be sought on the priority list before the RISSB Board approval of the funded project list is sought in May/June each year. Following approval by the Board, RISSB management commences development of the approved projects. 3.6 Preparation for Project If the development proposal is approved the Project Manager; advises stakeholders of the project development, seeks stakeholder involvement (both major and minor) for Development Group (DG) participation, and obtains Standing Committee approval of Development Group. If the approved proposal is for development of a RISSB Standard, the Accreditation Manager shall provide ADSDO with notification. ABSDO are to be provided with a spreadsheet documenting all current projects under development. The spreadsheet will include the project ID number name description estimated date of completion and the PM details 4 Record Requirements The following records are retained as evidence of compliance to this procedure:

6 Every Stage of project development is stored in the RISSB SharePoint Site; the major categories being Project proposal requests Request for Development Templates Initial Project Lists (MS Excel versioned and saved annually) Prioritisation Workshop records SMART product proposal assessments Future Projects Lists (MS Excel versioned and saved annually) Minutes of relevant Board Meetings (RISSB CEO and Board Approvals)

7 ANNEX A Step 1: Presentation of the project list CONDUCT OF PROJECT PRIORITY SETTING WORKSHOP CEO RISSB will give an overview of all projects recommended by the RISSB Standing Committees. (product type, scope & purpose ) SC chairs will give a synopsis of their project priorities and explain why they were prioritised. (need for proposed product, expected benefits, potential impacts of implementation) Workshop delegates will have the opportunity to ask questions on the projects. Step 2: Constitution of the syndicates Six syndicates will be constituted from the workshop delegates to review the list of priorities. Each syndicate represent a RISSB functional area, namely: Safety, Rolling Stock, Infrastructure, Train Control Systems, Interoperability/Operations, and Wheel Rail Interfaces. The respective SC chairs will lead the syndicates discussion with the assistance of the respective RISSB PM. Workshop delegates will be allocated a syndicate in accordance with their nominated preference. Step 3: Deliberation by syndicates Each syndicate will review all listed projects and rank them in order of preference without ties (1 being the preferred project). Each syndicate will use the SMART technique to assess the projects and determine their rank: S = Simple: How simple would it be to implement the product across all networks (easy (5), medium (3), difficult (1)); M = Measurable: If the product is suitable for implementation, how difficult would it be to manage its implementation across the networks (low (5), moderate (3) or high (1)); A = Attainable: Will the product achieve a harmonising effect for the Industry (yes (5), maybe (3), no (1)); R = Relevant: Does this product address a risk or risks in the Australian Rail Industry ((yes (5), maybe/some (3), no (1)); T= Timely: How long would it take for the rail industry to accrue benefits from this product if it were implemented (short (5), medium (3), long term (1)). Each syndicate will discuss the list resulting from the SMART assessment and may modify the list if it wishes to do so. When each syndicate has reached an agreement on the ranking, it will submit its finalised list to CEO RISSB for consolidation.

8 Step 4: Presentation of the results and approval Proposing a Product CEO RISSB will combine the lists and present the consolidated list to the workshop delegates. The results will be discussed by workshop delegates, with the SC chairs providing explanation of their ranking if required. The list may be modified based on these discussions. CEO RISSB will seek the workshop delegates approval of the consolidated list. In the event of dissension, a vote by show of hands will be undertaken, with a simple majority required to adopt the specified list.