...

The Change Advisory Board will be phased out completely as it will be covered by the Yamaha Portfolio Board and  Software project(s).

J-sox compliance

J-SOX requires Japanese companies to enhance internal control reporting and demonstrate the effectiveness of their internal controls. 

To be J-SOX compliant,

...

Yamaha Motor Europe N.V. will need to demonstrate 4 primary security controls in a yearly audit:

• Secure Access Control Management. ... 
• Demonstrate a Resilient Cybersecurity Framework. ... 
• Demonstrate Data Backup Protocols. ... 
• Change Management.

For Information Systems Division

...

Controls will be integrated in the Jira workflows:

• Secure Access Control Management: new user accounts must be registered and logged in Jira. Users manager need to be informed and

...

Beforehand it is not known if a database correction or program change is required, to prevent delay in resolving reported issues the users manager is automatically added to a ticket. 

YIS: DoD projects

When closing an item, it is mandatory to full the field "DoD projects":

Image Removed

A Definition of Done (DoD) is a term from the scrum framework, which describes the agreement of what it means when an item is set to "Done" status. 

Within YME the intent it to validate these three organization-wide requirements for each ticket, because YME is being audited on these three points. For this reason, it is expected that this field will become mandatory across all YME projects in Jira.

N.B.: Jira COP wishes to limit the field to only being mandatory when a release is involved, this is a planned improvement.

Yamaha Applications Support Desk (SD)

In Yamaha Applications Support Desk all operational support (BAU- Business As Usual) requests are registered that relates to IT Application Issues/errors for existing functionality, data correction and authorization requests.

Users can create a new issue via the Yamaha Motor Europe support portal, via this portal you can go to the YME Information Systems Support Portal to submit a IT request.
Instructions of the portal forms can be found here: YME Information Systems Support Portal Guide

The Image Removed button should NOT be used for creation of a SD issue.

SD Issuetypes

Image RemovedIncident:  Reporting a incident or outage. Currently all incoming issues submitted via the Jira Customer portal will have Issue type Incident.

Image RemovedService Request:  Request for information, this issue type is currently not used anymore.

Image RemovedAudit: Used for J-sox change requests and IRY issues registered to deliver evidence for auditors.

Image RemovedAuthorization request: Elevate user rights request used for Ympact to request YMXXITS1 access to have command line access and to operate in Ympact (Branch specific) Production environment.

Image RemovedRobotJob Change: Robot Job Change request used for Ympact Job scheduling

...

• included in the ticket.
• Secure Access Control Management: all user authorization changes for Business applications (Ympact, SYS2000, YLS) must be logged in Jira.
  Approval for new authorization(s) is required from IT management (division manager, department manager, team lead).
• Change management: approval (SQL's) by IT management (division manager, department manager, team lead)
• Change management: Role segregation for development and testing. Developer does not test their own developed code.
• Change management: Deployment approval request by IT management (division manager, department manager, team lead).
• Change management: Deployments can only be performed by authorized roles (division manager, department manager, Team lead, Product Owner, Delivery manager).
• Change management: Agile teams must met the organizations set Definition of Done. This is done via a checklist for issues moved to ready for Deployment.

Beforehand it is not known if a database correction or program change is required, to prevent delay in resolving reported requests the users manager is automatically added to the request (Jira issue/ticket).
YME and distributor users are directly synchronized in Jira with Active directory including users manager. The users manager is added via a automation after request creation. 
Active directory is maintained by Servicedesk.

Yamaha Applications Support Desk (SD)

In Yamaha Applications Support Desk all operational support (BAU- Business As Usual) requests are registered that relates to IT Application Issues/errors for existing functionality, data correction and authorization requests.

Users can create a new issue via the Yamaha Motor Europe support portal, via this portal you can go to the YME Information Systems Support Portal to submit a IT request.
Instructions of the portal forms can be found here: YME Information Systems Support Portal Guide

The Image Added button should NOT be used for creation of a SD issue.

SD Issuetypes

Image AddedIncident:  Reporting a incident or outage. Currently all incoming issues submitted via the Jira Customer portal will have Issue type Incident.

Image AddedService Request:  Request for information, this issue type is currently not used anymore.

Image AddedAudit: Used for J-sox change requests and IRY issues registered to deliver evidence for auditors.

Image AddedAuthorization request: Elevate user rights request used for Ympact to request YMXXITS1 access to have command line access and to operate in Ympact (Branch specific) Production environment.

Image AddedRobotJob Change: Robot Job Change request used for Ympact Job scheduling

Image AddedDeployment request: Triggered by Development software projects used by B2B teams for Ympact,Ympulse, Yamcom deployments.

SD Issues overview

SD Specific Fields

SD mandatory fields have been highlighted in Yellow

Image Added

• Type: Issue type
• Priority: By default issues are set to Medium
  Image Added
  
• Solution group *: Drop down single select list to define which department will be working on the issue.
  Image Added
• Team Yamaha: Label field, multi select, always starting with team# <team name> mandatory for non-agile teams to determine which team will be working on the issue.
  This field will be replaced with Yamaha Team.
  Image Added
• Yamaha Team*: Drop down single select list to define which (agile) team will be working on the issue.
  Image Added
  
• Application-Module:  Drop down single select list to indicate the involved Application-Module of the reported request (issue).
• Department: Department of the reporter of the issue.
• Company: Company of the reporter of the issue.
• Epic Link: Linked epic issue if a issue is related to a Project.
• SD Classification: Drop down single select list, by default for incoming issues set to Business as Usual (BAU)
  Image Added
  
• Status: Workflow status
• Resolution: Resolution can be set when a issue will be closed.

* Combination of Solution group and Yamaha Team determines in which queue/board a issue is visible for non-agile teams.
   For Agile teams only Yamaha team field determines in which board the issue is visible.

Image Added

• Request Type: Customer portal request type
• Customer status: Status visible in the Customer portal. This does not always corresponds directly with the issue workflow status.
• Channel: Portal or e-mail request
• View customer request: link directly to the Customer portal request. This link can be shared if a customer need to access a specific issue.

SD Workflow(s)

If a (bug) fix for a application is required the Bugfix transition can be used to trigger a issue being created in a Development project.

...

Additionally, on Kanban boards, closed items will disappear from the board once a fix/version is closed, not earlier.

...

YIS: DoD projects

When closing an item, it is mandatory to full the field "DoD projects":

...