Enablement of data flow from Inventory Service to ECM

ecm business requirement for “qualify data flow into ecm” new devices or existing devices are required to meet certain ecm business conditions to make them eligible to flow to the ecm system when a new device is added though the ansible scanners or best practice scans, the device will be added with lifecycle state as “discovered” by default the new device data from inventory service will not flow to ecm until the ecm business conditions are met similarly, for the existing devices, the ecm business conditions should be met for the data to flow to ecm following are the ecm requirements & mandatory business rules to qualify inventory service records to flow to the ecm system ensure the ou is active and enabled in aiops primary checks is to validate basic customer details are reflected correctly \ serial number \ \ customer details \ \ notes \ 1 bac id 2 bam id 3 contract name 4 customer name 5 opaque id 6 country name 7 customer sector (valid sector) 8 security managed by verify in blue id tool https //blueidp1 zkpw3uspriv app kyndryl net 8443/blueid/staticpage html?page=searchclients html removed from mandatory list as per ecm team's request 9 is designated for compliance reporting must be y verify contract ids bac/bam exist compliance flags are set as = y all the mandatory fields are present in os and subsystems – validate the inventory data in the tool refer next slides for important data fields which are required for the ecm team to build correct account details os fields in inventory service to qualify data into ecm following pre checks are required to qualify records to flow to ecm \ s no \ \ field name \ \ expected input \ 1 is designated for compliance reporting y 2 customer sector valid sector in blue id tool 3 security managed by (removed from mandatory) 2 digit country code (fr, jp, in, gb, etc ) 4 lifecycle status (include idle status as well) active + idle 5 operating system name valid value 6 operating system version valid value 7 operating system release (removed from mandatory) valid value 8 is continued business need required y/n 9 is dormant user id process required y/n 10 is employment verification required y/n 11 is health check required y/n 12 is manual health check required y/n 13 is privileged id revalidation required y/n 14 is vulnerability scan required y/n 15 ip address (removed from mandatory) valid ip address (refer slide 6) 16 is primary ip address (removed from mandatory) y/n 17 image purpose provide valid value examples server, network, storage, accessory 18 parent system type examples server, network, storage, accessory, security, etc all security and compliance flags with "y" must have intervals and units set for more details, refer to the next 5 charts mandatory subsystem fields in inventory service to qualify data into ecm following pre checks are added for subsystem to qualify valid records to flow to ecm \ s no \ \ field name \ \ expected input \ 1 subsystem name valid subsystem name, no blank 2 product name valid product name, no blank 3 product generic type must contain valid product generic type published in ecm link 4 subsystem lifecycle status active or idle 5 subsystem last changed date valid date, no blank 6 security health check match type must contain "application" or "instance" values 7 security id check match type must contain "application" or "instance" values 8 subsystem opaque id valid id, no blank 9 subsystem security managed by 2 digit country code (fr, jp, in, ) not mandatory currently as per ecm 10 subsystem parent opaque id valid parent opaque id available in os 11 product release (removed from mandatory) valid product release, no blank 12 product provider valid provider, no blank 13 product version valid product version, no blank 14 product type must contain valid product generic type published in ecm link 15 subsystem is designated for compliance reporting must be "y"