It appears that Data Standard is incapable of creating custom iProperties if they do not exist. This creates a headache and lots of work adding the custom iProperties to templates, files, content center libraries, design accelerator templates, Tube & Pipe, Cable harness. iLogic and other API's offer ability to create them. Being able to create them from powershell would avoid all of this other work. Recently found out that Cable & Harness segments have no template to set the iProperties in so there is no way to add them besides manually adding them else data standard will fail.