There are different types of Plant Maintenance :-
Maintenance systems can be grouped into 5 major groups:
1.Operator Maintenance
2.Breakdown Maintenance
3.Scheduled Maintenance
4.Planned Maintenance
5.Preventive Maintenance
The purpose of maintenance is to make available for production purpose, machinery and equipment to fulfill their technological functions as specified and economically which means that the output quality and quantity from each machine or equipment will conform to specified purposes.
Tuesday, January 19, 2010
Performance tuning is the improvement of system performance. This is typically a computer application, but the same methods can be applied to economic markets, bureaucracies or other complex systems. The motivation for such activity is called a performance problem, which can be real or anticipated. Most systems will respond to increased load with some degree of decreasing performance.
A system's ability to accept higher load is called scalability, and modifying a system to handle a higher load is synonymous to performance tuning.
• Systematic tuning follows these steps:
1. Assess the problem and establish numeric values that categorize acceptable behavior.
2. Measure the performance of the system before modification.
3. Identify the part of the system that is critical for improving the performance. This is called the bottleneck.
4. Modify that part of the system to remove the bottleneck.
5. Measure the performance of the system after modification.
This is an instance of the measure-evaluate-improve-learn cycle from quality assurance.
A performance problem may be identified by slow or unresponsive systems. This usually occurs because high system loading, causing some part of the system to reach a limit in its ability to respond. This limit within the system is referred to as a bottleneck.
A handful of techniques are used to improve performance. Among them are code optimization, load balancing, caching strategy, and distributed computing, and self-tuning.
The topics covered in this are:-
1. Performance analysis
2. Performance engineering
3. Code optimization
4. Caching strategy
5. Load balancing
6. Distributed computing
7. Self-tuning
8. Bottlenecks
A system's ability to accept higher load is called scalability, and modifying a system to handle a higher load is synonymous to performance tuning.
• Systematic tuning follows these steps:
1. Assess the problem and establish numeric values that categorize acceptable behavior.
2. Measure the performance of the system before modification.
3. Identify the part of the system that is critical for improving the performance. This is called the bottleneck.
4. Modify that part of the system to remove the bottleneck.
5. Measure the performance of the system after modification.
This is an instance of the measure-evaluate-improve-learn cycle from quality assurance.
A performance problem may be identified by slow or unresponsive systems. This usually occurs because high system loading, causing some part of the system to reach a limit in its ability to respond. This limit within the system is referred to as a bottleneck.
A handful of techniques are used to improve performance. Among them are code optimization, load balancing, caching strategy, and distributed computing, and self-tuning.
The topics covered in this are:-
1. Performance analysis
2. Performance engineering
3. Code optimization
4. Caching strategy
5. Load balancing
6. Distributed computing
7. Self-tuning
8. Bottlenecks
Document management system
A document management system (DMS) is a computer system (or set of computer programs) used to track and store electronic documents and/or images of paper documents. The term has some overlap with the concepts of content management systems. It is often viewed as a component of enterprise content management (ECM) systems and related to digital asset management, document imaging, workflow systems and records management systems.
Overview
In the broadest sense, document management systems can range from a shoebox all the way to an enterprise content management system. There are several common issues that are involved in managing documents, whether the system is an informal, ad-hoc, paper-based method for one person or if it is a formal, structured, computer enhanced system for many people across multiple offices.
Location
Where will documents be stored? Where will people need to go to access documents? Physical journeys to filing cabinets and file rooms are analogous to the onscreen navigation required to use a document management system.
Filing
How will documents be filed? What methods will be used to organize or index the documents to assist in later retrieval? Document management systems will typically use a database to store metadata about documents and a File System to store the actual physical files.
Retrieval
How will documents be found? Typically, retrieval encompasses both browsing through documents and searching for specific information. What kind of information about documents are indexed for rapid retrieval?
Security
How will documents be kept secure? How will unauthorized personnel be prevented from reading, modifying or destroying documents?
Disaster recovery
How can documents be recovered in case of destruction from fires, floods or natural disasters?
Retention period
How long should documents be kept, i.e. retained? As organizations grow and regulations increase, informal guidelines for keeping various types of documents give way to more formal records management practices.
Archiving
How can documents be preserved for future readability?
Distribution
How can documents be available to the people that need them?
Workflow
If documents need to pass from one person to another, what are the rules for how their work should flow?
Creation
How are documents created? This question becomes important when multiple people need to collaborate, and the logistics of version control and authoring arise.
Authenticity
Is there a way to vouch for the authenticity of a document?
Traceability
When, where and by whom are documents created, modified, published and stored?
Functions of DMS
Indexing
Storing
Structuring
Versioning
Audit Trail
Document Security
Retrieval
Document Control
Adhering to Compliance
Overview
In the broadest sense, document management systems can range from a shoebox all the way to an enterprise content management system. There are several common issues that are involved in managing documents, whether the system is an informal, ad-hoc, paper-based method for one person or if it is a formal, structured, computer enhanced system for many people across multiple offices.
Location
Where will documents be stored? Where will people need to go to access documents? Physical journeys to filing cabinets and file rooms are analogous to the onscreen navigation required to use a document management system.
Filing
How will documents be filed? What methods will be used to organize or index the documents to assist in later retrieval? Document management systems will typically use a database to store metadata about documents and a File System to store the actual physical files.
Retrieval
How will documents be found? Typically, retrieval encompasses both browsing through documents and searching for specific information. What kind of information about documents are indexed for rapid retrieval?
Security
How will documents be kept secure? How will unauthorized personnel be prevented from reading, modifying or destroying documents?
Disaster recovery
How can documents be recovered in case of destruction from fires, floods or natural disasters?
Retention period
How long should documents be kept, i.e. retained? As organizations grow and regulations increase, informal guidelines for keeping various types of documents give way to more formal records management practices.
Archiving
How can documents be preserved for future readability?
Distribution
How can documents be available to the people that need them?
Workflow
If documents need to pass from one person to another, what are the rules for how their work should flow?
Creation
How are documents created? This question becomes important when multiple people need to collaborate, and the logistics of version control and authoring arise.
Authenticity
Is there a way to vouch for the authenticity of a document?
Traceability
When, where and by whom are documents created, modified, published and stored?
Functions of DMS
Indexing
Storing
Structuring
Versioning
Audit Trail
Document Security
Retrieval
Document Control
Adhering to Compliance
Wednesday, November 4, 2009
Friday, October 30, 2009
Tips on optimizing primary index in Axapta
Primary index plays an important role in gaining optimum performance in Axapta. The Primary Index of a table is the main index that is used to uniquely identify records in it. No duplicated values are allowed in this index. When caching records, primary index is used as the caching key if it exists.
When you designing a table's primary index, follow these rules:
1.Keep the "width" of your indexes as narrow as possible. This reduces the size of the index and reduces the number of disk I/O reads required to read the index, boosting performance.
2.If possible, try to create indexes on columns of Integer data type instead of string. Integer values have less overhead than string values.
3.Don't use Real data types for primary keys, as they add unnecessary overhead and can hurt performance.
4.Indexes on narrow columns are preferable to indexes on wide columns. The narrower the index, the more entries SQL Server can fit on a data page, which in turn reduces the amount of I/O required when accessing the data.
5.Reduce the size of the index, thus decreasing read I/O during the join process, and increasing overall performance.
When you designing a table's primary index, follow these rules:
1.Keep the "width" of your indexes as narrow as possible. This reduces the size of the index and reduces the number of disk I/O reads required to read the index, boosting performance.
2.If possible, try to create indexes on columns of Integer data type instead of string. Integer values have less overhead than string values.
3.Don't use Real data types for primary keys, as they add unnecessary overhead and can hurt performance.
4.Indexes on narrow columns are preferable to indexes on wide columns. The narrower the index, the more entries SQL Server can fit on a data page, which in turn reduces the amount of I/O required when accessing the data.
5.Reduce the size of the index, thus decreasing read I/O during the join process, and increasing overall performance.
Wednesday, October 28, 2009
AX 2009 Workflows:
Workflow - "Machine readible code for a business process"
-Feature of Base AX 2009
-Workflow components reside on a Web Server
-Utilizes the Windows orkflow Foundation (.NET 3.0)
-Utilizes the AX Batch framework
-Requires AD User for Workflow
-Requires exclusive site on IIS to function
-The Workflow components on the Web server use the .NET BC to communicate with the AOS using Workflow system account(existing AX user).
Setup (Steps):-
-Setup AD User for Workflow Account & configure in AX
-Setup & Configure IIS on Web Server
-Setup Workflow Component using AX installation option
-Run the Workflow Infrastructure Configuration Wizard {Batch Jobs, Workflow site}
-Configure the Workflow in AX
Workflow Objects:
Workflow templates:
Workflow templates capture information about workflow categories , what business document the workflow will operate over, what workflow elements (Tasks and Approvals) are required in the workflow configuration, which application event handlers will handle the events that are raised as the workflow executes etc.The first step in creating a workflow is to add a workflow Template. A Workflow Template can be said to be the metadata A workflow template provides information on:
• Which workflow document to use.
• Tasks and approvals that can be configured by the user.
• Workflow categories used for assigning a workflow template to a specific module.
Workflow category:
The workflow category determines whether a workflow template is available in a specific module. After a workflow
category is created, it is possible bind the workflow category to a workflow template.
Workflow Configuration:
A Workflow Configuration is bound to a single Workflow Template, and there can be multiple Workflow Configurations
for the same Workflow Template. Only a single Workflow Configuration for each WorkflowTemplate can be the default WorkflowConfiguration. The Workflow Configuration captures what tasks will be executed, who the tasks are assigned
to.
Workflow Query:
Dynamics AX workflow uses a query to set up conditions for a workflow. The query identifies which data is available to workflow users. Queries are bound to Workflow templates. Once the query is created, a Workflow class needs to be created which contains the query name & any calculated fields.
Workflow Tasks:
AX workflow tasks are used to track documents or tasks from the start to the end of a work process. A workflow may contain one or many tasks. Each task contains one step.
Workflow Approvals:
Workflow Approvals are used to track status of Workflow documents. The fixed outcomes are ‘Approve’, ‘Reject’, or ‘Request Change’.
After you create a task, approval, or outcome in a AX workflow, it must be added to a menu item. The end-user can then start the task or approval using the menu item as a part of the workflow process.
Workflow can be activated throughout the various lifecycle stages of a business document: Create, Update, Delete, Post. The Workflow runtime will execute the Workflow and assign Tasks to users. Users interact with theWorkflow through Alerts/Workflow Tasks, from where they can take action (Approve, Reject) or they can navigate to the business document and view all details before taking the workflow action.
-Feature of Base AX 2009
-Workflow components reside on a Web Server
-Utilizes the Windows orkflow Foundation (.NET 3.0)
-Utilizes the AX Batch framework
-Requires AD User for Workflow
-Requires exclusive site on IIS to function
-The Workflow components on the Web server use the .NET BC to communicate with the AOS using Workflow system account(existing AX user).
Setup (Steps):-
-Setup AD User for Workflow Account & configure in AX
-Setup & Configure IIS on Web Server
-Setup Workflow Component using AX installation option
-Run the Workflow Infrastructure Configuration Wizard {Batch Jobs, Workflow site}
-Configure the Workflow in AX
Workflow Objects:
Workflow templates:
Workflow templates capture information about workflow categories , what business document the workflow will operate over, what workflow elements (Tasks and Approvals) are required in the workflow configuration, which application event handlers will handle the events that are raised as the workflow executes etc.The first step in creating a workflow is to add a workflow Template. A Workflow Template can be said to be the metadata A workflow template provides information on:
• Which workflow document to use.
• Tasks and approvals that can be configured by the user.
• Workflow categories used for assigning a workflow template to a specific module.
Workflow category:
The workflow category determines whether a workflow template is available in a specific module. After a workflow
category is created, it is possible bind the workflow category to a workflow template.
Workflow Configuration:
A Workflow Configuration is bound to a single Workflow Template, and there can be multiple Workflow Configurations
for the same Workflow Template. Only a single Workflow Configuration for each WorkflowTemplate can be the default WorkflowConfiguration. The Workflow Configuration captures what tasks will be executed, who the tasks are assigned
to.
Workflow Query:
Dynamics AX workflow uses a query to set up conditions for a workflow. The query identifies which data is available to workflow users. Queries are bound to Workflow templates. Once the query is created, a Workflow class needs to be created which contains the query name & any calculated fields.
Workflow Tasks:
AX workflow tasks are used to track documents or tasks from the start to the end of a work process. A workflow may contain one or many tasks. Each task contains one step.
Workflow Approvals:
Workflow Approvals are used to track status of Workflow documents. The fixed outcomes are ‘Approve’, ‘Reject’, or ‘Request Change’.
After you create a task, approval, or outcome in a AX workflow, it must be added to a menu item. The end-user can then start the task or approval using the menu item as a part of the workflow process.
Workflow can be activated throughout the various lifecycle stages of a business document: Create, Update, Delete, Post. The Workflow runtime will execute the Workflow and assign Tasks to users. Users interact with theWorkflow through Alerts/Workflow Tasks, from where they can take action (Approve, Reject) or they can navigate to the business document and view all details before taking the workflow action.
What's New in Microsoft Dynamics AX 2009 for Developers
The following are the Development features that are available in Microsoft Dynamics AX 2009:-
• Layers
• Workflow
• Business Connector
• Development Best Practice Checks
• Version Control System Integration
• XML Documentation
• Enterprise Portal
• Reporting Tools for Microsoft Visual Studio
• Reverse Engineering Tool
• Navigation Pages
• Queries and Views
• Time Zone Support
• Composite Query
• Cross-Company Support
• X++ SQL Enhancements
• X++ Enhancements
• Debug a Batch that Runs on the AOS
• Update Cross-reference by Using AT.exe
• E-signature Subsystem Support
• Application Integration Framework
• MorphX
• Business Intelligence
• Documentation Changes
• Layers
• Workflow
• Business Connector
• Development Best Practice Checks
• Version Control System Integration
• XML Documentation
• Enterprise Portal
• Reporting Tools for Microsoft Visual Studio
• Reverse Engineering Tool
• Navigation Pages
• Queries and Views
• Time Zone Support
• Composite Query
• Cross-Company Support
• X++ SQL Enhancements
• X++ Enhancements
• Debug a Batch that Runs on the AOS
• Update Cross-reference by Using AT.exe
• E-signature Subsystem Support
• Application Integration Framework
• MorphX
• Business Intelligence
• Documentation Changes
Subscribe to:
Posts (Atom)
