The U.S. Department of Transportation's (USDOT) Intelligent Transportation Systems Joint Program Office (ITS JPO) works to strengthen supply chain resilience by supporting projects that develop cross-modal tools and technologies. This project, the Port Community Information Sharing System (PCIS) demonstration system, is a U.S. DOT’s initiative, in collaboration with Federal Highway Administration (FHWA), Maritime Administration (MARAD), and Volpe National Transportation Systems Center (Volpe) to improve supply chain transparency through real-time data exchange.
This project examined how real-time visibility, and connectivity can enhance system efficiency and explored opportunities for expanding and integrating the demonstration system, highlighting how emerging technologies like cloud computing and serverless applications can improve real-time data sharing, decision-making, and optimization of supply chain processes. This project output multiple resources and artifacts including written documentation of the user centered design process, a code base and software design document for the demonstration system, and a final report exploring future work that could contribute to the development of more efficient and resilient transportation networks.
This is a public repository that contains web application code and configuration files related to Amazon Web Services.
Step 1:
Download or clone this repo by using the link below:
https://github.com/usdot-fhwa-OPS/pcis-poc.git
Step 2:
Go to project root and execute the following command in console to install the required dependencies:
npm install
Step 1: Attain Codebase
Fork this repository, create a repository from this template (recommended), or download this repository as a .zip file
https://github.com/usdot-fhwa-OPS/pcis-poc.git
Step 2: Create New Amplify App
Access the AWS Amplify Console within your account and choose "Create new app." Follow the instructions to deploy a new application using your repository or .zip file.
Read AWS Amplify Documentation
Step 3: Create Port Capacity Variable
Set up the dynamic port capacity with AWS and the project. First, in the Amplify console, click into the deployment branch (in this case develop) > select Data in the left-hand menu > Data manager to see your database data. Click Select table > select Limit > select Create Limit > enter number.
You should now see a record populated within the table. Copy your newly created record's full id. Using that id, update the following lines of code within the project:
- src/components/settings/settingsButton.tsx, line 41.
- src/routes/__root.tsx, line 67.
- src/routes/index.tsx, line 151.
- src/routes/reservation.tsx, line 140.
Ensure that these changes make it to the develop branch. Within the Amplify console, click into the deployment branch > click Redeploy this version.
Step 4: Create S3 To DynamoDB Lambda Function
Step by step instructions for creating this Lambda function.
Step 5: Create Users API Endpoint with Lambda and API Gateway
Step by step instructions for creating this Lambda function and API Gateway.
Step 1:
Request an AWS account with the AmplifyBackendDeployFullAccess managed policy, ensuring you retrieve the username, session url, and region.
Read AWS Amplify Documentation
Step 2:
Install the AWS CLI.
Read AWS Amplify Documentation
Step 3:
Access your AWS account via the AWS CLI by running the following command in terminal:
aws configure sso
Terminal output example with suggested input:
SSO session name (Recommended): username from above
SSO start URL: session url from above
SSO region: us-east-1
SSO registration scopes [sso:account:access]: <leave blank>
Attempting to automatically open the SSO authorization page in your default browser.
If the browser does not open or you wish to use a different device to authorize this request, open the following URL:
https://device.sso.us-east-2.amazonaws.com/
Then enter the code:
SOME-CODE
## browser opens
The only AWS account available to you is: <your-aws-account-id>
Using the account ID <your-aws-account-id>
The only role available to you is: amplify-policy
Using the role name "amplify-policy"
CLI default client Region [us-east-1]: us-east-1
CLI default output format [None]: hit enter
CLI profile name [amplify-policy-<your-aws-account-id>]: default
To use this profile, specify the profile name using --profile, as shown:
aws s3 ls --profile default
Step 4:
Execute the following command in terminal Run a cloud development sandbox environment, which deploys a high-fidelity AWS backend locally:
npx ampx sandbox --profile <profile-name>
The amplify_outputs.json file should be written/updated.
Step 5:
With the command from Step 4 still running, execute the following command seperately to run the frontend project's development server on localhost:
npm run dev
The current version and release history of the PCIS-POC can be found here: Release Notes
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Welcome to the PCIS POC contributing guide. Please read this guide to learn about our development process, how to propose pull requests and improvements, and how to build and test your changes to this project. PCIS POC Contributing Guide
Please read our PCIS Code of Conduct which outlines our expectations for participants within the PCIS POC community, as well as steps to reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored. Anyone who violates this code of conduct may be banned from the community.
The development team would like to acknowledge the people who have made direct contributions to the design and code in this repository. PCIS POC Attribution
For more information, contact christopher.h.castillo@leidos.com.
For technical support, please contact the CAV Support Services at CAVSupportServices@dot.gov.