Inventory Control Project
Bibliographic record
Abstract
Sioux City Brick is a manufacturing company that produces four main products in various colors. The products include a residential and architectural brick, brick chips, and thin brick. Sioux City Brick employs over 100 employees and corners of the business extend from Iowa, Nebraska, to Minnesota, and South Carolina. However they service a much larger area including Canada.\nCurrently the company is experiencing long loading times, a cramped and cluttered yard, and fork lift operators spend a lot of time organizing and moving inventory around. All are a result of their being an excess amount of leftover brick. This brick comes from the remains of orders as well as faulty batches and almost all of the excess brick can meet at least one of many secondary uses so the company tends to accumulate it. For the time being their yard operations are lacking standardization from operator to operator, as well as a lack of accountability throughout their operators. The company is currently scheduling more orders and adding to the waitlist for this year and next year’s production schedule. Right now this facility is operating at a fractional value of their full capabilities regarding their yard operation and infrastructure of organization. With the utilization of our suggested SOP we feel that we can assist them with increasing standardization throughout the west lot which could easily translate throughout the facility. A well-organized brickyard creates several opportunities including more inventory space, possibility to start and fill more orders annually, and a higher inventory handling efficiency. Overall the yard is affecting the company by contributing to excessive product transportation which results in a form of overprocessing. Through implementation and adjunct application of our SOP Sioux City Brick will be able to benefit from standardization of work and how operators are facilitating yard activities. This will allow them to identify areas needing improvement in the future this will also allow for proper measuring of yard activities and efficiencies. This standardization will open pathways for future projects within the capstone area or within the company.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.012 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.006 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.012 | 0.004 |
| Open science | 0.004 | 0.003 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.126 | 0.043 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".