-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO.txt
224 lines (132 loc) · 6.61 KB
/
TODO.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
todo items & test cases
//////////////////////////////////////////////////////////////////
// Target
- show workorders attached to:
- site
- machine
- tool
- show the event name on the workorder
- apply the document display panel to :
- site
- machine
- tool
//////////////////////////////////////////////////////////////////
// Done Today - and committed
- dont be case sensitive on logins
- on workorder, show the site / machine / tool / event
- remove make/model from machine display, as we dont use it
- dashboard list, show site / machine / tool
//////////////////////////////////////////////////////////////////
// Works in Progress
- on site screen, edit user list
- on site screen, user list, toggle btns to put people on the dist list for alerts / workorders
- publish an
- on SMS send, grab the reference retvals and store the SMS traffic against the DB
- display comms history, including emails and SMSs
- look at the whole UI again, from the point of view of a mobile user
- admin user, hover over IP address, allow them to capture that and apply some rules such as :
- give it a name
- any other settings
- be able to viev much more sys activity info on user sessions
- QA scan and apply socket updaters everywhere needed
- All updaters to refresh page data
- All editable data to have AddNew btn and simple access
- On user display, be able to dig into the log file and extract their HTTP history, either by IP or name
- display machine images by serialnum, not database id
//////////////////////////////////////////////////////////////////
// Event and Workorder processing
- edit alarm dist lists for each site
- Global search
- Be able to remove any doc
- User manual
- Full test cases and QA with doc attachments and doc pointers
- On workorder entry, match people to site of event (not just skill)
- Update details of a live workorder (start date / duration / descr, etc ....) that is not yet complete,
then popup another dialog with :
- list of participants with checkboxes. Select which one to send an email to
- notes field to edit the contents of the update
- submit btn to generate the email(s)
- Add estimated costs to workorders, and include this data in reports
- Once workorder is created, should lock down the details and not allow edits ?
** Better **
- if add new assignee, add them to the workorder, and generate a Workorder email for them
- if add new doc, then send the new doc out to existing participants for the existing workorders
- Event search
- WorkOrder search
- Event list, toggle view all / open events
- WorkOrder list, toggle view all / open workorders
- Annotate WorkOrder as it progresses
- Close off WorkOrder
- Close off Event
- On close workorder, close off event (if no other workorders pending)
- On close event, clear tool (if no other events pending)
- On clear tool, clear machine (if all tools on that machine are clear)
- Allow user to edit the description of docs that are attached to the event
- Be able to mark the workorder as acknowledged or accepted ...
Either manually by the site mgr, or by the tech logging in
and acknowledging the workorder
- Raise an alarm for workorders that are not acknowledged after a set
acceptable delay
- On raise workorder, select people by site associated with the event
- Raise an email alert for any events that are not actioned / converted to workorders within a reasonble timeframe
- add auditing and activity logs to the workorders and events
//////////////////////////////////////////////////////////////////
// General Data Management
- Edit parts that make up a tool
- apply part edits to other machines of same type, in other sites, allowing some versioning
//////////////////////////////////////////////////////////////////
// Feature Mapping with FastMaint
- "Task Templates" .. sort of have this with the notes and docs attached to each site / machine / tool
//////////////////////////////////////////////////////////////////
// Scheduling Maintenance
- Allow the Site Mgr to maintain a Preventative Maint Schedule, with pre-canned
workorders, and store these on the basis of :
- Per tool
- Per machine
- Per site
- System shall report on suggested preventative maint that is due, either by
displaying the suggestions on the dashboard, the daily digest email, or
raising a maint event automatically
//////////////////////////////////////////////////////////////////
// Ports
- Port all WorkOrder and Event processing code and changes to Site Manager
//////////////////////////////////////////////////////////////////
// Reporting
- Email daily digest
- User sub / unsub from daily digest email
- Graphs as needed
- Cost reporting, including estimated costs for work in progress, and estimated preventative maint costs
that are projected forward
//////////////////////////////////////////////////////////////////
// Code Refactors
- All socket comms should be wrapped in channels
//////////////////////////////////////////////////////////////////
// Known bugs
- On raise new issue, if you add a photo, and then back off from raising the issue,
this leaves an orphaned doc still temporarily attached to the event
- CSS hover over lists loses any hilighting colors
- Create workorder from event list attached to machine list does not default time to a sensible value ???
... cant reproduce yet
//////////////////////////////////////////////////////////////////
// Done
- Notes field on w/order entry screen
- With event document card list, stack the text under the image
- With workorder document card list, stack the text under the image
- Allow the Site Mgr to very easily create a new Event of type Preventative Maint,
which can be used to attach workorders to as needed
- On site mgr or admin only ... raise issue modal dialog to have preventative maint option
- Trace updating workorder ....
- Fill in time on displaying workorder
- New workorder default start date no longer works ... fix
- Add workorder to event, needs to reload event-workorder data
- With workorder document updates, refresh data and screen, the same
way that the event screen works
- WorkOrder details not showing the time correctly
- Some docs still have type "event" in place of "toolevent"
(seems to be for docs that are supposed to be attached to a workordeg)
- Add document to existing workorder ... tries to call /docs/toolevent
- new workorder ... WO notes not appearing on WO initial email ??
- add SMS gateway to config
- on raise event, generate email and SMS to dist list by site
- On raise new issue, if you add a photo, and then back off from raising the issue,
this leaves an orphaned doc still temporarily attached to the event