Item Descriptions

We also use NuVia - but I've long ago given up on descriptions. NuVia's description is used to load the item to the system. If users don't like them, they are invited to create new ones. For Lab items, I go to them first.

We create our own descriptions.  Our standard is...

Start with ====>>>>Noun (what is it?) [NDL (needle), DRSG (dressing), CATH (catheter), PAPER, STAPLER, etc.] => 

Then apply modifiers. Move from general to specific.

Type (what is it used for?) [CERV (cervical), SPEC (specimen), URINARY, DENTURE, etc.], then

We are similar to JonA.  Noun then Adjective then Size then whatever else will fit in 30 characters.  We spell out the noun whenever possible.  Mostly limiting the 2nd description to show reason for inactivation.  We are looking at bringing in NuVia to help but we know going in it won't be perfect.

 

For those on NuVia & v10 - are you populating the new 3rd description field?  If so how are you maintaining it?  Our Epic users will certainly want it to interface from Lawson, but how to keep up with the maintenance?

Thanks for the feedback.  We're on V10 and are working to have all of our item master items have a description 3 60 character description for Epic and all end users.  We're hoping once we get them all loaded maintenance will be minimal.  It's working through the descriptions from Nuvia that's the hard part.  Making sure they're accurate and making sure they're not duplicated.  There's gotta be a better solution. 

Yes - we put NuVia's full description in D3 - it goes across to Epic as an alias so users can drill to it if they need it. Last Fiscal Year we added 59,096 items to the item master (thanks to a spinal implant rfp) - so NuVia's worth it's weight in gold to me.

Epic trains its users to look for part number if they find dupe descriptions and then report them. That's how we periodically get lists of "change description to" - which I am just uploading. (Like I said, we gave up ownership sometime ago. As long as the reorder number is correct, I honestly no longer care what they call it.)

The Epic users themselves are actually very good about creating the descriptions to meet the format - it's only when it duplicates (stryker vs synthes bone screw) or when the typical attribute order cuts something off.

Our current system is: We use IT's ticketing system for the users to create requests - everything loaded to Lawson - contract award, buyer requests, VAT approved, user requests - goes on a ticket - even if it's just to copy/paste an email chain and attach a spreadsheet.

Once the upload is ready, we run it through NuVia and load into Lawson. This closes Supply Chain's portion - users can successfully order the part number at the correct cost. The ticket then goes to Corporate Fiance who works with the Epic teams to verify supply/implant status and build EAPs. It's at this point that if they don't like a description they can just change it on the spreadsheet.

The returned sheet gets uploaded to IC11 for description, gl, use identifier and CDM (EAP in Epic) and into the IC12.

Hi all,
Hoping to get some input on items that are less supply like. What do your descriptions look like for things such as desktop or laptop computers, monitors, mounts, etc..?
Do you put in brand-specific items? Is each model its own item (like HP EliteBook 8040 is one and 8045 is another) or do you just add a generic?
Thanks!

We keep it generic and put brand information in attributes and manufacturer information- but our IT products aren't that "Diverse" - they only stock one type of laptop and the monitors are all same brand so we care about the sizes etc. The printers are PRINTER then COLOR or BW followed by brand and model.

Nope.  IT successfully rebelled against vague descriptions and uses Brand/Model descriptions in IC11.

 

Also for any coming on this thread - two years ago - apparently NuVia's Remove Duplicates in their descriptions broke. Hence the vastly different experiences between us and brupp.

Thanks, Kat.
So, for things like your monitors that you have multiple sizes, I'm guessing you have multiple items that look similar. But, you'd have the different sizes in the description? If so, that makes sense.
I'm still trying to figure out the best way to put desktops and laptops in. We don't have a ton of different varieties, but we do have a few. So, I'm trying to figure out how best to "name" each one to show how they are different. Things like bigger processor, more RAM, bigger hard drives, etc...

Went and looked - We *do* brand the laptops.

LAPTOP DELL 7480 6 GEN I7 PROC
LAPTOP DELL 5580 6 GEN I5 PROC
LAPTOP DELL LATITUDE E5570

And then the poor desktop got the "Lawson only has 30 characters" treatment.
DESKTP SFF OPTPLX 7050 6GEN I7

Some examples of IT equipment descriptions

MONITOR FLAT PANEL LED 19IN
MONITOR HP ELITE E243
MONITOR LCD 22IN NEC
MONITOR LED 19IN
MONITOR LED 21.5IN HP
HP PRODESK 600 G3 DESKTOP DVD+
PC HP AIO T310 ZERO CLIENT
PC HP ELITEBOOK 840 G3 CTO
PC HP ELITEBOOK 840 G3 SMRTBUY
PC HP ELITEBOOK 850 G3
PC HP ELITEBOOK 850 G3 CTO
PC HP T310 ZERO CLIENT

For our system we use the general convention similar to Noun, Adjective, size, color. 

Many times reaching out to the department end user to identify the differentiating characteristic. The 30 character limit does not do us any favors.  Would be great if INFOR would have went with at least 50.  30 is disappointingly small.

CloudSuite Item Master will have 60 character D1 - or so I've been told.