AyMINE – Technical documentation
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Region / project / methodology
Change management process in a project
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Objects affected by the problem
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
Objects related to the task pattern
Contacts and directories module (CRM)
Address book or people and companies
Web management and automation
Receiving a message from the web
Asset management module
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
The AyMINE framework module
Configure how your system looks and works
Gestures and keyboard shortcuts
How the system works and how it protects data
Private notes and tags for objects
Filtering in the list of records
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Time sequences allow you to define the order in which tasks follow each other and how they build on each other. Thanks to time sequences, it is possible to plan and reschedule all tasks that follow each other, e.g. an entire project.
How time sequences are created
You can manually create time sequences directly for tasks or define them for sample tasks. In the project management methodology, you can use the hierarchy and sequence of sample tasks to create a sample schedule for an entire project or stage.
It is possible to create links directly between tasks, and it is also possible to edit time sequences after creating tasks from the pattern. This allows you to customize the generated tasks.
Examples of use:
- ISO 26262 requires the preparation of an FMEA risk analysis of a project prior to the completion of planning and approval of the project plan. The ISO 26262 methodology in AyMINE includes a sample project plan that puts these tasks in the correct order. The inclusion of the project preparation stage automatically creates tasks so that the task of conducting the FMEA is properly scheduled.
- A project scheduled according to the methodology will be delayed in approval by 2 weeks. Once the approval date is delayed, you can have the project rescheduled and the other steps will be delayed by 2 weeks as well.
Scheduling using task sequences
AyMINE does not reschedule tasks by itself. It creates the schedule when generating tasks from the templates, but any task shifts must be done manually by the project manager or area manager. Therefore, there is no risk of shifting scheduled deadlines spontaneously.
Remember: Rescheduling a project is change management and should never be done without first reviewing the context. If you are managing the project in accordance with a methodology (e.g. Automotive SPICE, ISO 20000, etc.), change management is a process that must have documented reasons and consequences.
Replanning is possible:
- Either complete, where all tasks in the project are rescheduled, or
- only one branch, where tasks related to the selected task are rescheduled
Rescheduling an entire project is a function triggered from the project workbench. You can reschedule one specific branch from the task detail. (You can reschedule tasks that are related to a task from a task.)
What changes and what doesn't when rescheduling
Rescheduling only changes the scheduled beginnings and endings of tasks that have not yet started and are scheduled. It never reschedules tasks that have already started or have been cancelled. Started tasks can affect scheduling because they drive the scheduling of tasks that follow them, but they do not move themselves.
A task that acquires a link to a previous task becomes automatically scheduled and remains scheduled until all previous tasks are completed. However, it is also possible for the user to manually start such a task.
Remember: Do not delete tasks generated from the methodology in projects. In addition to having to explain where it was lost during an audit, deleting it would break the links between projects and they would lose their proper order. You can delete a task that is unnecessary in a project and write in the reason why it is unnecessary.