This feature should enable the user to quickly highlight a risk, making it immediately visible to everyone. Typically reporting such risk is done via email or phone call. With this feature the user can do this immediately through the app. Furthermore it is a massive benefit that all open risks are consolidated in the app and dashboard, enabling users to get an overview of all risks and quickly identify the most severe risks.

Following info about the risk could be relevant:

• Risk category (to be defined by admin and used for statistics)
• Risk description (optional)
• Risk probability
  • High = certain delay
  • Medium = probable delay
  • Low = unlikely delay
• Risk impact
  • High = delay of more than one week
  • Medium = less than one week
  • Low = delay within a day
• Risk status (Resolved Yes/No)

Have the possibility to link two or more entities with parent/child or sibling relationships. The is potentially powerfull for users who need establish as-built documentation where it is important that components are traceable throughout the final entity (parent entity).
Examples hereof could be requirements for material certificates and material traceability.

The features should enable the user to effortless find:

• Sub-entities based on the parent entity
• Sibling entities based on an entity or grouping identifier

The logistics feature is used to represent movement between locations and partners. It is useful to have a central overview of exactly what has been shipped and received against the entity, including traceability of all documents related to transport.
It should be possible to submit planning, shipment and reception data related to the entities, directly via the app.

Information and data that is relevant could be:

• Planning:
  • Estimated shipping date/time
  • Estimated arrival date
  • Carrier
  • Destination
• Shipping:
  • Shipment Qty
  • Actual shipment date/time
  • Photo of CMR doc
• sReception
  
  • Received Qty
  • Actual arrival date
  • Photo of delivery note
  • Update location (if possible based on GPS coordinate or user input)

It should be possible for users to add comments to an entity, to substitute email communication, which is often 1 to 1 and poorly organised.
It should be possible to add general comments, but also possible to add comments within the individual features, to maintain an even more specific context for the conversation

Enables users to instantly upload almost any file format to Prescience.
Documents are to be stored in relation with the entity, making it easy for users to see which documents pertain to which entities.

It should be possible to add some meta data to the attachment, in addition to the mandatory time, user and file format info, such as:

• File Type (quality document, certificate, etc)
• File description
• more?

The checklist (data form) feature is primarily directed at quality control, but can be used in other connections too.
The checklists and forms are access and filled out directly in the app by the operator. Replies are pushed to the data storage. The feature offers full transparency enabling the stakeholders to directly see data once it is keyed in.

Admins can create as many checklists as they want, combining unlimited:

• yes/no
• radio-button
• multiple choice
• text input
• number input
• perhaps even photo and sketch input

Checklists can be simple capturing quick yes/no questions, but they also allow for more detailed data capture, including data verification and evaluation features.

Common verification features:

• Ensure field has been filled
• Ensure value conforms to specific format
• Ensure value conforms to predefined allowed range
• Reduce likelihood of typo's by asking for double verification (like passwords)

Evaluation features:

• Assign "pass"/"fail" values to the data immediately based on predefined pass/fail criteria specified by the admin. This allows for direct acceptance statistics to be done on the results.

The "Track Defect" feature must enable users to quickly and effortlessly register defects right then and there using the mobile app. Often reporting observed defects can be a pain and usually this activity is postponed or neglected because people are in the middle of doing something. Enabling the users to register the defect with the mobile device they have on them, makes things a lot easier.

The feature should enable the user to quickly register the Defect with the mobile app:

• Select defect category (used for Pareto statistics)
• Describe the defect in words
• Take and upload one or more fotos documenting the defect

Later on the user or the quality casehandler can add the following info, either in the app or in the dashboard:

• reference to or attachment of the official incident report or link directly to the incident in casehandling system.
• Update status (fx. registered, resolved)