ISO 20000 Design and transition of new or changed services
Answer:
Design and transition of new or changed services is responsible (in scope of the SMS - Service Management System) to manage any changes on existing, or introduction of new services. In your case, I rather see that you'll have changes on existing services. In scope of your change management (e.g. in your policy) you should define which changes are introduced using design and transition process.
If you have Design and transition process in place, evidences that you can show to the auditor could include:
- specification
- service requirements
- test plan
- transition plan
- risk assessment
- service acceptance criteria, etc.
1.If those external warehouses belong to your organization and they are relevant to your scope they must be included. 2.Probably, during the certification audit a sample of some of those warehouses will be audited.
The following materials will provide you details about the scope of a management system:
For AS9100 Rev D the date to transition from an AS9100 Rev C certified QMS to the new standard has always been aligned with the ISO 9001:2015 transition dates. In September 2017 the ISO & IAF group put out a news release stating that this date for transition would be September 15, 2018. After this date no certification for ISO 9001:2008 would be valid, and likewise certifications for AS9100 Rev C would not be in effect any longer.
Of course, there is no last date to certify a new QMS to AS9100 Rev D. This will be the aerospace standard going forward.
For more information on AS9100 Rev D transition see this whitepaper https://info.advisera.com/9100academy/free-download/as9100-twelve-step-transition-process-from-rev-c-to-rev-d
Opposition to implementation
Answer: The main arguments against ISMS implementation generally are:
- the investment to be done
- lack of clear view of the benefits
- historical data supports the thinking "this will never happen to us"
- the thinking "no one is interested in our information"
Suppliers approved by customers and procedure requirement
Answer:
By “been approved by our customers” I imply that they have been selected by your customers. I would recommend keeping a procedure for Purchasing and Evaluation of Suppliers.
Although they have been selected by your customers your organization still needs to order them to deliver the right amount, of the right reference, with the right quality and with the agreed price in a particular date. Also, your organization must verify fulfillment of requirements upon reception of each delivery. Finally, although suppliers are selected by your customers it is wise to keep a record of suppliers’ performance. For example, it can be useful during negotiations with customers, particularly because your organization could be “importing problems” from those suppliers that affect your organization internal performance and even your performance at the eyes of the customers.
The following material will provide you information about the purchasing:
Its list of questions will help you to verify the degree of implementation of the standard you client has achieved and guide you on the definition of the project scope.
Answer: ISO 22301 was designed to be implemented in organizations of any size or industry, so there is no specific recommendation for financial organizations. In a general manner you should consider:
- Ensure the buy in of you top management for this project
- Make the employees aware of the importance of this implementation
- Identify and involve in the project the right people (the ones with the knowledge, experience and skills to help the implementation).
- Identify the proper implementation strategy
Answer: The control A.10.1.1 - Policy on the use of cryptographic controls defines the guidelines for the use of cryptographic technologies in an organization (e.g., which technologies to use, when, by whom, etc.). So, if you have cryptographic technologies in your organization (like the SSL certificate) you have to consider the implementation of this control to treat risks like:
- IT staff implementing SSL in different ways in different places because there is no general rule about the issue,
- Unauthorized people accessing cryptographic technologies, because there is no list defining who can use it