 |
|
|
|
Camstar’s InSite™ Manufacturing Execution System (MES) connects multiple plants, sites, and vendors with live production information, allowing companies to get the most out of their IT investments. The stability, flexibility and scalability of the solution enable rapid deployment while reducing implementation and maintenance costs. It is designed to deliver secure and reliable performance, provide easy integration with existing applications and shop floor systems, and accommodates complex process changes through simple commands. |
| | Learn More: |
| |
|
|
|
 |

|
|
| |
Designed for high-volume, high-reliability and high-availability performance, InSite is a Web-based application built on a distributed Microsoft .NET architecture that provides for maximum flexibility and scaling. Load balancing and redundancy are provided through Oracle’s RACTM and support for Microsoft’s Load Balancing™ (NLB) and Cluster Service™ (MSCS). |
|
|
| |
Depending on organizational needs, the system can be installed as a single-server system or distributed across several servers. Servers can be clustered to deliver resources and processing horsepower where they are needed most. |
| |
This distributed architecture comprises multiple tiers that isolate the complexities of distributed processing and provide support for multiple databases, security, and end user configuration options. InSite’s operational data store, “DataStore,” receives constant updates from the production transaction database in near real-time. DataStore contains all of the transaction data required for complete archiving and reporting, and optimizes the performance of the production application. |
| |
| <top> |
| |
| |
InSite is optimized to support system integration and web-based interfaces.
Users have access to InSite transactions and information from any application
on any platform through Web Services, Java, or ActiveX clients. The architecture
is ideal for transferring information among
disparate systems, as InSite incorporates XML technologies at the core of the system. |
 |
|
| |
| <top> |
| |
| |
For integrating live production information from multiple manufacturing
sites to business systems throughout the enterprises, InSite employs a point-to-framework
integration solution,
LiveConnect. The
LiveConnect model simplifies complex integration scenarios, making the architecture
easy to support and evolve. LiveConnect includes:
|
- Industry best practices for integrating MES with ERP and PLM applications
- Adapters for mySAP Business Suite and Oracle Applications Suite
- Graphical business process modeling and document routing
- Once-only document delivery across multiple platforms
|
Alternatively, InSite
Open Adapter employs InSite’s XML infrastructure
to easily connect directly to EAI frameworks or to other applications. InSite Open
Adapter supports multiple connections and transports, delivers data to file shares,
monitors and retrieves data from file shares, and applies style sheets to execute
XML transformations.
|
The InSite architecture also allows organizations to develop custom interfaces to
InSite using the platforms and languages of their choice. For example:
|
- Using Web Services, ActiveX or Java XML APIs, they can create custom platform-independent
or Windows-based clients
- For direct integration with equipment in a high-volume situation, InSite connects
directly to control platforms such as Supervisory Control and Data Acquisition (SCADA)
and Ole for Process Control (OPC) using the Active-X or Java interface. Camstar’s
InSite OPC client simplifies OPC connectivity by eliminating the need for custom
coding.
- The architecture supports Windows CE and PDA devices as workstations, and can utilize
radio-frequency (RF) communication devices
|
|
| |
| <top> |
| |
|
Configurable business logic, rather than hard-coded logic, allows InSite applications
to be tailored to meet unique factory requirements without changing or recompiling
program code. Because the application rules and logic are isolated from the client
logic and the database, the application logic to process a request is
always the same - whether the transaction originates in a configurable InSite form
(screen) or an interface to another system. This server-side logic approach makes
it possible to: |
- Provide 100% thin-client workstations to users; only a browser is required
- Easily integrate InSite with existing systems and specialized forms while ensuring
the integrity of the application processing
- Minimize re-validation requirements when configuring business logic or upgrading
- Make new functionality immediately available without disrupting operations
|
|
| |
| <top> |
| |
|
InSite employs a 100% thin client, browser-based user interface. Included are standard
web forms (screens) for shop floor and factory modeling activities that parallel
the actual work, and screen forms are easily customized using InSite’s
Web Forms Builder. User screens display
on desktop computers or smart mobile devices, maximizing your options and eliminating
work station maintenance.
|
|
Using the VisualStudio.NET™ Integrated Development Environment (IDE), designers
have direct access to InSite Web Services. Predefined templates, intelligent Web
controls, style sheets, and a complete field directory make it possible to “drag-and-drop”
functioning elements directly onto a screen form, accelerating its modification
and creation.
|
| |
|
| <top> |
| |
|
Designed specifically for use in global, distributed enterprises, InSite provides a comprehensive set of features to support multiple languages and time zones. Key internationalization features include GMT and local date and time stamps, support for multiple simultaneous user interface languages, user-defined labels, and double-byte character sets through the use of database tables that store labels in Unicode format. |
| |
| <top> |
| |
|  |

|
|
InSite security features are integrated with Windows Active Directory ™ services,
giving administrators a familiar interface for managing system access. Key user-
and group-level security options include: single log-on, user authentication, electronic
signature validation, function-level access to individual data entities, and role-based
configuration that complies fully with the FDA regulation 21 CFR Part 11 for electronic
signatures.
|
| |
|
| |
| <top> |
| |
|
|
|
|
|
|
|
 |
|