output,input,instruction AION: “SWITCH ON AI”,, "Industry Challenges & Solution using AION Challenges HCL AION Advantage Dev elopment of ML Models takes long time & need specialized skill setEmpower people in organization whether Technical (Working in code) or Business (Low code/No code) to create ML Models Data needed for building ML Models is not centralized and is available in varied data formats & platformsHooks to integrate with varied enterprise data sources Handle data cleansing, data quality issues, data outlier issues Handle multiple data types and unstructured data Data scientists do not have deep domain understanding & Domain experts do not understand Machine LearningAION helps citizen data scientists develop ML Models. Reduces Repetitive work needed by data scientists in developing models Saves precious data scientist e fo rt by automating low end work ML Model & Data might drift with time, resulting in incorrect insights & predictionsModel monitoring support and drift analysis for input/output data & Model predictions ML Models are black box & give no explanation on predictionsAION provides detailed explanations on reasons for prediction Code Generated by AI Lifecycle Mgmt. Platform is not reusable across PlatformsMLaC feature generates Platform independent Python code & containers that can be consumed outside AION as wellInput AIONOverview Organizations today are targeting to promote democratization of Machine learning & AI, this will unlock immense potential that is still untapped as most of the domain experts are not capable of building ML models. AION will enable domain experts (Also known as Citizen Data Scientists) build ML models to derive useful insight from raw data & help resolve business problems. AION is an AI lifecycle management platform for applying machine learning to real-world problems. AION encompasses the",, "complete pipeline from raw dataset ingestion to deployable machine learning model with low-code/no -code approach. AION Includes the following sub-processes: •Data exploration, insights generation and transformation (Data Engineering) •Machine learning, deep learning and artificial intelligence training (Algorithms & Models) •Prediction interpretation/explanation, model testing and uncertainty quantification (XAI / ML Test / UQ) •Model deployment, model observation and model operations (MLOps) Output Model MLaC x4 x59 x54 y n y n Explanations / Uncertainty",, "AION Business Benefits Productivity Improvement of Data Scientists in ML Model development timeML models helping in Operational effciencyWider analytics adaptability across organization helping in providing more insights INGESTOR Data Ingestion Hooks to consume data from disparate sourcesAION Components EXPLORER Exploratory Data Analysis Visual exploratory data analysis to derive descriptive insightsTRANSFORMER Data Processing Data cleanup & preparation to improve data qualitySELECTOR Feature Selection Identification of relevant features based on correlation & importance LEARNER Model Training Hyper Parameter Tuning Identify best algorithm & parameters for highest scorePUBLISHER Model Publishing Flexible ML Model deployment options for varied environmentsPREDICTOR Inference Service ML Model Serving & inference services EXPLAINER Explainable AI Explanation & Uncertainty quantification of the predictionTESTER Model Testing Flexible ML Model deployment options for varied environmentsCONVERTOR Model Conversion for Edge Device Convert ML Models to edge & hyper - scaler platformsOBSERVER Model Monitoring Identification of relevant features based on correlation & importance CODER Machine Learning as Code Automatic generation of Python code for ML pipeline components PIPELINE VISUALIZER Exploratory Data Analysis Performance Visualization Visualize all stages of the pipeline AION Visualizer",, "AION Differentiators Integrate with any digital platform and provide analytics as a service ML as a code (MLaC) available for expert data scientists & easier maintenanceModel & Prediction ExplainabilitySingle platform providing services to convert raw data into insights & value Easy integration with diferent data sources and hyperscalers",, "www.hcltech.com HCL Technologies (HCL) empowers global enterprises with technology for the next decade today. HCL’s Mode 1-2-3 strategy, through its deep -domain industry expertise, customer -centricity and entrepreneurial culture of ideapreneurship enables businesses to transform into next -gen enterprises. HCL s its services and products through three lines of business - IT and Business Services (ITBS), Engineering and R&D Services (ERS), and Products & Platforms (P&P). ITBS enables global enterprises to transform their businesses through o in areas of Applications, Infrastructure, Digital Process solutions in all aspects of product development and platform engineering while under P&P. HCL provides modernized software products to global clients for their technology and industry specific requirements. Through its cutting -edge co-innovation labs, global delivery capabilities, and broad global network, HCL delivers holistic services in various industry verticals, categorized under Financial Services, Manufacturing, Technology & Services, Telecom & Media, Retail & CPG, Life Sciences, and Healthcare and Public Services. As a leading global technology company, HCL takes pride in its diversity, social responsibility, sustainability, and education initiatives. As of 12 months ending on December 31, 2021, HCL has a consolidated revenue of US $ 11.18 billion and its 197,777 ideapreneurs operate out of 52 countries. For more information, visit www.hcltech.com Network Quality of Service (QoS) Classification Complaint Identification for Medical DevicesA leading telecom service provider wanted to introduce QoS analytics capabilities in a device management platform that they were using from HCL using HCL AION, a solution to provide Descriptive and Predictive Analytics insights for the CPE devices was developed. The Descriptive Analytics included",, "dashboards for QoS Analysis, Degraded QoS and Statistical insights. Predictive Analytics included quality -based traffc patterns, forecasts of error rates, noise and signal strengths. Customer Order ForecastingA leading telecom service provider wanted to automate order volume and trend monitoring (which was being monitored manually). No telemetry was defined for order volume variation. AION was introduced for AI/ML based forecasting to help in defining telemetry for order volume variation. A time series forecasting model was developed that was trained automatically every 24 hours (or as per configured interval) to forecast volumes for the next period (1 hour or configured interval).The problem was to identify cases of medical device complaints given a set of device services report records using unsupervised and supervised techniques. The complaint data was passed through AION pipeline where data profiling and feature selection were performed. Constant features were removed, and low variance features were handled. Features with empty rows were imputed appropriately. Supervised classification and unsupervised clustering was performed as two diferent approaches to categorize complaints.Proof Points",, "Copyright © 2021 HCL Technologies Limited | www.hcltech.comAION –Switch ON AI Roadmap Navin Saini",, "FY24AION v4.0 Edge ML & Federated ML ✓Distributed Learning for Faster Training of ML Models ✓Federated Learning to address issues like data privacy, data security & access rights ✓Building ML Models for devices with resource constraints using TinyML ✓Security for Edge Models ✓CI/CD Pipeline leversFY23AION v3.0 MLOps & Hyperscaler Integration Enabling Model deployments in Production ✓Feature Store ✓Integration with CI/CD pipeline ✓Data Quality check ✓Efficient & light weight Containerization ✓Incremental & Reinforcement Learning ✓Platform Governance (Roles)FY22AION v2.0 ML Test, Explainable AI & MLaC Covering of features Beyond AutoML ✓Model Monitoring, ✓Explainable AI, ✓Model Confidence score (Uncertainty Quantification), ✓Model Benchmarking ✓ML as a Code (MLaC)Product Roadmap Of AION AutoML & Exploratory Data Analytics FY21 Implement Core AutoML features covering all the data analytics pipeline stages of any AutoML solution like Model Building, selection, Hyperparameter tuning. Data Pre -Processing, Model mgmt.AION v1.0",, "3|Copyright © 2021 HCL Technologies Limited | www.hcltech.comPRODUCT ROADMAP OF AION V 1.0 (RELEASED)V 1.2 (RELEASED)V 1.5 (RELEASED)V 1.7 (RELEASED)V 2.0 (RELEASED) Dec ‘20 June ‘21 Sept ‘21 Dec ’21 Mar ‘22Core AutoML (Structured Data) Implemented Core AutoML features covering all the data analytics pipeline stages of any AutoML solutionAutoML+ (Unstructured Data) Enrichment of core features by adding capabilities related to unstructured data and increase the breadth of offeringExtended Core (Production Focus) Addition of features to help in productionization of Analytics models such as MLTest, MLOps & Hyperscaler to differentiate from competitionAutoML++ (Feature Hardening) Increasing depth of our offering by hardening the features . Introducing the functionality related to better training & learning experienceModular Core Comprehensive release with advanced features like Machine Learning as a Code, Integration with GCP and Optimized Ensemble algorithms Core AutoML PipelineImage Simulation & Labeling Object annotation & detection Edge Models (ONNX) Remote Training of modelsML Testing ML Ops (MLFlow integration) Hyperscaler Integration Containerization (Docker) Drift Analysis Edge Models (TensorRT)KubeFlow Integration TinyML for lightweight & low power edge devices Optimization of Algorithm & Pre-Processing stages Adverserial & Perturbation TestingMLaC – ML as a Code (Code, Container, Config) Document Similarity New Ensemble algorithm support ( CATBoost & Light GBM) Kubeflow Integration Optimized Edge Conversion Secure REST API",, "4|Copyright © 2021 HCL Technologies Limited | www.hcltech.comMARKET COMPETITION Tool / Framework / Vendor Classification Regression Time series Clustering Recommender System Survival Analysis Anomaly Detection Constraint Optimization Bayesian Optimization Genetic Programming Ensemble Construction Tree Parzen Estimator Neural Architectural search Grid Search Random Search Data Pre - processing Feature Selection Similarity Detection Drift Handling Cross Validation Data Balancing Tibco Software✓✓✓✓✓✓✓✓✓ ✓ ✓✓✓ ✓ RapidMiner ✓✓✓✓✓✓✓ ✓ ✓ ✓✓✓✓✓ ✓✓ IBM ✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓ Alteryx ✓✓✓✓✓✓✓ ✓ ✓ ✓✓✓✓ ✓ Databricks ✓✓✓✓✓✓✓ ✓ ✓✓ ✓✓✓✓ ✓ Deep Cognition AI✓✓✓ ✓ ✓✓✓ ✓ Dataiku ✓✓✓✓ ✓✓✓✓✓✓✓ Data Robot ✓✓✓✓ ✓✓ ✓✓✓✓✓ H2O ✓✓✓✓✓✓✓ ✓ ✓✓✓ ✓✓ AI.ON (HCL ERS)✓✓✓✓✓✓✓ ✓✓✓ ✓✓✓✓✓✓✓✓✓ML Algorithm Type Hyper Parameter Tuning & Optimization Miscellaneous",, "$9.9 BILLION | 150,000+ IDEAPRENEURS | 50 COUNTRIES",, 6|Copyright © 2021 HCL Technologies Limited | www.hcltech.comINDUSTRY CHALLENGES & SOLUTION USING AION,, "7|Copyright © 2021 HCL Technologies Limited | www.hcltech.comSOLUTION PROVIDED BY AION Data pre -processing •Handle data cleansing, data quality issues, data outlier issues •Handle multiple data types and unstructured data •Hooks for integration with disparate data sources Feature Selection •Identifying features from the data •Feature Correlation and reduction of features if needed Model Training • Ability to interpret model function and try out multiple models • Ability to optimize model parameters and fit the model with required scoring criteria • Handle overfitting of data and handle varied class of data Model Testing and Explainable AI • Provide model testing capabilities to baseline models, assess performance and confidence • Generate multi -dimensional KPIs and explanations of predictions ML Operations •Provide all common deployment options for ease of integration with third party applications •Support for open standards of edge deployment for hardware agnostic deployment Monitoring •Detect and notify data drift •Ability to configure and detect prediction drift",, "AION Product datasheet AI lifecycle management platform to assist data scientists & business users create, experiment, productize & Improve ML & LLM models to derive insights using low -code/no -code approach & enabling citizen data scientists(CDS) in an organization. Key Highlights •One platform from raw data to insights •One platform for all users ranging from domain engineers (No AI or code knowledge) to expert data scientists •Build once and deploy anywhere (including edge) •Easy integration of AION with customer existing digital platforms •Open for Research based collaboration in development of ML solution •AI as code •Generative AI Capabilities for Finetuning & Embeddings Generation using OpenAi & LLaMA2 Benefits •Continuous automation •Productivity Improvement •Improves operational efficiency and throughput •Helps in deskillingSalient Features •Intelligence for all covering entire ML Pipeline - AION is for everyone, from AI builders (Expert Data Scientists) to AI consumers (Domain users) •Generative AI Capabilities - Finetuning(Partial & Full) & Embeddings generation using online & Offline LLM Models like OpenAI & LLaMA2 to solve problems like QnA , Text summarization & Data Labeling. •Ecosystem of algorithms - AION supports all state -of-the -art algorithms including ensemble. It explores multiple algorithms with ideal hyperparameters resulting in an accurate system. •Hyperscaler Integration - AION can integrate with HyperScalers like AWS, Azure & GCP providing security, reliability & scalability to the ML model. •MLaC & MLOps - Automatic generation of Python code(& containers) for all ML Pipeline stages. Container orchestration using Kubeflow. •Varied deployment option - As Python Package, Docker & Service Endpoint, Model on Edge devices (ONNX & TFLite format), Model on Hyperscalers – Amazon Sagemaker •Benchmarking of AI & LLM Models - AION supports benchmarking of LLM & ML Models generated within or outside of AION •Model Observability - Input (Data Drift) &",, "•Model Observability - Input (Data Drift) & output(Prediction Drift) drift analysis for timely alerts •Trusted AI - Data Bias, Fairness, Transparency, Robustness & Explainability",, "Technical Requirements Third -Party Tools Component Requirement Processor 64 bit processor; Intel corei3, A100 GPU(for fine tuning) RAM 16GB RAM, 40GB (For Fine tuning) Operating SystemAny 64 bit Windows/ Linux HDD Free Space100GB min (preferred 500 GB) Java JDK 8 Other software Pre-requisitesGUI - Google ChromeHyperscaler Integration Data Ingestion Integration MLOPs Integration Capability Integration AION Solution Components Engines EXPLAINER – Explainable AI Explanation & Uncertainty quantification of the prediction TESTER – Model Testing Benchmarking & Testing of ML Models CONVERTOR – Model Conversion for Edge Device Convert ML Models to edge & hyper- scaler platforms CODER – Machine Learning as Code Automatic generation of Python code for ML pipeline components Benchmarking Benchmarking of LLM Models for safeguarding against performance deterioration PUBLISHER – Model Publishing Flexible ML Model deployment options for varied environmentsPREDICTOR – Inference Service ML Model Serving & inference services OBSERVER – Model Monitoring Model Monitoring for input & output drift of data or predictions INGESTOR & EXPLORER – Data Ingestion & Analysis Hooks to consume data from disparate sources & visually explore & analyze the data for descriptive insightsTRANSFORMER & SELECTOR – Data Processing & Feature Selection Data quality improvement & identification of important features based on correlationLEARNER – Model Training Hyper Parameter Tuning Identify best algorithm & parameters for highest scoreLLM Fine -tuning Partial (PEFT) & Full finetuning with configurable parameters for offline LLM Models on AWS & GCP Run + Design Time EnginesDesign Time Engines",, "HCLTech is a global technology company, home to 222,900+ people across 60 countries, delivering industry -leading capabilities centered around digital, engineering and cloud, powered by a broad portfolio of technology services and products. We work with clients across all major verticals, providing industry solutions for Financial Services, Manufacturing, Life Sciences and Healthcare, Technology and Services, Telecom and Media, Retail and CPG, and Public Services. Consolidated revenues as of 12 months ending March 2023 totaled $12.6 billion. To learn how we can supercharge progress for you, visit hcltech.com.",, "hcltech.com CUSTOMERS CHALLENGES Development of ML & Private LLM Models takes long time & need specialized skill set Data needed for building ML Models is not centralized and is available in varied data formats & platforms Data scientists do not have deep domain understanding & Domain experts do not understand Machine Learning Unable to Identify input & output drift for data for models in production HCL’s AION KEY OFFERINGS AION makes it easier for Citizen data scientists to develop ML & LLM models. Provide various mechanisms & connectors to consume data from varied sources Generative AI is offered by AION as a capability which is not part of most of the AutoML solutions in market like OpenAI & LLaMA2 Automatic Identification of input & output drift for data & ML Models BUSINESS BENEFITS Productivity Improvement of Data Scientists in ML Model development time ML models helping in Operational efficiency Wider analytics knowledge across organization helping in providing more insightsDIFFERENTIATORS Integrate with any digital platform and provide analytics as a service Single platform providing services to convert raw data into insights & value Build once deploy anywhere Easy integration with different data sources and hyperscalers ML as code(MLaC) available for expert data scientists & easier maintenance Generative AI (LLaMA2 & OpenAI) Positioning statement HCL has taken a lead in the field of AI/ML by coming up with its own AI lifecycle management platform i.e. AION. AION can assist expert data scientists or domain experts without AI or code knowledge to build ML models & derived useful insights from raw data.Expertise on AI/ML HCL continues to keep pace with the market dynamics through continued investments for technology and service capability development. HCL has a strong focus on driving large-scale AI/ML transformation, specifically for the large enterprise COMPETITIVE POSITIONING AION OFFERING World Class Delivery Organization",, "World Class Delivery Organization HCL has world class delivery infrastructure and processes backed by strong management and governance teams. AUDIENCE CDO, CTO, CIO VP & Director Digital, Products, AppsELEVATOR PITCH: AION is an AI lifecycle management platform to assist data scientists and business users create, experiment, productize and i mprove ML models using classic & Generative AI to derive insights using low code/no- code approach and enabling “citizen data scientists” in an organization.",, "hcltech.com AEROAREAS WHERE AION CAN PROVIDE SOLUTION OBJECTION HANDLING QUESTIONS 1.There are many AI/ML solutions in the market. Why should we choose AION over others? AION supports all the major features & capabilities supported by major players in market. Some of the differentiators that we would like to highlight are: Easy Integration with existing customer digital platforms Customization support as per customer needs Comprehensive deployment options (incl. edge devices) Feature set covering entire AI/ML pipeline & not just model building. AI available as code for expert data scientists & easier maintenance Includes Generative AI (Online-OpenAi & Offline-LLaMA 2) 2.Which specific domain or vertical solutions does AION serve? AION is domain agnostic as it is applicable to all the domains. It can be used across various industries like Industrial, Aero, semi -conductors, Medical, Auto, consumer Electronics etc. It can help in predicting failure of equipment across various domains such as Industrial, Aero, medical etc. It can also help in enhancing customer experience with analytics in different domains such as Medical, Auto, Consumer Electronics etc . In this way, AION serves various domains. 3.How does HCL compare to other well -known Analytics solution provider? HCL applies proven expertise and pre-built assets to provide businesses with unmatched analytics and AI expertise. Pre-built assets include advanced laboratories for IoT, integrated Computer Vision + NLP, and Analytics + AI. Pre-built assets accelerate solutions which includes automated AI processing, tools and frameworks for AI/ML development, and domain specific solutions. HCL leverages its strategic partnerships with leading AI technologies and cloud paradigms to bring strategic value to clients. HCL’s Analytics and AI services help clients innovate their products and processes, and differentiate themselves from competitorsFailure prediction of equipment Operation optimization to reduce cost",, "Operation optimization to reduce cost Robotics: Image Classification Network Service Assurance Sales and Marketing Analytics Customer Experience Enhancements Self-organizing and self -healing network Clinical Decision Support System Proactive healthcare Connected product usage & quality analysis Yield control and asset optimization Quality early warning systems Field and warranty management Image Classification for driver assistance systems Predictive maintenance and vehicle health monitoring Insurance analytics Sales and marketing analytics Customer experience enhancement Optimize field support operations Predictive Maintenance Asset health monitoring dashboard Predictive maintenance alerts Last mile optimization of spare parts Sales and Marketing Analytics Customer Intelligence Engineering and Support operations optimization Product/Service Performance AnalysisINDUSTRIAL MEDICAL AUTO CONSUMER ELECTRONICSSEMI- CONDUCTORSNETWORK SYSTEMS ISV/ONLINE",, "hcltech.com HCLTech is a global technology company, home to 225,900+ people across 60 countries, delivering industry -leading capabilities centered around Digital, Engineering and Cloud powered by a broad portfolio of technology services and software. The company generated consolidated revenues of $12.8 billion over the 12 months ended March 2023. To learn how we can supercharge progress for you, visit hcltech.com. 1.Helps to identify solutions/capabilities which can be positioned in AI/ML & Generative AI spectrum 2.Understand opportunities to help the client with specific AI/ML areas 1.Identify how AI/ML & Generative AI( OpenAi & LLaMA2) investments can enhance revenue and services 1.Helps to align Classic & Generative AI to customer’s roadmap 2.Helps to identify investment or partnership opportunitiesSALES PROBING QUESTIONS TO CLIENTS DirectorWhich are your major AI/ML Transformation Pain points? CONTACT US : Navin Saini - navins@hcl.comHow can AI/ML Technologies bring new value to your customers? What is your AI roadmap?CDO, CTO, VP & General Managers",, "Copyright © 2022 HCL Technologies Limited | www.hcltech.comAI Lifecycle Management Platform Competitive AnalysisSwitch on AI",, "2 Copyright © 2022 HCL Technologies Limited | www.hcltech.com Competitor Analysis FeaturesAzure AutoMLAmazon Gluon Dataiku Google AutoML DataRobot H2O Data Pre -processing     Text Analytics       Feature Selection       Algorithms Supported    Neural Architecture Search        Model Testing        Explainable AI        Uncertainty Quantification        Model Conversion        Flexible Deployment     Model Monitoring       Hyper -scalar Integration         Not Applicable  Basic  Supported  Good  Extensive As per June 22",, "• • • • Insights & Impact Data Sources Data Ingestion Pre- ProcessingBuild ML Models Deploy ModelsPredictions Model MonitoringExperiment & Optimize Data & Feature EngineeringMachine Learning (Experimentation & Optimization)MLOps (Production & Operations) ML Model MLaC Explanations Python Package Edge REST APIBusiness UsersVisualization & Feature EngineeringDocker Drift Analysis Docker Expert Data Scientist Deployment Options Consumers",, "Problem Types14 Supported Algorithms56 EDA Features09 Large Language Models04 AION can handle more than 14 types of problem types including Classification, Regression, Topic Modelling & Survival analysis56+ algorithms supported including supervised & unsupervised learning. Ensemble & Deep LearningExploratory Data Analysis capabilities like statistical analysis, data distribution, correlation analysis, feature importance, data deep dive & bias Identification Fine Tuning of 10 variants of pre-trained models are supported on AWS and GCP configurations Feature Engineering Recipes07 Model Conversion Formats09 MLOps Integration08 Advanced Learning Techniques08 Feature selection & feature reduction techniquesVarious Edge formats (ONNX, TFLite), Hyperscalers & Python packagesSupports experimentation, code generation, GitHub integration, MLFlow tracking, registration, Kubernetes, model monitoringIncludes Federated Learning, Distributed Learning, Online Learning and Homomorphic Encryption",, "Fine Tuning & Benchmarking Foundation LLM User Data Fine Tuning with Hyperparameter Data Scientist Private LLM Fine-Tuned Large Language Model on User Data LLaMA2 -7B & LLaMA2 -13B Embeddings Generation Documents (PDF, Doc, Text) (Offline & Online LLM) Database",, "• • • • •",, "Customer Digital Platform Core Functionalities Feature SetPrediction API Response PROPOSITION 1 Provide AION as a part of digital platform offering . In this case, AION is being integrated with the existing digital platform . It is embedded as a component of the digital platform .PROPOSITION 2 Provide AION as a standalone platform In this case, AION is outside the existing digital platform . It can be called from the digital platform using APIs or web services . It can be used as Analytics as a service . AION in integration with digital platform AION as a standalone platformCustomer Digital Platform Core FunctionalitiesFeature SetAION Developed ML Models",, "MLaC generates code automatically based on ML Operations performed during various ML Lifecycle . Using MLaC, expert data scientists can have better control on experimentation, optimization & deployment of ML Models . MLaC has four unique components . Generate Container Automatically Build container with github actions for all the components . Compatible with Kubernetes & Kubeflow .Generate Code Automatically Generate Python code for each ML Pipeline like Data Engineering, Feature Engineering & Model Training etc.Model Monitoring Monitor the pipeline for performance degradation & replace alternate model based on accuracy Container Orchestration Stitch Pipeline containers in a ML pipeline to derive a meaningful outcome",, "This pipeline will enable Model developers & MLOps engineers in ML model deployment to production & monitoring . Automatic drift identification & triggering of necessary actions for keep pipeline relevant . Model MonitoringData IngestionData TransformerFeature EngineeringModel TrainingModel Serving Monitors model as per schedule of pipeline . If Drift is observed in new data, then entire pipeline will be triggered again . Ingestions of data as specified by AION at the time of model creation Transform the data as per the business needs of the ML ModelSuggestion of features based on statistical, or ML model Model Training, each algorithm will have a separate container . Champion model will be selected based on performance for servingMaintaine Registry of ML Models on MLFlow Model will be served by exposing an end point that can be consumed by any applicationModel Registry Kubeflow Pipeline",, "Hyper Parameter Tuning Algorithm based hyper parameters Grid Search Random Search Bayesian Genetic AlgorithmSampling SMOTE Over Sampling Tomelinks Under SamplingScoring Criteria Classification oAccuracy oPrecision oRecall oF1 score oROC AUC Regression oMAE (Mean Absolute Error) oMSE (Mean Squared Error) oRMSE (Root Mean Square E) oR2 (Statistical Measure ) Clustering oSilhouette Coefficient oCalinski -Harabasz Index oDavies -Bouldin Index Scoring Criteria Forecasting oRMSE oMAE Recommender oRMSE oMAE Association oSupport oConfidence oLiftOptional Configurations Search Optimization parameters: oK fold CV split percentage oTrain / Test percentage oIterations Number of clusters: auto or configurable Making false failures zero (FP, FN = 0) Top N recommendations",, "Traditional Approach New & Better Approach (Buy & Customize) •Buy source code for upfront value, cost optimization and reduced time to market •Customize code / platform using own resources or use SI services •Regular code updates & feature enhancements can be negotiated as part of deal 02Complete Ownership Organization has complete ownership of the platform & can define the roadmap as per organization priorities. Development of features can be taken care by customer or HCL resources. 03Easier Modifications As the changes in customer source code branch is not shared with anybody, customer can create their own prioritization on features & release cycle. 01Tailor Made Platform or solution is tailor made as per organization needs & need not be generic like one size fits all approach. 04Offers Scalability Scalability needs are as per organization requirements & can be aligned to hyperscaller or infrastructure choice of customer",, "Sweden based multinational clothing customer The problem was to identify cases of medical device complaints given a set of device services report records using unsupervised and supervised techniques. The complaint data was passed through AION pipeline where data profiling and feature selection were performed. Constant features were removed, and low variance features were handled. Features with empty rows were imputed appropriately. Supervised classification and unsupervised clustering was performed as two different approaches to categorize complaints. Major Japanese industrial customer Apart from basic AutoML capabilities, custome r appreciated the features like Uncertainty quantification (provides a confidence level of the model in predictions) & explainability(Provides the explanation behind the prediction). Model explainability is part of responsible AI & hence part of compliance in certain geographies.Dutch based multinational conglomerate customer Customer appreciated AION’s collaborative solution related to all the data science related work across organization. Centralised MLOps capability was area of keen interest & resulted in identification of areas of engagement with customer. MLac was another powerful feature that helped customer achieve the total control of ML models in production. US Based Chip Manufacturer Impressive AutoML based capability to save significant effort in ML Models using No -code/Low -code approach. AION is also able to automate ( & hence save significant repetitive & low-end work) done by expert data scientists. Created models for automatic categorization of defects related to infrastructure (False Failures) using log files. 03 02 0401",, "# AWS Models LoRA QLoRA 1 LLaMA-2 7B ✓ ✓ 2 LLaMA-2 7B Chat ✓ ✓ 3 Code LLaMA-2 7B ✓ ✓ 4 LLaMA-2 13B - ✓ 5 LLaMA-2 13B Chat - ✓ 6 Code LLaMA-2 13B - ✓Technique # GCP Models LoRA QLoRA Full Fine Tuning 1 LLaMA-2 7B ✓ ✓ ✓ 2 LLaMA-2 7B Chat ✓ ✓ ✓ 3 Code LLaMA-2 7B ✓ ✓ ✓ 4 Falcon 7B ✓ ✓ ✓ 5 LLaMA-2 13B ✓ ✓ ✓ 6 LLaMA-2 13B Chat ✓ ✓ ✓ 7 Code LLaMA-2 13B ✓ ✓ ✓ 8 Code LLaMA 34B - ✓ - 9 LLaMA-2 70B - ✓ - 10 Falcon 40B - ✓ -Technique",, "D R A F T V E R S I ON, H C L C O N FI D E NT I A L A N D I N T E R NA L P U R P OS E O N LY1Device Complaint Classification for a Medical OEM client BenefitsKey Differentiators Problem Statement Solution Approach•Automated machine learning pipeline that does data profiling, feature selection and model generation •Automated visualization of descriptive and predictive results •Automated deployment models made available either as a service or as a package Complaints data had numeric, categorical and text features like Hospital, Model, Serial No., Test Date, Instrument Inspection, Reason, Technician Note, Manual Exception Reasons, Manual Exception Comment Feature Selection: •Removed constant and low variance features •Features with empty rows imputed appropriately Performed supervised classification and unsupervised clustering as two different approaches to categorize complaintsIdentify cases of medical device complaints given a set of device service report records using unsupervised and supervised techniques Accuracy Improvements8%30%70% 40% Ease of DeploymentEase of IntegrationModel GenerationEfficiency Improvements Results Approach 1: Supervised Classification •Achieved accuracy ~100% in detecting complaints vs non -complaints Approach 2: Unsupervised Clustering •Achieved ~87% accuracy in clustering complaints vs non -complaints",, "D R A F T V E R S I ON, H C L C O N FI D E NT I A L A N D I N T E R NA L P U R P OS E O N LY2AI/ML based Order Forecasting for a Telecom Service Provider client Aggregate at hourly intervals Approach •Use AI/ML based forecasting to help in defining telemetry for order volume variation •Define AI/ML Model that will be trained automatically every 24 hours (or as per configured interval) •Forecast volumes for next period (1 hour or configured interval)Order Telemetry data Results •Time Series Forecasting using 4 months of historical data •Achieved next 24 hours order forecasting with 90% accuracy •Provided configurable option to forecasting for next x hours or next y daysProblem Statement •Order volume trend monitoring is manual •No telemetry defined for order volume variation Order Forecasted ResultsModelTrainTest Train and generate time series forecasting model",, "D R A F T V E R S I ON, H C L C O N FI D E NT I A L A N D I N T E R NA L P U R P OS E O N LY3 Detecting pump faults based on vibration analysis for an Industrial OEM client 1. Data Collection •Data for 84 secs were captured for each fault condition •Data was captured in 150+ files, each file containing 10000 raw data values 2. Nature of Data •Types of Fault data collected: •Inner Ring Race Fault •Outer Ring Race Fault •Seal Fault •Cavitation Fault •Good condition3. Solution Development •Following features were extracted from the vibration data from each file – Mean, Standard Deviation, Variance, Kurtosis, Skewness, Crest Factor, Minimum, Maximum and Sum •Normalization was done on features •Training and Test data were split in the 80%:20% ratio 4. Benefits •Model available for easy deployment: as a package or as a service •Prediction API available to categorize new data points~100MB of data collected 97% accuracy of fault detection achieved 5 categories of faults capturedFlexible deployable model Seal FaultOuter ring Race Fault Inner ring Race Fault",, "Copyright © 202 3 HCL Technologies Ltd. | Confidential 1 Key Features Flow Diagram Wiki/KM Error/Bug Database DB/CRMData Extraction NLP/NLUAssociation and recommendation Generative AI Resource planning Demand forecasting Problem resolutionTicket management Knowledge managementAPI Custom Library Plugin/extensions Dashboard/Web portal Classification Cluster AnalysisData Cleaning Data Mapping Feature Extraction Data Transformation Data Integration Text Mining Scoring Forecasting AI Chatbot Similar Ticket identification Smart Ticket Assignment Dynamic Visualization Bug Prioritization Ticket Volume Prediction Ticket Clustering Ticket classification Log Analysis Generative AI based use cases Productivity Customer Satisfaction Response time Collect relevant Historical data Mine critical information By Using AI/MLOptimize task, Improve process and productivity IAFS framework built on top of iTS (Intelligent Tech Support) that leverage AI/ML and Gen AI to enhance field support operations . It streamlines ticket resolution, reduce manual efforts, improve product support quality to boost field support team efficiency and productivity .",, "Q1 FY25ISE v1.2 Program Management Use Cases, Upstream and Downstream Connectors/Plugins Q4 FY24ISE v1.0 Dev and Test Use Cases, Upstream and Downstream Connectors/Plugins •Additional Development Use Cases using Offline (Meta Llama 2) and Online (Azure Open AI) LLMs: •Design Activities - High Level, Low Level and Database Design •Augmented Code Commits, Merge Conflict Resolution •Static Code Analysis •Additional Testing Use Cases using Offline and Online LLMs : •Test Case Standardization, Test Case and Script Maintenance •Test Data Generation •Augmented Bug Logging •Upstream Connector Integrations: SVN, BugZilla •Downstream Application Plugins: •IDE: Eclipse•Program Management Use Cases using Offline (Meta Llama 2) and Online (Azure Open AI) LLMs: •Requirement Gathering and Summarization •Functional Spec Creation •Feature Prioritization and Roadmap Creation •Feasibility and Risk Analysis •Project Level Tarige and Planning •Release Planning •Upstream Connector Integrations: JIRA •Downstream Application Plugins: •IDE: Visual Studio, JetBrains •Browser: MS Edge •Support for new Online LLMs: •Google Vertex AI PaLM •AWS Bedrock Titan",, "Q1 FY25ISE v3.2 Support Training Use Cases, Upstream and Downstream Connectors, Security Enhancements Q4 FY24iTS v3.1 Integration Pipeline strengthening and new online/offline GenAI use cases •Reinforcement Learning Pipeline for OpenAI •Reinforcement Learning Pipeline for Llama2 •Distributed Inference Server Integration using” •vLLM •TensorRT -LLM •Additional Use Cases using Offline (Meta Llama 2) and Online (Azure Open AI) LLMs: •Case Notes Documentation •Predictive Maintenance •Log Trend Analysis •iTS UI Revamp •Prompt Configuration •Prompt Testing and Integration •Enhancement s to Usecase creation modules•Additional Support Use Cases using Offline and Online LLMs : •Virutal Issue Simulation •Workload Distribution •Training Documentation Creation •Machine Generated Events Monitoring •Executable Script Generation for Runbook •Virtual Tutoring •Upstream Connector Integrations: SNOW, SFDC •Security : •Homomorphic encription •Inflight data encryption •Support for new Online LLMs: •Google Vertex AI PaLM •AWS Bedrock Titan*",, "Market Overview Field service management (FSM) is an advanced software solution designed to effectively manage various components to streamline field activities such as scheduling, vehicle tracking, inventory management, and customer po/r_t.ligaals. FSM remains at the fore front of innovation, providing businesses with the latest tools and features to optimize their field service operations. By adopting FSM, firms can benefit by maximizing operational efficiency and fostering consumer-led experiences. There is, there fore a growing need for customer-centric solutions, leading to an increased demand for field service solutions. The global field service management (FSM) market was USD 2.87 billion in 2020. Its market size is estimated to grow from USD 3.24 billion in 2021 to USD 8.06 billion by 2028, at a CAGR of 13.9%. The increasing popularity and market share of FSM can be a/t_t.ligaributed to cu/t_t.ligaing-edge technological improvements in the field.Intelligent Automation for Field Suppo/r_t.liga (IAFS) is a framework developed on top of iTS (Intelli Service) that enables be/t_t.ligaer field suppo/r_t.liga operations by providing suppo/r_t.liga insights, enabling process optimization and improving field workforce productivity. IAFS solution resolves ticket quickly by deploying AI/ML models to mine critical insights. The framework reduces the manual effo/r_t.ligas involved in ticket resolution, reducess turn-around time and improves suppo/r_t.liga quality for products.",, "Functional Architecture iTS Engine Advanced Machine learning & analytics engineAdministrative ConsoleVe/r_t.ligaical Specific Integrations Web Inte/r_f.ligaace Mobile Inte/r_f.ligaace Chat Inte/r_f.ligaace APIIAFS Solution Overview Presentation/Integration Layer Distributed Model/Storage Distributed/Scalable AI/ML StackAPI Meta Data Wiki / KM Error/Bug DatabaseEscalation/Compatibility Matrix/Known IssuesEnvironment DB /CRM/CSAT DBKnowledge A/r_t.ligaicles, Title, Summary, ResolutionBug Description, Product/Env/Config to bug mappingIssue Occurances – Interval wise, E-Com DataPre-requisites for escalation, KI – Product/ver/build wiseIssue – Product/ ver/build/config/ env wiseAnalytics ETLInput SourcesText MiningNLU/NLP Graph/OntologyAssociation & Recommendation. Optimization ModelTime-Series Forecasting ScoringClassification Cluster Analysis Contextual RelevanceSentiment Analysis Usage Analysis Entity ExtractionDerived Models Custom RulesCustom LibraryBrowser Plugin/ExtensionsWeb Po/r_t.ligaal/Dashboard Consumption VOIP/Ecom Data Sources",, "Functional Challenges Functional Benefits Slow response time for basic first-level issuesConversational AI agent automatically responds to customer enquiries and pe/r_f.ligaorm tasks Multiple field visits required todeploy suppo/r_t.ligaPa/r_t.ligas prediction enables seamlessidentification of pa/r_t.ligas and their need for replacement Assigning tickets manually to different agents can be error-proneSma/r_t.liga ticket assignment suggests thebest service agent to assign the ticket Similar/duplicate tickets, clu/t_t.ligaered,unorganized tracking of updates and requestSma/r_t.liga ticket classification Unstructured big data is difficult to analyzeData is structured on the basis of the identified pa/t_t.ligaerns of events, errors & messages in log files from devices & equipment Sca/t_t.ligaered knowledge across multiple sources leading to increased MTTRAI/ML based advanced suppo/r_t.liga data analytics framework helps in examiningvarious data sources",, "Differentiators AI/ML based advanced suppo/r_t.liga data analytics framework to optimize product and field suppo/r_t.liga operations IAFS is preloaded with product and field suppo/r_t.liga use cases for easy adoption Ability to automate remote repair actions and diagnostics process. Enables volume avoidance and self-help capabilities Ability to easily train and onboard conversational inte/r_f.ligaace and predictive use cases over existing suppo/r_t.liga platformOut-of-the-box integration with various enterprise channels and applications like Teams, mIRC etc. Benefits of Intelligent Automation for Field Suppo/r_t.liga Reduces MTTR by 28.4%Reduces trouble shooting time by up to 50%Enables deskilling Reduces solutionidentification time by 41%Improves CSAT and product experiencHelps retain knowledgebase avoiding knowledge gap",, "Proof Points Why HCLTech? HCLTech continues to keep pace with the market dynamics through continued investments intechnology to ensureservice capability development. HCLTech has a strong focus on driving large-scale AI/ML transformation, specifically for the large enterprise. HCLTech’s Engineering and R&D Services (ERS) empowers enterprises to improve time-to-profit, accelerate product development and maximize return on investment. Building on four decades of leadership in engineering services, we combine the technological depth and solution-driven approach to provide customers with comprehensive end-to-end solutions. HCLTech’s ERS offerings span the entire spectrum of digital engineering solutions and leverage more than 60 solution accelerators and next-generation technologies such as Cloud, IoT, AI, augmented reality, vi/r_t.ligaual reality (AR/VR), and autonomous vehicles. HCLTech has a world-class delivery infrastructure and processes backed by strong management and governance teams.IAFS helped a leading online solutions vendor to help reduce the initial investigation time by identifying the possible solutions and related issues for any given problem statement.This enabled theteam to achieve an overall 10% improvement in mean response time and a 5 – 8% improvement in the mean time to resolution.IAFS helped a leading antivirus vendor reduce the overall incoming tickets via chat and emails by 60% with the help of chatbots. With the help of chatbot implementation, there was a significant reduction in the number of repo/r_t.ligaed issues, which were repetitivein nature, and productivity was improved by 10%. Large enterprise IT suppo/r_t.liga teams used IAFS to help standardize their operations by leveraging its features in a vi/r_t.ligaually integrated mode with their existing toolsets.Overall, an improvement of 15% in MTTR and a 5-10% improvement in MRT has been observed with an 85% of coverage.",, "hcltech.com HCLTech is a global technology company, home to more than 223,400 people across 60 countries, delivering industry-leading capabilities centered around digital, engineering, cloud and AI, powered by a broad po/r_t.ligafolio of technology services and products. We work with clients across all major ve/r_t.ligaicals, providing industry solutions for Financial Services, Manufacturing, Life Sciences and Healthcare, Technology and Services, Telecom and Media, Retail and CPG, and Public Services. Consolidated revenues as of 12 months ending June 2023 totaled $12.8 billion. To learn how we can supercharge progress for you, visit hcltech.com.",, "• • • • • • • • • • • • • • IAFS framework is built on top of iTS (Intelligent Tech Support) that leverage AI/ML and Generative AI to enhance field support operations . It offers valuable insights, optimize processes, streamlines ticket resolution, reduce manual efforts, product support quality, and offers predictive modeling capabilities .",, "Other software Pre-requisites Data Extraction Classification Clustering Predictive AnalyticsSentiment AnalyticsGen AI Fine tuned LLM Text analysis Recommendation NLP WebMobile Chat API Knowledge Repository Data Lake Document Library Logs CRM",, "1 Copyright © 2023 HCL Technologies | Confidential",, 2,, "3 • • • • • • • • • • • • • • • • • • • • • •",, "4 • • • • • • • Similar Ticket Identification Identification of similar tickets based on context for easy reference of the historical tickets Self Service & Technical Support Question answering module from a given data sourceResolution Recommendation Given a query, identify the best resolution for the given contextIssue Summarization Summarization of technically complex and verbose tickets for easy understanding and assignationEscalation Identification Classifying an issue as escalated issue for reduced MTTR Tone and Sentiment Analysis Analysis of tone and sentiment based on user input Diagnostics Questionnaire Identifying the relevant questionnaires for a given issue to arrive at a solutionRelated Issue Identification Identification of the next issue based on the current and historical trend Knowledge Base Article Creation Dynamic generation and documentation of the solution used for issue resolution Ticket Routing Identifying the right resource for assignation of the given issueAvailable using ML & Generative AI Available using Generative AI only",, 5,, "6 • • • • • • • • • • • • •",, "7 • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •",, "8 • • • • • • •",, 9,, 10,, 11,, 12,, "13 • • • • • • • • •",, 14,, 15,, 16,, "INTELLIGENT AUTOMATION for FIELD SUPPORT (IAFS)-MASTER LICENSE AGREEMENT BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN “ACCEPT” BUTTON, OR OTHERWISE USING THE PROGRAM, YOU (“LICENSEE” or “CUSTOMER”) AGREE TO THE TERMS OF THIS MASTER LICENSE AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND SUCH COMPANY OR OTHER LEGAL ENTITY TO THESE TERMSIN WHIAFS CASE THE TERMS “LICENSEE” WILL REFER TO SUCH ENTITY. THE AGREEMENT IS EFFECTIVE AS OF THE DATE YOU ACCEPT THESE TERMS (“Effective Date”). IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN “ACCEPT” BUTTON, OR USE THE PROGRAM; AND PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM IT WAS OBTAINED. IF THE PROGRAM WAS DOWNLOADED, DESTROY ALL COPIES OF THE PROGRAM. This Master License Agreement (“ Agreement ”)is made on [*************] by and between Licensee and HCL Technologies Limited , a company duly organized and existing under the laws of India and having its registered offices at 806 Siddharth, 96 Nehru Place, New Delhi -110019 (“Licensor ” or “HCL ”) and [*************] (“Licensee ”), and governs the receipt and use of IAFS and related Support (as defined below). Licensor and Licensee hereinafter referred to individually or collectively, as “Party ” or “Parties .” 1. Definitions. In addition to the terms defined above and elsewhere in this Agreement, the following terms will have the meaning set forth below: 1.1. “Affiliate ” means an entity that controls, is controlled by, or shares common control with HCL or Licensee, where such control arises from either (a) a direct or indirect ownership interest of more than",, "50%, or (b) the power to direct or cause the direction of the management and policies, whether through the ownership of voting stock, by contract, or otherwise, equal to that provided by a direct or indirect ownership of more than 50%. 1.2. “Documentation ” means guides, manuals, and other technical information in printed and machine - readable form for developing features that support IAFS . 1.3. “Feedback ” means (i ) Licensee's requirements, input, comments, responses, opinions, feedback and errata, concerning the definition, design or validation of IAFS and Documentation or (ii) Licensee's technical system requirements for HCL to include in the Licensed Software spec ifications, design or validation. 1.4. “Fees ” means license, Support, and other fees as specified in an Order or provided under this Agreement. 1.5. “Intellectual Property Rights ” or “ IPR” means any ideas, whether or not patentable, inventions, discoveries, processe s, works of authorship, marks, names, know -how, and any and all rights in such materials on a worldwide basis, including any rights in patents, inventor’s certificates, utility models, copyrights, moral rights, trade secrets, mask works, and all related, similar or other intellectual property rights recognized in any jurisdiction worldwide, including all applications and registrations with respect thereto. 1.6. “Licensed Capacity ” means the quantity of each IAFS node licensed as specified in an Order. 1.7. ""Object Code "" means software (IAFS ), including all computer programming code, entirely in binary form, wh IAFS is directly executable by a computer and includes those help, message, overlay, and other files necessary for supporting the intended use of the executable code.",, "1.8. “Open Source Software” means an open source or other license that requires, as a condition of use, modification, or distribution, that any resulting software must be (i) disclosed or distributed in Source Code form; (ii) licens ed for the purpose of making derivative works; or (iii) redistributable at no charge. 1.9. “Order ” means an agreed written or electronic document, subject to the terms and conditions of this Agreement that identifies IAFS to be licensed, the Licensed Capacity thereof, applicable Fees, and the Support to be purchased. 1.10. “Prerequisite Materials ” means any prerequisite software or materials (third party and/or HCL licensed) required by the Licensee, wh IAFS are not part of IAFS and are identified in the system requirements for IAFS . 1.11. “Problem ” means a reproducible condition that causes the operation of IAFS to deviate from its Documentation, so as to impact Licensee’s ability to use IAFS in the manner described in the Documentation. 1.12. “Program(s) ” means the Object Code of IAFS (including Third Party Software) and all accompanying Documentation delivered to Licensee, including all items delivered by HCL to Licensee under Support, but excluding Open Source Software. 1.13. “Source Code ” means computer programming code in human readable form and related system level documentation, including all associated comments, symbols, and any procedural code such as job control language. 1.14. “Supplemental Terms ” means document that provides information and any additional terms specific for IAFS and is attached as an Exhibit XX. 1.15. “Support” means the basic support services provided by HCL that available for IAFS as further specified in an Order or provided under this Agreement. 1.16. “Territory ” means the country or countries where Licensee is licensed to install IAFS as further detailed in an Order.",, "detailed in an Order. 1.17. “Third Party Software ” means third party software, libraries, and components incorporated in or included with IAFS , but excluding Open Source Software. 2. Agreement Structure. Licenses are granted and Support is obtained solely in connection with Orders executed by both parties. Each Order is subject to the terms of this Agreement and deemed to be a discrete contract, separate from each other Order, unless expressly stated otherwise therein. Orders may be entered into under this Agreement by and between (a) HCL or an Affiliate of HCL; and (b) the Licensee or an Affiliate of Licensee. With respect to an Order, the term HCL (or Licensor) or Licensee (or Licensee) will be deemed to refer to the entities that execute such Order. Neither execution of this Agreement nor anything contained herein will obligate either Party to enter into any Orders. In the event an Order is proposed by HCL, and is deemed to constitute an offer, then acceptance of such offer is limited to its terms. In the event Licensee proposes or accepts an Order by submitting a purchase order, order document, acknowledgment, or other communication, then regardless of whether HCL acknowledges, accepts, fully or partially performs under any such document, HCL objects and rejects any additional or different terms in such document and none of such additional or different terms will become part of the agreement between the Parties even if HCL uses or refers to such document for invoicing purposes. 3. License Grant 3.1. Subject to the terms, conditions, and other restrictions set forth in this Agreement and a valid, executed Order (including timely payments of any Fees therein), HCL grants to Licensee a non -exclusive, non- transferable, limited, and revocable license, without the right to sublicense, under HCL IPR, to install, access, and use IAFS (i) up to the Licensed Capacity; (ii) for Licensee internal business purposes; and",, "(iii) in accordance with the Documentation and the applicable Order. For avoidance of doubt, Licensee has no rights to create derivative works, assign, distribute, lease, rent, or otherwise transfer IAFS . 3.2. Licensee Affiliates may install, access, and use IAFS and Support under the terms of this Agreement, and Licensee is fully responsible for its Affiliates compliance with the terms of this Agreement and the Order.",, "3.3. Licensee hereby acknowledges that IAFS may contain Open Source Software and may require Prerequisite Materials . In the event that Third Party Software is included in the Program(s), Licensee agrees that unless separate supplemental terms are communicated via the release notes, the terms contained in this Agreement shall apply to use of such Third Party Software . In the event that IAFS rely on Prerequisite Materials, Licensee agrees that HCL and its Affiliates have not obtained or conveyed to Licensee any Intellectual Property Rights to use the applicable Prerequisite Materials. 4. License Restrictions 4.1. Restrictions . Except for the limited licenses expressly granted in Section 0, Licensee has no further rights in IAFS , whether express, implied, arising from estoppel or otherwise. Further restrictions regarding Licensee’s use of any and all Program(s) are set forth below. Except as expressly authorized herein, Licensee will not: 4.1.1. prepare any derivative works, or otherwise use, copy, modify, distribute, assign, sublicense, lease, rent, or otherwise transfer IAFS , except to the extent required by law; 4.1.2. use IAFS in an outsourcing or service bureau environment on its behalf and/or on behalf of non - affiliated third parties or allow IAFS to be used by an outsourcing or service bureau provider on behalf of the Licensee; 4.1.3. distribute IAFS to end -users as on -premises distributions or offer IAFS as a cloud service or software -as-a-service to any end-users; 4.1.4. reverse engineer, reverse assemble, reverse compile, translate, or otherwise attempt to discover the Source Code form of any Program(s) that are provided in Object Code form, except as permitted by the national or regional law of the places where the Licensee does business (without the opportunity for contractual waiver), and then only with r espect to the particular copy of Object",, "Code incorporated into that particular Program. 4.1.5. use any of IAFS ’s components, files, modules, audio -visual content, or related licensed materials separately from IAFS ; 4.1.6. attempt to disable or circumvent any of the licensing mechanisms within IAFS ; 4.1.7. alter or remove any copyright, trademark or patent notice(s) in IAFS ; and 4.1.8. use IAFS in a way that requires the Programs to be licensed as Open Source Software. 5. Feedback. Licensee is not obligated to provide Feedback to HCL. To the extent that Licensee provides Feedback to HCL, Licensee hereby grants to HCL a worldwide, non-exclusive, perpetual, irrevocable, royalty - free license, with the right to sublicense, under any and all Licensee IPR in and to the Feedback to make, use, sell, offer to sell, have made, import, reproduce, prepare derivative works, distribute, incorporate or otherwise utilize such Feedback. 6. Ownership. Licensee acknowledges that, as between Licensee and HCL, HCL has exclusive right, title and interest in and to all of the IPR in and to IAFS . Notwithstanding the use of the terms “purchase,” “sale”, or any similar terminology in connection with a transactio n contemplated by this Agreement, IAFS is licensed, not sold. 7. Delivery. During the term of this Agreement, and subject to Licensee making timely payments of any Fees in accordance with Section 11, HCL will make Program(s) avail able to Licensee. For Programs that are delivered electronically, Licensee agrees upon request from HCL to provide HCL with documentation supporting that the designated items were received electronically. For Programs that HCL provides to Licensee in tangible form, HCL fulfils its shipping and delivery obligations upon the delivery of such items to the HCL -designated carrier, unless otherwise agreed in writing by Licensee and HCL. The Programs are",, "accepted the day HCL delivers them either p hysically to the carrier or by providing access code(s) for electronic download, whIAFS ever occurs first. 8. Updates 8.1. If IAFS is replaced by a trade -up Program, the license for IAFS getting replaced will be promptly terminated. 8.2. When Licensee receives an update, fix, or patch to a Program, Licensee accepts any additional or different terms that are applicable to such update, fix, or patch that are specified in its Documentation.",, "If no additional or different terms are provided, then the update, fix, or patch is subject to the terms and conditions of this Agreement. 8.3. If IAFS is replaced by update, Licensee agrees to promptly discontinue use of the replaced Program. 8.4. Based on industry directions and technology changes, Licensor may discontinue further releases of IAFS . In such a situation, Licensor may continue to ship released versions of Programs, and all shipped versions will be governed by this Agreement. 9. Support 9.1. Licensee is automatically enrolled in Support for IAFS identified in an Order for the duration of the respective Order at no additional cost. HCL may offer and Licensee may purchase additional support, such as premium support, via the execution of a separat e contract. A further description of Support is available at https://www.hcltech.com/products -and-platforms/suppo rt (“Support Website”) and incorporated herein by reference. 9.2. HCL will provision and provide Support in accordance with the terms on the Support Website. Support is provided according to the support plan defined on the Support Website. HCL will only support a Program if it is used with third -party equipment, operating sy stem, hardware, and third -party software, including database server systems, networks, application server systems, and Licensee systems (collectively, “Platforms”) whIAFS meet the standards set forth in the applicable Documentation. Licensee will allow HCL reasonable access (including remote access) to IAFS and the supporting Platf orms, equipment, systems, documentation, and services, as necessary to perform Support services. Support does not include training on IAFS , Prerequisite Software or P latforms nor does it include any on-site diagnosis or on-site problem resolution. 9.3. HCL Program Support provides maintenance and technical support to Licensee for IAFS specified in",, "an Order. Support is limited to the specific release(s) of IAFS determined by H CL. Support for a particular version or release of a Program is available only for 3 years period OR until HCL withdraws Support for that Program's version or release (an “End of Support Release”). When Support is withdrawn, Licensee must upgrade to a supported version or release of IAFS to continue to receive Support. However, HCL will continue to offer, for an additional Fee to be mutually agreed -upon, the following extended support for End of Support Releases for so long as Licensee subscribes to Support for IAFS by: (i) answering Licensee’s routine, short duration installation and usage (how -to) questions; and (ii) answering Licensee’s code -related questions. However, in such cases, HCL will only provide existing code patches and fixes and will not develop or provide new patches or fixes for End of Support Releases. 9.4. HCL will use commercially reasonable efforts to provide resolution to each Problem submitted by Licensee in accordance with the Support Website. All Problems reported by a Support contact will be logged by a technology support engineer and assigned a tracking number. Licensee will be notified of the tracking number and should use this number in all f uture communication with HCL relating to such Problem. The severity level of a Problem will be determined in accordance with the applicable criteria set forth on the Support Website. HCL will use commercially reasonable efforts to resolve Problems within t he applicable designated timeframes set forth on the Support Website. In the event a Problem is not resolved within the designated timeframes, then HCL will escalate resolution in accordance with the procedures on the Support Website. Licensee will make re asonable efforts to assist HCL in identifying, isolating, and duplicating a Problem and will not hinder HCL’s ability to achieve Problem resolutions.",, "9.5. While HCL Support is in effect, HCL may make available defect corrections, restrictions, bypasses, new versions, releases, or updates available as part of Support (“Updates”). HCL will determine in its discretion the content and timing of all Updates. Updates will not be issued on any regular basis. If the solution to a Problem has already bee n made in a release later than the release Licensee is then using, then the solution to the Problem will require Licensee to migrate to the release in IAFS the Problem has been resolved. Updates will be considered part of IAFS , as applicable, and will be governed by and used under the terms and conditions set forth in this Agreement. Except as otherwise set forth in an Order, Statement of Work, or other agreement by the Part ies, Licensee will be responsible for installing and implementing each Update. HCL will provide Licensee with documentation regarding any specific",, "installation requirements for the Update. Once Support has been allowed to lapse, HCL will cease providing Updates (even Updates that were previously made available during Support IAFS Licensee chose not to accept). 9.6. Support does not cover problems, failures, or defects in the Programs caused by: (a) the misuse of or damage to the Program; (b) modificat ions to IAFS not made by or as authorized in writing in advance by HCL; (c) combination or use of IAFS with other software or hardware not provided or approved in writing by HCL; or (d) use of the Program in an operating environment other than that described in the Documentation or system requirements. HCL reserves the right to charge at HCL’s then -current standard hourly rates for any work performed by HCL that was found to be caused by the foregoing exclusions. To the extent a problem arises out of any Prerequisite Sof tware, Platform, hardware or services, Licensee will have the responsibility to contact the appropriate third party and obtain a resolution for the problem. 9.7. HCL may change its Support terms to be effective upon Licensee’s support anniversary date. HCL reserves the rights to discontinue Support for IAFS (including for prior releases or outdated versions of a Program) if HCL generally discontinues such services f or all licensees of such Program, provided such discontinuance of Support will be applicable from the next Support renewal term. If Licensee terminates Support, but then re-enrolls in Support, HCL reserves the right to charge a reinstatement Fee. 10. Licensee Data and Databases 10.1. To assist Licensee in isolating the cause of a problem with IAFS , HCL may request that Licensee (i) allow HCL to remotely or physically access Licensee’s system, or (ii) send Licensee information or system data to HCL. However, H CL is not obligated to provide such assistance unless HCL and",, "Licensee enter a separate written agreement or Order under IAFS HCL agrees to provide to Licensee that type of Support, IAFS is beyond HCL’s warranty obligations in this Agreement. Licensee acknowledges that HCL uses information about errors and problems to improve its products and services and to assist with its provision of related Support offerings. Licensee grants HCL the right to use such information and other feedback regarding IAFS for these purposes, including the right to use HCL entities and subcontractors (including in one or more countries other than the one in IAFS Licensee is located). 10.2. Licensee remains responsible for (i) any data and the content of any database Licensee makes available to HCL (“Licensee Data”); (ii) the selection and implementation of procedures and controls regarding access, security, encryption, use, and transmission of data (including any personally -identifiable data); and (iii) backup and recovery of any database and any stored data, including all Licensee Data. Licensee will not send or provide HCL access to any personally identifiable information, w hether as part of Licensee Data or in electronic or any other form, and will be responsible for reasonable costs and other amounts that HCL may incur relating to any such information intentionally or mistakenly provided to HCL or to the loss or disclosure of such information by HCL, including liabilities arising out of any third party claims. 11. Payments . 11.1. Fees . Licensee will pay any and all Fees as detailed in an Order. All amounts in this Agreement are in United States Dollars (USD). Licensee will pay HCL for the amounts due, owing, and duly invoiced under this Agreement within thirty (3 0) days of the date of invoice. Licensee shall make all payments pursuant to this Agreement through electronic transfer of funds to the designated bank accounts as",, "nominated by the HCL in writing. Overdue amounts payable under an Order will bear interest from the original due date at the rate of one percent (1%) per month or the maximum legal rate, IAFS ever is less. 11.2. Taxes . Licensee agrees to bear any withholding tax liability as may be required by law and would increase payment due under the Agreement by such an amount so that the net payment made to HCL after deduction of applicable withholding tax is the same, had there been no withholding tax applicable. 11.3. Licen se Compliance . Licensee agrees that HCL may, no more than one time per twelve (12) month period, audit the software logs of Licensee, its Affiliates, consultants, service providers and contractors (collectively, “Licensee Entity(ies) ”), relating to the Program in order to verify their use in compliance",, "with this Agreement and/or the Order. HCL may make copies of any such software logs to the extent necessary to verify Licensee’s compliance with the terms hereof. HCL may conduct the audit itself or at its option engage an independent third party to do such audit, provided that such third party is subject to confidentiality obligations consistent with this Agreement. The audit may be conducted at any sites of Licensee Entities, where the Program is installed, used or accessed from, including remotely. HCL will bear its own costs in connection with an audit. HCL will provide fifteen (15) calendar days’ notice prior to an audit. Any such audit will be performed during Licensee Entity’s normal business hours and in a manner that minimizes the disruption to its business. Licensee Entities will provide all assistance reasonably necessary for HCL to carry out such audit. If the audit reveals underpayments, Licensee will promptly make such payments. If the audit reveals under -reporting of usage, Licensee will promptly pay for the differentials at HCL’s then list price fo r the Program. HCL’s rights and remedies in this Section will be without prejudice to other rights and remedies HCL has under this Agreement or in any Order, at law or in equity. HCL’s rights under this provision will survive any termination or expiry of an Order or this Agreement for two years. 12. Term and Termination . 12.1. Term . Unless earlier terminated pursuant to the terms of the Agreement, the initial term of this Agreement is three (3) years from the Effective Date (the “Initial Term”). Unless either Party gives the other Party written notice thirty (30) days prior to the expiration of the then current term, this Agreement will automatically renew for successive periods of one (1) year each. 12.2. Termination by HCL. HCL may terminate this Agreement and any Order upon written notice to Licensee if:",, "Licensee if: 12.2.1. Licensee fails to pay the applicable Fees due under the Order within thirty (30) days of receipt of written notice from HCL for non-payment; 12.2.2. Licensee violates the IPR of HCL, its Affiliates, or its licensors or uses IAFS outside the scope of the license; 12.2.3. Licensee commits any material breach of this Agreement and fails to cure such breach within thirty (30) days after HCL notifies Licensee in writing of the breach; or 12.2.4. Licensee (i) files or has filed against it a petition in bankruptcy, (ii) has a receiver appointed to handle its assets or affairs, or (iii) makes or attempts to make an assignment for benefit of creditors. 12.2.5. HCL’s rights to terminate are in addition to any other rights HCL may have. 12.3. Effect of Termination or Expiration . In the event of termination or expiration of this Agreement, in whole or in part: 12.3.1. All licenses granted hereunder will terminate; 12.3.2. Licensee will return to HCL and/or certify that it has destroye d all copies of IAFS and Documentation, IAFS is in the possession of the Licensee; and 12.3.3. all Support obligations under the Agreement or an Order will terminate. 13. Confidentiality . Except as otherwise expressly permitted in this Agreement, Licensee will hold in confidence IAFS , Documentation and all other non-public or proprietary information made available by Licensor (“Confidential Information ”). Licensee agrees that the Programs and Documentation furnished by HCL will be treated as proprietary trade secrets of Licensor, and Licensee will not make any Confidential Information available in any form to any person other than to its employees and to contractors located on its premises with a need to know, subject to restrictions no less stringent than those contained herein (in the case",, "of nonemployees such restrictions will be contained in a written agreement executed by the applicable contractor). Licensee represents to Licensor that it maintains a system of confide ntiality to protect its own confidential business information, including written agreements with employees, and that the Confidential Information will be protected by such system using no less than a reasonable degree of care. If Licensee at any time becom es aware of any unauthorized use or disclosure of Confidential Information, Licensee will promptly and fully notify the Licensor of all facts known to it concerning such unauthorized use or disclosure",, "and reasonably cooperate with Licensor in seeking a protective order or other appropriate remedy to limit such disclosure. 14. Warranties and Exclusions 14.1. HCL warrants that (i) IAFS will perform substantially in accordance with its Documentation f or the duration of the relevant order (the “ Warranty Period ”); (ii) HCL has used commercially reasonable efforts consistent with industry standards to scan for and remove any software viruses; and (iii) other than passwords or license keys that may be required for the operation of IAFS , there are no codes that are not addressed in the Documentation and that are designed to delete, interfere with, or disable the normal operation of IAFS in accordance with the License (the “Warranty ”). 14.2. THE LIMITED WARRANTIES EXPRESSLY SET FORTH IN SECTION 14.1 ARE LICENS EE’S EXCLUSIVE WARRANTIES. HCL DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND ANY WARRANTY OR CONDITION OF NON - INFRINGEMENT. SOME STATES OR JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF EXPRESS OR IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO LICENSEE. IN THAT EVENT, SUCH WARRANTIES ARE LIMITED IN DURATION TO THE WARRAN TY PERIOD. NO WARRANTIES APPLY AFTER THE WARRANTY PERIOD. SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATION MAY NOT APPLY TO LICENSEE. 14.3. THE WARRANTIES IN THIS SECTION 14 ARE PROVIDED SOLELY BY THE HCL ENTITY LICENSING IAFS AND NOT BY A THIRD PARTY OR ANY OTHER HCL ENTITY. THE DISCLAIMERS IN THIS SECTION 14, HOWEVER, ALSO APPLY TO ALL HCL ENTITIES AND THEIR LICENSORS AND SUPPLIERS OF THIRD PARTY SOFTWARE. . THOSE SUPPLIERS PROVIDE SUCH SOFTWARE WITHOUT WARRANTIES OR CONDITION OF ANY KIND.",, "14.4. The exclusive remedy for any breach of the foregoing Warranty will be that HCL, at its own expense, and in response to a written notice of a warranty claim, will at its option (i) repair or replace IAFS to conform to the above standard, or (ii) refund to Licensee amounts paid for the non -conforming Program(s). 15. Indemnification 15.1. HCL will settle and, at its election, defend, any claim brought in any suit or proceeding against Licensee based upon an allegation that any Program(s) furnished hereunder constitutes a direct infringement of any patent, trade secret or copyright, and HCL will pay all damages and costs finally awarded against Licensee for the claim. In the event of any claim, allegation, or suit, HCL, in its sole discretion, may reengineer IAFS in a manner that removes the infringing material, replace IAFS with non-infringing software, or terminate the Agreement. HCL will not be liable for any costs or damages and will not indemnify or defend Licensee to the extent such action is based upon a claim arising from: 15.1.1. modification of IAFS by a party other than HCL after delivery by HCL; 15.1.2. use of IAFS in combination with hardware or software not provided by HCL, unless (i) the Documentation refers to a combination with such hardware or software (without directing Licensee not to perform such a combination); or (ii) such combination achieves functionality described in the Documentation (and the Documentation does not direct Licensee not to perform such combination); 15.1.3. any unauthorized use of IAFS ; or 15.1.4. Licensee’s failure to incorporate updates or upgrades that would have avoid ed the alleged infringement.",, "15.2. The foregoing obligations are conditioned on the following: (i) HCL is notified promptly in writing of such claim; (ii) HCL controls the defense or settlement of the claim; and (iii) Licensee cooperates reasonably and gives all necessary authority, information and assistance. 16. Limitation of Liability 16.1. IN NO EVENT WILL EITHER PARTY (OR HCL’S SUPPLIERS) BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE IAFS , OR OTHERWISE IN CONNECTION WITH ANY PROVISION OF THIS AGREEMENT, EVEN IF THE PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND EVEN IF THE REMEDY FAILS OF ITS ESSENTIAL PURPOSE. 16.2. EXCEPT FOR BREACHES OF LICENSE GRANTS IN SECTION 3, RESTRICTIONS IN SECTION 4, CONFIDENTIALITY IN SECTION 13, AND LICENSEE’S PAYMENT OBLIGATIONS, IN NO EVENT WILL EITHER PARTY'S (OR HCL’S SUPPLIERS) TOTAL CUMULATIVE LIABILITY TO THE OTHER PARTY FOR ANY DIRECT DAMAGES ARISIN G FROM THIS AGREEMENT, EXCEED THE SUM PAID OR PAYABLE TO HCL BY LICENSEE UNDER THIS AGREEMENT FOR THE PRECEDING TWELVE (12) MONTHS FROM THE DATE THE CLAIM AROSE. 16.3. The foregoing disclaimers, limitations, and exclusions may be invalid in some jurisdictions an d apply only to the extent permitted by applicable law or regulation in Licensee’s jurisdiction. Licensee may have additional rights that may not be waived or disclaimed. HCL does not seek to limit Licensee's warranty or remedies to any extent not permitted by law. 17. Other Terms 17.1. Conflict . In the event of a conflict between this Agreement and an Order attached to this Agreement, the terms of the Order will prevail solely with respect to such Order and only to the extent that such",, "conflicting terms are necessary to satisfy the requirements of applicable, local laws; otherwise the terms of this Agreement will prevail. 17.2. Force Majeure . Neither Party will be liable for any failure to perform due to unforeseen circumstances or causes beyond its reasonable control, including, but not limited to, acts of God, war, riot, embargoes, acts of civil or military authorities, delay in delivery by vendors, fire, flood, accident, strikes, inability to secure transportation, facilities, fuel, energy, labor, or materials. In the event of force majeure, time for delivery or other performance will be extended for a period equal to the duration of the delay caused thereby. 17.3. Export . Licensee will comply with all applicable export and import laws and associated embargo and economic sanction regulations, including those of the United States, that prohibit or restrict the export, re-export, or transfer of products, technology, services, or data, directly or indirectly, to certain countries, or for certai n end uses or end users. Licensee acknowledges that IAFS is subject to U.S. export laws and regulations. Licensee agrees that, unless authorized by the U.S. export license or regulation, it will not export or re -export IAFS provided by HCL under this Agreeme nt or an Order to (i) those countries (or nationals of countries) considered embargoed/terrorist countries under U.S. export laws and regulations or (ii) prohibited end users or end uses, including but not limited to: nuclear, space or missiles, and weapons systems (including chemical and biological). At the time of this Agreement, those countries considered embargoed/terrorist are: Cuba, Iran, North Korea, Sudan and Syria. 17.4. Anti -Corruption Laws. Each Party will comply, at its own expense, with all applicable laws, including, without limitation, all laws prohibiting corruption and bribery (such as, if applicable, the U.S.",, "Foreign Corrupt Practices Act of 1977), laws governing transactions with government and public entiti es, antitrust and competition laws, insider trading, securities, and financial reporting laws, laws governing consumer transactions, and laws regarding data privacy, where such compliance has any direct or indirect connection or relation to this Agreement or either Party’s exercise of rights or satisfaction of obligations under this Agreement.",, "17.5. Notices. All notices required or permitted by this Agreement will be in writing and will be valid and sufficient if sent by (i) registered or certified mail, return receipt requested, postage prepai d; (ii) by facsimile (provided the receipt of the facsimile is evi denced by a printed record of completion of transmission); or (iii) by express by express mail or courier service providing a receipt of delivery. Notices will be effective upon receipt as demonstrated by reliable confirmation. Notices will be addressed to the Parties using the contact information given in an the applicable Order or this Agreement. Either Party may change its address or other contact information by a notice given to the other Party in the manner set forth above. 17.6. Limitation of Claims. Unless otherwise required by applicable law without the possibility of contractual waiver or limitation: (i) neither party will bring a legal action, regardless of form, for any claim arising out of or related to this Agreement more than two (2) years after the cause of action arose; and (ii) upon the expiration of such time limit, any such claim and all respective rights related to the claim lapse. 17.7. Survival . All of the provisions in Sections 1, 4, 5, 6, 11, 12, 13, 16, and 17 w ill survive expiration or termination of this Agreement. 17.8. Assignment. HCL may assign or delegate its rights and/or obligations, or any part thereof under this Agreement to any or all of its subsidiaries. Licensee will not assign or transfer this Agreement or an Order executed under this Agreement, without the written consent of the Licensor. Except as mentioned herein, any attempted assignment or transfer by Licensee of this Agreement or Programs is null and void. 17.9. Relationship of Parties. The relationship between the Parties is that of independent contractors. This Agreement does not constitute a partnership or joint venture between Licensee and HCL. Licensee is",, "not the representative or agent of HCL and HCL is not the representative or agent of Licensee and neither will so hold itself out publicly or to any third party or incur any liability for the other Party. 17.10. Modifications . This Agreement may be modified or amended only by a written instrument duly signed by authorized representatives of Licensee and HCL. 17.11. Severability . All rights and remedies whether conferred hereunder, or by any other instrument or law will be cumulative and may be exercised singularly or concurrently. The failure of any Party to enforce any of the provisions hereof will not be construed to be a waiver of the right of such Party thereafter to enforce such provisions. The terms and conditions stated herein are declared to be severable. If any provision or provisions of this Agreement will be held to be invalid, illegal or unenforceable, the validity, legalit y and enforceability of the remaining provisions will not in any way be affected or impaired thereby. 17.12. Counterparts . This Agreement may be executed in several counterparts, each of wh IAFS will be deemed an original, but all of whIAFS together will constitute one and the same instrument. 17.13. Injunctive Relief . Licensee agrees that preliminary injunctive or other equitable relief will be a necessary and proper remedy in the event of a breach of this Agreement in violation of HCL’s IPR, in addition to all other rights that HCL has at law or in equity. 17.14. Governing Law and Jurisdiction . Any claims arising under or relating to this Agreement will be governed by the internal substantive laws of the State of California or federal courts located in California, without reference to (i) any conflicts of law principle that would apply the substantive laws of another jurisdiction to the Parties’ rights or duties; (ii) the 1980 United Nations Convention on Contracts for the International Sale of Goods; or (iii) other international laws. Each Party hereby",, "irrevocably agrees to submit to the jurisdiction and venue in the courts of the State of California f or all disputes and litigation arising under or relating to this Agreement. 17.15. Public Announcement . Neithe r Party will publicly announce or create a press release referencing this Agreement, its contents or its related activities without the prior written consent of the other Party. 17.16. Entire Agreement . This Agreement is the entire agreement between HCL and Licen see relating to the Program(s) and it supersedes all prior or contemporaneous oral or written communications,",, "Agreed: proposals and representations with respect to IAFS or any other subject matter covered by this Agreement. LICENSEE: _______________________ HCL. By: Typed Name: Title: Date: By: Typed Name: Title Date:",, "IAFS -Field Support Comparison and Recommendation deck",, "Copyright © 202 3HCL Technologies Ltd. | Confidential 2 Use Cases Productivity Customer Satisfaction Response time Collect relevant Historical data Mine critical information By Using AI/MLOptimize task, Improve process and productivity Field support solution incorporates cutting -edge AI/ML and Generative AI technologies to optimize field support operations . It built on top of iTS framework and streamlines ticket resolution, reduce manual efforts, improve product support quality to boost efficiency and productivity for field support teams . Only with Generative AIUse cases with GenAI and ML both",, "Company Accelerator Capabilities Features Top Clients Industry Covered Pricing Microsoft Microsoft Dynamics 365 Field Service1.Self-service Scheduling 2.Faster issue resolution 3.Streamline work order management 1. Self -service appointment Scheduling 2. Automate customer communication 3. Provide post engagement surveys 4. Provide tools directly in the flow of work 5. Streamline tasks using the mobile experience 6. Resolve issues quickly with remote collaboration 7. Streamline work order by using Generative AI 8. Intelligent Recap feature to stay up to date 9. Track performance with real time reporting 1. G&J Pepsi 2. Phillips 3. Santam 4. UD Trucks 1. Manufacturing 2. IT Service 3. Healthcare and Biotech Industry 4. Retail Industry 5. Finance (non -banking) Industry $20-$300 per user/ per month PraxedoPraxedo Field Service Management1. Scheduling 2. dispatching 3. Tracking 4. Reporting 5. Invoicing1. Configurable web app that allows define organization, business processes, and workflows. 2. Advanced scheduling based on skillset, travel time, and customer availability. 3. Dynamic scheduling dashboard 4.Mobile app for online and offline work 5. Inventory tracking 6. Customer portal that update real time communication.",, "communication. 7. APIs that enables to integrate Praxedo with client existing ERP, CRM, or accounting software. 1. Constructel 2.Altitute Infra 3. Premier Lifts 4. Simoneau 5. Veolia 6. Engie 7. Suez1. Manufacturing 2. Energy and Utilities 3. Construction Industry 4. Insurance (except health) Industry 5. Hardware Industry 6. Banking Industry 7. Energy and Utilities Industry 8. Telecommunication Industry $33 -$79 per user/ per month SalesForceSalesforce Field Service1. Scheduling 2. dispatching 3. Tracking 4. Reporting 5. Invoicing1.Scheduling and Optimization 2. Mobile productivity Tools 3. Dispatch Management 4. Asset service Management 5. Visual Remote Assistance 6.Appointment Assistance 1. Uber Eats 2. Western Union 3. Humana 4. The Auto club group 5. Schneider Electric 6. Pella windows and doors1. Manufacturing 2. Energy and Utilities Industry 3. Consumer Goods Industry 4. Telecommunication Industry. 5. Healthcare and Biotech 6. Media Industry 7. Construction Industry $25-$500 per user/ per month OracleOracle field Service 1. Scheduling 2. dispatching 3. Tracking",, "3. Tracking 4. Reporting 5. Invoicing1. Forecasting and workload management 2. Capacity Management 3. Scheduling and routing 4. Technician Enablement 5. Customer Self -Service 6. IOT and connected equipment 7. Service Logistics 1. Badger Daylighting 2. Enersense 3. Vivint smart Home 4.Ricoh 5. Cablevision 6. BOSCH 1. Energy, Utilities & resources 2. Manufacturing Industry 3. Service Industry 4. Telecommunication $100 -$225 Per user/Per Month",, "Software Starting price Key features Zendesk$19 per agent/monthOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics Tagging System integrations Ticket assignment flexibility No-code chatbot builder Zoho Desk$20 per user/monthOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics Tagging System integrations Ticket assignment flexibility No-code chatbot builder FreshdeskFree plan availableOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics Tagging System integrations Ticket assignment flexibility No-code chatbot builder LiveAgentFree plan availableOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics Tagging System integrations Ticket assignment flexibilitySoftware Starting price Key features HubSpot Ticketing SystemFree plan availableOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics, Tagging Ticket assignment flexibility, System integration SupportBee$15 per user/monthOmnichannel and intelligent routing Reporting and analytics Tagging, System integration, Ticket assignment flexibility TeamSupport$49 per agent/monthAutomations and workflows Agent interface with unified customer view Reporting and analytics Tagging, System integration, Ticket assignment flexibility HappyFox$39 per agent/monthOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics Tagging, System integration, Ticket assignment flexibility No-code chatbot builder Jira Service ManagementFree plan availableOmnichannel and intelligent routing Automations and workflows Agent interface with unified customer view Reporting and analytics Tagging, System integration, Ticket assignment flexibility",, "Web Help Desk by SolarWinds$19 per technician/monthAutomations and workflows Agent interface with unified customer view Reporting and analytics Tagging System integrations",, "deepsense.ai 2.Understand service MS Dynamics 365 Field Service SF Field Service Senti Sum Automation Anywhere",, "Company Accelerators Powered by Services Infosys REF-OR-M smart field Automation Microsoft 360 dynamics solution Asset Management Field service Team management Knowledge Management Accurate field force Scheduling Wipro Connected field service solution Azure IOT Microsoft connected field service Prescriptive maintenance Remote monitoring Connected devices IoT Analytics on Azure TCS NextGen Field Services Microsoft Azure AI, ML, IoT, digital twins, and more.Unified real -time information view Predictive field -service and advanced forecasting Omnichannel customer Collaboration Personalized customer experience Tech Mahindra Yantri.ai ORACLE IFS Click Software Scheduling and dispatch Workforce Mobility Service analytics Contract management",, Optimizing Field services Through AR,, Decision Support,, "10Voice based Support –AutoBot Automated documentation with GenAIForecast FailureAutomated alerts and notifications Dynamic Knowledge base maintenance Virtual training simulationsScenario modeling Workload forecasting/Demand predictions Predictive Ticket Resolution TimeResolution Upgradation",, "1FY24Graviton v2.0 Modern Data Platform with support for AWS and Intelligent Data Services •DataOps –Predction of pipeline delays and failures •Data Security Audit and Vulnerability Assessment •Data Minimization and masked data containerization •SelfService BI dashboard for interactive Data visualization •Collaboration workspace –Data Product Lifecycle Management, centralized configuration management •FinOps implementation to track cost and usage at project and resource level •Lake formation and data pipeline creation in AWS (Amazon S3, AWS Data Pipeline ) •PII compliant semantic domain layer over AWS data lake •Data Governance and Cataloging using AWS Data Governance •Integration with Sagemaker Studio to support AI/ ML FY23Graviton v1.0 Modern Data Platform with support for Azure and Intelligent Data Services •Synthetic Data generation (with and without differential privacy), Data Anonymization, AI assisted Data Labelling •Multi -dimensional Data Quality Assurance •Anomaly detection Service for time series data, single and multivariate data •Collaboration Workspace (RBAC, cloud resource provisioning) •DataOps –data observability, pipeline health monitoring, proactive measurement of delays, data lineage and affected schema teacking, alerts configuration •Semantic domain layer for Azure Data Lake and differential privacy -based data querying •Unstructured Data parsing using AI -Regex Engine •Out of box use case: Connected Factory and Customer 360 (churn)FY22Graviton v0.1 Data Platform Pilot (Utilities, E2E pipeline) •Data Pipeline and Storage –Azure PaaS and IaaS integration •Data Cataloging and governance (Azure Purview) •Data Zone level security definition, data classification and sensitive data identification using Purview •Data transformation and orchestration –Databricks integration, Apache airflow integration, CARE gateway integration •Creating data pipelines and data flow using ADF, Azure Synapse Integration •Out of box use case: Device Predictive Maintenance",, Graviton Long Term Product Roadmap,, "Positioning Statement For data engineering teams which want to create data products and feel the need of a modern data platform to do so, Graviton provides an implementation framework for modern data platform using polyglot data technologies, open -source data frameworks, and cloud native data services . In this way, it facilitates development and delivery of optimal data products and efficient management of data product lifecycle from develop men t to production. Unlike competition products, Graviton is highly customizable and provides additional suite of capabilities such as a collaboration w orkspace, data ops capabilities and data services for Multi -Dimensional Data Quality, Synthetic Data Generation, Differential Privacy, Unstructured Data Parsing , Data Labelling etc.Graviton – Powering Modern Data Platform Customer Challenges Business Benefits HCL’s GRAVITON Offerings Differentiators Customization support as per customer’s needPlug & Play intelligent data services and utilities Easy Integration with Customer’s existing platform/ tech stackCombined power of HCL IPs, hyperscaler capabilities, OSS and niche partner products❖Development of modern data platform is challenging and time consuming.❖Graviton enables implementation of modern data platform using polyglot data technologies, open -source data frameworks & cloud native services❖Time and effort savings with an efficient data modernization solution (up to 25%) ❖Limited collaboration between different stakeholders involved in data product development❖Graviton provides a collaboration workspace for seamless collaboration between different stakeholders for data product creation and management❖Improve d collaboration between data engineering and platform teams resulting in higher efficiency ❖Lack of intelligent tools that can be used by data engineering teams for data related issues❖Services such for multi -dimensional data quality, synthetic data generation, differential privacy, unstructured data",, "parsing help solve data related problems❖Reduced effort allowing data teams to focus more on creating innovative data products (up to 75%) ❖Limited observability and monitoring capabilities for data pipelines resulting in delayed issue identification and negative impact on delivery of data products ❖Graviton provides a single data observability control pane to monitor various data pipelines❖Increased Efficiency –DataOps teams can track and proactively fix issues related to data pipelines that might affect the smooth and timely delivery of data products 1",, "Graviton enables implementation ofModern Data Platform using polyglot data technologies, open -source data frameworks and cloud -native data services .Itfacilitates development and delivery ofoptimal data products and efficient management ofdata product lifecycle from development toproduction . Graviton provides a collaboration workspace, data observability control pane, data services and integrates with Hyper - scalers (Azure, AWS, GCP), HCL IPs (AION), OSS (Apache, Linux Foundation) to efficiently build, deploy, monitor and maintain an agile and cost-efficient modern data platform. Graviton – Powering Modern Data Platform 2",, "Copyright © 202 3HCL Technologies Ltd. | Confidential ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ 1",, "Copyright © 202 3HCL Technologies Ltd. | Confidential • • • • ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ • • ▪ ▪ ▪ ▪ ▪ ▪",, "HCLTech is a global technology company, home to 222,000+ people acros s 60 countries, delivering industry -leading capabilities centered around Digital, Engineering and Cloud, powered by a broad portfolio of technology services and software. The company generated consolidated revenues as of $12.3 billion over the 12 months ended December 2022. To learn how we can supercharge progress for you, visit hcltech.com.",, "Copyright © 2022 HCL Technologies | Confidential ERS Research",, "2Market Opportunities in Data Engineering GLOBAL BIG DATA AND DATA ENGINEERING SERVICES MARKET SIZE The global big data and data engineering market is estimated to grow from USD 39.5 billion in 2020 to USD 87.37 billion by 2025 at a CAGR of 17.6% *39.5 USD billion 87.37 USD billion CAGR = 17.6% 2020 2025 Source: https://www.marketdataforecast.com/market -reports/big -data -engineering -services -market https://www.marketsandmarkets.com/Market -Reports/big -data -engineering -services -market -165583166.htmlNorth America is expected to hold the highest market share in the big data and data engineering services market (36% market share ) followed by Europe (29% share ) and Asia Pacific (25% share ) * Asia Pacific region is expected to be the fastest growing geographical sector in the near future . The main drivers for the growth are: •Increasing needs for scalability, automation, agility, improved customer experience and cost savings •Growing adoption of cloud and related technologies •Rapid increase in the volumes of structured and unstructured data due to the growth of interconnected devices •Increased need for security, reliability optimum resource utilization, data backup and recoveryGROWTH OPPORTUNITIES The solutions in the big data and data engineering services are subdivided into the following: •Data Discovery •Data Visualization •Data Management •End-use Data Analytics",, "3Need for a Modern Data Platform Recent Technological Trends: Over the last 10 -15 years: •Manifold increase in the amount of data generated •Cloud has become the new norm •Data pipelines have become capable of handling terabytes of data •Storage has become cheap and fast •Data Processing frameworks have become more powerful ( Spark ) •AI/ML applications have proliferated every industry segment But, what is the problem? While all of these individual pieces of technology have matured, integrating all of them together is still a challenge. This has resulted in Data Silos that are: •Unscalable •Contain duplicate, out -of-date data •Have no security layer •Have caused organizations to be locked into proprietary solutions The Solution: Modern Data Platform A combination of interoperable, scalable, and replaceable technologies working together to deliver an enterprise’s overall data needs, allowing organizations to become data -driven and create efficient data products to deliver value to their ever -changing customers.",, 4Building Blocks of Next Generation Modern Data Platforms,, GRAVITON –SOLUTION OVERVIEW,, 6,, 7Modern Data Platform – Powered by Graviton,, 8Filling the gaps with Graviton – A representative view for Azure,, "9Customer Landscape – Downstream Use Cases and Segments Target Segments : •Manufacturing •Industrial •Semi •Aero •Auto •Telecom •Medical devicesPredictive MaintenanceEnterprise collaboration & data management platformConnected Factory/ Connected DesignConnected Vehicles/ Connected DevicesProduct Intelligence, Performance & Usage AnalyticsCustomer 360 Target Segments : •Manufacturing •Industrial •Healthcare •Telecom •ISV/OnlineTarget Segments : •Manufacturing •Industrial •Auto •SemiTarget Segments : •Medical devices •Aero •AutoTarget Segments : •Semi •Aero •Auto •ISV/Online •TelecomTarget Segments : •Telecom •Retail •Auto •Healthcare (Patient 360)",, "11Solution Architecture – A representative view for Azure Data Storage and processing Source Systems Data Ingestion Data Management Analytics & Visualization Core Sources Device DataData Ingestion Databricks Data Pipeline Raw Layer Curated Layer Azure Data Lake StoreAzure /GCP/AWS Cloud Platform Real Time Load Initial Load & Delta Load Real Time Data Batch Azure Purview (Data Governance)Orchestration and Scheduling by ADF/ Airflow Azure IOT Hub Azure Event Hub Azure SynapseData Warehouse Data Lake Analytical Sandbox & Model Management for Analytics as a ServicePower BI Data ModelPower BIPredictive Maintenance Dashboards PII compliant Semantic domain layer Synergizer Azure Kubernetes Service Snowflake DWH DataScope Xenius (Synthetic Data) Security implemented through Azure Active Directory Data Labelling, Data Quality, Unstructured Data Parsing",, "Core Sources Device Data 12Solution Architecture – A representative view for AWS Data Storage and processing Source Systems Data Ingestion Data Management Analytics & Visualization Data Ingestion Databricks Data PipelineRaw Layer Curated Layer AWS Data Lake StoreAWS DevOps Real Time Load Initial Load & Delta Load Real Time Data Batch AWS Data GovernanceOrchestration and Scheduling by AWS Glue AWS IOT AWS Kinesis AWS RedShiftData Warehouse Data Lake Analytical Sandbox & Model Management for Analytics as a ServiceQuickSight DatasetPredictive Maintenance Dashboards PII compliant Semantic domain layerData Labelling, Data Quality, Unstructured Data Parsing AWS Cloud WatchAWS EKS Snowflake DWH Security implemented through AWS IAM QuickSight Synergizer DataScope Xenius (Synthetic Data)",, "13Solution Architecture – A representative view for GCP Data Storage and processing Source Systems Data Ingestion Data Management Analytics & Visualization Core Sources Device DataData Ingestion Databricks Data PipelineRaw Layer Curated Layer GCP BigLake StoreGCP DevOps Real Time Load Initial Load & Delta Load Real Time Data Batch Google Data GovernanceOrchestration and Scheduling by Cloud DataFlow Google IOTCore Cloud Pub/Sub BigQueryData Warehouse Data Lake Analytical Sandbox & Model Management for Analytics as a ServiceData Studio Data ModelPredictive Maintenance Dashboards PII compliant Semantic Domain LayerData Labelling, Data Quality, Unstructured Data Parsing Cloud MonitoringGoogle GKE Snowflake Security implemented through IAMData Studio Synergizer DataScope Xenius (Synthetic Data)",, "Graviton: Powering modern da ta pla tforms",, "How does Graviton address challenges?Overview Challenging and time consuming processes for development and implementation of modern data platform. Graviton provides independent plug and play accelerators and enables faster implementation of modern data platform using polyglot data technologies, open-source data frameworks and cloud native services. Complex data product development process and limited collaboration between different stakeholders involved in data product development.Graviton enables a holistic platform for collaboration between different stakeholders (analysts, data engineers and business users) by providing a collaboration workspace for data product creation and management with easy and customizable workflows for different team members. Lack of intelligent tools that can be used by data scientists and data engineers to solve any data-related issues.Graviton provides a suite of data services and utilities for data quality, anomaly detection, synthetic data generation, differential privacy, data labeling, semantic domain layer over data lake and intelligent log parsing to be utilized by data engineering teams as per need. Limited observability and monitoring capabilities for data pipelines resulting in delayed issue identification and negative impact on delivery of data products.Graviton provides a single data observability control pane to monitor various data pipelines and enables Data Ops engineers to track and diagnose issues related to data, pipelines and services which might affect the smooth and timely delivery of data products. Challenges Advantages with GravitonOrganizations need to accelerate data resilience, increase revenues and enhance customer experience. Having a modern data platform allows organizations to achieve the above goals, adapt to new technologies quickly and respond to market needs while reducing the total cost of ownership (TCO) and maximizing return on investment (ROI). Graviton helps enterprises accelerate modern data",, "platform implementation and enables organizations to efficiently build, deploy, monitor and maintain an agile and cost-efficient modern data platform. Graviton provides a collaboration workspace, centralized control pane, intelligent data services and integrates with hyperscalers (Azure, AWS, GCP), HCLTech IPs (AION) and OSS (Apache, Linux Foundation) to facilitate development and delivery of optimal data products and efficient management of data product life cycle from development to production.",, "This is a cloud-agnostic view of a modern data platform implemented using Graviton and open-source data frameworks and services .Similar architectures can be built using Graviton with AWS/GCP/Azure data frameworks and services instead of open-source technologies Xenius – Data Services explained: 1. Representative Synthetic Data Generation – Synthetic data that is representative and maintains the same characteristics as t he source dataset 2. Differentially Private Synthetic Data – Synthetic data that ensures individual level PII information is not leaked from the generated data 3. Structured Data Generation using AI-Regex Engine – Conversion of unstructured, textual data (e.g., device logs) into structu red format 4. PII-compliant Semantic Domain Layer over Data Lake – Create domain objects to query data from data lakes and apply additional security and access-controls based on user-persona and permissions to safeguard sensitive data 5. AI-assisted Data Labeling – Use ML to label massive datasets within minutes and increase usability of data for downstream consumption 6. Multi-dimensional Data Quality Assurance – Comprehensive data quality assessment across six dimensions of data quality (accuracy, completeness, consistency, precision, uniqueness and validity) with data quality trends and cost of quality dashboar ds 7. AI-based Anomaly Detection – Single and multi-variate anomaly detection on both time series and non-timeseries datasets 8. Data Publishing to Cloud Streaming Services - Directly stream synthetic data into cloud via Event Hub, IOT Hub or Kinesis, a nd use it to simulate real-time data for different downstream use casesPLATFORM OPERATORSDP Admin Data Engineer Data Ops Enabling FrameworksPlatform Output Data Products Core Cloud ServicesDataScope (Collaboration Workspace) Xenius (Data Services) Synergizer (Platform Observability)Data Ingestion (Airbyte, NiFi) Data Tran sformation (Apache Sp ark, Flink) Data Orch estration Data Governa nce (Apache Atlas, CKAN) Data Obser vability",, "(Apache Atlas, CKAN) Data Obser vability (Grafana, Prometheus) Platform Orchest ration (Terraform, Helm)Cloud Resou rce Provision ingRole based Data WorkflowData Pro duct ManagementFinOps DashboardCentralized ConfigurationSelf-Service BI Dashboard Represen tative Synthetic Data Gene rationAI Ass isted Data Labelling for Structured DataPII Compliant Semantic Domain Layer on Data LakeStructured Data Gene ration us ing AI-Regex EngineDifferentially Private Synthetic Data Gene ration Data Publishing to Cloud Streaming Servi cesData Mi nimization and Masked Data Containerizat ionData Secu rity Audit and Vulnera bility Asse ssmentData Profili ng & AI based Anomaly DetectionMulti-Dimensio nal Data Qua lity Assura nce Pipeline ObservabilityData Governa nceDataOps Control CenterManagementData Lineage Track ingAffected Schema Track ingDownstream Frameworks and Users: Data Scientist Business UserAI/ ML Platform (HCLTech AION) & BI (Apache Superset)Components and Reference Architecture for the Modern Data Platform – Powered by Graviton Cloud ComputeCloud Data LakeCloud Data Wareho use Available in Latest Version",, "hcltech.com HCL Tech is a gl obal technol ogy compan y, home to 222, 000+ peopl e acr oss 60 coun tries, deliv ering industry-l eading capabilities cen tered ar ound Digital , software. The compan y gener ated consolida ted revenues as o f $12.3 billion o ver the 12 mon ths ended D ecember 2022. To learn ho w we can super char ge pr ogress for you, visit hcl tech. com.Supercharge your data to accelerate business transformation Contact: digitalengg@hcl.comBusiness Benefits Faster time-to-market Enabling accelerated data platform modernization with independent plug and play components managing repetitive data engineering tasks by using a host of intelligent data servicesEfficiency Improvement Seamless collaboration between cross-functional stakeholders allows for an increase in the efficiency of data product development processHCLTech Graviton Differentiators Combined power of HCLTech IPs (AION), hyperscalers and OSS (Apache, Linux) capabilitiesIndependent plug and play components which can be customized as per user needsA holistic platform for different persona across the enterprise - both technical and business Capability to handle different types of data issues using a host of built-in data servicesAbility to create different zones in data fabric and leverage different storage technologies resulting in polyglot persistence",, "Graviton enables implementation ofModern Data Platform using polyglot data technologies, open -source data frameworks and cloud -native data services .Itfacilitates development and delivery ofoptimal data products and efficient management ofdata product lifecycle from development toproduction . Graviton provides a collaboration workspace, data observability control pane, data services and integrates with Hyper - scalers (Azure, AWS, GCP), HCL IPs (AION), OSS (Apache, Linux Foundation) to efficiently build, deploy, monitor and maintain an agile and cost-efficient modern data platform. Graviton – Powering Modern Data Platform 1",, "Copyright © 2022 HCL Technologies | Confidential Competitive Analysis",, "2Competitive Analysis with System Integrators                                         ",, "3Competitive Analysis with Niche Player s                      Data Observability                Synthetic Data Generation",, "4Competitive Analysis with Niche Players                     Data Quality            Automated Data Labelling",, "Electronic Device Automation Testing ( eDAT ) Product datasheet eDAT is a modular, scalable, extendable and highly customizable framework for automated testing of electronic devices . It enables test automation using a black box approach through hardware and software interface accelerators . Key Highlights • Typically, 30% of effort and cost of ownership saving compared to existing solutions • High coverage (typically 50 - 60%) even in regulated industries (like medical) meeting compliance parameters • Ease of adoption without mandatory knowledge of programming • Faster GTM • Optimal ROI - One eDAT set- up can test multiple DUTs • Easy integration with legacy and new test infrastructuresSalient Features • Video testing which checks for frozen frames, black frames, distorted frames, unrelated frames and dropped frames. • Vision based testing using device under test (DUT) camera or HCLTech proprietary FPGA -based hardware. • Speech simulation and playback testing, alarm and audio testing. • Wired and wireless interface e.g., serial, USB, ethernet, WiFi , bluetooth , ZigBee, etc. • Keyboard (Multilingual) and mouse simulation which can test without installing any software. • Touch screen simulation using software and robotic ARM for capacitive and resistive types of touch screen displays. • Remote testing for testing devices from on -site & off-shore locations • Vertical specific CAN(Auto) and ARINC(Aero) protocols. • Customizable report generation in any format like Word, Excel, XML, etc. with objective evidence.",, "Technical Requirements Third -Party Tools Component Requirement Processor 32-bit/64 -bit processor; Intel Core i3 or higher Physical RAM 4GB RAM minimum Operating SystemWindows 7 (32 -bit/ 64 -bit) or above with .Net framework 4.5 External Card Asus nVidia 1GB DDR3 graphics card (for image - based testing) Network / Access RequirementThe system should have admin access and USB access to communicate with the device under test if required.T est Management Defect Management Source Code Management Automation T est T ool Engines Product Functional Architecture",, "HCLTech is a global technology company, home to 222,900+ people across 60 countries, delivering industry -leading capabilities centered around digital, engineering and cloud, powered by a broad portfolio of technology services and products. We work with clients across all major verticals, providing industry solutions for Financial Services, Manufacturing, Life Sciences and Healthcare, Technology and Services, Telecom and Media, Retail and CPG, and Public Services. Consolidated revenues as of 12 months ending March 2023 totaled $12.6 billion. To learn how we can supercharge progress for you, visit hcltech.com.",, "HCLTech eDAT is a modular, scalable, extendable and highly customizable framework for automated testing of electronic devices. It enables test automation using the black-box approach through hardware and software inte/r_f.ligaace accelerators. * Script execution in Test Application Tool decides when to communicate with DUT/Application/eDAT and also similar for responsesElectronic Device Automation Testing (eDAT) Business challenges addressed eDAT architectureInefficient manual simulation of analog and digital signals 1Difficulty in suppo/r_t.ligaing domain-specific protocol level simulation during manual testing2Inconsistent streaming quality and issues with playback resulting in end-user frustration and lower adoption rate 3 Inaccurate testing of many test cases related to user experience due to time to market constraint4High-risk of device failure and rework due to manual inspection in assembly line processes5Inefficiencies in monotonous manual testing for multiple languages, devices and versions 6 Huge maintenance effo/r_t.liga on changing device resolution or UI element as a result of image reference-based testing7 PC Environment SRS in Pseudo Format Inputs for ScriptPC EnvironmentXUT XML HCLTech eDAT HardwarePC Application Software HCLTech eDAT Libraries HCLTech COTS HCLTech + COTS DUTApplication Test Tool E.g.: QTP, Test Complete, Python, PowerShell HCLTech eDAT Configuration ToolATSG User Input System ConfigurationInput Simulation and Output Verification*",, "hcltech.com• Automated test script generation (ATSG) • Input simulation testing • GUI testing • Touch screen testing • Interfaces supported–BT, USB, Wi-Fi, Ethernet, Controller Area Network (CAN) • Audio and video testing • Vision-based testing • Imaging algorithms • OCR–Optical character recognition • Robotic arm-based non-intrusive testing • Multi-platform testing • Remote testing • Programmable Power Supply (PPS), Digital Multimeter (DMM), Digital Oscillascope (DSO), RelayKey Features Proof Points Why HCLTech eDAT? Delivers high coverage (~50 - 60 percent) while faster time to market Reduces testing costs, time-to-market and defect leakage Fits enterprises’ specific environment and test requirements leveraging customizationsEnsures optimal return on investment as one eDAT setup suppo/r_t.ligas multiple devices under test (DUTs) Offers objective testing evidence in repo/r_t.ligas • All possible ways (20) to launch a game via a leading gaming console system were targeted for automation. • Automated three di/f_f.ligaerent categories—game play, test case and launch scenarios. • The team has moved from 0 to 100 percent test automation for a set of games, freeing up resources to focus on the launch of different set of games. • Testing of online video app for leading ISV. • Leveraged image comparison to capture text from display images for testing. • Reduced testing costs by 36 percent and testing cycle times by 57 percent. • Automated testing of shower control unit for a leading French aerospace company. • Simulated shower control inputs for testing. • Reduced testing costs by 47 percent and testing cycle time by 68 percent.Pinpoints defects, thereby allowing faster troubleshooting Sample eDAT setup screenshots",, HCLTech eDAT | CASE STUDIES 1,, HCLTech eDAT | CASE STUDIES 2,, "3 HCLTech eDAT | CASE STUDIEST h e C l i e n t The client isheadquartered inCalifornia, USA and isafortune 50online major .ItisaLeaders inmultiple internet related services and products which include online advertising, mobile & cloud computing, software, search etc.with aglobal presence with aworldwide customer base and offices spread across 40+countries .Theclient hasadedicated supporting pre-production and livetesting ofone oftheworld’s largest video sharing platform . N e e d s &c h a l l e n g e s f a c e d •High testing complexity with continuous daily tests ofmultiple application versions, regression cycle &test cases with ashort test window of40hours forend-to-endtesting . •Managing ateam oftesters spread across multiple environments :Mobile devices ,Desktops ,major browsers ,Settopboxes ,Gaming Consoles •Only manual testing exist, because ofwide variety ofdevices •Nostandard input methods fordevices likeInfra Red, RF ,Gesture, Joystick, etc •Lack ofeffective planning because ofunavailability ofhardware test automation tools with screen capture ability High cost ofautomating thehardware dependent test cases which requires physical interaction with thehardware HCL’S A p p r o a c h &S o l u t i o n HCL’s proposition ofeDA T has customizations forphysical interaction with theDevice under test, which simplified theautomation process .ItisModular, Scalable, Extendable and Highly Customizable framework forautomated testing ofelectronic devices .Itenables test automation using black boxapproach through hardware and software interface accelerators . Aspart ofeDA T services deployment, HCL : •DidanAs-isprocess analysis toidentify automatable test cases forshrinking thetest cycle time andimproving productivity •Didanalysis ofcommon configuration forvarious input methods Device abstraction layer fordevices •Simple scripting engine •Common approach forvarious devices",, "4 HCLTech eDAT | CASE STUDIESImpa c t ofeDAT 5%Re l e a s e Re v i e w25% Im p l e m e n t5% 20% Re q u i r e m e n t Te s t 30% 15% De s i g n houtWit eDA T Regression Cycle Testing time 30% Regression Cycle Project Timeline d e s i g n im p le m e n t t e s t r e q u i r e m e n t r e l e a s e r e v i e wTesting time 3%40hours oftesting which constitute 30% of SDLC without eDAT is reduced to4hours oftesting with eDAT which is90%saving intesting timeC u s t o m e r b e n ef it s •Thecustomer achieved 90percent reduction intest cycle time per regression cycle •Acommon framework forwide range ofdevices wascreated. •New devices canbeadded withminimal/negligible effort. •Reduces dependencies on human skillset. Toknow more,Contact usat ersslus@hcl.com",, "HCLTech eDAT | CASE STUDIES 5 HCL’sELECTRONICDEVICE AUTOMATION TESTING (EDAT) H EL P S LEADING MEDICAL COMPANYR E D U C E TESTING TIME BYO N E -FO URTH",, "6 HCLTech eDAT | CASE STUDIESTHECLIENT Theclient isoneoftheleading American health care company .Thecompany primarily focuses onInfusion pumps andproducts totreat people with hemophilia, dialysis, immune disorders and other chronic andacute medical conditions . BUSIN ESSOBJECTIVE Client faced thefollowing challenges while dealing with testing oftheir Infusion Pump ; •Manual testing takes longer time forGTM •Multi -lingual testing HCL’sSOLUTION HCL proposition ofelectronic device automation testing (eDAT) hascustomizations forphysical interaction with theDevice under test, which simplified theautomation process .ItisModular, Scalable, Extendable and Highly Customizable framework forautomated testing ofelectronic devices .Itenables testautomation using black boxapproach through hardware andsoftware interface accelerators . HCL’sAPPROACH AspartofeDAT services deployment, HCL didanas-isprocess analysis toidentify automatable testcases forshrinking thetestcycle time andimproving productivity . •Deploying eDAT hasthefollowing benefits/features ; –Reusable Digital and analog accelerator forinput, output –Image comparison algorithm for oneresolution andtolerances –Audio capture foralarm andalerts",, "7 HCLTech eDAT | CASE STUDIES•Functionalities Covered : –Keypress using thedigital ports –Different Battery Conditions using serial ports –Sensor simulation forDownstream Occlusion using analog ports –Alarms capture using analog ports –Image capture using UDP Ethernet •Verification Done for: –Screen capture using image grabber forUIverification –Sound capture foralarm verification eDATPC Scripting Image Verification module Reportin gmoduleSound verification Module Digital/Analog moduleCommunication module Analog, Digital Inputs /OutputsKey Press / Sensor simulationUSB /RS232EthernetFPGA Board TFT Output USBBuzzer OutputInfusion Pump DAQ DAQ CUSTOMERBENEFIT •Automated 6software testprocedures •88% oftestscenario were covered •Reduces the testexecution time to1/4when compared tomanual efforts Toknow more,Contact usat ersslus@hcl.com",, "HCLTech eDAT | CASE STUDIES 8 HCL’S E L E C T R O N I C D E V I C E AUTOMATION T EST IN G (eDAT ) H E L P S L E A D I N G J A PA N E S E AUTO A C C E S S O R I E S MAKER A C H I E V E 90%R E D U C T I O N INT EST IN G TIME .",, "9 HCLTech eDAT | CASE STUDIESTheClient Aleading Japanese company involved insales and manufacturing ofInstrument clusters forautomobiles, motorcycles and other applications likeoffice automation appliances, remote controllers, LCD, OLED . Business Objective Client faced thefollowing challenges while dealing withtesting oftheir Head -UpDisplay (HUD) screens : •Outsourcing tomultiple vendors fordifferent platforms wasacumbersome process •Each vendor wasusing itsown platform forHUD testing •Little tonoautomation wasbeing followed byvendors eDAT HCL’s eDAT ismodular, scalable, extendable andhighly customizable framework forautomated testing ofelectronic/embedded devices .Itenables testautomation using black boxapproach through hardware and software interface accelerators .eDAT provides support forawide variety ofInterfaces andinput simulation for physical interaction withdevice under test, which simplifies theautomation process . HCL’s Approach &solution Aspart ofeDAT services deployment, HCL didanAs-isprocess analysis toidentify automatable testcases forshrinking thetestcycle time andimproving productivity . Deploying eDAT involved thefollowing steps : •Instrument Cluster /HUD Screen validation bycapturing thescreen image inspymode withHCL devel -oped FPGA Parallel RGB/ RSDS frame grabber . •Solution based ontheeDAT platform, used forautomated testing ofembedded devices withinputs from Ethernet andCAN. •DRGB /RSDS image capture byXilinx FPGA andTransfer ofimage toPCthrough theEthernet interface .Image data captured from theLCD controller through thespymode . •Pixel byPixel comparison ofthecaptured data with theexpected value usingHCL’s Image processing library . •eDAT enables automated GUITesting using QTP testscripts . •Automatic Execution ofCANoe T estconfiguration scenarios using QTP scripts Automated report generation reducing themanual errors inreporting process",, "10 HCLTech eDAT | CASE STUDIESCustomer Benefit •90% reduction intestcycle time wasachieved. •eDAT provides device abstraction layer which makes thesame setup applicable withminimum modifica tionfor8different product lines inwhich thecustomer showed interest.Interfacing with the FPGA hardware image reconstruction scripting and testingSending commands to FPGA board for image capture Image comparison SLU Adaptor AdaptorAutomation of testcases Automation of testcases Toknow more,Contact usat ersslus@hcl.com",, HCLTech eDAT | CASE STUDIES 11,, "12 HCLTech eDAT | CASE STUDIESTHE CLIENT PROFILE Aleading French aerospace group supplying systems andequipment foraircraft . EXISTING BUSINESS CHALLENGES Theclient was manufacturing shower control units (SCU) forprivate flights .Since theSCUs were manually tested, itwas aprotracted and cost- intensive process .Moreover, there was aneed tomaintain different test environments foradiverse range ofproducts .Test automation was, therefore ,anessential requisite . HCL’S METHODOLOGY &SOLUTION HCL’s test automation services implemented electronic device automation testing (eDATTM),which has amodular, scalable, extendable, and customizable framework .Itsimplifies theprocess byallowing physical interaction customization during thetest.Additionally, eDATTMfacilitates test automation viatheblack boxapproach –through hardware andsoftware interface accelerators . Apart from electronic device automation testing, HCL also performed anas-isprocess analysis toidentify automatable testcases forreducing test cycle time and improving productivity .The above frame work ,including thetest automation capabilities significantly changed the process landscape .",, "13 HCLTech eDAT | CASE STUDIESUSB USB eDATTMPC SCUSerialCommunication CANInterfaceDigitalI/OInterface CANHWScriptingDigital I/O Module Communicati on ModuleReporting Module DUT BENEFITS DELIVERED HCL’s test automation services had several transformative impacts .The deployment ofeDATTMhelped insimulating control signals tovalves and switches toenable theprogramming pins.eDATTMalso facilitated sending commands and receiving messages through serial interfaces and delivering messages over CAN bus. Theeffective implementation ofeDATTMreduced testcycle time by80%perregression cycle andprovided more than 85%coverage during test automation .eDATTMaltered theparadigm forthecustomer, simplifying thetesting environment . Toknow more,Contact usat ersslus@hcl.com",, Copyright © 2022 HCL Technologies Ltd. | Confidential,, HCLTech eDAT | OVERVIEW 1,, "2 HCLTech eDAT | OVERVIEWThe accompanying material and any related oral orwritten discussion (the “Materials”) isgoverned bythe limitations detailed below : Licensed Content and Ownership –HCLTech eDAT and other product names are ormay beregistered trademarks and/or trademarks inthe U.S.and/or other countries .Content distributed within aHCL client organization must display HCL copyright notices and attributions ofauthorship . IP&Patent Liability -This HCLTech eDAT iscovered byone ormore ofthefollowing patents : US20140095931 A1,US20150378878 A1,US9646205 B2,Other U.S.and international patents pending .Any refactoring or subsequent re-useisanunlicensed useand therefore constitutes patent infringement .Ifthere isany further detailed information required, please contact ersslus@hcl .com Liability Disclaimer -The information herein isforinformational purposes only and represents thecurrent view ofHCL Technologies Ltdasofthedate ofthis presentation .Because HCL must respond tochanging market conditions, itshould not beinterpreted to beacommitment onthepart ofHCL, and HCL cannot guarantee theaccuracy ofany information provided after thedate ofthis presentation .HCL MAKES NOWARRANTIES, EXPRESS, IMPLIED ORSTA TUTORY , ASTOTHE INFORMATION INTHIS PRESENTATION .",, "3 HCLTech eDAT | OVERVIEW➢Automated Test environment notavailable ➢Manual testing is laborious ➢Increased Effort, resource and cost investment ➢Skilled Resources ➢Test Setup Availability ➢Human errors, inconsistency ➢Test coverage, Defect leakage, Report Generation, Bug Fixing, Regression Testing",, "4 HCLTech eDAT | OVERVIEWHCLTech eDAT is a Modular, Scalable, Extendable and Highly Customizable framework for automated testing of electronic devices. It enables test automation using black box approach through hardware and software interface accelerators. HCLTech eDAT Architecture",, "5 HCLTech eDAT | OVERVIEW Requireme nts Story Line Creation Automated T est Case SelectionAutomated Functional/ Regression/ Integration/ TestingReport Generation Defect Management System Test Configuration T est Bank /T est Configuration Management System Automated T est Script Generation Development T eam Upload New Build Optimal T est Case Selection New Build /Regression Process",, "6 HCLTech eDAT | OVERVIEW SOFTWARE BASED APPROACH HARDWARE BASED APPROACH NON -INVASIVE BASED APPROACH MODULAR APPROACH",, "7 HCLTech eDAT | OVERVIEW HCL Optimus SmarTest is an Analytics -based Automation platform enabling end -to-end automation of your product testing lifecycle. Integration with popular ALM, CI tools, test engines and test/defect mgmt. tools Analytics -based test case recommendations and defect fixing ONE -STOP AUTOMATIONANALYTICS - BASED TESTING Jenkins/Hudson Import / Create Execute Defect ReportBuild Package DeployCheck -in Trigger CI System Trigger Test Test Management system Test / Defect Management system Platform -agnostic Keyword -based test stories enable faster test creationAUTO TEST SCRIPT GENERATION Reports in multiple formats, auto -defect logging into DMSAUTO - REPORTING & DEFECT LOGGING HIL Test Execution Engines ECUVirtual ECU Other Sensor s",, "8 HCLTech eDAT | OVERVIEWWindows PC Screen calibrationObject Detection ModuleImage Capture CommunicationOCR ModuleScript Robot Functions Linux box Simulation Hardware InterfaceRobotRobot functionsCommunication Robot DriverReport GenerationVision camera ROS Computer Vision (e -DAT) Robotics ( RoboOps ) Inverse Kinematics Robot Joint Control",, "9 HCLTech eDAT | OVERVIEW",, "10 HCLTech eDAT | OVERVIEW",, "11 HCLTech eDAT | OVERVIEWHighlights •Proactive automation initiatives otherwise deemed impossible by HCL through POC demo at each stage. •Reliable and speedy results attracted automation in other pockets (Launch scenarios and Functional TCs) •Competing vendors still using manual process to validate builds while HCL is using automation to sign off daily builds 60 Functional Test Case100 Launch scenarios50 Games Play 3 builds2 Months 8 Month 11 month 6*198 hours effort saving25k cost saving pm Automation not feasible POC Game Play A POC was done to automate 50 Games using HCL’s eDAT framework which use to launch a game and stay in the game for more than 10 minutes. Automation not feasibleMore Automation Automation was further introduced in the system and all possible ways (20) to launch a game was targeted for automation 100 % Automation Manual Validation Sign-off on Daily builds was purely manual and time consuming. Bug escapes common due to insufficient coverage. POC extended Automation was extended to target manual TC’s for functional flows. Automation & manual validation was done to provide sign of on daily buildsAfter automating 3 different categories Game Play, Test Case and Launch scenarios automation the team has moved from 0% Automation to100 % Automation100% Automation",, "12 HCLTech eDAT | OVERVIEW•Plug-insforvariousCOTStools •Solution already integrated with Dspace, QTP , Test Complete, AutoIT , etc. •Plug -ins can becreated tosupport new toolsLegacy and New infrastructure integration •Defined workflow from Requirements Generation toAutomation Testing •One-time Configuration, Automation Scripting, Automation Testing, Report GenerationMethodology •Objective evidence of thetests intheforms ofcustomized reports •Reports available in.doc, .excel, .csv, .html, .pdf formats (can beextended)Customized Reporting •One time Configuration, Very small training phase required, Basic scripting support •GUI driven testing approach; nomandatory scripting required •Not tiedto anyConfiguration toolsEasy toadopt •eDAT canprovide end toend solution forautomation • eDAT can seamlessly integrate with open source tools for end to end solutions (TestLink, Bugzilla, SVN, AutoIT)Customers new for Automation",, Copyright © 2022 HCL Technologies Ltd. | Confidential,, HCLTech eDAT | PRODUCT ROADMAP 1,, "2 OND’22Consumer Electronics/ Medical/Auto •Compatibility Testing (Microsoft) -Demo •Verification of multi channel audio capture feature – integration •eDAT Integration of STT/TTS •Realware Demo –Microsoft •Record & Playback -Microsoft •Localization –Multi -lingual support –REST API support POC •eDAT as service for partners •Urine chemical analyzer testing POC -Siemens •ATSG –POCs ---MCDC and OpenAI tool integration •IMA for Cargo -ANCRAJAS’22Consumer Electronics/Auto •4K video recording testing, Multi channel audio capture feature, Integration of video quality analysis •Display verification – Image processing •Compatibility Testing (Microsoft) -POC •STT/TTS feature analysis •STT/TTS tool identification for integration •ATSG–POCs ---MCDC tool integrationAMJ’22Consumer Electronics/Auto/ Aero Long Term Plan FY24 •Device virtualization – FPAT enhancement •3D image comparison •Cloud gaming testing •MR device testing •Metaverse enhancements •Synthetic code generation –Text case/Test script generation •GPS simulation •LVDS integrationJFM’23 •Record & Playback -Microsoft •MEND analysis •ATSG.ai -enhancement •IMA for Cargo –ANCRA - Deployment •SPI interface development for automotive -Requirement analysis •Localization –Multi -lingual support –REST API support POC •eDAT as service for partners •POS machine testing -POC •Visual servoing(tracking) -POC Consumer Electronics/ Medical/Auto •4Kvideo recording and Multi channel audio capture feature implementation •Test cases preparation for 4kvideo recording, multi channel audio capture, and video quality analysis(pixelation and blurriness) •XR application automation testing –user journey mapping •ATSG Python integration •HUD verification •Front Panel automation – simulation POC HCLTech eDAT | PRODUCT ROADMAP",, Copyright © 2022 HCL Technologies Ltd. | Confidential,, HCLTech eDAT | 1 -SLIDER 1,, "2 HCLTech eDAT | 1 -SLIDERHCLTech eDAT is a Modular, Scalable, Extendable and Highly Customizable framework for automated testing of electronic devices. It enables test automation using black box approach through hardware and software interface accelerators. HCLTech eDAT Architecture",, Copyright © 2022 HCL Technologies Ltd. | Confidential,, "Copyright © 2023 HCL Technologies Ltd. | Confidential • •",, Copyright © 2023 HCL Technologies Ltd. | Confidential,, Copyright © 2023 HCL Technologies Ltd. | Confidential,, "Copyright © 2023 HCL Technologies Ltd. | Confidential • • • • •",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • • • • • • • • • •",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • •",, HCLTech eDAT | COMPETITIVE ANALYSIS 1,, "2 HCLTech eDAT | COMPETITIVE ANALYSISFeatures HCL TATA ELXSI Falconeye Accenture Stormtest Witbe HARMAN Eggplant Allion Video Testing Yes Yes (AI Based) Yes Yes No No Yes Audio Testing Yes No Yes Yes No No Yes Image Comparison Yes Yes Yes Yes No Yes Yes 4K Support Yes Yes No No No No No Vision Based Testing Yes No No No No Yes No Robotics Yes No No Yes No Yes No Digital/Analog signal simulation Yes No No No Yes No Yes IR Emulation Yes Yes No No No No No OCR Yes Yes Yes No No Yes Yes GUI testing Yes Yes Yes No Yes Yes Yes Input Simulation Yes No No Yes Yes Yes Yes Virtual Assistant Testing(STT/TTS) Yes No No No No No Yes ATSG Yes Yes No No No No Yes Multi -screen/Multi -device Testing Yes Yes Yes Yes No No No Remote Testing Yes Yes No Yes No Yes No Compatibility Testing Yes No No No Yes Yes No Lab Automation Yes No No No Yes No Yes Ethernet Yes No No No Yes No Yes CAN/CANTP/CANFD Yes No No No No Yes No ARINC/AFDX Yes No No No No No No URLElectronic Device Automation Testing Framework (eDAT) | HCLTechTata Elxsi -FalconeyeStorm Test: Development Center | AccentureWitbeHARMAN Connected Car Technology for Better Automotive ExperienceEggplant Software | Test Automation SolutionAIoT Expert | IoT Test Solution Provider | Allion Labs",, "3 HCLTech eDAT | COMPETITIVE ANALYSIS• Single setup formultiple DUTs • Black -box/Non -invasive testing • Robotics and Computer Vision integration • Multi -lingual support • Audio/Video testing–4Kvideo testing • Reporting with objective evidence • Customizable framework • Wider applicabilityS O W TStrengths • Medical device testing–US$ 11.8bnby2025 ,CAGR 4.8% • HUD market–US$6.4bnby2027 , CAGR 21.3% • Broadcast and media technology –US$62.12bnby2027 ,CAGR 6.9% • Gaming industry–US$504.29bn by2030 ,CAGR 10.2%Opportunity • Small tonegligible ROI forlower number ofregression cycle • Higher Cost ofQuality (CoQ )Weakness • Players entering the market with ready -to-use products for narrow/niche applicabilityThreats",, Copyright © 2022 HCL Technologies Ltd. | Confidential,, HCLTech eDAT | 2 -SLIDERS 1,, "2 HCLTech eDAT | 2 -SLIDERSHCLTech eDAT is a Modular, Scalable, Extendable and Highly Customizable framework for automated testing of electronic devices. It enables test automation using black box approach through hardware and software interface accelerators. HCLTech eDAT Architecture",, "3 HCLTech eDAT | 2 -SLIDERS❖Inconsistent streaming quality and issues with playback results in end user frustration and lower adoption rate❖Frozen frame detection, Blur and pixelation identification with precise report generation, audio pattern match, volume change detection❖Optimal ROI -One eDAT set -up can test multiple DUTs ❖Many test cases related to user experience cannot be accurately tested because of time -to market constraint❖Input simulation, Automated test script generation, Robotic arm, Computer vision❖Up to 30% of lower effort and higher saving compared to existing solutions ❖Manual inspection in assembly line processes poses high risk of device failure and rework due to human errors❖Robotic arm with computer vision and collision detection ❖High coverage (up to 50 -60%) even in regulated industries( E.g. –Medical) meeting compliance parameters ❖Monotonous manual testing for multiple Languages/Devices/Versions is inefficient❖Input simulation, Keyboard/Mouse support and simulation, Multi - lingual support❖Use of simulator can parallelize the process -~25% reduction in deployment time ❖Image reference -based testing leads to huge maintenance effort onchanging device resolution or UI element❖Image capture, Verification without image reference, ML/DL based image verification, Computer vision❖>67% of reusable components ❖Manual simulation of analog and digital signals is inefficient ❖Support for simulation of signals as per the product requirements using H/W COTS tools❖All types of signal simulation leads to higher testing coverage related amplitude and timing requirementsPositioning Statement For the quality control manager of a medical/automotive/aero/consumer -electronics device manufacturer who struggles with lower a doption rate, the Embedded Device Automation Testing Solution provides higher coverage of test cases and faster GTM through a Modular, Scalable, Extendable and Highly Customizable framework for automated testing of",, "electronic devices . Unlike other competitive market products, eDAT enables test automation using black box approach through hardware and software interface accelerators. Customer Challenges Business Benefits HCL’s Optimus -eDAT Offerings Differentiators Success StoriesRobotics, Computer Vision, and OCR integration Black box approach to testing Reporting with objective evidence • Point of care device in healthcare system -Single setup to test multiple language GUI -85% UI string coverage through HCLTech eDAT • Embedded software in healthcare for infusing medicine/liquid -75% Reduction in the test execution time when compared to manual efforts and 88% of test scenarios were coveredDevice Abstraction –Enables testing multiple DUTs",, Copyright © 2022 HCL Technologies Ltd. | Confidential,, "Copyright © 2022 HCL Technologies | ConfidentialCloud Bridge Suite Case Studies",, "2Reference Case Studies •Modernization of a Monolith MES Application of Major multinational conglomerate corporation to improve scalability •Technologies: C#, ASP.Net MVC, .Net Framework 4.6.1, Entity Framework, Microsoft SQL Server •45% Effort savings in identify the critical feature, prioritize and planning •Accelerate planning & design phase . Problem Statement Approach & Solution Benefits •Perform Sizing and deep analysis of the system and get insights on code complexity, tech stack •Identify the critical feature and recommend to extract the associated code base and dependencies to create the potential m/s •Prioritize the transformation in strangler pattern based on business criticality and service autonomicity /dependency•Modernization of Monolith toll plaza management system to cloud and edge model •Due to tightly coupled architecture and huge data size, not able to meet the performance requirements •Tech stack: J2EE & C++, Oracle •30% reduction in As -is system Understanding and accelerate planning & design phase. •15% acceleration in microservice baseline code generation •Acceleration in dockerization and cloud deployment•Get insights on code complexity, tech stack nativity and performance bottlenecks of reference system using CB Analyzer •Generate Boiler plate code for the target microservices from specification using CB ACE Micro •Easy workload deployment based on IaCusing CB iStudioCase Study 1 Case Study 2",, "Case Studies •HCLTech designed and developed a cloud native global digital experience platform integrating discrete business functions into a unified solution Value Delivered •Supports 500k concurrent users with 1.5 M page views/second , Near Real time match -day updates, Integrations of 17 COTS platforms including Sitecore •Highly Engaging, Analytics Driven Responsive Web Experience and 4.8 Rated Mobile App with over 5M downloads within week of launch •Large scale Agile/DevOps based Implementation with 2400+ User Stories for9000+ business requirements •Six Sigma Initiative to drive 35% Cloud Infra Optimization •360 monitoring across platform, infra and services integrating with Servicenow ;resulted 10% YoY drop in Operations cost •HCLTech has also hosted platform on GCP & is taken to market across various industries as a leading customer engagement solution•Customer’s business were facing challenges in meeting customer demands of being innovative and competitive at same time they realised the need of becoming agile and reducing the operational / hosting cost. Therefore, they decided to embrace public cloud infrastructure to migrate/transform •Assessment and Migration of 1300+ Servers & 185+ applications from 8 Datacentres to Public Cloud( Azure & GCP ). GCP for SAP, AI and ML based workloads •50% Assessment automated via HCLTech Advantage Upgrade •Faster time to market, greater predictability and repeatability resulted in substantial improvements to the key business •30-40% automation in application testing and 50-60% automation in data conversion and migration •Reduction in OPEX by leveraging PaaS model •Reduced Resource Optimization, Increased Operational Efficiency and Improved service delivery agility •Migration of critical business and customer facing applications•The client’s customers include leading restaurant chain brands (QSR) of the world. •Developed platform for leading Kitchen Equipment Manufacturer which enables remote monitoring and",, "Manufacturer which enables remote monitoring and operation of the kitchen equipment across the globe. Single interface for Franchise Owners, Managers, Chefs & Servicers. The platform enables management of Menu, Service, Quality, Asset, various reports and supports over the air updates •Developed a robust IoT platform for new generation of connected kitchens encompassing 12 product brands of the client which reduced field visits and downtime by 80% and 50% respectively •End-to-end ownership with HCLTech including device connectivity, gateway, edge, developing the cloud platform, data lake and analytics engine, mobile app, and web portal. •API Driven: Implemented API strategy to ensure seamless integration with all 3rd party systems within client’s IT environment as well as in the end -customers IT landscape Digital fan engagement platform for one of the most sought -after soccer clubLeading coffee and beverage company in North AmericaStrategic Partnership with Commercial Kitchen Equipment OEM 3",, "HCLTech Expertise in Cloud Native Digital Platform Development Advisory, Cloud Native Dev, DevOps and Cloud Ops Services to Support OEM’s Hybrid/Multi Cloud Initiatives Re-Built B2B Commerce Platform to Custom Microservices Architecture & Deployed on AWS CloudArchitecture Consulting, Containerization & Migration of ERP/SCM Products to Azure CloudContainerization of deep learning training platform & CI/CD Automation to enable faster releases and Kubernetes Implementation on GPU/CPU based HPC Cluster Cloud Native B2B Ordering Platform for Pivotal Cloud Foundry based Multi -Cloud deployment Modernizing B2C Commerce Platform to Cloud Native Microservices Architecture Deployed on GCPBuilt Digital Marketing Platform on Azure Cloud driving 500+ brand sites across globeRe-Built Cloud Native Global Fan Engagement Platform deployed on AWS and Tuned to service 650M + Fan Base Consultancy, Cloud Native Transformation of Telemetry Analytics & Automation Platform & implementation of cloud agnostic solutionCloud Native Remote Development Platform to develop, deploy, execute and test user workloads on a specific hardware clusterLargest Semiconductor Chip Manufacturer Leading global toy manufacturerAmerican multinational food, snack, and beverage corporation Leading US cosmetics companyLeading Provider of Broadband Communications Solutions Global Supply Chain Software VendorLeading Global Telecom OEM World’s leading soccer club Leading Telecommunications service providerLeading Semiconductor OEM B2C/B2B eCommerce platform & Business Strategy Consultancy & modernization of platform to support seamless omnichannel transactions, Deployed on GCP An American -Canadian multinational athletic apparel retailereCommerce Platform Consultancy and modernization of B2C technology platform on AWS Cloud enabling seamless customer experience and direct delivery capability across 40+ Markets International Cosmetics, skin care and personal care company 4",, "hcltech.comSample Customer Cases -Industrial Industrial TechIndustrial TechEnergy Tech Automation of IIoTapp deployment on cloudPartnership to design and develop Gas meter safety system features Modernization of Monolith MES to improve scalability technologies Scope & Pain point •Complex home grown Genix IoT based analytics(AL/ML) system deployment in heterogeneous environment. •Manual deployment process is lengthy and involve SME dependency Approach and Solutions •Took stock of all IOT -based analytics system deployment environments with dependencies •Enabled One -click deployment of Infra and Genix workload components with all dependencies resulted in 70% reduction in deployment effort Scope & Pain point •Huge homegrown monolith MES solution, hangs during peak load which affected their throughput. •Extract the critical component and convert to a microservice to address the scalability issue Approach and Solutions •Perform deep analysis and get insights on code complexity, tech stack, •Identify critical features and internal dependencies with associated code base to create potential m/s •Prioritize transformation in strangler pattern based on business criticality and service automaticity /dependencyScope & Pain point •Green field development of Intelligent Gas Meter safety System with Alarm & notification, Valve response and safety recommendation, Receive and store meter events. Approach and Solutions •Bootstrap the microservices development by automated code generation with built in cross -cutting support like messaging, logging, authentication, exception handling etc •Automate deployment blue -print for easy workload deployment across cloud and on-prime based on IaCprinciple IIoTApplication Monolith MES Application Gas Meter Safety System Wind Energy Tech Rearchitecting of App used in identification of new Renewable power plant sitesSite Assessment Application Scope & Pain point •Rearchitecting of a centralized application",, "•Rearchitecting of a centralized application which identify new sites for renewable energy power plants. •Deployed in containerized environment hosted in Microsoft Azure cloud services. Approach and Solutions •Perform deep insight and accelerate the planning of refactoring •Accelerate the development of secure REST APIs using .NET 6 and entity framework through LC solution •Automated Build & deploy application with Azure Kubernetes Service (AKS)",, "hcltech.comSample Customer Cases -Transportation Transport Auto Aero Modernization of Toll Plaza System as Cloud & Edge Rehosting and Re - Platforming of AppsRearchitecting of BOM applicationToll Management Systems BOM Application App Modernization Auto Device Predictive MaintenanceData Platform Scope & Pain point •Tightly coupled architecture, huge data size, Legacy and not scalable host system not able to meet the performance requirements •Modernization of Monolith Host system to IOT model for vertical scalability Approach and Solution •Get insights & performance bottlenecks of Host system •LC micro service generation for host services with built in cross -cutting supports •Automated deployment based on IaC principle Scope & Pain point •Performance and maintenance of BOM system •Thick clients with heavy dependency of local environments increases duplication and maintenance cost •Analyze environmental dependencies and reorganize and modernize BOM system Approach and Solution •Complete assessment for planning the modernization strategy. •Prioritize and plan the modernization journey based on the business continuityScope & Pain point •Migrate 150+ applications to Cloud –Azure •Optimized Wave planning balanced with best fit estimation •Migration implementation without affecting business continuity Approach and Solution •Questionnaire and tool -based assessment for defining the migration strategy and wave planningScope & Pain point •Automate Infra Provision using IaCand workload deployment Approach and Solution •IaCAutomation for Deployment in Azure/AWS/GCP/OpenStack •Vulnerability assessment for Kubernetes environment •Cloud cost optimization using CB Optics for AWS and Azure",, "hcltech.comSample Customer Cases -Medical MedTechHealthcare, RCPG, Cons umer Hi - Tech Single view of Customer 360Modernization of Preoperative Planning Application to Cloud Scope & Pain point •Modernization of Patient Care system to cloud •Complex system tightly bound to business function •Long lead time for release of new product features Approach and Solution •Assessment of as -is system using solution accelerators •Standardized microservice development with ACEmicro to reduce time to marketScope & Pain point •Moving Device functionality to cloud – accelerating data entry •Device occupied during Surgical Planning Approach and Solution •Boosting Device and Doctor Utilization by decoupling device and preoperative surgical planning •Enabling analytics and AI •Collaboration and sharing of insights between multiple practitionersScope & Pain point •Consolidate customer/prospect data from different sources/channels andcreate single view Approach and Solution •Customer 360 todrive the personalized experiences across consumer channels, marketing and customer servicePreoperative PlanningCustomer data platform Cloud native microservice development Patient Care System Scope •Enabling subscription -based model through cloud adoption •Usage tracking, consumables tracking & cybersecurity •Enabling Remote diagnosis and service from OEMsMedTechMedical Devices Enabling DaaS model through cloud adoptionDevice as a Service",, "Scope Approach / Solution Benefits / Results Delivered •Leverage Data Collection in toward safety alarms •Near Real -time action to mitigate safety threats •End-to-end tracking of Safety Events to Closure •Enhance Operational Excellence from product dataCase Study 1: Addition of new microservices related to gas meter service safety for a leading gas product manufacturer •15% acceleration in microservice baseline code generation •Acceleration in dockerization and cloud deployment•Bootstrap the microservices development by automated code generation with built in cross - cutting support like messaging, logging, authentication, exception handling etc •Deployment blue -print generation and Easy workload deployment across cloud and on - prime based on IaC principle",, "Scope Approach / Solution Benefits / Results Delivered •Develop fully functional front end using angular & docker •Develop secure REST APIs using .NET 6 and entity framework •Work on DevOps implementation on Azure cloud •Build & deploy application with Azure Kubernetes Service (AKS)Case Study 2: Re -architecting and modernizing an existing GIS application •15% acceleration in microservice baseline code generation •Acceleration in dockerization and cloud deployment•Accelerate planning and designing by understanding the reference system •Microservice development by automated code generation with standardized CI/CD pipeline and development process and built in cross -cutting support like messaging, logging, authentication, exception handling etc •Deployment blue -print generation and Easy workload deployment across cloud and on -prime based on IaC principle",, "Globally leading medical device company CASE STUDY 3: CLOUD NATIVE MICRO -SERVICE DEVELOPMENT FOR A MEDICAL DEVICE COMP ANY SCOPE / CHALLENGES / PAIN POINT APPROACH / SOLUTION BENEFITS / RESULTS DELIVERED TIME TO MARKET COST/ ROI •Modernize 15 years old monolith system •Improve performance of the system •Reduce cost associated with maintenance •Stay relevant and competitive •Ensure large number of services are available in seamless way ▪CB ACEMicro accelerated standards based automatic code generation for base microservices with improved code quality ▪Support of different design pattern, ensuring low code and making communication between microservices simple ▪Security -Basic OAuth support for service authorization ▪Microservices architecture deployed on Azure ▪Achieved interconnection between complex services for synchronized functioning and end to end tracing 3X Faster time to market VELOCITY QUALITY Significant improvement in business agilitySignificant reduction in initial learning curve for development teams42% Acceleration in microservice code generation",, "Scope Approach / Solution Benefits / Results Delivered •Roadside toll collection and management with Zone controller (The system detects and classifies vehicles, captures images according to business rules, and creates a complete transaction from the roadside sensors.) & Host System: The application has the capability to service one or more toll zones. •Requirement is to modernize the existing Monolith Host System to IOT model for meeting the requirement of vertical scalability and improve performance •Tech stack: J2EE & C++, OracleCase Study 4: Modernization of Monolith toll plaza management system to cloud and edge •30% reduction in as -is system understanding and accelerated modernization planning & design. •15% acceleration in microservice development with boiler plate automation •Deployment efficiency improved by 75%•Get insights on code complexity, tech stack nativity and performance bottlenecks of the reference system which is 1.6MLOC •Bootstrap the plaza management and utility microservices development by automated code generation with built -in cross -cutting support like messaging, logging, authentication, exception handling etc. •Automated design of deployment architecture and provisioning across Cloud and Plaza Edge using IaCwhich helped to add/remove/update new Tool Plaza edge. 11",, "Scope Approach / Solution Benefits / Results Delivered • Home -grown MES solution hangs during peak load which affected their throughput. •Extract the key component from a huge monolith MES application and convert to a microservice to address the scalability issue •Technologies: C#, ASP .Net MVC, .Net Framework 4.6.1, Entity Framework, Microsoft SQL ServerCase Study 5: Modernization of a Monolith MES Application Data points LOC 2M Assemblies: 16 Namespaces/Packages: 34 Controllers/Handlers: 97 User Defined Functions: 22532 Total APIs 2253 Stage 1 Discover all endpoints of the selected usecase /components and associated call flow and dependenciesStage 2 Analyze the deendancies of usecase components and identify the boundary and interfacesStage 3 Isolate component and and retain remaining as monolith, Interface redefinitionStage 4 •Containerize and deploy the new microservice and necessary load balancing architecture •45% Effort savings in the assessment phase to identify the critical feature, performance bottlenecks, better prioritizatio n and planning •Achieved scalability with elastic load balancing and m/s architecture •Improved throughput by enhancing scalability during peak loads 12Panasonic",, "Scope Approach / Solution Benefits / Results Delivered • Understand As -is process • Took stock of all IOT based analytics system deployment scripts and verification mechanism and enhanced automation or addressed open issues jointly. • Automated infra components of IoT based analytics systems like Micro k8, NFS, HA Proxy, WSo2, Vault in iStudio with require parameters and automated with Terraform • Took phased approach for automation. • Enabled One click deployment of IOT based analytics systems with easy for phase 1 and demonstrated value➢Build universal installer for Genix •Automate Genix deployment on On -Prem and Cloud •Run installer on client location without internet •Version upgrade and patch deploymentCase Study 6: Universal Installer for Leading Industrial company •Deploy components in 30 minutes, from 2 to 3 manual days •75% Acceleration in product platform setup •Reduction of errors and predictable deploymentAchieved End-to-End Automation of •Kubernetes: micro k8 with 3 VM, Load Balancer Server: HA proxy (1VM), Persistence Disk: NFS (1VM), Kubernetes Traffic Management: NgNix Ingress , Front End Component: One Genix UI (Platform UI) Component, One Backend Component: Genix Backend Partial automation with the manual process •Database : MongoDB , (1VM) and MS SQL (1VM) Installation, Authentication : LDAP, IAM : WSO2, Secret Store: Hashicorp vault 13ABB",, "CASE STUDY 7: DECOMPOSITION OF A MONOLITH TEST AUTOMATION APPLICATION Problem Statement Approach / Solution Benefits / Results Delivered • Discovered insights on code complexity, tech stack nativity and performance bottlenecks of reference system •Through dynamic data collection, extracted the code flow associated the key business services like product service, user service, test services etc. •Performed AI driven algorithm for identifying the cohesiveness between services and between services and data layer •Clustered the code base based on the business logic affinity in to multiple business services •Accelerated the target microservice creation cloud deployment though integrated containerization and IaCbased deployment automation •Decomposition of a Monolith Test Automation application, built on Java/J2EE Spring MVC stack with postgresSQL as DB. (226 screens, files 2561 and LOC: 1.2M. 229 data tables. ) •Follows a layered architecture with UI layer on top, Multiple core services like “ Product/User/Test/Defect management” etc. in the middle layer, •Data layer for interacting with DB and connector management for interacting with multiple external system as the bottom layer. •Component wise scalability based on traffic rules can be achievedIndependent Scalability •Can easily add new test engine support, without affecting whole systemEasy Extensibility •Impact of changes in external systems (TMS/DMS etc. ) can localized and addressedLocalize External dependency",, "Leading furniture companyCASE STUDY 8: DEVOPS IMPLEMENTATION & SRE FOR A LEADING FURNITURE COMPANY SCOPE / CHALLENGES / PAIN POINT APPROACH / SOLUTION BENEFITS / RESULTS DELIVERED TIME TO MARKET COST/ ROI •30+ systems in the business division and each in different maturity curve in DevOps and SRE •Products are headless and more data driven workflows/pipelines •Large API based integration with ecosystem •Challenges with DevOps, automation and knowledge management •Ability to scale the release volumes ▪Manual infra provisioning and DevOps automation not ready. With CB iStudio reduced dependency with automation ▪Fill gap in DevOps with IaCimplementation and enable Infrastructure provisioning using CB iStudio ▪Enabled provisioning on GCP with workload deployment and monitoring by customizable API calls ▪Functional API’s and compliance to IaCstandards with improved efficiency ▪End-to-end deployment automation & Improved standardization across products Shorter release cycles with automation VELOCITY QUALITY Reduced errors and efforts across multiple products Consistent and predictable deployment across environments75% Acceleration in deployment design and provisioning phase",, "Leading enterprise software suite CASE STUDY 9: MODERNIZATION OF STUDENT MANAGEMENT PLATFORM SCOPE / CHALLENGES / PAIN POINT APPROACH / SOLUTION BENEFITS / RESULTS DELIVERED TIME TO MARKET COST/ ROI •Re-engineer/modernize student management platform for universities •Legacy Platforms with old tech stack , difficult to manage and scale •Not modular in nature because of older architecture •Microservice led architecture providing more agility •Faster deployment and IaCstandardization ▪CB ACEMicro accelerator enabled boiler plate microservice creation which can repurpose existing business stored procs using templates ▪Microservices architecture deployed on Azure to scale dynamically ▪Support of template to build infrastructure for different environments ▪Enabled automation of IaCand workload deployment with Helm through CB iStudio ▪Implemented DevOps runtime for reduction in time to production Faster release cycle with microservice development VELOCITY QUALITY Acceleration in microservice development Significant reduction in initial learning curve for development teams60% Acceleration in IaCand workload deployment",, "Leading industrial company CASE STUDY 10: AUTOMATION OF COMPLEX APPLICATION DEPLOYMENT SCOPE / CHALLENGES / PAIN POINT APPROACH / SOLUTION BENEFITS / RESULTS DELIVERED TIME TO MARKET COST/ ROI •Complex home grown IoTbased analytics(AL/ML) system deployment in heterogeneous environment •Manual deployment process and takes 7 -10 days •Need to fully automate the installation/upgrade process •High SME dependency as deployment in on-premise and cloud ▪Business onboarding takes lot of time with manual process, with CB iStudio reduced time with automation ▪One click deployment of Infra and platform components using CB iStudio ▪Automated infra components of IoTbased analytics systems ▪Support of template to build infrastructure for different environments ▪End to end deployment automation and improved standardization Deploy components in 30 minutes, from 2 to 3 manual days VELOCITY QUALITY Framework is extensible to host application from business divisions90% Acceleration in product platform setup Reduction of errors and predictable deployment",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • •",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • • • • • • • • • • • • • • • • • • • • •",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • • • • • • • • • • •",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • • • • • • • • • •",, "Copyright © 2023 HCL Technologies Ltd. | Confidential • • • • • • •",, "Cloud Bridge: Accelerate your cloud journey",, "Our Expe/r_t.ligaise With HCLTech Cloud Bridge suite, enterprises can accelerate their journey to the cloud and efficiently manage their on-premise assets. The user journeys powered by Cloud Bridge include optimizing existing products or services, refactoring to take advantage of cloud services or becoming cloud-native. Cloud Bridge suite solves complex problems with an end-to-end unified approach. Our strong pa/r_t.liganership ecosystem with hyper scalers and leading cloud technologists such as IBM and Cloud Native Computing Foundation (CNCF) helps us build cu/t_t.ligaing-edge solutions. We keep pace with evolving market dynamics through continued investments in engineering research and development, emerging technology and service capability development. Patent-led solutions uniquely position us as a trusted pa/r_t.liganer for cloud migration and modernization journey. With strong expe/r_t.ligaise and experience across multiple customer engagements, we enable assessment, migration, modernization, greenfield development, automated provisioning and cost optimization. 2 Cloud Bridge:Accelerate your cloud journeyWhen it comes to managing risk and driving innovation, revenue, growth and resilience, organizations agree that digital transformation is the way to go. Cloud is witnessing higher adoption than before as its successes across enterprises become evident. It has led to significant business impact by accelerating business transformation and pe/r_f.ligaormance, suppo/r_t.ligaing innovation and enhancing customer experiences in a cost-effective way. Despite the overwhelming benefits, choosing the right cloud services and solutions can be a complex process. Organizations must adapt to new technologies quickly and respond to market needs while reducing the total cost of ownership (TCO) and maximizing the return on investment (ROI). HCLTech Cloud Bridge helps enterprises accelerate their journey to the cloud. Our unified approach",, "incorporates our expe/r_t.ligaise in digital, cloud-native migrations to deliver business-accelerating solutions and strategies. Our best-in-class, in-house cloud services and solutions provide the flexibility, scalability and security to meet enterprises’ varied needs.",, "Cloud Bridge Suite User Journeys Cloud Bridge suppo/r_t.ligas the following enterprise user journeys to accelerate cloud migration and modernization. Intelligent Assessment Assesses monolith workloads to derive intelligent insights and recommend the best suitable cloud migration approach (re-host/re-platform/ re-architect)Monolith Modernization Modernizes monolith workloads to microservices based architecture for cloud-ready deployment with deep analysis Containerization and Deployment Enhances the maintainability and po/r_t.ligaability of workloads that can be seamlessly deployed and monitored across on-premise, cloud and edgeCloud-native Engineering Helps enterprises go digital, introduce innovation into development with low-code/ no-code solutions built on cloud-native principles for multi-cloud and serverless environments Observability and Optimization Enables continuous monitoring of cloud services, open source tools and workloads for tracking usage and recommend potential cost optimizations Enterprise Challenges Adopting modernization involves business and technological riskMonolith workloads are inconvenient to handle and complex to scaleCloud infrastructure and workload optimization is a necessity Standardizing deployment across heterogeneous environment and enabling seamless expansion into new regions can be challenging 3 Cloud Bridge:Accelerate your cloud journey",, "Our Solution Accelerators Designed to help customers accelerate their digital transformation journey, and maximize the business impact with cloud Observability and cloud spending optimization recommendation solutionCB Optics A comprehensive low-code, no-code platform for Infrastructure as Code (IaC) design and provisioningCB iStudio Cloud and edge-friendly, low code template-based microservices and function developmentCB ACEMicro CodeSense Generative AI and LLM-powered functional and API documentation solutionCB Advisor Platform for application po/r_t.ligafolio assessment and recommending the best R and wave planCB Analyzer Helps to analyze, decode monolith applications and make an informed transformation decisionCB MODular Containerization automation and container vulnerability assessment 4 Cloud Bridge:Accelerate your cloud journey",, "Benefits of Cloud Bridge Accelerated migration through proven methodologies Leverages AI and analytics to fuel digital transformation and accelerate innovationPowe/r_f.ligaul pa/r_t.liganer ecosystem Offers incremental value, generates customer-ready solutions and accelerates time-to-market Reduce total cost of ownership Consulting and tool-led approach improves efficient and cost-effective business transformationCloud agnostic User-friendly deployment blueprinting and provisioning across multi-cloud and on-premise Solution Differentiators Custom cloud migration strategyNo vendor lock-inOne-click code to deployPatent-led solution 5 Cloud Bridge:Accelerate your cloud journey",, "HCLTech is a global technology company, home to more than 221,000 people across 60 countries, delivering industry-leading capabilities centered around digital, engineering, cloud and AI, powered by a broad po/r_t.ligafolio of technology services and products. We work with clients across all major ve/r_t.ligaicals, providing industry solutions for Financial Services, Manufacturing, Life Sciences and Healthcare, Technology and Services, Telecom and Media, Retail and CPG, and Public Services. Consolidated revenues as of 12 months ending September 2023 totaled $12.9 billion. To learn how we can supercharge progress for you, visit hcltech.com.hcltech.com",, Copyright © 2022 HCL Technologies | ConfidentialCompetitor AnalysisCloud Bridge Suite,, "Capability / Focus AreasHCL Accenture EPAM Infosys CTS Capgemini Global Logic Offering Offering Offering Offering Offering Offering Offering Cloud Engineering services * Cloud Native Transformation Consultancy * Cloud Migration * Cloud Modernization * Cloud Native Development* Cloud Migration -Discovery and analysis, Migration Strategy, Planning, Execution * Application Modernization - App Assessment, Business Rules Mining, Remediation Services, Replatform Services,Migratio n ServicesPlatform and Product strategy -Legacy Transformation, Green field developmentInfosys Modernization Suite - * Infosys Cloud Native Development Platform * Infosys Cloud Modernization Platform * Infosys Migration Platform * Infosys Database Migration Platform * Infosys Mainframe Modernization PlatformApplication Modernization - * Assessment services * Migration Services ( re-host, re -platform) * Modernization Services ( re -factor, re - architect) * Software product engineering ( re -build, new build)* Cloud Migration - Assessment , Architecture, Migration Factory * Cloud Transformation Services (Plan, Transform, Operate) - -Cloud Migration -Application Modernization ( re -host, re - deploy, revise, refactor, rebuild, replace) -Cloud Native Build 1. Strategic Advisory 2. Cloud Architecture & implementation 3. Cloud Application Development Digital Operations & Automation* Consultancy for CI/CD Tools Selection * DevOps services* Intelligent Automation servicesEnterprise Technology and Operation Transformation * Process Automation * Cloud and DevOpsInfosys Cobalt - * Infosys polycloud platform * Infosys Infrastructure Management SuiteApplication maintenance and management-Application maintenance and management Observability Services - Operation and MonitoringCloud Deployment Management * Intelligent Automation services",, "Capability / Focus AreasHCL Accenture Infosys CTS Capgemini Accelerators Accelerators Accelerators Accelerators Accelerators Cloud Engineering services * CN Reference Architecture * Cloud Bridge Suite Accelerators -CB Analyzer, CB Migrate, MODular, ACEMicro* myNav -cloud assessment platform * Cloud Factory -500+ reusable assets * A4C -Accelerate for CloudInfosys Modernization Suite * Cognizant Applens -Assessment soln * Transformation Blueprint ( autom assisted re -host/re -platform) * Appln Portfolio Rationalization(APR) * Arc -Tern -Migration Mgmt and governance tool * Container Deployment Platform(CDP) -Containerize and Migrate * GO Platform (Microsoft Cloud Adoption) * Value Stream Mapping ( Cloud readiness assessment for Java/ .Net and remediation steps for AWS) * 10vū assessment platform * COSMOS ( Unified workbeach for m/s development, governance, mgmt of m/s in AWS)* eAPM * DevOps Platform (DevOps PaaS) * Container Management (Docker Enterprise - as-a-Service or DEaaS ) * integration platform ( xPaas ) * Testing PaaS Digital Operations & Automation* RAPID * iStudio * CloudWorksmyWizard DevSecOps Platform * IaC generator * Integrated Cloud Management Platform ( Maximize automation of CloudOps to NoOps AWS )- Observability Services - Operation and Monitoring* eNOC * iStudio * CloudWorksSynOps",, "• • • • • • • • • • • • • • • 010203 0 05 0 • • • • •",, "▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ • • • • •",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT -",, "❖ High cost of patient management with delays in care ❖ Remote patient monitoring & health data management ❖ Ensures patient safety and on -time care with limited human resources ❖ Chances of security breach in data management ❖ Multi -tenant IAM & password enabled authentication ❖ Prevents misuse of critical information ❖ Time -consuming & error prone manual data transfer across devices❖ Data exchange across connected devices ❖ Improves operational efficiency & data quality ❖ Manually intensive process of software upgradation where multiple devices are spread across geography ❖ Remote patch management across multiple devices ❖ Quick device upgradation & improved uptime ❖ Software development is a time -consuming process ❖ Reusable drag and drop builders for code generation & test automation​❖ Accelerates software development by at least 30%Positioning Statement For the patient caregiver of a medical device user facility who struggles with limited time for patient care or for the asset manager who struggles with issues of manual device management, CARE provides a secure platform for remote patient management & asset lifecycle management. CARE offers device connectivity, inventory management, device data management, associated patient monitoring, and patch management, all through a scalable remote application.Connected Assets in Regulated Environment (CARE) Customer Challenges Business Benefits HCL’s CARE Offerings Differentiators Success StoriesPatient Management Patch Management Reusable Libraries Remote Assistance • CARE reduced the effort spent on development by 26%, QA by 18% and deployment by 10% for a medical device manufacturer • Reduced time -to-market of a new solution by 40% for ​an American multinational manufacturing organizationBuilt -in Security",, "CARE is a powerful software framework that comes with the necessary building blocks for building next generation medical multitenant software / services faster . CARE brings together business application building frameworks, device connectivity, re-usable software components and best practice templates to provide acceleration to the development of software / platforms . It can be used to build both edge/gateway applications as well as scalable cloud application . Microservice based framework to build both edge as well as cloud applications – extendable business logicReusable microservices for authentication, authorization, audit, logs, notification, device management, remote access, patch management, patient engagement, consent management, case management and workflow. Supports Hierarchical Multitenancy, data access control, tenant data isolationApplication building templates for REST - API, device management, edge gateway, integration, remote software upgrade Remote device diagnostics/monitoring •Remote software update •Remote ssh/RDP/VNC Session •Remote logs and command executionDevice Gateway with store -n-forward data exchange, device integration framework, anonymization and command handling modules. Connected Assets in Regulated Environment (CARE) CARE Cloud Hospital/Partner NetworkMedical IoT Device 2 Device nBusiness ApplicationPHI data Device 1CARE AgentCARE AgentCARE AgentCARE IntegratorCARE Gateway",, "HCLTech CARE (Connected Assets in Regulated Environment) Enabling Personalized, Connected and Intelligent Healthcare",, "Achie ving in teroper ability in a he terogeneous clinical en vironmen t with de vices from mul tiple vendor s using diff erent data forma ts A dynamic threat landscape in which ensuring security of patient and de vice da ta in transit and at rest is gr owing incr easingl y chall enging.A highl y regula ted landscape in which the solution must compl y with sa fety and effectiveness, applica tion lif e cycle, and risk managemen t standar ds. Varying r evenue models, hard-to-track impact metrics, and incompl ete sol utions complica te the cal cula tion o f payoff on sol utions.Ubiquit ous de vice connec tivity: security: Archit ecting complian t sol utions: Realizing the digital care RoI: 62304Comp liant with NIST and IEC Deployed in wellne ss, chronic care, acute care, and post-acute care scenariosEnables care de livery for Has been in the market sinceDeployed across clinic s and laboratories150,000+ patients 5000+ 500+ 10 years countries and 5 continentsIn us e across 43 of the top medic al devices OEMsTrusted by 6 10Typical chall enges in cr eating a connect ed heal thcar e ecos ystem Critical car e interventions call for a car efully calibr ated digital heal thcar e ecos ystem and pa tient engagemen t. Whil e the industry is headed towards cl oud- first in frastructur e and da ta-driv en clinical Has an installed base of 250,000+ connected med ical devicesCARE (Connected Assets in Regulated Environment) CARE is a industry-leading healthcare platform for enabling device and patient care ecosystems to improve care efficacy and drive be/t_t.ligaer clinical outcomes. CARE brings together business application building frameworks, device connectivity, re-usable software components, and best practice templates to provide acceleration to the development of next generation medical software/ platforms.",, "What CARE delivers? Benefits of CARE Compr ehensiv e cyber security with NIST con trols impl emen tation.Adher ence to Medical R egula tory Standar ds - 62304 . Based on M ulti Cloud D eploymen t capabilityEasy to install and offers hassl e-free main tenance. Lowest TCO solution to mone tize heal th- care da ta pr oduc ts.Provides 30-50% upfront produc tivity impr ovemen t and cost savingsDigitiz e your car e deliv ery infrastruc ture: Onboar d de vices using diff erent data forma ts from mul tiple vendor s deliv ery workfl ows. Predic tive M aintenance o f Connec ted Assets: Con tinuousl y monit or Connec ted Assets for possibl e failures and optimiz e main tenance schedul es to incr ease up time o f your ecos ystem. Deliver software upgr ades r emo tely to your connec ted asse ts: by deliv ering pa tches to de vices o ver-the-air , and in form k ey stak ehol ders of associa ted do wntime. Ensuring da ta priv acy and security: Ensur e security of patient and teleme try data at rest and in transit . Leverage de vice da ta to impr ove efficac y of acut e car e deliv ery workfl ows Oper ationaliz e intelligen t car e deliv ery models b y inges ting de vice da ta and enriching it with anal ytics technol ogies. CARE Outcomes",, "Wha t next? clinician and pa tient experience, and incr easing the R oI on car e deliv ery. Take your first step towards intelligent care de livery, with the CARE platform. Build intelligence into your medical devices, and activate healthcare data products at the spee d of information. Let’s join hands to shape the e volution o f digital car e. Write to us a t ers.info@hcl. com today.Customer success stories IoT-izing st eriliza tion equipmen t and enabling 360-degr ee ecos ystem connectivity for a gl obal medical de vice pla yer Connecting Lasik diagnostic and surgical equipment to deliver real time precision surgery for a US based medical devices leaderEnabling seamless communication between devices and software to pe/r_f.ligaorm various stages of DNA sequencing for a leading Europe based medical devices player hcltech.com HCLTech is a global technology company, home to 225,900+ people across 60 countries, delivering industry-leading capabilities centered around Digital, software. The company generated consolidated revenues of $12.6 billion over the 12 months ended March 2023. To learn how we can supercharge progress for you, visit hcltech.com",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT -",, "❖ High cost of patient management with delays in care ❖ Remote patient monitoring & health data management ❖ Ensures patient safety and on -time care with limited human resources ❖ Chances of security breach in data management ❖ Multi -tenant IAM & password enabled authentication ❖ Prevents misuse of critical information ❖ Time -consuming & error prone manual data transfer across devices❖ Data exchange across connected devices ❖ Improves operational efficiency & data quality ❖ Manually intensive process of software upgradation where multiple devices are spread across geography ❖ Remote patch management across multiple devices ❖ Quick device upgradation & improved uptime ❖ Software development is a time -consuming process ❖ Reusable drag and drop builders for code generation & test automation​❖ Accelerates software development by at least 30%Positioning Statement For the patient caregiver of a medical device user facility who struggles with limited time for patient care or for the asset manager who struggles with issues of manual device management, CARE provides a secure platform for remote patient management & asset lifecycle management. CARE offers device connectivity, inventory management, device data management, associated patient monitoring, and patch management, all through a scalable remote application.Connected Assets in Regulated Environment (CARE) Customer Challenges Business Benefits HCL’s CARE Offerings Differentiators Success StoriesPatient Management Patch Management Reusable Libraries Remote Assistance • CARE reduced the effort spent on development by 26%, QA by 18% and deployment by 10% for a medical device manufacturer • Reduced time -to-market of a new solution by 40% for ​an American multinational manufacturing organizationBuilt -in Security",, "HCL Connected Assets in Regulated Environment (C .A.R.ETM) HCL’s CARE (Connected Assets in Regulated Environment) is a Micro -services architecture featured multi -tenant platform that helps in building a regulated medi cal class software within a significant reduced time. CARE platform that provides necessary building blocks for developing next generation software / services faster. CARE brings together packaged application framework s, re-usable software components, automation tools for developers & testers, support for best of breed architectural patterns and best practice templates to provide acceleration to the development of software / platforms. Key Features • Standardized and Integrated Best of breed technology • Data Management to store, retrieve, encrypt, import, and export data • State of the art in-built security for preventing attacks and ensuring compliance • Packaging and c ontainerization support for cross platform deployment of micro services with back-up/ restore features for business continuity • Integrated drag and drop builders for code generation, Entities, REST APIs, UI, Unit Tests and, Automation Scripts, Service Integration • Support for multiple architectural patterns, including Event Driven, N -Tier, and Micro - services • Integrated log managemen t for centralized logging, notification and custom dashboard etc.",, "HCL Connected Assets in Regulated Environment (CARETM) HCL CARETM Platform Architecture Business Challenges Addressed Without a “reuse/foundation” approach to software, organizations end up having significant redundancies in infrastructure, licenses, people, and processes, thus leading to an inefficient delivery of services Creating a Platform that can act as a foundation to launch business services requires sig nificant investments in terms of cost, skill and time A global service creates different code base of comparable functionalities, thus leading to increased cost of maintenance of these applications With high pressure on cost and time to market, it is diffi cult to approach software as a “holistic” solution Why CARETM? In-built tools, workflows, rule engines, libraries, etc. enable rapid creation of multi-tenant apps and the conversion of single tenant apps to multi -tenant apps Easy on -boarding of new countries/entities with easy to use configuration sans any additional development effort Execute complex test scenarios involving two or more development platforms working in tandem Extensibility to address data model extensions specific to country/brand/branch Support for single instance and distributed deployment models",, "HCL Connected Assets in Regulated Environment (CARETM) How CARETM Helps CARETM Acceleration through Software Development Phases",, "HCL Connected Assets in Regulated Environment (CARETM) Proof Points Benefits CARETM CARETM",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT Case Studies",, "Connected Asset in Regulatory Environment [ CARE ] CARE is a powerful software framework that has the necessary building blocks for building next generation medical multitenant software / services P faster . CARE brings together business application building frameworks, device connectivity, re-usable software components and best practice templates to provide acceleration to the development of software / platforms . It can be used to build both edge/gateway applications as well as scalable cloud application . Microservice based framework to build both edge as well as cloud applicationsHandles basic needs such as Authentication, Authorization, Audit, Logs, Email template etc. Supports Hierarchical Multitenancy, data access control, tenant data isolationApplication building templates for REST -API, device management, edge gateway, Integration, remote software upgrade Remote device diagnostics/monitoring •Remote software update •Remote ssh/RDP/VNC Session •Remote logs and command executionDevice Gateway with store -n-forward data exchange, device integration framework and command handling modules.",, "MEDICAL DIGITAL FOOTPRINTS ON CARE CARDIAC & VASCULARImplants HOSPITAL EQUIPMENTDIAGNOSTICS MD SEGMENTS OUR CUSTOMERSSolution : A Multi Safety classified Data Management System Connecting several Lasik Diagnostic equipment with Surgical equipment for delivering a real time Precision surgeryProblem : Device Centricity, Lack of Scale Solution : Patient Centric Digital Enablement Managing Million transactionsDomain : CARDIAC RHYTHM Domain : Hemodynamics Problem : Unconnected, Provider centric, Localized Solution : Azure Based real time Patient Monitoring and Episode PredictionDomain : Implants Problem : Unconnected Solution causing Loss of continuous CARE to patients. Low Physician ProductivityDomain : Sterilization Problem : Unconnected System, Manual Errors, High Down time. High Field Service costs Solution : A cloud solution connecting multiple hospital equipment that does auto reconciliation and predicts device failures using AnalyticsDomain : Sequencing Problem : Unconnected workflow causing manual calculations and movement of data Solution : A Digital workflow synchronized orchestration managing multiple device types across the sequencing workflow Problem : Unconnected Diagnostic and Surgical causing lower productivity, loss of data and errorsVISION CARE DRUG DELIVERY & INFUSION PUMPS Segregate data about fluids/ medicines used for infusion and patient vitals to help in real time & offline recommendations for the Physicians ORTHOPEDICS Self Reporting Bone – A Digital Surgical Workflow System Ensuring Patient Adherence and Data MonetizationDomain : Surgical CARE Problem : Disconnected Eco System, Lack or surgical preparatory Environment. Provider Centricity Solution : A DIGITAL Surgical Workflow system connecting eco system playersDomain : Lasik Surgery",, "4BUSINESS CHALLENGE HCL SOLUTION: Integrated Service Delivery PlatformCASE STUDY: New business model Innovation for a leading office automation customer The online ecosystem enabled through our multi -tenant PAS, brought end customers, distributors and resellers on to a common platform. An overall 40% reduction in time to market of the new solutionGlobal company with stagnant or eroding market share for printers Loss of supplies (toner and other consumables) revenue due to grey market and 3rd party An Integrated Service delivery platform to bring End Customers, Distributors and Customer’s resellers into a common platformImproved Device management capabilities integrated to service delivery positively impacted the service levels Order ManagementCustomer OnboardingDevice Management End customers benefit due to the reduction in inventory at their end, and by the elimination of a cumbersome and error prone ordering processHCL IMPACT",, "5BUSINESS CHALLENGE HCL SOLUTION: e -Deposit Platform based on PAS (Business app builder module of CARE)CASE STUDY: DIGITALIZATION OF CHEQUE COLLECTION PROCESS FOR IMPROVED TURN AROUND TIME AND EFFICIENT TRACKING Workflow to manage and process cheque and collection data process flowNeed to have an OMNI - Channel (Web & Mobile) Data Capture Platform to capture and store cheque collection data Management of Vendors like – Couriers, Data Processing Hubs etc. Configurability in terms of client on -boarding, Schedule Management, Route Management etc.",, "CASE STUDY: GLOBAL CARE PLATFORM for Incontinence care ……………………………………………. Geo #1 Geo #2 Geo #n Care Service Program #1 Incontinence Care ServicesGlobal Service Platform Launch Challenge : Varied back office systems, multiple payment options, different languages, different business rules and data policies associated with the same service Business Challenge : Track and monitor patients across the entire care spectrum and provide them appropriate care services and thereby increase adoption of their incontinence care product. Nursing Home #n Nursing Home #1•Cloud (AWS) based Care services for incontinence patients across care spectrum serving 125+ countries •Provide capability to launch multiple services leveraging the same platform •Patient data management adhering to local compliance regulations •Care Services enabled for customization at a country level and nursing home level •Connectivity to multiple back office technology & systems Care Apps Logistics Track and ManageWorkflow Rules & Data Models Internationalization Reports & Dashboards Entity Attribute Customization Business RulesIntegration with back end systems Care Service Program #2 Care Service Program #n Nursing Home #2 Nursing Home #3 Nursing Home #4Nursing Home #n - 1 Reseller #1 Reseller #nHierarchical Multi -T enant, Global Platform for launching Care Services • Infrastructure Cost reduced by 40% because of multi -tenant deployment • Support Cost reduced by 60% because of centralized management of the platform • 30% license cost saved by removing multiple deployments • New Nursing Home On -Boarding Reduced by 6 weeks",, "7BUSINESS CHALLENGE HCL IMPACT •Reach product parity with competitor by providing a connected solution that would make transfer of data between the diagnostics and surgical instrument more efficient •Single software platform to support on premise and cloud hosting. Cloud solution to be multi -tenant with full FDA Class III ComplianceLeverage of the reusable foundation of CARE reduced the effort spent on development by 17% •Manual Data transfer between diagnostics systems is time consuming and error proneHCL SOLUTION: Integrated Ophthalmology Care PlatformCASE STUDY: Ophthalmology Care Platform Pre-T ested components of CARE helped reduce QA efforts by 20% The connected device solution would increase device usage; patient handling per day is expected to increase by 11%Standardized and Integrated technology stack of CARE provided abstraction of complexity of cloud deployments and on premise deployments",, "8BUSINESS CHALLENGE HCL IMPACT A platform capable of onboarding an entire family of IoT devicesBring all devices and related management under a connected ecosystem A Hierarchical multi tenant framework to build association between different business units, the devices & countries in which the service is launchedEfforts to On -board new business units and their devices reduced by 70% Efforts saving of up to 80 person months Integrated Device Management with complete access control of device and its data HCL SOLUTION: Connected Device PlatformCASE STUDY: device management platform",, Backup,, "Our POV on Digital Services Platform Geographically Distributed Multi -tenant Able to launch Digital services across multiple geographies, customers, etc. Infrastructure as Code / DevOps driven sets up complete platform, services, environment in an automated fashion Micro -Services based Develop self -contained micro -services built for change and scalability IoT / Connectivity ready Platform should be ready with its IoT and Machine learning capabililities to cater todays/future needs Cloud scale Leveraging auto - scaling features. Built on best -in-class Cloud offerings.Security Data Isolation, HIPAA, GDPR compliance, Authentication and Authorization, etc.",, "Stay Focussed on the Device Expand to Premise Eco System Expand to Patient Eco System …..Device Eco SystemHow Customers travel the Digital journey …..Procedural System …..LIS EMR Integrations ….. Provider, LAB Workflows …… Device Integration…..People System …..Patient CARE ….. Monitoring & Adherence ….. Episode Management…..Device Eco System Plumbing Adjacencies & ConveniencesPotential RealizationCARE FOCUS",, "CARE Cloud Private/Partner Network Smart GatewayDevice interaction• Device life cycle management • Device inventory • Software update management • Remote diagnostics • Consumables management • Tracking usage, monitor uptime • Subscription management • Store -n-Forward • Command agent • Data flow orchestrator • Offline administration and data/event/workflow manager Options: • Appliance in a Box • Software appliance – OVA • Installable in PC/Laptop • Integrated with Device/Software Device 1 Device 2 Device nBusiness ApplicationCARE : Typical Deployment model • Collaboration between stakeholders • Task, process, approval workflow • Subscription, billing , metering • Reports & Dashboards Agent Agent AgentData store",, "Azure / AWS/ Cloud Device Remote -Support GatewayRemote - Support gatewayIoT Hub/ MQTTMQTT Or MQTT over W ebsocket (Push messages to Device) Remote - Support W ebsocket serverRemote - Support Device management Remote - Support agentW eb socket TunnelingVNC/RDP/ SSH Server Remote - Support Tunnel agent RDP/VNC to HTML5webserver server VNC/RDP Support EngineerHTTPS / HTML5Recoding done hereTLS1.2+ with X 509 Cert A uthentication TLS 1.2+VNC/RDP/ SSH Server Bash/CMD/ Powershell Enterprise/Private netw ork (F irew alled)•Remote file browsing and upload v ia browser •RDP/VNC/SSH access v ia browser •Automated Session Recording •Remote command execution •Logs/telemetry data collection •Remote Patch update[Optional] Remote - Support Agent •Remote file browsing and upload v ia browser •RDP/VNC/SSH access v ia browser •Automated Session Recording •Remote command execution •Logs/telemetry data collection •Remote Patch update •Store -n-forward •Dev ice/E MR integration frameworkBusiness App (optional) Business App (optional)Built using CARE reusable modules such as IAM , Audit, Email, M etadata, App templates etc .. Built using CARE reusable modules such as IAM , Audit, Email, M etadata, App templates etc .. Business user HCP PatientDevice integrationData Store: RDBMS, Blob, noSQL , In MemoryCARE : High -level architecture",, CARE : Usage,, "•Security •Multi tenant IAM •Handles password -based authentication •Supports OTP/TOTP based authentication •It can work with LDAP , openID , SAML AUTH providers •It can act as oAuth /openID auth provider •Pl. refer slide #9 •Admin •Manages tenant, user, roles, permissions •Password policies and management •Cross tenant data access policies •Metadata •Tennent specific data •UI localization per tenant •Email -template •Manages SMS and EMAIL templates •Email -sender •Email/SMS sender and retry •Audit •Captures Audit trail events •Manages Audit messages•Device management •Device type and Device inventory •Device provisioning and other lifecycle management •Device remote access, Device commands •Device data handler •Patch management •Device patch management/rollout •Gateway •Device side agent with store -n-forward, command and remote connection agent •Consent management •Consent management •Patient management •Patient and HCP onboarding, and mapping •Patient demography and other data management •Case management •Custom Case workflow and management •PLUG gateway •A REST gateway that handles different security functions, like anonymization, consent check, authorization check, time based access, Geo base access etc ..CARE : Ready to use microservices",, "•API •JWT validation •Authorization – permission -based access control •Multitenancy •Audit event generation •Utilities to talk to other microservices with JWT/Certificate base auth •Please refer slide #8 •UI •Plain HTML/HTML •Angular based UI hosting •Simple API •JWT validation •Integration API•Dynamic route creation and management •Camel based •Supports interaction with different services - https://camel.apache.org/components/latest /index.html •Useful for scheduled activities, queue based offline processing •Camel provides some error handling mechanism •Workflow •Multitenant •Activiti based CARE : Microservice templates",, "Hierarchical Multi -tenancy Enable easy hospital on -boarding and integration Global Roll Out Data segregation Everything through configurationsMonetization Support business monetization needs Economical for firm and its customers Enable/disable capabilities per tiers Easy utilization tracking for charge backSecured, Controlled, Compliant yet Flexible “Privacy By Design”, to manage patient data privacy and security HIPAA, GDPR Compliance NIST and FDA Cyber Security guidelines Multi -Country Data Rules Ease of Use/Integrate Offer ease to build/integrate existing and new applications quickly Ease of data ingestion, analysis and integration APIs driven approachModular Architecture Use micro services with plug -able approach Standard data models and integrations Separate regulated/non -regulated componentsMedical Device Specific Device Life cycle management Device Integration through Open Ice Approval Workflows Data ManagementKey Imperatives for Platform’s Success",, "CARE FEATURE SET M2M Device Management Remote Control Software Upgrade Generic GatewayIntegration Plug -N-Play Agent based integration DICOM HL7 LISSECURITY & PRIVACY Centralized Audit Management HIPAA Compliance NIST Control Implementations Monitoring Service Monitoring Start up – Shut Down Auto Load Balancing ContainerizedAdvanced Architecture Micro Products Approach Event Architecture Data Ingestion workflow Hierarchical Multi T enancy MD as a Computer [Digital Twin]Provider Workflow Provider Workflow Path Single Provider Portal UI Builder Entity Builder",, "CARE - Device CARE Framework Global Care Platform Set up Geo/Country On boarding Language Settings Country Specific Settings Backend IntegrationsSite Onboarding Set Up Site specific Branding User/Role Creation Ward/Shift Planning Site ConfigurationsUser Onboarding Device Life Cycle HIS/LIS Connectivity Data ManagementDevice Onboarding Onboarding LAB UsersData Acquisition LIS/HIS Data Medical Device Data Manual Data EntryWorkflow Sample Ordering Orchestration Re Planning AutomationMonitoring Self Diagnostics Remote Monitoring UpgradesReports 19",, "CARE - Patient CARE Framework Global Care Platform Set up Geo/Country On boarding Language Settings Country Specific Settings Backend IntegrationsProvider Onboarding Set Up Hospital specific Branding User/Role Creation Ward/Shift Planning Set up Therapeutic AreasClinicians Onboarding EMR Order Entry Patient info from EMR Care AssignationPatient Onboarding Adding clinician infoData Acquisition Patient History from EMR Medical Device Data Get DICOM Data Manual Data EntryCare Planning Assessment Diagnosis Actions Drug ScheduleMonitoring Dosage Reminders Patient Monitoring Self CareReports 20",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT",, "CARE –LONG TERM PRODUCT ROADMAP 2",, "WWW.HCLTECH.COM that helps in building a regulated medical class software within a significant time frame. CARE brings together packaged",, "WWW.HCLTECH.COM CARE - INDUSTRY TRENDS The Healthcare industry is going through a paradigm shift from patient centricity to continuous patient engagement. There is an increasing urge to move from continuous monitoring to disease prediction, from patient -initiated admissions to continuous interventions and data ownership to data sharing. Whether you are in w ellness, chronic, acute , or post -acute care ; you nee d to bring integrated hyper -connectivity and a data -driven approach to the focus point. HEALTHCARE INDUSTRY CHALLENGES Each healthcare company find s itself at a different stage of connectivity and digital maturity level. You might face challenges that are unique to your stage . General challenges that can hold you back could be: • Lack of a clear end user -centric business case • Lack of a clear approach towards monetization of data • High upfront cost • Longer pay -off period • Challenges with the interplay of software and device • Understanding and preventing ever -increasing cyber security threats • Extensibility of a solution across product families • Navigating the regulatory maze with the device and software interpla y The growth rate in the medical de vices industry has shrunk from a two -digit figure in the past decade to a mere 2% in recent years . This decrease is a result of reduc ed large -scale innovation, tightened regulatory norms, tougher reimbursement procedures, and presence of alternatives . In this scenario, a c onnected digital health ecosystem can serve as a manufacturer’s ammunition to fuel -differentiated value creation. HCL’s CARE GIVES YOU AN EDGE HCL leverages the Asset, Service , and User Value Chain approach for digitization and connectivity enablement. HCL’s CARE (Connected Assets in Regulated Environment) Platform is a • Micro -services architecture featur es a multi -tenant platform that helps you in building a regulated medical class software within a significant time.",, "software within a significant time. • Comprehensiv ely addresses the business solution and technical challenges faced by all kinds of care settings. WELLNESS CHALLENGES AND SOLUTIONS Device Business Challenge Platform Need ed Technical Challenge HCL’s Solutions Wearable Monetization, Customer Ownership, Repeat Business Social Media Integration Wellness Portals, Customer Health Tracking Data Integration, Data Ownership Gym Management, Cloudfeeds Integrated patient predictive analytics",, "WWW.HCLTECH.COM CHRONIC CARE CHALLENGES AND SOLUTIONS Device Business Challenge Platform Need ed Technical Challenge HCL’s Solutions Pumps, Smart Tablets, Patches Adherence, Therapy Outcome/ Efficacy, Replenishment Care Platform, E -Commerce, Integration, Content Management Communication standards, Data Privacy, Security Cloud Connected Glucometer, Diabetes Patch, Cloud Connected Home dialysis, Infusion pumps for multiple sclerosis ACUTE CARE CHALLENGES AND SOLUTIONS Device Business Challenge Platform Need ed Technical Challenge HCL’s Solutions Defibrillator , EMG, MRI, Sterilizer , Microbial Detector, Sedation, Lasik Surgical Device, Compounder, Hemo dialyzer Low availability of devices Device Integrator, EMR Integration Care Continuum, Analytics Analytics, Informatics, Device Integration, Cyber Security, Integration Connected Infusion Pumps, Connected Surgical Sterilizers, Connected Medical Optics POST ACUTE CARE CHALLENGES AND SOLUTIONS Device Business Challenge Platform Need ed Technical Challenge HCL’s Solutions Sensors, Wearables Adherence, Monitoring Data Management Data Creation, Device Connectivity CloudFeeds, Sensor Integration",, "WWW.HCLTECH.COM REMOTE DIAGNOSTICS AND SOLUTIONS Device Business Challenge Platform Need ed Technical Challenge HCL’s Solutions Medical Devices Monitoring, Troubleshooting Remote Diagnostics Secured Device Connectivity Remote Diagnostics HOW CARE ENABLES MEDICAL SOFTWARE DEVELOPMENT CARE ADVANTAGES Low risk/higher rate of success ➢ Follows standard technology patterns allowing standard skills to be leveraged. ➢ Low risk technology approach acts as a bridge between Build vs Buy. ➢ Abstraction of technolog ical complexity ➢ Focus ed on business requirement",, "WWW.HCLTECH.COM Acceleration ➢ Reusable components accelerate software development by at least 30% ➢ Automation to ease code development ➢ Pre conceptualized approach to a global platform saves time in all phases of Software Development Life Cycle ( SDLC ) Quality ➢ Pre-built components driving ‘Getting it right first time ’ ➢ Best Practices enforce d right from design phase . ➢ Pre-tested components cut down the time taken in functional, non -functional , security and deployment testing. Cost Reduction ➢ The platform -based approach reduces the cost of building new services by up to 50% ➢ Open -source components reduce the overall cost of ownership . ➢ The administrative first approach enables better management and delivery of services across the globe. CARE Functionalities 1. HIERARCHICAL MULTI -TENANT MANAGEMENT CARE provides you the ability to create a multi -tenant hierarchy (multitenancy), which means your software architecture can have multiple single instances of software run ning on a single physical server, that serves multiple tenants (different customers or countries ). You can use this architecture to allow multiple users into a single application . CARE provides a hierarchical multi -tenant metadata engine to configure different policies for tenants and influence the behavior of the application accordingly. Here, e ach tenant can have ancestors, peers , and descendants . For instance, in the below figure, for tenant D : ➢ Tenant A is a n ancestor. ➢ Tenant B and C are peers. ➢ Tenant F and Tenant G are descendants.",, "WWW.HCLTECH.COM 2. CUSTOMIZATION The CARE platform comes along with a metadata customization service that offers you customization that is based on Identity and Access Management (IAM) configuration . This service allows the externalization of different facets of application behavior in order to allow a multi -tenant applicati on to behave differently for different tenants. The customization is enabled through a meta -data -driven infrastructure . It allows the customization of : a. Data Model - Entity extensions may be required in the data model b. Validation - Show/ hide column s based on tenant -specific requirements c. Workflow - Definitions of specific workflows based on tenant requirements d. Business Rules - Definitions of rules that vary based on tenants e. Reports - Definitions of reports that are new for tenants 3. SECURITY The security component in CARE ensures that your software is capable to handle Authentication , Authorization and Auditing I. AUTHENTICATION You get two options for authentication with CARE : 1. CARE Inbuilt Authentication with the following functionalities : a. Inbuilt user, role , and permission data model b. Encrypted passwords c. Support for OTP or Time -based OTP through Multi-Factor Authentication (MFA) d. Access request interception and validation e. Secure password reset and recovery mechanism f. Support to configure and enforce password policies 2. Delegat ion with the following functionalities : a. Delegated to the customer identity providers using standard protocols like Open ID, LDAP/AD b. Provision for integration with 3rd party authentication systems II. AUTHORIZATION CARE empowers the application to handle two types of authorizations : a. Role -Based Authorization - Provide s permissions to access features based on the role defined for a particular user. It is possible to assign multiple roles to a user.",, b. Edition/Subscription based authorization - Enforces permission -based control on features mapped to editions.,, "WWW.HCLTECH.COM The authori zation framework leverages spring security annotations to restrict access to business services. It is also possible to directly map application -level permissions to Create, Read, Update and Delete (CRUD ) activity of an entity to restrict permission. E.g., the CREATE_USER permission can be mapped to CREATE user entity and therefore enforcing permission become s simpler . III. AUDIT CARE supports two kinds of auditing and logging. a. Security Logging - Logging/storing of information related to login, logout, failed logins, password changes and password policy changes. b. Application Logging - Entity level logging of information like created date, updated date, edited by and created by. Logging supports various log levels - Trace, debug, info, error, warn. The logging framework can also be used by business services to do business level logging. 4. DEVICE MANAGEMENT With CARE, you can main tain all your available devices in the application based on their types. It is necessary to add the devices when you procure them and delete the devices when not in use. 5. PATCH MANAGEMENT Our patch files can be utilized to fix software bugs, improve progra m usability, replace graphics, and update software features. A patch file contains the essential data to update an application or fix a problem with the associated software program. 6. REMOTE CONNECTIVITY Remote connectivity in CARE offers you the convenience of troubleshoot ing a devic e by accessing it through a remote connection . You can view the ‘remote session videos ’ to view the activities occurring during the remote connection. CARE also enables you to access the files in a remote location .",, "WWW.HCLTECH.COM 7. NOTIFICATION The notification feature in CARE enables you to send notification s to the user s. For instance, if you are creating a new user in the CARE application, a notification will be sent to the respective user. Likewise, when the user forgets password, and click s on ‘forget password ’, a link will be sent to the user for generating a new password. 8. CONSENT MANAGEMENT The consent management feature is built on top of the CARE framework. This service is useful for getting consent from the user s. You can get a list of users who have given consent. Similarly, you can also obtain the status of all the consents for a specific user. There are many other application programming interfaces ( APIs) to help you extract information regarding consents. 9. PLUG Plug proves to be vital for intercepting the requests sent by the user before he/she can access any feature . Using the Block API, the user can be blocked based on certain conditions. SUCCESS STORY A LEADER IN THE MEDICAL DEVICE SEGMENT GETS DATA MANAGER FOR STERILIZATION EQUIPMENT AND CONNECTIVITY WITH HOSPITALS Scenario : Customer wanted to launch smarter and more connected devices for the future. They wanted to progressively connect the medical devices with each other, connect them with the hospital systems , and eventually connect the m to the internet. Challenge : A g lobal manufactur er of sterilization devices : ➢ Require d a service offering that differentiated them from their competitors ➢ Need ed to launch a connected device platform that would help hospitals eliminate manual tracking of sterilization reports. ➢ Wished to e nable dual access to service, from the cloud and within the premise. HCL Approach : HCL’s extensive experience in embedded, hardware , and software Digital Engineering plus investment s in the connected devices space were leveraged to launch a ‘first of its kind ’ connected -platform -enabled product globally.",, "HCL’s prior knowledge of the sterilization domain and the products ensured better time to m arket. HCL’S COMPREHENSIVE SOLUTION ➢ HCL’s ability to provide all services under one roof proved very critical for the launch of the platform • HCL’s partnership with Intel ensured that the best gateway board from Intel, embedded operating system ( OS) from Wind River and security enablement from McAfee is in place. • HCL’s expertise in hardware engin eering ensured that the Gateway hardware is customized for actual customer ’s needs .",, "WWW.HCLTECH.COM ➢ Leveraging HCL’s Global Device CARE Platform (GDCP) • Leverage d HCL G DCP to build a solution that could be deployed on-premises as well as on the cloud , thereby reducing the time to market by 50 % and keeping the cost of the Gateway significantly low. • Utilized a local gateway to deploy the solution within the hospital with an integrated monitoring and management service for the ga teway. • Abstract ed the complexity of cloud deployments and on -premises deployments using GCP. ➢ Adoption of HCL’s Medical Device Agile Methodology • Adoption of Agile methodology kept the product requirements flexible and allow ed granular and impactful produc t improvements. • The metric -based approach resulted in a high -quality solution . The solution minimized the wastage of efforts invested in defect -fixing during the verification cycle , which in turn accelerated the time to market. • The talent -centric approach ensure d that all areas of the solutions were fully addressed resulting in lower field -level issues. • Frequent hardening cycles ensure d that integration and usability issues are caught upfront resulting in faster time to market and superior quality. • Performance engineering specific approach ensure d that non -functional requirements of the system were addressed beforehand, resulting in limited system changes towards the end of the program . FUTURE BENEFITS ➢ Consumables purchase through automated monitori ng and replenishments. ➢ Remote diagnostics and predictive maintenance will lower sterilization cycle failures and provide sterilization guidance to operators . HCL Technologies is a next -generation global technology company that helps enterprises reimagine their businesses for the digital age. Our technology products, services, and engineering are built on four decades of innovation, with a world -renowned management philosophy, a strong",, "culture of invention and risk -taking, and a relent less focus on customer relationships. We offer an integrated portfolio of products, solutions, services, and IP through our Mode 1 -2-3 strategy, built around Digital, IoT, Cloud, Automation, Cybersecurity, Analytics, Infrastructure Management and Engineering Services, amongst others. With a worldwide network of R&D, innovation labs and delivery centers, and 132,000+ ‘Ideapreneurs’ working in 44 countries, HCL serves leading enterprises acr oss key industries, including 250 of the Fortune 500 and 650 of the Global 2000. cl.com Follow us on Twitter: http://twitter.com/hclers Visit our Website: http://www.hcltech.com/engineering -services/",, "CONNECTED ASSETS IN REGULATED ENVIRONMENTS ™ (CARE ) Security white Paper Copyright Notice The information contained in this document is the property of HCL Technologies Limited. Except as specifically authorized in writing by HCL Technologies Limited, the holder of this document shall: (1) keep all information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to all third parties and, (2) use same for operating and maintenanc e purposes only Disclaimer The information contained in this white paper is for reference purposes only. Nothing contained in this document or relayed verbally to any customer will be deemed to amend, modify or supersede the terms and conditions of any written agreement between such customer and HCL Technologies .",, "CARE Security White Paper HCLT Confidential Page 2 of 15 Glossary Abbreviation Description FDA Food and Drug Administration CIO Chief Information Officer IT Information Technology CARE Connected Assets in Regulated Environment™ OTP one-time password TOTP Time -based One -time Password LDAP Lightweight Directory Access Protocol OpenID OpenID is an open standard and decentralized authentication protocol AD Active Directory is a directory service developed by Microsoft for Windows dom ain networks MFA Multi -factor authentication mTLS Mutual TLS, is a method for mutual authentication TLS Transport Layer Security (TLS), is a cryptographic protocol designed to provide communications security over a computer network. SIEM Security Information and Event Management SCA Software composition analysis SSH Secure Shell RDP Remote Desktop Protocol VNC Virtual Network Computing SSL Secure Sockets Layer JWT JSON Web Token RBAC Role Based access control HTTPS Hypertext Transfer Protocol Secure CA Certificate Authority OWASP Open Web Application Security Project",, "CARE Security White Paper HCLT Confidential Page 3 of 15 Table of Contents PURPOSE ................................ ................................ ................................ ................................ .... 4 WHAT IS CARE? ................................ ................................ ................................ .......................... 4 DEPLOYMENT MODEL ................................ ................................ ................................ ............... 6 NETWORK COMMUNICATIONS: ................................ ................................ ................................ 7 IDENTITY AND ACCESS MANAGEMENT ................................ ................................ .................. 8 DATA ENCRYPTION - TRANSIT AND AT REST ................................ ................................ ........ 9 DEVICE ACCESS CONTROL ................................ ................................ ................................ ...... 9 KEYS AND SECRETS ................................ ................................ ................................ ................ 10 CERTIFICATE MANAGEMENT ................................ ................................ ................................ . 10 AUDIT TRAIL ................................ ................................ ................................ .............................. 10 CARE DEVELOPMENT AND RELEASE PROCESS ................................ ................................ 11 DEPLOYMENT CONSIDERATIONS ................................ ................................ ......................... 11 CARE SECURITY CONTROLS - SUMMARY ................................ ................................ ............ 12",, "CARE Security White Paper HCLT Confidential Page 4 of 15 PURPOSE HCL’s CARE (Connected Assets in Regula ted Environment) Platform is a micro-services architecture featured multi - tenant platform that helps in building a regulated medical device connectivity software ’ within a significant reduced time. CARE has been designed and built incorporating cybersecurity b est practices from industry leading resources such as the National Institute of Standards and Technology (NIST) Cybersecurity Framework and Open Web Application Security Project (OWASP Internet of Things IoT Framework), etc. Throughout the platform design and development cycle , threats were account ed for, requirements were built -in and robust testing was performed . The purpose of this document is to detail how the security and privacy practices have been applied within the CARE platform, and the considerations for the solutions being built using CARE platform . WHAT IS CARE ? ➢ CARE brings together business application building frameworks, device connectivity, re-usable software components to provide acceleration to the development of software / platform s. ➢ CARE is primarily a micro-service s based framework to build edge/gateway applications as well as scalable cloud hosted applications. ➢ CARE provides services to handle standard application needs such as Identity and Access Management , Audit and Logging , Email /Text notifications. ➢ CARE supports Hierarchical Multitenancy, data access controls and tenant data isolation. ➢ CARE provides services for remotely connecting and managing customer’s devices that are deployed to facilities that end customers own and operate. ➢ CARE comes with Device Gateway with store -n-forward data exchange, device integration framework and command handling modules. ➢ CARE supports remote device management capabilities , which includes: ▪ Remote software deployment ▪ Remote SSH/RDP/VNC Session with recording",, "▪ Remote SSH/RDP/VNC Session with recording ▪ Remote diagnostics and command execution ▪ Remote file system access ➢ CARE provides templates for building additional multi -tenant aware micro -",, "CARE Security White Paper HCLT Confidential Page 5 of 15 services as per the application needs . Micro -services architecture can be leveraged to isolate the regulated software components & medical data within the application services & data. A typical CARE based solution can be depicted as shown below :",, "CARE Security White Paper HCLT Confidential Page 6 of 15 DEPLOYMENT MODEL Here is an overview of various high level components of CARE deployment : Gateway Gateway provides secure connectivity and data exchange between multiple medical devices and the Cloud. It enables network isolation between medical device s and the Cloud thus protecting the medical devices from direct connectivity to the external network or internet. It also provides the capability for local processing and/or caching of data before it is transferred t o the Cloud. It is installed on premise within the hospital /end-customer network and typically can be deployment either as a hardware box OR as a software installed on any hospital/end -customer system meeting the specified requirements. Typically, it can be deployed on any machine with minimum 4GB memory and supports Windows and Linux based OS . Agent Agent runs on the medical device and facilitates communication between the medical device and gateway. It ensures secure and reliable data exchange between medical devices and the ga teway. It is typically distributed as part of medical device software itself . Typically, d evice agent can be deployed in any system with 2GB memory and supports Windows & Linux based OS . Cloud Cloud provides the functionality required to on-board/manage c ustomers, manage users and their access, register gateway and devices, manage/access gateway and devices, perform remote s ervice operations and other custom capabilities implemented",, "CARE Security White Paper HCLT Confidential Page 7 of 15 on top of CARE . It includes the web -based interface s and the backend services required to provide these functionalities along with the hosting infrastructure . Typically, the cloud services are deployed in a customer owned public cloud environment like Azure/AWS/Google. NETWORK COMMUNICATION S: All network communications done by the platform are performed over hardened TLS 1.2+ channels with mutual authentication wherever applicable . Here are various connections and how they are secured : Device and Gateway : CARE Agent on the medical device establishes an SSL -encrypted connection (TLS v1.2) to the Gateway on port 443 (configurable). This connection uses mutual certificate authentication. Gateway and Cloud : The Gateway establishes an SSL -encrypted (TLS v1.2) connection to the Cloud via port 443/ TCP. Only an outgoing connection via this port is required . This connection uses mutual c ertificate authentication User to Cloud Portal : User can access the Cloud Portal only on successful authentication and authorization. Connection from end u ser’s browser to Cloud is over HTTPS via port 443. User to Device Remote Access : After successful authentication and authorization to the Cloud Portal , an user can connect to the allowed Gateway and medical devices via the secure communication channels (using SSL encryption via TLS v1.2) already established between Gateway and Cloud , and Device and Gateway . .",, "CARE Security White Paper HCLT Confidential Page 8 of 15 IDENTITY AND ACCESS MANAGEMENT One of the most important securi ty controls for any solution is to allow only authorized users access to perform operations within a system. Authentication Users are individually identified through unique accounts and require authentica tion via username and password prior to being permitted access to the CARE application . All user accounts are centrally managed . CARE platform supports following authentication mode . Standalone : This is the default mode of authentication using standalone accounts setup at the CARE platform level. The platform provides a number of standard security controls to ensure all user accounts and passwords are managed appropriately. ▪ Support for OTP and/or TOTP based MFA ▪ Account Lockout/Brute force attac k protection ▪ Support to c onfigure and enforce password policies – password complexity requirements , password expiration and reuse restrictions ▪ Secure Password Reset and Recovery mechanism ▪ Support to disable inactive accounts based on the inactivity period configured ▪ Passwords are stored in an encrypted format Delegation : Authentication can be delegated to the external/customer identity providers using standard protocols like Open ID, LDAP/AD thereby automatically enforcing all the ir account management policies. Custom: CARE supports custom plugin to validate the passwords with external database and systems. Session Management CARE Cloud uses encrypted JWT token for stateless sessions. No sensitive information is disclos ed in the token. Session timeouts and UI inactivity timeouts are also implemented. Authorization Authorization to functions in the CARE application can be enforced using role - based access control (RBAC). RBAC is implemented in CARE using a user to roles to permission s map. All services can be configured to access only by users with",, "configured to access only by users with necessary permissio ns. Applications using CARE can define custom roles as per the ir need. While defining roles, it is recommended to consider Principle of least privilege .",, "CARE Security White Paper HCLT Confidential Page 9 of 15 TENANT ACCESS AND DATA ISOLATION CARE platform deals with the devices/data belonging to multipl e hospitals/customers also typically referred as tenants. Multi - tenant systems need to ensure containment and protection of a tenant data and its access from other tenants on the platform . CARE provides a couple of options for tenant isolation – logical isolation within a shared database/storage by tagging each record with a tenant identifier/context or full isolation using tenant specific database/ storage. CARE m ulti-tenant data access control s ensures that tenant’s data i s isolated at framework level and access to the data is restricted based on the logged -in user tenant context. Cross tenant data access is however possible by specifying tenant access control policies. SENSITIVE DATA HANDLING AND DATA DE-IDENTIFICATION For handling any sensitive data received from a device , CARE provides option s to either allow the sensitive data to cloud or de-identify the data before sending to cloud. This can be controlled at an individual gateway level by configuring the data transfer settings. Any sensitive data is always transferred over a secure connection and can be configured to be stored within the region and in an encrypted storage . Additionally, access control s can be configured to allow access to sensitive dat a only within the region to meet data residency needs and also control who can access the data . All the data access operations can be audited as well. DATA ENCRYPTION - TRANSIT AND AT REST All communication s done by CARE platform happens via Transport Layer Security (TLS 1.2 or higher [configurable] ) to secure data in transit . TLS tunnel can be configured with industry standard ciphers. To secure data at rest, CARE can be configured to use the encryption capabilities of the cloud platform s where it is deployed . DEVICE ACCESS CONTROL",, "is deployed . DEVICE ACCESS CONTROL Device to user mapping can be configured to ensure only authorized users can access the device. On -demand access can also be enabled through an approval workflow and with specified expiry interval . All the device a ccess operations are audited as well. INTEGRITY & AUTHENTICITY CARE leverages transport security (TLS 1.2+) for integrity of the data transferred over network. Additionally, gateway can be configured to digitally sign each message",, "CARE Security White Paper HCLT Confidential Page 10 of 15 that is sent from gateway/device to cloud. To ensure integrity of the update packages rolled out through CARE platform , validation of digital signatures can be enabled at the gateway . KEYS AND SECRETS CARE Cloud supports integration with secure Key Vault capabilities of the cloud platforms to store keys and secrets. It uses password protected keys at Gateway while also ensuring proper file permissions to secure the keys . And the platform maintains no hardcoded keys/secrets. CERTIFICATE MANAGEMENT CARE uses digital certificates to protect the authenticity, confidentiality, and accuracy of data transferred to and from the devices through the use of industry standard encryption and certificate -based authentication. User connections to the Cloud portal are also protected by digital certificates supporting latest industry standard encryption. Device and Gateway certificates are signed by a private root of trust. Update packages to be signed by a trusted Code signing Cert. Cloud Portal cert to be signed by a public CA. AUDIT TRAIL CARE Audit Trail components can be configured to log security events such as user account changes, ac cess privilege changes, specific data access and device operations like remote access, file transfer or software distribution performed on the gateway and the medical devices through the Cloud Portal . The audit trail includes a date and time stamp of the operation as well as user identification. Furthermore, when using remote desktop tool (VNC), the entire session can be recorded as a screen recording. Audit trails can be configured to be retained as p er the security and regulatory requirements. Additionally , all the audit trails and platform logs can be pushed centrally to enable monitoring , analysis and al erting capabilities . REMOTE SOFTWARE DEPLOYMENT CARE Software deployment feature is designed to enable automatic/manual",, "designed to enable automatic/manual patches, software upgrades in the connected devices. It provides cloud & gateway modules which are responsible for rolling out the patches from cloud to the devices to address security and stability issues. Rollout is a controlled process with approval workflow and can be performed only by authorized users.",, "CARE Security White Paper HCLT Confidential Page 11 of 15 CARE DEVELOPMENT AND RELEASE PROCESS CARE software is developed using HCL’s defined medical quality m anagement system which is based on ISO 13485. And all developers have undergone Risk Management - ISO 14971 and SDLC - IEC 62304 trainings . Source code analysis is done using SAST tools before every release. Software Composition analysis is done to identi fy vulnerabilities in the open -source components and reviewed before each release. Penetration testing and security assessment for the platform is done by internal security testing CoE team. Regular monitoring for known vulnerabilities is done using industr y standard SCA tools and upgraded as needed. DEPLOYMENT CONSIDERATIONS The following should be considered as part of CARE application deployment and operational procedures: • Enable MFA and strong password pol icies as per the business needs. • Ensure that all product services are using the latest version of CARE platform. • CARE supports TLS 1.2 and higher. It has to be ensured that proper TLS versions and strong ci phers suites are enabled as part of deployment . • CARE Gateway and CARE Device Agent communication is secured via TLS and Certificate authentication. But not all deployment model s use CARE Device Agent. In such a case, CARE Gateway and the device communicate directly and it has to be ensured that the certificate authentication is supported by the device software . • Cybersecurity best practices involves a layered approach also referred as Defense in Depth to protecting systems such that a violation of any single control does not lead to a breach of the system. This involves controls at the system perimeter, controls embedded in the runtime environment, and controls embedded in the application layer. Considering this, it is recommended to ensure proper controls are put in place as",, "CARE Security White Paper HCLT Confidential Page 12 of 15 part of infra hardening in addition to the application level controls provided by the CARE platform. These controls typically include but are not limited to Firewall for perimeter protection, WAF for payload inspection, IAM for infra and administrative access, Centralized logging and monitoring, SIEM, application gateway with hardened TLS config urations and network segmentation . • Responsibility of monitoring of operating environments are not with CARE product team. Customer should ensure that product environment is well monitored, protected from malware and external accesses. Internal (support/operations team) access also should be restricted and audited. CARE SECURITY CONTROLS - SUMMARY ✓ Authentication (including MFA and SSO) ✓ User, Role, Permission mana gement and role based access control ✓ Audit Trail to track all key events ✓ Secure device on -boarding, and X509 certificate based authentication. ✓ Device gateway eliminates the need for inbound access from cloud to the enterprise/internal network. ✓ Device g ateway also isolates internal and external network and avoids devices getting exposed to cloud. ✓ Multitenancy, and tenant level access control ✓ All device to cloud communications are performed over mutually authenticated secure channel. ✓ Built -in controls for addressing OWASP top threats. ✓ Integrity and Authenticity of device software updates using digital signatures ✓ Enables data encryption and secure key storage by integrating with Cloud platform services. PLUG CARE PLUG is set of pluggable Security Modules for enhancing Data Privacy and Cyber Security of a medical applications that is fi eld. Purpose of PLUG is to the externalize application level security controls , and it is not a replacement for a network level security",, "CARE Security White Paper HCLT Confidential Page 13 of 15 mechanisms such as firewall, IDS or WAF. It has controls/modules for Parsing AWT, enabling role based access control, geo based access control, time based access control, X509 authentication va lidation , validating use consents, anomaly detection (work in progress), data masking, data tokenization , digital signature generation and validation, ePHI/FHIR/PII Detection , Audit/Logs, Notif ication, Text replacement etc . Also, customer controls can be built very quickly. Controls can be stacked, with a pre-condition based on the out from the other controls. PLUG @ WEB Gateway PLUG @ Device gateway",, "CARE Security White Paper HCLT Confidential Page 14 of 15 De-identification / tokenization using PLUG @ HTTP gateway – illustration",, "CARE Security White Paper HCLT Confidential Page 15 of 15 De-identification / tokenization using PLUG @ device gateway – illustration",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT -",, "2| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comSignificant Market Trends in Digital Adoption in MedTech… Covid Induced Business Challenges has accelerated adoption of connected medical device ecosystems . Regulatory compliance needs (MDD and MDR) have forced Med Tech companies to evaluate their entire application landscape identify, re -validate and certify those apps found to be designated SAMD.Connectivity is a red ocean space. Current innovation focused on leveraging data in the following areas: ▪Patient Engagement & Intervention ▪Remote Patient Monitoring ▪Device & Service Management ▪Data Product MonetizationAI/ML technologies are being increasingly adopted to support clinical decision. Adoption is enabled by using Data Synthesis / Federated Learning mechanisms to ensure regulatory compliance from a patient data perspective. Cyber attacks on major health systems have quadrupled . Cybersecurity is the major focus areas given the vulnerability of device/patient data on connected ecosystems. We are increasingly addressing DevSecOps opportunities with our customers.",, "3| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comLeading to adoption of following Use Cases Digitizing and Aligning Internal Processes for Maximizing Monetization Digital Ontology Creation and Data Hub Creation Interconnected devices for improved clinical interventions Closed Loop Systems Tele Medicine / Remote Patient Monitoring Smart Enabling old medical devices without going through Product Changes and FDA",, "4| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comOur Medical Digital and Analytics Practice is Solution Rich Skill & Experience #1in Medical Devices services and capabilities across IOPs 40+ Customers NVDIA, Intel, MSFT, AWS, GCP, PTC, John Hopkins, Ramachandra University PartnershipsExpertise in domains - Orthopedic, Hospital Equipment. Cardio, Diabetic Care, Surgical, Lungs etc1500+ Digital Engineers and 1200+ Analytics & AI Engineers 100+ Regulatory ConsultantsDigital Assets AI-ON CARE Eco System Next.ai IOT Collab, Cognitive Intelligence LabsMobile Solution Accelerator, MMTAF AI Solution Accelerators CARE Data Grind – Patient Data Management & Monetization PlatformAnalytics Offerings Analytics ConsultingAI / ML Model Development Data Engineering Data Architecture, Data IntegrationAI Data Operations Data Quality Management Data MonitoringData Compliance HIPAA, GDPR, HI Trust, Safe harbourManual and Automated Curation EnginesData Curation Statistical Models Supervised & Unsupervised Data As a Service Anonymized Field Patient DataProfessional Service Tech Staffing SolutionsNew Product Development End-End Engineering Services Use case Creation Prototypes",, "5| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comThe CARE Eco System Solution is modular…. Data Visualizer Medical Analytics Data Visualizer on Azure MLData Grind Data Orchestration and Monetization Solution Service Agent A Plug -N-Play integration solution for managing External Integrations – Thirdparty cloud, EMR, Smart Device Connect Plug-N-Play Smart Devices Connectivity Solution – On- Board new devices RapidlyPlug – Cyber Security Engine A pluggable Security Module for Data Privacy and Solution Cyber Security Management Device Workflow A solution for creating Clinical Workflow of devices that share data seamlesslyService Manager Log, User and Telemetry data gathering, assessment and analytics platform CARE Eco System 1 2 3 45 6 7 8Patient Engagement Micro Platforms Patient CARE and Adherence Management",, "6| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comAnd Collectively CARE Ecosystem will provide Customers with… Clinical Intelligence Process Intelligence Realigning Internal Processes to deliver Effective Returns on R&DDelivering Customer Experience through Intelligent Clinical InterventionsDelivering Cost Optimizations through Intelligent Service Interventions iServe PLUG teleCARE Data Grind AI . ON Device Connect AI . ON PICASSO Service Intelligence",, "7| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE is Market Proven Medical Device Data Manager Smart Enabler Medical Device Gateway Remote Patient Monitor About Impact Pride Delivering30 $03Brevenues enabled for customers 6OF TOP 9 Years of Existence| 32 Countries | Across 5 continents | 16+ Million Investment| 150 K connected devices| 7 Patents 10 MD 25Health care + other industry",, "8| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE is Endorsed by Customers and Hyperscalers like Microsoft https://www.microsoft.com/security/blog/2022/03/14/secure -your -healthcare -devices -with -microsoft -defender -for-iot-and-hcls-care/",, "9| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE has enabled Real Time Neuromodulation Alerts for Global Medtech Co Remote Stimulation Programming over Azure Cloud Real Time Stimulation adjustments to even remotest parts Telehealth Reimbursements Multi Layer Security Multi Safety Classification simplifying filing and improving innovation Real Time video pipeline for Analytics",, "10| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE has enabled Component Failure Identification and Prediction, using Sensor Data •Parameters are tracked from each Sterilization Cycle •Faults are displayed in the graphical form for the service Engineers •Age of the various components are tracked •Data fed to a prediction algorithm that determines the probability of failure for each components and when crossing threshold raises the alarm",, "11| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE has powered a Cardiac Rhythm Realtime Event Management Platform Cloud GatewayGlobal Cloud Platform Clinician portalAdmin Portal Cert/Token/C redentials Config Gateway Policy Device RegistrationAuthenticate EnrolmentHDF HDM Decompress Filter XMLTUSave Files Device Workflow Push SQL HDFSFHIR Data Model Stream Analytics (HOT) Kafka Storm Accumolo (Near time analytics)ePHI Data HDFS HIVE Hadoop Map ReduceKnox Oozie WebHDFSYARNMicro ServicesAdministration EMAIL/SMSEvent DB Live EventReports",, "12| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE has enabled Drug Adherence For Multiple Sclerosis Infusion Large European Pharma Customer 8 Billion USD Market SharePreferential Drug Push by PayersPatient Provider Pharma Payer EcosystemRemote Programmable Drug Adherence Patient/Clinician Tech Providers IT R&D , Clinicians Cyber SecurityGDPR / HIPAA Cyber Security/ MonitoringAI/ AnalyticsReal Time Notifications Data Ingestion Clinical WF Integration Adherence Reports Payer Integration",, "13| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE has enabled Post Surgery Adherence 1 •EMR Lite •ePRO •Setting Up /Supply Chain •Data Driven Assessments •OR Planning •Integrate Implant partner2 OPTIMIZE COST/ IMPROVE OUTCOME•Register Implant •Secure Channel •OR Programming3 TRACK IMPLANT4 •20 Years of Data •Engaging Patients •AI Driven Decisions •Learning Feedback MONETIZE DATAWELLNESS GATHERING/ PATIENT INTELLIGENCEDATA DRIVEN SURGICAL PLANNINGLIMITLESS ADHERENCE TRACKINGOR PROGRAMMING KNOW THE PATIENT Partner/ Payer Dashboards HCP Dashboard Patient Dashboard LEARNING DRIVEN OR PROGRAMMING DAT A MONETIZATION LIFE LONG MONITORING Raising above the patient compliance needs for RPM, the solution tracks compliance data for 20 straight years providing a mon etization realization of 2 USD Per Day Per Patient (Million Implant surgeries happen every year). The RPM detects patient adherence to post surgical regime allowing clinicians to intervene thereby obviating the need for readmi ssions. The gathered information is useful to the Payers in reconstituting insurance policies",, "14| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE CARE is a powerful software framework that has the necessary building blocks for building next generation medical multitenant software / services faster . CARE brings together business application building frameworks, device connectivity, re-usable software components and best practice templates to provide acceleration to the development of software / platforms . It can be used to build both edge/gateway applications as well as scalable cloud application Microservice based framework to build both edge as well as cloud applicationsHandles basic needs such as Authentication, Authorization, Audit, Logs, Email template etc.Supports Hierarchical Multitenancy, data access control, tenant data isolation Application building templates for REST - API, device management, edge gateway, Integration, device agentRemote device diagnostics/monitoring •Remote patching •Remote ssh and screen -sharing session •Remote file system access •Remote logs and command executionNo code/low code modules for device interaction, data anonymization & transformation, and business application buildingCARE",, "15| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.com CARE Cloud Hospital/Partner Network Smart Gateway Device interaction • Device life cycle management • Device inventory • Software update management • Remote diagnostics • Consumables management • Tracking usage, monitor uptime • Store -n-Forward • Command agent • Data flow orchestrator • Offline administration and data/event/workflow manager Options: • Appliance in a Box • Software appliance – OVA • Installable in PC/Laptop • Integrated with Device Device 1 Device 2 Device n Business Application • Collaboration between stakeholders • Task, process, approval workflow • Subscription, milling , meteringCARE – Deployment",, "16| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE - Modules CARE Cloud Services •Business workflow and application •Device management •Remote access •Patch management CARE Device Gateway •Device connectivity •Data & file handling •Patch handling •Care integrator •Isolation CARE Device Agent •Patch agent •Remote access agent •File push •Device integration Lightweight (60 MB RAM, 400 MB HDD). Works in Linux/Windows. Low code integrationOptional & Lightweight. C++, .net, nodeJS versions. Scalable. Kubernetes based horizonal scaling, device data handling using PaaS services.",, "17| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE - Functions Device Care framework Field/Remote Support Patent Care framework Health data handling",, "18| Technology for the Next Decade, Today Copyright © 2022 HCL Technologies Limited | www.hcltech.comCARE deployed in Azure Device CARE Gateway [Linux/W indow s/Appliance]IoT Hub SDKMQTT Or MQTT over W ebsocket (Push messages to Device) CARE ServicesCARE gateway base modulesW eb socket Support EngineerHTTPS / HTML5TLS1.2+ with X 509 Cert A uthentication TLS 1.2+ Enterprise/Private netw ork (F irew alled)CARE Device Agent •Remote file browsing and upload v ia browser •RDP/VNC/SSH access v ia browser •Automated Session Recording •Remote command execution •Logs/telemetry data collection •Remote Patch update •Store -n-forward •Dev ice/E MR integration framework Business user HCP PatientCARE Remote diagnosticsCARE : High -level architecture CARE Device integrator / Anonymization / Tokenization IoT defender AgentRESTIoT Hub Event HubStream AnalyticsData Lake SynapseAKSSQLPower BI Gateway/ WAF Gateway/ WAF AD Signal R Azure Services CARE ServicesKey VaultApplication InsightTime series IoT defender AgentBlob StoreIoT Def ender Healthcare API PII data",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT ™ Datasheet",, "COMPONENT REQUIREMENT Processor RAM Operating SystemTECHNICAL REQUIREMENTS HDD Free Space Java Other software Pre-requisites Access requirements--------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Copyright © 2021 HCL Technologies Limited | www.hcltech.comCARE Hello there! I am an Ideapreneur. I believe that sustainable business outcomes are driven by relationships nurtured through values like trust, transparency and flexibility. I respect the contract, but believe in going beyond through collaboration, applied innovation and new generation partnership models that put your interest above everything else. Right now 110,000 Ideapreneurs are in a Relationship Beyond the ContractTMwith 500 customers in 31 countries. How can I help you? 64-bit processor: Intel Core i3 or equivalent 8 GB RAM (preferred 16GB) Any 64 bit Windows/Linux/Ubuntu 100 GB min (preferred 500GB) Minimum JDK 8, recommended JDK 11 PostgreSQL/MSSQL ActiveMQ/RabbitMQ Native MQTT/Azure IoT Hub Optional -Docker, Kubernetes System should be accessible to all resources expected to use CARE application",, "Copyright © 2021 HCL Technologies Limited | www.hcltech.comPRODUCT SALIENT FEATURES PRODUCT OVERVIEW HIGHLIGHTS--------------------------------------------- • Standardized and Integrated Best of breed technology stack . • Multiple Architecture support • Docker integration and packaging support fordifferent deployment models . • Asetofautomation tools fordevelopers tobootstrap, develop, test and deploy software and applications . • Complete Device Management services for your device connectivity needs, device remote diagnosis and management . • Audit Trail and Smart Remote Assist .Multi Tenant and Sensitive Data Handling •Helps in multi tenant & multi geo deployment •Hierarchical Multi Tenancy •Geo Data Fencing •Data Masking/ Tokenization@cloud •Data Tokenization/ masking@device gateway Remote Access •Access devices (RDP/VNC/SSH) from browser via cloud with session recording •Remote file browsing •Remote commands •Access Device gateway UI from cloud •Access Integrator UI from cloud for troubleshooting •Remote camera view (mobile based) for field support Device Gateway •Key for medical devices deployment environment to avoid direct internet connectivity •Handle offline status gracefully •Store -n-forward •Patch File download •Ready to use module for Windows IoT and Linux Device Agent •Optional -works with device gateway •Agent for remote access and patch handling •Azure Power BI •Azure Data ExplorerCARE platform has been built overHCL’s powerful software suite that provides necessary building blocks for building next generation software/services faster .CARE brings together packaged application frameworks, re-usable software components, automation tools for developers &testers, support forbest ofbreed architectural patterns and best practice templates to provide acceleration to the development ofsoftware/platforms .Presentation Layer Web PortalCONSUMPTIONCONSMPTION ANALYTICS ETLKnowledge Articles, Title, Summary, ResolutionIssue Occurances –Interval wise, E - Com DataKnowledge Articles, Title,",, "wise, E - Com DataKnowledge Articles, Title, Summary, ResolutionIssue Occurances –Interval wise, E - Com Data Telemetry Data SourcesEnvironment DB/CRM/ CSAT DBCARE Integrator •Support all standard and medical protocols •Configured to interact with existing devices •Definitions at device type and gateway level •Cloud managed. •Changes can be pushed to gateway anytime. HCL Services •Offers customization and integration services. •Building custom services for customer. •Years of experience with different classes of devices. Reusable Components •Authentication and Authorization •Roles/Permission Management •Audit Trail, Restore, Patch Management Key Integration •OpenID, LDAP , EventHub, Azure Active Directory Supported Platforms •PostgreSQL, MSSQL •RabbitMQ/ActiveMQ •Native MQTT/Azure IoT Hub",, "4|Copyright © 2021 HCL Technologies Limited | www.hcltech.comBuilt using CARE reusable modules which has all platform capabilitiesRemote Support ServerBusiness App (Optional) IoT BrokerWeb User InterfaceRDP/VNC to HTML5Remote Tunnel Agent Support Engineer Business user HCP Patient IAM RBACUser Management Tenant ManagementNotifications Customization Remote Support Device ManagementData Store: RDBMS, Blob, NoSQL, In - MemoryRest based ReportsCase ManagementPatient Adherence AuditData IngestConsent ManagementPatch ManagementRemote Assist DeviceRemote -Support GatewayRemote - Support gatewayRemote - Support agent VNC/RDP/ SSH Server VNC/RDP/S SH Server Bash, CMD, PowerShell [Optional] Remote Support Agent •Remote file browsing and upload via browser •RDP/VNC/SSH access via browser oAutomated Session Recording •Remote command execution •Logs/telemetry data collection •Remote Patch update •Store -n-forward •Device/EMR integration framework Business App (optional) Device integration MQTT (or) MQTT over Websocket (Push messages to Device)TLS 1.2+ with X 509 Cert Authenticat ionWeb socket TunnelingTLS 1.2+Built using CARE reusable modules such as IAM, Audit, Notification, Metadata, App templates etc. Recording done hereCARE : HIGH LEVEL ARCHITECTURE",, "CARE Connected Assets in Regulated Environment ™ COMPETITIVE ANALYSIS",, "CARE TM-COMPETITIVE ANALYSIS Feature PTC Axeda / ThingWroxHCL CARE FLEX Capsule Intelligent Care Platform Access Control Multiple Access Control Mechanisms only at device levelMultiple including certificate, token, and Credentials Based Advanced and extended Access Control Mechanisms such as OAUTH, User Binding, Credentials Policy ManagementMultiple Access Control mechanisms only at device levelStandard Access Control Mechanisms Device Integration Elaborate Custom CodeDynamic Plug -N-Play Custom Code Has excellent out of the box interfaces for wareform image integrations Remote ConnectivityA Local agent based tunnelingNeeds no agent to downloaded. Browser based Remote AccessX A Local agent based tunneling Software Upgrade Provides multiple Software push mechanisms from cloud. High customizations needed. Not Medical Grade.Manages Software upgrade comprehensively Patch Push, Controlled Installation, Diagnostic ModeProvides multiple software push mechanisms from cloud. High customization needed. Not Medical Grade.X Cyber Security Limited to device levelComprehensive –Implements NIST ControlsImplements NIST ControlsLimited to device level Openness Closed Model - Data goes to PTC CloudOpen -Data is owned by customer. Closed Model –Data goes to Flex Closed Model –Data goes to own Cloud Cloud InteroperabilityPTC, Azure & AWS CloudAWS, Azure or Private Cloud – Integrates well with customer strategy, policy and relationshipOpen Cloud X Gateway Model Software only Mobile, Hardware, Blade and Software Gateway optionsSoftware Only Software Only Backup -Restore X Allows on premise and cloud -based backup restoreX X On-Premise Mode X Supports On -Premise only, Cloud and Cloud ModeX X Service Monitoring & ReliabilityX Advanced Monitoring capabilities ensuring High availability and system reliabilityX Has advanced monitoring capabilities On-Premise IntegrationsX EHR, PACS, LIS Integrations EMR/EHR integration capabilitiesEMR/EHR integration capabilities",, "capabilitiesEMR/EHR integration capabilities Multi -Tenancy X Supports Hierarchical Multi Tenancy Supports Multi Tenancy and not hierarchical multi tenancy X Editions & Entity ExtensionsX Ease of managing data extensions. Helpful in regulated environmentX X Medical Device SpecificX Built for Medical Devices Industry Has good medical device overlap. However falls short in areas like software upgrade, micro products approach etcHas good medical device overlap. However falls short in areas like software upgrade, micro products approach etc Micro Services X Micro services and Micro Products ArchitectureMicro Services Compliant X",, "CARE TM-COMPETITIVE ANALYSIS Feature PTC Axeda / ThingWroxHCL CARE FLEX Capsule Intelligent Care Platform Development PlatformX Bundled Connectivity and Development PlatformX X HIPAA Compliance X Compliant Compliant Compliant GDPR Compliance X Compliant Efforts are on. X High Speed Data PipelineX High speed Data Integration (Million Records)X X Audit Trails X Audit Trail Recorder and Viewer X X Event Architecture X All Events are queued –Helps in Custom Apps DevelopmentX X Ease Of Regulation X Simplifies Regulation with Micro Products ArchitectureMedium X Safety ClassificationX X FDA Approved, CE MarkingX Adherence ManagementX Needs Customization Real Time Adherence DashboardX Patient Consent ManagementX Built in Consent Management X X Patient Data EncryptionX Built in Automatic Encryption Custom Code X User Interface ThingWorks provided UICustom Development Flex provided UI Capsule UI Degree of CustomizationMedium Very High Low Low Ownership of Patient DataLow Very high to Company Low Low TCO Very High Lowest TCO Low for higher volume>75K patientsHigh Collaboration Very Low Very High Low Low",, "CARE TM Connected Assets in Regulated Environment ™ BATTLECARD",, "CARE TM – BATTLE CARD Key Features: •Device Connectivity: CARE comes with reusable modules that are cloud -provider agnostic, to build on premise smart gateways and cloud servers. Customizable remote diagnostics, patch rollout capabilities are inbuilt. •Data Management: Data retrieval and encryption are important to ensure efficiency of your operations. CARE comes with robust Data management to store, retrieve, encrypt, import, and export data, thereby directly enhancing operational efficiency. •Standardized Architecture: Rather than have you design and experiment with new architectures, HCL offers you a proven and time -tested architecture. •CARE’s AppBuilder Gen -AI feature is built on top of latest LLM (Large Language Models) models, to aid development of backend microservices as well as frontend. •Automated code generation for domain models, workflows, UI, service etc., which reduces overall efforts and coding errors. The AppBuilder Gen -AI provides features of db design, requirement design, editor & others. •In-built Multitenancy capability with data access policies that enable you to build SaaS and multi -geo applications quicklyElevator Pitch: CARETM provides customers with a micro services -based next generation medical software platform for launching global business services with 52% cost reduction and 31% accelerated software development. Audience: Horizontal Proposition, applicable to All ERS Specific Verticals that need launching global business services through a scalable cloud platform. This could be a fresh product development or migration of existing monolithic applications that are not cloud ready.Product Positioning When to Engage • Fresh product development or existing product migration/re - engineering to cloud -based application. • Dual deployment approaches – Build once, run on premise and on the cloud. When not to Engage • Maintenance (ADM/PDM) projects Business Challenges :",, "Business Challenges : Traditional companies (that are not yet fully digital) are being pushed to create core software services. These companies are risk averse for a big bang approach and look at incremental innovation • With high pressure on cost and time to market, it is difficult to approach software as a “wholistic” solution. Tactical dec isions always take priority over strategic ones in most cases • Without a “reuse/foundation” approach to software, organizations end up having significant redundancies in infrastructure, licenses, people, and processes, thus leading to inefficient delivery of services • Creating a platform that can act as a foundation to launch business services requires significant investments in terms of c ost, skill and time • A global service creates different code base of comparable functionalities, thus leading to increased cost of maintenance o f these applications Business Benefits: Industrialization : ✓ Promotes the use of commoditized skills to perform complex jobs ✓ Standardization across Technology and Engineering process Acceleration: ✓ Automation to ease code development ✓ Reusable components accelerate software development by at least 31 % Quality Enforcement: ✓ Pre-built components driving “Get it right first time” benefits ✓ Best practices enforcement through design itself Total Cost of Ownership: ✓ Platform based approach reduces the cost of building new services by up to 74% with enhancement using Gen -AI, at design/coding stage itself",, "CARE TM – BATTLE CARD Differentiator: In-built tools, workflows, rule engines, libraries, etc. enable rapid creation of multi -tenant apps and the conversion of single tenant apps to multi -tenant apps •Easy on -boarding of new countries/entities with easy -to-use configuration sans any additional development effort •Uniform platform to support different stakeholders •Extensibility to address data model extensions specific to country/brand/branch •Configurability to alter workflows, business rules, validations specific to country/brand/branch Access control to enable fine grained control to different functions of the application •Support for single instance and distributed deployment models •Drag and drop application development and in-built packaging and containerization support for rapid application development and deployment •CARE’s AppBuilder Gen -AI feature is built on top of latest LLM (Large Language Models) models, to aid development of backend microservices as well as frontend. SOLUTION HCL DIFFERENTIATOR COMPETITOR WEAKNESS CARETMProvides a single platform for both on premise and cloud hosted solutions.Cost of development is higher due to licensing cost of commercial automation tools CARETMMicroservices architecture support providing higher scalability/flexibility Deployments are generally tightly coupled with specific cloud/virtualization environments CARETMGen-AI features ensures the code quality, with relatively less bugs, readable, with comments, with unit testing.Time to develop quality code are more. OBJECTION RESPONSE No such immediate requirement (Scaling required in future based on business growth) •Start small and grow as your business grows. Using CARE, you build once and run on premise and/or on the cloud. •Customer can start as a small on -premise application and move to cloud (adding newer services while catering to multiple customers /geographies) as the business grows. •Existing monolithic applications hosted as independent/discrete",, "services can be clubbed and launched as a single solution thus greatly reducing the maintenance & operational costs. Customer is against using Open Source•CARE is built using technologies, where the commercial support can be bought when required. •Open -Source technologies help in reducing the overall all development and operational cost.",, "CARE TM – BATTLE CARD FAQs : Q: What is the technology/language used? A: The platform is based on Java/J2EE, existing application written in other languages can be integrated with platform using restful APIs. Supports Java, NodeJS, ,net core based microservices and react based frontend. Q: What kind of services can be built using CARE? A: CARE is a horizontal platform accelerator. It can be leveraged to build anything from device -based cloud services to patient management healthcare platforms, to insurance platforms. Q: I have an existing product. How can I use CARE? A: CARE can be used to re -engineer legacy products. However, CARE cannot be leveraged for maintaining an existing product. Q: Is CARE Free? A: CARE is not free. It has a license cost involved and requires the customer to sign an agreement for the T&C of CARE (allowing HCL to sell CARE to other customers). Q: My customer does not want Open Source; can I still position CARE? A: “Open Source” is used in a variety of ways. CARE is built using technologies, where the commercial support can be bought when required. Therefore, it is as good as commercial software where required. Q: Is CARE a product? A: CARE is not a product. It is a solution accelerator that we use to deliver complex projects in a consistent and shorter timeframe.Q: What is the support model for CARE ? A: Typically, support model is included as part of the project support (of the customer project we develop on top of CARE) while we sign up with the customer. However, there are models, where separate dedicated support can be planned for. Q: Would my customer receive updates to CARE as new releases are made? A: New releases can be leveraged by existing CARE Customers. Q: My customer wants access to source code. Should I still go ahead and position CARE? A: Access to source code can be provided on an exception basis for additional cost. However, any change to the base source code will void the customer from getting further",, "access to new releases as it would not be possible to track the changes and support that code too. Q: My customer wants more features than what is available in CARE. What should I do? A: Typically, custom features can be built as part of the implementation by delivery teams. However, in cases where features add true value to the platform and can be leveraged across customers, the CARE platform team will implement the feature. Q: My customer wants to do a 100K project. Can I leverage CARE? What will the license component be? A: Unless there is a long -term vision for the customer and there is a customer promise of long-term work, CARE cannot be positioned for very small projects as the platform team cannot manage the overheads of supporting multiple small projects. In specific cases, where there is a long -term commitment, an appropriate payment schedule can be arrived at, that will fit within the budget at the same time provide for the licensing of CARE.",, "CARE TM – BATTLE CARD ENGAGE: CARE supports multiple pricing models. A standard CARE platform starts with a base price of 200k. Pricing may vary based on t he actual scope of development. CASE STUDY: •For a Fortune 500 American MNC involved in manufacturing of medical devices CARE helped reduce time to market by 52%, develop ment time by 26%, testing time by 18% & deployment time by 10% •For a Fortune 500 American MNC involved in selling of business services and document technology products, use of CARE helped revive business by enhancing customer satisfaction that led to increased revenues for the client, its Distributors, and resellers •For an American MNC involved in supply of ophthalmic surgical products, CARE platform helped transform a disjoint manual proc ess into a connected device environment with centralized database. This is expected to impact business growth by up to 45% CONTACT US @ ersslus@hcl.com",, "Developer Guide for CARE Guideline ID: O120003 Release Date: 20-Oct-2021 Revision: 2.7 Copyright Notice The information contained in this document is the property of HCL Technologies Limited. Except as specifically authorized in writing by HCL Techn ologies Limited, the holder of this document shall: (1) keep all information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to all third parties and, (2) use same for operating and maintenance pur poses only . Reviewed and Approved by Name Role / Function Signature Date Venkatesh Shankar Senior Technical Manager 01-Nov-2021 Jose Vincent Group Project Manager 01-Nov-2021",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 2 of 133 Revision History Revision No. Date Prepared By Summary of changes 1.0 10-Jan-2020 Jose Vincent CARE has been changed to CARE – updated the changes. 1.1 14-Jan-2020 Nadeem Mailsender boot deployment, Mailsender newly added smtp services, OTP & TOTP 1.2 17-Jan-2020 Ramesh Cross -domain Access Support, Device mangement(Device, P atch, Gateway) 1.3 20-Jan-2020 Sindhu Key Store - modified Document, Security gateway with nginx. 1.4 20-Jan-2020 S.Arun Prasad Audit trail, Audit details 1.5 21-Jan-2020 Virat Update archetypes 1.6 22-Jan-2020 Ram Kiran Kubernetes 1.7 24-Jan-2020 Sumathi B Data partitioning 1.8 29-Jan-2020 Vijay Opent ID Connect 1.9 30-Jan-2020 Venkatesh Shankar Password Encryption, Access Open ID Client thru Platform 2.0 30-Jan-2020 Vijay Administration services 2.1 15-Jun-2020 Ramesh Docker support 2.2 26-Jun-2020 Venkatesh Docker support 2.3 13-Aug-2020 Sumathi B Single schema for security and admin microserive and Swagger Enable/Disable 2.4 14-Sep-2020 Gokila B On-Demand synchronization and Token Validation 2.5 20-Jan-2021 Ramesh Device management – Modi fied gateway microservice - RD and API changes 2.6 08-JULY - 2021 Vijay Domain Metadata Configuration 2.7 20-Oct-2021 Rahman Khan Updated the document as per template",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 3 of 133 Glossary Abbreviation Description PAS Platform Acceleration Suite CARE Connected Asse ts in Regulated Environment API Application Programming Interface",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 4 of 133 Table o f Contents 1 Introduction ................................ ................................ ................................ ................................ . 9 1.1 Purpose ................................ ................................ ................................ .............................. 9 1.2 Scope ................................ ................................ ................................ ................................ . 9 2 Reference Documents ................................ ................................ ................................ .............. 10 3 CARE - An Overview ................................ ................................ ................................ ................. 11 3.1 Multi -Tenancy ................................ ................................ ................................ ................... 11 3.1.1 Hierarchical Multi Tenancy ................................ ................................ .............. 11 3.2 What is CARE ................................ ................................ ................................ .................. 12 3.3 CARE and Microservice ................................ ................................ ................................ ... 13 3.4 Get Started ................................ ................................ ................................ ....................... 13 3.5 CARE Pre -Requisites - Set up Environment ................................ ................................ .... 13 3.5.1 Jdk ................................ ................................ ................................ ..................... 13 3.5.2 Eclipse ................................ ................................ ................................ ............... 13",, "3.5.3 Database ................................ ................................ ................................ ............ 14 3.5.4 Artifacts ................................ ................................ ................................ ............. 14 3.6 CARE Platform Deployment ................................ ................................ ............................. 15 3.6.1 Configuration ................................ ................................ ................................ .... 15 3.6.2 Database configuration ................................ ................................ ................... 15 3.6.3 Port Configuration ................................ ................................ ............................ 15 3.6.4 Deployments ................................ ................................ ................................ ..... 16 3.6.5 Accessing the Platform ................................ ................................ ................... 21 3.7 MicroServices ................................ ................................ ................................ ................... 22 3.7.1 Multi Tenancy in Microservices ................................ ................................ ...... 22 3.7.2 Dev Set up - Microservice Components ................................ ........................ 23 3.8 Features o f 3.0 Release ................................ ................................ ................................ ... 31 3.9 TaggingMetadataService ................................ ................................ ................................ . 39 3.10 EnumerationService ................................ ................................ ................................ ......... 39 3.11 I18NService ................................ ................................ ................................ ...................... 39",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 5 of 133 3.12 Other CARE Functionalities ................................ ................................ ............................. 39 3.12.1 Caching ................................ ................................ ................................ ............. 39 3.12.2 Transactions ................................ ................................ ................................ ..... 39 3.12.3 Data Partitioning ................................ ................................ ............................... 39 3.12.4 UI Framework ................................ ................................ ................................ .... 40 3.12.5 Integrating Other Frameworks ................................ ................................ ........ 40 3.12.6 YAML Support ................................ ................................ ................................ .. 40 3.12.7 Support for Other Systems ................................ ................................ ............. 43 4 Admin Microservice ................................ ................................ ................................ .................. 45 4.1 Tenant Management ................................ ................................ ................................ ........ 45 4.1.1 What is Company Type? ................................ ................................ .................. 45 4.1.2 Onboard a Tenant ................................ ................................ ............................. 45 4.2 User Management ................................ ................................ ................................ ............ 45 4.2.1 User Creation ................................ ................................ ................................ .... 45",, "4.2.2 User Update ................................ ................................ ................................ ...... 46 4.2.3 User Soft Delete ................................ ................................ ................................ 46 4.2.4 User Activate/Deactivate ................................ ................................ ................. 46 4.2.5 User Emails ................................ ................................ ................................ ....... 46 4.2.6 User Security Related ................................ ................................ ...................... 46 5 Metadata – Customizations ................................ ................................ ................................ ..... 48 5.1 Metadata ................................ ................................ ................................ .......................... 49 5.1.1 Entity Customization ................................ ................................ ........................ 50 5.1.2 Other Customizations ................................ ................................ ...................... 51 5.1.3 Metadata Tagging ................................ ................................ ............................. 52 5.2 Hierarchical Data ................................ ................................ ................................ .............. 53 5.2.1 Email Templates ................................ ................................ ............................... 53 5.2.2 Enumerations ................................ ................................ ................................ ... 54 5.2.3 Localization ................................ ................................ ................................ ....... 55 5.2.4 Domain Metadata ................................ ................................ .............................. 56",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 6 of 133 6 Security Microservice ................................ ................................ ................................ ............... 60 6.1 Authentication ................................ ................................ ................................ ................... 60 6.1.1 Platform Authentication ................................ ................................ ................... 60 6.1.2 SAML Authentication ................................ ................................ ....................... 61 6.1.3 LDAP Authentication ................................ ................................ ....................... 62 6.1.4 Multifactor Authentication ................................ ................................ ............... 64 6.1.5 OAUTH ................................ ................................ ................................ ............... 72 6.2 Authorization ................................ ................................ ................................ .................... 72 6.2.1 System Role ................................ ................................ ................................ ...... 73 6.2.2 How to introduce new System Roles? ................................ ........................... 73 6.2.3 Product an d Services ................................ ................................ ....................... 74 6.3 CARE Security and Micro Service ................................ ................................ ................... 74 6.4 User Password ................................ ................................ ................................ ................. 76 6.4.1 Password Policy ................................ ................................ ............................... 76",, "6.4.2 Forgot password ................................ ................................ .............................. 77 6.4.3 Password reset ................................ ................................ ................................ . 77 6.5 Session management ................................ ................................ ................................ ....... 77 6.6 Key Management ................................ ................................ ................................ ............. 77 6.7 OWASP Guidelines ................................ ................................ ................................ .......... 78 6.8 Cross Domain Access ................................ ................................ ................................ ...... 79 6.9 Token Validation ................................ ................................ ................................ ............... 79 7 Email Service ................................ ................................ ................................ ............................ 80 7.1 Email Rest Service ................................ ................................ ................................ ........... 80 7.2 Template Services ................................ ................................ ................................ ............ 81 7.3 Email SMTP Services ................................ ................................ ................................ ....... 83 8 Mail Sender Service ................................ ................................ ................................ .................. 86 8.1 Sending Mail Through SMTP ................................ ................................ ........................... 86 8.2 Sending Mail Through AWS ................................ ................................ ............................. 87 8.3 Custom SMS sender ................................ ................................ ................................ ........ 88",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 7 of 133 9 Development Acceleration ................................ ................................ ................................ ...... 89 9.1 Eclipse plugin ................................ ................................ ................................ ................... 89 9.2 CRUD Plugin ................................ ................................ ................................ .................... 94 9.3 UI Plugin ................................ ................................ ................................ ........................... 96 9.4 API Plugin ................................ ................................ ................................ ......................... 98 9.5 Junit plugin ................................ ................................ ................................ ..................... 107 9.6 Service te st plugin ................................ ................................ ................................ .......... 112 9.7 JPA plugin ................................ ................................ ................................ ...................... 112 10 Secured Gateway using Ngnix ................................ ................................ .............................. 118 10.1 Requirements ................................ ................................ ................................ ................. 118 10.1.1 Primary Requirements ................................ ................................ ................... 118 10.1.2 Setup requirements ................................ ................................ ........................ 118 10.1.3 Setup ................................ ................................ ................................ ................ 118",, "10.1.4 Nginx -Clojure with Gateway module setup ................................ ................. 118 10.1.5 RabbitMq Configuration ................................ ................................ ................ 119 10.1.6 CARE configuration ................................ ................................ ....................... 121 10.1.7 Nginx -Clojure with Gateway module startup ................................ ............... 121 11 Two way SSL ................................ ................................ ................................ ........................... 122 11.1 Setup ................................ ................................ ................................ .............................. 122 12 HTTPS Deployment ................................ ................................ ................................ ................ 123 12.1 Setup ................................ ................................ ................................ .............................. 123 13 Audittrail ................................ ................................ ................................ ................................ .. 124 14 Keyvault ................................ ................................ ................................ ................................ ... 125 15 Kubernetes ................................ ................................ ................................ .............................. 126 16 Device Management ................................ ................................ ................................ ............... 127 17 Archetype ................................ ................................ ................................ ................................ 128 18 OPEN -ID CONNECT ................................ ................................ ................................ ................ 129",, "19 PASSWORD ENCRYPTION ................................ ................................ ................................ .... 130 20 OPEN ID CLIENT accessing thru the platform ................................ ................................ .... 131",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 8 of 133 21 Docker Support ................................ ................................ ................................ ....................... 132 22 Swagger Enable/Disable ................................ ................................ ................................ ........ 133",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 9 of 133 1 Introduction 1.1 Purpose This User Guide focuses on providing documentation for developers leveraging the CARE platform for building their software and ensures they get the most out of PAS. 1.2 Scope The document will walk you through • the step -by-step procedures involved in getting started with the development set up of PAS • a detailed description of CARE in -built core components, the functionality it serves, how these components can be configured and reused to accelerate any application development • the integrated technology stacks, and the configuration steps involved • the automation components which integrates wi th Eclipse IDE, accelerates the development process and reduces the developer effort.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 10 of 133 2 Reference Document s Sr. No Document ID / File Name Document Description 1 O120003_SR_CARE SR reference documen t 2 O120003_SRS_CARE SRS reference document 3 O120003_HLD_CARE High Level Document reference 4 O120003_LLD_CARE Low Level Document reference Table 1: Reference Document s",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 11 of 133 3 CARE - An Overview 3.1 Multi -Tenancy Multi -tenancy is an architecture in which a single instance of a software application serves multiple customers. Each customer is called a tenant. In multi -tenant scenario, each tenant's data is isolated and remains invisible to other tenants. Key factors to be considered while designing a multi tenant application are: 1. Data Security: Most tenants are concerned about data falling into wrong hands. Therefore the flexibility to store data in separate database or separate schema is necessary. 2. Authentication and Authorization: Most of the tenants ma y have their own user identity store. Hence there arises a need for multitenant application to support in - house authentication as well as delegated authentication per tenant. Delegated authentication is nothing but single sign on with tenant’s existing sec urity infrastructure. 3. Customizations: Multiple tenants bring in the complexity of customization per tenant. So there is a need for supporting customizations of UI, data models and business processes at runtime. 4. Internationalization and Localization: Te nants can be located in different countries and would want the application localized for their country and language. So the application needs to support multiple locales in a single instance. CARE comes in with all the above cited factors as built -in fea tures. 3.1.1 Hierarchical Multi Tenancy Hierarchical Multi Tenancy can be defined as the ability to define a hierarchy of tenants and establish multi tenancy within the hierarchy. As an example if a health care service is launched by a health care service pro vider (dealing with retail health care products) to the entire globe, they would have the possibility of establishing a root organization, create geographies (or countries/states) as",, "tenants within the root organization, create customers (possibly targeted hospitals which consume the service) as tenants within the geography. Every tenant in the hierarchy has access to their own data as well as data within the hierarchy. The need for this kind of multi tenancy is to launch services that span across the glob e consistently with a lot of administration being handled at individual tenant level yet providing control to ancestors of the hierarchy on how the service can be consumed. This facet of hierarchical multi -tenant applications is called Hierarchical config uration. In hierarchical multi tenancy each tenant can have ancestors, descendants. In the sample diagram shown, Tenant A is an ancestor of Tenant C and Tenant E is a descendant of Tenant C.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 12 of 133 Hierarchical Model Now the challenge in creating a Hierarchical multitenant application is to maintain all tenant data in the same database whilst ensuring the data segregation and authentication. The primary motivation of Data Isolation in any hierarchical multi -tenant applic ation is:  A tenant has access to all of its own data, has access to all of its descendant’s data, and has access to all of its ancestor’s data.  But the tenant will not have access to any data of a tenant not in its hierarchy CARE handles these challenges by supporting hierarchical multi tenancy (called n degree multi tenancy) apart from flat multi tenancy (1st degree multi tenancy). 3.2 What is CARE CARE - Connected And Regulated Environment is a solution designed to ensure successful software engineering p rojects through out -of-the-box software components for reuse, automation components for the development process and knowledge artifacts for quick references.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 13 of 133 3.3 CARE and Microservice Microservices architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated depl oyment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. Why microservices?  Each microservice is relatively small  Each servi ce can be deployed independently of other services  Easier to scale development.  Improved fault isolation.  Each service can be developed and deployed independently CARE support Microservices based architecture by providing capability to write API and UI based services that integrate seamlessly with rest of the functionality. The different deployment options and components will be discussed in this guide. 3.4 Get Started Following sections provides the steps involved in environment setup, core CARE platform de ployment and microservice components set up: 3.5 CARE Pre -Requisites - Set up Environment 3.5.1 Jdk CARE requires JDK 8 or above as a pre -requisite. 3.5.2 Eclipse Download and install Eclipse Kepler from the below URL:  For Window 32 Bit https://www.eclipse.org/download s/download.php?file=/technology/epp/downl oads/release/kepler/SR2/eclipse -standard -kepler -SR2-win32.zip What is platform? A “Platform "" is a system comprising of sharable and reusable components and technologies that can be programmed and therefore Consumed and Extended by Developers both Internal and External and in that way, enabling building and exten ding of Application, Products, Services adapted to the unlimited needs of",, "A. Internal Users B. Partner Organization C. Customers",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 14 of 133  For Window 64 Bit https://www.eclipse.org/downloads/download.php?file=/technology/epp/downl oads/release/kepler/SR2/eclipse -standard -kepler -SR2-win32 -x86_ 64.zip 3.5.3 Database CARE supports  MySQL 5. 0,5.1,5.4  MSSQL Se rver 2012  Postgresql 8.4.4-1, 9.3.0-1 3.5.4 Artifacts Following are the list of CARE artifacts that would be available as part of the CARE release and their brief descriptions:  Security security -boot-x.yz.jar is a self -contained( embedded with a jetty container ), independently deployable component of CARE which handles  authentication  authorization  password policy management  Delegated Authentication  Metadata metadata - boot-x.yz.jar is a self -contained, in dependently deployable component of CARE which enables the storage and retrieval of hierarchical metadata like entity extensions, field validations, reports, rules and workflow. More information about Metadata is available in the Metadata Section .  Email email -api-boot-x.y.z.jar is a self -contained component of CARE which allows authoring emails as a centralized service. email -api-boot.jar is dependent on the metadata module for startup.  Application 1. CARE Admini stration API administration -api-boot-x.yz.jar is a reference implementation provided that acts as a backend for metadata authoring, user management and Generic Multi -Tenant company Management. administration -api-boot.jar is dependent on metadata module fo r startup. 2. CARE Administration UI administration -ui-boot-x.yz.jar is a self -contained component of CARE that is provided as a reference implementation that consists of a portal that allows authoring of metadata, user management and Generic Multi -Tenant C ompany Management. It interacts with the CARE Administration API maven boot module for backend services. administration -ui-",, "boot.jar is dependent on metadata module for startup. 3. Application API Archetype api-application -boot-template is a maven archetype of CARE using which api modules can be created, that is used for developing module specific services that are remotely exposed as API’s (supporting Spring Remoting and JAX -RS Rest Services). Modules created through the archetype depends on metadata module for startup.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 15 of 133 4. Application UI Archetype api-ui-boot-template is a maven archetype of CARE using which UI modules can be created, that is used for developing UI components using Bootstrap/JSP/html and Spring MVC. The implementation team can use this module f or enabling module specific UI with spring MVC support. 3.6 CARE Platform Deployment Following sections describes the steps involved in deploying the CARE administration portal: 3.6.1 Configuration Changes to be done in \\WEB -INF\\classes \\application .yaml file: 3.6.2 Database configuration CARE supports spring data source configuration. MySQL data source configuration are given as default in CARE modules. To change the data source configuration: a. Based on the database used (MySQL/ MSSQL/ Postgres), the jdbc connection details should be given in the \\WEB - INF\\classes \\application.yaml file. For example, sample Configuration for MYSQL database is given below: Where, , , , should be replaced with actual values. 3.6.3 Port Configuration Configure the port where each module has to run: 3.6.3.1 RabbitMQ Configuration Configure the RabbitMQ properties with respective exchange name and queue. A sample configuration is shown below:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 16 of 133 where, host - where rabbitmq server is running port – port number at which rabbitmq server is running username – user name with administrator rights password – password for connecting to the server exchangename – exchange name is the exchanger between multiple queues hierarchyqueuename – this is hierarchy queue name which is used as the routing key for company creation event routing userqueuename – this is user queue name which is used as the routing key for user creation event routing userdele tequeuename – this is user queue name which is used as the routing key for user deletion event routing userupdatedqueuename – this is user queue name which is used as the routing key for user updation event routing Note: If multiple machines are connected t o the same rabbitmq server, use unique exchange name for each machine . 3.6.4 Deployments 3.6.4.1 Security -Boot Deployment War to be deployed: security -boot.x.yz.jar Steps to be followed for deployment: 1. Hibernate connection: Refer section DB Setup for configuring the database for security module. Replace with “pas -security”. 2. Port Configuration: Refer section Port Configuration for configuring the port number in which security m odule should run. Same port should be configured in the “security_url”. A sample is shown below:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 17 of 133 3. Rabbitmq Setup: Refer section RabbitMQ Configuration for configuring rabbitmq properties. 4. Open a command promp t and run the command “java –jar security -boot-x.yz.jar”. 5. To ensure the module is up and running, hit the following url in browser: http://:/security -web/poll The poll response will be “Yes” when the security module is deployed successfully and “No” in case of deployment failure which may have resulted due to any misconfigurations of the parameters mentioned above. Error log ca n be traced back to sort out the cause. 3.6.4.2 Metadata Boot Deployment War to be deployed: metadata -boot.x.yz.jar Steps to be followed for deployment: 1. Hibernate connection: Refer section DB Setup for configuring the databas e for metadata module. Replace with “pas -metadata”. 2. Port Configuration: Refer section Port Configuration for configuring the port number in which metadata module should run.  Same port should be conf igured in the “metadata_url”.  Configure security port number for the property “security_remote_url”. A sample is shown below:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 18 of 133 3. Rabbitmq Setup: Refer section RabbitMQ Configuration for configuring rabbitmq prop erties. 4. Open a command prompt and run the command “java –jar metadata -boot-x.yz.jar”. 5. To ensure the module is up and running, hit the following url in browser: http:// :/met adata -web/poll The poll response will be “Yes” when the security module is deployed successfully and “No” in case of deployment failure which may have resulted due to any misconfigurations of the parameters mentioned above. Error log can be traced back t o sort out the cause. 3.6.4.3 Adminstration API Boot Deployment War to be deployed: administration -api-boot.x.yz.jar Steps to be followed for deployment: 1. Hibernate connection: Refer section DB Setup for configuring the datab ase for application -api-boot module. Replace with “admin -api”. 2. Port Configuration: Refer section Port Configuration for configuring the port number in which application api module should run.  Same po rt should be configured in the “application_url and application_remote_url”.  Configure security port number for the properties “security_url” and “security_remote_url”.  Configure metadata port number for the properties metadata_url and “metadata_remote_ur l”.  Configure administration -ui- boot port number for the properties “application_ui_url”. A sample is shown below:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 19 of 133 3. Rabbitmq Setup: Refer section RabbitMQ Configuration for configuring rabbitmq properties. 4. Open a command prompt and run the command “java –jar administration -api-boot- x.yz.jar”. (For this jar to start, assumption is made that the metadata module is up and running) 5. To ensure the module is up and running, hit the following url in browser: http:// :/admin -api/poll The poll response will be “Yes” when the security module is deployed successfully and “No” in case of deployment failure which may have resulted due to any misconfigurations of the parameters mentioned above. Error log can be traced back to sort out the cause. 3.6.4.4 Administration UI Boot Deployment War to be deployed: administration -ui -boot.x.yz.jar Steps to be followed for deployment: 1. Port Configuration: Refer section Port Configuration for configuring the port number in which application ui springmvc module should run.  Same port should be configured in the “application_url and application_remote_url”.  Configure security port number for the properties “security_url” and “security_remote_url”.  Configure metadata port number for the properties metadata_url and “metadata_remote_url”.  Configure administration -api-boot port number for the properties admin_url” and",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 20 of 133 “admin_remote_url”. A sample is shown below: 2. Rabbitm q Setup: Refer section RabbitMQ Configuration for configuring rabbitmq properties. 3. Open a command prompt and run the command “java –jar administration -ui-boot- x.yz.jar”. (For this war to start, assumption is made that the administration api module is up and running) 4. To ensure the module is up and running, hit the following url in browser: http:// :/admin -ui /poll The poll resp onse will be “Yes” when the security module is deployed successfully and “No” in case of deployment failure which may have resulted due to any misconfigurations of the parameters mentioned above. Error log can be traced back to sort out the cause. 3.6.4.5 Email AP I Boot Deployment War to be deployed: email -api-boot.x.yz.jar Steps to be followed for deployment: 1. Hibernate connection: Refer section DB Setup for configuring the database for email -api-boot module. Replace with “pas -email”. 2. Port Configuration: Refer section Port Configuration for configuring the port number in which email api module should run.  Same port should be configured in the “application_url and applicat ion_remote_url”.  Configure security port number for the properties “security_url” and “security_remote_url”.  Configure metadata port number for the properties metadata_url and “metadata_remote_url”.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 21 of 133  Configure administration ui boot port number for the pr operties “application_ui_url”. A sample is shown below: 3. Rabbitmq Setup: Refer section RabbitMQ Configuration for configuring rabbitmq properties. 4. Open a command prompt and run the command “java –jar email -api-boot-x.yz.jar”. (For this jar to start, assumption is made that the metadata module is up and running) 5. To ensure the module is up and running, hit the following url in browser: http://www.pas.com:84/email -web/poll The poll response will be “Yes” when the security module is deployed successfully and “No” in case of deployment failure which may have resulted due to any misconfigurations of the parameters mentioned above. Error log can be traced back to sort out the cause. 3.6.5 Accessing the Platform Once a ll the components are polled “Yes”, the platform can be accessed as shown below:  Use the application_url property that was configured in Url Configuration in administration -ui -boot to access the CARE portal application.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 22 of 133 By default this url would be, http://www.pas.com:/admin - ui/listuser.mvc  The default administrative username, password and domain name are Username: admin Password: xxxxxx (The actual password would be provided on request) Domain: hcl.com 3.7 MicroServices The subsequent sections will guide you through the concept of multi tenancy in microservice modules, patterns inv olved and deployment scenarios. The steps involved to make the development set up for the same is also explained in detail. 3.7.1 Multi Tenancy in Microservices 1. In microservice architecture, all modules may or may not have the entire hierarchy of a single tenant. 2. This presents us two patterns and three deployment scenarios . Patterns: 1. Microservice with entire hierarchy of tenants in place/hierarchy aware microservice This is the basic assumption and rules will be enforced as described API/Services Archetype . 2. Microservice with only one tenant/tenant specific microservice/hierarchy unaware microservice . UDS will check if the logged in user’s tenant is present in the tenant table of that module. - If present, it will execute the rules as per the above section. - If not present HDP service will call a remote (rest) service in another module where the entire hierarchy is present to enforce the rules. - If the te nant accessing the application and microservice is configured for the tenant, then overhead of checking the tenant access to the data is removed. This will improve the overall performance of the microservice. Deployment scenarios : Assumption in all the dep loyment scenarios is that microse rvice will know what pattern is configured. 1. One microservice ->multiple databases: In this deployment, one microservice will be able to connect to two different databases.",, " Hierarchy unaware microservice pattern - If the micr oservice is configured to be tenant specific e.g Bonitas, then both the databases will have only Bonitas tenant provisioned. - In this case, microservice will check if the logged in tenant is same as tenant configured for the microservice.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 23 of 133 - If yes, check for validating the access of the tenant to the data is skipped. - If no, check for validating the access of the tenant to the data is delegated to a remote microservice where the entire hierarchy is available. This logic will be applied for access to both the da tabases.  Hierarchy aware microservice pattern If the microservice has the entire hierarchy of the tenant provisioned, then microservice will validate the access of the logged in tenant to the data running queries within the microservice. 2. UI microservice ->tenant specific microservice:  UI microservice needs tenant specific data.  Calls a service registry with the tenant as the argument and gets the url for the tenant specific microservice.  UI microservice makes a call to tenant specific microservice with a tok en identifying the logged in user and the tenant.  Tenant specific microservice checks if the logged in tenant is same as the tenant configured at the microservice.  If yes, microservice allows the access to the data.  If no, microservice will make a call to hierarchy aware microservice to validate the access of the tenant and the tenant configured for the microservice. If found logged in tenant having access, microservice will allow the access to data.  Data is returned to the UI microservice. 3. UI microservice ->API microservice ->tenant specific API microservice:  UI microservice calls a registry service to find the url of a API microservice.  UI microservice makes a call to API micro service.  API microservice needs to fetch data from two different API microservic es which are configured for particular tenants.  API microservice calls the service registry with tenant names to get the urls of the tenant specific microservices.  API microservice makes two different calls to each tenant specific microservice.",, " Tenant spec ific validates the access as mentioned in the previous deployment scenario.  If the logged in tenant has access to the data, data will be returned.  API microservice receives and collates the data from the two tenant specific microservices.  API microservice returns the data to the UI microservice. UI microservice receives the data and processes accordingly. 3.7.2 Dev Set up - Microservice Components To support micro services based architecture CARE provides two application maven archetypes. 1. API archetype - api-application -boot-template 2. UI archetype - ui-application -boot-template",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 24 of 133 With these development archetypes delivered by PAS, the micro service components can be built rapidly and efficiently. The procedures involved in the process of building the micro service components in explained below: 3.7.2.1 Prerequisite Before moving to the development set up, as a prerequisite, install the following artifacts (CARE related jars) in the maven repository. Artifacts.zip consist of the CARE components in the archived format. Be low is a screenshot of the list of files included in the Artifacts.zip. Following are the steps for installing the artifacts: 1. Copy and extract Artifacts.zip folder. The path in which it is extracted will be the ARTIFACT_DIR. 2. To Install the CARE relate d jars to the local maven repository, use install -artifact - local.bat 1. Open install -artifact -local.bat file and update ARTIFACT_DIR path E.g.: SET ARTIFACTS_DIR= E: \\\\Kit\\\\Artifacts 2. Start the bat file 3. To install the CARE related jars to the central maven nex us repository make use of install -artifact -repository bat 1. Open install -artifact -repository bat file and update ARTIFACTS_DIR, REPOSITORY_URL locations E.g.: SET ARTIFACTS_DIR= E: \\\\Kit\\\\Artifacts E.g: SET REPOSITORY_URL = http:///nexus/con tent/repositories/snapshots 2. Start the bat file . 3.7.2.2 API Microservice The API micro services for the application is built with CARE API archetype as the base. Given below is the pictorial representation of api microservice component setup .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 25 of 133 Here microservice -api-1 and microservice -api-2 are individual microservice api components, built on CARE API archetype available from local maven repository. CARE API archetype serves as the base for building microservice API components. Thus the microservice API componen ts inherit certain features from CARE which are explained below in detail. 3.7.2.2.1 Functionalities API archetype provides the following functionalities: 1) Integration with the platform API a) Data management i) Unified Data Services (UDS) framework to provide a common dat a access framework for all entities. Refer section UDS for detailed explanation. ii) JPAService to allow access to JPA Query Language that will enforce hierarchical multi tenancy. Refer section JPA Service for detailed description. 2) Data validation. 3) Multi -tenant data protection. Access tenant specific record as well as all records defined at the ancestor levels. 4) Metadata management - Refer section Metadata for detailed description 5) Email Services 6) Import data through excel  Since the data models with in CARE is standardized, data can be imported using excel.  Excel Import API in CARE can be used to import data for all the data models. These data models are not busin ess domain models.  Each sheet in excel will be mapped to a data model using conventions. Related data can also be imported. 7) Menu registration with UI  Individual microservice modules can define menus.  These menus will be registered with the UI component using the menu registration API provided by the UI component.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 26 of 133  Microservice will listen for an event that UI microservice has started, then registers the menus. 8) Security – Authentication, Authorization and Auditing Note: API Archetype will follow the packa ge conventions mentioned . 3.7.2.2.2 Maven Setup Following are the steps for building api microservice component using the CARE API archetype. 1. Create a new maven project using CARE provided maven api archetype i.e. api -application -boot-template (select , include snapshot archetypes in archetype selection page) in the eclipse workspace. 2. Given below is the sample structure of any api microservice component.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 27 of 133 3. Refer section Administration api boot deployment to set up the required properties for this api module. 4. Property “logged_module_name” should be replaced with in /src/main/resources/application.yaml file to identify the logs specific to the module which is also used for co rrelation. 5. After doing the above mentioned configuration, right click on the main class and start the component. 6. Url for accessing the api mciroservice component is http://www.pas.com:/simple -api/poll . 7. To access the url, with the actu al api module name replace the property “server.context - path” from the /src/main/resources/application.yaml property file with the required name for api module .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 28 of 133 Now access the api module with the url as: http://www.pas.com:/poll 3.7.2.2.3 Configurations Provides one configuration file as a java class named as ApplicationTemplateWithEmaiAndAmqpConfiguration .java which contains list of packages of all the configuration classes whatever need to run the application. That class is placed in ""com.hcl.hmtp.configuration.application"" 3.7.2.3 UI Microservice The UI micro services for the application is built using CARE UI maven archetype. Given below is the pictorial representation of UI microservice component setup Here microservice -ui-1 and microservice -ui-2 are individual microservice ui components, built using CARE UI archetype available in local maven repository. CARE UI archetype serves as the base for building microservice UI components. Thus the microservice UI components inherit certain features from CARE which are explained below in detail.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 29 of 133 3.7.2.3.1 Functionalities UI archetype provides the following functionalities: 1. Integration with the API  Data management  Data validation.  Multi -tenant data protection.  Internationalization  Metadata ma nagement 2. Security - Authentication and Authorization. 3. Integration with Spring MVC framework. 4. UI components include integration with bootstrap and html 5. 5. Provides Menu framework which can be extended by the implementation team 6. Error handling - takes care of centralized error handling . 3.7.2.3.2 Maven Setup 1. Create a new maven project using CARE provided maven ui archetype i.e. ui -application -boot-template (select, include snapshot archetypes in archetype selection page) in the eclipse workspace. 2. Refer section Administration ui boot deployment to set up the required properties for this ui module .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 30 of 133 3. Property “logged_module_name” should be replaced with in /src/main/resources/application.yam l file to identify the logs specific to the module which is also used for correlation. 4. After doing the above mentioned configuration, right click on the main class and start the component . 5. Url for accessing the ui microservice component is: http:// www.pas.com:/simple -ui/poll 6. To access the url, with the actual api module name replace the property “server.context -path” from the /src/main/resources/application.yaml property file with the required name for ui module 3.7.2.3.3 Configura tions Provides one configuration file as a java class named as ApplicationUITemplateConfiguration.java which contains list of configuration classes whatever need to run the application. That class is placed in ""com.hcl .hmtp.configuration.application "". 3.7.2.4 Advanced Configuration Configure the same module name in the application.yaml property file of both api and ui skinny modules as Example:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 31 of 133 The application module name should definitely be same for microservice api component and ui component, since this property is used for metadata tagging for specific module and execution of metadata at runtime . 3.8 Features of 3.0 Release 1. Active Directory Authentication  To configure Active Directory(AD ) based authentication, we need to change ‘authentication_scheme’ value from “default” to “activedirectory” in application.yaml file present in following wars:  Security -boot-x.yz.war path: security -boot-x.y.z-war \\WEB -INF\\. classes \\ application. yaml  application -api-boot-x.yz.war path: application -api-boot \\WEB -INF\\. classes \\ application.yaml Note : If authentication_scheme is “ default” , platform based authentication will be done.  Set AD properties in application.yaml file of security -boot.war li ke as Where, providerURL: the AD url, userDn: username of AD server, password : password of AD server, groupSearchBase: group where users are provisioned in AD server. Excel Configuration: Set XL_Location to “otherexcels” in application.yaml file of security -boot-x.y.z.war as below Provisioning LDAP users in PAS : If you are logged into the admin portal, list of users that are not provisioned will be displayed by clicking Admin  Unprovisioned Users submenu.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 32 of 133 Provisioning the users in CARE is done by assigning any role to the user in PAS, as shown below: The screenshot below shows list of available roles in the system. Select one or more roles and click save button. The message will confirm that user is provision ed and associated to selected roles. Provisioned user information can be verified in the user table of application, metadata and security database.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 33 of 133 2. Data S coping Data scoping feature provides environment in which user can access data which is specific at tenant level. Tenant specific data which is abstracted to other tenants by defining the Data access policies. D ata access policies are defined at security database level with the combination of tenant id, role id and user id. Platform take the responsibility to enforce the data access policies applicable at each tenant level. Use Cases: 1. Existing CARE behavior  When user Login with permissions which are not matched with the Service API permissions  Then user should get spring security exception. This is existing CARE behavior 2. Without Data access policies in Data base  When user Login with permissions which are ma tched with the Service API permissions  And Data access policies are not defined in data base  Then user should be able to perform actions as usual. 3. With Data access policies in DB Case (i):  When user Login with permissions which are matched with the Serv ice API permissions.  And Data access policies are defined with logged in user, Role which contains the Service API Permissions, Logged in tenant id.  Then user should be able to perform actions Case (ii)  When user Login with permissions which are matched w ith the Service API permissions.  And Data access policies are defined with logged in user, Role which contains the Service API Permissions, Tenant id is not the logged in tenant id  Then user should get Data access violation exception from UDS 4. Verifica tion of Data access policies for descendants  Update applyTochildTenats flag to true in tenantdataaccess table.  Create another company under root, for example Medscheme  Assign Medscheme company to Root admin",, " Assign Medscheme company to Root admin  Now logout and login with Root Admin and execute the servlet to create the entry in appDataAccessPolicy table.  Then it should make entry in appDataAccessPolicy table without any issues. 3. Micro Service based Metadata Registration Micro service based metadata registration feature provides environment in whi ch all micro services will be registered in the pas -metadata. Each micro service have feature corresponding to component. Depending upon the micro service data’s are stored and retrieved. Use Cases: There are two micro services Application api temp late service and e mail service.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 34 of 133 1. Enable all features  In CARE application: Entity Field validation, Data Source, Rules, Reports, Invisible fields and Work flow for all these module, component tag is enabled for all micro services.  In Rule module, comp onent name will be displaced from component table (refer above table). Component Name have drop down values as email - web and default.  User can select the component name and perform CRUD operation.  Based on the component selection separate rule can be defin ed for email - web and default micro services.  According to the micro service, user can customize the rules. 2. Enable optional features In CARE application, Entity Extension is optional feature. List of components will be displayed based on the feature.  In Entity Extension module, based on extension_value_feature, corresponding component name will be displayed as dropdown.  Component name will be displayed as default and email -web. User can select any one of the component and perform CRUD operation.  Base d on the component selection separate extension value can be defined for email -web and default microservices. 3. Component tag CRUD operation can be done both for self and descendant. Usage: 1. Each micro service will work independently of other service. A nd particular functionality can be implemented to that micro service. 2. Consider email service have entity extension feature, Entity Extension feature can be accessed only to email service.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 35 of 133 4. Synchronization 4.1 User Synchronization Whenever a micro service API is started, the users present in in the CARE metadata database (user table) will be automatically synchronized to the micro service API database (user and applicationuser table). Parent company of the created users will be maintained during the synchroniz ation process. Use Cases: 1. If the micro service API is started for the first time with fresh database, all the users in CARE metadata database (user table) will be synced to the current micro service API database (user and applicationuser table). 2. If any on e of the existing micro service API is stopped, in mean while some new users are created, when the micro service API starts again, new users present in CARE metadata database (user table) is synced to the current micro service API database (user and appli cationusertable). 4.2 Bootstrap Service for Hierarchy Synchronization Whenever a micro service API is started, the companies present in in the CARE metadata database (company table) will be automatically synchronized to the micro service API database (company and applicati oncompany table). Hierarchy of company is maintained during the synchronization process. Use Cases: 1. If the micro service API is started for the first time with fresh database, all the companies in CARE metadata database (company table) will be synced to the current micro service database (company and applicationcompany table). 2. If any one of the existing micro service API is stopped, in mean while some new companies are created, when the micro service starts again whatever new companies pr esent in CARE metadata database (company table) is synced to the current micro service database (company and applicationcompany table). 4.3 Company Type Synchronization",, "4.3 Company Type Synchronization Whenever a micro service API is started, the company types present in the CARE metadata da tabase (company_type table) will be automatically synchronized to the micro service API database (company_type table) . If the micro service API has new company type, this company type is synced to CARE metadata database (company_type table) first and the n it is synced to the rest of the micro services API. Use Cases: 1. If the micro service API (say microservice -api1) is started for the first time with fresh database, all the company types present in CARE metadata database (company_type table) will be synce d to the current micro service database (company_type table). 2. If any new micro service API (say microservice -api2) with new company type is started for the first time with fresh database, this company Type is synced to CARE metadata database",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 36 of 133 (company_typ e table) first and then it is synced to the rest of the micro services API (for example, to the microservice -api1). 3. If any one of the existing micro service API is stopped, in mean while new micro service API’s with new company types are started, when t he micro service API starts again whatever new company types present in CARE metadata database (company_type table) is synced to the current micro service API database (company_type table). 4.4 Company Sync and User Sunc - On Demand Basis Company details will be synced on demand basis only when accessing the microservices if the company_sync_type is on -demand. User details will be synced on demand basis only when accessing the microservices when logged in as a user if the user_sync_type is on -demand. These 2 properties has to be in all yaml and type should be set to “on - demand”. If Company sync is on -demand then user sync should be in on -demand. If the properties are set to default then company table and user table will be automatically synchronized to the micro service API database #sync company in other microservices #default - company will be synced in other microservices at the time of creation itself #on-demand - sync will happen only at the time of microservice access company_sync_type: on-demand #default - User will be synced and User will be validated on each microservice #on-demand - On Demand syncing of the Users. #never - Never syncs the Users, and User validation on microservices will not happen #If company_sync _type is on demand then user sync should be on demand user_sync_type: on -demad 5. CARE Annotation To enable CARE specific features, CARE provides enablement of the feature through CARE specific annotations. By default CARE specific features are not",, "enabled. They can be enabled for specific requirements of the micro service API. Use Cases: List of CARE specific annotations and their uses. 1. @EnableEnumeration This annotation will enable the enumeration feature of PAS, by doing so enumerations can be cr eated using EnumerationService. When this feature enabled enumeration specific tables will be created in the micro service database.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 37 of 133 2. @EnableI18n This annotation will enable the localization feature of PAS, by doing so properties can be created for a particular locale using I18nService. When this feature enabled I18n specific tables will be created in the micro service database. 3. @EnableDefaultRolesAndPermissions By giving this annotation default role and permissions provided CARE can be available for usage. Those roles and permissions can be customized. New Roles creation or existing role customization can be done using RoleAndPermissionService. When this feature enabled default role and permissions specific tables will be created in the micro ser vice database. 4. @EnableExtensionvalues This annotation will enable the entity extension feature of PAS, by doing so extensions used for module specific UI components can be created at runtime using EntityExtensionService. 5. @EnableAllOptionalFeatures This annotation will enable all the above mentioned CARE features. CARE specific features can be accessed in the micro services API. 6. Yaml Grouping Yaml provided grouping supports for readable and maintain the structure of the properties. Using grouping, th e related properties are maintained under a respective group.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 38 of 133",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 39 of 133 3.9 TaggingMetadataService 3.10 EnumerationService 3.11 I18NService 3.12 Other CARE Functionalities 3.12.1 Caching  The choice of Cache is Jboss Infinispan Cache. This comes neatly integrated with the JBoss Application Server and provides good capabilities to have a distributed cache across a cluster of machines. In order to deploy it in a public cloud like AWS/Azure it comes with specific capabilities to avoid UDP Multi Casting for node detec tion.  For security, there are 2 modes for cache synchronization 1) An invalidation mode that invalidates with just the id in all participating nodes in the cluster. 2) Encrypt cache communication over SSL.  Typical Entities Cached in different components 1) Security Hibernate L2 Caching Cache all Tenant, User, Roles and Permissions. 2) Metadata Hibernate L2 Caching Cache all Tenant hierarchy, Extensions, Validations, Visibility, Rules and Reports metadata 3) Possibility to cache metadata obtained from Metadata server  Only Application Level Custom Cache  Decision taken based on benchmarking results  This in combination with Application Hibernate Cache will allow the application to be co -located with database anywhere without performance implication 3.12.2 Transactions  The transaction in application is handled manually  Initially threadsession manager is initialized through spring  Before performing any transaction to database by performing create/update/delete the threadsession has to be initialized  Call “ThreadSessionManage r.currrentThreadSession().beginTransaction()” to start the transaction  Perform the operation using service class for hitting the database  Use “ThreadSessionManager.currrentThreadSession().commitSession()” to end the transaction 3.12.3 Data Partitioning  As some tenants require their own data to be maintained in separate",, "database, CARE supports it by providing partitioning  Refer to b2b_Partition_InstallationGuide for it’s detailed implementation \\  Refer the following setup document for data partitioning,",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 40 of 133 O120003_d evguide_ Data Partitioning 3.12.4 UI Framework  UI framework helps building CARE UI in providing cross browser support  In match with the standards based on JavaScript + HTML 5  MVC Architecture o Standard Error Handling that intercepts unhandled exceptions and provide o Standard error pages avoid implementation stack traces to be show to users  Validation o Predefined validations for common data types o Custom validations through configurable regular expression o Validation Framework integrated with metadata which can pr ovide tenant specific validations for entity fields  I18N o Resource Bundle implementation for database allowing locale on boarding to have language translations that can be imported o I18N Aware UI ensures the correct implementation for all  The core framework allows the possibility of mapping permissions to menu items  The MenuService takes the responsibility of retrieving a list of menus, the mapped permissions, the permissions that the logged in user has and constraining the list of menu items to which the use r does not have access to  While menu level access control is automatically enforced, access control beyond menus for actions based out of links/buttons/selects have to be controlled by the individual JSP pages 3.12.5 Integrating Other Frameworks  CARE is built in such a way that integration of other frameworks to CARE is pluggable  In CARE by default spring mvc framework is used, by which the following is handled o Contains validation logic for form inputs o Delegates to business service for ALL processing o While ther e is a level of validation required at the UI level, the services layer will revalidate and enforce all business logic independent of UI validations If apart from the used framework, other technology to be integrated, then complete",, "implementation to be tak en care by the implementation team 3.12.6 YAML Support As YAML is much less verbose and simply reduces all the properties files to a single YAML. In CARE following are the property files that are combined to a single yaml configuration file as mentioned below:  .properties – url and application property configuration  application_hibernate.properties – database configuration  domain_whitelist_urls.properties – set of whitelisted domains  application.properties for server configuration in spring boot - configuring server port and context module name Configuration File Replacement in D etail  application -api-boot.x.yz.war & application -api-boot-x.yz-skinny.zip : This property file combines the values of application.properties, application_hibernate.properties ,",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 41 of 133 domain_whitelist_urls.properties and application.properties for server configuration in spring boot  application -ui-springmvc -boot.x.yz.war & application -ui-springmvc -boot-x.yz- skinny.zip : This property file combines the values of application.properties , domain_whitelist_urls.properties and application.properties for server configuration in spring boot.  metadata -boot: This property file combines the values of metadata.properties, metadata_hibernate.properties, domain_whitelist_urls.properties and applic ation.properties for server configuration in spring boot  security -boot: This property file combines the values of security.properties, security_hibernate.properties, domain_whitelist_urls.properties and application.properties for server configuration in s pring boot For example, taking a single module application -api-boot.x.yz.war , the property files of that module is replaced by a single YAML i.e application.yaml as shown below",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 42 of 133",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 43 of 133 In the same way we can configure yaml for reaming all module s. 3.12.7 Support for Other S ystems In addition to default configuration provided above, CARE do support the deployment of CARE in other DB’s such as MSSQL and PostgreSQL along with tomcat support. 3.12.7.1 Database Support for other DB such as MSSQL and Postgresql is als o provided by PAS. Follow the connection details given below for its respective support . 3.12.7.1.1 MS SQL Server 1. Create the following empty databases; ensure they are created with Unicode Support 1. pas_application 2. pas_metadata 3. pas_security 4. pas_quartz 3.12.7.1.2 Postg reSQL Create the following empty databases; ensure they are created with Unicode Support 1. pas-application 2. pas-metadata 3. pas-security 4. pas-quartz",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 44 of 133 Change it to pas - application",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 45 of 133 4 Admin Microservice The Administration micro service manages the tenant and user information in th e platform. It also deals with the users password related operations such as sending email to user in case if the user forgets his password , forcefully making the user to reset his password, validating user based additional security such as security quest ions and answer. 4.1 Tenant Management In order to login into the system and onboard a tenant, there must be a root tenant and a Administrator user. These details will be populated from the excel. The name of the root tenant is configured in the YAML co nfiguration file. 4.1.1 What is Company Type? As mentioned previously CARE is a hierarchical multi -tenant platform. One can able to create multiple levels of tenant in the platform, which is referred from now as “Company Type”. Each company type defines a speci fic layer in the hierarchy. Such as Geography, Country, States and City. The default Company Type of the application is PASCOMPANY. If needed the company type can be modified by updating the initialization excel data. 4.1.2 Onboard a Tenant To onboard a tenant into the system, one can use the REST API mentioned in the Swagger documentation under Application Company Service. ownerId The primary key of the tenant under which you want to provision your tenant. By default, it is the tenant Id of the logged -In use r ompanyType By default PASCOMPANY 4.2 User Management Users can be created under a given tenant. They are provided permissions to access his hierarchy. Following are the functionalities provided under user management as REST services. You can able to fin d it in swagger under Application User Service and User logon Sevice. 4.2.1 User Creation ownerId The primary key of the tenant under which you want to provision your tenant.",, "By default, it is the tenant Id of the logged -In user",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 46 of 133 roles Common Separated String . The roles assigned for the user can be mentioned here. It is mandatory 4.2.2 User Update 4.2.3 User Soft Delete User soft deleted into the system will be having the retired flag set as true. A user with the same login name can be created again if the previo usly defined user with same login name is soft deleted. 4.2.4 User Activate /Deactivate User once deactivated. He can not able to login or perform any kind of operation until the user is activated again. Once reactivated, user has to set his password again to access the system. 4.2.5 User Emails Sending Reset password link if user forgets his password Sending Reset password link to the user 4.2.6 User Security Related Find out user information from the encrypted code sent in email",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 47 of 133 Get the password policy rule s et in the system Get the user password validated against our password policy Updating user password using encrypted code sent to user email Get all security questions configured in system Save the user selected questions and respective answer Change password Note: - Single schema provided for security and admin microservice Henceforthe all the Admin API’s have been moved to Security Microservice from CARE_V5.2. Please check the sections of Security Microservice for the Admin API’s 1.Security Admin user service 2. Security Admin Company service 3. Application user logon service.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 48 of 133 5 Metadata – Customizations In PAS, Hierarchical Configuration is yet another important architecture driver. The primary reason behind establishing hiera rchy is to allow control of descendants. This means specific configurations can be inherited or over -ridden by any node in the hierarchy. These configurations are the metadata of the application which may be extensions to data models, changes to workflow or changes to the look and feel and these operate at all layers of the application. Irrespective of the type of configuration there are fundamental rules governing how a configuration of metadata or application data can be authored and accessed at vario us levels in the hierarchy. General rules for defining metadata customizations are given below: Definition of metadata can be done in following ways:  Self o Where the Company defin es metadata for himself o Scenario: When ownerId == authorId, metadata is defined for self  All Descendants o Where the Company defines metadata for all descendant companies o Scenario: When owner==0 and authorId – company id of the one who creates metadata  Specific Company Type o Where the Company defines metadata for specific companies grouped under particular company type o Scenario: When authorId – company id of the one who creates metadata and companyTypeId – id of the company type to which the metadata has to be assigned",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 49 of 133  Specific Company o Where the company defines metadata specific to company o Scenario: When authorId - id of the company wh o creates the data and ownerId - id of the company to whom the metadata has to be assigned, ownerId!=authorId Metadata cu stomization in CARE is done in two ways as explained: 1. OVERRIDE - it first look out for the data defined by self and if no records found, it searches for the data defined by specific company and if no records found, then specific company type and finally a ll descendants. In this case only specific record to self/ specific company/ specific company type / all descendants will be fetched. If a record found at any level in this hierarchy it returns only that particular set of record. 2. INHERIT - it looks out fo r the data defined by self, then all descendants, specific company type and then under specific company and give out the aggregated records. This type can be used by enum . 5.1 Metadata Metadata is data which changes/affects the behavior of the syst em.. The Metadata component within CARE is a central place where metadata about different components are persisted and retrieved for enabling runtime customizations in the platform. Following are the metadata that can be defined in PAS:  Extensions - new f ields can be added to data models at runtime. The list of customizable entities can be specified by the developer during development time and each of these customizable entities can have their extensions defined through metadata. While the data access laye r would automatically pick up extensions where defined, all UI screens must reflect additionally defined fields which has to be consciously enabled during the development of the screens.  Validation s - The validation to be done for each field in the data mo del defined across",, "components can be configured with the ability to change the validation differently for each tenant  I18n – Localization of text for a specific label can be configured differently based on tenant specific requirements  Invisible fields - Show/Hide fields based on differently based on tenant specific requirements  Rules - Specific business rules can be configured based on tenant specific requirements  Enumerations – List of values can be defined and customized based on tenant specific requireme nts Types available public static enum TYPE { INHERIT ,OVERRIDE }; Usage in metadata class RuleMetadadata extends Metadata { @Override public TYPE getType() { return TYPE. OVERRID E; } }",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 50 of 133  Template – Email templates per tenant per locale can be configured  Workflow – business process  Reports – Reports can be customized differently for tenants based on specific requirements 5.1.1 Entity Customization Customizations supported for entities are ru ntime extensions, field validations and invisibility. By default all entities are not enabled for customization. Any entity to be eligible for customization should be marked as customizable. Entities can be marked customizable for a particular tenant type by a particular tenant type. E.g. Only Service Provider can customize USER entity for customers; customers cannot customize USER entity. 5.1.1.1 Entity Extension Entity extension is a metadata. A tenant can add a runtime field to an entity for a specific tenant o r a specific set of tenants. Tenant can specify field name, data type for the field, localization label key and the screen component type for that field. In short it is used to define run time fields, which is of type ‘INHERIT’. API used for managing ent ity extension is ‘TaggedMetadataService’. This is exposed as a remote Spring Bean . Entity Extension Attributes:  Field Name – the identifier of the hierarchy data .  Data type – data type supported by CARE for defining run time fields are decimal, data, blo b, list, String, long/integer, short, byte .  Label key – the key that can be used to define localization values for the run time field labels .  UI/ Screen component type – this is used to define how the run time fields will appear in UI. This type can be t extbox, text area, label, combo box, etc. Here one can control the entity extension CRUD operation by invoking ‘TaggedMetadataService’ API methods with respect to the operation performed. Hence the extension is done obeying the metadata rules.",, "Reference f ile in CARE that takes care of the entity extension operation is “MetadataController” class. For e.g. consider a scenario, where a global health care concern “Testa”, is operating in different regions. For different region we have different users and in e ach region they may require some field or attribute in addition to that of the data model defined for the other regions. This can be done possibly in CARE by means of entity extensions. 5.1.1.2 Field Validation Entity field validation is a metadata of type ‘OVER RIDE’. A Tenant can customize validation for a particular field for an entity. The field can be either extension fields or fields defined during the development time. Field Validation captures data type of the",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 51 of 133 field and validation to be done. Supports vali dation for byte, short, date, double, float, list, String, long and integer as well as regular expressions. In general, the default validations for the entities from its respective validation xml’s are fed during the first time server start up. (i.e. on b ootstrap). One can define validation for the existing field and also for the new field defined under entity extensions. To override the default validation for the existing entities, the tenant can create validation with the same name. It overrides the val idation value of the default one. E.g. If tenant A describes validation for the all of its descendants say tenant B and tenant C, and now if tenant B wishes to override the validation defined by its parent tenant A, then Tenant B can create new validation for the same field under self -configuration. Now tenant B will have validation defined by him and tenant C will have validation defined its parent tenant A. EntityFieldValidation Attrbiutes:  fieldName – the identifier or name of the field for which valid ation is to be defined  extension – flag to define whether the field is extended through entity extension  mandatory – flag to set whether the field is mandatory  validation – supported validations through CARE are for byte, short, date, double, float, list, String, long and integer Here one can control the entity extension CRUD operation by invoking ‘Tagged MetadataService ’ API methods with respect to the operation performed. 5.1.1.3 Invisible Fields Runtime Fields or instance fi eld of entities which are non -mandatory can be marked invisible for a particu lar tenant or a set of tenants. Invisible field is a metadata of type ‘INHERIT’. E.g. If tenant A is the parent having two descendants B and C. Consider the entity called",, "“UserD etails” which has name, gender, age, email and mobile phone as its fields. Here gender and age are non -mandatory fields. If tenant B wishes not to show gender then it can be marked invisible. Now tenant B will have only name, age, email and mobile shown in UI and tenant C will have all the fields. InvisibleField Attributes:  fieldName – name of the non -mandatory field to be marked as invisible. Here one can control the entity extension CRUD operation by invoking ‘Tagging MetadataService ’API methods with respect to the operation performed. 5.1.2 Other Customizations 5.1.2.1 Workflow CARE allows workflow definitions to be managed via the same metadata model. While there is no direct support for workflow at runtime, any workflow engine ca n be plugged into CARE and the Metadata component can be used to manage the workflow definitions that are hierarchically defined. Workflow definitions/configurations can be customized for",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 52 of 133 all descendants, for a specific company/tenant type or for a specifi c company/tenant. Workflow is a metadata, of type ‘Override’. API for managing workflow is TaggingMetadataService. ‘m_workflow’ is the name of the table in where workflows are stored. Attributes of workflow are o workflowName – name of the w orkflow o description – description of the workflow o content – blob content, usually a file uploaded as input 5.1.2.2 Rules Same as workflow Rule definitions/configurations can be customized for all descendants, for a specific company/tenant type or for a specific company/tenant. Rule is a metadata, of type ‘Override’. API for managing rule is TaggingMetadataService. ‘m_rules’ is the name of the table in where rules are stored. Attributes of rules are o ruleName – name of the rule o description – descri ption of the rule o content – blob content, usually a file uploaded as input 5.1.2.3 Reports Same as Workflow Report definitions/configurations can be customized for all descendants, for a specific company/tenant type or for a specific company/tenant. Report is a me tadata, of type ‘Override’. API for managing report is TaggingMetadataService. ‘m_reports’ is the name of the table in where reports are stored. Attributes of reports are o reportName – name of the report o description – description of the rep ort o 9content – blob content, usually a file uploaded as input 5.1.3 Metadata Tagging Metadata tagging is done in CARE to support metadata customization for micro service based architecture. As metadata is the master module where all the api mciroservice module s communicate for administering metadata, this tagging helps in identifying and provisioning metadata at runtime specific to the module.",, "runtime specific to the module. While authoring metadata, out of the various microservice components deployed, one can choose the module and define m etadata. Here, metadata will have an additional parameter called “tag” which can take any string input. This is applicable for all metadata as given below:  Entity Extension",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 53 of 133  Entity Field Validation  Invisible Fields  Rules  Reports  Workflow  Datasource API called TaggedMetadataService is introduced to handle/manage the CRUD functionality of metadata, which takes tag as an additional parameter. 5.2 Hierarchical Data Apart from metadata, an application has the possibility of holding hierarchical application data that is not metadata, but requires the same access rules of being able to hierarchically define data. CARE provides the possibility of creating a hierarchical data model with the same set of access rules as metadata easily. Any entity which implements ‘H ierarchy’ interface will hold hierarchical data. Hierarchical data will be stored locally in the individual application component/microservice and is not stored as part of metadata. A tenant can define hierarchical data for self, for all descendants, for a specific descendant or for particular type of descendant. CARE comes pre -defined with a few hierarchical data models that it uses. These are listed below  email templates  I18N and  enumeration 5.2.1 Email Templates In PAS, email templates can be defined wit h pre -defined template tagsthat can be replaced with actual values when emails are actually created. Email template is a hierarchical data of the type override, and can be customized per tenant per locale. Templates can be added for Self/All Descendants/f or a Company Type /for a Company. Default email templates supported by CARE are loaded on bootstrap to ‘ h_template ’ table in Template attributes:  Identifier, Description – unique name and description of the template respectively  body – Holds the body of the email content with tag holders  Html – flag to indicate if the body content is of type html",, " Subject – Subject of the email to be sent when an email is created with this template  senderName – name of the user from whose account email is sent  senderEmail – email id of the sender from whose account email is sent  replyTo – email id, which receives emails when a reply to is given  locale – value of locale to which the templates are associated Templates can be created in CARE by following ways: 1. Imported at bootstrap via Excel 2. Authored at runtime via the Template REST Service 1. Importing at Bootstrap via Excel",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 54 of 133 To create a new template, navigate to the bootstrap excel of email -api- boot.war/src/WEB -INF/classes/excels, namely brownstone_applic ation_init_1.xlsx  sheet named “app.TEMPLATE”  Fill the data for new template and start the email module. The bootstrap service present in the email module will load the template entries into the database. Available Templates  PASSWORD_RESET_TEMPLATE – Used when User Account is created for the first time  PASSWORD_EXPIRATION_REMINDER_TEMPLATE – Used when password expiry notification has to be created  ACCOUNT_LOCKED_TEMPLATE – Used when User account locked email is to be created  PASSWORD_RESET_EXTENDED_TEMP LATE - Used when Password Reset is done by admin  PASSWORD_EXPIRED_TEMPLATE – Used when password expiry email is to be created  FORGOT_PASSWORD_TEMPLATE – Used when Forgot Password email is to be created These templates are loaded from excel for self and all descendants. Note: This will work only when is empty 2. Template Service Templates can also be created by using rest services. Refer Template Service to know the list of API’s for creating templates. 5.2.2 Enumer ations Enumeration is nothing but a list of pre -defined values. All list of constants that need to be defined and changed at runtime for different tenants within the hierarchy can leverage Enumerations. In PAS, Enumeration is a hierarchical data type, o f type overridewhich can be customized and defined for each tenant. Similar to other hierarchical customizations, templates can be added for Self/All Descendants/for a Company Type /for a Company. Enumeration can be managed by an API exposed via Spring Re moting called ‘EnumerationService’ defined as a Spring Bean. Default enumerations and its enumeration values are loaded on bootstrap to",, "‘h_enumeration’ and ‘h_enumeration_value’ tables in respectively. The Enumeration and the Enumeration values in CARE loaded at bootstrap are:  Enumeration – Countries, States  Enumeration Values – Countries (India, US), States (States of India and US) Enumeration Attributes: 1) Identifier – unique name of the enumeration E.g. COUNTRIES, STATES 2) Description – description of the enumeration defined 3) parentEnumeration – value of the parent Enumeration, if any. E.g. Countries are parent enumeration of ‘States’. 4) enumerationValues - Mapping the list of values for enumeration Enumeration value attributes",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 55 of 133  Name – actual name of the enumeration values  labelName – Value of the enumeration to be displayed as label in the UI  enumeration – reference of associated enumeration. E.g. On Selection of Countries (US, India are the enumeration values related to enumeration COUNTRIES )  relatedEnumerationValues – values of the related enumeration E.g. On selection of India, the states of India will be displayed . Introducing new enumeration There are two ways of adding enumeration and enumeration values 1. Excel 2. UI Excel To create new enumeration, navigate to the b ootstrap excel of /src/main/resources/excels, namely brownstone_application_init_1.xlsx sheets named “app.ENUMERATION” Fill the data for new enumeration and navigate to “app.ENUMERATIONVALUE” fill the data for new enumeration values. Now start the api module, the bootstrap services for excel upload will load the enumeration entries into the database Note: This will work only when is empty UI Enumerations can also be added through UI, under the menus My Config and Manage Offshoot. Enumerations defined under My Config are applicable for Self. Enumerations for All Descendants/ a company type/ a specific company can be defined under Manage Offshoot . While adding enumerations through UI, the user has to def ine the enumeration with name, related enumeration and enumeration values. 5.2.3 Localization In PAS, it is possible to upload locale specific translations at run time. Here Localization is hierarchical data where values for specific keys can be defined based o n the locale. Localization can be managed through an API called ‘I18NService’ defined as a spring bean and exposed as a remote service. The keys and its values are captured in ‘h_i18nkey’ and respective values in",, "‘h_i18nvalue’ tables of respectively specific to locale. Localization Attributes: • key – the identifier of the hierarchy data • values – set of values where each value is mapped to a locale o locale – a set of parameters that defines the user's language, country o value – actual value to displayed in the UI based on locale E.g. mobileLabel is the key, then the values can be  Mobile for en_US (English locale)  携帯電話 for ja_JP (Japanese -locale) Localization can be added through UI, under the menus My Config and Manage Offshoot. Localizations defined under My Config are applicable for Self. Localizations for All Descendants/ a company type/ a specific company can be defined under Manage Offshoot .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 56 of 133 While adding Localizations through UI, the user has to define a Key, the set of values and the locale associated to each value. 5.2.4 Domain Metadata In PAS, specific domain related meta information and resources can be saved a nd retrieved. The applied configurations will be reflected in hierarchical manner i.e, the configuration done for a specific domain will apply to childs. Below are two types of metadata storage allowed. 1.Configuration Map Meta information can be store as key value pair against a given type. For example, if we take UI example, Assume there is a different landing page for Tenant A and Tenant B, if we want to configure the same, these will be sample configuration respectively. Tenant A configuration Type – ui-links Key - landing -page Value - http:///landingpage Tenant B configuration Type - ui-links Key - landing -page Value - http:///landingpage Sample Request Descript ion Create Domain configuration URL http://{hostname}:{port} /metadata -web/json/domain -metadata/configuration HTTP Method POST Path Parameter N/A Query Parameter N/A Request Body { ""domainname"": ""tenantB"", ""type"": ""ui -url"", ""configkey"": ""landing -page"", ""configValue"": ""http:///landingpage"" } Header Parameter Content -Type: application/json HTTP Headers Accept: application/json Request http://localhost:81/metadata -web/json/domain -metadata/configuration HTTP Response 200 Samp le Fetch Request",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 57 of 133 Description Fetch Domain configuration URL http://{hostname}:{port} /metadata -web/json/domain -metadata/ /configuration/{domainname}/{type}/{key} HTTP Method GET Path Parameter domainname - tenantB type- ui-urls key- landing -page Query Parameter N/A Request Body N/A Header Parameter N/A HTTP Headers Accept: application/json Request http://localhost:81/metadata -web/json/domain - metadata/configuration/tenantB/ui -urls/landing -page HTTP Response 200 { ""key"": ""landing -page"", ""value"": ""http:///landingpage"" } For Updating the configuration, Description Update Domain configuration URL http://{hostname}:{port} /metadata -web/json/domain -metadata/configuration HTTP Method PUT Path Parameter N/A Query Parameter N/A Request Body { “id”:2, ""domainname"": ""tenantB"", ""type"": ""ui -url"", ""configkey"": ""landing -page"", ""configValue"": ""http:/// newlandingpage "" } Header Parameter Content -Type: application/json HTTP Headers Accept: application/json Request http://localhost:81/metadata -web/json/domain -metadata/configuration HTTP Response 200 Sample Request For fetching all the key/value pairs against a given type Description Fetch All Domain configuration for a type URL http://{hostname}:{port} /metadata -web/json/domain -metadata/",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 58 of 133 /configuration/{domainname}/{type}/all HTTP Method GET Path Parameter domainname - tenantB type- ui-urls Query Parameter N/A Request Body N/A Header Parameter N/A HTTP Headers Accept: application/json Request http://localhost:81/metadata -web/json/domain - metadata/configuration/tenantB/ui -urls/all HTTP Response 200 [ { ""key"": ""landing -page"", ""value"": ""http:///landingpage"" } ] 2. Confiuration Resource Meta information can be stored as key and re source file pair against a given category. We take a UI example, Assume you want to show different header image for Tenat A and Tenant B, these will be sample configuration respectively, Tenant A configuration category – images key - header file - tenan tAheader.jpg Tenant B configuration category - images key - header file - tenantBheader.jpg Sample Request Description Create Resource configuration URL http://{hostname}:{port} /metadata -web/json/domain -metadata/resources HTTP Method POST Path Param eter N/A Query Parameter N/A Multipart Request Body category - images key - header file - Header Parameter Content -Type: multipart/form -data HTTP Headers N/A Request http://localhost:81/metadata -web/json/domain -metadata/resources HTTP Response 200",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 59 of 133 So when you try to fetch the resource, the mapping is done as per the above configuration and related resource will be supplied. Sample Request Description Fetch Domain Resource URL http://{hostname}:{port} /metadata -web/json/doma in- metadata/resources/{domainname}/{category}/{key} HTTP Method GET Path Parameter domainname - tenantB category - images key- header Query Parameter N/A Request Body N/A Header Parameter N/A HTTP Headers N/A Request http://localhost:81/metadata -web/json/domain - metadata/resources/tenantB/images/header HTTP Response 200 File - ",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 60 of 133 6 Security Microservice Following are the security mechanism followed in PAS . 6.1 Authentication CARE provides support for following three type of authentic ation by default: 1. Platform In -Built Authentication 2. Delegated SAML Authentication 3. LDAP Authentication 6.1.1 Platform Authentication In Platform authentication, complete authentication cycle in contained within CARE components. User provisioning, password expir y, password policy enforcement etc. is done by the platform itself. Following diagram depicts the flow of authentication in this mode. Following are the key features of Platform based Authentication:  Strong password policy enforcement using configurab le password policy.  Passwords are encrypted and stored in the database for increased security.  System generated passwords expires automatically expire after 24 hours.  Use of token based authentication and zero trust of server side sessions.  All access t o the platform is authenticated and secured by an authentication token or via certificates.  Strong token encryption to avoid breaking of tokens  Every request is intercepted and token validated before transferring to the service layer. All invalid requests are automatically logged and rejected.  Cookie does not contain any user data and used only as a reference for the server to pick up actual user data from the server",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 61 of 133 6.1.2 SAML Authentication Platform supports delegated authentication using third party ident ity service providers. Communication to authentication service provider is secured using shared certificates and SAML. Steps to configure SAML mode 1. To configure SAML authentication, we need to change ‘authentication_scheme’ value from “default” to “saml” in application.yaml file in the following wars:  Security -boot-x.yz.war path: security -boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  metadata -boot-x.yz.war path: metadata -boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  application -api-boot-x.yz.war path: application -api-boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  application -ui-springmvc -boot-x.yz.war path:application -ui-springmvc -boot-x.y.z-war\\WEB -INF\\classes \\ application.yaml Note : If authentication_shcme is “ default” , Platform ba sed Authentication will be done. 2. To configure SAML Authentication need to change ‘authentication_mode’ value from “default” to “saml” in application.yaml file of the following wars:  Security -boot-x.yz.war path: security -boot-x.y.z-war \\WEB -INF\\. class es\\ application.yaml  metadata -boot-x.yz.war path: metadata -boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  application -api-boot-x.yz.war path: application -api-boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  application -ui-springmvc -boot-x.yz.war path:application -ui-springmvc -boot-x.y.z-war\\WEB -INF\\classes \\ application.yaml 3. Replace SAML Excel for security -web 4. Make sure the CARE application runs in the port other than 8080 5. Configure the host like : openam.example.com. 6. Hit Url : 7. It will redirect to openAm login page.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 62 of 133 6.1.3 LDAP Authentication 1. To configure LDAP based authentication, we need to change ‘authentication_scheme’ value from “default” to “ldap” in application.yaml file present in following wars:  Security -boot-x.yz.war path: security -boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  metadata -boot-x.yz.war path: metadata -boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  application -api-boot-x.yz.war path: application -api-boot-x.y.z-war \\WEB -INF\\. classes \\ application.yaml  application -ui-springmvc -boot-x.yz.war path:application -ui-springmvc -boot-x.y.z-war\\WEB -INF\\classes \\ application.yaml Note : If authentication_scheme i s “default” , platform based authentication will be done. 2. Set LDAP properties in application.yaml file of security -boot.war like as Where, providerURL: the LDAP url, userDn: user name of LDAP server, password : password of LDAP server, groupSearchBase: group where users are provisioned in LDAP server. Excel Configuration: Set XL_Location to “otherexcels” in application.yaml file of security -boot-x.y.z.war as below Provisioning LDAP users in PAS : If you are logged into the application, list of users that are not provisioned can be displayed by clicking Admin  Unprovisioned Users submenu.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 63 of 133 Provisioning the users in CARE is done by assigning any role to the user in PAS, as shown below: The screen shows list of avail able roles in the system. Select one or more roles and click save button. The message will confirm that user is provisioned and associated to selected roles. Provisioned user information can be verified in the CARE database tables",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 64 of 133 Please refer to Roles and Access Management section to know more about how to add new roles in the system. 6.1.4 Multifactor Authentication CARE provides multifactor authentication mechanism which in addition to the default authentication with the username and password, have additional security layer to authenticate user by either One Time Password (OTP) or Time -based One time Password (TOTP). 6.1.4.1 OTP A one -time password ( OTP), also known as one -time pin or dynamic pa ssword, is a password that is valid for only one login session or transaction. In addition to the default (username and password) authentication, OTP authentication can be enabled in the following steps. 1. Set ‘database_auth: true’ in the application.yaml file to enable database authentication. database_auth: true 2. For the users of the domain to be OTP authentication enabled, ‘totp’ should be updated in the ‘pasauthenticationprovider’ table against the domain with the following API in the Authentication Pro viders Service. PUT : Updates Auth Provider. /authproviders/updateAuthProvider Json Input: { ""id"": 1, ""name"": ""otp"", ""description"": ""otp authentication"", ""authDesc"": ""otp"", ""domainName"": ""hcl.com"", ""editedBy"": ""admin"", ""leftIndex"": 0, ""rightIndex"": 0, ""createdBy"": ""admin"", ""applyToChild"": true, ""createDate"": ""2020 -01-13T10:47:07.313Z"", ""modifiedDate"": ""2020 -01-13T10:47:07.313Z"" } 3. The validity time and length of the OTP can be configured in the application.yaml as follows: otp.de fault_length: 6 (Default length is 6) otp.max_life_time: 5 (Default validity time is 5 minutes) 4. While logging into the CARE, default authentication with username and password is done as follows:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 65 of 133 5. Then it prompts for the Generate OTP link as follows: 6. After clicking on Generate OTP link, The OTP is generated and sent to the user’s mail / mobile number and the user enters the OTP in the screen as follows :",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 66 of 133 7. Once the received OTP is entered by the user in the screen, the validation is successful and lo gs in to the application as follows: API used to generate the OTP is as follows: Description Generate the OTP for the username URL http://{hostname}:{port} /security -web/json/otp -services/generateOtp HTTP Method POST Path Parameter N/A Query Paramete r N/A Form Parameter j_username : This is the username org : This is the domainname Header Parameter N/A HTTP Headers Accept: text/plain Request http://localhost:20090/security -web/json/otp -services/generateOtp HTTP Response The response is text sho wing the OTP. 6.1.4.2 TOTP Time -based one -time passwords are commonly used for two -factor authentication. TOTP is an algorithm that factors in the current time to generate a unique one -time password. Time - based one -time passwords provide additional security, beca use even if a user's traditional password is stolen or compromised, an attacker cannot gain access without the TOTP, which expires quickly (usually 30 seconds). In mobile app implementations, the user only needs to launch the TOTP application and then key-in the TOTP that appears on -screen onto the web application's login screen or for critical operation access. Unlike most mobile -based one -time passwords that need to be received via a text message or via the Internet through some wireless connection, TOT Ps aren't dependent on the presence of a cellular signal or data connection. Time -based One -Time Password (TOTP) token services rely on the physical device. Steps to enable TOTP - Multifactor Authentication: 1. Set ‘database_auth: true’ in the application.y aml file to enable database authentication.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 67 of 133 database_auth: true 2. For the users of the domain to be TOTP authentication enabled, ‘totp’ should be updated in the ‘pasauthenticationprovider’ table against the domain with the following API in the Authenticatio n Providers Service. PUT : Updates Auth Provider. /authproviders/updateAuthProvider Json Input: { ""id"": 1, ""name"": ""totp"", ""description"": ""totp authentication"", ""authDesc"": ""totp"", ""domainName"": ""hcl.com"", ""editedBy"": ""admin"", ""leftIndex"" : 0, ""rightIndex"": 0, ""createdBy"": ""admin"", ""applyToChild"": true, ""createDate"": ""2020 -01-13T10:47:07.313Z"", ""modifiedDate"": ""2020 -01-13T10:47:07.313Z"" } 8. After Admin creates the user or in case the user uses Forgot/Reset Password link, a mail with the url containing the encrypted code, for password set/reset will be sent to the user. Eg: http://localhost:8585/care/confirmPassword?code=V2 - 6hDv_7fVHvlIHsu0L7MjFB20sYknhN1hgqUXxa18 9. Using the url, the user can set/reset the password, set the security Questions/ answers and scan the generated QR code into a TOTP mobile app (Google Authenticator ) installed in his/her phone as follows: 10. The application prompts the user to ensure the user scans the QR code as follows:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 68 of 133 11. Once the scan completes, a new user account (along with the name of the web app) will be created in the Google Authenticator mobile app as follows: 12. The user account in the Google Authenticator app, you'll notice that it's accompanied by a code (e.g. 259111 ) that changes every n -number of seconds (usually 30 seconds). That's the Time -based One Time Password or TOTP. 13. In order for the user to login or to use any MFA authentication enabled critical operation, a user should enter the current TOTP into the field provided on the applicatio n's login screen/ TOTP field for successful authentication as follows:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 69 of 133 14. Once the entered TOTP is validated successfully, the user is logged in to the application as follows: 15. Once the user has verified, a user will no longer have to enter a shared ke y or scan a QR code in succeeding logins/authentication. All the user has to do in succeeding logins is to key -in the TOTP currently displayed on user’s mobile app into the Verify field. Multifactor Authentication Service – TOTP APIs : Multifactor Authen tication Service includes TOTP services which helps to generate/regenerate the QR code for the users to sync with the user's Google Authenticator App and validate the TOTP token against the session to provide multifactor authentication for the users during login or any other critical operations. 1. Get QR code for the user Description Enable TOTP and Return QR Code for the User to sync with the device URL http://{hostname}:{port}/security - web/json/ totp/getQRCode/encryptedCode/{encryptedCode} HTTP Met hod GET",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 70 of 133 Path Parameter encrytedCode: Encrypted Code Query Parameter N/A Form Parameter N/A HTTP Headers Accept: application/json Request http://localhost:20090/security - web/json/totp/getQRCode/encryptedCode/M7C_sDzftc - FJmWD0XoeaQCf211CNNivn0 HTTP Response The Response is the byte array of the QR Code image 2. Activate the user for the TOTP Authentication: Description Activate the user for TOTP Authentication after user syncs the QR code to the device. URL http://{hostname}:{port}/security - web/json/totp/activateUser/encryptedCode/{encryptedCode} HTTP Method GET Path Parameter Encrypted Code Query Parameter N/A Heade r Parameter N/A HTTP Headers Accept: application/json Request http://localhost:20090/security - web/json/totp/getQRCode/encryptedCode/M7C_sDzftc - FJmWD0XoeaQCf211CNNivn0 HTTP Response HTTP Response Code 3. Reset QR code for the user: Description Reset the QR Code for the User to sync with the device URL http://{hostname}:{port}/security - web/json/ totp/reset/encryptedCode/{encryptedCode} HTTP Method GET Path Parameter encrytedCode: Encrypted Code Query Parameter N/A Form Parameter N/A HTTP Heade rs Accept: application/json Request http://localhost:20090/security -web/json/totp/reser/encryptedCode/M7C_sDzftc - FJmWD0XoeaQCf211CNNivn0 HTTP The Response is the byte array of the QR Code image",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 71 of 133 Response 4. Validate the TOTP token: Description Validate t he entered TOTP against the user URL http://{hostname}:{port}/security -web/json/ totp/validateTotp/{userName}/{totp} HTTP M ethod GET Path Parameter userName: User Name totp: TOTP code generated from the device Query Parameter N/A Form Parameter N/A HTTP Headers Accept: application/json Request http://localhost:20090/security -web/json/totp/validateTotp/admin/548792 HTTP Response Returns true/ false 5. Validate the TOTP token after the user logs in (for the Session user): Description Validate the entered TOTP against the user and stores the session Id URL http://{hostname}:{port}/security -web/json/ totp/validateTotp/{userName}/{totp} HTTP Method GET Path Parameter userName: Username totp: TOTP code generated from the device Query Parameter N/A Form Parameter N/A HTTP Headers Accept: application/json Request http://localhost:20090/security - web/json/totp/validateSessionTotp/admin/548792 HTTP Response Returns true/ false 6. Get QR code for the logged user Description Return QR Code for the logged User to resync with the device URL http://{hostname}:{port}/security -web/json /totp/getMyQRCode/{userName} HTTP Method GET Path Parameter userName: Username Query Parameter Domain: Domain Name Form Parameter N/A HTTP Headers Accept : application/json Request http://localhost:20090/security -web/json/totp/getMyQRCode/admin HTTP The Response is the QR Code image",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 72 of 133 Response 7. Get the Last validation details for the given session Description Get the last TOTP Authentication details URL http://{hostname}:{port}/security -web/json /totp/getTotpValidation HTTP Method GET Path Parameter userName: User Name Quer y Parameter Domain: Domain Name jwtId: Session Id Form Parameter N/A HTTP Headers Accept: application/json Request http://localhost:20090/security -web/json/totp/getTotpValidation HTTP Response The Response is the Json output containing last successfu l validation of the user against the given session. 6.1.5 OAUTH Authentication using OAuth 2.0 protocol is supported in the platform. Please refer the below document for O120003_OAUTH.d oc 6.2 Authorization Authorization is enforced by using role b ased access control and edition management. Apart from roles defined in by the tenants, CARE also support a default System Role. 1. Role based access control a. Definition 1. Every role will have multiple permissions. 2. Each user can be associated to multiple roles. 3. Every company will have their own set of roles mapped with permissions. b. Enforcement 1. Permissions can be enforced for menus using menu.xml 2. Permissions can be enforced for CRUD operations of any entity through the data access layer. 3. Permissions can be enforc ed for any business service method using java annotations. Following screen shot shows available roles and permissions for a specific tenant. Highlights shows the selected role and permissions.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 73 of 133 6.2.1 System Role  System roles are the roles that are not speci fic to any tenant.  This system roles by default are available throughout the platform for all the domain independent of the hierarchy  For the System Roles, the tenantid is updated as -1 in the database.  Supported system roles from PAS o System Admin o System User Following screen shot shows the table view from the database for System Role: 6.2.2 How to introduce new System Roles?  Initial role required for the application in the CARE is loade d through bootstrap. Hence, system roles can also introduced in the same way  Under security module, open security -boot.war/WEB - INF/classes/excels/brownstone_sec_init_1.xlsx, navigate to the sheet “sec.ROLE” specify the company attribute value as -1 as show n below.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 74 of 133 6.2.3 Product and Services Product and services feature allows to configure the applicable actions/operations at each company level. In PAS, authorization is enforced by using permissions based access control. Service: In PAS, every service is c reated with one or more permissions. Product: A Product is created with one or more services. Associating Product to a company: When a product is associated to a company, the users of the company are restricted to access only the permissions forming th e service which in turn is associated to the product and to the company. 6.3 CARE Security and Micro S ervice When CARE is deployed in Micro service based architecture, following sequence will be followed for authentication and authorization. 1. Client/User reques ts a protected resource in Application UI module. 2. Authentication filter in UI module checks if the user is authenticated (looks for a cookie). If the user is not authenticated, UI module redirects the user to security module for login. 3. Client is redirected by the browser to the security module for authentication.  Security module prompts the user for authentication.  User submits his credentials to security module. 4. Security module processes the credentials.  Validates the credentials.  If successful, generate s a random token, associates it to the user and stores it in database.  Sets the generated token as a cookie and redirects the user to access resource. 5. Client is redirected back to the accessed resource but this time with the cookie. 6. Authentication filter v alidates the user request",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 75 of 133  Finds the cookie in the request.  Sends a request to security module along with the cookie to authenticate the request.  Security module processes the cookie, finds the associated user and returns  User  Company  Permissions of the u ser. 7. Authentication filter finds the request as authenticated and pass the permissions to authentication filter. 8. Authorization filter processes the request.  Checks if there are any permissions mapped to the URL.  If yes, checks if the user has that permissi on else redirects to an access denied page. 9. Authorization filter passes the request to Spring MVC controller which checks if this is a spring mvc request and passes the request to controller class. Controller class calls application services/CARE service t o serve the request. 10. REST API is used invoke the application services/CARE services deployed in Application API module along with the cookie submitted by the client. 11. Authentication filter in Application API filter validates the user request  Finds the cooki e in the request.  Sends a request to security module along with the cookie to authenticate the request.  Security module processes the cookie, finds the associated user and returns  User  Company  Permissions of the user. 12. Authorization filter processes the r equest.  Checks if there are any permissions mapped to the URL or to the API  If yes, checks if the user has that permission else throws an access denied exception. 13. Invokes the application services. 14. Application services in turn invoke the CARE services to se rve the request and the response is returned to Application UI module. 15. Application UI module serves a response based on the business logic.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 76 of 133 6.4 User Password There is provision in CARE to support for defining the password policy, forgot password settings and user to set his password for the first time. This is applicable only in case the authentication_scheme is set to default. 6.4.1 Password P olicy CARE supports configuration of password policy to secure the user passwords. Password policy in CARE enables to configure various parameters relation to user password and its security. Security questions are used during forgot password. These questions are internationalized and can contain localized data.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 77 of 133 6.4.2 Forgot password User password can be managed in three ways 1) forgot password, 2) change password and 3) first time password Forgot password can be used to reset user password when the user forgets his credentials. Forgot password is secured with multiple security questions which is set by user during his first t ime login. 6.4.3 Password reset User can change his password anytime by going to administration pages. When the user is provisioned, an email will be sent to him with a link to set his password and security questions. After setting the password, user will be ab le to login. 6.5 Session management 1. User session is managed by using cookies which do not contain any sensitive information. 2. User session will be invalidated due to idle timeout and / session timeout. 3. Idle timeout: When user remains idle for a configurable pe riod of time, session will be logged out. 4. Session timeout: user will be logged out after a configurable period of time. Below is a sample configuration of idle timeout and session timeout 6.6 Key Management  CARE comes with a default keystore that stores al l encryption keys used in the platform.  The KeyStore Management Service provides a common set of helper functions to access the keystore.  Acts as a single place to replace key management related functionality with a more hardened solution like a Hardware Security Module.  The main purpose of the service is to provide a key (or phrase) required for the encryption. The service can import the key as well as export the key with appropriate credentials.  Keys will be stored and retrieved from a keystore file us ing the parameters, o Storepass – password for keystore o Keypass – password to be stored  The keystore file has to be placed in the local system drive and the location needs to",, be specified in the property files in the variable Store_Location,, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 78 of 133 Also the parameters like , Store_Pass, Key_Pass, alias need not be modified if any other external key is imported as it will be overridden . Default parameters of the current Keystore Storepass = brownstone123 Keypass = keypassword Alias = brownstone First time creation of keystore KeyStore is initially created manually using the keytool command on the command line keytool -keystore brownstoneStore.jceks –storetype jceks -genkey -alias brownstone - storepass storepassword -keypass keypassword command parameters: -keystore – name of the keystore to be mentioned -storetyp e – type of the keystore -alias – alias -storepass – password for keystore -keypass - password for t he key 6.7 OWASP Guidelines Apart from the security features described, the platform also comes tested for the top 10 OWASP security threats and has threat prevention measures that can be utilized to thwart these attacks. The critical attacks that are tested for are  Injection  XSS  Broken Authentication  Broken Session Management  Insecure Direct Object Reference  XSRF  Security Misconfiguration  Insecure Cryptographic Storage  Failure to restrict URL Access  Insufficient Transport Layer Protection  Unvalidated Redirect s and Forwards A dedicated document on how OWASP guidelines are followed and implementation will be shared separately.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 79 of 133 6.8 Cross Domain Access Cross domain access support has been detailed out in the below referenced document. Document name - O120003_CROS S_DOMAIN_ACCESS 6.9 Token Validation Security microservice will validate the User token for all the requests from any microservice. Also the it will cache the result till the user get logged out/ deactivated or the user role get changed. Similarly user domain access will also get validaed and cached in the same manner .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 80 of 133 7 Email Service Contains the Rest APIs, used to create email messages with pre -defined templates in PAS. Exposed as the rest service  The Email Message is for creating an email message wit h the predefined template. These templates will be made available through bootstrap service.  The API’s used for fetching the available template is TemplateService API which consist of the following methods.  Generally the template bean will be null, if ther e is no template with the given name.  From the available template one can get the sender details and can set the message content based on the format (HMTL \\Simple Text) 7.1 Email Rest Service Contains API to post the email messages to the DB based on the email message parameters Post Email Message : Description Post the email message URL http://{hostname}:{port}/email -web/json/emails/ HTTP Method POST Path Parameter N/A Header Parameter/Bod y template.txt HTTP Headers Accept: text/plain Request http://www.pas.com:20084/email -web/json/emails/ HTTP Response HTTP Response Code Following are the available MIME_TYPE constants from EmailAttachmentBeans:  MIME_TEXT_HTML_NAME - MIME_TEXT_HTML (name of the Mime type text/html)  MIME_TEXT_PLAIN_NAME - MIME_TEX T_PLAIN (name of the Mime type text/plain)  MIME_TEXT_CSS_NAME - MIME_TEXT_CSS (name of the Mime type text/css)  MIME_VIDEO_AVI_NAME - MIME_VIDEO_AVI (name of the Mime type video/avi)  MIME_IMAGE_BMP_NAME - MIME_IMAGE_BMP (name of the Mime type image/bmp)  MIME_IMAGE_GIF_NAME - MIME_IMAGE_GIF (name of the Mime type image/gif)  MIME_IMAGE_JPEG_NAME - MIME_IMAGE_JPEG (name of the Mime type image/jpeg)  MIME_APP_MIME_NAME - MIME_APP_MIME (name of the Mime type application/mime)  MIME_APP_EXCEL_NAME - MIME_APP_EXCEL ( name of the Mime type application/excel)",, "application/excel)  MIME_APP_OCTECT_STREAM_NAME - MIME_APP_OCTECT_STREAM (name of the Mime type application/octet -stream)",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 81 of 133 7.2 Template Services The Rest APIs available for Template Management is “TemplateSe rvice” Followings are the list of API with their usage. Fetch Templates: Description Fetch the email message templates URL http://{hostname}:{port} /email - web/json/templates?domain={domain}&locale={locale} HTTP Method GET Path Parameter N/A Query Param eter domain = Domain info locale = Locale attribute Header Parameter N/A HTTP Headers Accept: application/json Request http://www.pas.com:84/email - web/json/templates?domain=hcl.com&locale=en_US HTTP Response No Content Post Template – Self/Specific : Description Post a template for self domain URL http://{hostname}:{ port}/email - web/json/templates?domain=hcl.com&locale=en_US HTTP Method POST Path Parameter N/A Query Parameter N/A Header Parameter/ Body template.txt HTTP Headers Accept: application/json Request http://www.pas.com:84/email - web/json/templates?domain=hcl.com&locale=en_US HTTP Response HTTP Response Code Post Template – Descendents: Description Post a template for descendents URL http://{hostname}:{ port}/email -web/json/ templates/all HTTP Method POST Path Parameter N/A Query Parameter N/A",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 82 of 133 Header Parameter/ Body template.txt HTTP Headers Accept: application/json Request http://www.pas.com:84/email -web/json/templates/all HTTP Response HTTP Response Code Post Template – Company Type: Description Post a template for descendents URL http://{hostname}:{ port}/email - web/json/templates/companyType/{Company_Type} HTTP Method POST Path Parameter Company_Type : Name of the Company Query Parameter N/A Header Parameter/ Body template.txt HTTP Headers Accept: application/json Request http://www.pas.com:84/email - web/json/templates/companyType/PASCOMPANY HTTP Response HTTP Response Code Fetch Template by template name: Description Fetch the template i dentified by the template name URL http://{hostname}:{port} /email - web/json/templates/templateName/{template_name} HTTP Method GET Path Parameter template_name – Name of the template Query Parameter N/A Header Parameter N/A HTTP Headers Accept: appl ication/json Request http://www.pas.com:84/email - web/json/templates/templateName/NEW_TEST_TEMPLATE HTTP Response The response is json will be showing the template information. Update Template: Description Update a template fields URL http://{hostname} :{port}/email -web/json/templates/updateTemplate HTTP Method PUT",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 83 of 133 Path Parameter N/A Query Parameter N/A Header Parameter/ Body template.txt HTTP Headers Accept: application/json Request http://www.pas.com:20084/email - web/json/templates?domai n=hcl.com&locale=en_US HTTP Response HTTP Response Code 7.3 Email SMTP Services Contains The Rest APIs to configure the SMTP properties from which the mail sender services gets the SMTP configuration dynamically by default. The user can add, update or deact ivate the SMTP configuration as and when required in order to take effect dynamically. Followind are the REST APIs available for SMTP related configurations: Configure / Activate SMTP Settings: Description Configure / Activate SMTP Settings URL http:// {hostname}:{port}/email -web/json/smtp HTTP Method POST Path Parameter NA Query Parameter N/A Form Parameter/ Body server - to define where the server is running (by default it is localhost). It can be customized to the machine ip in which SMTP server is running port - port on which SMTP server is running timeout - server time out(in milleseconds) authrequired – true / false username - username if it requires authentication password - password if it requires authentication supportssl - support for http s (true / false) HTTP Headers Accept: application/json Request http://www.pas.com:20084/email -web/json/smtp HTTP Response HTTP Response Code Deactivate SMTP Settings: Description Deactivates the active SMTP Server URL http://{hostname}:{port}/emai l-web/json/smtp/deactivate/server",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 84 of 133 HTTP Method DELETE Path Parameter Server Id ( Id of the server that needs to be deactivated. Query Parameter N/A Form Parameter/ Body NA HTTP Headers Accept: application/json Request http://www.pas.com:20084/email -web/json/smtp/ deactivate/server HTTP Response HTTP Response Code Fetch SMTP Settings: Description Fetch all the available SMTP Settings URL http://{hostname}:{port}/email -web/json/smtp/getSmtp HTTP Method GET Path Parameter NA Query Parameter N/A Form Parameter/ Body NA HTTP Headers Accept: application/json Request http://www.pas.com:20084/email -web/json/smtp/ getSmtp HTTP Response HTTP Response Code Update SMTP Settings: Description Update the SMTP Server parameters URL http://{hostnam e}:{port}/email -web/json/smtp/updateSmtp HTTP Method PUT Path Parameter NA Query Parameter N/A Header Parameter/ Body Example : { ""id"": 12, ""server"": ""10.98.11.14"", ""port"": 25, ""timeout"": 300, ""requiresAuth"": false, ""userName"": """", ""password"": """", ""supportSsl"": false, ""status"": 0",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 85 of 133 } HTTP Headers Accept: application/json Request http://www.pas.com:20084/email -web/json/smtp/s updateSmtp HTTP Response HTTP Response Code",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 86 of 133 8 Mail Sender Service Mail Sender is an as sociate module of the Email module of CARE. This module send out the mail to the recipients based on the templates and the messages that are pushed in the email_message table in the Email module . Following are some of the scenarios where mail sender servi ces triggers the mail  Password set for the first time by the user  On account lock (based on the inputs from password policy)  Mail for Password Expiry Reminder that are triggered by Scheduler jobs The tables that are referred by this module are  email_a ttachment  email_message  email_recepient 8.1 Sending Mail Through SMTP Mail sender service provides implementation for sending mails though SMTP protocol. The SMTP configuration are provided in the SMTP_Properties table of the Email services. The SMTP configu rations can be added and activated or updates as and when required and are dynamically loaded and referenced by mail sender services and the activated SMTP configurations are used for sending mails. Refer Email SMTP S ervices for more details. If there are no SMTP configurations provided in the database, the SMTP configurations are loaded from the application.yaml properties of the mailsender services. Below are the SMTP configuration properties that need to be set i n the application.yaml file: SMTP Configuration Properties : server : 10.98.11.10 ( SMTP Server IP ) port : 25 ( SMTP Server Port ) timeout : 3000 (Server timeout in milliseconds) requiresauthentication : false (authentication required or not -true/ fals e) username : admin@agora.in (user name if authentication is required) password : admin (password if authentication is required) supportssl : false (true / false for SSL support) Additional properties: sleeptime : 10 (server sleep time (sec)",, "sleeptime : 10 (server sleep time (sec) # Default : 10. Set the batch count of messages for each thread batchsize: 10 # Default : 0. Set the interval time(in seconds) for delay between each batch of messages batch_interval : 0",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 87 of 133 # Set the below to true , if you want to reconnect everytime for sending each message, to avoid spamming reconnect_everytime : false # Set to true, if mail debug message to be displayed in the log debug_enabled : false 8.2 Sending Mail Through AWS Mail sender services also provides imp lentation for sending mails and SMS through AWS services. AWS uses SES ( Amazon Simple Email Service - Amazon SES) for sending mails and Amazon Simple Notification Service (SNS) for sending SMS to the users identified by the mobile number provided. Follow ing are the configurations required to send the email messages: #aws ses config ses_enabled: true ses_sender_mail_address: admin@agora.in ses_sender_display_name: 'CARE admin' OTP via SMS can be sent to the mobile number through Amazon SNS by enabling the following properies: #aws sns config sns_enabled: true sns_sender_id: senderId sns_max_price: 0.50 sns_sms_type: Transactional System Configurations for enabling OTP via Amazon SNS : Set the below configurations in your system Environment variables : 1) set pasProxyHost=campus -proxy 2) set pasProxyPort=80 3) set pasProxyUsername={your_hcl_username} 4) set pasProxyPassword={password} config credentials Place the above files in your system and give the path to those files in environment varia bles as in point 5 & 6 5) set AWS_CREDENTIAL_PROFILES_FILE=path/to/credentials_file 6) set AWS_CONFIG_FILE=path/to/config_file Notes:  OTP via SMS can be sent to any mobile number.  For receiving OTP via Email, the receiver email ID should be added and register ed on the AWS email services.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 88 of 133 8.3 Custom SMS sender The user can provide their own implemtation for sending the SMS to the user with the help of OTP Plugin. The logic for sending the SMS and be provided in the OTP plugin and the mail sender service will acc ordingly pickup the messages from the email_message table and provides the key details to the plugin and once the message is successfully sent or the failure of the message sending is sent bak to the mail sender service the status of the messages sent or not is updated accordingly in the email_message table by the mail sender service. Following configurations in the application.yaml file are added to enable custom SMS implementation: # If custom message sender implementation is used, set this property to true. Default is false. otp_custom_sender : false # If OTP must be enabled through SMS, along with email OTP, set this property to true. Default is false. otp_plugin_enabled : false # Custom plugin Class for SMS/Message sender. Specify absolute path of the implementation class name. pluginserviceclass : com.hcl.hmtp.otpplugin.OtpServiceImpl # Method Name of Custom SMS/Message sender implimentation . pluginservicemethod : sendMessage The implementation class and the method are provided in the foll owing file where the user can provide their own implementation. OtpPlugin.zip Once the implemtation is done, the above project should be converted in to jar file and the path of this jar file should be referenced while running the mailsender serv ices. If the custom SMS implementation is enabled, the mail sender service should be run in the following format: java -cp ""mailsender -boot-4.7-SNAPSHOT.jar"" -Dloader.path=<> -Dloader.main=com.hcl.hmtp.core.mailsender.server. MailsenderBootA pplication org.springframework.boot.loader.PropertiesLauncher secretAppCode=pas1243",, secretAppCode=pas1243,, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 89 of 133 9 Development Acceleration CARE comes with automation component that enhances the development through eclipse plugins. These plugins are provided by the CARE Plugin In staller 9.1 Eclipse plugin CARE Plugin installer CARE also supplies variety of eclipse plugins to speed up the development of applications over the CARE platform. Following plugins available in CARE as of now: 1. CARE CRUD plugin (Entity Generator) – generates the data models and beans defining the attributes also taking care of the relationship of the entities. 2. CARE UI Plugin (UI Generator) – generates the files required for performing CRUD operations for generated entities. UI generated using the plugin are response and uses bootstrap. 3. API Enablement plugin -The plugin populates user interface to configure API Specific information and exposes Restful web service for an existing java service method. 4. Unit Test case automation plugin (Unit Test case generator) - automates the test case generation for java files containing pojo/business entity model classes as well as for the classes containing business logic. 5. JPA Plugin – Plugin that generates the data models and the UI taking input as the selected db’s. 6. Service Tes t Plugin – That is used to generate UI and helps the testers to test the SOAP API/ method taking input from the selected source file. CARE Plugin installer is the installer by which the available automation plugins in CARE can be selectively installed in the eclipse. The primary purpose of this is to license the plugin usage and track the usage of plugins by other CARE Users in HCL. Pre Requisite: Note : Make sure the eclipse path (can be called as Eclipse home) does not contain spaces Plugin Instal lations Steps: 1. Copy PAS_Plugin_Installer.jar to the local folder system e.g. E: \\Test",, "2. Double click the PAS_Plugin_Installer.jar or go to command prompt  type the command “java –jar E: \\Test\\PAS_Plugin_Installer.jar”",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 90 of 133 3. Welcome wizard of CARE plugin installer w ill be opened. Read the 4. Click on next to choose the installation path. 5. In the wizard click on browse to choose eclipse home. 7. Click on save. It will ask for overriding the directory. Select yes.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 91 of 133 8. Then click on next to proceed. This is the selection pan el which is as follows",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 92 of 133 Developer can select the plugins that he wishes to install from the above screen. By default all plugins will be selected. One can uncheck if the plugin that is not needed for him. 9. Then click on “Next” to proceed to installation panel and process panels. 10. Once the installation is complete. The final panel will be as follows",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 93 of 133 Uninstalling the Plugins: 1. Go to control panel  uninstall programs  look out for CARE Plugin  select to uninstall 2. Select Uninstall/Change 3. This will op en the CARE Plugin uninstaller window, which can be as follows",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 94 of 133 4. Select “Uninstall” button from the window. Note : don’t select the force deletion of eclipse, which will completely delete the eclipse from your system 5. Wait until the progress bar is comple te. This might take 10 -15minutes. 6. Once it is complete click on quit to exit 7. Uninstallation process completely uninstalls all the plugins that you selected to install. 9.2 CRUD Plugin CRUD plugin is a CARE plugin that automates the data model generation i n PAS Why we need a CRUD Plugin?  CARE CRUD plugin is used to develop Data models and its supporting files on top of CARE in an easy way.  It accelerates the development speed, enforce standards, reduce defects and hence reduces the time and effort. What d oes CRUD plugin generate?",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 95 of 133  CARE CRUD plugin generates the following files for the given inputs.  Entity - Entity class is for creating tables and column attributes in the Database.  Bean - Bean class is for client side interaction.  Bean _ - Bean_ is a meta -model which is used with criteria queries to build simple or complex functions for identifying the attributes.  Validation.xml - Validation xml has the validations specified for each attribute and is validated while persisting in the DB Non-Child Relations Non child relations used in CRUD plugin: CRUD plugin allows creating the entity with different types of relation. Relations supported are OneToMany, OneToOne, ManyToOne, ManyToMany Plugin UI Wizard Create Entity Bean wizard page where the user is allowed to specify the following details.  Entity Name : Name of the Entity that needs to be created.  Entity Source Folder : When Entity source folder browse is clicked, it prompts a window it allows to select the src folders of the selected project.  Entity Package : Specifies the package where the entity should get generated. The user can also modify the package name.  Super Class : Allows selecting an Entity that will be a Super class for the generating Entity.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 96 of 133  Interface : The generating Entity should implements the class “Entity” or “EditableEntity” which is mandatory. In addition to that, user can also select MultitenantEntity, PlatformEntity.  Bean Package : Specifies the package where the bean and bean_ classes should get generated. User can also modify the packa ge name.  Bean Source Folder : When bean source browse is clicked, it prompts a window wherein the user can select the folder from any module.  Attributes : Entity attributes can be added individually with its data types. Added attributes can be deleted by o n clicking the row of the table Non Relation Wizard Non-relational attributes wizard allows adding non -relational attributes for the Entity. Name: Attribute name of the related entity. Related Entity: Double click on the field, it prompts a window where in the user can browse and select the Related Entity . Relation Type: User is allowed to choose different types of relation between the generating Entity with the related Entity. Validation Wizard  Validation wizard is for providing validations for the att ribute individually.  Validation XML Folder: Allows selecting the appropriate folder where the validation xml should get generated.  Attributes: Set of attributes added for the selected Entity will get listed.  Mandatory: Check whether the selected attrib ute is mandatory or not.  Read -only: Check whether the selected attribute is Read only. This field will be non - editable.  Types of Validation: Allows choosing the type of validation for the selected attribute. Types of validations supported are Long Vali dation, List Validation, Date Validation, Expression validation. 9.3 UI Plugin Why CARE UI Plugin? CARE UI Plugin generates the UI related files for preforming CRUD operation of an Entity",, "and reduces developer time and effort. What does UI Plugin generate?  It generates JSP pages for create, list and update for a selected Bean. And also it creates Action class and struts xml configuration  The Plugin is capable of parsing the selected bean file and its superclass.  It generates the JSP’s with selected file’s a ttributes and its super class attributes",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 97 of 133  The Plugin also generates permissions for the CRUD operations and these permissions are mapped only to the Admin Role by default  The plugin also generates the menu xml file in which the permissions are provided to access the CRUD functionality in the UI  Provides the default support for adding extensions and invisible fields for the selected bean class  The generated JSP’s have I18n support How to generate? Open the bean class of an entity, right click on it. Select the menu CARE and then UI Code Generation .If the selected file is not Bean class, it will throw an error message. Configuration The below explains how the properties file can be configured for the default target src folder, JSP folder and struts xml fol der , Navigation Page Property file and I18n File.  Action class will get generated in the default src folder  Create, list and update JSP’s will get generated in the default JSP folder  Struts -.xml will get generated in the default struts.xml fo lder  Menu configuration for the selected bean is generated as “ -menu.xml” under default menu folder NOTE : While deploying the application the generated struts file must be included in the Struts.xml file",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 98 of 133  The files will get generated in the target src, web content and resources folder specified in the properties page of the project where the bean class is present.  If the file with same name exists in the target path, the existing file will be rename d and new files will get generated.  Plugin works only on the Bean class. 9.4 API Plugin Pre-Requisite For installing CARE API Plugin, make sure that following requisites.  JDK 1.6.0_11  Eclipse IDE version is 3.7.1 or above Preparing for the Installation The steps will guide us to the installation of CARE API enablement plugin. The following assumption has been made for the installation process.  All Pre -Requisite configured in the Eclipse IDE.  The installation is executed by an administrator with the following skillset o Knowledge of Java and Eclipse IDE. o Knowledge of installing plugin sites in Eclipse IDE. o Basic knowledge on REST API’s CARE API Plugin site is available in the below shared path. Install the CARE API site and restart the Eclipse IDE. Preparing fo r the deployment The steps will guide us to the deployment of CARE API plugin enabled REST services. The following assumption has been made for the installation process",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 99 of 133  The installation is executed by an administrator with the following skillset o Knowledge of java and J2EE and how J2EE components work o Knowledge of deploying application in Jboss 6.x/Apache Tomcat 7.0  Configured CARE API implementation supporting jars to App server If it is Jboss 6.x or Apache Tomcat deployment: Configure the below 11 jars t o application deployment path o commons -collections.jar o jackson -core-asl-1.9.2.jar o jackson -jaxrs -1.9.2.jar o jackson -mapper -asl-1.9.2.jar o jackson -xc-1.9.2.jar o javassist -3.3.GA.jar o jettison -1.1.jar o jsr311 -api-1.1.1.jar o resteasy -jackson -provider -2.3.2.Final.jar o resteasy -jaxrs -2.3.2.Final.jar o scannotation -1.0.2.jar If it is Jboss 7.x deployment: 1. Configure the below 3 jars to application deployment path. o jsr311 -api-1.1.1.jar o resteasy -jackson -provider -2.3.2.Final.jar o resteasy -jaxrs -2.3.2.Final.jar 2. Copy the jboss -deployment -structure.xml to the jboss 7.x deployment path. Sample file shared in above location. Project Property Setting for API Enablement Once the CARE API Site installed in the Eclipse IDE, for each project API Enablement property page will be display ed.  Select a project from Eclipse IDE Package Explorer  Click on Project -> Property ->API Enablement The Property page helps to configure the default values for API Enablement. These preconfigured values are populated in API Enablement Popup page. These va lues can be modified in the popup page. Default Source folder: (optional) Allows to select the source folder to which Code should be generated. Project specific source folder will be displayed in the browse option. Default Package: (optional) Configuring P ackage to which code should be generated. If package name doesn’t exist, packages will be created inside the selected source folder and",, code will generated.,, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 100 of 133 Deployment Descriptor Location: (optional) for enabling Restful web services, Deployment Descriptor file( web.xml) should be configured.Web.xml can reside within workspace, so browse option will allow to select the desired web.xml file. Figure : Project Property Setting",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 101 of 133 CARE API Plugin View  Select a service method to which Restful web service to be exposed.  Right click and select PAS -API -> API Enablement from context menu Figure : CARE API Plugin view",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 102 of 133 CARE API Plugin UI Popup API Specific information should be configured in the popup UI. By default few fields will be auto populated t hat can be edited. API Class Name : Specifies the file to which code should be generated. For incremental support same class name can be used. Class Name should follow Java standard. User can modify the pre populated values. Method Type : Depends on the se rvice method functionality, operation method type should be selected. By default POST will be selected. Consumer Type : By default application/json will be selected. Producer Type : By default application/json will be selected. Class URL : Specify the head er URL to access the Restful service. User can modify the pre populated values. The value should start with \\ character. Class level URL should be unique with in a project. Deployment will failed if same URL is available. Method URL : Specify the method U RL to access the Restful service. User can modify the pre populated values. The value should start with \\ character. Method level URL should be unique with in a class. API Wrapper Name : For each API Service class a wrapper class will be generated. In whi ch user can specify the service factory class to initiate the service class. Json Response Header : Specifies json response header. The field will be disabled if method return type is void. Source folder : Allows selecting the source folder to which Code s hould be generated. Project specific source folder will be displayed in the browse option. Package : Configuring Package to which code should be generated. If package name doesn’t exist, packages will be created inside the selected source folder and code w ill generated.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 103 of 133 Deployment Descriptor Location : for enabling Restful web services, Deployment Descriptor file (web.xml) should be configured.Web.xml can reside within workspace, so browse option will allow selecting the desired web.xml file. Parameter In fo: Depends on selected method, method parameter details will be listed in table format. Parameter Name : Parameter name is editable and it should follow java standards. Parameter name will be used to pass json request. Parameter Type: Depends on paramete r data type, user can specify the mode of request (path Param, Query Param or Body Param).User defined data type can be passed only as body param. Date Type: Displays the parameter data type. Not editable field. Figure: CARE API Plugin UI Popup view",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 104 of 133 CAR E API Plugin Success Message On successful completion of API Enablement, Plugin will display confirmation message. Figure: CARE API Plugin Success message CARE API Plugin Error Message Each API enablement action will verify the selected methods elig ibility; if it fails then error message will be populated. Below condition fails API Enablement.  Selecting a private method  Selecting a constructor  Selecting a method overloaded method  Selecting a method with complex data type  Failed to located web.xml fil e  Failed to create package",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 105 of 133 Figure: CARE API Plugin Error message CARE API Plugin default setting For enabling Restful web services, Deployment Descriptor file (web.xml) should be configured.Web.xml file we specified in the API Plugin popup. As a onet ime action web.xml will be modified and default Restful configuration will be done. User can edit for deployment specific configuration.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 106 of 133 Supported data types in API Plugin  Void  Primitive data type  String  Array  Wrapper data type  List  Map  List ? denotes any data type except collection  Map ? denotes any data type except collection Eclipse Version  The about page (Help -> About Eclipse) has some icons towards the bottom of the dialogue. This should include two which are the plain Eclipse icon . Select the one with tooltip ""Eclipse.org"". Eclipse has many components, each of which has its own version number. The core is the Eclipse Platform  Check readme file inside your Eclipse directory at path eclipse/readme/eclipse_readme .At the very top of this file it clearly tells the version number: By default rest keyword is used, that can edited and same keyword should be specified in both the places For each service class, an entry will added in the param value Tag. While deleting API file, corresponding entry should be deleted from here.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 107 of 133 9.5 Junit plugin This plugin is used to automate the test case generation for pojo/business model classes and for the classes containing business logic Prerequisites 1. Add junit(4.x) libraries to the project 2. Mocking framework adopted here is Easymock, add easymock(3.x) jar to the project How to use this plugin? Install CARE j -unit test case plugin in eclipse Make sure the CARE Unit Test plugin is installed through CARE Plugin installer. Create test folder in p roject module Typically every project requires a test folder where all unit test cases are written. This folder has to be configured so that the plugin can generate all unit test cases in the test folder. In order to do this, Open Navigator View  right cl ick on project and select properties to display project properties select Test case Generation Properties  select test folder name applyok Creation of test cases One can generate the test cases for a file or on a package containing n number of java files Open Package Explorer right click on Package containing java files / a java file click Test CaseGenerate Test Case OR Right click on any opened Java Editor (File) and Click Test Case -> Generate Test Case This will generate all unit test cases in the folder selected in the above step Note: We can create test cases only for java classes Controlling the generated Code",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 108 of 133 It is possible to control what gets generated by setting the code generator properties in eclipse preferences. Open eclipse windowpreferences testcase generator enable a demonstration of a preference page implementation check boxes applyok 1. Generate failure string If we will enable generate failure string ,it will show below method in test case. /** * Test Method: getMessage
* Test Scenario: try{} block: MissingResourceException ----->not thrown
*/ @Test () public void getMessage1 () { String failureString = """"; failureString = failureString + ""Test Method: getMessage \\n""; failureString = failureString + "" Test Scenario: try{} block: MissingResourceException ----->not thrown \\n""; classUnderTest .getMessage(); }",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 109 of 133 2. Assert fail stat ement in method body If we will enable add Assert.fail as part of method body it will show below method in test case. 3. Assert fail statement in try catch 4. If we enable add Assert fail statement in try catch, it will show below method in test case. /** * Test Method: getMessage
* Test Scenario: try{} block: MissingResourceException ----->not thrown
*/ @Test () public void getMessage1() { String failureString = """"; failureString = failureString + ""Test Method: getMessage \\n""; failureString = failureString + "" Test Scenario: try{} block: MissingResourceException ----->not thrown \\n""; classUnderTest .getMessage(); Assert. fail(failureString); } /** * Test Method: add
* Test Scenario: try{} block: HMTPException ----->not thr own
*/ @Test () public void add1() { String failureString = """"; failureString = failureString + ""Test Method: add \\n""; failureString = failureString + "" Test Scenario: try{} block: HMTPException ----->not thrown \\n""; try { classUnderTest .add(); } catch (HMTPException ex ) { Assert. fail(failureString); } catch (Exception ex ) { Assert. fail(failureString); } Assert. fail(failureString); }",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 110 of 133 4. Generate for abstract base class: If one needs to generate test methods for base class whose type if of abstract can be done by enabling this option. So this will generate test methods for the current file as well as abstract base class in the same generated file. 5.Exclude class pattern: Given the package for which the test cases are to be generated, and if one wishes to exclude some classes from being executed by this plugin can make use of this. e.g. If some metadm odel classes which is with prefix Bean_ are to be excluded then, by giving the pattern inside braces “(_Bean.java)” can work. If more patterns are to be used then n number of patterns can be giving inside braces with “; “ separated. Plugin Description Test cases for POJO classes: This plugin automatically generates test case methods for all setter and getter methods, hash code and equals method. If we want to create test case in pojo class for any other specific method apart from setter, getter, hash code and equals method then we need to write test case code manually . Test cases for business methods This plugin creates test cases for business logic methods plugin will be identifying code path then it will be generates number of test cases depends o n code path. This will generate the basic template for the possible number of test cases with javadocs that provides sufficient information to the developer. There are some scenarios that are handled by this plugin to mock or initialize variables based o n the code path. They can be categorized as Handled scenarios: 1. All method and member variables are handled if it is a part of code path 2. Simple expression are handled for basic data type based on the given condition 3. Simple expression for string/object wh ich means null and !null are handled",, "4. Service calls with simple expression that return basic datatypes are mocked based on the given condition 5. Service calls with simple expression that return String literal and if the condition in the codepath is null or !null are mocked 6. Method variables that are not a part of codepath are initialized with default value of “1” for primitive data types and new String/Object() for any String or object respectively Unhandled scenarios: 1. Code path with local variables present in its condition 2. Code path with complex expressions are not handled 3. Code path with ternary expression 4. Service calls with complex expression that returns any type of data are not handled Thus in case of test case generation, all handled expressions will be m ocked and unhandled expressions will be given with TODO statement with specified condition to the developer to handle it manually",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 111 of 133 Example for creating test case to below business model method The above method will be generates two test case methods. One test case method for if (company != null && company.size() == 1) is true and another test case for if (company != null && company.size() == 1) is false. Tips to the developers to modify the generated test cases 1. For service classes, the develope rs can make use of comment given in the TODO and mock the variables based on true and false conditions 2. For a method with no code path, a single method will be generated and incase if it contains reference class objects as method parameter, mocked statement s from easymock will be generated whereby the developers has to fill in the “MISSING” variable and return value of the statement",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 112 of 133 3. CARE UT plugin completely generates the test case for POJO methods, with normal setter and getter. If any changes done in gett er or setter then it is left to the developer to take care 4. For a POJO class containing setters and getters with equals and hashcode method,CARE UT plugin is capable of generating test cases with test data which can give upto maximum code coverage 5. One can also refer to workspace log in eclipse to check loggers 9.6 Service test plugin Refer to the ServiceTest_Installation Guide for detailed implementation 9.7 JPA plugin Pre-Requisite For installing CARE JPA Plugin, make sure that following requisites.  An insta lled 1.5 JRE or higher  Any Eclipse it should support JPA project . Preparing for the Installation: The steps will guide us to the installation of CARE JPA plugin. The following assumption has been made for the installation process.  All Pre -Requisite confi gured in the Eclipse IDE.  The installation is executed by an administrator with the following skillset o Knowledge of Java and Eclipse IDE. o Knowledge of installing plugin sites in Eclipse IDE. Choose JPA Plugin site from CARE plugin Installer. Generating e ntities/bean from tables : Use this procedure to generate Java persistent entities and bean from database tables. You must create a JPA project and establish a database connection before generating persistent entities. 1. Right -click the JPA project in the Project Explorer and select JPA Tools > Generate Entities/bean from Tables .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 113 of 133 DB Connection:  Select your database connection and schema.  To create a new database connection, click Add connection .  If you are not currently connected to the database, the D atabase Connection page appears. Select your database connection and schema. Specify whether or not JDBC driver JARs should be added to the project class path",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 114 of 133 Tables list : 1. This will populate the Tables list 2. From the Tables list, select dat abase tables for which you want to generate entities and beans.  On the Table Associations page, select the associations to generate. You can specify to generate specific references for each association.  To create a new association, click Add Association . Use the Create New Association wizard to define the association.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 115 of 133 Table Associations :",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 116 of 133 Customize Defaults : Property Description Default Source Folder The location of the JPA project's src folder. src Package Unselect The U se Default option and click Browse to select a new package location. Entity location Bean Package Unselect The Use Default option and click Browse to select a new package location. Entity Bean and Entity_Bean classes location. Superclass Select the sup erclass. Customize Individual Entities: Use this page to customize each generated entity. Select an item in the Table and columns area, then complete the following fields for each item. Property Description Mapping defaults Use these options to defi ne the table mapping information for the entity. Class name Name of the entity class Key generator Select the generator used for this mapping. Sequence name Enter a name for the sequence. You can use $table and $pk as variables in the name. These will b e replaced by the table name and primary key column name (respectively) when Dali generates a table mapping. Entity access Specify the default entity access method: Field (default) or Property .",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 117 of 133 Property Description Domain Java Class Use these options to define the class info rmation (Superclass and Interfaces ) for the entity. Generate this property Enable this option to generate the following properties for the selected column. Column mapping Property name The name of the property derived from the column Mapping type The attribute type Mapping kind The type of mapping for the attribute Column is updatable Specify if the column is included in SQL UPDATE statements. Column is insertable Specify if the column is included in SQL INSERT statements. ValidationXml folder Unse lect The Use Default option and click Browse to select a new folder location. For validation.xml location. Domain Java Class Use these options to define the getter and setter scope for the entity.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 118 of 133 10 Secured Gateway using Ngnix Secure -gateway is a ngi nx module (developed in java), running with the nginx to provide the support for gateway validation in PAS. This module act as a gateway for the CARE application to validate the user requests before reaching into the specific service and nginx will provide other features like load balancing and reverse -proxy to get the better performance in PAS. 10.1 Requirements 10.1.1 Primary R equirements  Requests should be validated before sending to the specific micro - service.  Request should have valid JWT token to call the specifi c micro - service, which is not expired neither blocklisted. 10.1.2 Setup requirements 1. To run CAREv4.7 we need to install Windows and Linux OS 2. To verirfy the micro service Secured Gateway the following services should be up and running. a) Security b) Metadata c) Admin -api d) Angular -ui e) Java 1.8 f) Nginx -clojure module g) Secure -gateway jar h) Dependent jars of the secure -gateway jar i) RabbitMq/ActiveMq 3. Database name with pas -security, pas -metadata, pas -admin should be created. 4. Set up the maven cofigurations. 10.1.3 Setup 10.1.4 Nginx -Clojure with Gateway module setup a. Please download the module from below location and extract it into your system. http://10.98.11.13/device/nginx -clojure -0.4.5.tar.gz b. After extracting the module nav igate to the conf folder inside the module and replace the below file with existing nginx.conf file. Configuration_file c. After that, download the following dependencies folder and paste it inside the jars folder of nginx module. Dependent -jars",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 119 of 133 d. Now, take the se cure-gateway code from following location: https://svnedge - 7.hcl.com/svn/PBASolutions/brownstone/utility/trunk/secure - gateway/source build the source code and take the jar and place it inside the jars folder of nginx module. 10.1.5 RabbitMq Configuration a. Please follow the below attached document to setup the RabbitMq. O120003_USER_GUI DE_RabbitMQ_CAREv4.7.doc b. Navigate to RabbitMq management url: http://localhost:15672/ - > Click on Exchanges c. Create the exchange in RabbitMq by below: Type: topic Durability: Durable. d. Create the queue in RabbitMq by below:",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 120 of 133 JWTBlocklist: Table name, in security DB e. Bind the queue with excha nge like below: Exchanges -> Secure -gateway -> Bindings -> JwtBlockList: The Queue created (Table name) Routing key: routing_key_prefix.QueueName (Pas.X800.DM.Audit.usBlockList) routing_key_prefix will be defined in the YAML.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 121 of 133 10.1.6 CARE configurati on a. Add below properties in application. yaml file of security -boot service: pas: audittrail: true routing_header_name: rabbitmq.ROUTING_KEY routing_key_prefix: Pas.X800.DM.Audit jwt_blocklist_cleaner: true jwt_blocklist_cleane r_job_cron: 0/20 * * * * ? b. Add the below to uri into CamelRoute.xml of security -boot service: 10.1.7 Nginx-Clojure with Gateway module startup a. In UI jar config.json file, change all the service port number into nginx port number which configured in nginx.conf file. b. Start all the required CARE jars and start nginx server by below steps: Navigate to nginx pa th -> cmd -> nginx -win64.exe c. Now access the CARE ui through nginx. Ex: http://localhost:69/care - where 69 is nginx port.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 122 of 133 11 Two way SSL This is a reference to deploy PAS/CARE jars enabling two -way SSL. This set up makes sure that all the communication between microservices and from external systems are protected via X509 based authorization. Only authorized trusted parties including gateway can communicate. This also ensures all traffic is done over private/encry pted channel. 11.1 Setup Use the following document for reference : O120003_USER_GUI DE_2WAY_SSL_CAREv4.7.doc",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 123 of 133 12 HTTPS Deployment This is a reference to deploy PAS/CARE jars enabling HTTPS. This set up makes sure that all the communication will be HTTPS based. Only a uthorized trusted parties including gateway can communicate. This also ensures all traffic is done over private/encrypted channel. 12.1 Setup Use the following document for reference : “O120003_devguide_HTTPS ” document is the developer guide that provides th e complete configuration information. O120003_DEVGUIDE _HTTPS.doc",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 124 of 133 13 Audittrail Audit trail module is responsible for storing and querying the data of the following events: a) Entity audit information a. Entity creation b. Entity Updation c. Entity deletion b) Login events a. Login b. Logout c. Login Failed c) Log events a. Access Logs b. Logs The “ O12003_Devguide_AuditTrail” document is the developer guide that provides the complete configuration information. O120003_DEVGUIDE _AUDITTRAIL.docx",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 125 of 133 14 Keyvault Keyvault module is responsible for generating a secret key by contacting a plugin which in turn could connect to cloud systems like AWS and AZURE. The keyvault module also has the capability to encrypt or decrypt the given value using the secret key. Please refer “ O120003_ DEVGUIDE_KEYVAULT_DBENCRYPTION” is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 126 of 133 15 Kubernetes Kubernetes module is responsible for easy deployment and aut o-scaling of CARE Microservices as Docker Containers. Please refer the “ O120003_devguide_kubernetes” which is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 127 of 133 16 Device Management This section mainly focuses on providing the documentation support for the Device Management Modules available in the CARE Framework. Please refer the document “ O120003_DEVGUIDE_DEVICE_MANAGEMENT_3.0” which is the developer guide that provides the complete configurat ion information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 128 of 133 17 Archetype The purpose of this section is to provide the details of the Archetype, its types, its creation and deployment, which provides support for managing the it. Please refer “ O120003_DEVGUIDE_ARCHETYPE” which is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 129 of 133 18 OPEN -ID CONNECT The purpose of this section is to provide the details of the OPEN -ID Connect where in the details of execution and usage f or managing it. Please refer “ O120003_DEVGUIDE_OPENIDCONNECT” which is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 130 of 133 19 PASSWORD ENCRYPTION The purpose of the this section is to provide the d etails of the password encryption where in the details of execution and usage for managing it. Please refer “ O120003_DEVGUIDE_PASSWORD ENCRYPTION” which is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 131 of 133 20 OPEN ID CLIENT accessing thru the platform The purpose of this section is to provide the details of the OPEN ID CLIENT accessing thru the platform where in the details of execution and usage for managing it. Please refer “ O120003_D EVGUIDE_OpenID_for_Platform” which is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 132 of 133 21 Docker Support The purpose of this section is to provide the details of the Docker support accessing thru the platfo rm where in the details of execution and usage for managing it. Please refer “ O120003_DEVGUIDE_DOCKER ” which is the developer guide that provides the complete configuration information.",, "Guidel ine ID: O120003 Revision: 2.7 Developer guide for CARE Effective Date: 20-Oct-2021 HCLT Confidential Page 133 of 133 22 Swagger Enable/Disable This featu re allows user to disable the swagger documentation for a particular microservice they can make use of the below mentioned property by setting it to false. pas.api_documentation: false The below feature allows the user to enable/disable particular servic e from swagger if set to false. Yaml Property to be added in each microservice: ##Properties to make unwanted CARE [REST] services Optional. ##If set false, will remove associated service from swagger. ##pas.EntityService.rest.service.value: true pas.Dat aList.rest.service.value: true pas.AuditHistory.rest.service.value: true pas.DataEncryption.rest.service.value: true pas.Loggerservice.rest.service.value: true pas.MenuService.rest.service.value: true pas.user.rest.service.value: true pas.SyncData.rest.ser vice.value: true pas.TenantUnawareUnified.rest.service.value: true pas.company.rest.service.value: true This feature has been added into CAREV5.2.",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT Datasheet",, "CARETM Connected Assets in Regulated Environment ™ DATASHEET",, "TECHNICAL REQUIREMENTS CARE CARE TM – DATA SHEET COMPONENT REQUIREMENT Processor 64-bit processor: Intel Core i3 or equivalent RAM 8 GB RAM (preferred 16GB) Operating System Any 64 -bit Windows/Linux/Ubuntu HDD Free Space 100 GB min (preferred 500GB) Java Minimum JDK 8, recommended JDK 17 for latest CARE version Other software Pre -requisites PostgreSQL/MSSQL ActiveMQ/RabbitMQ Native MQTT/Azure IoT Hub, AWS IoT Optional -Docker, Kubernetes Access requirements System should be accessible to all resources expected to use CARE application",, "CARE TM – DATA SHEET PRODUCT OVERVIEW: CARE is a powerful software framework that has the necessary building blocks for building next generation medical multitenant software / services faster. CARE brings together business application building frameworks, device connectivity, re -usable software components and best practice templates to provide acceleration to the development of software / platforms. It can be used to build both edge/gateway applications as well as scalable cloud application HIGHLIGHTS: •Standardized and Integrated Best of breed technology stack. •Multiple Architecture support •Docker integration and packaging support for different deployment models. •A set of automation tools for developers to bootstrap, develop, test and deploy software and applications. •Complete Device Management services for your device connectivity needs, device remote diagnosis and management. •Audit Trail and Smart Remote Assist. •CARE’s AppBuilder Gen -AI feature is built on top of latest LLM (Large Language Models) models, to aid development of backend microservices as well as frontend. PRODUCT SALIENT FEATURES: Multi Tenant and Sensitive Data Handling • Helps in multi tenant & multi geo deployment • Hierarchical Multi Tenancy • Geo Data Fencing • Data Masking/Tokenization @ cloud • Data Tokenization/masking @ device gateway Remote Access • Access devices (RDP/VNC/SSH) from browser via cloud with session recording • Remote file browsing • Remote commands • Access Device gateway UI from cloud • Access Integrator UI from cloud for troubleshooting • Remote camera view (mobile based) for field support Device Gateway • Key for medical devices deployment environment to avoid direct internet connectivity • Handle offline status gracefully • Store -n-forward • Patch File download • Ready to use module for Windows IoT and Linux Device Agent • Optional -works with device gateway • Agent for remote access and patch handling • Azure Power BI • Azure Data Explorer • Agent based on C#, CAppBuilder -GenAI",, "• Agent based on C#, CAppBuilder -GenAI •Support development of backend and frontend •Ensure basic needs such as paginated display, document generation etc .. by default •It can generate CARE compatible / standard microservices •It can be used as local IDE as well as cloud based shared IDE •It can be used to build Smart Medical Services faster CARE Integrator • Support all standard and medical protocols • Configured to interact with existing devices • Definitions at device type and gateway level • Cloud managed. • Changes can be pushed to gateway anytime. HCL Services • Offers customization and integration services. • Building custom services for customer. • Years of experience with different classes of devices. Reusable Components • Authentication and Authorization of Security • Roles/Permission Management of Security • Audit Trail, Restore, Patch Management Key Integration • OpenID, LDAP, EventHub, Azure Active Directory Supported Platforms • PostgreSQL, MSSQL • RabbitMQ/ActiveMQ • Native MQTT/Azure IoT Hub/AWS IoT",, "CARE : High -Level Architecture Device CARE Gateway [Linux/Windows/Appliance]IoT Hub SDKMQTT Or MQTT over Websocket (Push messages to Device) CARE ServicesCARE gateway base modulesWeb socket Support EngineerHTTPS / HTML5TLS1.2+ with X 509 Cert Authentication TLS 1.2+ Enterprise/Private network (Firewalled)CARE Device Agent •Remote file browsing and upload via browser •RDP/VNC/SSH access via browser •Automated Session Recording •Remote command execution •Logs/telemetry data collection •Remote Patch update •Store -n-forward •Device/EMR integration framework •IOT Defender Optional Business user HCP PatientCARE Remote diagnosticsCARE : High -level architecture CARE Device integrator / Anonymization / Tokenization IoT defender AgentRESTIoT Hub Event HubStream AnalyticsData Lake SynapseAKSSQLPower BI Gateway/ WAF Gateway/ WAF AD Signal R Azure Services CARE ServicesKey VaultApplication InsightTime series IoT defender AgentBlob StoreIoT Defender Healthcare API PII dataCARE TM – DATA SHEET",, "CARE Connected Assets in Regulated Environment ™ BROCHURE",, "CARE TM HCL’s CARE (Connected Assets in Regulated Environment) is a Micro -services architecture featured multi -tenant platform that helps in building a regulated medical class software within a significant reduced time. CARE platform that provides necessary building blocks for developing next generation software / services faster. CARE brings together packaged application frameworks, re -usable software components, automation tools for developers & testers, support for best of breed architectural patterns and best practice templates to provide acceleration to the development of software / platforms. Key Features •Standardized and Integrated Best of breed technology •Data Management to store, retrieve, encrypt, import, and export data •State of the art in -built security for preventing attacks and ensuring compliance •Packaging and containerization support for cross platform deployment of micro services with back -up/ restore features for business continuity •Integrated drag and drop builders for code generation, Entities, REST APIs, UI, Unit Tests and Automation Scripts, Service Integration •Support for multiple architectural patterns, including Event Driven, N-Tier, and Microservices •Integrated log management for centralized logging, notification and custom dashboard etc.Business Challenges Addressed •Without a “reuse/foundation” approach to software, organizations end up having significant redundancies in infrastructure, licenses, people, and processes, thus leading to an inefficient delivery of services •Creating a Platform that can act as a foundation to launch business services requires significant investments in terms of cost, skill and time •A global service creates different code base of comparable functionalities, thus leading to increased cost of maintenance of these applications •With high pressure on cost and time to market, it is difficult to approach software as a “holistic” solutionWhy CARETM? •In-built tools, workflows, rule",, "CARETM? •In-built tools, workflows, rule engines, libraries, etc. enable rapid creation of multi -tenant apps and the conversion of single tenant apps to multi - tenant apps •Easy on -boarding of new countries/entities with easy -to- use configuration sans any additional development effort •Execute complex test scenarios involving two or more development platforms working in tandem •Extensibility to address data model extensions specific to country/brand/branch •Support for single instance and distributed deployment models",, CARETM: High -Level Architecture -Azure,, CARETM: High -Level Architecture -AWS,, "How CARE TMHelps CARE comes with a standardized application architecture stack that can be shared across applications. CARE provides the ability to handle different tenant specific configurations of UI, the systems functional/non - functional behavior and the services. CARE framework comes with reusable components & device connectivity and automation tools for faster & easier development. CARE comes with pre -integrated security functionality to secure the application built on top of the CARE platform. CARE provides you a foundation with hierarchical multitenancy support across new distribution channels, or with new partners. CARE comes with support for code generation, automated build and development thus reducing the cycle time. Architecture & Design •Well defined Micro - services Architecture. •Different archetypes for different needs. •Takes care of all non - functional requirements. •Well defined and up to date technology stack.Development •Pre-Integrated technology stack for day zero development. •Code generation within IDE for data models, validations and UI. •Automatic Unit Test Case Generation. •Runtime features allow rapid development. •Integrate with different system with ease.Testing •Pre-Tested Components for reduced testing effort. •Pre-Tested Security for all core components leading to near zero security testing effort. •Pre-Tested Performance and Scalable Components for reduced performance testing cycles. Deployment •Cloud Tested Deployments. •Compatible to be deployed in Data Centers as well as in any public cloud. •Integrates well with any monitoring infrastructure including public cloud (like cloud watch). •Administration Console to administer the application. •Centralized Logging. •One Touch Deployment with container support.CARE TMAcceleration Through Software Development",, "CARE TMProof Points Low Risk/ Higher Rate of Success •Abstraction of technology complexity, focus on business requirement. •Get it right first time. •Low Risk technology approach acts as a bridge between Build Vs Buy. Follows standard technology patterns allowing standard skills to be leveraged.Acceleration •Reusable components accelerate software development by at least 31%. •Automation to ease code development. •Pre- Conceptualised approach to a global platform saves time in all phased of SDLC (requirement, architecture, design, implementation and deployment).Quality •Pre-built components driving ""Get it right first time"" benefits. •Best practices enforcement through enforced architecture/design. •Pre-tested components reduces time for functional, non - functional, security and deployment testing.TCO •A platform -based approach reduces the cost of building new services by upto 52%. •Open -Source Components allows the overall cost of ownership to be low. •An ""administration first"" driven approach allows better management and delivery of services across the globe.CARE TMBenefitsFor a Fortune 500 American MCN involved in manufacturing of medical devices, CARE helped reduce TTM by 52%, development time by 26%, testing time by 18% and deployment time by 10%.For an American MCN involved in supply of ophthalmic surgical products, CARE platform helped transform a disjoint manual process into a connected device environment with centralized database. This is expected to impact business growth by up to 45%.For a Fortune 500 American MNC involved in selling of business services and document technology products, CARE platform achieved an overall 43% reduction in time to market of the new solution.",, "Copyright © 2022 HCL Technologies | ConfidentialCARE CONNECTED ASSETS IN REGULATED ENVIRONMENT ™",, "Elevator Pitch CARETM provides customers with a micro services - based software platform for launching global business services with 50% cost reduction and 30% accelerated software development. Audience Horizontal Proposition, applicable to All ERS Specific Verticals that need launching global business services through a scalable cloud platform. This could be a fresh product development or migration of existing monolithic applications that are not cloud ready. PRODUCT POSITIONING When to Engage •Fresh product development or existing product migration/re -engineering to cloud based application. •Dual deployment approaches –Build once, run on premise and on the cloud. When not to Engage •Maintenance (ADM/PDM) projectsBusiness Challenges •Traditional companies (that are not yet fully digital) are being pushed to create core software services. These companies are risk averse for a big bang approach and look at incremental innovation •With high pressure on cost and time to market, it is difficult to approach software as a “wholistic” solution. Tactical decisions always take priority over strategic ones in most cases •Without a “reuse/foundation” approach to software, organizations end up having significant redundancies in infrastructure, licenses, people, and processes, thus leading to inefficient delivery of services •Creating a platform that can act as a foundation to launch business services requires significant investments in terms of cost, skill and time •A global service creates different code base of comparable functionalities, thus leading to increased cost of maintenance of these applications Business Benefits Industrialization : ✓Promotes the use of commoditized skills to perform complex jobs ✓Standardization across Technology and Engineering process Acceleration: ✓Automation to ease code development ✓Reusable components accelerate software development by at least 30 % Quality Enforcement ✓Pre-built components driving “Get it right first time” benefits",, "✓Best practices enforcement through design itself Total Cost of Ownership ✓Platform based approach reduces the cost of building new services by up to 50%•Device Connectivity : CARETMcomes with reusable modules that are cloud -provider agnostic, to build on premise smart gateways and cloud servers. Customizable remote diagnostics, patch rollout capabilities are in - built. •Data Management : Data retrieval and encryption are important to ensure efficiency of your operations. CARETMcomes with robust Data management to store, retrieve, encrypt, import, and export data, thereby directly enhancing operational efficiency. •Standardized Architecture: Rather than have you design and experiment with new architectures, HCL offers you a proven and time -tested architecture. •Automated code generation for domain models, workflows, UI, service etc., which reduces overall efforts and coding errors •In-built Multitenancy capability with data access policies that enable you to build SaaS and multi -geo applications quicklyBATTLECARDCARETM Key Features",, "Differentiator •In-built tools, workflows, rule engines, libraries, etc. enable rapid creation of multi -tenant apps and the conversion of single tenant apps to multi -tenant apps •Easy on -boarding of new countries/entities with easy -to-use configuration sans any additional development effort •Uniform platform to support different stakeholders •Extensibility to address data model extensions specific to country/brand/branch •Configurability to alter workflows, business rules, validations specific to country/brand/branch Access control to enable fine grained control to different functions of the application •Support for single instance and distributed deployment models •Drag and drop application development and in -built packaging and containerization support for rapid application development and deploymentSOLUTION HCL DIFFERENTIATOR COMPETITOR WEAKNESS CARETMProvides a single platform for both on premise and cloud hosted solutionsCost of development is higher due to licensing cost of commercial automation tools CARETMMicroservices architecture support providing higher scalability/flexibilityDeployments are generally tightly coupled with specific cloud/virtualization environments Common Objections and Responses OBJECTION RESPONSE No such immediate requirement (Scaling required in future based on business growth)• Start small and grow as your business grows. Using CARETM, you build once and run on premise and/or on the cloud. • Customer can start as a small on -premise application and move to cloud (adding newer services while catering to multiple customers /geographies) as the business grows. • Existing monolithic applications hosted as independent/discrete services can be clubbed and launched as a single solution thus greatly reducing the maintenance & operational costs . Customer is against using Open Source• CARETMis built using technologies, where the commercial support can be bought when required.",, "required. • Open Source technologies help in reducing the overall all development and operational cost.BATTLECARDCARETM",, "FAQs What is the technology/language used? A: The platform is based on Java/J2EE, existing application written in other languages can be integrated with platform using restful APIs. Q: What kind of services can be built using CARE? A: CARE is a horizontal platform accelerator. It can be leveraged to build anything from device -based cloud services to disease management healthcare platforms, to insurance platforms. Q: I have an existing product. How can I use CARE? A: CARE can be used to re -engineer legacy products. However, CARE cannot be leveraged for maintaining an existing product. Q: Is CARE Free? A: CARE is not free. It has a license cost involved and requires the customer to sign an agreement for the T&C of CARE (allowing HCL to sell CARE to other customers). Q: My customer does not want Open Source; can I still position CARE? A: “Open Source” is used in a variety of ways. CARE is built using technologies, where the commercial support can be bought when required. Therefore, it is as good as commercial software where required. Q: Is CARE a product? A: CARE is not a product. It is a solution accelerator that we use to deliver complex projects in a consistent and shorter timeframe.Q: What is the support model for CARE? A: Typically, support model is included as part of the project support (of the customer project we develop on top of CARE) while we sign up with the customer. However, there are models, where separate dedicated support can be planned for. Q: Would my customer receive updates to CARE as new releases are made? A: New releases can be leveraged by existing CARE Customers. Q: My customer wants access to source code. Should I still go ahead and position CARE? A: Access to source code can be provided on an exception basis for additional cost. However, any change to the base source code will void the customer from getting further access to new releases as it would not be possible to track the changes and support that code too.",, "code too. Q: My customer wants more features than what is available in CARE. What should I do? A: Typically, custom features can be built as part of the implementation by delivery teams. However, in cases where features add true value to the platform and can be leveraged across customers, the CARE platform team will implement the feature. Q: My customer wants to do a 100K project. Can I leverage CARE? What will the license component be? A: Unless there is a long -term vision for the customer and there is a customer promise of long -term work, CARE cannot be positioned for very small projects as the platform team cannot manage the overheads of supporting multiple small projects. In specific cases, where there is a long -term commitment, an appropriate payment schedule can be arrived at, that will fit within the budget at the same time provide for the licensing of CARE.BATTLECARDCARETM",, "Case study • For a Fortune 500 American MNC involved in manufacturing of medical devices CARE helped reduce time to market by 52%, development time by 26%, testing time by 18% & deployment time by 10% • For a Fortune 500 American MNC involved in selling of business services and document technology products, use of CARE helped revive business by enhancing customer satisfaction that lead to increased revenues for the client, its Distributors, and resellers • For an American MNC involved in supply of ophthalmic surgical products, CARE platform helped transform a disjoint manual process into a connected device environment with centralized database. This is expected to impact business growth by up to 45%.CONTACT US @ ersslus@hcl.comENGAGE CARETMsupports multiple pricing models. A standard CARE platform starts with a base price of 200k. Pricing may vary based on the actual scope of development.BATTLECARDCARETM",,