Results captured as Other (2S0Z)
- Sticky: Identify the “911” issue in manufacturing interoperability to motivate government, Congress, and administration (2S8Z)
- Slide: Identify the “911” issue in Manufacturing Interoperability to motivate govt, congressional, and administration (2S90)
- How to get people excited? Cost savings? Panic manufacturing issue, e.g., DHS protecting flow of goods, supply chain? Motivation by crisis? Business problem? (2S91)
- Innovation with the mfg business case across business and technical folks; continues to be disconnect (2S92)
- Sticky: Motivating defense and commercial industry to develop standard interoperability solutions for coalition warfare (2S93)
- Slide: Broker commercial/military standards solution for coalition warfare (2S94)
- Sticky: Reorganize your focus areas – (Not a logical taxonomy). Suggest: (2S95)
- Slide: Reorganize the program’s focus areas (not a logical taxonomy) (2S9B)
- Cross-cutting enablers (cross-referenced to “enablers” slide) (2S9C)
- Domain Unique (2S9G)
- Sticky: Katherine Morse is trying to fund a task to look at the interoperability issues between TENA and HLA RTIs (don’t know if she has included DSS), and solve those issues. Not funded yet. If manufacturers move to service-oriented architecture (SOA), NIST could play a role in maintaining the Discovery/Registry models for identifying specs, services, date, models, tools, that are authoritative and available for manufacturers to use in their product development process. Honest broker and interoperability facilitator. (2S9H)
- Slide: Honest broker & interoperability facilitator (e.g., IF manufacturers move to SOA, NIST could maintain discovery/registry models/tools for identifying specs services data that authoritative and available for manufacturers to use in their product development process.) (2S9I)
- Sticky: Most of the discussion has been at the piece-part level. NIST may want to look at the manufacturing process from a system engineering view and develop a manufacturing system engineering view model. (2S9J)
- Slide: Work on a manufacturing systems engineering model (standard?) (2S9K)
- Systems engineering approach to MIP; overarching engineering process instead of stovepipes (2S9L)
- Sticky: NIST, with the support of industry associations, maintain a persistent testbed for interoperability (2S9M)
- Slide: With support of industry, maintain a persistent test bed for interoperability (2S9N)
- Sticky: Focus on data models and data exchange formats by industry, including international agreement to support global sourcing (2S9O)
- Slide: Focus on data models and data exchange formats by industry, including international agreement to support Global Sourcing (2S9P)
- (counter) You should look at what you can do at cross-cutting first (JH) (2S9Q)
- Sticky: Expand effort in off-shore interoperability (2S9R)
- Slide: At what level should standardization take place? (2S9S)
- Expand effort in off-shore interoperability (2S9T)
- Sticky: At what level should standardization take place? (2S9V)
- Sticky: Long-term data retention (2S9W)
- Slide: Long-term data retention (2S9X)