Hi Bobby,It’s good to hear from you. For product direction and roadmap for IFS Maintenix you can find information on this topic on the new IFS A&D customer portal. For more granular feature development, we collecting feature requests through the Ideas portal of IFS Community. [Edited 2024]Regards,Rob
Hi, Yes, several customers have adopted flight adapter v2. Some customers are using it inferentially because their processes include entering flights manually, where the behavior through the UI matches that of the new flight adapter logic. Some customers went live with this version and solutions were designed with this functionality in mind, while others have updated their middleware and processes as part of recent upgrades. We have seen all variants of adoption. This area of the product has been receiving consistent investment in stabilization and feature improvements since its launch in 8.2-SP3. Regards, Rob Technical Lead, A&D Global Technical Support
Hi Brian, I have redirected your inquiry into the IFS Apps section of the community portal. The reply was made in the context IFS’ Maintenix application, which has a different support portal. I have just logged in to the portal you have linked, and it appears to work for me.
Does this require any particular version of Maintenix to be installed prior? Hi Harvey, The solution is applicable to any customer running 8.1-SP2 or above.
Hi Brian, I opened the link, then clicked Login to IFS Portal. I was redirected to a Microsoft-based single sign on page, and using my ifs credentials I was given access to the portal. Is your process similar?
Who would be able to connect with our Business Team to discuss in more detail, is that our account rep? We have an All Operator Message from Bombardier, but I’m not sure I want to make the call myslef on if/how we can utilize this solution. Hi, We have reviewed AOM700-1162 and the software will be delivered compatible with Bombardier’s advice on the matter.
Hi all, The product now supports a rollback function for single aircraft. By removing all blackouts from an aircraft your task deadlines for this aircraft will return to their initial state, having a sched to plan matching the baseline, and a deviation matching the original extension on the task. The documentation in Nelson’s post has been updated to revision 1.1.
So, as I understand it, Clock Stoppage is an extension of the Blackout option, adding calendar based limits to the solution. To use Clock Stoppage one must also be using Blackout and therefore the additional functionality of Blackout would also be put in effect. Hi Harvey, That is correct. The blackout feature will push estimated due dates to the right for usage-based deadlines. The period of blackout will replace the forecast model, replacing estimated daily usage increase. The two effects are complimentary, and will give a better visibility to planners on the expected maintenance once the storage period is lifted.
Hi Harvey, Without this solution in place Overdue calendar tasks will collect on aircraft, and must be completed to return the aircraft to service. If you have sched to plan high values your forecast tasks will be rescheduled from LASTDUE, earlier than you are entitled. The short term horizon of the aircraft’s usage based deadlines will shift every day. For example, a task with an estimated due date in approximately 7 days will be updated daily to be due in 7 days. With the solution in place, you can estimate fleet maintenance demand as you reactivate the fleet. You will perform less work to return your aircraft to a serviceable state. Calendar tasks will be credited with extensions, and will not come due during the storage period. At a high level, if a task had 10 days remaining when it went into storage, it will be due 10 days after the aircraft is returned to service. Your program will be permanently credited. Calendar task chains will benefit from an extension to the maintenance pr
Hi Bobby, These topics are also covered in the document attached to Nelson’s original post, see the “Effects On Tasks - Extension rules”, and “Effects On Tasks - Task Revisions”. I am updating the document as the software continues to evolve based on feedback. Latest revision is 1.2 from 27-Apr-20. For Boeing aircraft, the quick answer is yes, the whole program with specified exclusions is eligible for up to 6 months of extension from its original due date. All your examples are correct for Boeing aircraft. For Airbus the rules are more complicated. Extension limitations are based on the rescheduling interval, and tasks whose due date is during the storage period have their extensions capped based on Return To Service (RTS) date, rather than original due date. Some of Airbus’ rules related to limits from RTS are not mathematically possible to reach depending on your interpretation of the rules, but the limits have been specified, and the software adheres to them. The due date is 20-Oc
To those who are curious about my statement about limits not being mathematically possible, here is an example. For an Airbus task C1 with a 3 year interval that is due 20-Apr-20. Given an aircraft in storage from 01-Apr-20 to 01-Apr-21. According to the rules, this task is permitted an extension up to 6 months from RTS, or 20-Oct-21. Our interpretation is that the extension in days can be up to a maximum of the total storage period, 365 days on our example. Therefore this task is eligible for an extension of 365 days, and due 20-Apr-21. Another interpretation of the rules is that you get credited up to RTS, then have the capped extension applied afterwards. The total storage time was 365 days, but you are only allows to be credited 180 days of extension after RTS. The eligible extension is 346 days from original due date to RTS + 180 days limited extension. The total extension is 526 days, and due 20-Oct-21. We have elected to implement the first interpretation, which is the safer opt
New features are available now. Please inquire through the support portal if you are interested in these latest developments. Giving the control to your engineering team: The software was originally designed to use one query with baseline data rules to identify tasks. It worked best if the list of tasks stayed consistent. Using the task definition tags feature, we are giving your engineering team full control over which tasks are identified for extensions. Inclusion tags for standard extension rules. Exclusion tags to roll back changes for task definitions that were incorrectly included in the program. Exception 1 and Exception 2 tags for Airbus specific rules. A data loading tool will soon become available to bulk load tags into the system. Support for tasks going in and out of the storage program: Using tags means the list of tasks that are included in the program will change over time. The software now supports bringing new tasks in, and taking tasks out. Tasks removed will recov
Hi Samuel,Several customers are using the cycle counting feature in their daily operations. Some customers are using the classic portable device pages, and some customers are using the spreadsheet feature. The GTS team has reached out to these customers to see if they would like to share their experiences here.In 8.3-SP2 we launched modernized workflows for cycle counting that streamlines the process using mobile scanning devices, a redesigned UI, as well as improvements to bulk import and export of cycle count data. There is successful adoption of all the available methods.
Hello Ye,It is most common for a Maintenix solution to track CYCLES, HOURS, ECYC, and EOT on an engine assembly to address this need. The task definition would be defined on the engine itself, but use the HOURS parameter for scheduling. These parameters could be added to the MXFL data source on the assembly, or could be added to the BULK data source. It depends on the capabilities of your flight following system. If added to the MXFL data source, your engines would automatically inherit the same usage as the aircraft when flights are complete.I took the opportunity to review your data and I saw that some of your engines are designed with this solution, while some of the engines do not have an MXFL data source defined. Is there more detail to this issue that I’m missing? For example, is it mandatory that the task definition is defined on the aircraft assembly?
Hi Ye,From a Maintenix perspective, if it was mandatory for the task definition to be on the aircraft, we would experience the exact problem you are trying to solve. Maintenix would not have an automated method to determine that scheduling for this task needs to follow the engine, or be reset when a new engine is installed to the aircraft. The best solution here is to add an MXFL usage data source. This is performed from the Assembly Details > Usage > Create Usage Definition.
Hi Mags,I believe the intent of IFS Community is to achieve this ecosystem-level engagement for customers, our partners, and ourselves. If your objective is to present parity of vision during a sales engagement, then I believe our platform is already offering many of these functions today, based on your summary.As with any community based platform, the quality and depth of its content is as good as the contributions of its members. If you would like to know more about the current and future capabilities of IFS Community I can recommend @KristenGastaldo who is the Director of Customer Self-Service, and a champion for IFS Community engagement.
Hi Mags,Thank you for expanding. My understanding of what you have summarized above is that IFS Community can meet all the topics you have mentioned: exchanging of ideas and enabling communication. The delta you present is that IFS Community sits on the open internet, and is not a module within our SaaS product. Our IFS Cloud product contains links to IFS community to raise visibility of the service.I have connected with our product management team to get a better understanding of the topic. Their key takeaway from AMOScentral is that while it has a subset of the features of IFS Community, it will contain a platform with the capabilities of data exchange. For example two AMOS customers could transfer faults, send a workscope to an MRO, or enabling leasing of an aircraft. We do not offer an equivalent product in our eco-system, but with the development of our Disconnected Operations feature we have the infrastructure required to build an equivalent feature.
Hi Bjarki,I’ve been in touch with another customer who uses this API. The users are automatically created in Maintenix during an on boarding process in their HR software service. A manual process is in place to assign organizations and roles after the initial user creation.There is a section detailing this information in the Human Resources API Guide:All new users are added to the group of unassigned users in your default organization in IFS Maintenix. If you want to assign a new user to any organization, you must complete this action within IFS Maintenix manually. These users appear in the ADMIN organization’s Unassigned Users tab, and they can be assigned to the ADMIN organization in bulk from this page. I have attached a sample below.
Hi,Could we get a little more information about the challenge that you want to solve? Based on the information presented it seems that you would like to defer this maintenance to the installation activity, but the state of REPREQ is preventing your supply chain processes from reserving the inventory, and bringing this component into that scenario, because Maintenix enforces that only RFI inventory can be reserved and issued?From a compliance perspective, is the calendar deadline related to days fitted and in operation, or does the deadline intend to inspect and replace components that are subject to degradation over time like oxidation or rubberized fittings?
Hi Bobby,Our supply chain processes for addressing material demands are contingent on inventory being in a serviceable state. In 8.2-SP5 we softened this restriction by creating a new status called Ready For Build (RFB). An inventory is allowed to be missing mandatory sub-components and serviceable for the purposes of reservation and installation.Your exploration into potential options is already quite exhaustive. I have reached out to our architects group to see if other options exist.
Hi Magnus,There are a few articles on consignment orders within the online help built into the Maintenix product. Click Help in the top right hand corner, and search for ‘Consignment’. These consignment-specific articles are very similar to the resources available in the User Guide. The search does give you some additional insight into how this interacts with inventory ownership, and other elements of the product.There is no formal overview of the feature, as the feature is a close equivalent to the processes of purchase or exchange orders, with additional rules around financial transactions. The pre-sales organization has a recorded demo of the feature, and the client that was involved in the production of the video has allowed it to be shared privately. I will contact you via e-mail to share the link.
Hi Bjarki,I agree with your assessment, there is no feature in Maintenix that allows for all in work work packages to be rescheduled to a new location. This is especially important if there are part requests in your work package. If only one work package was started at one time, then it would be possible to reschedule the one work package to a new location, to ensure that newly picked parts are sent to the correct physical location. In your scenario there is risk that without double-checking the tail the parts will be delivered to the wrong bay.This is a good candidate for an Idea. Can you please raise your suggestion there? If you have counterparts in other organizations that you can encourage to vote for your idea, this would raise the visibility of the need.
Hi Philip,End Of Support (EOS) for the 8.1-SP3 product line was January 1st, 2016.
Hi Philip,The End of Life is a concept that applies to the major versioning of Maintenix, and does not apply to directly to Maintenix 8.1-SP3.
Hi Olivier,If your system is not running with Encrypt Parameters enabled, then the reference document page can be bookmarked, and this URL can be shared. If a user is not logged in, they will be redirected to the login page, but retrying the URL again will result in accessing the page. Robert.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
