%@ Language=VBScript %> <% Option Explicit dim DatabaseConnection,DataCommand,SQLCommandText,action dim strUID action = "" strUID=Request.Form("uid") 'Create database connection Call MakeConnection if(Request.QueryString("action") = "")then if(Request.Form("action") <> "")then action = Trim(Request.Form("action")) end if else action = Trim(Request.QueryString("action")) end if 'Database related procedures Sub MakeConnection set DatabaseConnection = Server.CreateObject("ADODB.Connection") DatabaseConnection.Open "Provider=Microsoft.Jet.OLEDB.4.0;Persist Security Info=False;Data Source=" & server.MapPath("argisoft.mdb") 'DatabaseConnection.Open "DSN=argi;pwd=argi" DatabaseConnection.CursorLocation = 3 End Sub Sub CloseConnection databaseconnection.Close End Sub if(action = "Login")then 'if data exists in login master Set DataCommand = Server.CreateObject("ADODB.Recordset") SQLCommandText="" SQLCommandText="select * from argi_login where uid='" & trim(request.form("uid")) &"'" DataCommand.Open SQLCommandText,DatabaseConnection,1,2 if DataCommand.recordcount>=1 then 'password checking if DataCommand("password")<>request.form("password") then session("status")="Invalid Login Information" else '-------Redirect to main index file---- session("argi_rights")=DataCommand("rights") session("firstname")=DataCommand("FirstName") session("surname")=DataCommand("SurName") session("MailerAddress")=DataCommand("EmailID") Response.Redirect "/adminpanel/menu1.html" end if else session("status")="Invalid Login Information" end if end if Set Session("FSO") = CreateObject("Scripting.FileSystemObject") Session("n")=0 Session.Timeout=1 %>
|
|
|
What
is FMEA ?
FMEA's basic idea is to spot risks and to initiate dedicated efforts to control or minimize risks. FMEA Failure Mode and Effects Analysis is an easy to use and yet powerful pro-active engineering quality method that helps you to identify and counter weak points in the early conception phase of products and processes. The structured approach makes it easy to use and even for non-specialist a valuable tool. The benefits obtained encompass by large the investments in time and resources to execute the analysis. FMEA is a systematic analysis of potential failure modes aimed at preventing failures. This is intended to be a preventative action process carried out before implementing new or changes in products or processes. An effective FMEA identifies corrective actions required to prevent failures from reaching the customer and to assure the highest possible yield, quality and reliability. In semiconductor device design and manufacturing, it is common to perform different types of FMEA. These can be divided into two primary categories: product related and process related. These are often called Design FMEA and Process FMEA and they are often further subdivided to focus on specific areas of product or process development. The main purpose of an FMEA is: To identify possible failure modes that could occur in the design or manufacturing of a product.
An FMEA is a two-phase process. First the potential failure modes and corrective actions are identified. Then after the corrective actions are implemented, the product or process is re-evaluated to determine if the result is acceptable. This is best accomplished with a cross-functional team with members from all affected work groups (e.g. Marketing, Engineering, Manufacturing, Test, QRA, etc.)
Benefits of FMEA An FMEA provides benefits to both the manufacturer and the customer. Some of these benefits include:
Documenting an FMEA This preventative action process provides a methodical approach to study the cause and effect of potential failures. The form below (Fig. 1) is used to document the process.
The Process/Product Description or Purpose should be clearly defined. This may be broken down into sub-processes with each being considered separately. Potential Failure Modes lists the different ways the process might fail to meet the process requirements or design intent. The Potential Effect(s) of Failure is how the customer perceives the failure. The “customer” includes subsequent design or manufacturing operations and/or the end customer. Each of the Failure Modes and Effects is assigned a Severity (SEV) value and Classification (CLASS). How a failure could occur should be described in terms of something that can be corrected or controlled and listed under Potential Causes/Mechanisms of Failures. The probability that a given cause or mechanism that might occur is assigned a numeric value in OCC. Current Design/Process Control Prevention/Detection describes any controls that can prevent or detect each of the failure mechanisms. The probability that each control will effectively detect the failure is assigned a numeric value in DET. The Risk Priority Number (RPN) is the product of Severity, Occurrence and Detection. These are assessed and engineering judgment is used to determine if the risk is acceptable. Recommended Actions are developed to reduce the RPN with priority given to the highest RPN values and customer defined specific characteristics. Once the actions are implemented, the Severity, Occurrence and Detection values are reassessed, and a new RPN is calculated. This process continues until the risk level is acceptable. An FMEA is a living document that should be reviewed and updated periodically. Any change in design, process or use of the product should be updated in the FMEA. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
© ArgiSoft Sdn. Bhd.
|