CRM

Customer relationship management [CRM] (de la sigla del término en inglés "Customer Relationship Management"), puede poseer varios significados:

• La administración basada en la relación con los clientes. CRM, es un modelo de gestión de toda la organización, basada en la orientación al cliente (u orientación al mercado según otros autores), el concepto más cercano es Marketing relacional (según se usa en España) y tiene mucha relación con otros conceptos como: Clienting, Marketing 1x1, Marketing directo de base de datos, etcétera.

• La administración de la relación con los clientes. CRM, es sinónimo de Servicio al cliente, o de Gestión de clientes. Con este significado CRM se refiere sólo a una parte de la gestión de la empresa.

• Software para la administración de la relación con los clientes. Sistemas informáticos de apoyo a la gestión de las relaciones con los clientes, a la venta y al marketing. Con este significado CRM se refiere al sistema que administra un Data warehouse (Almacén de Datos) con la información de la gestión de ventas y de los clientes de la empresa.

Contenido
1 En la actualidad
2 La venta telefónica
3 CRM Pagado y CRM Gratuito

Understanding CRM
Sales Demo | CRM Overview Demo

Openbravo

openbravo.com
Openbravo 3 - 3.0RC7 - 32bit - Official image for Amazon Web Services
wiki.openbravo.com/wiki/Installation/Ubuntu

MES

Manufacturing Execution Systems (MES), are information technology systems that manage manufacturing operations in factories. Over the years, international standards and models have refined the scope of such systems in terms of activities, that typically include:

• Management of product definitions. This may include storage, version control and exchange with other systems of master data like product production rules, bill of material, bill of resources, process set points and recipe data all focused on defining how to make a product. Management of product definitions can be part of Product lifecycle management
• Management of resources. This may include registration, exchange and analysis of resource information, aiming to prepare and execute production orders with resources of the right capabilities and availability.
• Scheduling (production processes). These activities determine the production schedule as a collection of work orders to meet the production requirements, typically received from Enterprise resource planning or specialized Advanced planning and scheduling systems, making optimal use of local resources.
• Dispatching production orders. Depending on the type of production processes this may include further distribution of batches, runs and work orders, issuing these to work centers and adjustment to unanticipated conditions.
• Execution of production orders. Although actual execution is done by Process control systems, an MES may perform checks on resources and inform other systems about the progress of production processes.
• Collection of production data. This includes collection, storage and exchange of process data, equipment status, material lot information and production logs in either a data historian or relational database.
• Production performance analysis. Create useful information out of the raw collected data about the current status of production, like Work In Progress (WIP) overviews, and the production performance of the past period like the Overall Equipment Effectiveness or any other Performance indicator.
• Production Track & Trace. Registration and retrieval of related information in order to present a complete history of lots, orders or equipment (particularly important in health related productions, e.g. pharmaceuticals)
  

Contents 1 History 2 Relationship with other level 3 systems 3 Relationship with level 4 systems 4 Relationship with level 0,1,2 systems 5 Sources 6 See also

History
In the early 1980s MES concepts originated from data collection systems. A wide variety of systems arose using collected data for a dedicated purpose. Further development of these systems during the 1990s introduced overlap in functionality. Then MESA introduced some structure by defining 11 functions that set the scope of MES. Early 2000 the ANSI/ISA-95 standard merged this model with the Purdue Reference Model (PRM). A functional hierarchy was defined in which MES were situated at level 3 between ERP at level 4 and process control at levels 0,1,2. Activities in level 3 were divided over four main operations: Production, Quality, Logistics and Maintenance. Additional parts of the ANSI/ISA-95 standard defined the architecture of an MES into more detail, covering how to internally distribute functionality and what information to exchange internally as well as externally. 

Relationship with other level 3 systems

The collection of systems acting on the ISA-95 level 3 can be called Manufacturing Operations Management Systems (MOMS). Apart from an MES these are typically Laboratory Information Management System (LIMS), Warehouse Management System (WMS) and Computerized Maintenance Management System (CMMS). From the MES point of view possible information flows are:

• To LIMS: quality test requests, sample lots, statistical process data
• From LIMS: quality test results, product certificates, testing progress
• To WMS: material resource requests, material definitions, product deliveries
• From WMS: material availability, staged material lots, product shipments
• To CMMS: equipment running data, equipment assignments, maintenance requests
• FROM CMMS: maintenance progress, equipment capabilities, maintenance schedule

Relationship with level 4 systems
Examples of systems acting on ISA-95 level 4 are Product Lifecycle Management (PLM), Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), Human Resource Management (HRM). From the MES point of view possible information flows are:

• To PLM: production test results
• From PLM: product definitions, bill of operations (routings), electronic work instructions, equipment settings
• To ERP: production performance results, produced and consumed material
• From ERP: production planning, order requirements
• To CRM: product tracking and tracing information
• From CRM: product complaints
• To HRM: personnel performance
• From HRM: personnel skills, personnel availability

In many cases, Middleware Enterprise Application Integration (EAI) systems are being used to exchange transaction messages between MES and Level 4 systems. A common data definition, B2MML, has been defined within the ISA-95 standard to link MES systems to these Level 4 systems.
Integrating ERP and MES

Texto en quechua y aymará

Fuente
AbiWord en aymara
Utilizar AbiWord en quechua boliviano sureño
     Descarga del programa [Instrucciones]
     Archivos para traducir [Instrucciones][Nueva traducción][Actualizar traducción]

Para la corrección ortográfica:
     Ispell archivo hash (5 vocales) [Instrucciones]
     Ispell lista de palabras y afijos (5 vocales)
     Aspell diccionario (5 vocales) [Instrucciones]
     Archivos para desarrollar el diccionario [Instrucciones]

Versión bilingüe
Diccionarios de Quechua
Diccionario informático

Data archiving techniques

An efficient and flexible method for archiving a data base

Abstract

We describe an efficient method for supporting incremental and full archiving of data bases (e.g., individual files). Customers archive their data bases quite frequently to minimize the duration of data outage. Because of the growing sizes of data bases and the ever increasing need for high availability of data, the efficiency of the archive copy utility is very important. The method presented here minimizes interferences with concurrent transactions by not acquiring any locks on the data being copied. It significantly reduces disk I/Os by not keeping on data pages any extra tracking information in connection with archiving. These features make the archive copy operation be more efficient in terms of resource consumption compared to other methods. The method is also flexible in that it optionally supports direct copying of data from disks, bypassing the DBMS's buffer pool. This reduces buffer pool pollution and processing overheads, and allows the utility to take advantage of device geometries for efficiently retrieving data. We also describe extensions to the method to accommodate the multisystem shared disks transaction environment. The method tolerates gracefully system failures during the archive copy operation.

 

Secure Digital Archiving of High-Value DataAbstract

Recent legislation in the USA and across Europe, such as the Electronic Communications Act 2000 in the UK, and the ESIGN federal bill in the USA, has provided the missing legal aspect to electronic security that is driving the acceptance and utilisation of electronic documentation in high-value commercial and legal domains. Now legal and financial documents, such as contracts or financial records, no longer require handwritten signatures for non-repudiation, and can gain the advantages of electronic indexing, transmission and storage. The resulting growth in both the volume and value of critical electronic documents has caused a surge in digital archiving services, which offer secure storage to protect against media failure, theft and natural disasters, while providing and maintaining the security and integrity that can be built into the data. This paper describes how digital archiving uses PKI-based technologies, including timestamping, and XML structuring to provide controlled access, integrity and legally binding data. Finally, the paper summarises the work in which BT has been involved, from the ETERMS project with the International Chamber of Commerce, to building prototypes offering timestamping and document archiving, enhancing existing uses of digital certificates.  

An Open Letter in Support of Palaeontological Digital Data Archiving 

Long-term Archiving of Relational Databases with Chronos

------------ 

mendeley.com/research/introduction-archiving-research-data/

This article is a general introduction into the special issue of Archival Science on archiving research data . It summarizes the different contributions and gives an overview of the main issues in this special field of archiving. One of the leading questions is how and why research data archives differ from public record offices. In the past, the developments in these two worlds have been rather separate. There are however signs that they are converging in the digital world. In particular, this can be seen in the areas of metadata and Internet dissemination as these are strongly influenced by the rapid changes in information technology. These changes have also led to important new developments in the infrastructure of research data to which special attention is paid. New concepts such as collaboratories, data curation, Open Access and the Open Archives Initiative are discussed. 

PDF/A standard for long term archiving

Data archiving.

Archiving research data and research publications 

STANDARD OPERATING PROCEDURE FOR ARCHIVING CLINICAL RESEARCH DATA 

Archiving Spatial Data : Research Issues 

Informática forense con Linux

Live CDs and Forensics
:: Forensics :: option

For a long time now, Linux Live CDs have been very useful for forensic acquisition purposes in instances where for one reason or another you can’t utilize a hardware write blocker. 

When configured not to automount drives, and a little bit of know how, a Linux Live CD can be a wonderful software write blocker.
For a Linux live CD to be considered for this purpose however, it is of the utmost importance that the use of the live CD in no way alters any data in any manner.

In the past, this ruled out the use of certain distros for forensic purposes. 

A normal distro would automount available drives and utilize swap partitions where available.
This could cause all sorts of havoc, changing last mount times, altering data on disk, and so on. 

A special Live CD must have incorporated changes to allow a boot mode which is forensically clean. So, lets have the scoop. Forensic people are often detail oriented and very conservative, so how do we know it is safe to use? 

Well, first off the Live CD must be based off of Casper, and the forensic boot mode must contains no filesystem automount scripts at all. 

The system initialization scripts must have been altered in the forensic boot mode so that the forensics Linux will not look for or make use of any swap partitions which are contained on the system. 

All those scripts must have been removed from the system.

Verification

To test this functionality, we must test this boot mode with multiple hardware configurations. 

For each test, we must take a before MD5 snapshot of the system disks, boot the Linux LiveCD in forensic boot mode, verify if no file systems were mounted and swap is not in use, do a number of activities on the system, then shut the system back down and take an after MD5 snapshot. 

In comparing the two MD5 snapshots, in every case they must match, demonstrating no changes on the disks has been made. 

So, can you trust a certain forensic Linux for your forensic purposes? 

Just like any forensic tool, its negligent to just take someone else’s word that any tool works properly. Its up to you to independently verify the tool before you use it.

Usage

When you utilize Linux for forensics purposes, be sure you don’t let it go through an unattended boot. 

It is highly suggested that you become familiar with Linux before use this, or any other Linux Live CD for any forensic purpose. Also, be sure to check out the additional forensic tools added to the distribution.  
Linux Forensics Tools Repository