mcbradford Posted March 16, 2005 Share Posted March 16, 2005 I have been tasked with determining the percent operability of equipment. I accomplished this by defining a relationship and three fields. relationship match:match percent_op (calculation Sum(count)/Sum(match)*100 count (calculation if (equipment is operational =1, TextToNum ("")) match (calculation = 1) Another condition has been added, "limited". So I went about setting up three more fields and another relationship. The limited has a weight of 50. I then add the weighted percent to the operational to get an adjusted percent operational. Bottom line - there are 62 pieces of equipment. I do not want to define 124 relationships, and 372 fields! Any ideas???? Please!!! Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 If I understand correctly: FIELDS: Operability (number, or calculation, number) - either 1 (operational), 0.5 (limited), or 0 (not operational). IMPORTANT: blank values will be ignored! Constant1 (calculation, number) = 1 cAvgOperability (calculation, number) = Average ( AllEquipment::Operability ) RELATIONSHIP: AllEquipment (Constant1 = Constant1) Format cAvgOperability to display as percentage (layout mode, Format>Number..) Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 The operability field is radio button. y, n, l y = operational, n = out of service, l = limited Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 Then you need: cOperability (calculation, number) = Case ( operability = "y", 1, operability = "n", 0, operability = "l", 0.5 ) And do the average calc on that. Or simply change operability field to a number field, and change your value list to: 1 0 0.5 You can label the choices appropriately on the layout with text objects. Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 I do not display the values, I have the titles above - so yes I can change the y, n, and l very easily to 1, 0 and .5. Are you asking for clarification in your first post or a solution? Looks like a relationship per piece of equipment and 3 fields - this is where I am at. I need operability on each piece of equipment not operability for the all combined. Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 My first post was a proposed solution. Now I see I may not understand the problem. [ QUOTE ] I need operability on each piece of equipment not operability for the all combined. [/ QUOTE ] Doesn't the field 'operability' indicate the status of an individual piece of equipment? If there are 62 pieces of equipment, there should be 62 records, each one with its own 'operability'. If a piece of equipment breaks down, the user needs to go the appropriate record, and change 'operability' to "out of service" or "limited". Is it possible that you have 62 fields in a single record? Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 One record with 62 fields. Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 I am working it, but still need to lean it down. I am doing it without a relationship, but I have too many fields. Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 That is not a good idea (to put it mildly), and your current predicament is a proof of that. What happens if you buy another machine? You need to re-define the database, instead of simply adding a record. With 62 pieces of equipment, you should have a file Equipment.fp5 with 62 records. Once you organize your data that way, life will become much easier. Because then you can make Filemaker do the work for you. The way you have it now is no better than keeping your data on a piece of paper. Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 I think I understand - but I want to be clear. Display my list of equipment in a ... portal on my record for each day? Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 At this point I am talking about structuring your data, not how to display it. In order to relate to that, I'd need more information. What other data are you tracking besides equipment? IOW, what is the whole thing supposed to do? Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 Additional FYI - thinking about it... A record is created every 12 hours. I am trying to figure out what value there is in having all my equipment in another file. The equipment needs to be updated every 12 hours. If I define a portal - then I define a relationship - what is related? Maybe I am really missing something. Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 This is a shift turnover report. Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 I am sorry - that doesn't mean anything to me. Turnover of what? What is recorded every 12 hours? Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 All activities within a 12 hour period. Equipment Operational Status Comments Equipment piece 1 Y n/a Equipment piece 2 N needs repaired Safety No one was hurt Staffing - Salley called in sick Work Performed - Complete ### items. Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 Do you need to keep the report in the database, or will a printout do? Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 Each report is kept. It is a record. It has a serial number assigned to each record. The record is locked and cannot be modified after the off-going supervisor confirms the data is correct. The records could be audited (making sure serial numbers in order and last modified timestamp has not been changed). Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 Can you post your current file, with one or two records? Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 You see.... My database currently has 623 records in it. I can see how many times a piece of equipment has been down during the past 623 shifts. Also if I need to know how many times Salley has called in sick, I can find it here (and other places - just an example). Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 Not easily - hosted - would need to take it down. Each record has ~10 layouts. Display of information depends on the user. This is a small piece of the pie - this tracks one group of 10. Link to comment Share on other sites More sharing options...
mcbradford Posted March 16, 2005 Author Share Posted March 16, 2005 Signing off for the day -I will check post tomorrow. Thanks for the efforts so far. Link to comment Share on other sites More sharing options...
comment Posted March 16, 2005 Share Posted March 16, 2005 Pity, because I see only a partial picture, obviously. The way I see it, you should have these files: MAIN.FP5 EQUIPMENT.FP5 REPORTS.FP5 and probably some others, like PERSONNEL.FP5. The MAIN file reflects current status. In one of the layouts, you have a portal to EEQUIPMENT, showing the current status of ALL equipment. If a status changes, the user goes to the layout Equipment in the MAIN file, scrolls the portal to the relevant row, and enters the change (in terms of interface, this can be made much better, but for now I am sticking to the basics). When a shift changes, we want to "snapshot" the current status, and make a record of that in REPORTS. This is not that different from what you have now, except for equipment. Two ways of dealing with that: (1) a single text field in REPORTS will hold the information for all 62 machines. Pros: fewer records. Cons: information about a specific machine is buried in a long text field, thus cannot be accessed directly. (2) another file, REPORTITEMS.FP5, will a hold a record per machine per shift. Pros: easy access to any data, for example: from EQUIPMENT, I can see the history of any selected machine. Cons: about 45,000 records generated in a year, so maybe we'd want to archive that file every year or two and replace it with a fresh one. If (1) is acceptable, and you really want to keep it simple, you can roll MAIN and REPORTS into one file (basically the way you have it now). The only change is that EQUIPMENT is now in another file, and a snaphot of that needs to be stored before creating a new record. Are you with me so far? Link to comment Share on other sites More sharing options...
mcbradford Posted March 18, 2005 Author Share Posted March 18, 2005 I do not want to rework the entire database at this time - I plan to do this when our FileMaker 7 server is up and running. Thanks for your help, but I was looking for a somewhat better way to do the performance indicators. I have come up with a solution that requires only 2 fields per piece of equipment. Link to comment Share on other sites More sharing options...
By Soliant Consulting,
By Soliant Consulting,
By Soliant Consulting,
Recommended Posts
Archived
This topic is now archived and is closed to further replies.