Production Engineering Scheduler — User Guide

What this tool is

The scheduler replaces the Trello board for production engineering. It holds every project, task and review card. It tracks what is issued each week and who is working on what.

The bar at the top of every page has these parts:

• Menu: the screens described in this guide. You only see the screens your role can use.
• Search box: type and press Enter. It searches every card, including archived and issued cards.
• Bell: your notifications. The red number is how many you have not read. It checks every minute.
• Version (small text): the version of the tool you are running and when it was published.

The Board and Timeline also show a weekly box in the corner. On the right it shows the engineering revenue issued this week, the adjusted target, a progress bar, the number of tasks issued, and the time left until the Friday close. In the middle it shows the number of open ECRs and ECRs closed this week (from the last ECR log import; a closed ECR counts in the week of its "Date Fixed or Rejected"). On the left it shows the previous 8 weeks, oldest on the left: their total, and each week's engineering revenue issued under its Friday date. The bar over each week is green if it met that week's adjusted target, yellow if it was within $25,000 of it, and red if it was further below. A dash means the week was before the scheduler was in use. On narrower screens the four oldest weeks are left out first, then the history, then the ECR counts.

Who can do what

Board

The board is a row of columns, left to right. It opens by default when you start the tool.

The columns

• Project pipeline: New Sold Projects, In Project Engineering, Ready for Production Engineering, In Production Engineering Summary. These hold the parent project cards only.
• Issued Parts for this Week: cards issued since the last Friday close.
• Project columns: one column per project, made by Add Project. Bars marked "Project columns" and "Project columns end" fence this area. The column heading shows the job number, job size and ship date.
• Miscellaneous Tasks (require parts to be issued), Other Tasks, Continuation/ECR's and PTO: work that is not part of a project task list. PTO cards are never issued.
• Every week a Sling & Parts Orders - week ending M/D card is made in Miscellaneous Tasks, due on the Friday, for the engineering work on the Sling Order Tracking and Non-Stock Parts Order Tracking Trello boards (links in its description). Assign it each week. It works like any other card. It is made once per week; deleting it does not bring it back that week.
• Previously Issued: locked history, filled at each Friday close. After 12 months cards move to the archive.
• Completed Projects: parent cards of finished projects.

Controls

• Filter cards… (text), All members and All projects drop-downs. A filtered column shows "shown / total".
• ↻ Refresh reloads from the server. The board also reloads when you come back to the tab.
• Clear filters resets all three filters.
• Σ on a column shows its totals: In Engineering Value, Issued Engineering Value, Previously Issued Eng. Value, Hours, Issued Date, Controls Value, Issued Controls Value, Previously Issued Controls. Your choice is remembered in this browser.
• ‹ on a column folds it to a narrow strip showing its name and card count. Click the strip to open it again. Each column folds on its own, and your choice is remembered in this browser.
• S on a project column shows its systems: sling type, trolley type and soil/moisture factor, as entered on the parent card.
• Previously issued from this column (drop-down under project and misc column headings): every card issued from that column, with date and person.
• + Add card at the bottom of a column. In a pipeline column, type "E2000000 Customer; City" to make a parent card (most are now made by themselves from the Project Capacity app). It gets the default "Project engineering" checklist.
• Load more shows older cards in long columns.

Moving cards

• Drag a card to another column or up and down in its column.
• Dropping a card on Issued Parts for this Week issues it (see Weekly close and issuing). Dragging it back out undoes the issue.
• Parent cards stay in the pipeline columns and Completed Projects. Task cards cannot go into pipeline columns. Nobody can drag into Previously Issued.

What a card tile shows

Label name tags on top, then the title. Below: HIGH, ON HOLD (an on-hold card is yellow on the board), review status, REVIEW, due date (red when overdue), the task's revenue (engineering value, and controls value as "C $…"; once issued, the issued value), CUSTOM, the Progress % chip in its colour, and an initials circle for each person on the card. Open tasks also show their start-by date. The job number is left off while a card is in its job's own column (the column heading says it) and shows again once the card is in Issued Parts for this Week. Hours are in the card window and the column totals (Σ).

Manager only

• Double-click a column title to rename it. The ⋯ menu sets a column colour, renames it, or deletes a column you added (only when it is empty).
• Drag a column by its top bar to move it. Double-click the gap between columns to add a column there. Project columns can only be made by Add Project.

Timeline

One row per person by default. Each task is a card laid across the days it covers.

Controls (defaults in bold)

• By member / By project / By column: how rows are grouped.
• Filter text, All members, All projects.
• Weeks across the window: 2 weeks, 4, 6, 8 or 12. The chosen weeks fill the window exactly.
• Show issued (off): adds issued cards in green. Issued cards cannot be dragged.
• ‹ and › move one week. Today jumps to this week. You can also scroll back 8 weeks and far ahead.

Reading it

• A heavy line marks each Monday. A clear line marks every day. Weekends are grey. Today is highlighted.
• At 2 weeks the cards are two lines tall and show "Job name - task" (for example "Kent ImageFirst - CONVEYOR LAYOUT"). At wider views the text is shorter.
• Colours: scheduled, overdue, returned for corrections, review, on hold (timeline), issued.
• Initials circles on a card show everyone on it. A card with several people appears in each of their rows.
• Under each name: the person's level, number of cards, and hours due this week.
• A card with only a due date is drawn back from the due date, one day per 8 hours. A card with neither date is listed under the row as "No dates".

Changing dates

• Drag a card to move it. Start and due dates move together.
• Drag the grip at the left end to change the start day, or at the right end to change the end (due) day.
• Everything snaps to whole days. A short message confirms the change, for example "Moved 2 days later".
• Tasks (n): a drop-down under each person's name lists their tasks, soonest due first. Drag a task from the list onto a day to schedule it. It keeps its length. Click a task to open it.
• Click a card (without dragging) to open the card window.

List

• Columns: Project, Card, Type, Assigned, Due, Hours, Review, Ship date, Latest eng. start, In Eng. $, Controls $, Column. Click a heading to sort. Default sort is Due.
• Filters: text, member, project, and a status drop-down (Any status, Overdue, Due this week, No due date, On hold, Ready for review, Returned for corrections).
• Include issued / completed (off) adds finished cards.
• Export CSV saves what you see. The page shows the first 600 rows.
• Click a row to open the card.

Team Calendar

• Every card with a due date sits on its due day, Monday to Sunday. Each item shows the person's initials and the title, in the person's colour. Overdue cards are red. On-hold cards are grey.
• Weeks in the window: 2 (default), 3, 4, 6 or 8. Scroll up and down through the weeks. ‹ › move a week. Today returns to this week.
• Filters: text, member, project, and Show issued (off).
• A busy day shows "+N more". Click it to see the whole day.

My Dashboard not for viewers

Your own page of widgets. It refreshes by itself every 30 seconds.

Widgets

• Counts: Due this week, Assigned no due date, Overdue, On hold, Ready for review, Returned from reviewer. Click a count to jump to its list.
• Hours scheduled this week: hours due this week against your available hours (weekly hours less estimated PTO).
• My projects: parent cards where you are the project engineer.
• Calendar of my due dates: Day, Week or Month view.
• Recent activity on my cards: what others did on your cards in the last 30 days (comments, reviews, assignments, changes, reactions).
• Task lists: one table per count above, plus All current tasks. Ready for review marks each line "waiting on you" or "waiting on reviewer".
• Record of tasks issued: the last 12 months, with a search box and an Open archive button for older ones.

Controls

• Project picker: show only one of your projects on the whole page. Show all my projects clears it.
• Customize: move, resize, add and remove widgets. Use + Add widget, Close gaps, Reset to default and Done. Your layout is saved for you.
• My review feedback opens your review page.

The manager can open anyone's dashboard from the Manager page. It shows in that person's layout and cannot be rearranged.

Manager manager only

• Three tiles: engineering revenue issued this week (with % of target), the adjusted weekly target (from the Operations Scorecard; override sets it by hand, blank goes back), and controls value issued this week.
• Team this week: per engineer: level, open, due this week, hours due, capacity (hours due turns red when over capacity), overdue, no due date, on hold, ready for review, returned. Click a name for their dashboard, or "review analytics". Also a count of unassigned tasks and an Open Smart Scheduler button.
• Project engineers: each PE and their projects, and how many active projects have no PE.
• Review queue: review cards marked Ready For Review, with the reviewer (or "no reviewer assigned").
• Locked weeks and reports: each closed week with totals, e-mail status and Download PDF. Catch up missed closes is only for a Friday the server missed. It can never close a week early.

System health banner (only you see it)

When something is wrong, a strip across the very top of the window shows how many problems there are and the first one. Red means an error, amber only warnings. Nobody else sees it. It is checked every minute and disappears by itself once the problem is fixed.

• Automated actions failing: any background job whose last run failed (production refresh, Project Capacity sync, notices and their e-mails, reading Teams posts, work order / PO # fill-in, the Friday close, recurring cards), or the background jobs stopping altogether. A week not closed by Saturday, or a weekly e-mail that failed, shows too.
• Functions broken: an unexpected server error (red), or an error in anyone's page in their browser (amber), in the last 24 hours.
• Data links not working: a link that is set up but failing or out of date (production app data over a day old, Project Capacity failing or not read for an hour, the Operations Scorecard or skills chart file missing, no target for this week, the ECR import over 7 days old, the Custom Solutions Library folder not writable).
• Details lists every problem with when it started and what to do, the links still waiting on setup (these are not errors, so they do not raise the banner), and the recent errors with who saw them. Hide hides the banner until the list of problems changes.

Review Analytics / My Review Feedback not for viewers

Engineers see this as My Review Feedback, about themselves only. The manager sees Review Analytics: a tile for every person, then each person's page.

• Tiles: first-pass approval (last 90 days, and the 90 days before), tasks reviewed, returns per task, average rating.
• A plain-language summary.
• Current skill ranks from the skills chart: 1 Apprentice, 2 Journeyman, 3 Grand Master.
• By task type: open a type to see its numbers, its review cards (click to re-read the feedback) and its tasks. An orange "N shop issues" chip counts the shop's posts about that type of work.
• Shop issues: posts in the Teams chat Engineering Drawing Questions/Issues matched to this person's work (see Shop Issues), the last 90 days and in all, per task type, with the latest ones and a link to each post. The team tiles show the 90-day count too.

It counts only feedback recorded in this tool. It started fresh at go-live.

Smart Scheduler manager only

It is an assistant only. It never assigns, dates or moves a card by itself.

• Left: Needs an owner (default) or All open, with a filter box. Tasks are listed by target start date: the most behind schedule at the top, the farthest out at the bottom, then tasks with no start date. The target start is the suggested ENG start when the historical data gives one ("Start by"), otherwise the card's own start date ("Card start"). A red chip shows how many days behind a task is. High priority no longer moves a task up the list.
• Pick a task. Right: suggested ENG start, issue-by, ship date and estimated effort.
• Who could take it (or Possible reviewers): production engineers ranked by skills-chart rating for that kind of task, then by free hours. Columns: rating, free before start (red if negative), free by issue-by (fits or does not fit), open load, notes.
• Add to card asks you to confirm, then adds that person to the card. Anyone already on it stays. No dates are set.
• Availability by week: six weeks of free hours per engineer. Red = over-committed, amber = nearly full, green = room.

Project engineers, R&D helpers and viewers are not listed here, with one exception: ... REVIEW BY PROJECT ENGINEER cards (the sling reviews) list the project engineers and every engineer who reviews, by free hours.

Add Project not for viewers

Drop the FORECAST_TASK SCHEDULE workbook on the page, or click Browse for Excel file…. Close the file in Excel first. Nothing is written to Trello. The full rules are in Adding a project.

• Summary tiles: project, job size (automatic from revenue; you can pick Small, Medium or Large), cards to create, In Engineering Value, Controls Value and total hours.
• Drawing tasks (DRAWING or DWG in the name) get a fixed number of hours instead of the sheet's Duration: 4 h on a small job, 8 h on a medium job, 16 h on a large job. Install drawing reviews are always 2 h. The hours follow the job size if it changes. Hours you type on a card yourself are kept. Project engineering tasks on the parent card's checklist have no hours.
• Review → task link map: which tasks each review covers, with a confidence score. Remove a link with × or add one with "+ add a task…". Recalculate and Download as CSV are here too.
• Rows from the sheet: tick or untick rows. Rows left out are listed below with the reason.
• Tick I have reviewed the review → task link map, then Create project (n cards). Start over drops the file.

Reports

• Report on: Issued work (history) or Open work (right now).
• Issued work has From and To dates (default: the last 90 days) and quick buttons: Last week, 30 days, 90 days, 12 months.
• Filters: project, engineer or person, task type. Group by week, month, project, customer, person, task type and more, or no grouping.
• Columns in the detail table: tick the columns you want.
• Save this report keeps your choices in this browser. Saved reports… brings them back.
• Export summary CSV, Export detail CSV, and Print / save as PDF. Click a row to open its card.

ECRs

The open ECRs from the SharePoint Engineering Change Requests list, as of the last import (shown at the top; an orange chip means it is more than a week old). SharePoint stays the master: the scheduler only reads it.

• Tiles: Open, Approved, ready (accepted, with a priority and an estimate), Approved, needs an estimate, Not reviewed yet, and every ECR in the list.
• The table: ECR number (opens it in SharePoint), status, priority (P1 highest to P5), estimate, age, part, change requested and why, who asked and when, who it is assigned to. Show all open, ready, needs an estimate or not reviewed; sort by priority, oldest, smallest estimate or ECR number. Export CSV downloads what is shown.
• Priority and estimate are read from the ECR's Notes, typed by Jeff as Priority 4 Hours 1.

Coming next: a suggested ECR each week for the engineer with the most free time, the Friday outcome log, and backlog charts.

Shop Issues manager only

The posts in the Teams group chat Engineering Drawing Questions/Issues, saved by a Power Automate flow (setup below). Read only: nothing is posted to Teams.

• Issues and replies: a Teams Reply belongs to the post it quotes; an engineer's post answers the latest issue of the last 12 hours (with none, it is set aside, like an announcement); a second post by the same person within 30 minutes is part of their issue; anything else is a new issue.
• Matching: a work order in the post or its replies (E2021800-D1A, also e2021800-d1a) finds the task card with that work order, or the job's card with that letter, and its engineer. Otherwise a product named in the post (rail, cable lift, chutes, slings, conveyor ...) gives the product line. With no card, the engineer is the one tagged, else the first engineer who answered (you only when nobody else is).
• Needs matching (red): no work order and no product. The work order is often only on the print in a photo, which the scheduler cannot open: Open in Teams, read it, then Assign… and type the work order (the card and engineer follow), or pick the engineer and product line yourself. Assigned by hand stays as you set it; Back to automatic undoes that.
• Other statuses: Matched (card found), Work order (no card has it yet, e.g. issued before the scheduler), Product only, Resolved, Not an issue.
• Fixing the sorting: Part of previous issue, Not an issue / It is an issue, and on a reply Make it its own issue. Resolved closes an issue.
• Show: Needs matching (first when there are any), All open, Resolved, Not issues, All. Check for new posts reads the folder now; it is also read every minute.

Setting up the flow (once)

1. In OneDrive make the folder Engineering Scheduler with Teams Issues inside it.
2. make.powerautomate.com > Create > Automated cloud flow, trigger When a new chat message is added (Microsoft Teams), Chat: Engineering Drawing Questions/Issues.
3. Add Get message details (Microsoft Teams): Message = the trigger's Message id, Message type = Chat, the same chat.
4. Add Create file (OneDrive for Business): Folder Path /Engineering Scheduler/Teams Issues, File Name expression concat(body('Get_message_details')?['id'], '.json'), File Content expression string(body('Get_message_details')). Save.

Only standard connectors, so no premium licence. Posts made before the flow was switched on are not included. Once the scheduler is hosted the flow stays the same; the saved posts reach the hosted scheduler either through read access from IT or through a relay on a company PC. Full details: docs/TEAMS_ISSUES.md.

Library & Archive

• Custom solutions: every card saved as a custom solution, with project, task type, work orders, date and Open PDF. The PDF is made when the card is issued. Search by name, project, customer, work order or comments.
• Archive search: type at least two letters to search every card, including archived and previously issued ones. Each result shows "archived", "previously issued" or "on board".

Admin manager only

• Data sources: status of production dates, PTO allowance, Operations Scorecard, skills chart and weekly e-mail. The weekly target is the row Eng Rev adjusted weekly goal to finish on schedule of the Operations Scorecard (Matt Wilson's OneDrive, sheet Score Card_<year>), read from the scorecard_path setting.
• Import ECR log: in SharePoint, open the Engineering Change Requests list, then Export > Export to CSV (not Export to Excel), and choose that file here. Do it every Friday before 4 pm; the Manager page warns when the import is more than a week old. Each import replaces the last.
• Project Capacity: new parent cards: whether the link is connected (it needs that app's public key from Matt), when it last checked, the last projects it saw and what it did with each, and Check now.
• Teams chat: shop issues: whether the Power Automate flow's OneDrive folder is on this PC, how many posts were read and when, open issues and how many need matching. The folder is the teams_inbox_dir setting.
• Import Unissued Shipments: Sync now from the production app, or paste or choose a snapshot. Instructions for taking the snapshot are in the drop-down.
• People: name, level, e-mail (used for sign-in), role (engineer, manager, viewer), active, kind (production engineer, project engineer, R&D / occasional, view only), Can review, hours per week. Add person and Import skills chart now.
• Optional CSV imports of ship dates and historical hours.
• Settings, then Save settings. Includes "notify email send" for the PE notice and "archive after months".
• Label consolidation proposal: how the old Trello labels map to this tool.

The card window

Click any card to open it. Changes save as soon as you leave a field. Close with × or Close.

Top

The title (edit it on task cards) and the label name tags.

Left side

• Description: free notes.
• Checklists: + Add checklist, rename it, add lines with Enter, tick lines done, set a due date, remove a line with ×, or delete the checklist. Lines on task cards have an Assigned to column. The parent card's lines do not, because the PE owns them all. A line that stands for a card opens that card, and ticks itself when the card is issued.
• Review (task cards): the review status drop-down, shared with the linked review card, and the list of review cards. If there is no review: "This task has no review card."
• Reviewer feedback (review cards): the status, then a thread of feedback, oldest first. Reviewers can write feedback, paste a marked-up screenshot (Ctrl+V) or Attach screenshot, add an optional 1–5 rating, then Post feedback. The owner of the task sees all feedback on it.
• Custom solution (task cards): see below.
• Comments with reactions, Images and attachments (image or PDF), and Activity (the history of the card).

Right side (task, review and misc cards)

• Move to Issued: the issue button. On an issued card you see the issued date and Undo issue instead.
• Assigned to: a tick-list. Tick everyone who works on the card. It saves when the list closes. The first person stays the main owner in reports. Each person shows as an initials circle on the card. On ... REVIEW BY PROJECT ENGINEER cards (the sling reviews) the list has the project engineers and every engineer, because any of them can do the review.
• Suggested people manager: the top five people for this task, with free hours before the start date and whether they fit by the issue-by date. Add puts that person on the card. Nothing is assigned until you click.
• Hours, Start date, Due date.
• Progress %: a drop-down in 10% steps, 0% to 100%. Coloured red at 0%, orange about 30%, yellow about 60%, green about 90%, blue at 100%. The same colour shows on the card tile.
• On hold and High priority tick boxes.
• Labels: a drop-down of task labels. Tick the ones you want. They show as name tags on top of the card.
• Values: In Engineering Value and Controls Value (only the manager can change them), and the issued, previously issued and issued-date figures.
• Issuance (after issue): issued date, work order and PO #. Filled in automatically when known. What you type is kept.
• Schedule: ship date, job size, engineering time, shop time, issue by, latest engineering start (red when past), and the source. "NO HISTORICAL DATA" means no estimate exists yet. The manager can set the ship date and job size here.

Review statuses

Not Started, Ready For Review, Under Review, Returned for Corrections, Approved for Issuing, Not Required.

• The task owner can set Not Started, Ready For Review or Not Required.
• A reviewer (not the owner) sets the rest. The manager can set any.
• A task and its review card share the status. When a review covers several tasks, tasks marked Not Required do not hold the review back.

Custom solution and the Custom Work Flow label

Ticking Custom solution - save for future and choosing the Custom Work Flow label are one switch. Turning on either turns on both. It adds a Custom work flow checklist once, with these milestones:

1. Concept review with the salesman, BDP, PE and engineering manager
2. Initial design review with the BDP and PE
3. Manufacturing review with the MFG manager
4. Bring the design to 80% completion
5. Send to the customer for approval
6. Redesign after customer feedback (if applicable)
7. Customer approval received
8. Finalize the design and drawings
9. Summary saved to the custom solutions library

Turning the switch off removes the label but keeps the checklist. Fill in the solution name and related work orders. A summary PDF is saved to the library when the card is issued.

The parent project card

• Project engineer: Assigned to (a PE), Due date, and Labels from the parent-card label set.
• Project, in this order: Job number, Customer number, Customer, Target first ship, ENG start by, Issue by (these three from the Project Capacity app), City, State, Engineering Revenue, Controls Revenue, then the systems (system type, sling type, trolley type: 12.5" 4-wheel, 10" 4-wheel, 6" 4-wheel, 2-wheel, customer bag or garment; soil/moisture factor). + Add system adds another. Only the PE on the project or the manager can change these.
• A new parent card starts with the Project engineering checklist: system forecast, task list, phases of installation, Basecamp shipments, M2 drawings, coordination drawings, and the four system layouts.

Labels

Task cards use: Custom Work Flow, Waiting on ICS, Design Change, Sent to Customer, Awaiting Approval, Ready for Print, RFQ Out, PO Sent, Parts Issued, Still Need Install Dwgs. All other labels (for example Logistics, Equipment, eVue Upgrade, Conveyors Ordered) belong on the parent card. Retired and removed from all cards: In ICS Design, ICS Complete, In Programming, Programming Complete, In Panel Fab, Waiting on eVue, Conveyors Needed, and the AREA labels. Old Trello labels for state (Done, On Hold, High Priority, percentages, review states) are now fields instead.

Archive and delete

• Archive (anyone): the card leaves the board but stays searchable in Library & Archive. Archiving a parent card leaves its project column and tasks alone.
• Delete manager: removes the card for good, with its comments and attachments. It cannot be undone.
• A card that has ever been issued cannot be deleted. An issued card cannot be archived either: use Undo issue first.

Adding a project (task list import)

1. The parent card must exist first. It is made by itself when the project is entered in the Project Capacity app (see New projects from Project Capacity); Matt or the PE can still make it by hand in New Sold Projects. Its title starts with the job number (E-number). Without it the import stops with an error and the Create button stays off.
2. Open Add Project and drop the workbook. This is a backup: Basecamp jobs are always populated by the task uploader in the eRail Suite, and nothing here writes to Basecamp. The tool reads the ENG_PROJECT_TASKS sheet with the same rules as the old Task Uploader. A task comes in when it is sold (has revenue above zero). Reviews follow the tasks they cover.
3. Check the link map and the rows, then create the project.

Import rules

• Project engineering tasks are not imported. They are the parent card's "Project engineering" checklist instead.
• ICS controls (rows under "Controls tasks by ICS", or with ICS in Resource Names) are totalled into one card: CONTROLS BY ICS.
• Safety netting review is brought in automatically when safety netting is sold, even if the review row shows $0.
• System design reviews stay standalone review cards. They are not linked to tasks. They are named in the PE notice.
• Custom curve drawings are never linked to a review.
• Each card gets its In Engineering Value (MECHANICAL column), Controls Value (CONTROLS column) and Hours (Duration).
• If the project already has cards, only rows that are not there yet are added.

What happens to the parent card

• It stays in its column and is tied to the project.
• It is renamed job - customer number - customer - city, state. City and state come from the CUSTOMER LOCATION on the task list.
• Its Engineering and Controls Revenue are filled in from the task list.
• A checklist "Task list import (date) (n cards)" lists every new card, linked.

New projects from Project Capacity

A sold project is entered first in the Project Capacity app. Within 10 minutes the scheduler makes its parent card in New Sold Projects, and you get a notice in the bell.

• Title: job number - customer number - customer - city (Canadian projects end ", Canada"). The Capacity app has no state, so add it on the card if you want it.
• Filled in from the Capacity entry where the scheduler has nothing yet: customer, customer number, city, total revenue and job size (small/medium/large from the project value).
• Dates on the parent card always follow the Capacity app, for every project on the board (not only new ones), refreshed every 10 minutes: ENG start by (its engineering start), Issue by (its engineering finish) and Target first ship (its planned first shipment). The task cards' own start-by and issue-by dates still come from the production app (Unissued Shipments).
• If the job already has a parent card here (made by hand or by the Erail Suite), no second card is made; only its blanks are filled in.
• A project saved in that app without a job number (it shows TEMP-...) waits until the real number is typed there.
• Each project is handled once: if you archive or delete the card here, it does not come back.
• Only projects entered after the link was first switched on are copied; the projects already in that app are not.
• The card's activity says "from capacity". Parent cards can still be made by hand at any time.

Read only: the scheduler never changes anything in the Project Capacity app. Admin > "Project Capacity: new parent cards" shows when it last checked, what it did, and Check now.

Weekly close and issuing

Issuing a card

• Click Move to Issued in the card window, or drag the card onto Issued Parts for this Week.
• If a linked review is not Approved for Issuing (or Not Required), you are warned. You can choose Issue anyway.
• The values move from In Engineering / Controls Value to Issued, and today's date is stamped. Values on issued cards are locked.
• When the last card leaves a project column (and something was issued), the parent card moves to Completed Projects.
• Issuing takes all of the card's labels off. The job number shows on it instead.
• Undo issue works while the card is still in Issued Parts for this Week. Its labels come back too. The values go back and the card returns to its column.

The Friday 4 pm close

• The week runs Friday 4:00 pm to Friday 4:00 pm, Central time.
• At the close the week's totals are locked and a PDF report is made. Cards in Issued Parts for this Week move to Previously Issued. After that they cannot be undone.
• The PDF lists every task issued that week, with a Total row at the bottom for the week's Engineering revenue and Controls revenue. It is the one fixed weekly report.
• The PDF is e-mailed through the company mail API, the same way the Project Capacity app sends its weekly report, once the Kannegiesser data token is saved on this PC (~/.kannegiesser/token, from Larry Erickson or Randy Schmidt). No SMTP is needed. Until then it is saved to the outbox folder. Download it from the Manager page. A copy is always kept in the outbox; a PDF over 3 MB is sent without the attachment.
• Cards in Previously Issued for more than 12 months move to the archive.

Notifications

• The project engineer on a parent card gets one notice per system (soil, clean, dryer loading ...) when every floor support (not floor support drawings), conveyors, rail and support req's task of that system is ready for review (Ready For Review, Under Review or Approved for Issuing) or issued. Each system's notice comes separately, as soon as that system is ready, and names that system's design review. Tasks for all systems (like the rail maintenance kit) are not waited for.
• Only the tasks the project has count. A task set to Not Required counts once it is issued. A task returned for corrections is not ready.
• If no PE is assigned yet, the notice waits until one is.
• The notice lists the tasks and any system design reviews now ready, with links to open them.
• It always appears under the bell. It is also e-mailed when the manager switches that on in Admin.
• The manager gets a notice when a parent card is made from the Project Capacity app (bell only, not e-mailed).
• Open the bell to read notices. Mark all as read clears the red number.

What's coming

• Erail Suite button: "Send to Engineering Scheduler" in the Erail Suite (rail.kannegiesser.ai) will send a task list straight into the scheduler, with no Excel file to save and drop. The scheduler side is ready; it waits for Matt's button and for the scheduler to be hosted. When it is on:
  • If a parent card with that job number is already on the board, the task list is linked to it and the card is filled in (it stays where it is).
  • If there is none, a new parent card is made in New Sold Projects.
  • The job's column and task cards are made with their values and hours, linked to the parent card, with a suggested start date on each task.
  • Sending the same job again adds only the tasks that are not on the board yet.
• Live production feed: the task cards' start-by and issue-by dates, ship dates and issued work orders will come straight from production.kannegiesser.ai every few hours. It stays off until its access key is provided. Until then, dates come from the snapshot imported in Admin.