Spark vs Hadoop


Hadoop (MapReduce)



  • Uses disk-based batch processing
  • Slower due to frequent read/write to disk
  • More complex code (typically Java-based)
  • Good fault tolerance via HDFS replication
  • No native real-time processing (requires external tools like Apache Storm)
  • Machine learning via external tools like Apache Mahout
  • Best for: large-scale, cost-effective batch jobs




Apache Spark



  • Uses in-memory processing (much faster)
  • Supports batch, real-time, and streaming workloads
  • Easier to use with high-level APIs (Scala, Python, Java, R)
  • Efficient fault tolerance using RDD lineage
  • Built-in Spark Streaming and Structured Streaming
  • Includes MLlib for machine learning
  • Best for: fast, iterative tasks, real-time analytics, and machine learning



From Blogger iPhone client

ITIL applications

Here’s a list of popular ITIL (Information Technology Infrastructure Library) tools that help organizations manage IT services based on ITIL best practices. These tools typically support incident, problem, change, configuration, and service level management, among other ITSM functions.





Top ITIL-Compliant Tools




1. ServiceNow



  • Type: Cloud-based ITSM suite
  • Features: Incident, change, CMDB, knowledge management, workflows, automation
  • Strengths: Highly customizable, strong ecosystem, AI features




2. BMC Helix (Remedy)



  • Type: Enterprise-grade ITSM platform
  • Features: Full ITIL support, cognitive automation, AIOps, service desk
  • Strengths: Suitable for large enterprises, strong CMDB & integrations




3. Ivanti Neurons for ITSM



  • Type: Modular ITSM tool
  • Features: Incident, problem, change, asset management
  • Strengths: Low-code customization, flexible deployment (cloud/on-prem)




4. ManageEngine ServiceDesk Plus



  • Type: ITSM for SMBs and enterprises
  • Features: ITIL-ready modules, asset tracking, self-service portal
  • Strengths: Cost-effective, user-friendly




5. Jira Service Management (Atlassian)



  • Type: Agile-friendly ITSM
  • Features: Incident & change management, automation, integrations with Jira
  • Strengths: Great for DevOps and agile environments




6. Freshservice (by Freshworks)



  • Type: Cloud-native ITSM tool
  • Features: Service catalog, incident, problem, change management
  • Strengths: Simple UI, fast setup, good for mid-sized teams




7. Cherwell (now Ivanti)



  • Type: ITSM platform
  • Features: ITIL-aligned modules, flexible workflow engine
  • Strengths: Customizable without code, used in regulated industries




8. SolarWinds Service Desk



  • Type: ITSM + asset management
  • Features: Incident, change, SLA tracking, reporting
  • Strengths: Integrates well with SolarWinds monitoring tools






Open Source / Lightweight Alternatives



  • GLPI: Open-source ITSM suite with ITIL-aligned features
  • OTRS: Free version supports incident management and basic workflows
  • Snipe-IT: Focused on asset management, can be paired with ticket systems





Would you like a comparison table with pricing, ITIL support levels, or hosted vs. on-premise options?


From Blogger iPhone client

787 a check c check

Sure — a C-check for a Boeing 787-8 Dreamliner is a part of the aircraft’s scheduled maintenance program, typically performed every 20–24 months or after a set number of flight hours/cycles, depending on the airline’s maintenance planning document (MPD) and regulatory authority (e.g., FAA or EASA).


Here’s an outline of a typical C-check inspection checklist for a Boeing 787-8:





C-Check Inspection Overview – Boeing 787-8




1. Airframe Inspection




  • Fuselage: Structural inspection for cracks, dents, corrosion.
  • Doors & Windows: Latches, seals, hinges, and pressure integrity.
  • Wings & Empennage: Spars, ribs, skin panels.
  • Landing Gear: Struts, actuators, tires, brakes, and uplock mechanisms.




2. Flight Control Systems




  • Surfaces: Elevators, rudders, ailerons – hinges, linkages, and actuators.
  • Fly-by-wire system checks: Software versioning, signal verification.




3. Engines and Nacelles (GEnx or Trent 1000)




  • Engine mounts, fire detection systems, and pylon attachments.
  • Fan blades and internal borescope inspection.
  • Oil, hydraulic, and fuel leak inspection.




4. Electrical and Avionics Systems




  • Check power distribution units (PDUs) and Integrated Modular Avionics (IMA).
  • Verify communication, navigation, and surveillance systems.
  • Battery inspection (especially lithium-ion on 787s).




5. Environmental Control System (ECS)




  • Cabin air system, packs, bleed air systems.
  • Humidity control and cabin pressure monitoring.




6. Fuel System




  • Tanks, pumps, venting systems, and fuel quantity indication.
  • Inspections for microbial growth and seal integrity.




7. Hydraulics




  • Check for leakage, pressure stability, accumulator pre-charge.
  • Inspect flight control actuators and hydraulic power transfer units (PTUs).




8. Auxiliary Power Unit (APU)




  • Operational check and borescope inspection.
  • Check fire detection/suppression systems.




9. Cabin and Interior




  • Inspection and functional check of seats, lavatories, oxygen systems.
  • Smoke detectors, emergency lighting, and PA systems.




10. Software and Aircraft Health Monitoring




  • Updates to flight control and system management software.
  • Review health monitoring logs (e.g., Boeing Airplane Health Management system).






Documentation & Certification




  • Logbook entries and sign-offs by certified maintenance engineers.
  • Compliance with Airworthiness Directives (ADs) and Service Bulletins (SBs).
  • Update maintenance tracking systems (e.g., TRAX, AMOS, or Maintenix).





This is a generalized checklist — each airline customizes it based on their Approved Maintenance Program (AMP) and Boeing’s Maintenance Planning Data (MPD).


From Blogger iPhone client



Absolutely. An A-check is a lighter and more frequent maintenance check compared to the C-check. It’s part of the routine maintenance schedule for commercial aircraft, including the Boeing 787-8, and helps ensure airworthiness between more intensive checks.





A-Check Overview – Boeing 787-8




Frequency



  • Typically every 500–750 flight hours, or about 6–8 weeks, depending on the airline’s maintenance schedule and utilization.
  • Takes around 6–24 hours to complete.
  • Often done overnight at an airport maintenance base (line maintenance hangar).






Typical A-Check Task Categories




1. General Visual Inspections



  • Fuselage & Wing Surfaces: Exterior panels for dents, cracks, fluid leaks, missing fasteners.
  • Landing Gear & Tires: Wear, tire pressure, brake wear pins, hydraulic leaks.
  • Cargo Doors & Passenger Doors: Latches, seals, and proper operation.




2. Systems & Component Checks



  • Hydraulics: Reservoir levels, leaks, pressure checks.
  • Electrical Systems: Battery condition, generator load checks.
  • Avionics: Functional tests of nav, comm, and flight management systems.




3. Cabin & Emergency Equipment



  • Oxygen Systems: Bottle pressure, masks, and deployment mechanisms.
  • Fire Extinguishers & Emergency Lighting: Pressure, expiry, and functionality.
  • Seats, Belts, Lavatories: General condition and secure fittings.




4. Engines & APU



  • Fan Blade Visual Inspection: FOD (foreign object damage), nicks.
  • Oil Level Checks: Top-off as needed.
  • Filter Inspections: Bypass indicators and replacements if needed.




5. Software & Diagnostics



  • Check for error messages from the Aircraft Condition Monitoring System (ACMS) or Airplane Health Monitoring (AHM).
  • Update minor software packages if required (787s have extensive avionics software).






Typical Deliverables Post A-Check



  • Signed maintenance log entries.
  • Updates to the aircraft’s digital maintenance tracking system.
  • Rectification of any deferred defects (MEL/CDL items).






Tools & Systems Involved



  • Electronic Flight Bag (EFB) for recording tasks.
  • Maintenance software like TRAX, AMOS, or Maintenix.
  • Use of 787-specific GSE (Ground Support Equipment) and remote diagnostics tools.






Difference Between A-Check and C-Check



Building SSIS package

building an end-to-end SSIS (SQL Server Integration Services) data pipeline. This tutorial covers extracting data from a source, transforming it, and loading it into a destination — commonly known as ETL (Extract, Transform, Load).





End-to-End SSIS Data Pipeline Tutorial




Scenario



You want to extract customer data from a flat file (CSV), transform the data (e.g., clean and format), and load it into a SQL Server database.





Prerequisites




  • SQL Server and SQL Server Data Tools (SSDT) installed (Visual Studio with SSIS project template).
  • Sample source file (CSV).
  • A destination SQL Server database/table to load data into.






Step 1: Create an SSIS Project




  1. Open Visual Studio.
  2. Click Create a new project.
  3. Select Integration Services Project, then click Next.
  4. Name your project (e.g., CustomerETLPipeline) and choose a location.
  5. Click Create.






Step 2: Create a Data Flow Task




  1. In Solution Explorer, open Package.dtsx.
  2. In the Control Flow tab, drag a Data Flow Task onto the canvas.
  3. Double-click the Data Flow Task to switch to the Data Flow tab.






Step 3: Add a Source (CSV File)




  1. In the Data Flow tab, drag a Flat File Source to the canvas.
  2. Double-click it to configure:

  3. Click New to define a flat file connection.
  4. Browse to your CSV file and configure the column delimiter, header row, etc.
  5. Click OK.






Step 4: Add Data Transformations (Optional)



Depending on your needs, drag any of the following:



  • Derived Column – to create new columns or transform data.
  • Data Conversion – to convert data types.
  • Conditional Split – to branch data flow based on conditions.
  • Lookup – to enrich data from another source.



Example:



  1. Drag a Derived Column transform.
  2. Connect it to the Flat File Source.
  3. Double-click it to create expressions like trimming strings, calculating fields, etc.






Step 5: Add a Destination (SQL Server)




  1. Drag an OLE DB Destination to the canvas.
  2. Connect it to your transformation or source.
  3. Double-click to configure:

  4. Click New to create a new OLE DB Connection Manager.
  5. Connect to your SQL Server database.
  6. Choose the destination table or create a new one.
  7. Map the input columns to destination columns.






Step 6: Execute and Test the Package




  1. Press F5 to execute the package.
  2. Monitor the progress via green/red icons.
  3. Check the destination table in SQL Server to ensure data is loaded.






Step 7: Deploy the Package (Optional)



To schedule or run the package outside of Visual Studio:



  1. Use Integration Services Catalog to deploy the package to SQL Server.
  2. Use SQL Server Agent to schedule execution.






Best Practices




  • Use configurations or parameters for file paths and connection strings.
  • Log errors using SSIS logging.
  • Handle data quality issues during transformation.
  • Validate data types to avoid truncation or type mismatch errors.





Would you like this tutorial turned into a downloadable PDF, or should I tailor it to a more specific use case (e.g., API source, Excel, cloud DB)?


From Blogger iPhone client


Certainly! If you want SSIS to dynamically pick a file with a specific prefix (e.g., Customer_*.csv), you’ll need to use a Script Task in the Control Flow to search for that file and store its path in a variable, which the Flat File Connection Manager will then use.


Here’s how to insert this step into your pipeline:





[Updated Step] 2.1: Dynamically Pick a File with a Certain Prefix




Goal:



Pick a file from a directory with a specific prefix (e.g., Customer_*.csv), and pass its full path to the Flat File Connection Manager.





A. Add a SSIS Variable



  1. Go to SSIS > Variables (or press Ctrl+K).
  2. Create a new variable:
  3. Name: SourceFilePath
  4. Data Type: String
  5. Value: Leave blank (to be filled dynamically)






B. Add a Script Task in Control Flow



  1. In the Control Flow, drag a Script Task above your Data Flow Task.
  2. Double-click it, and in the Script Task Editor:
  3. Click Edit Script.
  4. Use the following code in Main():






public void Main()

{

  string folderPath = @"C:\Data\"; // Update this path

  string prefix = "Customer_";

  string[] files = Directory.GetFiles(folderPath, prefix + "*.csv");


  if (files.Length > 0)

  {

    Dts.Variables["User::SourceFilePath"].Value = files[0];

    Dts.TaskResult = (int)ScriptResults.Success;

  }

  else

  {

    Dts.TaskResult = (int)ScriptResults.Failure;

  }

}




Certainly! If you want SSIS to dynamically pick a file with a specific prefix (e.g., Customer_*.csv), you’ll need to use a Script Task in the Control Flow to search for that file and store its path in a variable, which the Flat File Connection Manager will then use.


Here’s how to insert this step into your pipeline:





[Updated Step] 2.1: Dynamically Pick a File with a Certain Prefix




Goal:



Pick a file from a directory with a specific prefix (e.g., Customer_*.csv), and pass its full path to the Flat File Connection Manager.





A. Add a SSIS Variable



  1. Go to SSIS > Variables (or press Ctrl+K).
  2. Create a new variable:
  3. Name: SourceFilePath
  4. Data Type: String
  5. Value: Leave blank (to be filled dynamically)






B. Add a Script Task in Control Flow



  1. In the Control Flow, drag a Script Task above your Data Flow Task.
  2. Double-click it, and in the Script Task Editor:
  3. Click Edit Script.
  4. Use the following code in Main():





By default, the example processes only the first matching file (files[0]). If there are multiple files with the same prefix (e.g., Customer_202504.csv, Customer_202505.csv), only the first one will be processed unless you modify the pipeline to loop through all matching files.



To Process Multiple Files: Use a 

Foreach Loop Container



Here’s how you can enhance your SSIS package to process all files matching a prefix:





[New Step] Use Foreach Loop to Process Multiple Matching Files




1. Add a Variable



Create a string variable:


  • Name: SourceFilePath
  • Scope: Package level
  • Data Type: String






2. Add a Foreach Loop Container



  1. In the Control Flow, drag a Foreach Loop Container.
  2. Double-click it to configure:
  3. Collection tab:
  4. Enumerator: Foreach File Enumerator
  5. Folder: C:\Data\ (your folder path)
  6. Files: Customer_*.csv
  7. Check “Fully qualified” file name
  8. Variable Mappings tab:
  9. Map Index 0 to the User::SourceFilePath variable






3. Move the Data Flow Task Inside the Loop



Drag your Data Flow Task inside the Foreach Loop Container so it runs once per file.





4. Set the Flat File Connection to Use the Variable



  1. Open your Flat File Connection Manager.
  2. Go to Properties > Expressions.
  3. Set the ConnectionString property to:




@[User::SourceFilePath]






Now each time the loop iterates, SourceFilePath gets updated, and the connection manager reads the correct file.





Result



The pipeline will:


  • Iterate through all files with the prefix Customer_
  • Load each file using the Data Flow Task
  • Process them one at a time





Would you like me to generate a visual flow diagram for this setup?





Canadian

Airline

Fleet Size

Fleet Highlights

Air Canada

166

Mix of Airbus A220, A320 family, Boeing 737 MAX, 777, 787, and Embraer E175 aircraft

WestJet

138

Boeing 737 series, 787 Dreamliners, and Bombardier Q400s via WestJet Encore

Porter Airlines

71

29 De Havilland Dash 8-400 and 42 Embraer E195-E2 aircraft

Air Transat

44

All-Airbus fleet: A310, A321ceo, A321LR, and A330 aircraft

Sunwing Airlines

23

Boeing 737-800 and 737 MAX 8 aircraft

Flair Airlines

20

Boeing 737-800 and 737 MAX 8 aircraft

PAL Airlines

20

Dash 8-100/300, Saab 340, and Beechcraft 1900D aircraft

Pacific Coastal Airlines

28

Saab 340, Beechcraft 1900, and Grumman Goose aircraft

Calm Air

14

ATR 42/72 and Boeing 737 aircraft

Canadian North

32

Boeing 737-200/300/400, ATR 42/72, and Dash 8 aircraft

From Blogger iPhone client

Aircraft A Checks C Checks

Of course! Here’s a clear list of A-checks and C-checks typically done for an aircraft. I’ll make it structured and easy to follow:





A-Check (every ~400–600 flight hours or 200–300 cycles)



Light maintenance, usually done overnight or during short downtime.



General A-Check Items:



  • Visual inspection of fuselage, wings, landing gear.
  • Lubrication of key parts (hinges, actuators, etc.).
  • Operational checks of emergency equipment (oxygen bottles, fire extinguishers).
  • Cabin interior check (seats, belts, lavatory systems).
  • Inspection of fluid levels (oil, hydraulic fluid, potable water).
  • Tire and brake inspection.
  • Avionics system functional check.
  • Lighting systems check (internal and external).
  • Minor software updates (if applicable).
  • Fuel leak checks.
  • Drain water separators and sumps.
  • Replacement of filters (air conditioning, hydraulics).
  • Battery condition inspection and servicing.






C-Check (every ~20–24 months or specified flight hours/cycles)



Much deeper inspection, aircraft out of service for 1–2 weeks typically.



General C-Check Items:



  • Detailed structural inspection (using borescopes, non-destructive testing like ultrasonic or X-ray methods).
  • Comprehensive system checks (hydraulics, pneumatics, avionics, flight control systems).
  • Full landing gear inspection and servicing (may involve partial disassembly).
  • Interior refurbishment (carpets, panels, seats removal for inspection).
  • Corrosion inspection and treatment.
  • Electrical wiring checks and potential rewiring.
  • Pressure bulkhead and door seal inspections.
  • Engine and APU (Auxiliary Power Unit) inspections (sometimes off-wing checks).
  • Removal and inspection of flight control surfaces (rudder, elevators, ailerons).
  • Update or modification of airworthiness directives (ADs) or service bulletins (SBs).
  • Detailed fuel tank inspection (including opening of tank access panels).
  • Full operational tests of backup and redundant systems.
  • Replacement of life-limited parts nearing expiration.





Would you also like a simple table version you can use for easy tracking or reporting?

I can format it nicely for you if you want!


From Blogger iPhone client

YouTube to text

https://youtube.com/shorts/iQydw-MgwNI?si=2RNZvp7D-nIAJ2cd

From Blogger iPhone client

Drone analysis of aviation

The URL shown in your screenshot is:


https://donecle.com/products/#Iris_3D


This link takes you to the Donecle website, specifically the product section for Iris dentCHECK.


Would you also like me to give you a quick summary of what Iris dentCHECK does based on that page?


From Blogger iPhone client

Sidra IRB

Sidra Medicine’s Institutional Review Board (IRB) is a pivotal entity ensuring the ethical conduct of human subject research within the institution. It operates under the guidelines set forth by the Ministry of Public Health (MoPH) in Qatar and adheres to international standards such as the Belmont Report and the International Conference on Harmonization Good Clinical Practice (ICH-GCP) guidelines.



🔍 Overview of Sidra Medicine’s IRB




  • Ethical Oversight: The IRB is responsible for reviewing all human subject research conducted at Sidra Medicine, regardless of funding source, to ensure the protection of participants’ rights, dignity, welfare, and privacy. 
  • Compliance: Sidra Medicine’s IRB policies and procedures align with MoPH’s regulations and international ethical standards, ensuring that research activities meet both local and global requirements.
  • Review Authority: The IRB has the authority to approve, require modifications in, or disapprove research activities involving human subjects. This includes initial reviews, continuing reviews, and the assessment of any changes to approved research protocols. 
  • Informed Consent: A key aspect of the IRB’s function is to ensure that informed consent is obtained from all research participants or their legal guardians, with special considerations for vulnerable populations such as children.




📋 Submission and Approval Process




  1. Protocol Submission: Researchers must submit their study protocols, informed consent documents, and any other relevant materials to the IRB for review.
  2. Ethical Review: The IRB reviews submissions to assess the ethical implications, potential risks, and benefits to participants, ensuring that the study complies with ethical standards. 
  3. Approval: Upon satisfactory review, the IRB grants approval for the study to proceed. Researchers must obtain this approval before initiating any research activities involving human subjects.
  4. Ongoing Oversight: The IRB conducts continuing reviews of approved studies, monitors compliance, and reviews any proposed changes to the research protocols.




📞 Contact Information




  • IRB Registration: Sidra Medicine’s IRB is registered with the MoPH under the code IRB-SIDR-2020-009, with the current registration valid until September 10, 2027. 
  • IRB Chairperson: Dr. Ayman Saleh 
  • Contact Email: asaleh2@sidra.org 



For more detailed information on the IRB’s policies, submission guidelines, and procedures, please visit Sidra Medicine’s Clinical Research page: Sidra Medicine Clinical Research.


If you require assistance with the IRB submission process or have specific questions about conducting research at Sidra Medicine, feel free to ask!


From Blogger iPhone client


Dr. Ayman Saleh is a distinguished physician and researcher specializing in pediatric hematology, oncology, and bone marrow transplantation. He currently serves as the Division Chief of Pediatric Hematology-Oncology & Bone Marrow Transplant at Sidra Medicine in Doha, Qatar. In addition to his clinical leadership, Dr. Saleh holds the position of Chairman of the Institutional Review Board (IRB) at Sidra Medicine, where he oversees the ethical conduct of clinical research within the institution. 


With over three decades of experience in pediatric medicine, Dr. Saleh has held multiple leadership roles throughout his career. Prior to joining Sidra Medicine in 2017, he served as the Division Chief of Pediatric Hematology Oncology from 1998 to 2011 and as the Medical Director and Chairman of the Department of Pediatrics from 2005 to 2007. His extensive experience includes chairing various committees such as the cancer care committee, credentialing committee, pediatric academic review committee, pediatric executive committee, standing committee of the board, and professional affairs committee. 


Dr. Saleh is also an active researcher and has been a full member of the international Children’s Oncology Group (COG) since its inception in 2000. He has conducted numerous clinical trials and received multiple grants focusing on childhood cancer, hemophilia, hemoglobinopathies, and supportive care. His contributions to the field have been recognized with several awards, including the American Cancer Society Fellowship Award, Children’s Miracle Network Award, and the Hemophilia Grant Award funded by the Maternal and Child Health Bureau and the Centers for Disease Control and Prevention of the U.S. 


For more detailed information about Dr. Ayman Saleh’s professional background and contributions, you can visit his profile on Sidra Medicine’s official website: .


Building CRO in Middle East

To operationalize a Contract Research Organization (CRO) in Qatar, it’s essential to engage with specific regulatory and institutional bodies that oversee clinical research activities. Below is a structured guide to the key entities and steps involved:





🏛️ Key Regulatory and Institutional Bodies in Qatar



  1. Ministry of Public Health (MoPH) – Health Research Governance Department
  2. Role: Primary regulatory authority for clinical research in Qatar. Responsible for approving clinical trials and ensuring compliance with ethical and scientific standards.
  3. Requirements:
  4. Obtain approval from the MoPH before initiating any clinical trial.
  5. Ensure the research institution is accredited by the Health Research Governance Department.
  6. Maintain a registered Institutional Review Board (IRB) under the Health Research Governance Department.
  7. Application Process:
  8. Submit an application form for clinical trial approval.
  9. Provide an approval letter from the IRB.
  10. Include a recommendation letter from the Data Safety and Monitoring Committee.
  11. Attach the clinical trial protocol and informed consent form.
  12. Reference:  
  13. Institutional Review Boards (IRBs) / Independent Ethics Committees (IECs)
  14. Role: Review and approve clinical trial protocols to ensure the protection of human subjects.
  15. Requirements:
  16. All clinical trials must receive prior approval from a registered IRB/IEC.
  17. Ensure compliance with ethical principles originating from the Declaration of Helsinki and Good Clinical Practice (GCP) guidelines.
  18. Reference:  
  19. Hamad Medical Corporation (HMC)
  20. Role: Qatar’s largest public healthcare provider and a significant site for clinical research.
  21. Requirements:
  22. Collaborate with HMC for access to clinical trial sites and patient populations.
  23. Engage with HMC’s research administration for support and guidance on conducting research within their facilities.
  24. Reference:  
  25. Sidra Medicine
  26. Role: Specializes in pediatric and maternal health research.
  27. Requirements:
  28. Coordinate with Sidra’s IRB for studies conducted within their institution.
  29. Focus on clinical trials that benefit children in the Arab region, particularly those with rare diseases.
  30. Reference:  






✅ Steps to Operationalize a CRO in Qatar



  1. Institutional Accreditation
  2. Ensure your CRO is accredited by the MoPH’s Health Research Governance Department.
  3. Register your Institutional Review Board (IRB) under the same department. 
  4. Protocol Development
  5. Design clinical trial protocols adhering to ICH-GCP guidelines and ethical standards.
  6. Prepare comprehensive documentation, including informed consent forms and data management plans.
  7. Ethical Approval
  8. Submit the clinical trial protocol to a registered IRB/IEC for ethical review and approval. 

  9. Regulatory Submission
  10. Apply for clinical trial approval through the MoPH, providing all necessary documentation and approvals.

  11. Site Collaboration
  12. Establish partnerships with institutions like HMC and Sidra Medicine for access to research sites and patient populations. 

  13. Compliance and Monitoring
  14. Implement quality management systems to ensure ongoing compliance with regulatory requirements.
  15. Conduct regular audits and monitoring of clinical trial activities.





By engaging with these key bodies and following the outlined steps, you can effectively establish and operate a CRO in Qatar, ensuring compliance with local regulations and contributing to the advancement of clinical research in the region.


From Blogger iPhone client

Building CRO

Building a Contract Research Organization (CRO) service requires a mix of scientific expertise, regulatory knowledge, operational efficiency, and client-centric business development. Here are the key elements to focus on:



1. Service Portfolio Design

• Core Services: Clinical trials (Phase I–IV), regulatory affairs, data management, biostatistics, medical writing, site monitoring.

• Specialized Services: Pharmacovigilance, bioanalytical lab services, patient recruitment, decentralized trials, etc.

• Therapeutic Focus: Oncology, neurology, rare diseases, etc., depending on your expertise.



2. Regulatory Compliance

• Adherence to ICH-GCP, FDA, EMA, and local health authority regulations.

• Ensure processes align with 21 CFR Part 11 (electronic records/signatures).



3. Talent & Expertise

• Hire clinical research professionals, project managers, data scientists, regulatory specialists, and medical experts.

• Emphasize continuous training and certifications (e.g., GCP, CRA, PMP).



4. Technology Infrastructure

• Clinical Trial Management System (CTMS)

• Electronic Data Capture (EDC)

• Randomization and Trial Supply Management (RTSM)

• AI-powered tools for patient recruitment, trial design, and remote monitoring.



5. Quality Management System (QMS)

• Develop SOPs for all functions.

• Implement audit trails, CAPA systems, and risk-based monitoring.



6. Site Network & Patient Access

• Build relationships with hospitals, clinics, and investigators.

• Consider strategic partnerships or alliances to access global sites.



7. Business Development & Partnerships

• Offer competitive pricing, flexible models (full-service or FSP).

• Build long-term relationships with sponsors—biotech, pharma, or academia.



8. Data & Security Infrastructure

• Ensure data integrity, HIPAA/GDPR compliance, and robust cybersecurity.

• Leverage real-world data and eSource technologies for speed and quality.



9. Global Reach & Localization

• If aiming for global trials, ensure regional regulatory expertise and multilingual teams.

• Understand cultural, logistic, and regulatory differences across geographies.



10. Reputation & Trust

• Demonstrate success via case studies, KOL endorsements, and trial performance metrics.

• Maintain transparency and ethical practices.



Would you like a sample org structure or roadmap to launch a CRO startup?


From Blogger iPhone client

Pharmaceutical and adoption of AI

Pharmaceutical companies are increasingly leveraging AI to accelerate clinical trials, improve success rates, and reduce costs. Here’s how they’re doing it:



1. 

Patient Recruitment & Matching




  • AI models analyze electronic health records (EHRs), genetic data, and demographics to identify eligible patients faster.
  • Natural language processing (NLP) helps extract relevant info from unstructured medical data.




2. 

Trial Design Optimization




  • AI simulates trial scenarios to help design smarter protocols—choosing endpoints, dosage, duration, and patient groups more effectively.
  • Machine learning can predict trial feasibility based on historical data and site performance.




3. 

Site Selection and Monitoring




  • AI predicts which trial sites will recruit and retain patients most effectively.
  • Real-time data monitoring with anomaly detection flags issues early (e.g., adverse events, protocol deviations).




4. 

Predictive Analytics for Outcomes




  • AI predicts patient response and early signs of efficacy or failure, allowing for faster go/no-go decisions.
  • Digital twins and predictive biomarkers help in adaptive trial design.




5. 

Decentralized Clinical Trials (DCT)




  • AI enables remote monitoring using wearables, mobile apps, and telemedicine.
  • Automates data collection and improves patient adherence and retention.




6. 

Natural Language Processing (NLP) for Data Extraction




  • Speeds up regulatory documentation, medical coding, and adverse event reporting.
  • Automates clinical trial result summarization and submission generation.



Would you like a real-world case study or visual summary of these applications?


From Blogger iPhone client



Several medications are employed to control bleeding in critical situations such as pregnancy-related hemorrhage and hemorrhagic strokes. Below is an overview of key drugs used in these scenarios, along with information about the pharmaceutical companies that produce them and their recent annual revenues.





Medications for Controlling Bleeding




1. 

Tranexamic Acid (TXA)



  • Use: Antifibrinolytic agent used to reduce bleeding in various conditions, including postpartum hemorrhage and trauma-related bleeding.
  • Manufacturers: Pfizer Inc., Teva Pharmaceutical Industries Ltd., and other generic drug manufacturers. 




2. 

Oxytocin



  • Use: Hormone used to induce labor and control postpartum bleeding by stimulating uterine contractions.
  • Manufacturers: Novartis AG, Pfizer Inc., and various generic pharmaceutical companies.




3. 

Misoprostol



  • Use: Prostaglandin analog used to prevent and treat postpartum hemorrhage and for medical management of miscarriage.
  • Manufacturers: Pfizer Inc., Teva Pharmaceutical Industries Ltd., and other generic manufacturers. 




4. 

Recombinant Activated Factor VII (rFVIIa)



  • Use: Promotes hemostasis in patients with hemophilia and is sometimes used off-label for severe bleeding, including intracerebral hemorrhage.
  • Manufacturer: Novo Nordisk A/S.




5. 

Desmopressin (DDAVP)



  • Use: Synthetic hormone used to treat bleeding disorders such as mild hemophilia A and von Willebrand disease by increasing levels of clotting factors.
  • Manufacturers: Ferring Pharmaceuticals, Teva Pharmaceutical Industries Ltd., and others.






Pharmaceutical Companies and Annual Revenues



Here are some of the major pharmaceutical companies producing these medications, along with their reported revenues:


Aviation industry and Bloomberg

Bloomberg Data Services is a suite of tools and APIs provided by Bloomberg that offer access to a wide range of financial, economic, and alternative datasets. These services are typically consumed through:


  • Bloomberg Terminal (Desktop access)
  • Bloomberg Data License (BDL)
  • Bloomberg REST API / SAPI / Python SDK
  • Managed services (feeds, reference data, pricing, etc.)






Types of Data Offered



  • Market data: Real-time and historical pricing for securities (equities, fixed income, FX, derivatives, commodities)
  • Reference data: Security master data, identifiers, corporate actions, and metadata
  • Economic data: Country-level indicators, inflation rates, GDP, employment stats
  • Alternative data: ESG scores, sentiment, satellite insights, etc.
  • FX and interest rate curves
  • News and financial events






How Airlines Can Benefit from Bloomberg Data



Even though Bloomberg primarily targets financial services, airlines and related industries can also gain significant value, especially in areas like fuel risk management, financial planning, and strategic decisions.



1. Fuel Hedging & Risk Management



  • Jet fuel prices and crude oil futures data help airlines monitor price volatility.
  • Use Bloomberg curves and real-time data to:
  • Build hedging strategies (swaps, futures)
  • Manage exposure to commodity price movements
  • Monitor FX impact on fuel purchases




2. Macroeconomic & Geopolitical Analysis



  • Access macroeconomic indicators to anticipate travel demand or route profitability:
  • Consumer confidence
  • GDP growth
  • Interest and inflation rates
  • Geopolitical news and risk signals to adapt operations (e.g., avoid volatile regions, anticipate regulatory changes)




3. FX Risk Management



  • Airlines operating across multiple regions can use:
  • Real-time FX rates
  • Historical trends
  • Volatility metrics
  • Helps in pricing tickets, settling contracts, and managing currency exposure




4. Competitor and Industry Benchmarking



  • Use equity and financial data to track:
  • Airline peers’ financial health (debt levels, stock performance, margins)
  • Industry benchmarks and valuation multiples
  • Useful for investor relations, M&A strategy, or pricing models




5. ESG and Carbon Emissions Data



  • Access to ESG scores, carbon metrics, and sustainability disclosures.
  • Helps align with regulatory or investor expectations on sustainability.




6. Financing & Treasury



  • Monitor interest rate curves, bond yields, and credit ratings for:
  • Issuing debt
  • Optimizing capital structure
  • Managing treasury investments






Summary



While Bloomberg may seem finance-focused, airlines can use its data services for:


  • Fuel and FX hedging
  • Economic forecasting
  • Competitor benchmarking
  • ESG reporting
  • Financing decisions



Want a tailored example, like how a specific airline (e.g., Qatar Airways or Delta) might integrate Bloomberg data into their strategy or systems?


From Blogger iPhone client

Bloomberg data pipeline benefits

Pulling data from the Bloomberg REST API can offer several powerful benefits, especially for financial institutions, investment firms, and enterprises that rely on timely and accurate market data. Here are the key advantages:




1. Real-time and Historical Market Data




  • Access real-time market data (price quotes, market depth, etc.) for equities, bonds, commodities, FX, and more.
  • Retrieve historical data for time series analysis, backtesting, or performance tracking.






2. Wide Coverage of Financial Instruments




  • Bloomberg supports a vast array of instruments including:

  • Equities
  • Fixed income
  • Derivatives
  • Currencies
  • Commodities
  • Economic indicators






3. Automation and Integration




  • Seamlessly integrate Bloomberg data into:

  • Analytics models
  • Dashboards (e.g., Power BI, Tableau)
  • Data warehouses/lakes
  • Trading systems and risk engines






4. Custom Queries and Flexible Data Retrieval




  • Use Bloomberg’s rich data model to customize requests (e.g., specific fields, conditions, filters).
  • Schedule pulls at regular intervals (e.g., end-of-day prices, intraday snapshots).






5. Improved Decision-Making




  • Get up-to-date and high-quality data to inform:

  • Portfolio strategies
  • Risk management
  • Market research
  • Compliance and reporting






6. Cost Efficiency and Performance




  • Reduce dependency on desktop terminals for data exports.
  • Increase speed and consistency of data updates without manual intervention.






7. Enhanced Governance and Auditability




  • API-based access can be monitored and logged for compliance.
  • Data lineage and quality controls become easier to implement and audit.





Would you like to dive into specific use cases like investment research, risk management, or data pipeline design with Bloomberg data?


From Blogger iPhone client

Phone analysis

https://youtube.com/shorts/ssAcCGotDEA?si=_Pe7gky92jvnLO7l


Dial

*#67#


to disable call forqarding

#002#




From Blogger iPhone client

Inspecting robots

https://youtube.com/shorts/QKWm1xQuj-E?si=Iet-01kDTLNCOvEk

From Blogger iPhone client

Ai tools to learn

https://youtube.com/shorts/eFy8tepEByw?si=zXHrpVFaab4Qm-nL

From Blogger iPhone client

Creating levitating magnet applications

https://youtube.com/shorts/smYlhDK-P4o?si=wznkVnn8TgrS3uqI

From Blogger iPhone client

IFS

IFS (Industrial and Financial Systems) offers a robust, aviation-specific software suite designed for airlines, MROs (Maintenance, Repair & Overhaul), and defense aviation operators. It is widely adopted by major global carriers and service providers for maintenance, engineering, asset, and supply chain management.





IFS Applications for Airlines




1. Maintenance, Repair & Overhaul (MRO)



  • Line, Base & Heavy Maintenance Support
  • Schedule, execute, and track all types of aircraft maintenance activities.
  • Component Maintenance
  • Manage overhaul, inspection, and test of rotable and repairable components.
  • Mobile MRO
  • Technicians access real-time work orders and manuals via tablets.






2. Fleet & Asset Management



  • Aircraft Configuration Management
  • Manage and track aircraft, engines, and component lifecycles.
  • Airworthiness & Compliance
  • Automate compliance with EASA, FAA, and other regulations; manage ADs and SBs.






3. Supply Chain Management



  • Inventory Optimization
  • Forecast demand, reduce excess stock, and ensure part availability.
  • Procurement & Logistics
  • Streamline purchase orders, vendor management, and parts logistics.






4. Maintenance Planning & Scheduling



  • Short- and Long-term Maintenance Planning
  • Balance aircraft availability with maintenance schedules.
  • Hangar & Resource Planning
  • Efficiently allocate bays, tools, and personnel.






5. Digital Transformation



  • AI & Predictive Maintenance
  • Integrate IoT sensors and AI algorithms for condition-based maintenance.
  • Integration with Flight Ops
  • Interfaces with flight planning, crew scheduling, and EFB systems.






IFS Airline Clients



IFS is used by a range of commercial and cargo airlines, such as:


  • LATAM Airlines Group
  • Qatar Airways
  • AirAsia Group
  • AAR Corp (as MRO provider)
  • Bristow Group
  • Cape Air
  • PSA Airlines (subsidiary of American Airlines)






Deployment Options



  • Cloud-based SaaS
  • On-premise installations
  • Hybrid models for data-sensitive operations





Would you like a comparison between IFS and other aviation systems like AMOS or AVIATAR? Or a breakdown of how it integrates with Oracle/SAP or BI tools?


From Blogger iPhone client

Aviator aviation

AVIATAR, developed by Lufthansa Technik, is a cloud-based digital platform designed to enhance airline operations by offering a suite of modular applications. These applications focus on predictive maintenance, real-time aircraft health monitoring, and streamlined technical operations. AVIATAR integrates data from various sources, including aircraft systems and maintenance records, to provide actionable insights that help airlines optimize their operations and reduce unscheduled interruptions.





✈️ Airlines Utilizing AVIATAR



Several airlines worldwide have adopted AVIATAR to improve their operational efficiency:


  • LATAM Airlines Group: Implemented AVIATAR across its Airbus A320, Boeing 777, and Boeing 787 fleets, totaling over 300 aircraft. The airline utilizes AVIATAR’s Predictive Health Analytics to transform data into actionable insights, optimizing technical operations and minimizing unexpected disruptions. Additionally, AVIATAR’s Electronic Technical Logbook digitizes cockpit-to-maintenance communication, improving efficiency.  
  • United Airlines: Adopted AVIATAR for its Boeing 777 and Airbus A320 fleets, with plans to develop new predictive maintenance solutions for its Boeing 737 fleet. The integration aims to provide tech-ops professionals with data and recommendations to optimize operations and reduce maintenance-related delays.  
  • ASL Aviation Holdings: ASL’s European airlines have adopted AVIATAR’s Electronic Technical Logbook solution to replace existing paper-based processes, enhancing efficiency and data accuracy.  
  • Eurowings: Introduced AVIATAR’s Electronic Technical Logbook, which offers prefilled text blocks and automated input masks to capture technical issues during flight and on the ground, replacing manual entries and improving data quality.  






🧠 Key Features of AVIATAR



  • Predictive Health Analytics (PHA): Utilizes live data from aircraft systems to predict potential technical issues before they occur, enhancing operational reliability and reducing unplanned maintenance events.  
  • Electronic Technical Logbook (ETL): Digitizes the process of capturing technical issues, allowing for real-time data availability and seamless collaboration between pilots and maintenance teams.  
  • Technical Repetitives Examination (TRE): An AI-based tool that analyzes recurring defects within aircraft technical logbook write-ups, making them more transparent and easier to monitor.  
  • Engineering Analytics Suite: Part of AVIATAR’s Reliability Solutions, this suite enables users to create live data dashboards for fleet performance indicators, supporting root-cause analysis and authority reports.  





AVIATAR’s modular design allows airlines to select and integrate applications that best fit their operational needs, contributing to improved efficiency, reduced costs, and enhanced safety in airline operations.


From Blogger iPhone client

Amos aviation

Swiss AviationSoftware’s AMOS (Aircraft Maintenance and Engineering System) is a comprehensive MRO (Maintenance, Repair, and Overhaul) software solution utilized by over 220 customers worldwide, including commercial airlines, cargo carriers, MRO providers, and aircraft manufacturers. 



Notable AMOS Clients



Here are some of the prominent organizations currently using AMOS:


  • Air India – The flag carrier of India, operating a diverse fleet including Airbus A319, A320, A321, A350, and Boeing 777, 787.  
  • Azerbaijan Airlines (AZAL) – The national airline of Azerbaijan, with aircraft such as Airbus A319, A320, A340, Boeing 767, 777, 787, and Embraer 190.  
  • Flair Airlines – A Canadian low-cost carrier headquartered in Edmonton, Alberta, operating Boeing 737 aircraft.  
  • airBaltic – The flag carrier of Latvia, operating Airbus A220 aircraft.  
  • JetSmart Airlines – A South American ultra low-cost carrier based in Santiago, Chile, operating Airbus A320 and A321 aircraft.  
  • Turkish Technic – The maintenance, repair, and overhaul (MRO) center of Turkish Airlines.  
  • Saab AB – A Swedish aerospace and defense company, operating as both an aircraft manufacturer and MRO provider.  
  • Magnetic Group – An aviation company and leading MRO service provider based in Tallinn, Estonia.  
  • Asia Digital Engineering (ADE) – Part of Capital A, specializing in line and base maintenance, component & warehouse services, and engineering support services.  
  • HAECO Global Engine Support – Provides global round-the-clock on-wing and off-wing engine support from strategic locations.  



These clients represent a diverse range of aviation operations, showcasing AMOS’s adaptability to various organizational needs.


For a comprehensive list of AMOS customers, you can visit the Swiss-AS official customer list.


If you’re interested in information about AMOS clients in a specific region, such as North America or Europe, or within a particular segment like cargo or low-cost carriers, feel free to ask!


From Blogger iPhone client

IFS airline

IFS (Industrial and Financial Systems) offers an enterprise-grade aviation solution suite tailored for the aerospace and defense sectors, especially airlines, MRO providers, and military operators. It’s widely used for managing maintenance, engineering, supply chain, and operational efficiency.





Key Features of IFS for Airlines & Aviation




1. Aviation Maintenance Management



  • Line, Base & Heavy Maintenance
  • Schedule and manage all maintenance activities.
  • Real-time tracking of aircraft status and work packages.
  • Mobile Maintenance Support
  • Technicians can view and update work orders via tablets in the field or hangar.




2. Fleet & Asset Management



  • Aircraft Configuration Management
  • Track the entire lifecycle of aircraft, engines, and components.
  • Monitor airworthiness, service bulletins (SBs), and ADs (Airworthiness Directives).
  • Lifecycle Costing
  • Understand cost per flight hour and optimize asset investments.




3. Supply Chain & Inventory



  • Inventory Optimization
  • Forecast parts demand and reduce excess inventory.
  • Parts Tracking
  • Full traceability of parts and tools, with integration into logistics.
  • Warehouse Management
  • Integrated with barcoding and RFID for real-time part visibility.




4. Compliance & Safety



  • Regulatory Compliance
  • Compliant with EASA, FAA, and other global aviation authorities.
  • Maintenance Records
  • Complete digital audit trail and documentation for regulatory checks.




5. MRO and Third-Party Services



  • MRO Provider Module
  • For organizations offering maintenance as a service.
  • Includes quoting, invoicing, and customer contract management.




6. Planning & Optimization



  • Maintenance Planning
  • Long-term and short-term planning to minimize downtime.
  • Resource Management
  • Assign crews, tools, and bays efficiently.






Integration Capabilities



  • IFS can be integrated with:
  • ERP systems like Oracle, SAP, and MS Dynamics.
  • Flight operations systems for live aircraft status.
  • IoT/AI modules for predictive maintenance and performance analytics.






Airlines & Aviation Clients Using IFS



IFS powers systems for major airlines, defense forces, and MROs including:


  • LATAM Airlines
  • Qatar Airways
  • AAR Corp
  • Bristow Group





If you’re considering IFS for a new deployment or integration (like with Oracle Fusion or a BI stack), I can help map out the architecture or provide use-case specific guidance. Let me know how deep you’d like to go.


From Blogger iPhone client

Jeppesen

Jeppesen, a Boeing subsidiary, provides a wide range of digital solutions for the airline and aviation industries, with a strong focus on flight operations, crew management, navigation, and optimization. Here’s a breakdown of their core airline solutions:





1. Flight Planning & Dispatch



  • Jeppesen FliteDeck Pro: A widely used electronic flight bag (EFB) application for pilots, providing charts, NOTAMs, and real-time updates.
  • Jeppesen Flight Planning (JFP): Optimizes routes, fuel consumption, and cost by using advanced algorithms and real-time data.
  • Ops Control: A central platform to monitor and manage operations, from flight dispatch to real-time disruptions.






2. Crew & Operations Management



  • Crew Pairing and Rostering: Advanced optimization tools to build cost-effective crew schedules while ensuring compliance with labor agreements.
  • Crew Tracking: Real-time monitoring and reallocation of crew members during disruptions.
  • Fatigue Risk Management: Tools to evaluate and mitigate pilot fatigue based on scientific models and schedules.






3. Navigation Services



  • Airway Manual Services: Digital and paper-based charts and manuals used for global navigation.
  • Tailored Charts: Custom navigation charts specific to an airline’s operations or aircraft type.
  • Obstacle and Terrain Data Services: Used in flight planning and approach procedures.






4. Training and Qualification Management



  • Training Management Solutions: For tracking pilot and crew training, certification, and compliance.
  • Qualification Tracking: Ensures that only qualified staff are scheduled for operations, reducing compliance risk.






5. Digital Transformation & Optimization



  • Total Mission Optimization (TMO): Integrates data from flight planning, crew management, and maintenance to optimize the overall flight mission.
  • Aviator Suite: A connected, mobile-first suite for flight and ground crew, enhancing situational awareness and operational efficiency.





Jeppesen’s solutions are used by major global airlines, regional carriers, and military aviation units. Let me know if you’re looking for insights into one specific module (like crew management or flight planning), or how to integrate these with existing ERP or MRO systems.


From Blogger iPhone client

Robotics

Aircraft and aviation-related robots are widely used in both military and commercial sectors to enhance safety, efficiency, and productivity. Here are some notable types and use cases:





1. Aircraft Manufacturing Robots



  • Robotic Drilling & Fastening Systems: Used by Boeing and Airbus for precise assembly of fuselage and wings.
  • Composite Layup Robots: Automate the layering of composite materials, critical for lightweight aircraft parts.
  • Painting Robots: Ensure consistent coating while reducing human exposure to hazardous chemicals.






2. Maintenance, Repair, and Overhaul (MRO) Robots



  • Inspection Drones: Used for visual inspection of aircraft surfaces, including fuselage, wings, and tail.
  • Example: EasyJet’s drone for A-check inspections.

  • Ultrasonic Inspection Robots: Non-destructive testing using robotic arms to scan for cracks or corrosion.
  • Robotic Crawlers: Miniature robots that inspect hard-to-reach areas like fuel tanks and ducts.






3. Airport & Ground Operations Robots



  • Baggage Handling Robots: Automate luggage transport to improve efficiency and reduce delays.
  • Autonomous Tugs: Pull aircraft to and from gates without human drivers.
  • Example: TaxiBot, co-developed with Airbus and TLD.

  • Security Robots: Patrol terminals using facial recognition and anomaly detection.






4. In-flight Support and Cabin Service Robots



  • Service Robots: Provide food and beverages or assist with passenger needs.
  • Example: ANA’s “Newme” robot for telepresence assistance.

  • Cleaning Robots: Disinfect cabins between flights using UV-C light or automated spraying.






5. Research & Experimental Robots



  • Swarming UAVs: Tested for formation flying, surveillance, or wingman roles in military aviation.
  • Robotic Co-pilots: AI-based systems that support or replace human copilots in experimental aircraft.





If you’re exploring this for a project or specific use case (like MRO, AI integration, or cost analysis), I can dive deeper into those areas too.






From Blogger iPhone client

Tableau to Microsoft power bi using Pulse converter

Converting Tableau dashboards to Power BI involves recreating visualizations and dashboards in Power BI, replicating calculations, and ensuring data source connections. You can achieve this by exporting Tableau dashboards as images or PDFs, then recreating them in Power BI. Tools like Pulse Convert offer AI-powered automated conversion, while other solutions like Wavicle's Analyzer and Converter help analyze and transform Tableau dashboards. 


Here's a more detailed breakdown:


1. Data and Data Sources: 

  • Establish Data Connections:
  • Connect Power BI to the same data sources used in Tableau (databases, files, web services). 
  • Data Transformation:
  • Use Power Query (Power BI's data transformation tool) to clean, prepare, and transform the data as needed. 

2. Visualizations and Layout: 

  • Recreate Visuals:
  • Recreate the charts, graphs, and other visualizations in Power BI, using the same data and ensuring consistent formatting. 
  • Dashboard Layout:
  • Reproduce the layout of the Tableau dashboard in Power BI, including the positioning and arrangement of visualizations. 
  • Customization:
  • Customize Power BI dashboards to enhance functionality and user experience, while ensuring consistency with the original Tableau dashboard. 

3. Calculations and Logic: 

  • Calculated Fields and LOD Expressions:
  • Translate Tableau calculations and LOD expressions into equivalent DAX formulas in Power BI. 
  • Filters and Interactions:
  • Implement filters and interactions on the Power BI dashboard to match those in the original Tableau dashboard. 

4. Tools and Solutions: 

  • AI-Powered Migration Tools:
  • Tools like Pulse Convert offer AI-powered automation to convert Tableau dashboards to Power BI with high accuracy. 
  • Migration Frameworks:
  • Frameworks like Bristlecone's TPBI (Tableau to Power BI) accelerate the migration process and reduce manual effort. 
  • Migration Services:
  • Companies like Wavicle Data Solutions and Maq Software offer migration services, including tools and expertise to facilitate the transition. 

5. Testing and Validation: 

  • Data Validation:
  • Thoroughly validate the data to ensure accuracy and consistency between Tableau and Power BI. 
  • Performance Testing:
  • Test the performance of the Power BI dashboards to ensure they load quickly and perform efficiently


From Blogger iPhone client

Tableau to Power BI migration

Migrating from Tableau to Power BI is a bit complex due to the differences in their underlying architectures, APIs, and file formats. While there’s no official one-click migration tool from Tableau to Power BI, you can automate parts of the process using Python, REST APIs, and third-party tools.


Here’s a breakdown of what you can do and how to approach building a migration script using Python:





Step 1: Extract Metadata from Tableau



Use the Tableau REST API and Metadata API (GraphQL) to extract workbooks, datasources, and visualization metadata.



Python Example (Tableau Metadata API):






Use Python libraries like gql or requests to send this GraphQL query.





Step 2: Parse and Convert the Metadata



Translate the Tableau metadata into something Power BI understands. This requires custom mapping logic:



  • Tableau Viz → Power BI Visual
  • Tableau Filters → Power BI Slicers
  • Tableau Data Sources → Power BI Dataflows or imported datasets



You can write this logic using pandas or custom JSON translators.





Step 3: Use Power BI REST API to Create Equivalent Artifacts



Power BI’s REST API supports operations like:



  • Creating workspaces
  • Uploading PBIX files
  • Updating datasets
  • Managing reports



However, you cannot programmatically create detailed visuals via REST API alone — that requires Power BI Desktop and the PBIX format.


But you can prepare data and models using:



  • Power BI XMLA endpoint
  • Tabular Editor (for datasets)
  • Power BI Desktop Automation using PowerShell/Python & PBIX Templates






Alternative/Third-party Tooling



Some tools that can help in this migration:



  • Power BI XMLA/Tabular Editor: To create models programmatically.
  • Tableau to Power BI Migration Tool by MAQ Software (limited features).
  • ZappySys ODBC Drivers / ETL tools to extract Tableau data and push to Power BI.
  • Alteryx or KNIME: As middle-layer ETL tools.






Caution




  • Visuals cannot be directly migrated — you’ll need to recreate them.
  • Some calculations (e.g., LOD in Tableau) must be translated manually into DAX.
  • Tableau dashboards (layouts, interactivity) won’t be 1:1 with Power BI.






Want a Starter Script?



If you’re interested, I can generate a Python starter script that:



  • Authenticates with Tableau
  • Extracts workbook metadata
  • Prepares a mapping JSON for Power BI



Let me know how automated you want it (full flow vs metadata only).


From Blogger iPhone client


MAQ Software offers a Tableau to Power BI migration tool called MigrateFAST, which aims to simplify and accelerate the process of transitioning from Tableau to Power BI. This tool, powered by AI, is designed to help businesses migrate large volumes of reports, potentially saving time and resources. 


Key Features and Benefits: 

  • AI-Powered Migration:
  • MigrateFAST utilizes artificial intelligence to automate and expedite the migration process. 
  • Large-Scale Migration:
  • The tool is designed to handle large-scale migrations of reports from Tableau to Power BI. 
  • Time and Cost Savings:
  • By automating the migration, MigrateFAST can reduce the time and resources required, potentially leading to cost savings. 
  • Optimized Conversion:
  • The tool focuses on ensuring high-quality and accurate report conversion during the migration process. 
  • Data Discovery and Exploration:
  • MigrateFAST can help streamline the data discovery and exploration process, allowing for more intuitive and accessible data insights. 
  • 6-Week Implementation:
  • MAQ Software claims to offer a 6-week implementation plan for the migration process. 
  • Expert Support:
  • MAQ Software provides expert support and guidance throughout the migration process. 
  • Other Services:
  • MAQ Software also offers services like performance analysis, report optimization, and adoption training to support the overall migration and adoption of Power BI. 

How MigrateFAST Works: 

MigrateFAST, according to MAQ Software, uses AI to analyze and convert Tableau workbooks (.twbx) to Power BI, simplifying the migration process. It can automate tasks, reduce manual effort, and improve the accuracy of the conversion, ultimately leading to a smoother transition to Power BI. 


For a more detailed understanding of MAQ Software's services and the MigrateFAST tool, it is recommended to visit their website


Pain points migration from oracle to bigquery


1. 

SQL Syntax Differences



  • Oracle uses PL/SQL, while BigQuery uses standard SQL.
  • Key differences in functions, procedures, windowing functions, and error handling often require manual rewriting.






2. 

Stored Procedures & Packages



  • Oracle’s stored procedures, packages, and triggers are deeply embedded in workflows.
  • BigQuery has limited support for procedural logic and doesn’t support packages like Oracle.






3. 

ETL/ELT Reengineering



  • ETL processes built with Oracle-specific tools (e.g., Oracle Data Integrator) must be re-architected using tools compatible with BigQuery (e.g., Dataflow, Cloud Composer, dbt).






4. 

Data Type Mismatches



  • Differences in data types (e.g., NUMBER, DATE, CLOB) between Oracle and BigQuery can cause data fidelity issues during migration.






5. 

Performance Tuning Shift



  • Oracle relies on indexes, partitions, and hints, while BigQuery is serverless and relies on query optimization and table partitioning strategies.
  • Performance tuning paradigms must be relearned.






6. 

Security and Access Control



  • Oracle uses role-based access control and fine-grained access policies, which may not map 1:1 to BigQuery’s IAM model.
  • Requires redesign of data governance policies.






7. 

Migration of Historical Data



  • Large volumes of data, especially if not well-partitioned, can be costly and time-consuming to move.
  • May require staging in Google Cloud Storage and batch load jobs.






8. 

Change Management & User Training



  • Analysts and developers accustomed to Oracle tools need training in BigQuery and associated cloud-native tools.
  • Business users may also need to adapt to new reporting workflows (e.g., from Oracle BI to Looker).






9. 

Integration with Legacy Systems



  • Oracle often integrates tightly with legacy ERP systems and custom apps.
  • BigQuery may require middleware or APIs to maintain similar integrations.






10. 

Cost Management



  • BigQuery uses pay-per-query pricing, which is very different from Oracle’s licensing model.
  • Lack of understanding of cost controls (e.g., materialized views, partitions, byte limits) can lead to unexpected costs.



From Blogger iPhone client

Access to source system raw layer

Data analysts should have access to the raw data layer for several important reasons:



1. 

Data Integrity & Transparency



Access to raw data allows analysts to verify the accuracy and completeness of processed or transformed data. It provides transparency into how data has been cleaned, aggregated, or filtered, which helps identify potential issues in upstream transformations.



2. 

Flexibility in Analysis



The raw layer provides full granularity, enabling analysts to explore data in ways that might not be possible with curated layers. This is crucial when:


  • Investigating anomalies
  • Building custom reports
  • Performing exploratory or ad hoc analysis




3. 

Root Cause Analysis



When data issues arise, analysts often need to trace the data lineage back to its origin. Raw data access enables them to perform root cause analysis without relying entirely on data engineers.



4. 

Creating Custom Logic



Standard transformations might not meet every analytical need. Analysts might need to apply custom logic or business rules not captured in the semantic layer or data marts.



5. 

Speed & Agility



Waiting for engineering teams to expose new data points or fix curated datasets can delay insights. Direct access to raw data allows analysts to move faster, especially in fast-paced or data-driven environments.




Caveat:

While access to raw data is valuable, it should be governed properly:


  • With read-only permissions
  • Clear documentation
  • Training to ensure responsible use



Would you like this rephrased for a presentation or documentation purpose?


From Blogger iPhone client

Asana integration azure devops

Yes, you can integrate Asana with Azure DevOps (ADO) to synchronize tasks, work items, and project data across both platforms. This integration is particularly beneficial for aligning non-technical teams (using Asana) with development teams (using ADO), ensuring seamless collaboration and real-time updates.





🔄 Integration Options




1. 

Unito – Two-Way Sync (No-Code)



Unito offers a robust, no-code integration that enables real-time, two-way synchronization between Asana tasks and Azure DevOps work items. Key features include:


  • Live Sync: Automatic updates between Asana and ADO. 
  • Custom Rules: Define specific conditions for syncing tasks or work items. 
  • Field Mapping: Map fields such as titles, descriptions, assignees, tags, attachments, comments, dates, statuses, priorities, URLs, and custom fields between platforms. 
  • Historical Data Sync: Option to sync existing data between tools. 
  • Enterprise Security: SOC 2 Type 2 certified with strict security measures. 



To set up the integration:


  1. Sign Up: Create an account on Unito. 
  2. Connect Tools: Authorize Unito to access your Asana and Azure DevOps accounts. 
  3. Configure Flow: Set the direction of data flow (one-way or two-way), define rules, and map fields. 
  4. Launch: Activate the integration to start syncing data. 



For a visual guide on setting up this integration, you can watch the following tutorial:






2. 

Zapier – Trigger-Based Automation



Zapier provides a flexible, no-code solution to automate workflows between Asana and Azure DevOps. With Zapier, you can:


  • Create Asana Tasks from ADO Work Items: Automatically generate tasks in Asana when new work items are created in Azure DevOps. 
  • Update Asana Tasks Based on ADO Changes: Reflect updates made in Azure DevOps within corresponding Asana tasks.
  • Map Specific Projects: Link particular Asana projects with corresponding Azure DevOps projects. 



Note that while Zapier supports many triggers and actions, syncing comments between Asana and Azure DevOps is not currently supported.



3. 

Getint – Advanced Integration Platform



Getint offers a comprehensive integration solution with features such as:


  • Field Synchronization: Sync fields including titles, descriptions, assignees, tags, sub-tasks, attachments, comments, dates, statuses, priorities, URLs, and custom fields. 
  • Advanced Filtering: Implement complex rules to control data flow between platforms. 
  • Deployment Options: Choose between SaaS or on-premise deployment to suit your organization’s needs. 
  • Custom Development: Access to custom development and consulting services for tailored integration solutions. 






✅ Choosing the Right Integration Tool



Tool

Best For

Key Features

Unito

Real-time, two-way sync without coding

Live sync, custom rules, field mapping, historical data sync

Zapier

Simple, trigger-based automation

Task creation, project mapping, status updates

Getint

Advanced, customizable integrations

Comprehensive field sync, advanced filtering, deployment flexibility




Yes, you can use Power Automate to synchronize between Asana and Azure DevOps, but with some important caveats:





What’s Natively Supported in Power Automate?




1. Asana Connector



Power Automate includes a built-in connector for Asana, allowing you to:


  • Trigger flows when:
  • A task is created
  • A task is completed
  • Perform actions like:
  • Create task
  • Update task
  • Add comment
  • Assign users




2. Azure DevOps Connector



There’s also a native Azure DevOps connector, which lets you:


  • Trigger flows when:
  • A work item is created or updated

  • Perform actions like:
  • Create work item
  • Update work item
  • Query work items






Possible Integration Scenarios




Asana → Azure DevOps

Azure DevOps → Asana

Create a work item in ADO when a task is added in Asana

Create a task in Asana when a work item is added in ADO

Update ADO when task is completed

Mark Asana task complete when ADO item is closed

Sync comments or notes (complex)

Sync state or metadata (custom fields, tags, etc.)







Limitations to Watch For



  • No native 2-way sync: Power Automate is trigger-based, so you have to manually build both directions.
  • Rate limits: Asana’s and ADO’s APIs have limits which could slow down bulk syncing.
  • Comment syncing: Not natively supported—would require use of custom HTTP actions.
  • Field mapping: You’ll need to manually map fields between both systems, especially for custom fields.






Pro Tip: Use HTTP Actions for More Control



If you’re comfortable with APIs, you can:


  • Use Asana’s REST API via HTTP action in Power Automate to fetch or push more detailed data.
  • Do the same for Azure DevOps REST API to access features not covered by the native connector.






Bottom Line



Power Automate can definitely be used to build a synchronization pipeline between Asana and Azure DevOps, especially for basic use cases. For a richer, real-time, and bidirectional sync, consider a third-party tool like Unito or Getint, or build a custom integration using Azure Functions or Logic Apps.


Would you like a sample Power Automate flow template to sync Asana → Azure DevOps?


From Blogger iPhone client

Downloading, Connecting and publishing Videos from DJI Neo

 

To safely remove content from your DJI Neo (likely referring to the DJI Osmo Pocket 3 or similar DJI camera), here’s a clean and risk-free process:


Option 1: Using a microSD Card Reader (Safest & Fastest)

  1. Power off your DJI Neo.

  2. Remove the microSD card from the camera.

  3. Insert it into a microSD card reader connected to your PC/Mac.

  4. Open the file explorer and back up your videos/photos.

  5. Once safely copied, format the card:

    • Either using your computer (FAT32 or exFAT format).

    • Or inside the DJI Neo’s settings (recommended for camera compatibility).


Option 2: Using USB-C Cable to Connect Directly

  1. Power on the DJI Neo and connect via USB-C to your computer.

  2. It should show up as a mass storage device or allow access via DJI Mimo.

  3. Open folders and copy all media to your computer.

  4. After ensuring successful backup, you can:

    • Delete files manually, or

    • Format the SD card via camera settings (again, recommended for stability).


Option 3: Via DJI Mimo App (Limited control)

  1. Connect DJI Neo to your smartphone using the appropriate cable or wireless.

  2. Open the DJI Mimo app.

  3. Browse, download, or delete files directly from the app.

    • Note: This can be slower, and full-resolution files may not transfer depending on the mode.


⚠️ Tips to Keep It Safe

  • Always eject safely (on PC or phone) before unplugging.

  • Never remove SD card while camera is powered on.

  • Format in-camera for best SD card performance and to prevent file system issues.


If you're dealing with space issues or want help organizing backups automatically, I can suggest some workflows or tools too. Let me know what device or system you're using (Windows, Mac, Android, etc.).

Connectivity Issues

If your USB-C cable isn't showing video when connecting your DJI Neo (assuming you mean the DJI Osmo Pocket 3 or a DJI camera that uses the "Neo" connection system), here are a few things to check:

🔌 1. Cable Type Matters

Not all USB-C cables support video output (DisplayPort Alt Mode). Many are charging/data-only cables. To show video:

  • You need a USB-C cable that supports video output.

  • Look for cables labeled as "USB-C 3.1 Gen 2" or "Thunderbolt 3/4".

📱 2. Device Compatibility

  • Make sure your phone, tablet, or display supports USB-C video input/output.

  • Some phones (especially older or budget models) don’t support DisplayPort Alt Mode.

📷 3. DJI Device Mode

  • On DJI devices like Osmo Pocket 3 or DJI Action, the camera might need to be in a specific mode to output video over USB-C.

  • Try powering it on before or after connecting the cable to see if there's a difference.

🧪 4. Try These Troubleshooting Steps

  • Use a different USB-C cable (with video support).

  • Try a different device (phone, tablet, or monitor).

  • Update the firmware of your DJI device using the DJI Mimo app.

  • Check for a DJI accessory (like the official USB-C to HDMI accessory if needed).