Scheduling Webapp for production planning and resource scheduling.
- About
- Features
- Screenshots
- Getting started (local)
- Usage
- Contributing
A scheduling web application built with Next.js and TypeScript for planning, tracking, and exporting production schedules.
- Gantt chart view
- Weekly and downloadable schedules
- Production tracking and sheet integration
- Race/die differentiator and view-by-dies
- Schedule settings and configuration
To get started, take a look at src/app/page.tsx.
More views — click to expand
Short descriptions:Weekly schedule: compact, week-focused schedule view. Downloadable schedule: exportable/downloadable schedule layout.
Additional screens — click to expand
Short descriptions:Production tracking: track production quantities and status. Schedule settings: configure scheduling parameters and preferences.
Integration & filters — click to expand
Short descriptions:Sheet integration: connect to sheets for import/export of schedule data. View by dies: filter and view schedule items grouped by die.
Small tools — click to expand
Short description:Die differentiator: helper tool for distinguishing dies or variants.
You can run this application on your local machine (like a Windows PC) for development and testing. You don't need to convert it to a desktop application. Here's how:
- Install Node.js: If you don't have it installed, download and install the "LTS" (Long Term Support) version of Node.js from the official website: https://nodejs.org/
- Node.js includes
npm(Node Package Manager), which you'll need to install the project's dependencies.
- Node.js includes
Before you run or modify any Apps Script or change the sheet structure, read the following files in the docs/ folder:
-
get-urls-apps-script.js
Fetches URLs from the Google Sheet. Configure this script with the correct sheet ID and default sheet name before running. -
google-apps-script.js
Handles scheduled-time behavior and sheet updates. Note: scheduled time values are not forwarded to the molding sheet in the same format — check the comments for handling of JC numbers and start times. -
production-conditions-apps-script.js
Contains production-condition logic and mappings (for example, producing itemGCH_S121_NBRwith die569). Review these rules before changing production or die assignments.
Why read these first
- These scripts contain configuration values and logic that affect how data moves between sheets and how schedules are generated.
- Changing sheet columns or IDs without updating the scripts can break imports/exports.
- Review the inline comments in each file for environment-specific instructions and examples.
Need adjustments?
- I can add this snippet into README.md or create docs/README.md and commit it on a new branch (suggested: add-docs-index). Reply with:
- A to create a new branch and commit (provide branch name or accept default add-docs-index), or
- B to overwrite README.md on master, or
- C to just get the snippet (you’ll paste it yourself).
- Open a Terminal: Open a command prompt, PowerShell, or any other terminal on your Windows PC.
- Navigate to Project Directory: Use the
cdcommand to go to the folder where your project files are saved. - Install Dependencies: Run the following command. This will download and install all the necessary packages listed in your
package.jsonfile. You only need to do this once.npm install
After the initial setup, you can start the application easily without opening a terminal manually.
- Find
start-local.bat: In your project folder, you will find a new file namedstart-local.bat. - Double-Click to Run: Simply double-click this file. It will automatically:
- Open a new terminal window for the server (keep this window open).
- Wait a few seconds for the server to be ready.
- Open the ProSched application in your default web browser.
For a true desktop experience:
- Right-click on
start-local.batand select "Send to > Desktop (create shortcut)". - Go to your desktop, rename the new shortcut to "ProSched".
- You can even change the icon! Right-click the shortcut, go to Properties > Shortcut > Change Icon....
If you prefer to start the server manually:
- Start the Development Server: In your terminal, run this command:
npm run dev
- View Your App: Open your web browser and go to the address shown in the terminal, which is usually
http://localhost:9002.
Your application is now running locally! Any changes you save to the code will automatically be reflected in your browser.
You can download a .zip file of your entire project to your local computer. While there is usually a "Download Code" top in the top toolbar.
- Use the main view to create and edit schedules.
- Export or download schedules from the "Download" option.
- Use the Gantt chart for timeline-based visualization.
- Configure schedule settings from the settings panel.
- Create a branch for your change: git checkout -b my-feature
- Commit and push, then open a pull request.







