Caliach Vision Feature Requests up to V6.0000

R0017 - Make and buy calendar working day proportion

Date: 18 Apr 2001, version due: 6.0000, rating: 20, platforms: All

Description: Make and Buy Calendar. We open up on Monday morning and run 24 hours a day until Friday lunchtime. Saturday mornings are worked if required. Work centres which run at night have an available time set at 24 hours each day. Other work centres are set at between 8 and 12 hours depending on typical overtime working. This means that the capacity planning routine over estimates our production capacity on Fridays and Saturdays, when we do not work in the afternoon or at night. Perhaps some thought could be given to the maximum available hours on a 'make day' within the Calendar maintenance window. Perhaps instead of just ticking the checkboxes for Monday to Sunday as required, we would enter the hours worked per day. e.g. Make days[18] Monday[24] Tuesday[24} Wednesday[24] Thursday[13] Friday[5] Saturday[ ] SundayCapacity planning would then provide better work centre loading as it would know not to allocate 24 hours of available time on a (say) Friday. The 'Buy Days' would not need altering as the number of hours worked per daydoes not alter any thing with respect to this function.

Get around: None

Caliach response: Pl

R0019 - Consignment stock goods inwards

Date: 18 Apr 2001, version due: 6.0000, rating: 20, platforms: All

Description: Additional option to identify consignment stock on receipt to be held in a similar way as quarantine. Suggestion for an additional option to dispatch consignment stock to bonded and produce a dispatch note for customer up to sales to mark order no invoice on dispatch.

Get around: None

Caliach response: Pu

R0027 - Capacity planning planning board

Date: 18 Apr 2001, version due: 6.0000, rating: 20, platforms: All

Description: Planning board display and drag & drop of orders in existing capacity planning function. A Capacity Planning window for graphically presenting individual WO schedule showing the capacity required in each WC in its operation routes. This info for each WO is currently already available in the Work Operation List window, but having it presented graphically for individual WO will make it easier for the user to interpret the capacity requirement of each WO (see CapacityWOFromCK.xls file in Notes).

Get around: None

Caliach response: Pl

R0041 - Batch Tracking of WO Outwork Operations

Date: 24 Aug 2001, version due: 6.0000, rating: 30, platforms: All

Description: Provide some sort of batch tracking record for outwork operations on a work order. Pehaps by special tracking records created when WO completed.

Get around: None

Caliach response: Wo

R0043 - Serial Number Assignments in Stock History

Date: 22 Aug 2001, version due: 6.0000, rating: 10, platforms: All

Description: Would it be feasible to have the option to include Serial Number Assignments as transactions in Stock History? It would show as something like "SN Assign", Qty 1, Ref= SO-12345, Comments=<THE SERIAL NUMBER>. This would greatly enhance our ability to track Serial Numbers through their lifecycle. {Original customer reference: R0017}

Get around: None

Caliach response: Sn

R0071 - Change Work Order Quantity

Date: 5 Sep 2001, version due: 6.0000, rating: 20, platforms: All

Description: It is only possible to change a WO qty when it is un-kitted. This is either at the start (before kititng) or after it has been fully un-kitted. I realise that this is probably to ensure that WIP components do not get orphaned. 1) Would it be difficult to allow WO qty change at any time and just return any excess kitted items to stock? 2) If this is not simple then would it be possible to automatically mark a WO as un-kitted after a WO receive if there are no kitted items remaining. For example: if a WO was for 20 items and I kit 10 lots of components. I then receive 10 of the item. This leaves 10 items remaining but no components kitted. At this point it should be marked as un-kitted so that it can be changed or cancelled. {Original customer reference: R0004}

Get around:  

Caliach response: Wo

R0084 - Part Serial Number Control Option

Date: 5 Sep 2001, version due: 6.0000, rating: 20, platforms: All

Description: I would like to propose that you add another option - "Force SN Structure Assignments on WO Receive". It is good to force users to create the WOs parent part SN when you receive the WO. But it would be better (optionally) to make them set the structure at this time also. Suppose I have issued child parts with SNs to a WO and that the parent assembly that I am making is also serial numbered. The whole point of the exercise is to make people stipulate which child is with which parent. {Original customer reference: R0017}

Get around:  

Caliach response: Sn

R0101 - Make calendar to be associated to work centres for downtime

Date: 18 Dec 2001, version due: 6.0000, rating: 20, platforms: All

Description: The current calendar applies to all work centres and when capacity planning is run it is not possible to evaluate the results in relation to machine that may have maintenance down time or where key operators may be on leave. Would it be possible to have a calendar related to work centres that may be adjusted to reflect actual availablity. {Original customer reference: R0068}

Get around:  

Caliach response: Pl

R0110 - Work Tracking enhancement: mandatory breaks

Date: 28 Jan 2002, version due: 6.0000, rating: 20, platforms: All

Description: We would like to be able to set the minimum daily breaks in the system, to meet working hours legislation.

Get around:  

Caliach response: Wo

R0111 - Work Tracking enhancement: single swipe recording

Date: 28 Jan 2002, version due: 6.0000, rating: 20, platforms: All

Description: We would like an option to allow the system to automatically determine whether a logging was a logon or a logoff. I.E. if you are logged on it loggs you off, and if you are logged off it logs you on. This would reduce swiping times considerably. requiring only one bar code per employee badge.

Get around:  

Caliach response: Wo

R0112 - Work Tracking enhancement: repeated logging checks

Date: 28 Jan 2002, version due: 6.0000, rating: 20, platforms: All

Description: We would like the logical inconsistancy checking to include a check for accidental repeated loggings (i.e. the same logging repeated within a given time, say 3 mins).

Get around:  

Caliach response: Wo

R0113 - Work Tracking enhancement: maximum daily hours

Date: 28 Jan 2002, version due: 6.0000, rating: 20, platforms: All

Description: We would like to be able to set the maximum allowable daily attendance hours by employee for time and attendance recording. We would also like to be able to see the daily attendance hours already booked for each employee. (Talk to Jo Stone).

Get around:  

Caliach response: Wo

R0135 - Engineering Change Warning window change

Date: 17 Jul 2002, version due: 6.0000, rating: 10, platforms: All

Description: I would like to suggest an improvement to the warning window that appears when you add a part to a PO that is subject to engineering change. The window also appears when you list MRP results and other places I'm sure. It would be much more useful if the window included: a) The same button that is on Parts\Engineering marked "View Engineering Data" that allows you to look-up engineering data so that the changes can be referenced easily. b) The "Subject to Engineering change" tick box so that the change flag can be removed to indicate that the process has ended and that the new drawing has been sent to the supplier. Additionally, if you have many parts subject to change and you go into "Create PO/WO from MRP" you have to repeatedly click the warning window for each change (if you just want to go and have a look). Either, this warning should be displayed as you create the PO/WO (rather than when you enter the window) or a button provided on the window that ignores further warnings ("Yes to all"?) {Original customer reference: R0125} **REJECTED FROM V1.3000 - Window is modal**

Get around: None

Caliach response: Ma

R0137 - Part Available to Sell and Parts Sales Data window improvements

Date: 29 Jul 2002, version due: 6.0000, rating: 10, platforms: All

Description: When someone calls to check availability of items it is difficult for a sales person to know how many of an item could be sold because phantom parts are never in stock. It appears to the user that we have no stock and no projected stock. Could these two windows be enhanced to handle phantoms correctly? Could you expand all phantoms and determine the number that could be dispatched at that time - this gives the physical stock. I realise that projected would be more difficult. Alternatively, the components could be included in the list (like aliases are) and we could work it out ourselves. {Original customer reference: R0126}

Get around: None

Caliach response: Sa

R0160 - Part cost log enhancement

Date: 13 Nov 2002, version due: 6.0000, rating: 10, platforms: All

Description: The costs history log is a very useful innovation (and will be even better when you do it as a graph :-) ) but For a fuller picture should you not include some additional information: 1. The MOQ for the part at that time (without which you cannot really tell if the cost was a realistic one. 2. The selling price (and then 2 calculated columns for margin and margin%). Do you not think that it would be very useful to know selling price and profit over time?

Get around: None

Caliach response: Ma

R0161 - Addition of drag-and-drop capability to Process Route maintenance

Date: 28 Oct 2002, version due: 6.0000, rating: 10, platforms: All

Description: We usually build up our Operation Instructions in Procees Route Maintenance by listing a number of standard clauses which we keep in Standard Texts. It would be very convenient to be able to drag-and-drop from the Standard Texts into the Operation Instructions window as it is possible to put only one Standard Text into the Standard Works Text window {Original customer reference: R0146}

Get around: A lot of typing !

Caliach response: Ma

R0165 - Sales item configuration special notes

Date: 22 Oct 2002, version due: 6.0000, rating: 10, platforms: All

Description: During the creation of configured part to be able to add additonal description/notes that will be printed on any subsequent work order in the comments field. This is particularly useful where the description may be greater than 30 characters {Original customer reference: R0124}

Get around: Remember to add the notes when creating WO

Caliach response: Sa

R0176 - Direct Payments between Customers and Suppliers

Date: 28 Jan 2003, version due: 6.0000, rating: 20, platforms: All

Description: In some situations the customer is the same external business as the supplier, and in these cases it is necessary to set up a suspense account so that payments/refunds can be made from this rather than the bank. Any unallocated amounts can then be paid from the bank if necessary. Some accounting systems allow a direct payment between the A/R and A/P for a business that is both a customer and supplier, such that a "credit (or payment?)" is created in one and a "debit" in the other. The credit can then be allocated against debits on the receiving account. This does away with need for a suspense account and would be very useful. {Original customer reference: R0004}

Get around: Use suspense account

Caliach response: Le

R0177 - SO Bonding options to be added

Date: 16 Sep 2003, version due: 6.0000, rating: 20, platforms: All

Description: Option to be added to permit 'Bond all items available' so that a SO can be bonted up to the availability of current stock. Also to dispatch all items on a sales order only if previously bonded, both for single dispatches and shipping load dispatches.

Get around: Manually enter quantities

Caliach response: Sa

R0178 - Message Box facility to have message threads

Date: 16 Sep 2003, version due: 6.0000, rating: 10, platforms: All

Description: The Message Box is a very useful tool, but suffers from the inability to reply to a message, thereby often losing the thread of a discussion.

Get around: None

Caliach response: Sy

R0179 - Archive old Quotations feature

Date: 16 Sep 2003, version due: 6.0000, rating: 10, platforms: All

Description: Having spent a little time tidying up the datafile by deleting some old quotations which have expired, I realised it would be very nice if they could have been archived instead, so that they could be brought up in the (non-) sales history in future. In some ways failed quotations are more important to analyse than successful ones converted into sales orders.

Get around: None

Caliach response: Sy

R0182 - Currency default bank account

Date: 12 Feb 2004, version due: 6.0000, rating: 20, platforms: All

Description: Provide an additional field on the currency file CURGLAC which could be optionally used to apply a default bank account which would apply when receiving payments from a customer or from a supplier when their default currency had a default currency bank account entered.

Get around: Change from the system default bank account manually

Caliach response: Le

R0187 - Failed login to list users

Date: 15 Sep 2004, version due: 6.0000, rating: 10, platforms: All

Description: When unable to login due to too many users could the warning message display a list of users logged in.

Get around: None

Caliach response: Sy

R0188 - BoM Changes to have comments

Date: 26 May 2004, version due: 6.0000, rating: 20, platforms: All

Description: The Bom Log is great for tracking who changed what and when, but lacks the ability to include information on why a change was made. It would be useful if there was space to add a comment when a change is made to a BoM.

Get around: Keep external records of reason for change

Caliach response: Ma

R0189 - Payments to Customers to show on-order value

Date: 15 Sep 2004, version due: 6.0000, rating: 10, platforms: All

Description: It would be useful to have the customers on-order value on the customer payment window with appropriate drill down to view orders.

Get around: None

Caliach response: Le

R0191 - Export and save file destination path held as default

Date: 15 Sep 2004, version due: 6.0000, rating: 10, platforms: All

Description: There needs to be a default directory list that is recorded in Terminal.ini as a non-visible option. Then when export/import read/save file functions are called the user selection is recorded for use as default for that function the next time it is used.

Get around: None

Caliach response: Sy

R0192 - Option to restrict update of purchase parts records

Date: 15 Sep 2004, version due: 6.0000, rating: 15, platforms: All

Description: Provide an option that can contain a calculation that would act as a filter to restrict the action of "Update or Create Purchase Part Records". For example, PTMTYPE<>'N'.

Get around: None

Caliach response: Pu

R0193 - Forecast and Auto-Plan not messaging other plan windows

Date: 15 Sep 2004, version due: 6.0000, rating: 10, platforms: All

Description: When a forecast auto-plan is saved, changes are not updated on other open plan windows.

Get around: None

Caliach response: Pl

R0194 - Add option to control 5 sec Workgroup Trigger timer

Date: 15 Sep 2004, version due: 6.0000, rating: 20, platforms: All

Description: Provide an option to alter the default 5 second timer that Workflow Triggers use to wait after processing stops to initiate the sending of trigger messages.

Get around: Be patient after initiating a trigger!

Caliach response: Sy

R0196 - Clean reports for HTML in-line headings

Date: 15 Sep 2004, version due: 6.0000, rating: 20, platforms: All

Description: Some reports that use an extended height kText heading do not render an in-line heading in HTML. The use of this legacy technique should be removed.

Get around: None

Caliach response: Sy

R0197 - Batch numbers to be pre-assigned to WOs

Date: 30 Aug 2004, version due: 6.0000, rating: 10, platforms: All

Description: When we issue a Work Order to a third party manufacturer we include all necessary process instructions on the WO, including labelling of the containers. Many clients require us to mark the batch numbers as part of the standard labelling, but we cannot auto-issue a batch number until later, when we backflush the WO, which is too late for the plant. We need a system in which batch numbers can be pre-issued and reserved at the point of creation of the WO.

Get around: None

Caliach response: Wo

R0198 - Costing of purchased goods to be extended

Date: 30 Aug 2004, version due: 6.0000, rating: 75, platforms: All

Description: In our international business the typical build-up of our costs of incoming goods is as follows :- purchase cost + transport to port + forwarding cost + ocean freight + clearance costs + transport from port + handling + warehouse charge. (I think it is the same for international businesses of all types.) Currently we accumulate all of these cost contributors into one field, PUHCOST, after which it is impossible to track cost history at the level of detail we require. Could we have extra fields to track all, or at least some, of these important variables in accumulating purchase history, and a new Confirm Received Purchase Order Item Costs window to reflect the more complex underlying structure. Ideally this window should allow data entry into each field in currencies other than that of the PO, which only reflects the currency of the purchase cost.

Get around: None

Caliach response: Pu

R0201 - Batch Location Assignment float stock visibility

Date: 31 Jan 2005, version due: 6.0000, rating: 10, platforms: All

Description: The listing of float-stock for a selected part would help in avoiding negative float stock for multi-location non-tracked parts.

Get around: None

Caliach response: In

R0203 - WO Kit Return - full return with no quantities not allowing to mark as unkitted

Date: 11 Nov 2004, version due: 6.0000, rating: 30, platforms: All

Description: Often we have to cancel an order without completing the full quantity, but if there are no kit items to return (i.,e. we have scrapped the lot) the system will not allow us to mark the work order as unkitted, so we can't cancel it without doing a 'pretend' return and then adjusting the stock. If full return is clicked, and then the quantities returned to zero, could the system offer the option of just marking as unkitted so we can cancel it?

Get around: Return 0.001 of one of the materials, then adjust stock.

Caliach response: Wo

R0206 - Unplanned by-products from backflushed Work Orders

Date: 4 Nov 2004, version due: 6.0000, rating: 10, platforms: All

Description: We can have planned by-products via the Part set-up. But we also often create unplanned by-products in a Work Order. It would be very useful if the backflush window would allow for the creation of by-product, either stock or non-stock, tracked or non-tracked.

Get around: None

Caliach response: Wo

R0207 - A/P overdue payments when un-allocated credits option

Date: 31 Jan 2005, version due: 6.0000, rating: 10, platforms: All

Description: When a credit is applied to an A/P account and it is uncleared, it is corrrectly accomodated in the overdue payment list but if payment is made, it is not allocated and therefore does not list in the remittance advice note. Request and option in the date selection dialog to 'Include and allocate un-cleared credits'.

Get around: None

Caliach response: Le

R0208 - Job Invoicing - option to create Dispatch Note & number for sales history items

Date: 20 Oct 2004, version due: 6.0000, rating: 15, platforms: All

Description: We often need a dispatch note to accompany completed job shipments. Can we have a check-box on the invoicing window, which allows the addition of a dispatch note number to sales history items, to allow us to print a dispatch note for those same items?

Get around: Customise invoice document to serve as dispatch note.

Caliach response: Sa

R0209 - Purchase History report to show batch tracking reference

Date: 31 Jan 2005, version due: 6.0000, rating: 10, platforms: All

Description: Add a purchase history report like rPuhList that includes a batch tracking reference, if any.

Get around: None

Caliach response: Pu

R0210 - Purchase History report to show actual stock location(s)

Date: 7 Oct 2004, version due: 6.0000, rating: 20, platforms: All

Description: The standard Purchase History report rPuhList is a little confusing in that it shows 'Location' only as the standard or preferred location. It would be less confusing and, we believe, more informative if the location showed the actual location into which the incoming material was received.

Get around: None

Caliach response: Pu

R0214 - Allocated employee code on WO Operations

Date: 24 Feb 2015, version due: 6.0000, rating: 20, platforms: All

Description: The ability to list next available operations for operators and work centres etc. If a column was added to the work order operations to allocate and store employees, then a listing window (independent of CRP, but obviously doing a mini-scheduling calculation to put all the operation starts in order) could be offered so that operators can just go and get the next job. A modification to work order operation route maintenance, and/or a new window, would be needed to allocate employees of course.

Get around: None

Caliach response: Wo

R0217 - Batch tracking records for Stock Transfers

Date: 24 Feb 2015, version due: 6.0000, rating: 20, platforms: All

Description: Batch-tracking records are not created for stock transfers, while changing location quantity in stock control activities does. This seems inconsistent, and as you can move from one batch to another, could result in losing track of part of a batch when using Stock Transfer.

Get around: None

Caliach response: In

R0218 - Introduce Ledger Transaction Serial Number

Date: 24 Feb 2015, version due: 6.0000, rating: 20, platforms: All

Description: Currently there is no "Transaction Serial" in the sense of a single sequential number for the group of transaction rows that make up a process activity - a payment, invoice, journal, etc.. This currently means you have to assume some common attributes, in this case Doc Ref, Comment, Trans Type, Ident or contra, to identify the group of transaction rows. It becomes more problematic with greater concurrent user activity.

Get around: None

Caliach response: Le

Back to Program Changes Contents