This knowledge base article focuses on the role of Blueprints in the implementation process of the Sprinklr platform. It highlights the challenges faced prior to the introduction of Blueprints, the benefits they offer, and how they fit into different roles within the implementation process.

Challenges in Configuration 

Configuring the Sprinklr platform before the introduction of Blueprints posed several challenges: 

• Infinite Customization Options: The platform's flexibility allowed for infinite customization options, making the configuration process error-prone and resource-intensive.  

• Unique Setups: Each implementation consultant, managed services consultant, and success manager built the platform from scratch, resulting in unique setups for each customer. This diversity of configurations made troubleshooting and ongoing maintenance difficult. 

Benefits of Blueprints in Configuration 

Blueprints address the challenges mentioned above and offer several benefits in the configuration process: 

• Efficiency and Standardization: Blueprints provide standardized configuration templates, streamlining the implementation process and ensuring consistency across implementations. 

• Time Savings: By using Blueprints, consultants save significant configuration time that would otherwise be spent on starting from scratch. This allows them to focus on more advanced client use cases. 

• Cross-Departmental Alignment: Blueprints serve as a common reference point for all teams involved in the platform, facilitating collaboration and improving issue resolution. 

Roles and Blueprints 

Different roles within the implementation process interact with Blueprints in various ways: 

• Configurations and Enablement Team - The Configurations and Enablement Team is responsible for deploying the Blueprints and enabling all necessary Dynamic Properties (DPs) in the Production and Sandbox Environments. They ensure that the environment is properly set up before handing it over to the Implementation Consultants for further customization based on customer-specific requirements. 

• Implementation Consultants - During the Build phase of a project, the Implementation Consultants take the deployed Blueprint as a foundation and customize it according to the customer's needs. This customization is based on the information provided by the customer in the Build Requirements Workbook (BRW) and the insights gathered during the discovery phase. The Implementation Consultants tailor the configuration on top of the Blueprints to align it with the customer's specific business goals and objectives. 

• Managed Services Consultant: References Blueprint configurations as the framework for the client's environment setup and can also deploy additional, smaller, single-use case blueprints as necessary. 

• Success Manager: References Blueprints to understand how configurations meet customer business needs and explores the deployment of additional standalone use case Blueprints for value-added benefits. 

Configuration & Enablement Process

The C&E team follows two distinct routes for blueprint deployment based on the nature of the project. For projects that meet specific eligibility criteria—such as being for net new customers, having no phased projects, involving a single product (excluding SP&E), and not requiring integration or technical services—a new blueprint process is introduced to deploy configurations directly in Production. Projects that do not meet these criteria will continue to follow the standard Sandbox process to ensure thorough testing and validation before going live.

​

Blueprints have a crucial role in the configuration process of the Sprinklr platform, addressing challenges, improving efficiency, and promoting standardization. They align cross-departmental teams and provide a foundation for successful implementations. Different roles interact with Blueprints in their respective ways, ensuring smooth execution and customer satisfaction.