Steve Ray - Academia.edu (original) (raw)
Papers by Steve Ray
The goal of the NIST Process Specification Language (PSL) project is to investigate and arrive at... more The goal of the NIST Process Specification Language (PSL) project is to investigate and arrive at a neutral, unifying representation of process information to enable sharing of process data among manufacturing engineering and business applications. This paper focuses on the second phase of the project, the analysis of existing process representations to determine how well existing process representation methodologies support the requirements for specifying processes found in Phase One. This analysis will provide an objective basis from which to develop a comprehensive language and will promote the leveraging of existing work. Process Specification Language: An Analysis of Existing Representations
Recent years have seen rapid progress in the development of ontologies as semantic models intende... more Recent years have seen rapid progress in the development of ontologies as semantic models intended to capture and represent aspects of the real world. There is, however, great variation in the quality of ontologies. If ontologies are to become progressively better in the future, more rigorously developed, and more appropriately compared, then a systematic discipline of ontology evaluation must be created to ensure quality of content and methodology. Systematic methods for ontology evaluation will take into account representation of individual ontologies, performance (in terms of accuracy, domain coverage and the efficiency and quality of automated reasoning using the ontologies) on tasks for which the ontology is designed and used, degree of alignment with other ontologies and their compatibility with automated reasoning. A sound and systematic approach to ontology evaluation is required to transform ontology engineering into a true scientific and engineering discipline. This chapte...
2009 IEEE International Conference on Automation Science and Engineering, 2009
The high cost of healthcare in America is well-known, with imperfect interoperability adding as m... more The high cost of healthcare in America is well-known, with imperfect interoperability adding as much as $77.8 billion/year to that cost, according to one study [1]. One of the principal causes of this high cost is the large amount of “paperworkz” — the administrative expenses incurred for each medical procedure. While the debate continues about whether the country would be better off with a single-payer medical system or the current private insurance approach, there are a number of ways to reduce the administrative costs without excessive risk. These costs are essentially about getting information in the right form, to the right place, at the right time — a challenge that is by no means unique to the healthcare industry. This presentation identifies some of the approaches that have been successful in the manufacturing sector to make the sharing of information — interoperability — more efficient. Manufacturing technology has been developing and improving for decades. Principles like lean manufacturing, paperless design, ISO 9000 performance practices and Taguchi methods are a given for today's major manufacturers. With trends toward global manufacturing and outsourcing, practices have now evolved to Internetbased communication of engineering designs, inventory levels, purchase orders, and a wide variety of other logistical, financial and technical data. Supporting all this, a suite of standards has been developed, deployed, and winnowed down to some that really help, leaving others that seemed promising but failed to meet expectations by the wayside.
Internet stranica: http://www. mel. nist. gov/psl/pubs/spain/paper. htm, 1997
Abstract: The goal of the NIST Process Specification Language (PSL) project is to investigate and... more Abstract: The goal of the NIST Process Specification Language (PSL) project is to investigate and arrive at a common, unifying model of process which will ultimately be suitable for multiple process-related applications, yet powerful and robust enough to meet each set of requirements. This paper focuses on the second phase of the project, that of analyzing existing process representations to determine how well they represent the information requirements found in an earlier phase of the project.
Standards and Technology (NIST), the Upper Ontology Summit (UOS) took place. The Upper Ontology S... more Standards and Technology (NIST), the Upper Ontology Summit (UOS) took place. The Upper Ontology Summit was a convening of custodians of several prominent upper ontologies, key ontology technology participants, and interested other parties,
Conference on Lasers and Electro-Optics
Applied Ontology
The Ontology Summit 2012 explored the current and potential uses of ontology, its methods and par... more The Ontology Summit 2012 explored the current and potential uses of ontology, its methods and paradigms, in big systems and big data: How ontology can be used to design, develop, and operate such systems. The systems addressed were not just software systems, although software systems are typically core and necessary components, but more complex systems that include multiple kinds and levels of human and community interaction with physical-software systems, systems of systems, and the socio-technical environments for those ...
The National Institute of Standards and Technology is in the process of establishing a testbed wh... more The National Institute of Standards and Technology is in the process of establishing a testbed which will serve the research and information needs of the process planning community. This testbed is building up four primary services designed to facilitate the development of process planning technology: information services, workshops, a testing and integration laboratory, and a collaborative research program. Each of these services is described, along with their motivation and expected impact.
In April, 1997, the Process Specification Language (PSL) Project held a Roundtable discussion at ... more In April, 1997, the Process Specification Language (PSL) Project held a Roundtable discussion at the National Institute of Standards and Technology (NIST). The goals of the Roundtable was to assemble key champions and stakeholders of various approaches towards process representation in order to discuss the relative merits to reach consensus on a language architecture and to establish a technical approach for proceeding. It was agreed that the language architecture should be based upon a formal semantic foundation, upon which would be layered a number of syntactic mappings, each with one or more presentations. In discussions about principal concepts of any process representation, it was agreed that "process" and "participant (resource)" are basic. A number of possible other concepts were suggested, but no consensus was reached. Additionally, five potential uses for the PSL were identified and discussed. They were: 1) provide a description of a process that has already occurred; 2) provide a "recipe" (prescription) describing how a process can occur; 3) provide a semantic model to determine concepts and establish the scope of systems; 4) enable interoperability between manufacturing systems, enterprise systems, and/or AI systems; 5) enable technology transfer between manufacturing and other disciplines. Finally, three teams were formed to define: • A set of scenarios to support the identification and definition of semantic concepts and to provide potential uses of the language; • A semantic description covering a small subset of the core language requirements; • Three syntactic interpretations of that semantic description, mapping to object-oriented, KIF, and constraint-based presentations. A relational presentation was also
This document presents the development of the Manufacturing Systems Integration project as of Jul... more This document presents the development of the Manufacturing Systems Integration project as of July, 1990. It provides a foundation for the understanding of the project and its results. It is important to note that since work on the project is ongoing, some of the results presented in this document have been superceded. This document is the initial report of a series of reports planned for this project; it serves as a reference for these future reports. 1. The first occurrence of glossary terms appear in bold-italics (see Appendix 1-Glossary). administrative control The process of ensuring the smooth start-up and shutdown of the control system, both in ordinary operations and in response to emergency conditions. administrative subordinate interface An MSI control entity interface from which administrative supervisory commands are received and administrative subordinate status is reported. administrative supervisor interface An MSI control entity interface from which administrative supervisory commands are issued and administrative subordinate status is received. architecture The design and structure of a system. baseline configuration (1) The process of specifying the initial configuration of the system. (2) The result of the process in (1), (i.e. the specification of the initial configuration of the system.) black box A subsystem which is described only in terms of its inputs, outputs and functionality, but whose internal architecture is unspecified. checkpoint A step in a production plan where the manufacturing process may be halted in a safe manner without damaging either the equipment or the workpiece and later resumed. communication paradigm The set of operating principles characterizing a given communications approach. communication The transmission of information between distinct agents. configuration The collection of resources in a given shop and their physical and logical relationships to one another. configuration management Specification and control of shop resources, capabilities, and their physical and logical relationships.
This task status report acknowledges the receipt of the get_data command for the shuttle.
A wide range of manufacturing software applications deal with the manipulation and expression of ... more A wide range of manufacturing software applications deal with the manipulation and expression of collections of activities. Examples include manufacturing process planning, production scheduling, simulation, project management, workflow, business process reengineering, and product realization process modeling. While each of these applications serves a specific audience and need and focuses on particular aspects of a process, much could be gained by sharing process information among applications. One of the primary obstacles to such integration is the lack of any common representation of what is really the underlying concept of process. The objective of the work described here is to investigate the feasibility of a unifying specification of process that is applicable to all of the above manufacturing applications, yet powerful and robust enough to meet each set of requirements. The results of the first phase of the work-that of researching the process specification requirements for design/manufacturing process life-cycle applications-are described and analyzed. Alternative views of the process specification requirements provide the ability to better understand them, to ensure their completeness, and to envision the structure and approach of a future, generic process specification language (PSL). Task, resource, product, and time are identified and analyzed as the fundamental aspects of process, offering insights to understanding, analyzing, and improving manufacturing and business processes.
Problem Currently, there is no agreed on methodology for development of ontologies, and there is ... more Problem Currently, there is no agreed on methodology for development of ontologies, and there is no consensus on how ontologies should be evaluated. Consequently, evaluation techniques and tools are not widely utilized in the development of ontologies. This can lead to ontologies of poor quality and is an obstacle to the successful deployment of ontologies as a technology. Approach The goal of the Ontology Summit 2013 was to create guidance for ontology developers and users on how to evaluate ontologies. Over a period of four months a variety of approaches were discussed by participants, who represented a broad spectrum of ontology, software, and system developers and users. We explored how established best practices in systems engineering and in software engineering can be utilized in ontology development. Results This document focuses on the evaluation of five aspects of the quality of ontologies: intelligibility, fidelity, craftsmanship, fitness, and deployability. A model for the ontology life cycle is presented, and
Proceedings of the 1996 Nsf Design and Manufacturing Grantees Conference, 1996
The goal of the NIST Process Specification Language (PSL) project is to investigate and arrive at... more The goal of the NIST Process Specification Language (PSL) project is to investigate and arrive at a neutral, unifying representation of process information to enable sharing of process data among manufacturing engineering and business applications. This paper focuses on the second phase of the project, the analysis of existing process representations to determine how well existing process representation methodologies support the requirements for specifying processes found in Phase One. This analysis will provide an objective basis from which to develop a comprehensive language and will promote the leveraging of existing work. Process Specification Language: An Analysis of Existing Representations
Recent years have seen rapid progress in the development of ontologies as semantic models intende... more Recent years have seen rapid progress in the development of ontologies as semantic models intended to capture and represent aspects of the real world. There is, however, great variation in the quality of ontologies. If ontologies are to become progressively better in the future, more rigorously developed, and more appropriately compared, then a systematic discipline of ontology evaluation must be created to ensure quality of content and methodology. Systematic methods for ontology evaluation will take into account representation of individual ontologies, performance (in terms of accuracy, domain coverage and the efficiency and quality of automated reasoning using the ontologies) on tasks for which the ontology is designed and used, degree of alignment with other ontologies and their compatibility with automated reasoning. A sound and systematic approach to ontology evaluation is required to transform ontology engineering into a true scientific and engineering discipline. This chapte...
2009 IEEE International Conference on Automation Science and Engineering, 2009
The high cost of healthcare in America is well-known, with imperfect interoperability adding as m... more The high cost of healthcare in America is well-known, with imperfect interoperability adding as much as $77.8 billion/year to that cost, according to one study [1]. One of the principal causes of this high cost is the large amount of “paperworkz” — the administrative expenses incurred for each medical procedure. While the debate continues about whether the country would be better off with a single-payer medical system or the current private insurance approach, there are a number of ways to reduce the administrative costs without excessive risk. These costs are essentially about getting information in the right form, to the right place, at the right time — a challenge that is by no means unique to the healthcare industry. This presentation identifies some of the approaches that have been successful in the manufacturing sector to make the sharing of information — interoperability — more efficient. Manufacturing technology has been developing and improving for decades. Principles like lean manufacturing, paperless design, ISO 9000 performance practices and Taguchi methods are a given for today's major manufacturers. With trends toward global manufacturing and outsourcing, practices have now evolved to Internetbased communication of engineering designs, inventory levels, purchase orders, and a wide variety of other logistical, financial and technical data. Supporting all this, a suite of standards has been developed, deployed, and winnowed down to some that really help, leaving others that seemed promising but failed to meet expectations by the wayside.
Internet stranica: http://www. mel. nist. gov/psl/pubs/spain/paper. htm, 1997
Abstract: The goal of the NIST Process Specification Language (PSL) project is to investigate and... more Abstract: The goal of the NIST Process Specification Language (PSL) project is to investigate and arrive at a common, unifying model of process which will ultimately be suitable for multiple process-related applications, yet powerful and robust enough to meet each set of requirements. This paper focuses on the second phase of the project, that of analyzing existing process representations to determine how well they represent the information requirements found in an earlier phase of the project.
Standards and Technology (NIST), the Upper Ontology Summit (UOS) took place. The Upper Ontology S... more Standards and Technology (NIST), the Upper Ontology Summit (UOS) took place. The Upper Ontology Summit was a convening of custodians of several prominent upper ontologies, key ontology technology participants, and interested other parties,
Conference on Lasers and Electro-Optics
Applied Ontology
The Ontology Summit 2012 explored the current and potential uses of ontology, its methods and par... more The Ontology Summit 2012 explored the current and potential uses of ontology, its methods and paradigms, in big systems and big data: How ontology can be used to design, develop, and operate such systems. The systems addressed were not just software systems, although software systems are typically core and necessary components, but more complex systems that include multiple kinds and levels of human and community interaction with physical-software systems, systems of systems, and the socio-technical environments for those ...
The National Institute of Standards and Technology is in the process of establishing a testbed wh... more The National Institute of Standards and Technology is in the process of establishing a testbed which will serve the research and information needs of the process planning community. This testbed is building up four primary services designed to facilitate the development of process planning technology: information services, workshops, a testing and integration laboratory, and a collaborative research program. Each of these services is described, along with their motivation and expected impact.
In April, 1997, the Process Specification Language (PSL) Project held a Roundtable discussion at ... more In April, 1997, the Process Specification Language (PSL) Project held a Roundtable discussion at the National Institute of Standards and Technology (NIST). The goals of the Roundtable was to assemble key champions and stakeholders of various approaches towards process representation in order to discuss the relative merits to reach consensus on a language architecture and to establish a technical approach for proceeding. It was agreed that the language architecture should be based upon a formal semantic foundation, upon which would be layered a number of syntactic mappings, each with one or more presentations. In discussions about principal concepts of any process representation, it was agreed that "process" and "participant (resource)" are basic. A number of possible other concepts were suggested, but no consensus was reached. Additionally, five potential uses for the PSL were identified and discussed. They were: 1) provide a description of a process that has already occurred; 2) provide a "recipe" (prescription) describing how a process can occur; 3) provide a semantic model to determine concepts and establish the scope of systems; 4) enable interoperability between manufacturing systems, enterprise systems, and/or AI systems; 5) enable technology transfer between manufacturing and other disciplines. Finally, three teams were formed to define: • A set of scenarios to support the identification and definition of semantic concepts and to provide potential uses of the language; • A semantic description covering a small subset of the core language requirements; • Three syntactic interpretations of that semantic description, mapping to object-oriented, KIF, and constraint-based presentations. A relational presentation was also
This document presents the development of the Manufacturing Systems Integration project as of Jul... more This document presents the development of the Manufacturing Systems Integration project as of July, 1990. It provides a foundation for the understanding of the project and its results. It is important to note that since work on the project is ongoing, some of the results presented in this document have been superceded. This document is the initial report of a series of reports planned for this project; it serves as a reference for these future reports. 1. The first occurrence of glossary terms appear in bold-italics (see Appendix 1-Glossary). administrative control The process of ensuring the smooth start-up and shutdown of the control system, both in ordinary operations and in response to emergency conditions. administrative subordinate interface An MSI control entity interface from which administrative supervisory commands are received and administrative subordinate status is reported. administrative supervisor interface An MSI control entity interface from which administrative supervisory commands are issued and administrative subordinate status is received. architecture The design and structure of a system. baseline configuration (1) The process of specifying the initial configuration of the system. (2) The result of the process in (1), (i.e. the specification of the initial configuration of the system.) black box A subsystem which is described only in terms of its inputs, outputs and functionality, but whose internal architecture is unspecified. checkpoint A step in a production plan where the manufacturing process may be halted in a safe manner without damaging either the equipment or the workpiece and later resumed. communication paradigm The set of operating principles characterizing a given communications approach. communication The transmission of information between distinct agents. configuration The collection of resources in a given shop and their physical and logical relationships to one another. configuration management Specification and control of shop resources, capabilities, and their physical and logical relationships.
This task status report acknowledges the receipt of the get_data command for the shuttle.
A wide range of manufacturing software applications deal with the manipulation and expression of ... more A wide range of manufacturing software applications deal with the manipulation and expression of collections of activities. Examples include manufacturing process planning, production scheduling, simulation, project management, workflow, business process reengineering, and product realization process modeling. While each of these applications serves a specific audience and need and focuses on particular aspects of a process, much could be gained by sharing process information among applications. One of the primary obstacles to such integration is the lack of any common representation of what is really the underlying concept of process. The objective of the work described here is to investigate the feasibility of a unifying specification of process that is applicable to all of the above manufacturing applications, yet powerful and robust enough to meet each set of requirements. The results of the first phase of the work-that of researching the process specification requirements for design/manufacturing process life-cycle applications-are described and analyzed. Alternative views of the process specification requirements provide the ability to better understand them, to ensure their completeness, and to envision the structure and approach of a future, generic process specification language (PSL). Task, resource, product, and time are identified and analyzed as the fundamental aspects of process, offering insights to understanding, analyzing, and improving manufacturing and business processes.
Problem Currently, there is no agreed on methodology for development of ontologies, and there is ... more Problem Currently, there is no agreed on methodology for development of ontologies, and there is no consensus on how ontologies should be evaluated. Consequently, evaluation techniques and tools are not widely utilized in the development of ontologies. This can lead to ontologies of poor quality and is an obstacle to the successful deployment of ontologies as a technology. Approach The goal of the Ontology Summit 2013 was to create guidance for ontology developers and users on how to evaluate ontologies. Over a period of four months a variety of approaches were discussed by participants, who represented a broad spectrum of ontology, software, and system developers and users. We explored how established best practices in systems engineering and in software engineering can be utilized in ontology development. Results This document focuses on the evaluation of five aspects of the quality of ontologies: intelligibility, fidelity, craftsmanship, fitness, and deployability. A model for the ontology life cycle is presented, and
Proceedings of the 1996 Nsf Design and Manufacturing Grantees Conference, 1996