RFI Attachment 02 - Vendor Reponse Template.xlsx

Sheet1

Please answer the following questions to assist us in making some strategic decisions, refining our requirements, and assessing the marketplace.

Deployment Model: Government Cloud Cloud Service Designation: FedRAMP Authorized Cloud Service Impact Level: FISMA Moderate or higher Accessibility: 508 Compliant Cyber-security: Phishing Resistant Multi-Factor Authentication (Certificate Base (PIV), FIDO2, Login.gov)

b. Intuitive

• The tool shall provide an intuitive user interface without or minimal tool customization to ensure quick adoption.

• The tool shall be configurable for organizational and individual stakeholder views and business requirements.

c. Integration

• The tool shall integrate seamlessly with existing systems and tools used within the organization to streamline workflows and data exchange.

• The tool shall seamless integrates into an industry agnostic reference architecture and no-code/low-code API integration

• The tool should support integration with Data Governance tools, such as Collibra

• The tool should seamless integrate with third party products such as Microsoft products ( Excel, Power BI, etc.)

• The tool should seamlessly integrate with other enterprise systems, such as ERP, CRM, ITSM, and more

• The tool shall support Azure cloud deployment and integrates with Azure services

• The tool shall integrate with Azure identity and access management (IAM) tool

d. Modeling

• The tool shall have the ability to link elements in the repository to defined business capabilities, goals, strategic objectives, as well as other taxonomies at various levels

• The tool shall support Business Process Model and Notation (BPMN)

• The tool shall support the ability to extend the meta-model to include object classes, underlying notation, relationship types, and methodologies to reflect the organization domain-specific context

• The tool shall enable the ability to map external data sources to appropriate element types and fields within the meta-model

• The too should support federated extensions of the meta-model to allow different viewpoints of the same content for different stakeholders

• The tool shall allow the creation of comprehensive architectural models, to include business processes, data, applications, and technologies

• The tool shall support cross line of business collaboration and optimize workflows

• The tool should support application portfolio management, technology risk management, IT integration, and overall business transformation

e. Data

• Support robust data governance practices, including data quality, lineage, security, and compliance with regulatory standards.

• The tools shall manage and process large volume of data

• The tool should support automatic attestation for meta date related to the technology within the respository

• The tool shall allow for real-time data feeding and analysis

f. Collaboration

• The tool shall enable real-time collaboration among stakeholders

• Allow for collaboration among cross functional teams to share information and work together

g. Customization

• The tool shall support no code/low code implementation

h. Repository

• A centralized database storage for all architectural assets for easy managing and retrieving information

• Repository shall connect data, diagrams, metrics, and KPIs to ensure integration and integrity

• The tool shall allow for an extensile metamodel that enables new classes, business concepts, metrics, and relationships.

• The tool repository shall provide a singe source of truth for storage, categorization, and versioning of objects and models related to business capabilities and technology.

• The tool shall support the ability to represent value streams and support the aggregration of metrics and connection to portfolio analysis to create transparency.

i. Analysis and Reporting

• Allows for evaluation of potential changes, impacts, and provides “what-if” analysis for better decision-making

• Advance analytics and user-friendly reporting capabilities to generate insights from architectural data

• The tool shall track performance metrics and identify potential bottlenecks

• Allow for intuitive visualization reports or dashboards to tracking progress, identifying bottlenecks, and making data-driven decisions

• Allows for the creation of roadmaps showing the transition from current to future state architectures

• The tool shall provide heat maps, gap analysis, scenario planning, and risk indicators to support decision making

• Allow for version control and tracking changes made to the architecture

• The tool should provide interactive visual exploration across elements in the repository

• The tool should allow analytical views to automatically update based on selection or filtering in one pane.

• The tool shall provide role-based and configurable dashboards with user defined searches

• The tool shall allow multiple forms of visualization such as 3D, 2D graphs, tree maps, and multidimensional roadmaps

j. Scalability

• The tool shall be able to scale horizontally or vertically as the organization grows, accommodating increasing data volumes and user numbers

• The tool shall support distributed teams accessing and updating information seemlessly

k. Security

• Ensure data privacy, compliance and robust security features to prevent data breaches

• Shall have robust security features, access control based on role and permissions and protect sensitive data

• The tools shall support role-based access controls with support for single sign-on (SSO).

l. Training

• Provide training sessions to familiarize users with the features, interface, and functionalities of the tool

• Teach users how to navigate through various workflows within the tool, such as creating, modifying, and deleting architectural artifacts

• Train users on best practices for using the tool effectively, including naming conventions, version control, and documentation standards

• If the tool integrates with other systems or tools, provide training on how to connect and utilize these integrations

• Educate users on security measures within the tool, such as access control, permissions management, and data encryption

• For power users or administrators, offer training on advanced features and configurations of the tool What pricing model is used to account for services such as integration, maintenance and training? For instance, are such services included as part of the product purchase, purchased separately as a BOM item, or procured through a labor hour model? Is there enough information provided in the PWS for the vendor to price all servies including integration, maintenance and training? If not, what further information would be needed?

8 Please provide any feedback or questions you have regarding the attached PWS.