View source for 42Q-MES0135-C Rapid IIoT Work Instruction


<small>[[42Q_Cloud-Based_MES/MOMS|42Q Home]] > [[IIoT|IIoT]]&nbsp;>&nbsp;42Q Rapid IIot</small>

&nbsp;

&nbsp;
<center>'''IIoT'''</center> <center>'''42Q Rapid IIot'''</center> <center>'''Version MES 15.70'''</center> 
&nbsp;
<center>&nbsp;</center> 
&nbsp;

&nbsp;

= <span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT"><span class="mw-headline" id="42Q_Rapid_IIoT">42Q Rapid IIoT</span></span></span></span></span></span></span></span></span> =

<span id="docs-internal-guid-8d65a8ea-4bf0-e533-b380-1f81566e2f8a">42Q's Rapid IIoT solution&nbsp;accurately captures raw data from the shop floor (sensor devices and machinery), and inserts that data into business intelligence software, MESWeb, or 42Q SPC, where reports such as unit history, defect and repair, and SPC charts are generated for self-service analytics.</span>

&nbsp;

== <span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity"><span class="mw-headline" id="Connectivity">Connectivity</span></span></span></span></span></span></span></span></span> ==

Sensor data from the Shop Floor moves to the&nbsp;42Q&nbsp;Cloud through a designated path. The following architectural diagram illustrates&nbsp;the equipment and protocol used to exchange information. &nbsp;

'''Figure 1: 42Q Rapid IIoT System Architecture Diagram'''

[[File:42Q Rapid IIoT System Architecture.png|border|700px|RTENOTITLE]]

&nbsp;

&nbsp;

&nbsp;

== <span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications"><span class="mw-headline" id="Data_Applications">Data Applications</span></span></span></span></span></span></span></span></span> ==

<span id="docs-internal-guid-8d65a8ea-4bf0-e533-b380-1f81566e2f8a">Rapid IIoT enables factories to quickly capture sensor data, and analyze that&nbsp;data to improve productivity and performance. The following sensor-related capabilities are possible through Rapid IIoT's&nbsp;dynamic data exchange.</span>

*<span id="docs-internal-guid-e91dbf02-4bf3-a23b-58aa-ce34965454c8">Collect&nbsp;sensor data from machines (e.g. temperature, pressure, tension).</span> 
*<span id="docs-internal-guid-e91dbf02-4bf3-a23b-58aa-ce34965454c8">Perform&nbsp;SPC analytics on sensor data.</span> 
*<span id="docs-internal-guid-e91dbf02-4bf3-a23b-58aa-ce34965454c8">Generate&nbsp;Out of Control Action Plans (OCAPs) for sensor behavior outside of lower and upper control limits.</span> 
*<span id="docs-internal-guid-e91dbf02-4bf3-a23b-58aa-ce34965454c8">Compile&nbsp;sensor data for self-service analytics.</span> 

&nbsp;

== <span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow"><span class="mw-headline" id="Sensor_Data_Flow">Sensor Data Flow</span></span></span></span></span></span></span></span></span> ==

'''<span class="mw-headline">Figure 2: Data Flow</span>'''

[[File:Sensor Data Flow.png|border|700px|Sensor Data Flow.png]]

&nbsp;

&nbsp;

&nbsp;

== <span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity"><span class="mw-headline" id="IIoT_Connectivity">IIoT Connectivity</span></span></span></span></span></span></span></span></span> ==

'''<span class="mw-headline">Figure 3: Connectivity</span>'''

[[File:IIoT Connectivity.png|border|700px|RTENOTITLE]]

&nbsp;

#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">Sensors capture sensitive measurement data (such as temperature, and humidity).</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">Plants can use a variety of systems to release data from controlled machinery (e.g. reflow ovens).</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">Some standard hardware solutions include: PLCs, DCS, and RTU (see drawing).</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">Sensor data is then transferred to the system’s driver via an OPC (KepServer is one OPC software used by many manufacturers).</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">OPC then sends the information to an IoT plugin that communicates with 42Q’s API.</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">42Q’s API utilizes a Measurement parser to process and store the data.</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">Measurement pushes data to the data analytic tool (SPC, MESWeb, or other third-party data analysis tools such as Tableau or Splunk).</span> 
#<span id="docs-internal-guid-8d65a184-4f90-cfc0-4d14-d872a956b992">Data is analyzed by SPC and/or MESWeb, where reports are generated.</span> 

== <span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites"><span class="mw-headline" id="Configuration_Prerequisites">Configuration Prerequisites</span></span></span></span></span></span></span></span></span> ==

In order to capture sensor data, the following items must be defined:

&nbsp;

*A Generic Part Number ('''PN''') See [[SOP-5-I-MES0011-C_RA1_Part_Maintenance|'''Part Number Maintenance''']]. 
*An '''Attribute''' by '''Process'''. See [[SOP-5-I-MES0003-C_RA1_Attribute_Def_Maintenance|'''Attribute Definition''']].&nbsp; 
*'''SPC '''Monitor (described in this document). 
*Sensor Capture '''Measurement Parser'''&nbsp;(described in this document). 

&nbsp;

'''<u>Note</u>''': The '''Process''' serves an important function by creating a '''context''' for the data being captured. The Process aids technical engineers and administrators in analyzing reports and diagnosing root causes. See also: [[SOP-5-I-MES0069-C_RA1_Statistical_Process_Control|'''SPC''']] and [[SOP-5-I-MES0073-C_RA1_Measurement_3.1|'''Test Integration''']].

= <span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="mw-headline" id=".E2.80.8BIntroduction"><span class="c24 c7">Introduction</span></span></span></span></span></span></span></span></span></span> =

<span class="c5">This document provides complete instructions on how to configure a sensor capture parser that captures&nbsp;data from sensors. Instructions also include how to send that data to other systems, such as&nbsp;SPC or CMMS.&nbsp;</span>

&nbsp;

= <span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home"><span class="mw-headline" id="Home">Home</span></span></span></span></span></span></span></span></span></span></span></span></span> =

<span class="c5">Measurement can be accessed from the 42Q Welcome page. &nbsp;To log in, select a language, enter a valid screen name and password, and click the </span><span class="c7">'''Sign In''' </span><span class="c0">button.</span>

'''Figure 4: Log&nbsp;In'''

[[File:Figure 1- IAM unified login page1.png|700px|42Q Welcome Page.png]]

&nbsp;

<span class="c5">The </span>'''<span class="c7">Parser</span>'''<span class="c5">, </span>'''<span class="c7">Tooling</span>'''<span class="c5">, </span>'''<span class="c7">AutoLog Configuration</span>'''<span class="c5">,</span><span class="c7">&nbsp;'''SPC Integration,''' </span><span class="c5">and</span><span class="c7">&nbsp;'''Recipe Maintenance''' </span><span class="c0">modules are located in the Shop Floor Control menu, within '''Measurement Config'''. To access, navigate to: Shop Floor Control > Configuration > Measurement Config.</span>

'''<span class="c0">Figure 5: Navigation</span>'''

[[File:Figure 5- Navigation.png|RTENOTITLE]]

&nbsp;

<span class="c5">Select the</span><span class="c7">&nbsp;'''Measurement Config'''</span><span class="c0">&nbsp;menu item to display the available modules.</span>

&nbsp;

'''Figure 6: Measurement Config Modules'''

'''[[File:Figure 5 Meas Config.png|border|RTENOTITLE]]'''

<span class="c5"><u>'''Note'''</u>: To return to the menu of the current application suite, click the Return</span><span class="c0">&nbsp;to Menu button.</span>

&nbsp;

'''Figure 7: Return to Menu Icon&nbsp;'''

'''[[File:Figure 6 Return to Menu Icon.png|border|RTENOTITLE]]'''

&nbsp;

&nbsp;

== <span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="mw-headline" id=".E2.80.8BInstance_Selection"><span class="c7 c21">Instance Selection</span></span></span></span></span></span></span></span></span></span></span></span></span></span> ==

<span class="c0">The Measurement Configuration web application is instance-based. All parsers, stations, and any Measurement automated line production-related information constitutes an instance and is stored in a Measurement database. Each instance is set to view one Measurement database. This produces one instance per Measurement installation.&nbsp;</span><span class="c5">Generally, Measurement is configured to have one installation per site. It is also common to have a separate instance in the same site when there are medical operations.</span>

<span class="c5">To view available instances in the Measurement application, select the</span><span class="c7">&nbsp;Instances</span><span class="c0">&nbsp;drop-down list.</span>

&nbsp;

'''Figure 8: Instance&nbsp;Menu Bar Location'''

[[File:Figure 9 Instances Menu Bar Location.png|RTENOTITLE]]

<span class="c0">A list of instances will display. Instances can be selected in order to update information.</span>

&nbsp;

'''<span class="c0">Figure 9: Select a new Instance</span>'''

'''<span class="c0">[[File:Figure 8 Select a New Instance.png|RTENOTITLE]]</span>'''

&nbsp;

<span class="c0">The instance set displays the screen’s title to help the user identify the current instance.</span>

&nbsp;

'''Figure 10: Instance in Screen Title'''

'''[[File:Figure 7 Instance Menu Bar Location.png|RTENOTITLE]]'''

&nbsp;

= <span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="mw-headline" id=".E2.80.8BSPC_Monitor"><span class="c24 c7">SPC Monitor</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> =

In order for measurement to send data to SPC, engineers must first assign an SPC monitor to receive the data. To '''configure an SPC Monitor''':

#<span class="c5">Navigate to: '''Quality&nbsp;> Reporting > SPC'''.</span> 
#<span class="c5">From the system menu, click the Expand button (+)&nbsp;</span><span class="c5">on the left of Quality to show the menu options.</span> 
#<span class="c5">Select the&nbsp;'''SPC icon'''.</span> 
#<span class="c5">Select Enter to access </span><span class="c0">the SPC monitor list.</span> 

'''Figure 11: SPC Monitor Location'''

[[File:Figure 11- SPC Monitor Location.png|border|RTENOTITLE]]

&nbsp;

<span class="c19 c5">'''Figure 12: Enter SPC Portal'''</span>

[[File:Figure 12- Enter SPC Portal.png|border|RTENOTITLE]]

&nbsp;

<span class="c5">A list of all available Monitors displays on the SPC Home page.</span>

#<span class="c5">Select the Monitor Group by clicking the yellow '''Go''' icon[[File:Go Icon.png|RTENOTITLE]], or create new groups by selecting '''New[[File:Add New Icon.png|RTENOTITLE]]'''.</span> 

&nbsp;

'''<span class="c5">Figure 13: Select Monitor Group List</span>'''

[[File:Figure 34- Monitor Group List Page with Go Icon Highlighted.png|border|800px|RTENOTITLE]]

&nbsp;

&nbsp;

&nbsp;

=== <span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="mw-headline" id=".E2.80.8BCreate_a_New_Monitor"><span class="c19 c5">Create a New Monitor</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ===

#<span class="c5">The Function List displays in an icon format.</span> 
#<span class="c5">Select </span>'''<span class="c7">Monitor Maintenance</span>'''<span class="c0">&nbsp;to open a list of&nbsp;all Monitors available ('''Figure 11''').</span> 

&nbsp;

'''Figure 14: Select Monitor Maintenance from the Function List'''

'''<span class="c5">[[File:Figure 13 Select Monitor Maintenance.png|border|800px|RTENOTITLE]]</span>'''

&nbsp;

'''Figure 15: Monitor List'''

'''[[File:Figure 15- Monitor List.png|border|800px|RTENOTITLE]]'''

&nbsp;
<ol start="3">
<li><span class="c5">To create a new Monitor, click on the green '''+New''' icon. The following form displays:</span></li>
</ol>

&nbsp;

'''<span class="c5">Figure 16: New Monitor Form</span>'''

'''<span class="c5">[[File:Figure 16- New Monitor Form.png|RTENOTITLE]]</span>'''

&nbsp;

&nbsp;

&nbsp;

=== <span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="mw-headline" id="Complete_the_Monitor_Form"><span class="c5">Complete the Monitor Form</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> ===

#<span class="c5">Select a '''Part Number''' from the drop-down, or type it in the Part Number field (value is case sensitive).</span> 
#<span class="c5">Select '''Location'''/'''Process.'''</span> 
#<span class="c5">Select the predefined '''Location'''/'''process''' from the drop-down menu.&nbsp;</span> 

<span class="c5"><u>'''Note'''</u>: Part Number and Process are [[#Configuration_Prerequisites|'''Configuration Prerequisites''']].</span>
<ol start="4">
<li>'''<u>Important Note:</u>'''&nbsp;To create an SPC Monitor&nbsp;fed from&nbsp;sensor data, select [https://42qrpt1.42-q.com/mes_wiki/index.php/SOP-5-I-MES0069-C_RA1_Statistical_Process_Control#Automatic_Collection_via_SPC_API '''Automatic&nbsp;Collection via SPC API'''].</li>
</ol>

&nbsp;

'''Figure 17:&nbsp; Data Collection Strategy'''

'''[[File:Figure17- Automatic Collection via SPC API.png|RTENOTITLE]]'''

&nbsp;
<ol start="6">
<li><span class="c5">Add a '''Characteristics'''/an '''Attribute&nbsp;'''</span><span class="c5">to </span><span class="c5">Monitor.</span></li>
</ol>

<span class="c5"><u>'''Note'''</u>: Attributes are&nbsp;[[#Configuration_Prerequisites|'''Configuration Prerequisites''']].</span>
<ol start="7">
<li><span class="c5">Configure chart parameters as desired:</span></li>
</ol>
<ul style="margin-left: 80px;">
<li>'''<span class="c5">Control Chart Type</span>'''</li>
<li>'''<span class="c5">Chart Rules</span>'''</li>
<li>'''Notification Actions'''</li>
</ul>
<ol start="8">
<li><span class="c5">After all configuration fields are complete,&nbsp;select&nbsp;'''Save'''</span><span class="c5">.</span></li>
<li><span class="c5">The</span><span class="c5">&nbsp;new Monitor is now available in the '''Monitor List''' and ready to receive sensor data.</span></li>
</ol>

&nbsp;

= <span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="mw-headline" id=".E2.80.8BMeasurement_Configuration"><span class="c7 c24">Measurement Configuration</span></span></span></span></span></span></span></span></span></span> =

== <span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="mw-headline" id=".E2.80.8BParser"><span class="c40 c30 c7 c21">Parser</span></span></span></span></span></span></span></span></span></span> ==

=== <span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="mw-headline" id=".E2.80.8B.E2.80.8BCreate_a_New_Parser"><span class="c19 c5">Create a New Parser</span></span></span></span></span></span></span></span></span></span> ===

<span class="c5">To access the Parser module from the main menu, go to:&nbsp;</span>'''<span class="c7">Shop Floor Control</span><span class="c5">&nbsp;> </span><span class="c7">Configuration</span><span class="c5">&nbsp;></span><span class="c7">&nbsp;Meas Config</span>'''<span class="c0">&nbsp;and select the Parser icon.</span>

&nbsp;

'''Figure 18: Create New Parser'''

'''[[File:Figure 17 Create New Parser.png|RTENOTITLE]]'''

&nbsp;

<span class="c5">To create a new sensor capture Parser, click the green '''+New'''&nbsp;icon for the Parser Wizard, located at the top right of the menu bar. This action opens the Parser Wizard.&nbsp;</span>

&nbsp;

'''<span class="c5">Figure 19: Parser Wizard&nbsp;</span>'''

[[File:Figure 18 Parser Wizard.png|RTENOTITLE]]

&nbsp;

&nbsp;

'''Figure 20: Parser Wizard'''

[[File:Parser Wizard 2.jpeg|500px|Parser Wizard 2.jpeg]]

&nbsp;

=== <span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package"><span class="mw-headline" id="Choose_.26_Install_the_Package">Choose & Install the Package</span></span></span></span></span></span></span></span></span> ===

#Select the '''+&nbsp;icon''' [[File:Magnifying Glass Icon.png|RTENOTITLE]]to Choose and Install the Parser Package.&nbsp; 
#This action opens a new screen (see '''Figure 18,''' below). 
#Choose the Sensor Capture Package from the '''drop-down menu''' available on the new screen. 
#This action populates the remaining fields: 
<ul style="margin-left: 80px;">
<li>'''Core Version''':&nbsp;The 4-digit&nbsp;version from the Measurement application this parser was deployed to run.</li>
<li>'''Parser Version''':&nbsp;4-digit version number from this parser assembly file.</li>
<li>'''Import Type''':&nbsp;Informative data to identify the import mechanism the parser uses.</li>
<li>'''Default Workflow''': Technical option set by the developer to identify the parser to run in a default workflow (Import data, Parse to measurement data, send unit information to SFDC, store parametric data, release the file to out folder).</li>
</ul>
<ol start="5">
<li>Select '''Install'''.</li>
</ol>

&nbsp;

'''Figure 21: Install Package'''

'''[[File:Install Package-1526325393800.png|600px|Install Package-1526325393800.png]]'''

&nbsp;
<ol start="5">
</ol>

&nbsp;

=== <span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="mw-headline" id="Package_Tab_Field_Description"><span class="c0">Package Tab Field Description</span></span></span></span></span></span></span></span></span></span> ===

<span class="c0">Once the package is installed, the user is '''redirected''' to the Parser configuration page (Parser Wizard) (See '''Figure''', below). Note that the Package Field is now populated with the newly installed package and the additional '''Channel Tab''' is also available.</span>&nbsp;

Package Field Descriptions are outlined as follows:

*<span class="c7">'''Package''': </span><span class="c5">&nbsp;</span><span class="c0">The system populates this field based on the package installed. It includes the fully qualified name from the parser file, including its extension.</span> 
*<span class="c7">'''Alias''':</span><span class="c0">&nbsp;The alias identifies the parser instance. This field is automatically populated based upon the package installed. Users may optionally change the Alias by deleting the text and entering a new Alias.&nbsp;</span> 
*<span class="c0">'''Customer''': The customer whose products are processed&nbsp;on&nbsp;the automated line connected with sensor activity.</span> 
*<span class="c7">'''Caller''':</span><span class="c0">&nbsp;Set how the parser will process data.</span> 
**<span class="c0">'''API:''' Set the parser to be run from Measurement Core.</span> 
**<span class="c0">'''Service''': Set the Parser to be loaded from another parser.</span>   
*<span class="c7">'''Asynchronous''':</span><span class="c0">&nbsp;Identify if the parser will process multiple serial numbers in parallel on SFDC.</span> 
*<span class="c7">'''Enabled''':</span><span class="c0">&nbsp;Set the parser to run or stop.</span> 
*<span class="c7">'''Logging''': </span><span class="c0">The user can set logging to all, info, or debug information.</span> 
*<span class="c7">'''Backfill''': </span><span class="c0">Select whether or not to load historical data.</span> 
*<span class="c7">'''Inspection Review''': </span><span class="c0">Toggle inspection review on or off.</span> 
*<span class="c7">'''Token''':</span><span class="c0">&nbsp;A unique identifier string associated with a parser instance. This token is automatically generated.</span> 

&nbsp;

'''Figure 22: Sensor Capture Parser Package'''

'''[[File:Figure 20 Sensor Capture Parser Package.png|500px|Sensor Capture Parser Package.png]]'''

&nbsp;

&nbsp;

=== <span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements"><span class="mw-headline" id="Sensor_Capture_Parser_Field_Requirements">Sensor Capture Parser Field Requirements</span></span></span></span></span></span></span></span></span> ===

#For Sensor Capture Parsers, the following Package Fields are required. Refer to '''Figure 19'''&nbsp;(above) for Sensor Capture Configuration Example. 
<ul style="margin-left: 80px;">
<li>'''<span id="docs-internal-guid-0a18bfd3-41a5-07fc-d9b2-289c02a01d0f">Caller</span>:''' Defines if this parser will be called via '''Service''' or '''API'''. For sensor capture, Select '''Service'''.</li>
<li>'''<span id="docs-internal-guid-0a18bfd3-41a5-07fc-d9b2-289c02a01d0f">Enabled</span>''': Defines if this parser will be initially created as enabled or not. There are more configurations to set before enabling it, it should remain '''No.'''</li>
<li>'''<span id="docs-internal-guid-0a18bfd3-41a5-07fc-d9b2-289c02a01d0f">Backfill</span>:'''&nbsp;Select '''No'''.</li>
<li>'''<span id="docs-internal-guid-0a18bfd3-41a5-07fc-d9b2-289c02a01d0f">Inspection Review</span>:'''&nbsp;Select&nbsp;'''No.'''</li>
</ul>
<ol start="2">
<li><span id="docs-internal-guid-0a18bfd3-41a5-07fc-d9b2-289c02a01d0f">Click the</span> '''Next''' button to go to the next screen, or click '''Close''' to abandon changes.</li>
</ol>

&nbsp;

=== <span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab"><span class="mw-headline" id="Channel_Tab">Channel Tab</span></span></span></span></span></span></span></span></span> ===

#<span class="c0">None of the fields in the '''Channel''' tab&nbsp;are required for the Sensor Capture parser.</span> 
#<span class="c7">Select '''Save'''</span><span class="c5">&nbsp;to save the parser and reload the parser list screen. Select&nbsp;</span>'''<span class="c7">Close&nbsp;</span>'''<span class="c5">to abandon changes</span> 
#<span class="c5">Select&nbsp;</span>'''<span class="c7">Back</span>'''<span class="c0">&nbsp;to return to the Package tab.</span> 
#<span class="c0">For more details about Channel&nbsp;Tabs and Parser configuration, refer to [[Test_Integration|Measurement/Test Integration]].</span> 

'''Figure 23: Channel Tab'''

[[File:Figure 21 Channel Tab.png|500px|Channel Tab.png]]

&nbsp;

= <span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="mw-headline" id="Rapid_IIoT_Workflow"><span class="c0">Rapid IIoT Workflow&nbsp;</span></span></span></span></span></span></span></span></span></span> =

#<span class="c0">A parser has a well-defined workflow structure based on inbound processing and outbound information.</span> 
#<span class="c0">Group configurations dictate&nbsp;</span>'''''where payload data will be stored & transferred'''''. 

<span class="c0">[[File:Sesnsor Data Process Flow4.jpeg|1000px|RTENOTITLE]]</span>

&nbsp;

&nbsp;

&nbsp;

&nbsp;

== <span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups"><span class="mw-headline" id="Parser_Configuration_Groups">Parser Configuration Groups</span></span></span></span></span></span></span></span></span> ==

<span class="c0">Configuration Groups allow plants to customize workflows to&nbsp;accommodate production line variances and technical integration requirements.</span>

<span class="c5">The following 4 groups must be configured for sensor parsers to capture data:</span>

*'''<span class="c7">CMMS Configuration</span>''' 
*'''<span class="c7">Sensor Capture</span>''' 
*'''<span class="c7">SPC Configuration</span>''' 
*'''<span class="c7">Tag Attribute Mapping</span>''' 

#Select the '''+ icon''' to the left of the Sensor name. 
#Select the '''notepad icon''' in the Configuration Groups tab&nbsp;(see '''Figure 21''', below). 

&nbsp;

&nbsp;

'''Figure 24: Parser Configuration Groups'''

[[File:Figure 22 Parser Configuration Groups.jpeg|1000px|Figure 22 Parser Configuration Groups.jpeg]]

&nbsp;
<ol start="3">
<li><span class="c5">To add a configuration to each dynamic configuration group/item, expand the group by selecting&nbsp;the '''+ icon'''</span><span class="c0">&nbsp;[[File:Plus Icon.png|RTENOTITLE]] to the left of the group name.</span></li>
</ol>

&nbsp;

'''<span class="c0">Figure 25: Expand To Configure Item</span>'''

'''<span class="c0">[[File:Figure 23 Expand To Configure Item.jpeg|1000px|Figure 23 Expand To Configure Item.jpeg]]</span>'''

&nbsp;
<ol start="4">
<li><span class="c5">To add configuration details, select&nbsp;'''Edit'''&nbsp;[[File:Edit Icon.png|RTENOTITLE]]('''pencil icon''') at the right of the line item.&nbsp;</span></li>
</ol>

&nbsp;

'''<span class="c5">Figure 26: Select Edit Icon</span>'''

'''<span class="c5">[[File:Figure 24 Select Edit Icon.png|1000px|Figure 24 Select Edit Icon.png]]</span>'''

&nbsp;
<ol start="5">
<li><span class="c5">After changing the value, select '''Save''' [[File:Save Icon.png|RTENOTITLE]]&nbsp;to update, or '''Cancel[[File:Cancel Icon.png|RTENOTITLE]]''' &nbsp;to abort the action.</span></li>
</ol>

&nbsp;

'''Figure 27: Save, Cancel, and Delete Icons'''

'''[[File:Figure 25 Save, Cancel, Delete Icons.jpeg|1000px|Figure 25 Save, Cancel, Delete Icons.jpeg]]'''

&nbsp;

&nbsp;

=== <span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="mw-headline" id="CMMS_Configuration"><span class="c54">CMMS Configuration</span><span class="c19 c5">&nbsp;</span></span></span></span></span></span></span></span></span></span> ===

<span class="c0">CMMS configuration defines how the parser will send data to CMMS.</span>

&nbsp;

'''Figure 28: CMMS Configuration Group'''

'''[[File:Figure 26 CMMS Configuration Group.png|1000px|Figure 26 CMMS Configuration Group.png]]'''

&nbsp;

&nbsp;

==== <span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items"><span class="mw-headline" id="CMMS_Configuration_Items">CMMS Configuration Items</span></span></span></span></span></span></span></span></span> ====

*'''<span class="c7">AddDataToCMMS</span>'''<span class="c0">: Define if data will be sent to CMMS or not.</span> 
*'''<span class="c7">SendAllTagsToCMMS</span>'''<span class="c5">: Define if Sensor Capture parser will send all tags received via payload to CMMS or only the ones configured in the </span><span class="c7">TagAttribute</span><span class="c0">&nbsp;item. Select '''False''' to specify a TagAttribute (see '''<u>Note</u>''', below).</span> 
*'''<span class="c7">SiteId</span>'''<span class="c0">: Site identification at CMMS.</span> 
*'''<span class="c7">TagAttribute</span>'''<span class="c5">: Define which tag from the payload will be sent to CMMS. <u>'''NOTE'''</u>: When '''TagAttribute'''&nbsp;mapping is selected, </span>'''<span class="c7">SendAllTagsToCMMS</span>'''<span class="c0">&nbsp;value must&nbsp;be '''FALSE'''.</span> 
*'''<span class="c7">URL</span>'''<span class="c0">: Define the CMMS URL the&nbsp;API will call.</span> 

&nbsp;

=== <span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="mw-headline" id="Sensor_Capture_Configuration"><span class="c54">Sensor Capture</span><span class="c19 c5">&nbsp;Configuration</span></span></span></span></span></span></span></span></span></span> ===

<span class="c5">The Sensor Capture Group defines how the Sensor Capture parser handles data.</span>

#<span class="c5">Select '''Edit'''.</span> 
#<span class="c5">Complete the fields per&nbsp;plant requirements.&nbsp;</span> 

&nbsp;

&nbsp;

==== <span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="mw-headline" id="Sensor_Capture_Configuration_Items"><span class="c5">Sensor Capture Configuration Items</span></span></span></span></span></span></span></span></span></span></span></span> ====

*'''<span class="c7">AddProcessFieldInformation</span>'''<span class="c5">: Defines if parser will send information to the FlexFields attached to the process or not. Select True to utilize Flex Field configuration options.&nbsp;</span> 
*'''<span class="c7">AsyncSaveTransaction</span>'''<span class="c0">: Select '''True''' to store&nbsp;the transaction in parallel to the rest of the processing.</span> 
*'''<span class="c7">CollectStatistics</span>'''<span class="c5">: Defines if system will collect growth statistics related to the database and transaction tables. Default value is </span><span class="c7">FALSE</span><span class="c0">.</span> 
*'''<span class="c7">CreateRawTransactionOnLine</span>'''<span class="c0">: Defines if transactions entering via MES-API sync method (online transaction) are saved. Select TRUE to save MES-API transactions.</span> 
*'''<span class="c7">MaxRecipeOnCache</span>'''<span class="c0">: Defines&nbsp;the Maximum number of Recipes that can be cached.</span> 
*'''<span class="c7">NumberOfTransactionsToProcess</span>'''<span class="c0">: Defines the number of transactions to be retrieved for processing. Default value is 50.</span> 
*'''<span class="c7">OnLineTransaction</span>'''<span class="c0">: Defines if the parser will send values to CMMS and SPC synchronously or not.</span> 
*'''<span class="c7">PartNumber</span>'''<span class="c0">: Defines the generic part number the parser will use.</span> 
*'''<span class="c7">SensorMappingType</span>'''<span class="c0">''':''' Defines the Tag Sensor Capture parser should look for in the station mapping configuration.</span> 
*'''<span class="c7">SleepProcessingType</span>'''<span class="c0">: Defines the amount of time (milliseconds) the parser will wait to start processing the next set of data.&nbsp;&nbsp;</span> 
*'''<span class="c7">TagNameForDevice</span>'''<span class="c5">: Tag name used to locate&nbsp;device information. &nbsp; &nbsp;</span> 

&nbsp;

'''Figure 29: Sensor Capture Configuration Group'''

'''[[File:Figure 27 Sensor Capture Configuration Group.png|800px|Sensor Capture Configuration Group.png]]'''

&nbsp;

&nbsp;

=== <span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="mw-headline" id="SPC_Configuration"><span class="c54">SPC Configuration</span><span class="c19 c5">&nbsp;</span></span></span></span></span></span></span></span></span></span></span> ===

<span class="c5">This configuration section defines how the parser integrates with the API to send&nbsp;data to SPC.</span>

'''<span>Figure 30: SPC Configuration Items</span>'''

[[File:Iiot spcconfig.png|800px|Iiot spcconfig.png]]

&nbsp;

&nbsp;

==== <span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items"><span class="mw-headline" id="SPC_Configuration_Items">SPC Configuration Items</span></span></span></span></span></span></span></span></span></span> ====

*'''<span class="c7">GetAddDataToMonitor</span>'''<span class="c0">: Define the Method used to post data to a given SPC monitor.</span> 
*'''<span class="c7">GetMonitorsMethod</span>'''<span class="c0">''':'''&nbsp;Define the Method used to get the list of monitors available.</span> 
*'''<span class="c7">SendMonitorDataInBatches</span>'''<span class="c0">: Define whether the parser will&nbsp;send data to monitors in batches or not.</span> 
*'''<span class="c7">SPCUri</span>'''<span class="c5">: Define the Base SPC Uri.</span> 

&nbsp;

=== <span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="mw-headline" id="Tag_Attribute_Mapping"><span class="c54">Tag Attribute Mapping</span></span></span></span></span></span></span></span></span></span> ===

<span class="c5">'''Tag Attribute Mapping''' defines the relationship between tags (sent within payloads) and attributes (configured in MES). The Sensor </span><span class="c5">Capture<span style="font-size: 10.8333px;">&nbsp;</span></span><span class="c5">parser uses this configuration to send data to SPC.</span>

&nbsp;

==== <span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements"><span class="mw-headline" id="Tag_Attribute_Mapping_Format_Requirements">Tag Attribute Mapping Format Requirements</span></span></span></span></span></span></span></span></span> ====

[[File:Tag Attribute Mapping Format Requirements2.5.png|RTENOTITLE]]

<span id="docs-internal-guid-560432d8-4be7-d40d-85ed-60c0d860c901">Sensor data from PLCs (Programmed Logic Controls) is sent to 42Q’s API via HTTPS. During original configuration, the Measurement parser generates a token that includes the URL (instance), the process, and the software’s payload. Payload is written in JSON format Text (see below)</span><span>. &nbsp;In this way, the parser is able to locate the information according to the token, URL, and process, then send the data to 42Q’s SPC via 42Q's API.</span>

==== <span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span class="mw-headline" id="JSON_Format"><span>JSON Format</span></span></span></span></span></span></span></span></span></span> ====

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">{</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">"agent_id": "PLC_1",</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">"data_acquisition_ts": “123213213132” ,</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">"measurements": [</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">&nbsp;&nbsp;{</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"id": "sensor_pi.office.temp",</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"value": “74”,</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"quality": "true",</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"timestamp": "213132132132"</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">&nbsp;&nbsp;}</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">]</span>

<span id="docs-internal-guid-560432d8-4bea-e883-6eca-a2f436fef9e6">}</span>

&nbsp;

&nbsp;

&nbsp;

&nbsp;

==== <span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="mw-headline" id="Create_an_Attribute_Mapping"><span class="c5">Create an Attribute Mapping</span></span></span></span></span></span></span></span></span></span></span></span></span> ====

#<span class="c5">Select '''AttributeMapping'''.</span> 
#<span class="c5">Select '''Edit'''.</span> 

&nbsp;

'''Figure 31: Create Attribute Mapping'''

<span style="font-size:larger;">'''[[File:Figure 29 Create an Attribute Mapping.png|800px|Create an Attribute Mapping.png]]'''</span>

&nbsp;
<ol start="3">
<li><span class="c5">A new form displays:&nbsp;'''Item Name: Attribute Mapping.'''</span></li>
</ol>

&nbsp;

'''Figure 32: Item Name: Attribute Mapping Form'''

'''[[File:Item Name Attribute Mapping Form2.jpeg|600px|Item Name Attribute Mapping Form2.jpeg]]'''
<ol start="4">
<li>Complete the fields:</li>
</ol>
<ul style="margin-left: 80px;">
<li><span class="c5">'''Key Field''': Enter the Tag Id (from the payload)</span></li>
<li><span class="c5">'''Value Field''': Enter the Attribute (from MES).</span></li>
</ul>
<ol start="5">
<li><span class="c5">'''Save'''.</span></li>
</ol>

&nbsp;

'''Figure 33: Tag Attribute Mapping Configuration Example (Completed)'''

&nbsp;

[[File:Tag Attribute Mapping Connection to previous configurationFig31.jpeg|800px|RTENOTITLE]]

<span id="docs-internal-guid-6a3c8d59-f1d9-6111-99e1-0b0cfe3602bf">To further explain the movement of data, refer to the figure above. The popup shows the xml for the tag list. Note that the attributes defined in the tag are embedded in the code.</span>

&nbsp;

=== <span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span class="mw-headline" id="Flex_Field_Use_Case"><span>Flex Field Use Case</span></span></span></span></span></span></span></span></span></span></span></span></span> ===

<span id="docs-internal-guid-6c8b018c-f1de-5431-709a-d1d390cf9635">To illustrate how flex fields are applied to a factory floor, consider Shop Floor X. Shop Floor X managers need to measure two different attributes on PCBs as they exit the reflow oven: temperature and humidity. The first image (</span>'''Flex Field Use Case 1''') shows the last parsed values of the flex field.

'''<span id="docs-internal-guid-6c8b018c-f1de-5431-709a-d1d390cf9635">Figure 33a: Flex Field Use Case 1</span>'''

'''<span>[[File:Flex Field Use Case 1.png|border|700px|RTENOTITLE]]</span>'''

#<span id="docs-internal-guid-ab4ed0fb-f1de-c9b6-061f-1f5f2c1cfcf2">Flex Field attributes are mapped to a process in MES and connected to the sensor via the attribute’s tag sent through the payload (see&nbsp;</span>'''Flex Field Use Case 2''','''below).''' 

'''<span id="docs-internal-guid-ab4ed0fb-f1de-c9b6-061f-1f5f2c1cfcf2">Figure 33b: Flex Field Use Case 2</span>'''

'''<span>[[File:Flex Field Mapping 2.png|border|700px|Flex Field Mapping 2.png]]</span>'''
<ol start="2">
<li><span id="docs-internal-guid-a9eac640-f1df-a862-3b43-2c851bd8aa7a">This measurement tag shows the temperature value of 23.9 sent in the payload:</span></li>
</ol>

'''<span id="docs-internal-guid-a9eac640-f1df-a862-3b43-2c851bd8aa7a">Measurement Tag</span>'''

{| dir="ltr" style="width:625px;"
|-
| 
<span id="docs-internal-guid-3aa6e95b-f1e7-05bf-4e17-ad9b01048913">{</span>

<span id="docs-internal-guid-3aa6e95b-f1e7-05bf-4e17-ad9b01048913">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"timestamp": 1532535732707,</span>

<span id="docs-internal-guid-3aa6e95b-f1e7-05bf-4e17-ad9b01048913">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"quality": "true",</span>

<span id="docs-internal-guid-3aa6e95b-f1e7-05bf-4e17-ad9b01048913">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"id": "simulator.001a38000080029e.temperature",</span>

<span id="docs-internal-guid-3aa6e95b-f1e7-05bf-4e17-ad9b01048913">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"value": 23.9</span>

<span id="docs-internal-guid-3aa6e95b-f1e7-05bf-4e17-ad9b01048913">&nbsp;&nbsp;&nbsp;&nbsp;}</span>

|}
<div style="clear:both;">&nbsp;</div> <ol start="3">
<li><span id="docs-internal-guid-1f6976c1-f1e0-2bfe-f988-d8560223f12c">The final flex field image (</span>'''Flex Field Use Case 3''', below) shows all attribute/tag values sent from connected sensors on Shop Floor X. &nbsp;</li>
</ol>

'''<span id="docs-internal-guid-1f6976c1-f1e0-2bfe-f988-d8560223f12c">Figure 33c: Flex Field Use Case 3</span>'''

'''<span>[[File:Flex Field 3.png|border|700px|RTENOTITLE]]</span>'''

== <span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="mw-headline" id=".E2.80.8BStation"><span class="c5 c19">Station</span></span></span></span></span></span></span></span></span></span> ==

<span id="docs-internal-guid-e9fdd247-4bde-8d69-fe77-4c0fa741c822">The Station Mapping module links test stations to an SFDC '''device''' number and '''process'''. Within the IIoT framework, a '''Device''' is noted on the payload’s '''Tag'''. (See [[#Tag_Attribute_Mapping|'''Tag Attribute Mapping Requirements''']] for more details).</span>

<span id="docs-internal-guid-e9fdd247-4bde-8d69-fe77-4c0fa741c822">The Station mapping feature provides plants the ability to dynamically connect multiple customers, brands, and/or test stations to SFDC/MES locations and workstations. By placing similar data into the same subset, administrators can view overall measurement patterns to analyze and improve production.</span>

<span id="docs-internal-guid-e9fdd247-4bde-8d69-fe77-4c0fa741c822">For '''Sensor Capture parsers''', station mapping is used to hook up data coming from specific sensors to a process, and allows measurement to send data to different SPC monitors.</span>
<div>&nbsp;</div> 
=== <span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="mw-headline" id="Add_Station"><span class="c19 c5">Add Station</span></span></span></span></span></span></span></span></span></span> ===

<span class="c5">To add a new station, select&nbsp;the '''New +''' icon.</span>

'''<span class="c5">Figure 34: Add Station&nbsp;</span>'''

'''<span class="c5">[[File:Figure 31 Add Station.png|border|700px|RTENOTITLE]]</span>'''

&nbsp;

<span class="c5">The Station Form will display.</span>

'''<span class="c5">Figure 35: Save Station Form</span>'''

[[File:Figure 33 Save Station Form.jpeg|border|700px|RTENOTITLE]]

&nbsp;

&nbsp;

&nbsp;

=== <span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="mw-headline" id="Station_Form_Fields"><span class="c5">Station Form Fields</span></span></span></span></span></span></span></span></span></span></span></span> ===

*<span class="c7">'''Station Group''':</span><span class="c0">&nbsp;Name of the group to which the station will belong.</span> 
*<span class="c7">'''<span style="color:#FF0000;">*</span>Station ID''':</span><span class="c0">&nbsp;This is the station identification. Measurement parsers use this field to match a station and device mapping from a tag in the payload sent by the sensors.</span> 
*<span class="c7">'''<span style="color:#FF0000;">*</span>Device''': </span><span class="c5">The SFDC device number Measurement will use to communicate to SFDC when using this Station mapping.&nbsp;&nbsp;</span> 
*<span class="c7">'''AutoLog Defect Code''':</span><span class="c5">&nbsp;</span><span class="c5">If there is no defect mapping found for the defect being recorded, Measurement uses this default defect code on SFDC to fail a unit. This field will automatically populate.</span> 
*<span class="c7">'''Comments''':</span><span class="c5">&nbsp;This is a generic field to provide additional information on the parser. </span><span class="c7">Optional</span><span class="c5">.</span> 
*<span class="c7">'''Commands''':</span><span class="c0">&nbsp;This is a generic field to provide additional information on parser. If this sensor parser is being configured to send data to an SPC monitor, then this field must contain the '''monitor name''' the parser will send data to.&nbsp;</span> 

<span class="c0">'''<span style="color:#FF0000;">Note</span>''': Enter the exact monitor name defined in SPC: SPC_MON={spc-monitor-name}. For example: SPC_MON=MEAS_SENSOR_CAPTURE_Sensor 1_temperature</span>

*<span class="c7">'''Enabled''':</span><span class="c5">&nbsp;Set the station to be used, or not, while processing a test result data. '''For sensor parsers''', select&nbsp;</span><span class="c14 c30 c7">'''YES'''.</span> 
*<span class="c7">'''AutoLog Config''': </span><span class="c0">The SFDC PC this parser uses to send data.</span> 
*<span class="c7">'''<span style="color:#FF0000;">*</span>Name''':</span><span class="c5">&nbsp;A station name identification, like an alias, to be used on a station. </span><span class="c0">.</span> 
*<span class="c7">'''<span style="color:#FF0000;">*</span>Badge''': </span><span class="c5">The default operator to be used to login on SFDC in case this information is not provided in the test result data.&nbsp;</span> 
*<span class="c7">'''Process''':</span><span class="c0">&nbsp;The MES process to which the test station belongs. This is used for recipe creation. It is part of the Checklist module that identifies&nbsp;the recipe, and sends sensor data to SPC monitors. NOTE: SPC monitors are configured in Quality > SPC.</span> 
*<span class="c7">'''Arguments''':</span><span class="c5">&nbsp;This is a generic field </span><span id="docs-internal-guid-d33ce907-f1f6-c644-9e3f-73ff309b619f">that allows plants to pass information (arguments) from plant-specific data centers to parsers (e.g. a custom tag for a work station).</span> 
*<span class="c7">'''Use Autolog''': If yes is selected, the Station will not communicate with S</span><span class="c5">FDC.&nbsp;&nbsp;'''For sensor parsers''', select&nbsp;</span><span class="c7">No</span><span class="c0">.</span> 
*<span class="c7">'''Use Measkey''':</span><span class="c5">&nbsp;This sets the parser to send/not send the MEASKEY command to SFDC. When set to Yes, Measurement sends the MEASKEY command to SFDC and links this MES Activity to Measurement parametric data generated by this test. &nbsp;Doing so makes Parametric data viewable inside the Unit History report on MESWeb. '''For Sensor Parsers''', select&nbsp;</span>'''<span class="c7">No</span>'''<span class="c0">.</span> 

#<span class="c5">Fill out all mandatory fields (denoted with<span style="color:#FF0000;">*</span>).</span> 
#<span class="c5">Select&nbsp;</span>'''<span class="c7">Save</span>'''<span class="c0">.</span> 
#<span class="c0">Measurement will validate the data and insert the new station into the group.</span> 
#<span class="c0">The new station is now available in the station list (see '''Figure''', below).</span> 

&nbsp;

'''<span class="c0">Figure 36: Newly Configured Work Station</span>'''

'''<span class="c0">[[File:Figure 34 Newly Configured Workstation.jpeg|border|900px|RTENOTITLE]]</span>'''

&nbsp;

----

&nbsp;