Here you will find cRM software of all known manufacturers (for example: Microsoft, Sage Software, Extensis, EBP, Panasonic, Easy Computing)
. Can compare prices and technical specifications (Software type, Recommended RAM, Recommended hard disk space, License type, Recommended processor, Language version).
Customer Care Framework 2009, External Connector, Open License Program-No Level, Government
Customer Care Framework 2009 The Microsoft Customer Care 2009 (CCF) solution is an end-to-end application infrastructure for delivery of composite applications. It includes development and runtime components. Applications built with CCF can provide unified access to customer information spread across different systems and aggregate different modes of customer interactions (channels).
Unlike expensive, rip and replace, and risky investments on custom development, CCF provides non-intrusive integration with existing systems.
The core characteristics of the CCF solution are: - User Interface composition – CCF allows the creation of composite UI applications, with support for enterprise level patterns such as Model-View-Controller (MVC); - Distributed architecture – CCF allows the creation of centrally managed distributed components. It helps in reducing latency, infrastructural costs and enabling offline operations; - Developer agility – CCF employs modern process driven development methodologies empowering developers through toolkits to reduce application development time while increasing quality and standardization; - Integration and automation – CCF provides non-intrusive application integration and automation both on the front-end (UI automation) and back-end (Service composition); - Security – CCF employs modern standards for securing communications such as WS-Security, WS-Trust, WS-SecureConversation, Security Assertion Markup Language (SAML) and Kerberos. CCF authorization model allows centrally managed role-based administration. CCF also provides E-SSO services to allow mapping of user identities across systems; - Scalability and reliability – CCF is designed to scale vertically and horizontally and can be used in clustered and load balanced scenarios.
CCF 2009 consists of four major subsystems: - CCF Middleware Server Components; - CCF Front-end Tools and Client Components; - CCF Management Solutions; - CCF Developer Tools.
CCF Core Services The CCF Core Services performs logging and reporting, configuration, session management, SSO credential storing, and other functions. It supports horizontal scale-out, clustered and load-balanced deployment.
Some of the notable highlights of the CCF Server include: - Agent Activity Logging provides records of transactions which can be aggregated in customizable reports to enable extensive business analysis e.g. to optimize Contact Center processes and customer handling; - CCF uses Enterprise Single Sign-On (E-SSO) and the Windows Active Directory® service to integrate authentication and authorization for agent roles and applications. E-SSO provides a way to map a Windows user ID to non-Windows user credentials. This is a key feature for businesses that aim to aggregate multiple applications spread over diverse systems; - Sessions management with session transfer supporting automatic application launching. If a step in a workflow process needs to be continued by another agent or at a later time, the session context, including the state of the supporting applications and information can be automatically transferred to the agent, restored later or transferred to another channel; - Applications configuration. All configuration information is stored on a core server. In the event that an agent’s workstation fails, the agent’s applications and operating state can be restored when the agent logs back on from another workstation.
CCF Distributed Connectivity Services (DCS) Distributed Connectivity Services (DCS) is an application infrastructure providing an end-to-end development model and reference architecture that enables a business-driven development model.
DCS provides service management capabilities such as transparent service location, dynamic client, context driven business process selection, scalable hosting of workflows and service configuration and a standards based security token service. DCS uses Microsoft .NET 3.0™, Windows® Communication Foundation (WCF) and Windows Workflow Foundation (WF) as its foundation. DCS includes reusable Application Blocks in a Software Factory to simplify solution development and deployment of processes and services.
DCS consists of the following Application Blocks: - Discovery Service Application Block – Allows client applications to discover at run time the service endpoints based on service type. DCS utilizes a Microsoft SQL Server® based repository store and a WCF based service discovery method (WS-Discovery); - Central Policy Store Application Block – It provides centralized configuration of service policies. Policies are consumed by the client application through metadata exchange; - DCS application server - The DCS application server is hosted inside Microsoft Internet Information Server and is composed of two main components: Task Factory – Supports DCS Business Logic selection based on a context; Workflow Host Application Block – Executes Windows Workflow-based Business Logic; - Security Token Service Application Block – Security Token Service implements the WS-Trust based authority service that issues SAML based tokens. Allows the configuration of external claim providers caching of SAML tokens for increased performance. Windows-based authentication of clients leverages Microsoft Active Directory.
DCS also provides the following patterns: - DCS Dynamic Messaging Patterns – DCS provides unique messaging patterns for distributed services in an enterprise to communicate with each other. These patterns include messaging to facilitate the client applications to discover the service location and communication policies at runtime, transportation of context data, authentication, and authorization. DCS Messaging Patterns leverage Windows Communication Foundation and have been built on WS- standards in order to maximize interoperability and extensibility; - Dynamic Service Policy Patterns – DCS facilitates centrally storing and managing the service policies. When the DCS based service starts, it contacts the central policy service, retrieves the relevant policies and configures its WSDL and receive pipeline according to the policies.
Configuration Server The CCF Configuration Server allows developers to dynamically create .NET configuration files from hierarchical sets of assertion about an application context. These assertions may be related to user roles, business environments or geographical locations for example. CCF also provides the ConfigurationUpdater client API that allows interaction with the configuration server.
CCF Databases The CCF Data layer is used to store configuration and audit information (activities performed by a CCF Client component). CCF requires the Databases to be hosted in Microsoft SQL Server to host the Databases. CCF also allows generating reports from the persisted audit information with SQL Reporting Services.
Application Integration Framework (AIF) The Application Integration Framework (AIF) is a software application framework that facilitates information sharing, interaction and communication between applications and processes running on the client. It is built upon the “Pattern & Practices” Composite UI Application Block (CAB). AIF leverages the CAB utilities and services for messaging, visual containment, application loading, state management, etc. In CCF, AIF is used by the integrated desktop: a Windows Smart Client that runs on the Customer Service Representatives (CSRs) workstation within Microsoft’s Windows XP® or Windows Vista® operating system.
The Customer Care Framework Integrated Desktop (ID) is a reference implementation that enables the reuse of existing line-of-business applications. It provides a composite user interface that clearly shows how applications and services can work together within shared workflows, computer telephony integration (CTI), and session management. Some of the key features: - ID optimizes the CSR’s desktop by combining existing resources into a single user interface. The unified user interface that ID provides enables CSRs to work more efficiently and with higher accuracy; - ID is highly customizable. The source code supplied with CCF is a reference implementation that enables the development of user interfaces that meet specific business requirements.
Hosted Application Toolkit (HAT) The Hosted Application Toolkit (HAT) significantly reduces the effort required to integrate applications in CCF. It allows applications to be hosted and automated in the Integrated Desktop with minimal coding. It provides an Application inspector tool, a set of Data Driven Adapters (DDA) and a visual designer that is used to create the business logic called Automation (click button A, copy data from textbox and paste it toâ¦), between hosted applications . This way the process of integrating an application is the execution of three well defined steps: Inspect, Automate, Host.
HAT has three major components: - Application Software Factory, a tool which allows visual inspection of the UI controls and generates an XML description file of the controls that will participate in the automation step, performed in a Visual Studio environment; - HAT Core Engine, drives automation leveraging Windows Workflow Foundation; - Data Driven Adapters (DDA) provides generic access to user interfaces through XML documents. CCF2009 provides DDAs for Windows-based applications, Web applications and Java-based applications.
Multi-channel Engine (MCE) The Multi-channel Engine (MCE) in CCF 2009 provides a common engine that allows UI processes to share common logic and metadata on different delivery channels. The MCE provides two major functionalities: - Separation between channel independent and channel dependent development. The channel independent components include all the logical aspect of User Interface, the navigational control logic, the logical information/data views and event handling. The channel dependent UI provides the actual navigational controls and visual representation of the information. The front-end multi-channel engine improves the consistency of the navigational logic amongst different delivery channels, increasing the productivity of the cross channels UI design. The standardization and reuse of the navigational logic will allow the developer of a particular channel UI to mainly focus on the particular physical layout and specific navigation of the channel; - The ability to persist an UI process state and to move it between channels. This represent a significant improvement in the user experience because it allows the interrupted acquisition of data without have the need for the user to start the process again all the times. It also enables the resuming of sessions across different delivery channel seamlessly!
DCS Service Agent The DCS Service Agent Application Block is a client component that uses the DCS discovery service to identify the target services endpoints and performs metadata exchange to determine service policies. It dynamically builds the send-pipeline as requested by service policies, including the standard DCS ones: encoding, security, client caching, logging and context transportation.
CCF Management Solutions The CCF management solution consists of three components â CCF Admin Console, DCS Admin Console and CCF Management Pack for System Centre. The CCF Admin Console allows an administrator to centrally configure all aspects of the Integrated Desktop running in an enterprise environment. The Console allows management of client configuration and runtime update to all clients and also allows federation of different components of the integrated desktop. The DCS Admin Console allows administrators to control all aspects of service based communication and DCS business logic. It enables to deploy services and tasks, add and edit Task Factory filters, change Discovery configured instances and policy on each instance. The CCF Management Pack for Microsoft System Center Operations Manager provides monitoring of business processes and infrastructure services through Microsoft Operations Manager 2007â¢. This pack also allows centralized management of CCF infrastructure components through MicrosoftâÂÂs System Center suite.
CCF Developer tools CCF provides a set of tools to facilitate rapid development of customer care solutions. - DCS Software Factory is a set of Microsoft Visual Studio add-ins and Guidance automation extensions that enable rapid development of workflow-enabled services using proven best practices. The Factory supports the creation of WCF based Messages, conversational workflows, service stubs from workflows and DCS service agents. It also helps in defining service contracts and services as workflows; - MCE Software Factory is a set of Visual Studio add-ins and Guidance automation extensions that enable the creation of logical views and UI process workflows, the creation of a physical representation of logical views for Winforms and asp.net; - HAT Software Factory is a set of Visual Studio add-ins and Guidance automation extensions that enable the inspection of existing user interfaces such as windows and web applications and the creation of UI automations as workflows. It also enables automatic deployment of the toolkit artifacts.
By clicking on the "Send" button, you agree that your data will be used to process your request. Further information and revocation instructions can be found in the data protection declaration.