Required Data Fields
- Print
- DarkLight
Required Data Fields
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
The following fields must be present in the input stream to the operator. Required Input Fields are represented below based on the model type.
Cycle Sink
REQUIRED DATA FIELDS
The following field definitions are required the input stream record type
.png "image(25).png")
OPTIONAL/DERIVED DATA FIELDS
The following fields are derived if not present in the input stream record schema.
.png "image(26).png")
Downtime Sink
REQUIRED DATA FIELDS
The following fields must be present in the input stream
.png "image(27).png")
OPTIONAL/DERIVED DATA FIELDS
The following fields are derived if not present in the input stream
.png "image(28).png")
Defect Sink
REQUIRED DATA FIELDS
The following fields must be present in the input stream to the operator.
.png "image(29).png")
OPTIONAL/DERIVED DATA FIELDS
The following fields are derived if not present in the input stream.
.png "image(30).png")
Raw Data Sink
REQUIRED DATA FIELDS
The following fields must be present in the input stream.
.png "image(31).png")
ADDITIONAL DATA FIELDS
Any additional data fields found in the input stream record will be defined in the DB table schema and sent to the database as well. Each data field in the input stream will correspond to a single column in the output DB and Model Metadata. The rules for describing the data field definitions is done via Field Annotations and a description of how those annotations are applied can be found in the Custom Defined DB Columns and Model Metadata documents.