Technical overview of Engineering Insights
Linked data from lifecycle management applications
Lifecycle Query Engine indexes data from your lifecycle management applications that support the Tracked Resource Set (TRS) specification.
Representational State Transfer (REST) is a set of principles that define how Web standards, such as HTTP and URIs, are to be used. REST is the basis for linked data, so that all artifacts that have IDs can link together, have multiple representations, and communicate.
Although the index is an important component of the application, teams use the index transparently to retrieve information through operations such as views, analysis, or search. The index is the data pool, but it is not visible to users. Linked artifacts are stored in it, and data is retrieved from it.
To easily query data from several data sources across your lifecycle applications and project areas, use the Report Builder from the Queries menu. Create Jazz® Reporting Service reports and publish them on a Jazz dashboard.
Aside from running views and analysis, teams need to print reports on the status of artifacts. A sample report is available to display information in a simple table.
To easily query data from several data sources across your lifecycle applications and project areas, use the Report Builder from the Queries menu. Create reports with graphs and charts. Publish them on a Jazz dashboard or export them to other formats. See Authoring reports with Report Builder.
To create templates to generate other document-style reports or to produce high quality printable documents with front and back matter, you need IBM Engineering Lifecycle Optimization - Publishing (PUB). See Authoring document-style reports.
PUB is not included in ENI. A separate installation and license are required. Contact your server administrator to verify that the installation is completed and that you can connect to the license server.
Collaborative use of Engineering Insights
An administrator creates special views for the team. The views provide a structured and dynamic look inside the product development work that enables team to view engineering data across all engineering disciplines. For example, a V-process view shows the lifecycle of a product starting with system design, moving through software architecture and development, and ending with integration and testing.
The team runs search, Report Builder queries, and analysis, to find artifacts and the relationships among them. Relationships are important when a component must be repaired or replaced, or if you work with multiple versions of products.