|
|
| Back to CRU-X Home |
| Wednesday, April 14, 2004 | ||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||
|
Quality Control Board - Members are Glenn Vanicek, Nancy Mager, Tim Francis, and Ron Mohr. This team will decide when facilities are to turn CruOps on with live data. They are currently testing 3.31 and expect to make a decision next week. Robicheau and NATCA Reps challenged the logic of this. Masson responded by essentially backtracking and saying the facility would say yay or nay to live testing, depending on their rationale. Robicheau asked for a definition of the QCB's task. CruOps 3.31 - This version has additional bug fixes. Masson promised Robicheau a change notification including a description of all changes since 3.29.3. Masson says the software is working well at NEW. Wismer would like to know how the training issue will be addressed since the CBIs are out of date. Essenmacher says the CBIs will not be updated, and that there will be literature and MBIs to advise users of new aspects of the software. Robicheau says it must be run in every area of the test facilities prior to any implementation outside of the test sites. Masson says it is Tobin's decision. NATCA MOU - Martinez recounted recent history of the negotiations. NATCA submitted a proposal and ground rules on Friday. Essenmacher said the Agency will not sign this MOU as is. TM Log Program - Hayden asked how this program would interface with CRU-X. Essenmacher says no decision has been made about which dash 4 would be official. Martinez said the TM Log Program should fall under Dennis Filler's group, but the management changes have not been made yet. NOP Issues - Wismer asked how CruOps handles a sector combination in the center environment. Masson did not know. Wismer indicated that the sector combinations appeared to be handled simply by the default settings. Position SISO with CIC - Orders will be changed so that it will be permissible to be signed on two separate dash-10 logs at once so that a cIC can work a position. This will only apply to a control position and a CIC position. | ||||||||||||||||||||||||||||||||||||||||||
| Wednesday, March 10, 2004 | ||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||
| MOU Status - Tuesday, March 23 the Agency will meet with NATCA. NOP - Offload is running at all centers. Offload capability exists, but CruOps has not been demonstrated to accept the data stream. CruOps - Essenmacher feels performance is adequate. Focus on version 3.29 (available 3/17) will be on the NOP issues. Sutton says that 3.28 showed an initial improvement with 3.28 on the drag-and-drop time but then it began to slow down dramatically. Currently, they are showing 15 secs for a drag-and-drop. Jones is experiencing the same problem at Van Nuys. Cleveland Center had an issue with having 100 positions per area, so this limit was removed from CruOps. Identified bugs last week involving closing out the dash 10's. Keysites - Focals have become quite involved with updating HQ on the status of keysites. Martinez to provide Robicheau with this information. Dennis Filler - Head of IT for the ATO. Tobin is reporting directly to Filler on a regular basis. Alaskan region - In the brave new world, the Alaskan regional office will only oversee FSS. There are transition issues connected with this. Product support - No change. Tobin has developed a resource document outlining how IT will be organized in the ATO. Version control - Robicheau informed Essenamcher that "third level" changes (3.28.1 to 3.28.2) will not require change notification forms. Second level changes (3.28 to 3.29) will require one. However, Essemacher agreed to make the third level revision available to all NATCA focals and this is not taking place. Credit hours policies - Essenmacher says now is the logical time to install the logic to enforce regulations regarding the increments that annual leave, time off award, and credit hours can be taken. Editing screens - Wismer feels many of the editing screens (LDR, dash 10s) are very awkward and that the workforce will find these too much trouble to work. Essenmacher responded with a discussion of issues involved in rebuilding training materials. | ||||||||||||||||||||||||||||||||||||||||||
| Wednesday, February 25, 2004 | ||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||
|
NATCA MOU Status - Agency submitted M-1. Includes NATCA staff. Robicheau says we responded to M-1 and waiting to meet.
Track It Feature Requests - Any Agency employee can access TrackIt and make feature requests, enhancements, and report bugs. ATX-400 has created a four page document on how to use this. It will go out in the minutes as an attachment. When will the feautres/enhancements be incorporated? After CruOps deployment. Cru-X 3.22 - Facilities must complete the feedback form by the 26th (tomorrow). Have only gotten one back thus far, none from AT terminal/en route. CruOps 3.27.1 - Was available Monday. Four facilities have downloaded. VNY, ZOB, NEW, SCT. Essenmacher was at Cleveland Center last week. Observed the software running in the area. Got feedback from two supervisors. Ops ran for 2 days without crashing. Sutton says only two sups are using it because the others are having problems and don't have time. He says they are not planning to run live testing on the 29th as Essenmacher understood. Waiting on MOU to come back. | ||||||||||||||||||||||||||||||||||||||||||
| Wednesday, January 28, 2004 | ||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||
|
CruSupport 3.19 - Had a significant immediate bug. Fice of seven bug reports said the software failed. Will be replaced by tomorrow with 3.0.21. Will release to AF. Will test for one pay period in AT. CruOps 3.23 - Essenmacher sent Robicheau a "quasi" change notification form. This version was released yesterday. Management telcon - Held yesterday. Essenmacher insists testing at the test sites can occur without I&I. Guidance is to be issued to -540 offices regarding impasse very shortly as a result of the management telcon. Sutton wants assurance that no live testing occur prior to MOU completion. Essenmacher says SCT, MYR, NEW, APA are all conducting ZZZ testing of CruOps (no data passed to payroll, but BUEs participating), and expects to have four more testing next week (JNU, ZAN, ZKC, MHT). Essenmacher says ZOB is ready to start testing but is waiting for MOU to come back from review, and adds that testing can begin. Robicheau strongly disagrees. N90 - Holtzman asked why the NATCA SME at N90 did not have a key to his office and did not have a LAN username and password. NATCA N90 cannot function as a test site without these. TrackIt! - This is the automated system for getting field reactions and feature requests. Essenmacher had previously said guidance would be issued but this will be delayed. Essenmacher refused to give a time frame. Schedule Import from Excel - Essenmacher said he'll try to get Vanicek on the next telcon. Nothing to report. Mentioned something about a global spreadsheet importer being worked. Time codes in CruSupport - Holtzman asked for the time codes to be shown in the T&A screen in CruSupport so that BUEs could figure out what their T&A meant. Essenmacher says this simple change won't be in effect until at least May. He said the new builds are "set in stone" weeks in advance and they cannot make changes on the fly. This was despite the fact that he just got done saying how they had rushed CruSupport 3.21 out after finding and correcting a bug in 3.19. Offload (NOP) - Despite the late hour in this project, ATX-400 is only now getting a first look at SISO data stream from HE980 patch. Wismer asked some technical questions about the reasons but Essenmacher reiterated the above. ZKC - ATX authorized the purchase of video cards needed at the supervisor workstations in order to accommodate CruOps. Both Grell and Wismer stressed that they cannot do anything without these. Apparently there was a communication problem with their 540. Next telcon - February 11. | ||||||||||||||||||||||||||||||||||||||||||
| Wednesday, January 14, 2004 | ||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||
|
Telcon lead - Paula Martinez is now running the national telcons with us. Keysite testing - ATX needs to open a dialog with facility management. Letter went out to advise them of what ATX is requiring. They are to reply by today with their status and explanations of reasons for delays. Robey asked what will be done with this information. Essenamcher says he'll share the responses with ATX-1 and Division Managers. The information will be used to decide on changes to time lines. The actual information will not be shared with NATCA, only the resulting guidance. Half of the facilities have responded. The information will be used to brief upper level management. In the letter, ATX advises facilities that I&I is not necessary to begin keysite testing. Agency cites Section 11 of the MOU, in that it does not apply to test facilities. Martinez insists that the software needs to be tested, regardless of I&I. Sutton advises it is not necessarily NATCA holding it back, particularly at ZOB. Essenmacher says keysites aren't waiving their rights. Jones says the Union will get the option to re-negotiate the agreement after the testing period. Brown also says he will permit re-negotiation of I&I after the testing period. Robicheau asked for a written statement regarding the Agency stance that test sites are not entitled to full I&I bargaining. Murray asked if the test site goes to impasse, can you implement? Essenmacher says they'll talk to ATX-500. Software - ATX-400 released CruOps 3.09 for testing as the "baseline" version. Was the software production ready? 3.17 is now intended to be released as the latest baseline version. They are thinking to release this on Friday. Robicheau wants to know why ATX-400 is not releasing the versions to NATCA Reps. TrackIt - Will be putting out guidance on how to use TrackIt. It will be used to record issues users would like to see. The information will be gathered and compiled and acted on only after the CRU-X software is fielded. February 27 - ATX-400 still intends to "implement CruOps" by this date. Essenmacher expects to have production grade software ready by this date. Wismer says Version 3.17 is not ready for release. He says he gets run time errors every 10 or so actions. He feels ATX will "poisin the well" by pushing the software out. Essenmahcer defines implementation as a facility passing T&A and LDR data gathered by CruOps to IPPS. Keysite testing is to implement same in the ZZZ database, not the live database. RADS - Reporting and Distribution System. Is RADS operational? Essenmacher says it is operational to a certain degree. Is it validating data from CRU-X? Essenmacher does not know. Robicheau wants the answer in writing. CruSupport populates IPPS, IPPS pushed that information through CUPS, and CUPS pushes it into RADS. Other questions: Jones wants to know when the databases will be populated with the duty schema. He says he cannot run CruOps without this. He says he cannot begin entering facility data until this happens, and that piece of the process will be very time consuming. Essenmacher says to talk offline. Wismer wants to know when Offload will be ready. Essenmacher essentially says it may not be ready any time in the near future. Wismer says the duty board will not function with more than 15 employees signed in. Robicheau wants to know what kind of support the Agency will provide to facilites that use Excel spreadsheets and do not know how to create text files. Essenmacher acknowledges this issue. | ||||||||||||||||||||||||||||||||||||||||||