Hello and welcome to this webinar where we're going to talk about how to tailor Superfis to drive CRM success. Thank you for taking the time to join us today as we will talk about some practical tips on how to adjust your CRM solution to support your business processes. You will also learn the benefits of using low-code and no-code technology and explore how you can use it to get the most out of your CRM solution. My name is Jeanette. I've been with Superfis for seven years, almost eight. Started as a customer experience operative and now working in product marketing. And I like to call myself a CRM enthusiast and I have a passion for use for adoption, helping companies to maximize the use of their CRM solution. And with me, I have Philip, which have been with Superfis for 16 years, now as a product manager but you also have a background in different roles in Superfis. Welcome, and can you tell me a little bit about what you've done previously? Yeah, absolutely. Thank you, Jeanette, and nice to be here. And I have worked within a lot of things in Superfis, from support to services and sales. And I think that in our roles we have worked closely with customers to drive CRM success. So it's very excited to share our insight on this topic. Absolutely. So what we will talk about today is, of course, how you can succeed with CRM, in particular with customizations. We'll talk about why you should customize. And then we will introduce you to some of the no-code tools in Superfis and the different types of customizations. And we will give you some tips on how to make Superfis your own with tools that we have available, and especially with the focus on no-code, no-code. And we will show you some examples, and we will also show a demo. So we will have about 60 minutes, and then, of course, if you can't bear for all of it, you will get the recording after. And also feel free to drop any questions on the topic or share your experiences in the chat. And we will answer those questions as best as we can during the session, or we will follow up after. So what defines CRM success? It can mean many things, but I think we can all agree that a successful CRM implementation is dependent on how much your team uses the system. So you will see high adoption when reps can clearly see how new CRM improves their ability to do their job. And this should be the preferred solution instead of scattered nodes and outlook and other systems as a source of truth. Yeah, and I think one other criteria that defines success is when you gain better collaboration within the team and also better productivity in your everyday work life. And then the last thing here is that if you work correctly in the system, you get the good data visibility in the organization and that enables you and the management team to take their effective decisions for the business. And that's a key CRM success factor. Absolutely. I think also you need to trust the data, because otherwise everything else will fail. And I think it's often difficult to quantify how CRM has contributed directly to achieve business success. But if you link it to your CRM strategy or with business KPIs, that will help you set direction. And these three points that we're talking about here is very important in setting those goals. And we actually asked on LinkedIn what's on your to-do list to ensure CRM success in your organization. And we were hoping for Taylor the CRM solution, as this is what we're talking about today. But of course there are other things as well that's important. And the audience voted buy-in from all stakeholders. And why do you think that is Philip? Why is buy-in so important? Yeah, I think that the daily work within the CRM system must be connected to the company's routines and goals. And those are often set up or handled by top and other stakeholders. So you need the strategy and ownership here. And I think that's the reason why. Yeah. And that's also what we see in the lack of CRM success, the common reasons. Yeah. And you see here on the people part here you have the lack of leadership and the clear objectives set. And then you will get poor user adoption for that. And then there could also be a lack of training that the people don't know how to actually use the system. Yeah. And then you have the processes part. And that's if you fail to align your daily work and the business operation with what you're actually doing on a daily basis. And then not planning for change if something is changing for you. And that's not reflected in your processes. Absolutely. I think yeah. And also in that part when you say about not planning for change. I think if you do not customize your CRM solution or you do overdo it, then it's the same problem. You end up with a system that maybe no one's using because it's not supported properly. And then again you end up with poor data quality as a result. Yeah. That's the technology part here. You need to use the tools and the technology in the right way. So it's very important as well. And then the last bubble here is about the business goal. And that's if you haven't have it defined clearly enough. And if you don't have the dashboards or KPIs within the system, I think you also have a reason for lack of CRM success. Yeah. I think it's important to use the data correctly. Focus on the goals. Talk about them in meetings and kind of use the system actively. From top down as well. So it's a part of your everyday work. And you can use it to talk about the data, use it in dashboards, competitions and so on. Yeah. So there are many factors to consider when we're talking about CRM success as we saw in the last slide. But this is what we will focus on in today's presentation. So we will focus on the user adoption, the process support and how to link these two business objectives. So how do you get started with this, Philip? Is it just by the CRM system and you're good to go? It can be tempting actually because Superoffice is out of the box. It's easy to start. But I think that you need to do the software your own. So you need to look at your processes and get them inside the Superoffice CRM solution. And then you need to link them to the objectives that we discussed also earlier. So you can track the right KPIs and see that you are actually doing what you set up in your processes. I say tailor it to support your business. So it's becoming that business critical solution. I think that's the goal. And I actually hear this all the time when we're talking about or talking to customers that CRM is not a mandatory system like ERP for example. That's why it's harder to maintain and ensure that good data quality. But I think and I hope that we all agree that CRM is in many ways a business critical solution. Because it's helping you as a company keeping your most valuable assets, your customers in focus. And as you said, you can start pretty much straight away with when you buy Superoffice. You can add your contacts. You can start saving those customer interactions. And I think we've always said like you should keep it simple and it should be transparent. That way it's easier for users to adopt and work in the solution. Yeah. And there are so many benefits for using an off the shelf software like Superoffice. You get the solution built on 30 years plus of years of CRM experience. But also the cost savings available by sharing the cost of developing new features and functions. As well as running the software in the cloud between thousands of other customers. However, there are also many reasons for customizing software so that it better reflects your particular business needs. And now we're going into the details where you can tailor information via use of the configuration, guides, labels. But also now the new screen designs that we will have a look at. And then you can get automations from CRM scripts, macros and triggers. And also enhancing and optimizing workflows and supporting your unique business needs and goals. Yeah. But I think when we're talking about unique business needs and goals, no two businesses are the same or do they have the same exact problems. And I think your business processes, your goals, they should be supported and visible in your CRM. So that your different teams can collaborate seamlessly and also where the customers truly are at the center. But I think as businesses evolve and your customer needs change, you need to evaluate your processes and continue to adjust the CRM solution to the way you work. Because we need to adapt to new channels, touch points and strategies. And that's actually a strong competitive advantage. So it's not just a set it and forget it type of solution. You need to, it needs a bit of work like in all other relationships. So when we're talking about customizations, it's not just a one off. It's a continuous effort. Yeah. And then you could think, okay, how do I start and what's the benefits of customization? So I think that we need to see that if we have better efficient process support, then it saves time and costs. And that will also improve data quality and reduce user frustration. And then you will automatically get the users in and get increased user adoptions. Because you simplify the task and get automations for the user, right? So it gets more fun, more easy. You don't need to work harder. You work smarter in your daily work. And then you will get the competitive advantage. Improving customer engagement, satisfaction levels from your customers. And then resulting in acquiring more customers and retaining more customers. So I think that's the benefits of customization. Yeah. But usually when we talk about customizations, people think it's too difficult. It's too expensive. But this is possible and it's made so much easier because of new technology like we're talking about today with the low code, no code. And this is also a strategic vision of our R&D department. Yeah. And this is a quote from our CPO, Guttorm Nilsen. And he says that sustainability focuses on meeting the needs of the present without compromising the future. So it's very important when we are talking about customizations of a business critical system like our own CRM solution, it can't be too complex to maintain or to make changes. As your business grows, you need to change your way of work and the tools you use. And the CRM solutions that cannot change quickly will become outdated and hinder the way you work. Not to mention the cost involved if you need to bring in experts to update or make new customizations before upgrading the system. So it's all about sustainability here as well. Yeah. And when we're talking about low code, no code as their name states, they required little or no involvement from software developers. So it's easy for the everyday user to use visual interfaces, drag and drop menus and other solutions to create and change and customize applications. And this makes it easier to... You need less time to define, to test, to implement, and you get less complexity. Also, it's less maintenance like you mentioned in terms of the sustainability part. And you can also iterate. If something doesn't work, it's easier to make those changes and improve a specific area and deploy as you need it. Yeah. So how do you do this in super office? I think that with our sustainability customization strategy, we want you customers to maintain and develop your own CRM solution as much as possible. So it's no wonder that we are keeping investing in our no code and low code options, making them stronger and more flexible as recent technologies allow us to do so. Yeah. So let's take a look at some different types of customizations in some slides. And then later on we will demo how to set up some of the examples using the no code, local tools in super office. So when we're talking about customizations, we have different set of tools and types of customizations. On the first level, we can make changes with configuration settings and preferences. And this is done in the admin client inside the solution. And these are available to everyone using super office as long as you have admin rights. So this can mean adding or changing lists, fields. We can add document templates. We can change simple user preferences. We can change labels. We can add project or sales guides, etc. Yeah. And also within the product, we have more tools. We have scripts, we have macros, we have the screen designer. And here we can extend the super office functionality with automation and workflows using these CRM scripts and macros. And with the screen designer, we can customize screens and layouts. And all of these customizations are done in super office. But usually you need to know a little bit more than just set a simple configuration for a setting in admin. But it's still the cost of ownership is still low to medium. If you're also using the cloud version of super office, you can use standard apps from our app store. We have like Sapir, for example, to in a standard way connect super office to other system for enable to automate your processes. But alternatively, if you can't find a standard app, there are possibilities within our API and our APIs where you can develop your own integrations and applications that works together with super office. And all customizations created with these tools are automatically deployed and operated on the platform ensuring your customizations are sustainable and robust over time. But here we have a cost of ownership that is a little bit higher here, medium to higher. And we're focusing on the easier low code, no code options today. So let's see some different types of examples or customizations in super office that will help you to save time. And we'll make it more productive. Yeah. So this is the examples of no code, low code that we have in super office. Yeah, so these are the standard based no code configuration. So 80% of this is just configuration. And they have a small part here, 20% maybe low code. That's what we call scripting here. So first we talk about configuration. Here we add fields, we change labels and that kind of thing. And when we've done that, we have the new screen designer when we can adjust screens. So we can design the relevant fields are available and also adjust the layout. And then the macros, they can be rule based actions to improve productivity. And then scripts, it's a high level programming languages to allowing you to customize even further. We have some examples of that as well. And then we have the standard apps. You know, in the ecosystem there's a lot of already made customizations like outlook synchronizer or calendar of calendar or integration to ERP. Yeah. And if you cannot find the standard app, you have the custom app, for instance, to integrate to internal systems. Yeah. So let's start by talking about the configuration part, but this is the easy part we can start with that. This is for everyone that has admin rights, you can set up and change this. And we actually meet so many companies who do not use this actively. Maybe they did when they first started and set up their solution. But these lists are so easy to change and maintain and adapt. And it's the easiest form for customizations. And the profits contains many default lists such as customer categories, business types, activity types, sales types, and many more. So if you want to change default lists to fit your company jargon and processes, you can easily edit these lists. And the solution is designed to fit the activity types for most businesses, but some might want to create their own. So depending on the type of business your company is in, you can tailor the system to meet your needs. So for example, you can customize all the main categories to reflect your types of activities. You can add new, you can deactivate those that are not necessary, or you can also edit existing ones. And some of the lists are more common to make changes on. For example, category, business, company, and contact interests. And we also have document templates. But you can configure the list to make it the way you work. We can also customize subscription types, privacy lists, and request tags. There's many different types of lists that we can edit in supreface. And then we have user defined fields. And like we've talked about before, it's all companies and organizations have their own requirements for the information they need to register. So this could be for customers, it could be sales, projects, contracts, and so on. And as an administrator, you can add your own fields. You can add extra fields to all modules. If it's sales, marketing, it can be a project. And you can also decide what content of the field should be. So it doesn't matter if it's free text, a date, it can be a preset value. It's all possible. So for example, by customizing your CRM, you can use find and the selection feature to segment your data based on your own value send fields. So if the follow-ups and actions in your CRM system reflects your sales process, then you can create more accurate sales reports. And like you see here in this example, we've added a field last service control. So we can level up by doing even more. We can, based on this field, we can merge this data into documents and emails using template variables. We can create automatic follow-ups, like booking a new service control activity in six months. Or we can just use it as specific information for the service team, like creating different layouts based on the type of data we want to display to the different teams. But then we're talking about doing some more customizations in the layouts. Yeah, because now when you have customized your fields now and your lists in Superoffice, and the next step is to configure the layout. And here you see the screen designer that we introduced in version Superoffice 10. And it lets you configure the layout of the company card, the contact screen, and also sale and project screens. And then you can fit your information needs and workflows even better. For example, you can create different layouts to match the needs of different teams and user groups in your company. So I really like the configurable screens. And you can add new fields. You can position fields where you want. You can hide the fields that you don't use. You can make custom fields easy to access. And you can also create and adjust archives, you know, the tabs that are underneath the main card. And different screens layouts can be used differently for different user groups. And also you can reduce the information noise. If you have a lot of users, a lot of teams, then there can be a lot of information in the system. So you can reduce the noise and help users find information easily and stay focused on what matters the most. So I think that that can increase user adoption by catering to specific needs of your team. So here we see an actual example when we have used the screen designer to reduce the noise. We see a company card. And you know that if you work a lot with customers you will get an activity tab filled with information. And here is an example where we have highlighted some very important sale documents. Here's a subscription agreement that is highlighted and just the special types of documents will land on this tab. So it's a good example how you can reduce the noise and easy find a very important type of documents. Yeah, I think also you can, like if you have signed agreements that specific type can then be shown just in this tab, right? So you can add different information needs in different tabs. Like you said, the activity, it has all of the interactions. But this is a great way to show that what's important to me as a salesperson for example. Yeah. And then we can use the screen designer on different entities. Here we do it on projects. And here we see that we have a certain type. We have the advanced project added. And then we will highlight some fields that is very important. So in this case, we need to have a product owner, we need to have a product manager, we will have a budget and other fields you need for these kinds of projects. And this works the same way for sale and sales types. So you can also use this for example when you have a sale to a new customer will trigger some fields, but a sale to an existing customer probably asks for less fields for instance. Yes. And then we will move on to some little bit more advanced because what you see with the screen designer is typically what we talk about when we're talking about no code or low code. Macros is also a way to improve productivity and reduce manual tasks through customizations. It's a step up from the screen designer because it's a little bit less visual you need to understand where the data is and the behavior of the profits. But it is a user friendly version of CRAM scripts. So you're able to customize and automate actions inside the profits with an easy to use wizard so that will help you set up your macros. So like you see here in this example it's a step-by-step example. Sorry, step-by-step wizard. And it's a set of predefined actions executed in a specific order. So you don't need extensive knowledge about scripting to create macros, but again, you need some knowledge of how Superfist behaves and where to find that data. So there's a number of functions in Superfist where you can use macros. They can be linked to specific triggers in the system such as escalations or new message on a request in Superfist service. It can be assigned to buttons in defined screens so that users can click a button to perform a set of actions that are often repeated. And this also makes user work faster and they avoid unnecessary clicking. Yeah, and now we'll see an example and this is actually one of my favorite features that you have. Here is also a sneak peek of our new request management solution Merge in Core CRM. But what we show here is also available in the current version. But instead of typing some information here, update status, we can do everything with two clicks here. So under the task button, we have a choice here that says move to invoice department. So what we're going to do here is that we will change the category to finance. We will update the status and we will also get back to the customer with some information so that we have seen his question but that we are currently processing it. So just two clicks and then you will get all the updates. The status is updated. We have get some more messages here in the request that you see. Yeah, category now is administration finance because this was a finance question. And here we see that we have an internal note and a comment that this has been moved by us and also a reply back to the customers that we're still processing this so they receive something back from us. So here is... I think that it's just your imagination here and your daily work that sets the limitations. So if you can figure out this, I think it's really fun to do. Yeah, and it saves a lot of time as well. It makes it more fun to work with when you don't have to do many, many manual clicks. So NCRM script is a feature that allows you to automate tasks in or modify the behavior of superfaces as well but it is a script that is a little bit more technical. It's a small program written to perform specific tasks and it requires programming skills to set up in comparison to macros, for example. So this is something consultants or our partners can help you with. But here are some examples of what you can do with CRM script. You can customize your workflows and automate. For example, you can use scripts in service by setting up if this, then that workflows to optimize your processes. You can also validate input. So if you want to make sure that users are familiar with the correct data, even in user-defined fields that we talked about earlier, we can block a save if essential fields haven't been filled out. For example, do not save company if VAT number is missing. And we can also dynamically update content and we can run a code in response to certain events on a website, like what should happen when a new ticket is registered or a sale is confirmed. And these scripts can run based on triggers, like a certain event in the system will trigger one or more predefined actions. Or they can also be scheduled at specific times. So this is just an example of a script, but we're using a triggered dialogue. So this is a way to interact with users through or displaying a dialogue box and acting on a response. And this also actually works in our app, Mobile Serum 2. Can you move? I will just hit play. I think you can talk over. Yeah, that's fine. So here we listen to what happens in Super Office. And it's actually that the sale here is set to sold. And then we add some reasons here. And then when we press save here, we will trigger a dialogue and said that will we celebrate this and add this to a team space. And then this is the actual trigger dialogue when you can act on responses. So here you can say, no, we don't want to celebrate this. Or of course, yes, let the world know about this or trigger this to another system. And this is what we're discussing here. So it's both a trigger and it's also a dialogue and then the dialogue and the answer will take you even further. So here you can really set up a workflow or a process. Yeah, and we actually have another example of how we're doing this in Super Office. Yeah, I actually discussed customizations with our support team recently and they mentioned this to me that they used to you know, support team, they work a lot with team viewer to see our customers' behavior on screen and guide them through the software. But daily they were doing some manual tasks sending out information, logging in to team viewer to get the right link and then send it back to the customer. So it was quite a few steps and it took almost one minute to do this. So they actually said, can't we just use this action button here and say that when we press the team viewer remote we will talk to team viewer software, get the link, send it to the customer and start the meeting. So I think that that takes now two seconds to do and before it took almost one minute so it was a huge time saver for our support team. Absolutely. It's a great example actually of what's possible with using scripts. Yeah, definitely. And then I also reached out to one of our customers and this is a quote from him. He said that the strong customization capabilities was one of the main reasons why we choose SuperOffice. It's from Thomas Walker-Wall at Martinsons and I also said can you share some examples that you do within your company? And he showed me really simple but useful customization and here we see that we have a sale date and we have a stage and they were really interested in following up after a certain stage. So here the stage is present offer and then when it's added in that stage they have presented the offer and then automatically a follow-up should be entered after 14 days so that you could always check back to the customer what they thought about the presented offer. So it's an easy yet very clever customization that they did. So it's registering an activity 14 days ahead so that you get that reminder. It's an easy one but it's still a very powerful customization that will help you get, I'm guessing more happy prospects as a customer. Get on top of your activities. And there's one more thing, you've actually added some trigger dialogues as well, right? Yeah, it's also, they check some... You cannot actually set a sale to sold if there aren't signed agreement from the e-signature solution. So you need to have the contract signed in order to set the stage to sold. So validating the... That was another one. And then I'm guessing as we talked about you can also show this in a separate tab, right? If you have one for sales documents in particular. And then I think the final one that deserves to mention is the App Store because you do have a lot of ready-made apps that will help you extend functionality and discover new possibilities with the cloud version of Super Office. So we have over 120 apps in our App Store and these will help you to increase your productivity, customize your service solution and in general just offer a better online experience. There's a lot of apps and we keep adding new ones. So it's a tip to take a look at the App Store and browse the different apps that we have. They're also separate or different categories. So it's easy to browse. So now, next up is let's dive into the product and actually see how you can tailor Super Office with the no-code options that we have. We will add some new fields. We can also add a new archive and change the layout a little bit. And I think we will try to add a macro as well. Exciting. In this demo, I will show you some examples on how you can adjust your serum to support your business processes. Super Office serum can be used out of the box so it's easier to get started and it comes with some set of standard fields and lists like for example category, we have business and you can also fit three customized fields on the first page like this one. And if you want more, then you can add them to the More tab. And we also have different tabs here with contacts, projects, activities and so on. And on activities, for example, we have different activity types and documents and these are also lists in Super Office that we can change easily. And all companies and organizations have their own requirements for the information they need to register. And we in Super Office, we want customers to be able to maintain and develop their own serum solution as much as possible. So now I will show you some ways you can take advantage of the low-code and no-code features in Super Office to easily tailor it to fit your specific needs. So what we will do today is we will add some more fields. We will add a new list. We will customize an archive and we will also change the layout for different teams. And at the end, we will also add a macro to perform a set of actions that are often repeated. This makes users work faster and they avoid unnecessary clicking. So let's go to settings and maintenance. And here we will start by adding some new fields. And these are some that you saw on the More tab on the company card. We can also add it to the contact card, project, sale, follow-up or document. But let's start by adding some to the company card. Now let's start by adding a field with discount. We can change the type of field. Let's save this one. We also want to add a field with a date showing when a customer has bought and become a VIP customer. And we will also add the discount field to the sales screen. Now we can add some more lists. So we want to see when a customer has signed a VIP contract. And also we want to plan some VIP onboarding activities. So let's start with a template. We'll find this under lists. And here we have a proposal for our premium service. And then we will add a new one called signed contract for premium. And we will also add a new activity type. So now that we've added some new lists and fields, we're going to customize specific layouts and screens for specific types of users. So let's move on to the screen designer. Here we can make changes to the specific screens in Superoffice. So here we can make changes on the company card, the contact, sale, project and request. And we can also make changes to the archives. And we will do both. So here we have made layouts for specific user groups or teams. So we have a default layout. We have one for customer service. So here we can see the fields change. We have NPS score, last service control and onboarded. And we have for sales. So here we have the one we saw before, the number of employees. And we also have a button linking to the LinkedIn profile of the company. So in this example, we want to continue customizing for the sales team. And we want to add the company discount and the VIP fields that we added before. So here we can use the visual editor to design the layout that we want for the specific teams. So we can use this visual screen designer to drag and drop and rearrange the layouts that we want. So for example, we can remove certain fields that are not necessary for a sales team. We can add new ones or we can move them around in different tabs. So let's add the discount field and the VIP customer since. And we will add that to the more tab and then we will save and publish. So these changes will only be for the sales team. The customer service team will still have their own layout. In addition, we want to make some changes to the archive. So we want to add a specific tab for sales documents. And this will only be available to the sales team. We can also add finance department and administration, for example. Press OK. Then we will edit the layout. We will add a new tab called sales documents. And we want to filter specific content. So we want to see only documents with the type proposals, sign contracts, quotes and premium contract. And then save. So now we have a separate archive just for specific sales documents. We'll also do some changes to the sales card or sales screen. Let's go to sale. Go back to main cards. So here we can also add some different layouts. Maybe we want to customize this to the sales team that only works with new customers and prospects. We can edit this layout. So here we will add a new tab specifically for the new best sales team so that the sales rep can add their comments and their plan on how to close the sale. And we will keep it at two columns. Call it close plan. And then we will add a grid. And we can change this to two columns. Six rows. So now we'll add some of these fields that I have prepared and add them to the grid. I will add reason to buy. Main risk for deal not to happen. If we have the budget secured any comments to that. If we have access to the one that signs and also who will sign from the customer side. Okay. And then I will save and publish. So now we have a separate tab where the sales reps can fill out more information regarding how they plan to close the sale. And the final thing that we will take a look at is a macro before we go back to super office and see all of the changes that we have done so far. Now macros are a little bit more complicated but I want to show you what's possible even without technical or programming skills. So let's go to serum script. So from here we can add a new macro and connect it to a button or a menu in super office and then manually trigger it from there. Or we can add a trigger so that the macro starts when something happens in super office. And here we have different triggers to choose from. We have requests if they're changed. We have chats or we can do things before or after a save in serum. And in this example we want to focus on the premium contract. So when the signed contract is archived into super office certain things will be updated on the company card and we will also create an onboarding activity. So here I've already set up a trigger based on after saving document that we want to change a company. So if we have the document type signed premium contract and it's completed. Then we want to update a company with a new category VIP customer and we will also update the date. Then we want to create an onboarding activity. So we add the VIP onboarding type. We add a title. We add the owner. And we'll set 14 days from now with a time and a duration. And then we also want to give a confirmation to the user that the customer card has been updated. And if you want to edit or add more steps then you can add it here. So here you can see we have different options. So you can build this step by step in this wizard. So now let's go back to SuperFest and see the different changes and customizations that we've made. On the More tab we have the new VIP customer sins and the discount. And we have the sales related documents in a new archive tab. Then we can move to Sales and find an open opportunity. So as you see here we have a discount field which we can update manually or we can connect it to an ERP or another and then we have the new tab with the close plan. So we can add our comments, check the boxes and add more information on how we plan to close the sale. And now let's test the macro. Let's say that we've got a signed copy in return from John Smith that we want to archive into SuperFest. So we will create a new document and here we can add a title and we choose the signed premium contract. And in this case we have a local copy but this can also be archived from an email or we can connect it to a digital signature system and archive it that way. But remember that we had to set it to complete. So let's open the document again set it to complete and save. So now we get the message congratulations on your premium service sale. The company has been updated and a VIP onboarding has been created 14 days from now. So let's check the company card. Here we can now see that the category has been changed to VIP customer and on the more tab we have VIP customers since and a new date. And we also have a new activity created, a VIP onboarding that's 14 days from now. Now there's many ways we can use this type of data. We can use it in document templates or we can add dashboards. So here I've made one for the sales team. So here you can see the upcoming VIP onboarding sessions. So this is just one example. We can also use them in selections. We can reuse the data in email templates. There are many, many possibilities. And this is a great way of using and visualizing the data that you've customized and some examples of how you can make the CRM system support your workflows and processes and again help your teams be more productive and unique customer experiences. Okay, so that was the demo. I hope you got some inspiration from that. But I also wanted to ask you, Philip you've been in the game for a long time and you've talked to a lot of customers seen a lot of solutions. Do you have some tips to our customers on how to get started with this customization? Yes, definitely. I think that first you need to understand and know super-office a little bit better so that you understand the capabilities and the building configurations and I think this webinar is a good example how to do that. And there are also a lot of other resources in our community, help file and also all the great people of super-office that you can talk to. So understanding get to know the super-office product a little bit better. That's a really good start. And when you do that you will get some ideas and then it's time to define your needs and outline your requirements. What is important to you? Like we saw in these examples what's important for the supporting, what's important for the sales team and so on. And then you can also seek advice because maybe like you told us there's already an app doing this. Maybe show something on a map or an integration to systems that already is done. And then you're all set, right? But otherwise after you you come a bit more ahead and done some configurations to support your team it's important to revisit them. So you check back is this still a good way of doing it? Are you reaching your goals? Why you actually did this? So that you continuously revisiting them. And then when you do that I think that you can fine-tune processes and achieve even more results. You will get even more ideas work even smarter. And then the last bullet point here is that you need to have someone or a group of CRM ambassador that document why you do this what's the reason behind it so that you can also follow up on this. So appoint someone that's responsible and document the changes on what you're why do you have a field in Superoffice for instance? Why do you use it? Why is it important? I think that's actually a very important point as well to document your changes. We actually have given out a routine guide so that you can make it your own and keep updating it kind of telling the users how to use Superoffice but also why? And why have we added these changes or fields and so on? And I think also we put ambassadors in plural as in a group because if you only have one and that person is sick or quits then all of a sudden no one's owning the CRM system and the processes and then it kind of gets to that point where people kind of start to slack and don't add the good data and maybe the routines and the setup doesn't make any sense anymore. So I think that's important to kind of have a group that's continuously working and improving the system but also document in that change. Yes. Filip, you want to talk about the Yeah, definitely. In Superoffice we have tools to customize yourself so you don't need a consultant for small but important changes if you just log in to the administration client and try it out yourself but also when you buy into Superoffice you also buy into a partnership with people who truly understands business other businesses and we are here to help you maximize the value of the technology and the CRM solution. So don't hesitate to talk to your Superoffice representative your partner our consultants I mean they optimized Superoffice for thousands of customers during the years so they are quite used to the processes and what we can achieve. So you can do a lot yourself but also don't hesitate asking someone who done this before. Absolutely. And I think also like we mentioned you can just log into your admin and get started and I think you can start by customizing to your needs and those options that are available in the settings and maintenance modules in Superoffice you only need the admin rights to do that which we talked about the user defined fields we talked about the lists and also using the standard apps and integrations in our App Store. So you don't need any special license to use those tools. However if you need more than what is available out of the box this means customizations like custom screens or configuring the layout with the screen designer for those instances we have an add-on called development tools which is a range of tools and add-ons you can use to create customizations of your Superoffice remit solution. So this is a subscription that will give you the configurable screen capability as well as access to macros scripting and there's a lot of more expand or expander services that we've called it before that you will have access to. So as we've shown in this presentation there are a lot of exciting things that you can do to customize your service solution and as always your Superoffice rep is more than happy to help you with more details regarding development tools and also talk to you about the possibilities. But I think it's important to reiterate this that it's a continuous effort really. You can do one easy customization like lists and fields in Superoffice but just know that you need to revisit it and to have that group I feel it's the best idea. Discuss the needs of the users putting your or linking your KPIs, your business goals and making a CRM strategy is very important and kind of making that into a continuous effort. Do you have any additional comments Philip? Yeah I think that you need to get you need to spend some time during a meeting with your colleagues to discuss this topic how can we do this better are we doing the right things do we have the KPIs in place maybe a dashboard for instance where we can see that we are on the right track so you don't have the daily work in the daily stress and activities taking over so that you need to remind yourself and the team of why you're doing stuff and make sure that it's still the best way. So continue to invest some time and follow up on the goals I think it's really worth it as the journey with the CRM system evolves. Yes So I think that's all we had for today. I hope you all got some inspiration start mapping out your needs, talk to users start documenting and start trying with the options you have available in the solution if you want to discuss how you can take that further, how you can customize maybe with macros or screen designer for example then reach out to us we would be happy to provide you with more information so thank you so much for joining and I hope to see you in an event soon. Bye Thanks


Hello everybody, last time in the module 1 we told you about the course and about algebraic topology in general, we also showed how a fundamental problem in algebraic topology is shown to be not solvable by solving a corresponding problem in group theory, this was due to the only course. So, today we will introduce the concept of homotopy, the two problems that we have stated namely lifting problem and extension problem. So, let us see what homotopy is and how homotopy is going to affect this thing. So, let me tell you something about homotopy itself. In analysis often we need to approximate a given function by nicer functions, maybe some kind of linear maps or smooth maps and so on. This is one side, this approximation is something that we have to keep in mind. On the other hand in physics there are certain, there is one certain property namely those properties which have this this particular property, they are the ones which are more interesting one for physics, namely called stable property. In terms of for me who does not know much physics, what it means is the following. Suppose you take a system and disturb it a little bit, the system should return to the original position by a one and so on. That little bit is to be made precise and that precise way is nothing but homotopy, we will come to that one. The classical idea which was all the way back to Lagrange which describes this, the perturbation is what is called mathematically is the notion of homotopy. But the modern definition of homotopy that we are going to study is due to Brauer, okay? So, let us make a definition, take two typical spaces X and Y, let I denote the closed interval 0, 1. When any continuous function from X cross I to Y will be called a homotopy. Whenever you have a function like that, the first variable is the space variable, the second variable you can think of as time variable that is why we denote it by X comma t. So, when you fix a time variable t, you get a function from X to Y at the time t. So, these functions are called, are denoted by little ht. So, often people in the in classically they used to think of this as a family of functions from X to Y, the family being indexed by the set I. It is very important, it is not just a set, it is the space time space, namely the interval in some interval in R, that is that continuity of the time is very important. So, the continuity with respect to t also, it is not a separate continuity, continuity in X and continuity in t, that is not the correct thing. What we need is a joint continuity from the product space X cross I to Y, such a thing is called homotopy. So, this is the modern definition. Symbolically, whenever such a homotopy exists, the homotopy from H naught which we will, we may call it as F and H 1 at the time 1, it is called as G. So, whenever such a thing exists, we say F is homotopic to G and write it in this way. So, that is the definition. Now, if you have a homotopy H, you can define another homotopy H trigger by just reversing the time, namely t being replaced by 1 minus t. Then at time 0, it will be G first, then when time 1, it will be F, that will be homotopy from G to F. So, what this shows is, whenever there is a homotopy from F to G, there is a homotopy from G to F. So, the relation, if F is related to G by this equal, whatever this symbol, then that relation is symmetric, that is the meaning of this one. So, on the other hand, it is very easy to see that F is related to F, all that I have to do is H of X t, ignority is H of X t is F x. So, that will be the identity homotopy itself from F to F. So, the relation is reflexive. Finally, to see that it is transitive, suppose you have a homotopy G from G to H in addition to homotopy from F to G, then you can put these two things together, it is called juxtaposition one homotopy with another homotopy juxtaposing. So, what is the meaning of that? This is explained here, technically, completely, rigorously, namely, in the first half of the interval, you define it to be H. Only thing is, you fill up the interval by speeding up, you take the double speed, X going to 2t, F of X t going to H of X comma 2t. Exactly, similarly, you have to do it in the other half of the interval. Only thing is now the 0 is taken by half and 1 is taken by 1 only. So, you have to do a shifting also. So, this will become X comma 2t minus 1 applied to G applied to that one. In the interval half to 11 equal to 1. So, such a function is automatically continuous because the first half of X cross 0 to half, it is H that is continuous. In the second term, X cross half to 1, it is G it is continuous. And on the intersection, which is X cross half, it is both all these things are closed subsets. These two functions agree. So, there is a one single function though there are two formulas. So, this F becomes a homotopy from now H X 0, which is F to G X 1, which is H. This shows that this relation whatever you are wrote is an equivalence relation. Reflects you symmetric and transitive. So, here is a picture which tells you this X cross 0 to 1 and the half part X cross 0 to half, I have taken H then the second half I am putting it G. So, they patch up because on X cross half what is the function? It is the function G there little G. Here it is F, it is G here, it is here H. So, F homotopy to G, G homotopy to H means F is homotopy to H. Set of homotopy classes of functions maps from X to Y, it will be temporarily denoted by double bracket X Y. This is a set now. See already we have started doing algebraic topology here, started with spaces from X to Y and maps from X to Y. We have constructed purely a set of equivalence classes here of functions here. These are basic objects of study in algebraic topology. He says an element of this double bracket X Y is always represented by some map F from X to Y and that map will be denoted that class will be denoted by double bracket F. Now, we have to study what happens under compositions and so on and that is the next lemma. All right, next lemma says that suppose F and G are homotopy from X to Y. Now, suppose there is a map from W to X, then you can first take alpha and then follow by F, first take alpha, follow by G. So, if you have two different maps, they were themselves will be homotopy. Similarly, suppose there is a map beta from Y to Z. Now, you can take first F from X to Y, then beta or first take G and then beta. So, those will be also homotopy. All these follows if F is homotopy to G. Pre-composition and post-compositions of homotopies is a homotopy. So, this is the message of this lemma 11, fundamental lemma. Proof is very easy. All that you have to do is corresponding compositions of homotopies. Starting with the homotopy H from F to G, take H, composite alpha cross identity. What does it mean by alpha cross identity on the W part? Remember alpha is the map from W to X, right, alpha. So, on the W part, it is alpha. On the I part, it is the identity. So, alpha of W comma T is nothing but alpha W comma T. Then apply H. That will give you homotopy in what between F composite alpha and G composite alpha. Similarly, if you take beta composite H, that will give you homotopy of beta composite F and beta composite G. So, those are the proofs which is very straightforward. Now, we can sum up what the effect of this lemma on these sets. Look at the starting with two a pair of topological spaces. We immediately wrote down this set. What is this set? Take a continuous function from here to here. Take the homotopy class. So, this is a set of all such homotopy classes. This assignment has some wonderful natural properties with respect to compositions. If you pre-compose alpha, you pre-compose this class with an alpha from W to X, a function from X to Y will become a function from W to Y. So, what happens to the class? The class will become a whole class. There is no change. That is the whole point here. So, alpha check from X, Y to W, Y, these are now sets will be well defined. A homotopy class here goes to homotopy class here because if two functions are homotopic here, alpha composite, F composite alpha, G composite alpha, they will be homotopic here. So, that is the whole idea. Similarly, you can compose with once more. So, alpha and beta from Z to W, then alpha from W to X, then what you get is alpha composite beta check is beta composite alpha check. So, this is all pre-compositions. Exactly same thing happens on the compositions on the right also. Then we get new composite gamma. Now, this time we have notation, the checks are suffixes. Here we are superscripts. Here it is pre-scripts equal to new check composite gamma check. Moreover, one more important property is that if you take identity map, then identity check is nothing but identity, whichever way you take either pre-composite or post-component. Okay. How to get this one? I have told you. It is just lemma 1.1 that we have just seen along with one simple property namely associativity of functional compositions. F composite G bracket, bracket report, composite H, you can put the brackets on the other side. F composite, bracket G composite H. So, that is associativity. That is all you have to keep using. In fact, let us just clarify this one. There is no hanky-panky is being done. Okay. Just to be very sure. So, let us verify one of the property in the first one namely start with alpha composite beta. The upper check I want to show is equal to beta check composite alpha check. It interchanges the slots. That is very important. Whereas if you take the lower check, then it will be alpha check lower, beta check lower in the same order. So, let us verify this. So, what I have to do? Operate on F. F is a function from x to y on both sides and verify that they are the same. So, I start with this one. What is the definition of alpha composite beta as a function? Check F. It is F composite this function alpha composite beta. Now use the associativity of this composition. It is the same thing as F composite alpha composite beta. But then this is namely beta check of this function. F of alpha, F composite alpha. But F composite alpha is alpha check of F. So, beta check of alpha check of F. It is just beta composite alpha check check. Exactly same way you can verify the other one also. As I have told you, I keep repeating this. The workspace of algebraic topologies in the whole later on we can make it smaller and smaller. In the whole is all topological spaces. And for each pair of topological spaces, the set is namely homotopy class of maps from x to y of homotopy classes of maps from x to y. This is the one which you are interested in. Not exactly the maps but the homotopy classes. Modern mathematics is full of such collections of assignment. So, we have assigned, starting with a pair of topological spaces we assigned. So, you know we study this set. This set when you take special cases will have lots of structures, different kinds of structures. And that is what we will have to study. So, the property of this assignment which we have seen just in the previous remark. So, those properties are themselves called, you know, they are categorized. They are, you can say, they have been put inside a kind of discipline which is called categories and functions, which is part and parcel of algebraic topology. These categories and functions gives you the basic language required to express so many complicated ideas into simple language. This has been, you know, this is a very modern discovery I would say. People like Euler, Gauss, they never had this kind of language. Even Riemann did not have, even Hilbert did not have this. So, if you try to read their papers, it will be very, very difficult for us. It is entirely different kind of language. Okay, let us take a closer look at these classes. Suppose I take a special case namely the domain is just a single point that I denote by your bracket star, very single point, singleton space. Then what is this space, set of homotopic lines of maps from x to y. To understand this first of all, you must see what are maps from a singleton space. Any function from a singleton space will be automatically continuous. There is only one topology there. So, what are all functions? A singleton space, what is the meaning of function? You have to just mention one point in the space y. As soon as you mention that the function is well defined, that the domain singleton goes to that point. Right? Therefore, this is nothing but set of points in y. Now, what is a homotopy?  So, they are functions from i, of course, continuous functions, maps. So, these maps you must have studied, they are called paths. The starting point is some point that is one function, end point is another function. So, these things are connected by a path. The equivalence classes of such things are nothing but now path components of y. So, this is one of the simplest algebraic topology invariant. This is a homotopy invariant which we have constructed now. So, this was there already in point set topology. The path connected components, a number of path connected components is something different from all other concepts like compactness, separateness, T1-ness, T2-ness, various things. So, this is a quantitative invariant as compared to qualitative invariants. So, all topological invariants in algebraic topology, they will be of this type. They will be quantitative, not qualitative. Quantity just doesn't mean that just the cardinality, there is much more than that. So, you can say it is algebra. There are structures there, of course, like groups, abelian groups, rings and so on. All right? So, we produce in algebraic topology and study various such invariants of topological spaces which are not only sets but more algebraic structures on them, rings, modules and so on. This basic idea of assigning algebraic invariant such as groups and rings instead of numbers goes back to a mean order. Before that, people were just counting the numbers like path connected components, number of, okay. If not, number of arcs needed to cut down a given something. For example, look at r, you remove one point, it has disconnected. Look at the circle. You remove one point, it is still connected. So, you need two points. So, this is the kind of things they are studying, okay. So, M. Minoiter says, don't worry about such things. Best thing is to do, assign group structures to them, okay. So, this was one of the landmark contribution of M. Minoiter. M. Minoiter has done a lot of physics also. So, now it is time for us to reformulate our fundamental topological questions in terms of homotopy, okay. So, first question we are going to change. That was lifting problem. Remember that. So, we are going to make it into homotopy lifting property. So, homotopy lifting problem, then things which have satisfied certain things will become homotopy lifting property. So, fix a map P from E to B. Given a function X, F from X to B, question is, does there exist a map G from X to E such that P composite G is homotopy to F instead of equality. Everything else is the same. Instead of equality here, replace it by homotopy equivalence, okay. So, here we are asking can F be lifted through P up to homotopy. This is the meaning of, this is another way of saying the same problem. Obviously, the original question when you have to equality here, okay, has an affirmative answer, then the change your question, I mean Q1A I am talking about, it is also a affirmative answer because equality implies homotopy equivalence also. But the converse is not correct. Even this is equivalent, if this is solved, there may not be any function G is a set, P composite G is equal to F, okay. But this simple observation that homotopy equivalence, okay, will be assured if there was actually a map, homotopy lifting, if this is not true, namely you cannot lift even the homotopy, then of course you cannot lift up to, you cannot lift the map at all, right. Therefore, a negative question, negative answer would have given you negative answer. So, even this much surveys given by this, this map is of importance to us, okay. But what we want to use is, we will ignore this portion, we will only solve or answer whether something is homotopy, homotopy equivalence can be lifted or not and we are satisfied by that. So, we will pretend as if the problem is over when you have lifted a function up to homotopy. What does that mean? We just make a hypothesis, namely assume if something can be lifted up to homotopy, then it can be lifted, okay. So, this is called homotopy lifting property, this is an axiom, you know, on the function, on the map from P, P from E to B, okay. So, let me state this one correctly. Regarously. So, start with a map P from A to B. So, we are given a homotopy from X cross I to B, okay. And a map G from X to E such that when you take P composite G, that is a map from X to B, right, it is the function f of X0, it means starting point of this homotopy. The starting point of this homotopy, namely suppose this is f of X0 small fx, then that map has been already lifted, that is G, okay. So, this is part of the hypothesis. So, this all this is called homotopy lifting data, this much is given, okay. We say P satisfies the homotopy lifting property if each such data, homotopy lifting data will give rise to an actual homotopy from G from now X cross I to E, see this homotopy was X cross I to B. Now, the lifting, this whole thing is gone up to E such that when you compose with G, compose with P it comes to f and the starting point of this homotopy G by X0 is the given function G from X to E, okay. If this happens for every X and every f and every G, there must be capital G like this, then we say P satisfies homotopy lifting property, understand. So, let me put this one in a figure in a picture which you will just easy to remember, this is a picture. So, here you have X cross 0, G to E and here you have X cross I, okay and this is your inclusion map data, X cross 0 goes to X cross 0 under this inclusion map. f is the homotopy at the starting point it is G, compose with P it is this f, this much is given as soon as you are given here you must have this dotted arrow capital G from X cross I to E when you compose it must be f. So, this triangle is commutative and this triangle is also commutative it is same thing as if you restrict it to X cross 0 it must be horizontal. So, this is the conclusion and this is the data for every such data if you can come here from this part this part that means P is a as homotopy lifting property, okay. So, this is a definition so this will take care of all our botherations about a pointed topology and we can do only on algebra topology this is the whole idea. Such special classes of maps are you may say very rare no that is not true there will be plenty of them and one such class we are going to study very rigorously in this course namely covering projections. The notion of homotopy lifting property is important enough to make it another definition namely such things are called Hurevid fibrations or just fibrations this is because Hurevid was the first one to notice it and study it quite deeply so people call it Hurevid fibrations, okay. What is the meaning of fibrations it is a map from one space to another space which has a homotopy lifting property, okay. So, this is what I am telling you Hurevid you are the first to recognize this one. So, one important case of fibrations will be studied in this course and that is covering projection, all right. So, we will take up the second question a little later namely the next module. So, today this is enough thank you.


Hello, everyone. It's my honor to talk about, to join the Open Source Summit North America and to talk about our session today. So today we will talk about an interesting topic about Kubernetes as a service, the Open Source Cloud on M64. And today we also have Xinliang from Linaro here to talk about this topic. Actually, now Kubernetes is running everywhere on top of the cloud. And now it has been a very famous service on different cloud vendors. But actually for the M64 platform and if you want to run an Open Source Cloud, maybe, yeah. So we have offered these good solutions. So just to have a brief introduction. So I'm Kevin Zhao. I'm from Linaro Data Center and a cloud group. And now I'm a tech leader of the cloud infrastructure. So my, I'm working on something related with Kubernetes and Open Source on the side. So here is my information about the ML Air Center site. And I'm working in Linaro too with Kevin. And we are all working on our server for the data center and cloud and so forth. Yeah, this is my email and my IRC. And you can talk to us. And if you have any stuff or questions, yeah. Thank you. Okay. So let's come to next. So some of you may know that what is Linaro? I just want to give a brief introduction. Linaro is an unbased ecosystem of open source organization. So we are dedicated for offering the open source project for the ARM ecosystem. So not only for the embedded system, but also for the data center and cloud. So here is the introduction about the Linaro LDCG. So we are focused on the server ecosystem. And we have several members now, as you can see that listed on the bottom on the slide. And we are now working on several famous open source software for the ARM servers. So in the architecture, we have UEFI, ACTN, server writing. Besides, we have a big data group working on the big top, the Hadoop, and Spark. And we have a cloud infrastructure group. That is Xenia and I working on. We are focusing on the Kubernetes open stack and site on the ARM ecosystem. So besides, we are searching and approaching for the scalable AI framework and the novel approaches. Besides, we are running a Linaro developed cloud. So that is an enterprise class-unpowered server hosted in the UK and available for the development and CI. So we can offer the VM-based instance and also offer the Kubernetes as a service. So if you have the interest on working with the ARM-based ecosystem, we are welcome to open, we are welcome you to registration. So we are totally based free cloud and benefit to the upstream. So here is several good projects that we are working on. And I have just talked before, so I will generally go through these slides. The next is general information about our Linaro developed cloud. So the developed cloud is used totally on top of the open stack site. So actually for building a private cloud platform, open stack is the only solution now, actually. So on top of open stack, we have offering the overlay service for Kubernetes. And now we are in to enable the IoT agent cloud ecosystem to develop pod test and enable the CI CD for the architecture. So, yeah. So now we are the open stack powered and all our resources are open to the totally open source community. Okay. So today we have this, we have talked about the three parts. As we know that we are talking about the open source cloud on the open source Kubernetes service on 64. So we should focus on the about two part. So first thing is actually we could not avoid the infrastructure as a series. Yeah, actually, in the public cloud side, you can choose some public cloud vendors, famous vendors to get the infrastructure service. But if we want to build up a totally open source platform, so we need to totally do that, a config network do these infrastructures all over all. And so in the first part, we will talk about the infrastructure service. So besides is our, yeah, Mungo is about to introduce how we have done to make the Kubernetes data service works on top open stack on the arm 64 platform. And in the last part, we will talk about the how is a Kubernetes pass level and with the open stack ice level integration with each other Kubernetes, how to leverage the open stack resources to offer the, offer the ability to the end users. So nice to have you hand over to Xinliang. So have you talked about the infrastructure level first? Okay. This helped me to switch to slide seven. Let me come to the first part. Yeah. So the first part is, in this part, we will share how we build our infrastructure service. Next slide. Yeah. This is our infrastructure service solution structure. We use open step to build the infrastructure service. We build and out to chase. It is all open source. On the right hand side, the bottom, on the left hand side, in the bottom, you can see we are all run our service on our, on our vendors arm 64 servers. For the storage, we use a set. And open step, we will use the latest stable, latest stable version. And we will keep, upgrading, once a new stable version can out yet. And on the right hand side, is our monitor tools and our deployed tools. Yes. This is the infrastructure service structure. Okay. Next slide. This is our neighbor solution. Yeah. As you can see, we mainly use three numbers. And on the top, it's turned out a network used by Never Know and to apply Internet access. And in the middle, the control network used by each node for control network flows. This is, meaning the API flow of the system. And the other neighbor is the internal network used by the computer and storage nodes. For the data or application, never flows. Yes. This is the neighbor solution. We are building. So next, this is our deployment solution. We use COLA container deployment method, which is very cool and amazing. And it package each component into the container image, which makes deployment quick and easier. It also supports online upgrade. Yeah. We have released the ARM64 Docker image on this Docker link. All the upstream events, they are all based on the tapping based images. Now we have released OpenSTEP, Lockheed, Stay and Trade version. And for that, we have released L and N version. Yeah. Also, for the, for the, we also deploy, develop a tool made with type of research to management, our bare metal machine. Yeah. This is like a method of the Open2 bare metal management solution. Yeah. This is the deployment solution. Next slide, please. Yeah. This is the monitoring solution. You can see our solution is Glamfana and fast, and then some OpenSTEP supporters. Yeah. We have developed OpenSTEP supporters to collect OpenSTEP metrics for the preliminary fears. Yeah. This is a sort of the, let's allow the OpenSTEP status status. Yeah. This is the monitoring solution. Next. Yeah. Now we have done before we have got the OpenSTEP power certificate, certification. Yeah. We all, we have passed all the OpenSTEP test shield. And we also donate our cloud to the OpenSTEP CI. They are used, now the Astrin are using our cloud to do the Amazon 34 server rotation. Yeah. Yeah. This is our infrastructure service solution. Next slide. This and that's fine. Yeah. The second part, we will talk about the Kubernetes service of our OpenSTEP. Next slide. Yeah. This is the Kubernetes service solution, et cetera. So look at the middle, on the middle. As you can see, we mainly use a mechanism project to build our Kubernetes service, which also utilize heat to create infrastructure resources and also for the low balance service. And on the left hand side, that is OpenSTEP cloud provider for Kubernetes to use the influence resource, such as the volume, low balance service and so on. Yeah. This is the Kubernetes service solution structure. Next. Yeah. This is the mechanism project with how we build our Kubernetes service. For the mechanism, no, as you can see, there is less for API service, so to serve a guy's request and then pass all the requests to the conductor to handle the Kubernetes service creation and also create the required influx resources. And the mechanism mainly use heat template to create the lower layer influx resources. All the Kubernetes service will run on the VN instance on the right hand side. Yeah. This is the mechanism architecture. Yeah. Next, I will introduce how we create our Kubernetes service for to create a Kubernetes service. First, we need to create a template. Yeah. A template will wire command line from the horizon UI. We can specify many parameters. Yeah. So you can see, for example, the Coup version and the locking key and which network solution, something like that. Next, let's slide please. Okay. Once we create a template, then we can create a Kubernetes service. That is a Kubernetes cluster. Yeah. We can also take some parameters from the template such as how many master nodes we want to create and how many working nodes we want to create. Okay. This is a brief introduction of the Kubernetes service. Next, I would like to welcome my colleague Kevin to give more details on how Kubernetes and OpenStat in creation. Yes. Kevin, thank you. Okay. Thank you, Xinliang. Okay. Thank you, Xinliang. Next, I will talk about the detailed creations for these precise. For the production level use case, for the production level use case, it will be essential for the Kubernetes has a multi-master node, right? So, we will need to create multi-load balancers for the different master. Traditionally, if you have a public cloud vendors, they will serve this and offer the load balancer service for you. We have not built our open source cloud on top of OpenStack. So, we need to serve for OpenStack for offering the load balancer service. In the left part in the picture, you can see that it is a general process for creating the load balancer and in the right side, it's a data model for these load balancer services to give a detailed introduction. For example, if we have two need to export, oh, sorry. We can see that for the first is the listener one. If we listen for the port 80 and the listener two will listen for port 443 and each listener will serve for its listener service. For each listener, they have a pool. So, for pool one, it will have an amplifier. So, this amplifier is a virtual machine and running with HAProxy to proc the HDP request for the different backend. And on the bottom of the picture, we can see there are two VMs. So, each VM will have running the application here. So, the VM one and VM two both have running the port has the application running to listen for the port about the 80 and 443. So, this is a data model totally for the Octavia. So, if you have a rotate service it will come from the listener one and will be approximately to the real VM backend. So, that is the general data models for this loader balance server. And it will be used to create the loader balancer for the Kubernetes cluster. We know that the Kubernetes API server usually use the port 6443 right. And EECDI use the 2379 and they need to be exposed to the outside API for the outside API request and also they need to be excised by the Kubernetes. So, we will create the Octavia for the Kubernetes API and also if you create the different use create the listener, create the pool and also add the member to the pool. So, in this picture we can see that this is totally for the loader balancer creation and this is a fundamental step for creating the Kubernetes cluster. Okay, let's come to the next slide. So, after the next slide is totally steps for the maximum creation and the creator loader balancer has been inserted to this totally precise. So, first when we create and when we want to get the Kubernetes cluster we should prepare the resources because it is a tenant-based multi-tenant support for OpenState and other actually the infrastructure as a service. So, it needs to set up the network, the virtual network for this different tenant and configure the security group rules to make it secure. And after that the mechanism will sign the TLS search for the Kubernetes cluster. Just you can treat it like the Kubernetes does for the Kubernetes cluster to send TLS search. And after that if you call the Octavia to create the loader balancer and configure the routes. So, after we go to the loader balancer we can see that now they need to create the master node and the process is very simple. So, it will provision the virtual machine and after the VM provision it will call the cloud init into this cloud init script to run the specified jobs. For example, the significantly job is use the system D to launch the Kubernetes cluster. So, we can see that the Qublate QAPS server and control manager. So, both of them are be launched by system D and managed by system D and also by Postman. So, after that the Kubernetes master has been launched and the other essential components. For example, the network driver container will be launched after the precise. So, after the master creation finished it will pick up the precise for create the worker. So, the worker are also the same precise. Let's use system D to provision these control this essential system containers and also after that it will join to the master to the total cluster. So, the difference, we are using the system D and the Postman to manage the total containers. That is a little different with traditionally using the Kubernetes static port methods. Yeah. Because we are actually using them to hold the federal OS operation system and this operating system traditionally have a very good competition compatible with the system D and Postman. So, it is very easy to use and manage. So, okay. We can see that it is general information about creation, right? So, but we can see that is a little complicated and traditionally you can see that it is much more complicated than creating, right? So, actually, yes, right. But actually for the creating it cannot be the core of the different resources with the cloud provider with the cloud provider side. So, it can just deploy a general cluster. But if you want to interact with the cloud side infrastructure side, yeah. So, you need to actually solve all the different problems. So, if it opens back the magnet will be the easy solution. So, here we come to this overview slide, right? So, generally in this overview slide we can see that we can see that there is a three part of the network and the first is the external network. So, that is for the external access and the public network access, right? And the private network. So, all our cluster hosts are running connected with the private network and in the green line we can see the container network is a traditional container network. So, you can also see there are three ingress. There are three load balancer. So, these are the key points of this cluster. So, you can see there is an API load balancer and a load balancer. So, for the API load balancer it is for the Kubernetes service and the load balancer is for the ETCD. So, they have offered the availability if the worker want to talk with the master they can directly connect to this master one or two or three even though they have connected in the private network. The worker need to connect it to the load balancer first. And we know that the API load balancer has served for the master server and the ETCD has served for the master ETCD right. So, the worker will so this load balancer are first act as the eternal HAA for the workers inside the private network. And also if the users want to expose the application exposed its cluster to the outside. So, the user need to amount of floating IP to this load balancer. And after that our Kubernetes cluster will have the outside access. Yeah, you can use the Kubernetes control to connect it at the remote side. And in the right you can see it is an ingress load balancer. So, that one is served for the applications that running inside the Kubernetes cluster to want to be want to be excised from outside. So, I will talk the detail in the following slides. Okay. So, so actually what is the difference with un64? We can see that we have talked about a lot of the OpenStrike and Kubernetes and even both sides. So, what have we have done to make the totally Kubernetes cluster Kubernetes service happen? Yeah, right. So, first is the project we have done to make OpenStrike and side multi-access port. So, this has included a lot of the problem, a lot of the deployment issue checking and a lot of the packaging and the enablement. So, besides we validate and the totally working precise and enable the totally Kubernetes service framework on top of the OpenStrike on un64 platform. So, after that we will start about a lot of problems about the production level, OpenSource cloud upgrade and maintain. So, besides that we will benefit to the upstream for the OpenStrike and also for side. And after that now we are serving, we are working for the Kubernetes conformist types on this unbased OpenSource cloud. Yeah. Okay. So, here is another maybe the next pending for our Kubernetes as a service. I do know that if we want to create a if we want to create a process for totally Kubernetes as a service, we need to create a lot of load balancers and create the master VMs for HA, right? But that will induce the problem about, firstly the slow creation precise. And the other is yeah, because the mechanism used for the actually script management. So, we need to change a lot of the code to maintain when the OS upgrade or when the Kubernetes upgrade and also even when yeah, and also even when the total framework has been upgraded I mean the department for frameworks. So, it has a lot of dependence. So, we are and also if you want to have an HA cluster, you need to deploy 3BM for master that will be a little cost that will be a high cost for the end users and not very convenient. So, on top of this this this yeah, advantages maybe. Yeah, so we have thinking about using another new approach to manage the Kubernetes. So, we call it proving queued. So, actually it is now a famous method in the private cloud deployment and as you may know, yeah, several companies are also using this method. But in the OpenStack word OpenStack offers infrastructure service that will be the first time. So, I can give a generally in brief introduction. So, for this we have divided into the cluster as the seed cluster and the custom cluster. So, the seed cluster has been launched by the main users and in the network and the custom cluster is offered by actually it is offered by other painters to use who want to deploy their Kubernetes. So, after that we can see that actually we can see that there will be two key parts when it is considered. First is about the control plane containers, control plane components. So, in the master, the seed cluster it has several worker nodes. So, the worker nodes will serve as a host to running as the components. For example the custom surveys the custom ones cluster, right? These clusters server, ETCD and other scheduler and something else will be running as a container inside the worker node in the seed cluster and there will be a load balancer to connect it to the main to connect it to the seed cluster network with the Knet cluster network. We can see that use this method the most it has problem is it will reduce the VM cost for the master for the custom watch. So, it will save a lot of time to provision the totally custom clusters and even for seed cluster you can use the traditional method to create the cluster. But for the custom cluster the control plane container will running at the worker node and also the worker node will running at the new VM. So, this will solve the problem about the high availability and the control plane container will be maintained by the seed cluster from the from the main site but this solution may have a problem. We are not working on to eliminate this effect is this cluster is heavily dependent on the HAP load balancer that we call the Octavia service. So, we need to we will to certify that this cluster will not have the performance issues. Yeah. Okay. Next, we come to the Kubernetes and OpenStack integration. This generally is because we have a cluster and actually we are not running a Kubernetes and have a Kubernetes cluster but it has running on top of the OpenStack site, on top of the infrastructure. So, the Kubernetes may need to several resources from the infrastructure because it may need to the volume it needs the authentication capability from service and also it may need it may need the network capabilities. So, we can see how does the integration with each other. So, yeah. For, yeah, realizing this we have several very important components. Each of them are the Kubernetes controller running inside the Kubernetes clusters. So, I've listed a component here and I will pick up several important components to give the introduction. So, the first is the Cloud Controller Manager. So, we know that the provider has been changed. The code of the provider has been refined due to it has closely relation with the control manager against server and cool it. So, it has been refined and pick up from the cloud provider first version to refine to the new one and it has several controllers. So, each of the controllers are sold for the different resources. We can see in the blue level, in the blue block yeah. It has a cloud controller cloud node controller. So, that is not only realize the node controller functions traditionally but also add several new functions. For example, the podElectionPolicy and if you monitor the infrastructure node, the infrastructure node status and also do the CIDR management. So, also it has a root controller but because that we are not a traditionally level 2 network right. So, we have different virtual private networks. So, the root network, the root controller is also very essential in the large-scale public cloud side and private cloud side. And after that, there is a service controller that serve for the load balancer to do some interesting things I will talk about later. And the last one is purchase the volume level controller. So, if you use the cloud provider to create the volumes. So, in OpenStack side, we use the thing that sets the driver to call the resources from the OpenStack. Okay. Next is a brief introduction and is a general picture about the Octavia. As we talked about before, the Octavia is a load balancer that service and it will take a very significant in due for offer the external network access to this cluster. So, we can just pay attention to the effort. Effort is a VM that running with HL proxy. So, it will serve as offer the load balancer capabilities to the Kubernetes. And yeah. So, we can see that what is the how to realize for if you want to running a application that inside your port to make access to the outside users or outside external access. So, first you have defined we can see that you have defined the port with a t-server right, port 1, port 2 has a t-server and the and there the t-service and port 3, port 4 is a coffee server and there is a coffee service right. So, for the service is a abstract way to expose the application running on a set of ports. Yeah, it is a very famous concept in Kubernetes and we have also an ingress object. So, ingress is a allows the external users and the clients to excise the HTTP service. So, we can see that we have defined the ingress object that the past T with the backend come to the t-service and there is a past coffee with the backend to come to the service with the coffee service right. So, and also they have a different service port yeah. When we done it first we define the service with the node port and after that the the service will have excise will be easy excise from the VM based node port right. And here after that each of them will have a node port exposed. And then we will have a very important component called Octavia ingress controller. So, that one we will be running at the Kubernetes to watch the ingress object change and after it watch the ingress object change it will call the Octavia. It will call Octavia to create the Ampfer to create a listener for this to create actually a load balancer right to excise to connect it to this to this ingress object and after that it will update the HAProxy rules after we after the creation success it will it will mount a floating IP to this load balancer and this load balancer will serve for the different node port and the totally chain floating will be come to from the node port from the load balancer that created by Octavia and come to the target node port and then come to the port. So, in that method we can actually achieve the network solutions and expose the capability for the running applications, quote. Okay, yeah. So here, yeah, thank you very much and here is all our session today. Thank you very much to attending this session and if you have any questions, please yeah any questions are welcomed and if you have any interest on the open source cloud on 64 and we are welcome you to register over the nano-developed cloud. Yeah, thank you. And we have one we have one question. So, the first is our data center move away from Intel to ARM, yeah. So actually we can see that there is a good change and there are more and more cloud vendors are trying to use more infrastructures apart from Intel and also ARM servers now have several good vendors over their product and actually the performance now has been improved during the open source community either from our member companies and also also from the upstreamers from the open source community. So, I think it's a good trend and it has been it will be more and more cloud vendors to over the ARM based servers and ARM based cloud servers, yeah. Yeah, this may the user have a second choice I think.


From Seattle, Washington, it's theCUBE, covering AWS Imagine. Brought to you by Amazon Web Services. Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're in downtown Seattle at the AWS Imagine EDU event. It's their education event and education everything from K through 12 to higher education, community college, retraining after service, it's a really great show. It's the second year, we're happy to be here. We've got somebody who's come all the way from Spain to talk about his very special company. It's Ignasi Nuglez, he is the CEO of click.edu. Correct? Yeah, right. Nice to see you, welcome. Thank you and we are really pleased to see you with you. Great, so tell us kind of what is click.edu? What is kind of your core value? Yeah, it's a platform that makes all the things that the school needs, at least in Spain. So it's a mid-system, also an LMS, also the communication with the families, et cetera. It's a way to manage all the school and also a lot of things that they are related on. Right, and you've been around for a while, so when did the company start? How, it was kind of some basic numbers on how many customers do you have? Cause you operated in a lot of countries, there's a lot of schools. Yes, we have schools working with us already in all of Spain, also in Chile, Colombia and also in UK and also in a little country in Europe that is called Andorra, so we are really happy because we have more than one million of users working with us. One million, great, congratulations. And is it mainly, do you specialize between, say, K through 12 or higher education or are you kind of all over the place? Yes, we are focusing K-12 schools, so one of the important parts are the communication with parents and to follow all the things that the student does. Right, so you guys have a very special thing that you're announcing here at the show is really focusing on Alexa 4K through 12, which nobody else is doing. That's really something unique that you guys, how did you get in that? What did you see in voice communication in Alexa that you couldn't do in the platform before that you really saw the opportunity? Yes, all the people say that the future or the present now is the voice and all we will communicate by voice in the future over internet. You see a lot of young guys doing all the things by voice, not the right texting, et cetera. So we thought that it could be a nice idea that the communication between parents and also for students to the school and in the other way could be by voice. So we imagined how to do it and we did it. It's really new. When did you start it? When did you start that project? This project we began three months ago. Oh, three months ago, so you just got up? Yeah, it's really, really new, the voice idea. Right, right. It was in a show that I have seen. A lot of people were talking about that, but there were at least in Spanish, nothing about, so we thought we couldn't be the first, so we did it. That's great. So before we turn the cameras on, we were talking about some of the issues that you have and one of the ones is integration to all these systems because I have kids, I might have multiple kids in a couple different grades, you have kids, and if I'm looking for access on their homework or their test scores, you just got to integrate with all those different back ends to keep things private. But you're kind of at a good spot because your system is the one that's on the back end, right? Yeah, yeah, that's true. So that works pretty well. And then the other piece you talked about is two-way voice. I don't think a lot of people think in voice communication yet, it's still more of an ask and get a reply, ask and get a reply, but you guys are actually pushing notifications from the school out to the families using voice. How's that working out? What are some of the use cases after that? It's like the parent can ask to Alexa, for example, what's the homework for tomorrow for one of your son or daughter and echo tell you about that. So it's really impressive because in that moment, the system goes to the school system to get that information. It's your system? Yeah, and Alexa translates in voice. So yeah, it's funny. I just think it's funny that I get emails from all my digital assistants telling me, suggesting things that I should ask them because it's really not native yet as an interface to work with these machines. But you mentioned that the young people voice is much more natural. So I wonder if there's been some surprises or some things you didn't expect in terms of people's comfort level with voice as a way to communicate with these systems. Yeah, I think it's the most natural way. Also for us that we are not native, but of course we communicate better by voice and writing or texting. So of course it's the future because it's another way. So the use of that systems goes up because of that. So I think it's the most, the most thing that perhaps is more surprising. Right, and so will you guys supply the Alexa for people's homes or is it something they can tap into their existing Alexa? Yeah, usually the case for using that is in your home or also in your phone. So you can install Alexa in your phone and you can ask them as if you have an Echo. But how do I hook my existing Echo up to the school system? Yes, because sometimes some universities or they put their Echo in the, I don't know, in the university, et cetera. But you can use your Echo that you are using for other things, listen music, you can use the same. You only have to download an app for your phone. Now it's more or less the same, you ask Alexa to install Clicked app or a skill that is how it's called. And then you have it. So what's next? What's on the roadmap, on the voice specifically? Where do you see this kind of evolving over the next little while? Yes, our next goal in that part is that they can use the teachers in the school, the voice systems also. So for doing what they do every day in more writing or whatever, we can do it by voice. For example, an interview with the parents at transcript or for example, to say that somebody hasn't come to the school or to tell to the transportation that something is happening. This kind of things is what we are imagining. It's in our next things that we will do with voice. So it'll be Alexa in the classroom, hoping that the classroom not just at home. What about privacy? I would imagine, it was funny, in the early days of cloud, security was not good. It was a showstop where people were concerned. 10 years later, now security is a strength of cloud. It's probably more secure than most people's data centers or disgruntled employees. I would imagine privacy and security is probably pretty top of mind in the school districts as well. There's a lot of personal information. Are they comfortable? Do they kind of get the security of cloud and cloud infrastructure? Or is that still a sticking point? You know that in Europe, there are really strict law about protection of data. So we are really concerned about that. So we are talking with the schools what kind of systems they will be comfortable because we want to use it. So we will have to find the clue to do that. But it's really important. I think all over the world, but in the States or in Europe we are really concerned about that. So we'll see how to find it, but we can create a private skill. Right. Yes, because there are a version of Alexa that is for business. So you can create your own private things and you don't have to be sure that somebody is listening to you. Right. So last question here at the conference. Did you come last year? No. So what are you, just your impressions of the conference? How is it nice to be with a bunch of like-minded, kind of forward-thinking educators? Because education doesn't always get the best reputation for being kind of forward-looking. But here you're surrounded. So I just wonder if you could share some of your thoughts of the event so far. Yeah, I think these kind of events give you more motivation and you increase your way to see that there are a lot of people that is pushing to innovate and do the things different. So really, really interesting to go to some machine learning exposition about California, what they are doing, et cetera. So I'm really interested. Good, good. All right. Well, Nossi, thanks for taking a few minutes and congratulations on that project. That's really crazy. Thank you for your interest. All right. You say, Nossi, I'm Jeff. You're watching theCUBE. We're at AWS Imagine in downtown Seattle. Thanks for watching. We'll see you next time.