|
OPS Systems, Telecation, Aspen, Conifer, Lab Cal, Laboratory Information Management Systems, LIMS, Oracle, MS SQL, sample scheduling, sample tracking, chain of custody, interfaces, reporting, training, support, consulting, quality control, databases, software |
|
|||
|
Telecation's decisions regarding hardware, operating systems and database platforms are based on a variety of criteria. Chief among them is the notion that our platform choices should improve rather than hamper the customer's position relative to value and risk, and that they should not impose unnecessary constraints or disruption to the customer's business. This means that to the extent possible we have engineered our products to be platform independent. Aspen LIMS adheres to technology standards while at the same time it avoids brand dependencies. By taking this approach, we believe we have given our customers the opportunity to make their own decisions with reagards to their technology choices. The Aspen LIMS Client runs on any contemporary (32-bit) MS Windows variant. Even within a given operating system or database family, our product is not necessarily reliant on a specific revision or point release level. This puts us in an ideal position to meet our customer's requirements, regardless of their corporate standards, without the added technical and administrative overhead imposed by multiple "products". Development of Aspen LIMS uses a fully documented Life-Cycle development methodology. Telecation's Quality System consists of Standard Operating Procedures (SOPs) governing the entire development life cycle and on-line systems that control and document all software changes. The Quality System is continuously being improved and is audited extensively by our customers and our internal staff. Aspen LIMS is extensively tested prior to each software release. Formal Test Plans and Scripts are utilized. Telecation is open to audits by any customer or regulatory agency, and all Quality System documentation is available for inspection and review. Security: Users of Aspen LIMS are not required to have individual database accounts. The database is only accessed by the LIMS application and the database account information is set up in an encrypted configuration file that is not accessible to users. In order to access Aspen LIMS, users must present credentials and be authenticated. Each user has a unique account within the system that tracks demographic information as well as which data groups and functional privileges can be accessed. Aspen LIMS gives you the ability to meet changing customer requirements and specifications quickly and cost-effectively. Aspen enables you to maintain visibility of all operations, enhancing your ability to protect product quality and deliver concise information to your customers, suppliers and other business partners. Deployment Options: Aspen LIMS may be deployed in one of several ways:
Aspen Enterprise 5.5 has n-tier architecture. The architecture separates applications into three main layers: the client tier, the application business rules tier, and the database tier. The flexible nature of Aspen's design allows customers to install a solution that meets the specific needs of their laboratory and processing environment.
|
|