Give analytical data its process context.
Use relevant Redshift information alongside operational documents and scientific sources to investigate manufacturing questions.
- reads
- moves
- publishes
- Test result
- Titer lower
- Feed lot
- 2231-B
- Feed 3
- 11:40, planned 09:00
- Deviation noted
- DV-0088
What the connection makes available.
Plan the connection around the work.
Review what the connection reads, the information your team needs, and the access the job requires.
| Kind | Data platforms |
|---|---|
| State | Available |
| Does | reads |
| Directory | Connectors directory |
Identify the source and the people responsible.
- 01The data sourceIdentify the Redshift environment and the information relevant to the job.
- 02The data ownerInvolve the people responsible for access and the meaning of the data.
- 03The operational comparisonDefine the process, measure, and question the data should help explain.
The information available through this connection.
Use this information to build operational context, with pointers to its original sources.
- 01
Batches
BR-0410 to BR-0421
- 02
Batch genealogy
Each batch to its feed lot
- 03
Certificates
0088 for 2231-A, 0091 for 2231-B
- 04
Test results
Titer lower on BR-0412 and BR-0421
- 05
Schemas
Manufacturing, quality, supply
- 06
Views
Titer by batch, lots by batch
- 07
Materialized views
Batch and lot summaries
- 08
Datashares
Read live where they are shared
Questions about Amazon Redshift.
Discuss the information you need and how your team will use it.
Turn time spent finding information into time spent moving forward.
Bring the job you want to move forward and the records you'd like connected. Thirty minutes on how Katalyze would do the work, and where your experts come in.
Or, just a quick chat to run through the product, your call.
