Enterprise Architecture Planning Tool
Request for Information
2/26/2015
NYULMC Enterprise Architecture Planning Tool – Request for Information
Table of Contents
1. Purpose 2
2. Response Instructions 2
3. Background 3
4. Objectives and Strategic Drivers 4
5. Company Information Request 6
6. Product Information Request 7
Product Portfolio & Roadmap 7
General Questions 7
Functionality 7
Architecture Frameworks, Languages and Metamodels 8
User Experience and Collaboration 8
Technology Platform 8
Cost Estimates 8
7. Pilot 10
Goal 10
Participation in Pilot Phase 10
1. Purpose
This is a Request for Information (RFI) only and does not constitute a commitment, implied or otherwise, that New York University Langone Medical Center (NYULMC) will take procurement action in this matter. Further, NYULMC will not be responsible for any cost incurred in furnishing the information requested. Any follow-on procurement strategy will be based on the results of the information provided and available funding.
2. Response Instructions
Unauthorized contact regarding this RFI with employees of the Hospital other than the designated Hospital contact or their designee may result in disqualification from this process.
All questions regarding interpretation or specifications must be submitted in writing to only. Under no circumstances shall vendor contact any employee of NYULMC. Any dialogue initiated by the bidder not addressed to contact above will result in an immediate disqualification.
Any oral communications shall be considered unofficial and non-binding with regard to this RFI.
The Hospital reserves the right to determine, at its sole discretion, the appropriate and adequate responses to written comments, questions, and requests for clarification. The Hospital’s official responses and other official communications pursuant to this RFI shall constitute an amendment of this RFI. Only the Hospital’s official, written responses and communications shall be considered binding with regard to this RFI.
Any oral communications shall be considered unofficial and non-binding with regard to this RFI.
Proposals must be submitted to no later than 12PM on March 12, 2015. A proposal must respond to the written RFI and any RFI exhibits, attachments, or amendments. A late proposal may not be accepted, and a proposer's failure to submit a proposal before the deadline may cause the proposal to be disqualified.
3. Nondiscrimination
No person shall be excluded from participation in, be denied benefits of, be discriminated against in the admission or access to, or be discriminated against in treatment or activities on the grounds of disability, age, race, color, religion, sex, national origin, or any other classification protected by federal or State Constitutional or statutory law; nor shall they be excluded from participation in, be denied benefits of, or be otherwise subjected to discrimination in the performance of contracts with the Hospital.
4. Background
NYU Langone Medical Center, a world-class patient-centered integrated academic medical center, is one of the nation’s premier centers for excellence in health care, biomedical research, and medical education. NYU Langone comprises three hospitals—Tisch Hospital, a 705-bed acute-care tertiary facility; Rusk Institute of Rehabilitation Medicine, the first rehabilitation hospital in the world with 174 beds and extensive outpatient rehabilitation programs; and the 190-bed Hospital for Joint Diseases, one of only five hospitals in the world dedicated to orthopedics and rheumatology—plus the NYU School of Medicine, one of the nation’s preeminent academic institutions which includes the Smilow Research Center, the Skirball Institute of Biomolecular Medicine, and the Sackler Institute of Graduate Biomedical Sciences. Campus transformation and other M&A activities over the next few years will add additional capacity to the enterprise as well.
NYULMC is committed to making world-class contributions that place service to human health at the center of an academic culture devoted to excellence in research, patient care, and education.
5. Objectives and Strategic Drivers
Over the last three years, NYUMC defined an Enterprise Architecture program in the IT organization (MCIT). The program has been focusing on different areas of architecture and technology management as well as definition of standards and roadmaps.
The program has implemented a number of processes and internal tools that have been used by the technical team. Most of these processes and mechanisms have been manual, following standard ad-hoc templates, governance processes and reporting. These activities have also been aligned with other related technology planning and operations processes of the organization, including project portfolio and IT service management (ITIL based).
Because of the manual nature of the existing processes and the use of ad-hoc templates there are significant opportunities to further standardize the technology planning and delivery mechanisms. We seek to improve the architecture practice by deploying appropriate tools and technology for articulate technology strategies, simplifying the creation of architectural documentation and tighter control of standards and governance. This capability will become critical as programs with increasing complexity are implemented by the institution. The use cases that we have identified include:
1) Solution Architecture
- Capability for solution architects and engineering to articulate the system architecture of a specific technical solution in a standard way. The tool would allow these users to document different views of the solution (business, information, technology etc.), to document alternatives and to manage the lifecycle of these designs. The resulting designs would be stored in a repository and its components could be re-used for different projects. The tool could provide standard templates aligned with an architecture framework.
2) Strategy Planning
- Ability to articulate and report on the strategic direction of a technical and/or business domain, describing capabilities, roadmaps and technology portfolios. This use case would be applicable to enterprise business architects, business partners and finance executives.
3) Standards Management
- Aimed at technology planners (architects and engineers), this function is to use a tool as a repository for standards lifecycle management.
4) Application Portfolio
- This is the ability for technical planners, domain architects and finance team to make decisions regarding the application portfolio, such as opportunities for rationalization and performing ROI on specific investments.
5) Architecture Practice Governance
- As part of the solution lifecycle, the architecture team reviews and makes decisions regarding technology approaches and is aligned with the project portfolio process. An enterprise architecture tool could help manage and document this decision process.
6) Reporting
- Ability to provide reports (ad-hoc or standard) regarding the architecture function processes (see above use cases), including metrics of appropriate KPI’s.
This RFI is aimed at identifying partners and a technology toolkit to address the above use cases and explore additional capabilities that might be available in the tools. Our next step is to gather information from potential vendors to better understand the solutions that are available in the market, assess their suitability to address NYULMC’s requirements, and launch a pilot project that will eventually inform an enterprise-wide acquisition.
6. Company Information Request
Please respond to the following questions – please be concise and as specific as possible.
1. Provide a brief company profile. If private, please include funding, number of employees, biggest customer wins, and customer wins in the healthcare sector
2. Provide information regarding any specific healthcare industry awards and/or third party endorsements your organization has received.
3. Provide 3 references
· Facility Name
· Contact Name
· Contact Title
· Contact Phone
· Contact E-mail
4. Does your company offer professional services or partner with other service providers to support solution deployment?
5. The vendor will provide one point of contact from which all service requests will be dispatched.
6. Describe your service and support options including phone, web support, proactive support, reporting, etc.
7. If reseller is providing the first line of customer support, please indicate the number of support engineers that are certified with the SGW system. How is the vendor involved in problem solving?
8. Briefly describe your near and longer term product vision and roadmap
9. Please describe any other high-value applications that are emerging in the healthcare space for which you have developed and deployed a solution.
10. Provide your training curriculum
11. When in-house labor is required, the vendor will provide in-house labor or contract with the Original Equipment Manufacturer or a suitable 3rd party that is mutually agreed upon by both parties. Please include onsite response times.
12. Vendor acknowledges that because of the nature of a Hospital business, some restrictions may be placed on vendor’s work schedule, and vendor may need to complete some portions of any service it is to provide after the Hospital normal operating hours.
13. Hospital policies. Vendor shall ensure that its personnel comply with all Hospital policies while performing any service on site, including policies relating to smoking, security, parking, use of radio equipment and mobile devices, access to any network, security, clothing and dress.
14. Vendor Registration Requirements. Vendor acknowledges that Hospital may have vendor registration policies and procedures and that vendor’s personnel will be required to comply with all such registration requirements.
15. Services Warranty. Vendor warrants that it will perform all services in a professional manner consistent with high standards of industry practice. If any service fails to accomplish its intended purpose, vendor shall re-perform the service until it accomplishes its intended purpose. Please detail length of warranty from time of purchase.
16. HIPAA Compliance. Vendor acknowledges and agrees that it is a “Business Associate” and every Hospital entity is a “Covered Entity” as such terms are defined under the Health Insurance Portability and Accountability Act of 1996 and rules and regulations promulgated there under (“HIPAA”), and each party shall comply with comprehensive privacy and security policies and procedures related to individually identifiable health information. Vendor shall be bound by the obligations of a Business Associate.
17. After the termination of this contract, all Inventory and Equipment Maintenance records will become the property of the Hospital.
18. The vendor shall observe all safety precautions throughout the performance of this contract and shall assume full responsibility and liability for compliance with all applicable regulations pertaining to the health and safety of personnel during the execution of work and shall hold the Hospital harmless for any action on its part or that of its employees that results in illness, injury or death.
19. Any work subcontracted by the vendor shall require the prior written approval of the subcontractor by the Hospital. Use of subcontractors must be clearly explained in the proposal and major subcontractors must be identified by name. The prime contractor shall be wholly responsible for the entire performance, whether or not subcontractors are used.
20. Vendor will provide an organizational chart and job descriptions for any service technicians to be assigned to Hospital upon Hospital request.
21. The Hospital will have access to any hospital maintenance databases from the vendor.
7. Product Information Request
For each section, provide an overview of how your solution addresses the specific area and briefly respond to the questions in each section.
Product Portfolio & Roadmap
1. What’s your vision of Enterprise Architecture and how your product fits into that vision?
2. Do you have an end-to-end Enterprise Architecture solution? What is the portfolio of products (or modules for a core product) that you offer in this space?
3. Please provide your product roadmap for the next 12 to 24 months
4. What sets your offering apart from other enterprise architecture tool players in the industry?
5. What is your company presence in the United States and support model for clients in this country?
General Questions
6. Describe typical deployment scenarios and use cases for your tool(s). What’s your best practice for institutions in the healthcare space?
7. Provide customer testimony or success stories of the deployment of your tool in the healthcare industry. Describe implementation challenges you have encountered deploying the tool in healthcare institutions (technical, process or organization related) and the approach you took to mitigate them.
8. Describe the product, modules and functionality. Is your product a monolithic system or has core and add-on modules.
- Does the system have a repository for architecture artifacts?
9. Does your product follow a SaaS model, customer hosted or a client device (e.g. workstation) product?
10. In addition to the tool or system, what are the training options and curricula available as part of the offering?
11. What is the support model offered as part of the tool?
12. Does the tool/system have extensive documentation?
13. Is there a user community or special interest group available?
Functionality
14. Describe the flexibility of the tool and ability to customize is models and objects to a specific environment.
15. Describe the full scope of functionality of the tool and modules. Including enterprise portfolio (application, services), business strategy, solution architecture patterns, financial planning
16. Does the system functionality overlaps with other frameworks, standards and best practices, including SOA, ITSM (ITIL), BPM/BPA.
17. Describe the modeling capabilities of the system and whether the tool includes mechanism like workflow engines as part of the deployment.
18. Does the system support scenario analysis and/or simulation?
19. What are the integration approaches supported to interface the tool and processes with external systems, such as project portfolio, ITSM systems (CMDB), or other source systems.
20. What are the repository and portfolio management capabilities of the system, including:
- Application portfolios
- Capabilities, process and service portfolios
- Technology (i.e. infrastructure) portfolios and roadmaps
- Requirements
- Other portfolios (e.g. project)
21. Does the tool provide automation of part of the architecture or strategy planning process?
22. Describe the governance capabilities of the tool to manage the above portfolios.
23. How does the tool allow for financial planning and tracking of technology investments
24. Describe the reporting options for the tool or its modules.
- Standard reports
- Custom and/or ad-hoc reports
- Customization options
Architecture Frameworks, Languages and Meta-models
25. Describe your tool support of architecture frameworks, languages and standards such as TOGAF and ArchiMate.