All Activity

This stream auto-updates     

  1. Today
  2. Marcos Garcia

    Product definition after 2019-02-26 Working Session

    Here there is an example for 2 IOT products. One of them using collections of lens blanks provided by a different vendor. https://drive.google.com/file/d/1WOeT749fTRTYdJcw1eub9apVTHAKSlR7/view?usp=sharing
  3. Last week
  4. Paul Wade

    Vision Expo East 2019 Agenda

    Agenda for our 2019 VEE meeting. 2019 VEE - DCS Agenda - FINAL.pdf
  5. Adrian

    Product definition after 2019-02-26 Working Session

    I also added the DCS fields for polarized film details into the Blank; PLRCRV & PLRLOC
  6. Adrian

    Product definition after 2019-02-26 Working Session

    Hi Steve, We have updated the Zeiss complete example to use the changes you have made above, excluding alphabetical ordering of fields. This example is larger than required for the working document but can provide a second reference. It can be found though the following link: Updated Example - Google Docs (I recommend turning print layout off when viewing the document) I have also added some suggested changes to better map fields in Blanks to their respective DCS fields: Base -> MBASE Addition -> ADD Front Radius -> FRNT Back Radius -> BACK
  7. Earlier
  8. I've updated the working definition, which is still using the same file location as before. https://docs.google.com/document/d/1W9JL-d93RfKZwRp_2K1hBtD27-PhyVI6_-WZjZdrKF4/edit?usp=sharing I've modified it so that some of the naming is more consistent now. A reference to a list of other items defined elsewhere in the document has a name ending with "IDs" A reference to a single item defined elsewhere in the document has a name ending in "ID" The Owner value has been removed from each object, given that the ID now incorporates the owner. Alphabetized fields, to make tracking down missing ones easier (Though I stopped doing Blanks after the first few). Changed the way treatments were included in the Characteristic Family to match how it was done at the product level, with using specific lists indicating requirements such as "Required Treatment IDs" I've also included a diagram of that JSON structure. Each box has three sections that are delimited by a horizontal line The first section indicates the name of the node. If there is more than one line in that top section, it indicates a child object of the parent. The second section is for values that are either the object's ID, or references to another objects ID The third section is for values that are not foreign keys, and are informational about that particular object. I think adding all the lines that would point to Parameters and Treatments would make the document a lot more difficult to read, so I've left those out. But, a name that has "* Parameter ID(s)" or "* Treatment ID(s)" will indeed be referencing objects in those appropriate nodes.
  9. https://drive.google.com/file/d/1JJjTVyaq626b9ggYyBP90m8Q4d0o-U8f/view?usp=sharing
  10. Marcos Garcia

    LPDS Data Structure Sample

    Thanks
  11. tonyleblanc

    LPDS Data Structure Sample

    Hi, Marcos - I sent you the link to the google document via email.
  12. Marcos Garcia

    LPDS Data Structure Sample

    Hi there, I was trying to find the working sample that Stephen was editing during our last call yesterday. Is it in a Google Drive or somewhere that can be shared? I would like to use it to edits the samples that I was working on. Maybe we should have a shared Google Drive folder where to upload everything that we work on directly. It could be easier to follow up for any updates. Thanks
  13. Paul Wade

    product structure

    Hi there. My name is Paul Wade and I'm a liaison for The Vision Council. I'd like to see if I can help you with this but it might be better if you contact me directly. You can email me at pwade@thevisioncouncil.org. If you could include some more detail about the system you are trying to design I can try and provide you with some documentation that might help with your goal.
  14. aqadirhasan

    product structure

    is there any standard and easy way i can define my lens code number with description to my customize lens inventory system. please advice.
  15. The audio from the DCS meeting at VEW 2018 has been uploaded to our Google Drive folder. https://drive.google.com/file/d/1SapKukV1slmkNc3DEKaQQD0IGraaZreT/view?usp=sharing Please let me know if you have any trouble downloading it. Paul
  16. Hi Everyone, The audio from our working group meeting is now available: https://drive.google.com/file/d/1wr30abo1Zib0v-dtwuONCzYBLw7pbRS0/view?usp=sharing Let me know if you have any trouble downloading it. Thanks, Paul
  17. Hi Everyone, The audio for our 2018 VEW meeting is now available: https://drive.google.com/file/d/1jsTOINTa0IwKT9y-xKi0jIGtfqQqsaPI/view?usp=sharing Let me know if you have any trouble downloading it. Thanks, Paul
  18. Steve Shanbaum

    Base Curve Charts

    Steve posted the presentation in another thread, so that's a better starting point than this one and the discussion should take place over there.
  19. The presentation attached proposes a way of more efficiently communicating range chart data rather than a list of each combination or simple array. The second file is a more detailed version of the presentation. Please review and provide feedback, suggestions or alternatives. One observation raised at the meeting was that there might be a more efficient way to define boundaries rather than the use of in between 025 steps (for example -262cyl) referring to a numerically irrelevant base curve (1000D). Base Selection Communication Detailed Description.pdf Base Charts Communication Presentation.pdf
  20. Steve Shanbaum

    Base Curve Charts

    This is to get the conversation started on Base Curve Charts within the LPDS. (Very condensed and slightly modified) Zeiss presented something similar to the following as a suggested terse method of transmitting the Base Curve Charts. Steve should be able to post the actual presentation to get much better detail to explain this. Add, Sphere, Cyl, Base 0, -9, -4, NA 0, -9, -2, 8 0, -9, 0, 6 0, -6, -4, NA 0, -6, -2, 6 0, -6, 0, 4 Where a -6sph, -2.5cyl would pick a 6 base. Which, at first glance, to fit into JSON tersely, would be something like: “Base Curve Charts” : [ { “ID” : “123”, “Owner ID” : “TVC”, “Adds” : [ “0” : { Spheres : [ “-9” : [ “-4” : “NA”, “-2” : 8, “0” : 6 ], “-6” : [ “-4” : “NA”, “-2” : 6, “0” : 4 ] ] } ] } ] Which, since JSON parsers don't ensure that things get spit out in the same order that they were input in, the readability goes out the window. It also doesn't have to be interpreted into JSON and could be left more in the original format. But, this is just to get conversation going about this.
  21. Marcos Garcia

    LPDS Data Structure Sample - IOT

    I just edit the sharing options of the Google Drive link so anybody can view it. Anyway, just in case I am attaching the file here. LPDS Data Structure _ IOT example.docx
  22. Paul Wade

    2018 VEE Meeting Minutes

    I apologize for the delay in posting these. Steve provided them several weeks ago and I thought I had already sent them out. I just realized my mistake this morni ng. 2018 VEE - LPDS Meeting Minutes - Final.pdf
  23. Marcos Garcia

    LPDS Data Structure Sample - IOT

    Hi all, I have uploaded to Google Drive an examples of the LPDS Structure for several IOT products. It is in a word format to try to make it easier to edit and follow. https://drive.google.com/open?id=1ImkUpeniCzh5Vb0hiS2YkKsCi_CkpHZ2
  24. Paul Wade

    Request for Agenda Topics for VEE 2018

    Thank you Thomas. This has been added to the agenda.
  25. Thomas Koerbe

    Request for Agenda Topics for VEE 2018

    Hi Paul, I would like to request one more label related to a blocking ring diameter for the Satisloh ART process. Currently we have the following labels being used: Alloy: BLKD RNGH ART: BLKD -->same as for Alloy BLKB BVAL As you can see BLKD is the same for both processes. In case a LMS wants to provide information for both processes ART and Alloy blocking, it would be good to have a separate label for the ART block diameter. Thank you! Thomas
  26. Paul Wade

    VEW 2018 Agenda Now Available

    Dear Colleagues, You can find the agenda for the LPDS Committee meeting at VEW 2018 posted here: https://thevisioncouncil.org/sites/default/files/2018-VEW-LPDS-Agenda-FINAL.pdf If you have any topics you would like added to the agenda please reply to this post or send them to Daniel Simonetta or myself directly. Thanks!
  27. Paul Wade

    Vision Expo West 2018 Agenda

    The synopsis would be very brief indeed. We have no such capability at the moment and without specifications it would be hard to predict what changes or additions would be necessary to support such a platform.
  28. DanielSimonetta

    Vision Expo West 2018 Agenda

    Hello Paul, Thank you for contributing to the discussion. I am sure that all of our members will be concerned with the security and access capability should TVC take on this type of responsibility. Would you be willing to prepare a short synopsis of TVC's current capability for this type of thing?
  1. Load more activity