|
SmartWIP - Work-In-Process
Tracking Platform
The SmartWIP platform has been developed on Microsoft technologies
as a service oriented architecture. The SmartWIP platform integrates
seamlessly with existing legacy applications and with factory floor
automation software such as an MES.
- Rapid implementation - SmartWIP provides customization
features and an extensive set of configuration tools for easy
modification and enhancement while reducing engineering and IT
support. Using intuitive operator interfaces to train technicians,
SmartWIP significantly reduces the overall configuration efforts
and set up costs.
- RFID Tag Database - SmartWIP uses the RFID tag as a
portable database storing WIP information within the tag. This
unique approach provides the ability to perform validations at the
process level without the need to integrate with an enterprise MES
system. The tag database also provides the ability to perform
validations and collect WIP data in environments that are not
connected to computer networks.
- Simulation - SmartWIP has a comprehensive simulation
engine that simulates not only the RFID hardware but the
individual process tools within the manufacturing process. The
simulation engine enables SmartWIP to be integrated into
production environments with minimal risk to disruptions.
- Standards support - SmartWIP support industry standards
for data and process integration. Including Semi E-10 standards
for tool state management and Web Services for data integration to
enterprise systems.
- Architecture - SmartWIP supports integrated web reports
and robust analytical capabilities for real time control of
production operations. The Web Services Framework and APIs support
real-time communications with enterprise systems regardless of
data format or platform.
- Scalability - SmartWIP supports the ability to deploy the
solution across a single process line and scale the implementation
to support multiple manufacturing lines. Advanced data caching
capabilities enable seamless transfer of validations, lots and lot
history between distributed clients and centralized data stores.

|
|