Common use of Project Risks Clause in Contracts

Project Risks. ● Identify the risks to the success of your project. Utilize the following guiding questions to structure the approach to risk identification. Consider your project’s risk holistically and add any necessary project-specific risks and mitigation measures. For each risk identified, explain the steps to mitigate those risks (before or during the project). We encourage you to use the ROAM Framework. ● Stakeholder risks ○ Who needs to contribute data to the solution? How likely are they to do so? ○ Who needs to utilize the solution? How likely are they to adopt it? What barriers to adoption are anticipated? ● Personnel risks ○ Are there key personnel on your team or on vendor teams who hold critical and unique knowledge? ○ Are there vendor relationships where the vendor has disproportionate leverage or lock-in? ○ Are there any ambiguities in your definition of “done” that could lead to misalignment between project goals and implementation expectations? ● Implementation risks ○ Will aspects of the system involve new technologies? ○ Will the system be required to process data at a larger scale than your current systems? ○ Does the completeness or format of the data itself present any significant challenges? ○ Which parts of the proposal are most likely to run over budget (time or cost)? ● Collaboration risks ○ If you are collaborating with another port, what challenges might arise in gathering consensus on decisions? What processes will you set up to resolve those? ● Risks to standardization and interoperability ○ Are there any datasets involved in your proposal that do not have a clear standard already available? If so, how do you plan to keep your implementation aligned with what other ports or stakeholders in the ecosystem will build?

Project Risks. ● Identify the risks to the success of your project. Utilize the following guiding questions to structure the approach to risk identification. Consider your project’s risk holistically and add any necessary project-specific risks and mitigation measures. For each risk identified, explain the steps to mitigate those risks (before or during the project). We encourage you to use the ROAM Framework. ● Stakeholder risks ○ Who needs to contribute data to the solution? How likely are they to do so? ○ Who needs to utilize the solution? How likely are they to adopt it? What barriers to adoption are anticipated? ● Personnel risks ○ Are there key personnel on your team or on vendor teams who hold critical and unique knowledge? ○ Are there vendor relationships where the vendor has disproportionate leverage or lock-in? ○ Are there any ambiguities in your definition of “done” that could lead to misalignment between project goals and implementation expectations? ● Implementation risks ○ Will aspects of the system involve new technologies? ○ Will the system be required to process data at a larger scale than your current systems? ○ Does the completeness or format of the data itself present any significant challenges? ○ Which parts of the proposal are most likely to run over budget (time or cost)? ● Collaboration risks ○ If you are collaborating with another port, what challenges might arise in gathering consensus on decisions? What processes will you set up to resolve those? ● Risks to standardization and interoperability ○ Are there any datasets involved in your proposal that do not have a clear standard already available? If so, how do you plan to keep your implementation aligned with what other ports or stakeholders in the ecosystem will build?