Release plan 1.2 (01.05.2021)
The new release focuses on improving the users experience, automatic data exchange and improved security. There will be only a few data structure changes and these will be focusing on data CBs will import into their systems.
The small changes list will be extended based on feedback.
Dates
01.11.20-31.12.20 | Development of new features and publishing on dev site. |
25.01.20-29.02.20 31.03.2021
| Beta Phase on development site for new features. Due to the Covid situation end Feedback to new features / answering of questions and clarification will until 15.02.2021. To accommodate further feature and especially field requests by Auditors and OO the development was extended to implement them in R1.2 and not the new major release cycle taking at least 5 months |
01.03.21-31.03.21 April.2021 | Implementation Time for CBs. No changes, all feature requests will go into next release. |
01.04.21 01.05.21 | Release of IATF CARA 1.2 cara.iatfglobaloversight.org |
Functionalities
1. Rest API
Possibility for CARA to load and send data to CBs from within the application.
Will remove the requirement to load and save reports and to send them manually to cbs
already implemented features will integrate with restful concept
Provide restful paths by setting import or selecting CB so data can be send directly
Provide restful commands for different exports and imports
Allow restful commands to be automated for example send backups directly to a server after 10 minutes/on save etc.
Enable/Disable encryption for restful
Further details https://infosysc.atlassian.net/wiki/spaces/CARA/pages/753041424
2. Encryption improvement
The implemented encryption in version 1.1 creates problems with interfacing with CARA due to the fact that CBs have to know every password to decrypt.
3. Single Sign On to ADP-Database
4. Small changes
Adding full bi-directional functionality for process reference list
if nc/pa/ofi templates if clicked on in the reference table empty template will be added
if nc/pa/ofi si deactivated auditor will be asked to delete pa/nc/ofi.
Providing scopes in different languages by the auditor
Individual naming conventions for files based on user or CB
naming conventions can be set in settings but overwritten by CB based on settings provided to the IATF CARA project.
Mark sites or sublinks for required print fields
order long list
Enable using highlighting elements in text boxes like (italic, bold, bullets points)
order and filter list items (NCs, Processes etc.)
Draft report print
print of old version reports in new design without new required fields
adhoc-NC report
improved listing NCs and Processes
not audited for processes
improved audit recommendations
shifts for audited audit cycle
optional zip based file compression for attachments
merge protocol
5. Data description changes
All changes in the data description are designed to be similar to the exiting data structure as much as possible imports are designed with all fallback or empty new fields.
allow to add language specific scopes for certificates in different languages [all reports->Organization information]
allow month based dates for Dates of CSR [audit reports->Customer information]
add evidence of implementation files container (CBs field request) [Nc Management->Organization]
because CARA inherits all NCs from previous reports verification of previous audit nonconformities will get a column special audit conducted which will replace effectively implemented in this case [Audit reports->Audit conclusion]
Manufacturing process add no of operational shifts for every cycle to avoid removing data on old cycles based on reduced amount shifts in this cycle [Audit report->Manufacturing processes]
Manufacturing process shift times for this audit cycle [Audit report->Manufacturing processes]
Repeating Cb block for NCs revoked and returned by organization multiple times. Final block is always the last one [NC-Management->CB]
CbCertificate No for providing and receiving support locations