Contents of the draft change issue in Jira

The technical author shall submit a draft change issue in Jira for the initial creation of new standards documents into the DMRB or MCHW or for any updates to that document.

  • NOTE 1:    Change issues record the governance associated with the creation of, or update to a document. There can be multiple change issues listed against a document to track the history of updates to that document.
  • NOTE 2:    Draft change issue templates are created by TSG to ensure they are linked against the appropriate document that is being created or updated. Please contact TSG to set this up in the first instance.
  • NOTE 3:    Training material for technical authors on how to use Jira is available here: https://youtu.be/sXPekN0GJZo

Once you’ve received the link of your change issue, please press the following workflow buttons to open the draft form that contains the background information related to the change you want to make:

New button in change issue and associated action to complete draft change issue form

Submit draft to TSC chair for review

Please complete the draft change issue by reviewing the three separate tabs. The related information and options are explained in more detail below.

Request to enter the SRP

Category of change (pick one of the following):

  1. Category A: Change to policy, major revision, new document development
  2. Category B: Incremental change to requirements
  3. Category C: Incremental change to advice
  4. Category D: Incremental change to notes and/or spelling mistakes

Reason for change (select all relevant drivers):

  1. Driver 1: Changes in strategic approach, needs and objectives
  2. Driver 2: Changes to European, UK and national legislation
  3. Driver 3: Changes to standards and the implementation or revision of harmonised European Standards (hENs)
  4. Driver 4: Changes to documents other than legislation and standards
  5. Driver 5: Changes to normative and informative references
  6. Driver 6: Changes in operational practice
  7. Driver 7: Develop collaboratively with other infrastructure clients
  8. Driver 8: Transfer responsibility for development of best-practice guidance to industry
  9. Driver 9: Impact of the updates made to other Overseeing Organisations’ documents
  10. Driver 10: Outcomes from research and development
  11. Driver 11: Industry or supply chain feedback on innovation and best practice
  12. Driver 12: Industry or supply chain feedback on errors identified
  13. Driver 13: Number and scope of departures from requirements contained in RADs (National Highways only)

Outline summary of the changes needed (free text):

Provide details of how the need for making the change was identified and any research that supports the change, e.g.

  1. correction of an error identified by a user through Standards Enquiries;
  2. change to a requirement to enable an innovation previously accepted as a departure;
  3. change identified by Technical Author to align with safety legislation.

Outline summary of the expected benefits (free text):

What are the expected benefits of the creation of, or update to the document?

Is the proposed change urgent? (pick one of the following);

  1. Yes
  2. No

If a change is not marked as urgent then the TSC may choose the timing of the update to manage the programme of changes to documents.

Urgency justification (free text):

If urgent, explain why there is an urgency, e.g. highlight if there is an immediate safety risk. This information will assist the TSC in programming the changes, e.g. to avoid too frequent changes to documents but to manage risks.

Example of request to enter the SRP form

People

  1. TSC Chair (enter name)
  2. TSC Secretary (enter name)
  3. TSC editorial consultee (enter name)
  4. Department for Infrastructure NI technical consultee(s) (enter name)
  5. Transport Scotland technical consultee(s) (enter name)
  6. Welsh Government technical consultee(s) (enter name)
  7. HE Technical consultee(s) (enter name)
  8. Other external technical consultee(s) (enter name)
  9. Group Programme Coordinator (enter name – optional)
Example of the people form

Dates

  1. Forecast initial consultation and development strategy meeting (input a date)
  2. Forecast DDP submission (input a date)
  3. Drafting forecast start (input a date)
  4. Forecast TSC consultation start (input a date)
  5. Forecast TSC consultation completion (input a date)
  6. Forecast submission for TSC chair approval (input a date)
  • NOTE        4 weeks for change to requirement and advice; 2 weeks for change to notes or editorial updates.
  • NOTE 1:    The forecast date to have finalised all TSC consultation feedback and governance deliverables.
Example of the dates form

Submit your form

Please press the button ‘Submit draft to TSC Chair for review’ once complete and the issue will be assigned to the TSC Chair for their decision.

Button to submit form to TSC Chair

If the form does not submit, please check the top of the form on the three separate tabs for any red warning errors. This usually means a mandatory data entry field has been left blank or unticked/unselected.

Back to top