This KB article describes the steps on how to raise requests for Content Services.  Requests for data and content maintenance on the data Libraries are handled by the Content Support & Operations teams and involves (but is not limited to) the following activities: Requests for the addition of new Vendors, Products and Versions not currently in the catalogue Requests for maintenance of existing content following Vendor announcement of product changes, including divesture, merger or retirement Requests for SKU/PURL maintenance including linking to Products in the catalogue Maintenance of discovered application evidence and mapping to Product and Versions Maintenance of market enriched data such as Lifecycle dates, Open-Source attributes, and Vulnerabilities, etc.   Requests for Content Services are made as follows: Navigate to the Support Portal on the Community here Select ‘Flexera Community’ if not already selected in the ‘Community’ picklist   Select ‘Content Requests’ from the ‘Product’ Picklist.  This applies to all customers irrespective if you are a FlexNet Manager, Technopedia, or IT Visibility customer     Select ‘Library’ from the ‘Version’ Picklist for which maintenance is required.  For example, Technopedia customers requiring Content Services for Product, Version and/or Evidence mapping would pick Technopedia.  FlexNet customers requiring similar would select ARL     Enter the requirements for Library maintenance in the ‘Description’ field   Severity will default to ‘Low’.  Increase the Severity as per the urgency of your request.  This will ensure that your requests will be addressed in the correct order compared to other requests for Content Services that you may have open   Note that for ‘Critical’ and ‘High’ severity requests we would like to understand more about the impact to your organization so that we can respond accordingly    If required, you may add up to 10 attachments into the ‘Drag and drop’ area.  We encourage customers to aggregate similar requests into one ask so as to reduce the administration overhead to tracking requests to closure     ... View more

This KB article describes the steps on how to raise requests for Content Services.  Requests for data and content maintenance on the data Libraries are handled by the Content Support & Operations teams and involves (but is not limited to) the following activities: Requests for the addition of new Vendors, Products and Versions not currently in the catalogue Requests for maintenance of existing content following Vendor announcement of product changes, including divesture, merger or retirement Requests for SKU/PURL maintenance including linking to Products in the catalogue Maintenance of discovered application evidence and mapping to Product and Versions Maintenance of market enriched data such as Lifecycle dates, Open-Source attributes, and Vulnerabilities, etc.   Requests for Content Services are made as follows: Navigate to the Support Portal on the Community here Select ‘Flexera Community’ if not already selected in the ‘Community’ picklist   Select ‘Content Requests’ from the ‘Product’ Picklist.  This applies to all customers irrespective if you are a FlexNet Manager, Technopedia, or IT Visibility customer     Select ‘Library’ from the ‘Version’ Picklist for which maintenance is required.  For example, Technopedia customers requiring Content Services for Product, Version and/or Evidence mapping would pick Technopedia.  FlexNet customers requiring similar would select ARL     Enter the requirements for Library maintenance in the ‘Description’ field      Severity will default to ‘Low’.  Increase the Severity as per the urgency of your request.  This will ensure that your requests will be addressed in the correct order compared to other requests for Content Services that you may have open   Note that for ‘Critical’ and ‘High’ severity requests we would like to understand more about the impact to your organization so that we can respond accordingly    If required, you may add up to 10 attachments into the ‘Drag and drop’ area.  We encourage customers to aggregate similar requests into one ask so as to reduce the administration overhead to tracking requests to closure     ... View more

Content releases bring new updates to Flexera applications which allow customers to maintain or expand their ability to manage changes in their inventory and asset data. Clarity on what the updates contain, what improvements or enhancements they bring–along with the knowledge of the size or volume–allow customers to understand and explain changes that they will see in their inventory and asset data. When these changes happen, they may or may not bring adverse impact to Flexera customers. When they do, it is critical for the customers to know in advance what changes are coming, and what kind of precaution or preparation they need to take to absorb them. Content Release Checklist proposes a mechanism to provide these advance notifications so that the customers are equipped with all information that they need to eliminate or minimize any potential impact. Furthermore, early communication of upcoming changes with customers encourage participation in terms of feedback, concerns or reservations, which improve the ability to ensure better outcome and prevent any unintended consequences.  Well documented and communicated changes will serve as references to answer any future questions around accountability and transparency, especially when dealing with any unforeseen impact. The ability to trace past changes will also produce reliable data-points for any future improvement which may have dependencies on them. Finally, content releases bring forth the result of all the hard work by the content team. They provide tremendous values and offer critical differentiators which the customers, the market, and the industry highly appreciate. Capturing all the goodies and communicating them regularly will enforce the message and strengthen Flexera's position as the de-facto standards of everything content. With this new Content Release Checklist process, Flexera will complete a checklist in advance for all content library releases. The more potential for risk that a given content library update may have, the higher the class of update before publication will be assigned, necessitating additional checks, customer notifications and management approvals.  Class 1   -  Major updates which introduce new content to support new product features/capabilities, modify existing content to change the behavior of existing product features/capabilities or deprecation of any existing content (along with the associated product features/capabilities) which require all customers to make necessary adjustments beforehand Class 2   - Moderate updates which bring significant changes in customers environment and potentially adverse impact in some customers environment had they not anticipated and made necessary adjustments beforehand Class 3   - Minor updates as a result of "Business-As-Usual (BAU)" activities which, historically, cause no adverse impact in customers' environment except for coverage increase   Class 1 Content Release Definition Major updates which introduce new content types to support new product features/capabilities, modify existing content types to change the behavior of existing product features/capabilities or deprecation of any existing content types (along with the associated product features/capabilities) which require all customers to make necessary adjustments beforehand Examples Technopedia (including Data Platform, IT Visibility): introduction of new content types  introduction of new content relationships deprecation or changes to existing content types deprecation or changes to existing content relationships ARL (ITAM, FNMS): significant changes which will impact a majority of customers, such as changes in products from publishers which are common across most customers, including all Tier 1 publishers significant changes with license impact on a high number of applications significant updates to PVU points significant updates to Oracle LMS scripts or Oracle option behavior significant product version or edition hierarchy changes with license impact for Tier 1 publishers significant application recognition changes linked to data center entries in the PURLs SKU/PURL/Bundle (ITAM, FNMS): significant redefinitions of SKU, PURL, or bundles, especially those linked to data center PURL entries any changes in PURL definitions Checklist All items in the Class 2 and 3 checklists, plus additional checklist items below Task Timeline Data Platform and/or Technopedia Specific Updates on product documentations On release date or earlier Release Notes (tied to Data Platform Release Notes) On release date or earlier Early engagement with select major customers 1 month or earlier FNMS and/or ARL Specific A blog entry in Community Portal (FlexNet Manager Content Blog) to capture summary of the changes, with links to necessary detailed KB Articles which customers can subscribe and get a notification every time new updates/changes are captured. The blog entry will capture the dates: the changes are (were) announced, the changes were (will be) deployed, with newest changes at the top of the post. 1 month or earlier   Class 2 Content Release Definition Moderate updates which bring significant coverage changes in customer environments and potentially adverse impact in some customer environments without prior notification allowing them to anticipate and make necessary adjustments beforehand Examples Technopedia (including Data Platform, IT Visibility): changes in content behavior (e.g. naming convention, mapping rules) moving evidence from one release to another lineage changes involving Tier 1/2 publishers and/or significant number of lineage changes (both software and hardware) tier changes which affect Tier 1/2 manufacturers  changes in Taxonomy (new categories introduced, existing categories modified/removed) any content bug fixes tied to multiple customers ARL (ITAM, FNMS): significant number of new file evidence recognition any updates to PVU points any updates to Oracle LMS scripts or Oracle option behavior any product version or edition hierarchy changes with license impact for Tier 1 publishers any application recognition changes linked to data center entries in the PURLs (not net new applications which are BAU - only changes) any bug fixes tied to multiple customers SKU/PURL/Bundle (ITAM, FNMS): any removal of an application from a bundle any net new PURL definition any bug fixes tied to multiple customers Checklist All items in Class 3 checklist, plus additional checklist items below. Tasks Timeline A blog entry in Community Portal (Technopedia Blog and/or FlexNet Manager Content Blog)  to capture summary of the changes, with links to necessary detailed KB Articles which customers can subscribe and get a notification every time new updates/changes are captured. The blog entry will capture the dates: the changes are (were) announced, the changes were (will be) deployed, with newest changes at the top of the post. 2 weeks or earlier Email notification to select major customers 2 weeks or earlier Targeted communication to CSM via Hey CSM! Teams channel 2 weeks or earlier   Class 3 Content Release Definition Minor updates as a result of "Business-As-Usual (BAU) activities which, historically, cause no adverse impact in customers' environment except for coverage increase Every content library release will be at least a Class 3 Examples Technopedia (including Data Platform, IT Visibility): new products/releases new mappings ARL (ITAM, FNMS): new applications new evidence rules SKU/PURL/Bundle (ITAM, FNMS): new SKUs new links between SKUs and applications new bundles Checklist Tasks Timeline Functional test is passed (confirmation that the content package is loaded into test instance of the applications successfully) On release date or earlier Automated content integrity tests are passed On release date or earlier ITAM, FNMS, ARL, SKU, PURL, or Bundle Specific ARL, SKU, and PURL build on the FNMS Cloud instances (US/EU) is confirmed to match the ARL, SKU, and PURL build being released On release date or earlier Release Notes, posted as a blog entry in Community Portal (FlexNet Manager Content Blog) On release date or earlier   ARL (and SLDP)     SKU, PURL, Bundle   Technopedia Specific Content Replication's email notification is received On release date or earlier   Successful: (none)     Unsuccessful/late: (see below)   Catalog generation's email notification is received On release date or earlier   Successful: A blog entry in Community Portal (Technopedia Blog) to capture content statistics (Manufacturers, Software Releases, Hardware Models, Mapped Signatures, Ignored Signatures). The blog will be updated for every release with the latest update on top.     Unsuccessful/late: A blog entry in Community Portal (Technopedia Blog) to provide reasons for failure and ETA for the next successful catalog. The blog will be updated for every unsuccessful/late instance with the latest update on top.   API Tests' email notification is received On release date or earlier   Successful: (none)     Unsuccessful/late: A blog entry in Community Portal (Technopedia Blog) to provide reasons for failure and ETA for the next successful catalog. The blog will be updated for every unsuccessful/late instance with the latest update on top.     ... View more

Content releases bring new updates to Flexera applications which allow customers to maintain or expand their ability to manage changes in their inventory and asset data. Clarity on what the updates contain, what improvements or enhancements they bring–along with the knowledge of the size or volume–allow customers to understand and explain changes that they will see in their inventory and asset data. When these changes happen, they may or may not bring adverse impact to Flexera customers. When they do, it is critical for the customers to know in advance what changes are coming, and what kind of precaution or preparation they need to take to absorb them. Content Release Checklist proposes a mechanism to provide these advance notifications so that the customers are equipped with all information that they need to eliminate or minimize any potential impact. Furthermore, early communication of upcoming changes with customers encourage participation in terms of feedback, concerns or reservations, which improve the ability to ensure better outcome and prevent any unintended consequences.  Well documented and communicated changes will serve as references to answer any future questions around accountability and transparency, especially when dealing with any unforeseen impact. The ability to trace past changes will also produce reliable data-points for any future improvement which may have dependencies on them. Finally, content releases bring forth the result of all the hard work by the content team. They provide tremendous values and offer critical differentiators which the customers, the market, and the industry highly appreciate. Capturing all the goodies and communicating them regularly will enforce the message and strengthen Flexera's position as the de-facto standards of everything content. With this new Content Release Checklist process, Flexera will complete a checklist in advance for all content library releases. The more potential for risk that a given content library update may have, the higher the class of update before publication will be assigned, necessitating additional checks, customer notifications and management approvals.  Class 1 -  Major updates which introduce new content to support new product features/capabilities, modify existing content to change the behavior of existing product features/capabilities or deprecation of any existing content (along with the associated product features/capabilities) which require all customers to make necessary adjustments beforehand Class 2- Moderate updates which bring significant changes in customers environment and potentially adverse impact in some customers environment had they not anticipated and made necessary adjustments beforehand Class 3  - Minor updates as a result of "Business-As-Usual (BAU)" activities which, historically, cause no adverse impact in customers' environment except for coverage increase   Class 1 Content Release Definition Major updates which introduce new content types to support new product features/capabilities, modify existing content types to change the behavior of existing product features/capabilities or deprecation of any existing content types (along with the associated product features/capabilities) which require all customers to make necessary adjustments beforehand Examples Technopedia (including Data Platform, IT Visibility): introduction of new content types  introduction of new content relationships deprecation or changes to existing content types deprecation or changes to existing content relationships ARL (ITAM, FNMS): significant changes which will impact a majority of customers, such as changes in products from publishers which are common across most customers, including all Tier 1 publishers significant changes with license impact on a high number of applications significant updates to PVU points significant updates to Oracle LMS scripts or Oracle option behavior significant product version or edition hierarchy changes with license impact for Tier 1 publishers significant application recognition changes linked to data center entries in the PURLs SKU/PURL/Bundle (ITAM, FNMS): significant redefinitions of SKU, PURL, or bundles, especially those linked to data center PURL entries any changes in PURL definitions Checklist All items in the Class 2 and 3 checklists, plus additional checklist items below Task Timeline Data Platform and/or Technopedia Specific Updates on product documentations On release date or earlier Release Notes (tied to Data Platform Release Notes) On release date or earlier Early engagement with select major customers 1 month or earlier FNMS and/or ARL Specific A blog entry in Community Portal (FlexNet Manager Content Blog) to capture summary of the changes, with links to necessary detailed KB Articles which customers can subscribe and get a notification every time new updates/changes are captured. The blog entry will capture the dates: the changes are (were) announced, the changes were (will be) deployed, with newest changes at the top of the post. 1 month or earlier   Class 2 Content Release Definition Moderate updates which bring significant coverage changes in customer environments and potentially adverse impact in some customer environments without prior notification allowing them to anticipate and make necessary adjustments beforehand Examples Technopedia (including Data Platform, IT Visibility): changes in content behavior (e.g. naming convention, mapping rules) moving evidence from one release to another which impacts significant number of evidence or evidence mapping rules or highly visible products lineage changes involving Tier 1/2 publishers and/or significant number of lineage changes (both software and hardware) tier changes which affect Tier 1/2 manufacturers  changes in Taxonomy (new categories introduced, existing categories modified/removed) changes to operating systems which could easily have significant impact to customers any content bug fixes tied to multiple customers ARL (ITAM, FNMS): significant number of new file evidence recognition any updates to PVU points any updates to Oracle LMS scripts or Oracle option behavior any product version or edition hierarchy changes with license impact for Tier 1 publishers any application recognition changes linked to data center entries in the PURLs (not net new applications which are BAU - only changes) any bug fixes tied to multiple customers SKU/PURL/Bundle (ITAM, FNMS): any removal of an application from a bundle any net new PURL definition any bug fixes tied to multiple customers Checklist All items in Class 3 checklist, plus additional checklist items below. Tasks Timeline A blog entry in Community Portal (Technopedia Blog and/or FlexNet Manager Content Blog)  to capture summary of the changes, with links to necessary detailed KB Articles which customers can subscribe and get a notification every time new updates/changes are captured. The blog entry will capture the dates: the changes are (were) announced, the changes were (will be) deployed, with newest changes at the top of the post. 2 weeks or earlier Email notification to select major customers 2 weeks or earlier Targeted communication to CSM via Hey CSM! Teams channel 2 weeks or earlier   Class 3 Content Release Definition Minor updates as a result of "Business-As-Usual (BAU) activities which, historically, cause no adverse impact in customers' environment except for coverage increase Every content library release will be at least a Class 3 Examples Technopedia (including Data Platform, IT Visibility): new products/releases new mappings ARL (ITAM, FNMS): new applications new evidence rules SKU/PURL/Bundle (ITAM, FNMS): new SKUs new links between SKUs and applications new bundles Checklist Tasks Timeline Functional test is passed (confirmation that the content package is loaded into test instance of the applications successfully) On release date or earlier Automated content integrity tests are passed On release date or earlier ITAM, FNMS, ARL, SKU, PURL, or Bundle Specific ARL, SKU, and PURL build on the FNMS Cloud instances (US/EU) is confirmed to match the ARL, SKU, and PURL build being released On release date or earlier Release Notes, posted as a blog entry in Community Portal (FlexNet Manager Content Blog) On release date or earlier   ARL (and SLDP)     SKU, PURL, Bundle   Technopedia Specific Content Replication's email notification is received On release date or earlier   Successful: (none)     Unsuccessful/late: (see below)   Catalog generation's email notification is received On release date or earlier   Successful: A blog entry in Community Portal (Technopedia Blog) to capture content statistics (Manufacturers, Software Releases, Hardware Models, Mapped Signatures, Ignored Signatures). The blog will be updated for every release with the latest update on top.     Unsuccessful/late: A blog entry in Community Portal (Technopedia Blog) to provide reasons for failure and ETA for the next successful catalog. The blog will be updated for every unsuccessful/late instance with the latest update on top.   API Tests' email notification is received On release date or earlier   Successful: (none)     Unsuccessful/late: A blog entry in Community Portal (Technopedia Blog) to provide reasons for failure and ETA for the next successful catalog. The blog will be updated for every unsuccessful/late instance with the latest update on top.   ... View more

Pitney Bowes Software and Data has been acquired by Precisely   Pitney Bowes Software and Data has been acquired by Precisely. Reference:  https://www.precisely.com/about-us/pitney-bowes-software-and-data?utm_medium=Redirect-PB&utm_source=Direct-Traffic Please note that this is a part-migration, as there are still some software products under Pitney Bowes. Technopedia has reflected this change based on our research findings.  We have integrated the related Pitney Bowes's products and releases under Precisely.   Please refer to the attachments in this blog to see the full product changes. ... View more

National Instruments renamed as NI   On June 16, 2020, National Instruments announced that they were officially changing the company's name to NI. https://en.wikipedia.org/wiki/National_Instruments To reflect these changes in Technopedia,  we have integrated all National Instruments ' products and releases under NI.  The manufacturer National Instruments  (mfr id: 7518 ) has been marked as 'inactive' and has been replaced by NI (mfr id: 1074694797) as a tier 2 manufacturer. This change is now reflected in the  Technopedia Manufacturer Tier 1 and Tier 2 List. https://community.flexera.com/t5/Data-Platform-Knowledge-Base/Technopedia-Manufacturer-Tier-1-and-Ti...   Please refer to the attachments in this blog to see the full product changes.   ... View more

Koninklijke Philips Electronics has been renamed as Koninklijke Philips   In 2013, Koninklijke Philips Electronics NV changed its name to 'Koninklijke Philips'. https://en.wikipedia.org/wiki/Philips https://web.archive.org/web/20140223051749/https://www.eurexchange.com/blob/exchange-en/4060-497582/497578/2/data/er13096e.pdf To reflect these changes in Technopedia,  we have integrated all Koninklijke Philips Electronics's products and releases under Koninklijke Philips.  The manufacturer Koninklijke Philips Electronics   (mfr id:  944382 ) has been marked as 'inactive' and has been replaced by Koninklijke Philips (mfr id: 1074682044) as a tier 2 manufacturer. This change is now reflected in the  Technopedia Manufacturer Tier 1 and Tier 2 List. https://community.flexera.com/t5/Data-Platform-Knowledge-Base/Technopedia-Manufacturer-Tier-1-and-Tier-2-List/ta-p/5951   Please refer to the attachments in this blog to see the full product changes. ... View more

We have noticed that the copyright of the website of  Sony Mobile Communications has changed to Sony Corp. Reference: https://www.sonymobile.com/ To reflect these changes in Technopedia, We have integrated all Sony Mobile Communications's products and releases under Sony. All mappings related are changed accordingly. Now the manufacturer Sony Mobile Communications   (mfr id:  8734 ) has been marked as 'inactive'.  We have compiled a complete list of the changes that we have made. Please refer to the attachments in this post. The Technopedia Manufacturer Tier 1 and Tier 2 list has now been updated with these changes. See here for full list: https://community.flexera.com/t5/Data-Platform-Knowledge-Base/Technopedia-Manufacturer-Tier-1-and-Ti...      ... View more

3M Health Information Systems, used to be a subsidiary of 3M. Now, 3M Health Information Systems is just a business of 3M. To reflect these changes in Technopedia, we have integrated all 3M Health Information Systems's products and releases under   3M . Now the manufacturer 3M Health Information Systems   (mfr id:  4268 ) has been marked as 'inactive'.  3M (mfr id:  1206165 ) has been upgraded to Tier 2. Please refer to the attachment in this blog to see the full product changes.   ... View more

Net Promoter Score (NPS) Survey launching for Content Requests   Flexera is rolling out the NPS Survey for all Customer requests for Content Services.  From this weekend, August 1st, every Support request for Content updates across FlexNet Manager, Data Platform, and Technopedia will generate an invite to take the NPS survey on case closure.    This survey asks one question:-   ‘How likely are you to recommend Flexera to others?’   We are gathering this information to measure customer attitude and satisfaction for how well we are meeting your needs for delivering enhanced content. The responses will help up to understand what we are doing well and react to the things that need improvement.  We hope that you will engage in the survey and provide your open and honest feedback. ... View more

Net Promoter Score (NPS) Survey launching for Content Requests   Flexera is rolling out the NPS Survey for all Customer requests for Content Services.  From this weekend, August 1st, every Support request for Content updates across FlexNet Manager, Data Platform, and Technopedia will generate an invite to take the NPS survey on case closure.    This survey asks one question:-   ‘How likely are you to recommend Flexera to others?’   We are gathering this information to measure customer attitude and satisfaction for how well we are meeting your needs for delivering enhanced content. The responses will help up to understand what we are doing well and react to the things that need improvement.  We hope that you will engage in the survey and provide your open and honest feedback.   ... View more

Description Mobile hotspots can be defined as mobile devices which are used to provide network access via (or requiring) cellular services such as LTE, 5G, etc.      The attachment provided in this blog displays the current hardware models that have been realigned to this category.         ... View more

In 2009, Nortel filed for bankruptcy protection in Canada and the United States, triggering a 79% decline of its corporate stock. The bankruptcy case was the largest in Canadian history, and left pensioners, shareholders and former employees with enormous losses. By 2016 Nortel had sold billions of dollars' worth of assets. Courts in the U.S. and Canada approved a negotiated settlement of bankruptcy proceedings in 2017 Reference: https://en.wikipedia.org/wiki/Nortel   SuperLogix Software has gone out of business, and the domain is currently on sale. Reference: http://www.superlogix.net/   The following manufacturers are now Inactive (downgraded from Tier 1 to Tier Inactive): Nortel Networks (7678) The following manufacturers are now Inactive (downgraded from Tier 2 to Tier Inactive): SuperLogix Software (804520)   The changes are now reflected in the official manufacturer tier list. https://community.flexera.com/t5/Data-Platform-Knowledge-Base/Technopedia-Manufacturer-Tier-1-and-Tier-2-List/ta-p/5951 ... View more