Zakázka: Enterprise Architecture Management System (EAMS) Solution
Zadavatel: WIPO – World Intellectual Property Organization, Ženeva
Deadline pro odevzdání nabídky: 23/7
Základní popis: WIPO would like to purchase an Enterprise Architecture Management System tool that would address its needs, and is launching this tender to select a vendor that would provide:
• An EAMS software product that can satisfy the identified needs of the Enterprise Architecture Division (ICTD/EA).
• Technical services for the deployment of the new EAMS as well as for the maintenance and related consulting services.
Mandatory Requirements
I. Company Profile
MR-1. Your company must be incorporated in the form of a commercial entity or similar.
MR-2. Your company must not be ineligible to do procurement business with any organization that belongs to the UN system.
MR-3. Your company must have positive net worth and/or be financially sound
MR-4. If your company is a reseller, it must be a key accredited reseller to the product company with the ability to resell, design, implement and maintain the product for organizations in Switzerland.
MR-5. Your company must have a minimum of 3 years experience specialized in Enterprise Architecture modelling, with customers similar to WIPO in size.
MR-6. Your company must have a minimum of 3 years experience in selling and supporting products in the domain of Enterprise Architecture modelling.
Resources
MR-7. Your proposed Lead Project Manager has at least 4 years of working experience handling similar projects (implementation of Enterprise Architecture products and leveraging Enterprise Architecture through tailored consulting services).
MR-8. Your proposed Lead Architect has at least 4 years of working experience in the area of Enterprise Architecture modelling (with outsdanding knowledge of the main viewpoints: Business, Information, Data and Technology).
MR-9. Your proposal includes a Customer Focal Point function (internal or external to this project) for all kinds of requests or incidents raised by WIPO.
MR-10. Your proposal includes HelpDesk services to be provided at least in the English language and with working hours covering WIPO official working schedule (Monday to Friday). Ouside this time slot, email recording mechanism is available for incoming requests to be automatically logged.
MR-11. Your offer should ensure implementation of final deliverables by December 9, 2019, taking into account the fact that you cannot be held responsible for delays attributable to WIPO.
III. EAMS Functionalities
III a) On-premises version – If you are offering an on-premises version of your product, it should satisfy the following requirements:
MR-12. Your proposed EAMS has release history of at least 3 years in the market.
MR-13. Your proposed EAMS has at least 100 subscribing customers.
MR-14. Supports as a core capability three main viewpoints: Business, Information and Technology.
MR-15. Supports the following modelling types: Business Capability, Business Process, Customer Journey Mapping and Business Ecosystem.
MR-16. Supports modeling from the strategy level to technical implementation.
MR-17. Supports modeling of current- and future-state architectures from three viewpoints: Business, Information and Technology.
MR-18. Supports Gap Analysis and Roadmap modeling for current- and future-state architectures from three viewpoints: Business, Information and Technology.
MR-19. Is able to prevent changes to recent modelling artifacts to impact already available within the repository, allowing changes to a model to be propagated only to identified artifacts in the repository.
MR-20. Can handle different stages of existence of objects, such as under discussion, validated, current production.
MR-21. Allows business stakeholders to contribute and collaborate on plans, scenarios, impacts and identified models as well as communicate with their audience on identified models, providing feedback directly via an embedded interface within the EAMS.
MR-22. Supports different types of stakeholders, and allows scenario planning, impact assessment, diagnostic deliverables and reporting.
MR-23. Has versioning features that protects changes to validated objects and models as well as those are undergoing the validation process.
MR-24. Allows parallel activities to take place, i.e. architecting models being created by architects and simultaneously permitting other stakeholders to consult available and validated artifacts.
MR-25. Has predefined dashboards for multiple stakeholders views.
MR-26. Provides end-users with a browser-like experience.
MR-27. Supports undo/redo features.
MR-28. Allows search based on given attributes such as name, definition and customized items.
MR-29. Allows attributes to be customized with information related to business focal point, technical focal point, geographical location, operational costs, etc.
MR-30. Can be deployed in modules.
MR-31. Supports the Archimate language.
MR-32. Natively supports the TOGAF framework.
MR-33. Can integrate with “Technopedia” (Flexera Software LLC) or similar tools.
MR-34. Allows Enterprise Architects to import/export information, including customized reports and grahics, in at least one of the following: pdf, excel, word, csv, xml, vsd
MR-35. Can integrate with a CMDB tool
MR-36. Can integrate with a Service Management System.
MR-37. Is able to integrate with a commercial database management system, e.g. Oracle and/or Microsoft, etc. for the repository.
III b) Cloud version – If you are offering a cloud version of your product, it should satisfy the following requirements:
MR-38. Your proposed EAMS has release history of at least 3 years in the market.
MR-39. Your proposed EAMS has at least 100 subscribing customers.
MR-40. Supports as a core capability three main viewpoints: Business, Information and Technology.
MR-41. Supports the following modelling types: Business Capability, Business Process, Customer Journey Mapping and Business Ecosystem.
MR-42. Supports modeling from the strategy level to technical implementation.
MR-43. Supports modeling of current- and future-state architectures from three viewpoints: Business, Information and Technology.
MR-44. Supports Gap Analysis and Roadmap modeling for current- and future-state architectures from three viewpoints: Business, Information and Technology.
MR-45. Is able to prevent changes to recent modelling artifacts to impact already available within the repository, allowing changes to a model to be propagated only to identified artifacts in the repository.
MR-46. Can handle different stages of existence of objects, such as under discussion, validated, current production.
MR-47. Allows business stakeholders to contribute and collaborate on plans, scenarios, impacts and identified models as well as communicate with their audience on identified models, providing feedback directly via an embedded interface within the EAMS.
MR-48. Supports different types of stakeholders, and allows scenario planning, impact assessment, diagnostic deliverables and reporting.
MR-49. Has versioning features that protects changes to validated objects and models as well as those are undergoing the validation process.
MR-50. Allows parallel activities to take place, i.e. architecting models being created by architects and simultaneously permitting other stakeholders to consult available and validated artifacts.
MR-51. Has predefined dashboards for multiple stakeholders views.
MR-52. Provides end-users with a browser-like experience.
MR-53. Supports undo/redo features.
MR-54. Allows search based on given attributes such as name, definition and customized items.
MR-55. Allows attributes to be customized with information related to business focal point, technical focal point, geographical location, operational costs, etc.
MR-56. Can be deployed in modules.
MR-57. Supports the Archimate language.
MR-58. Natively supports the TOGAF framework.
MR-59. Can integrate with “Technopedia” (Flexera Software LLC) or similar tools.
MR-60. Allows Enterprise Architects to import/export information, including customized reports and grahics, in at least one of the following: pdf, excel, word, csv, xml, vsd
MR-61. Can integrate with a CMDB tool.
MR-62. Can integrate with a Service Management System.
MR-63. Your company is geographically located in countries listed under https://treaties.un.org/Pages/ViewDetails.aspx?src=TREATY&mtdsg_no=III-2-15&chapter=3&clang=_en, in addition to the United States of America.
MR-64. Can ensure that customer data is geographically hosted in countries listed under https://treaties.un.org/Pages/ViewDetails.aspx?src=TREATY&mtdsg_no=III-2-15&chapter=3&clang=_en, in addition to the United States of America.
Leave a Reply