Frequently Asked Questions – FAQ
|Company Name||Pragmatic Solutions Inc.|
|Company HQ Location||Alexandria, VA|
|USA Sales Phone Number||1-703-798-3283|
|Metadata Product Name||Syspedia|
|Metadata product website||https://www.syspedia.com|
|Year company first started||Pragmatic Solutions, Inc was founded in 1994.|
|Year metadata product first introduced||Syspedia was first introduced as a software solution in 2005.|
|February 2007 – what is the current release number of your metadata product?||Version 3.01 is being released in Summer of 2007.|
|What is the next release number you are working on? When is it due?||The next version of Syspedia will be 3.01 due in the second quarter 2007.|
|What is the current number of active customer installations (metadata product only)||Syspedia is a formalization set of tools that have been used during several professional service engagements.|
|Feb 2007 – what is the current number of active customer installations (metadata product only)||Several of our service engagement clients still use the Syspedia tools along with others that have purchased the complete Syspedia Solution.|
|Provide a basic overview of your metadata solution offering.||Across all software platforms and many languages, Syspedia provides a meta data solution that systematically captures all existing business rules, application details, data usage, standards and relationships so you can quickly research, integrate, troubleshot, replace, modify or simply understand your universe of data and transactions.|
|Is it a client/server application? Describe the architecture of your product.||Syspedia can be configured in a centralized, networked or distributed environment to provide business units with the control, business rules and rich meta data they need to be effective. For example this allows a centralized Syspedia to feed department repositories or the departments to feed the centralized Syspedia repository. Syspedia’s is very flexible using a browser interface to the desired meta data repository architecture.|
|What is your metadata product designed to do? What type of audience is it designed for? (describe)||Syspedia is designed for architects, business analysts, system administrators and application developer. Syspedia provides meta data details for a better understanding of the cross platform and enterprise relationships. Syspedia shows element level relationships and dependencies between systems, applications, processes, modules, business rules, files, data movement and individual file elements. This rich meta data is a tremendous resource for migration, integration, consolidation and documentation or remediation of Sarbanes-Oxley controls.|
|Describe your “scalability”?||Syspedia is designed for performance. Since Syspedia is 100% Java based it is currently deployed on the mainframe, UNIX and Windows platforms. Syspedia scales by quickly handling the searching of millions of meta data entries. Performance and|
scalability are Syspedia’s strengths.
|Describe your ideal metadata solutions client or customer|
implementation. What is your “customer sweet spot” to sell to?
|Syspedia’s is an ideal solution for a large complex IT enterprise that needs to understand the relationships between platforms, systems, job streams, applications and files. Customers that need to quickly discover business rules, dependencies of a large number of JCL streams, COBOL and Java applications.|
|Is your product designed to be a stand-alone, fully independent metadata Management solution ? Or is it better utilized when it is combined with|
other products ?
|Syspedia provides a comprehensive stand-alone solution set. Since it is java based and uses industry standard interfaces it can be integrated quickly and easily with other complimentary products.|
|If you answered YES to the “independent” question (above), do you have actual customers that are using your metadata product in a completely|
|Syspedia is being used as a standalone solution|
and has been used as a resource during professional services
engagements. Syspedia provides quick answers for solving complex
integration and migration issues.
|Does your product “browse” metadata? (describe)||Syspedia is web application implemented with a back end meta data repository. The simple intuitive web interfaces provides rich deep information at your fingertips.|
|Is your product designed to physically move metadata definitions from|
one development tool to another? (describe)
|Syspedia is best|
integrated into the Change Management system so all data definitions,
business rules and job stream meta data can be up to date.
|What are the different product components called?||Syspedia is very simple. It is made up of the back end repository that stores the information on any JDBC2 compatible database. The Knowledge Discovery parsers that crawl your cross platform environments, DBMSs, applications, libraries, jobs, files and automatically populate element level meta data information. And finally the intuitive web interface that runs on any Java2 compatible application server.|
|What are your key product strengths? What is your key competitive advantage?||Ease of use – Easily obtain information from your Programs, Databases, Data Elements, & JCL across all of your enterprise computing environments. Self-Service Analytics – Syspedia’s intuitive and customizable Web interface makes researching IT assets and elements quick and easy for corporate auditors, IT personnel or executives. Harvest Business Rules – Syspedia harvests all levels of IT assets down to the data element level. This provides relationships to all levels of components so data lineage, data movements, application decisions and impact analysis for all components and their aliases is quick and easy.|
|Do you offer an Application Programming Interface (API)? What|
technology or programming language is utilized? (describe.)
|An XML interface is currently being developed to interface with Erwin and other third party tools.|
|Technical Environment – what is the ideal hardware/software configuration to run your product on for maximum performance?||Syspedia is 100% java and runs on any platform. This allows Syspedia to be the only meta data solution that provides comprehensive cross platform data element level relationships and dependency information. Performance and|
scalability are not a problem with Syspedia.
|Does your metadata product support concurrent access by multiple users at the same time ? What is the optimal number of concurrent users and what is the limit of number of users?||Syspedia is very fast. Syspedia’s architecture provides web browser concurrent access to a large number of users. Large numbers of users can use Syspedia to scale to the limits of the hardware, database and application server|
capacities. Syspedia’s use of standardized software components allows flexibility and large numbers of concurrent users.
|What hardware is required to run your product?||Syspedia scales to the limits of the hardware, database and application server capacities. Syspedia’s repository was designed by database performance experts that built the underlying open database to support easy, fast access to your enterprise components and elements.|
|Give a list of recommended (examples of hardware used at other customer implementations) including technical specifications.||Syspedia can be implemented in a variety of configurations, on the mainframe, UNIX or Windows platforms. Syspedia’s use of standard SQL and application servers allow it be implemented on DB2 (recommended) Oracle or SQL server. The web browser application supports any Java JSP2 web server including open source Tomcat (recommended), Websphere (recommended), or BEA. The most ideal configuration is where Syspedia has direct access to the component libraries that will populate the repository. This allows real time updates from the Change Management processes to the repository.|
|Does your metadata product use a repository database structure? (describe)||Syspedia uses its own repository data structures to ensure end-user concurrency and performance. These database structures are based and similar to the OMG and CWM standards.|
|Is your repository database structure proprietary?||Syspedia repository data structures are proprietary but opened and disclosed to customer so they may attach and use their third party products.|
|What database or file system does your repository run on?||Syspedia runs on mainframe, UNIX or Windows systems using DB2 (recommended), Oracle, or SQL server.|
|What operating systems does your repository database run on?||Since Syspedia is 100% java it can run on almost any hardware or software platform. It runs on the mainframe (z/OS), any UNIX, LINUX or Windows system.|
|Are your repository database tables “open”? Do you document or publish the table structures? Can you access the tables with SQL or a third-party reporting tool? (describe)||Syspedia repository structures are open for non-disclosed customers to access the repository from third part tools and other SQL type products. Since the underlying data stores are similar to the OMG and CWM structures they are disclosed to customers so they can use any OLAP or SQL product that support JDBC2 connectivity.|
|Can you access the tables with SQL or a third-party reporting tool ? (describe)||Once Syspedia is purchased, the repository database structures are disclosed to our clients. Many of our clients hook in their third party reporting tools to access Syspedia directly. Syspedia can be referenced by any third party tools that provide JDBC2 connectivity and SQL1999 compliant SQL.|
|What type of metadata is your product primarily designed to document, or provide access to? Business metadata? Technical metadata? metadata contained within 3rd-party development tools? (describe)||Syspedia maps, documents and helps you harvest the business rules and processes that run your business and IT department. Syspedia harvest all components of your software portfolio down to the element level so you can quickly understand the relationships, data lineage, and business|
rules and processes through your various applications. Syspedia provides this extensive technical metadata with a wikipedia for business definitions and discussions. Syspedia with its wikipedia provides a forum for more business metadata around the technical metadata. The web
interface then provides a common interface for all your enterprise personnel to discuss the business definitions along side the technical IT assets descriptions which provides for a truly “business system encyclopedia”.
|Does your product ship with any pre-defined meta-models? (describe)||Syspedia’s repository is similar to the OMG and CWM meta models.|
|Is the repository database fully or partially extensible? (describe) Can you truly model any type of custom metadata object, attribute, or relationship?||Syspedia is extensible through regular database processes. Any extensions would not be available through the intuitive web Syspedia interface but would be available through any third party tools.|
|Can you truly model any type of custom metadata object, attribute, or relationship?||Syspedia with its wikipedia plug-ins is capable of handling any metadata documentation. This allows any diagrams, PDFs spreadsheets or other documentation to be tied to the business description or technical metadata.|
|When you make extensions to the repository database, how are they implemented ? Are special DBA or consultant skills needed?||Extensions to Syspedia would be implemented as additional data structures within the Syspedia repository. These could be added through normal DBA processes and procedures.|
|In reference to part D.5, do you need to take down and re-create the repository database ? (describe)||Syspedia incorporates new metadata through it wikipedia using XML and binary object types. These formats allow a variety of information to be captured without having to modify|
or recreate the repository. Syspedia is about availablity, scalabiltiy and performance.
|Provide a general overview of your interfacing capability. How do the interfaces work?||Syspedia captures meta data from mainframe, UNIX and Windows platforms for an enterprise wide solution. The Syspedia web interface allow easy harvesting of the environment libraries, modules|
and elements by simply setting up the path to the library and giving Syspedia your harvesting criteria. This path and criteria information is then used by the batch Syspedia Knowledge Discovery java component to extract meta data from you environment.
|Do you offer “scanners” that copy and store metadata definitions in a centralized repository? (describe)||The Syspedia Knowledge Discovery module harvests and builds a comprehensive enterprise wide meta data. Syspedia builds this meta data by examining, scanning, and distilling your libraries, JCL, programs, modules and file definitions. business data.|
|How do you keep duplicated metadata definitions held in your repository up-to-date and synchronized with the real world? Can you automate the process to refresh metadata definitions?||Syspedia Knowledge Discovery process harvests meta data from enterprise wide system components based on several criteria. This automated process can easily be integrated|
with change management systems or scheduled to a frequency that can provide real time updates. Syspedia can keep as many versions as needed to show the component history since it stores as many copies as you like via both extract and component timestamps.
|In reference to F.3, can you automate the process to refresh metadata|
|Syspedia Knowledge Discovery automated process can be scheduled to refresh or extract any metadata on demand.|
|Do you offer “real-time” interfaces that browse metadata from other|
tools, but do NOT copy definitions into a central repository? (describe)
|Syspedia’s web application has a facility to interface or browse enterprise database structures or other third party products meta data structures or interfaces.|
|What reporting or business intelligence tools does your product|
|Syspedia’s underlying meta data structures are disclosed to customers so they can use any of their third party SQL capable tools.|
|What DBMS does your product interface to?||Syspedia can interface with any DBMS that is JDBC2 compatible and capable.|
|What data modeling or UML tools does your product interface to?||Syspedia is moving to a XML interface to interface with any architecture or other open products.|
|What ETL tools does your product interface to? Does it provide access to the data transformation or mapping rules?||Syspedia currently only harvests application programming languages and mainframe, UNIX and windows data structures. In the future Syspedia’s XML capabilities will be able to harvest from any open product.|
|What EAI tools does your product interface to? Does it provide access to the data transformation rules?||Syspedia currently only extracts and parses application programming languages for business rules and data structures. In future releases Syspedia looks to integrate with the XML|
interfaces to the CWM and XMI standards for all ETL transformation products.
|What ERP or CRM applications does your product interface to?||Syspedia supports extracting and parsing the data structures of any CRM or ERP|
system. Syspedia does not directly interface to these products it is able to extract and parse data structures and application programs.
|What programming languages does your product interface to?||Currently Syspedia parses and interfaces with COBOL and JCL. XML parsing is being|
added for extracting metadata from third party interfaces and multiple programming languages.
|Does your product interface to COBOL copybooks? MVS/JCL? Does it|
recognize REDEFINES and OCCURS?
|Syspedia interfaces and details the file layouts from all platforms, copybooks, redefines and occurs. It highlights the relationships between the primary elements and their subordinate elements. Syspedia also parses and provides detailed analysis capabilities of JCL. Syspedia is the only metadata product on the market that handles standard JCL. The Syspedia JCL parser handles JCL PROCS and expanding and cross referencing symbolic parameters within JCL.|
|What other 3rd-party products (not listed so far) does your product interface to?||Syspedia can be used to interface with many programming language data structures such as IDMS, PL/1 etc. Contact your Syspedia Representative for details.|
|What additional interfaces will you be delivering in 2007?||Syspedia is delivering the wikipedia interface and the cabability to associated any type object to the metadata.|
|Does your product provide a generic import/export facility? (describe) If YES, what file formats does it support?||Syspedia does provides database standard imports and exports of its information.|
|Can your product import/export metadata held in XML files?||Syspedia in 2007 is building an XML interface to data models along with other CWM and OMG standard XML interfaces. These interfaces are targeted for late 2007.|
|How do you establish linkages or relationships between metadata objects from different development tools? Is this done manually? Automatically? (describe)||Syspedia reflects and provides analysis capabilities of all the enterprise objects automatically as it parses|
and builds the meta data. These relationships are maintained inherently through the Syspedia data model and the timestamps associated with the meta data. This allows Syspedia a tremendous amount of flexibility to maintain versions and maintenance within the product.
|How quickly do you upgrade interfaces to new versions of the 3rd-party tools? What is your policy?||Syspedia follows 3rd party tools within a reasonable period.|
|Do you offer “mass update” or “mass purge” facilities? (describe)||Syspedia supports mass delete purging of old versions of meta data. For example I would like to only have three versions of meta data. Syspedia can easily and quickly handle this request through its support of timestamps.|
|Version Control – does your product provide “versioning”? How does it work? (describe)||Since Syspedia captures the timestamp of the all the objects it supports it can capture as many versions as needed. For example program timestamp of when the parsing was done and the timestamp of the module was last changed is capture. This allows meta data versioning to handle multiple versions based on any desired criteria.|
|Does the tool support multiple metadata object definitions over project or lifecycle phases – such as “Test”, “Development”, “Production”, “Release 1.1”, etc …? (describe)||Syspedia uses an Environment, Application, Module, Data Structure, and Element architecture that allows the administrator to capture or set up as many unique separate definitions as they need. These different levels of objects can support an unlimited number of object definitions.|
|Can you compare different versions of objects to one another? (describe)||Yes, Syspedia currently supports the comparison of any|
metadata elements across the enterprise and within data structures.
These comparisons verify data definitions for data movement and elements
involved in decisions and movement across the various modules.
|Does your product support any specific metadata exchange standards, such as CWM, UML, MOF, XMI, CDIF, etc? (describe)||Syspedia is going to a full XML metadata interface to exchange data with any thrid party tools.|
|Does your product support any government or educational standards such as ISO 11179? (describe)||The Syspedia Standardization section supports the different aspects of the ISO11179 standard phases. This Syspedia process supports data element consolidation, and remediation. Syspedia has a complete white paper on the different methods to resolve different data elements.|
|Does your product offer any prebuilt metamodels or reports for emerging industry regulations, such as HIPAA, Sarbanes-Oxley, ACORD, BASEL II, etc?||Syspedia supports Sarbanes Oxley by identifying data lineage, relationships and dependencies for IT controls. This information can then be used to understand general ledger data dependencies and help auditors trace and remediate changes in controls.|
|Is your company involved in any standards committees or memberships?||Syspedia looks to leverage the emerging UML and BPEL standards for better XML integration with other third party products.|
|Does your product support the concept of a “corporate data dictionary”? (describe)||Syspedia has become the corporate data dictionary for some clients. Since Syspedia can be integrated into the Change Management process it provides real time access to data definitions, dependencies|
and module relationships across the enterprise.
|Does your product support a Data Warehouse? (describe)||Syspedia helps support data warehousing efforts by identifying all the business rules, data definitions and data lineage of elements across the enterprise. This information can be vital for determining the best source for the data warehouse by understanding the most validated most used and best|
definition of the data use in your environments.
|Does your product support the concept of a “card catalog” or Information Directory? (describe)||Syspedia is the system encyclopedia of all your application modules, elements and JCL stream components. By|
categorizing and automatically relating this information at the lowest element level Syspedia provides the most comprehensive information.
|Does your product support an IDE or Service Oriented Architecture (SOA)? (describe)||Syspedia can be used to help identify SOA architecture dependencies and common definitions.|
|Does your product support Component/Object Management and the re-use of technology? (describe)||Syspedia’s Administration Facility allows for standardization and reuse.|
|Describe your reporting capabilities.||Syspedia comes with over 40 standards reports and an intuitive web interface to retrieve any object meta data information. Syspedia also discloses its underlying data model to customers so they can have SQL ad hoc access through any of their third party tools.|
|Do you support “Data Lineage” reporting?||Along with data lineage capabilities Syspedia can detail all the subordinate or master data elements impacted or related to a particular element. Syspedia provides detailed data allowing the user to drill up from the element to its related files or DBMS tables, then to the related application modules and then to the application(s) and finally the related environments. This capability Syspedia provides comprehensive data lineage and relationship information across enterprise platforms, environments and applications. Data lineage can be traced from data creation to archive processes across various components.|
|Do you support “Impact Analysis” reporting?||Syspedia provides comprehensive relationship data between all your enterprise objects and components. These objects include JCL components and application software running your business. Syspedia can detail all the subordinate or master data elements impacted or related to a particular element. Syspedia provides detailed data allowing the user to drill up from the element to its related files or DBMS tables, then to the related application modules and then to the application and finally the related environments.|
|Do you offer “graphical” reports – pictures, diagrams of objects and|
their relationships? (describe)
|Syspedia can support custom reports and graphical objects within these reports through HTML or JSP web pages. Syspedia is evaluating the integration possibilities of the ERWIN model HTML pages.|
|Can you publish to different file formats, such as .PDF, HTML, MS-Office, etc …? (describe)||Syspedia web information and batch reports can be migrated to many formats through a variety of third party tools. Syspedia discloses its data model to customers so it can be reference by any SQL third party product and publish any to any format.|
|Can you use 3rd-party reporting tools to access your repository database, such as an SQL-based tool? (describe)||Syspedia discloses its data model to its customer so any SQL based third party tool can reference the Syspedia information.|
|Describe your security and user-management features. Do you support “roles-based” security?||Syspedia leverages the security mechanisms of application server environment along with the security mechanisms of its|
DBMS environment. Based on these under lying components Syspedia supports roles based and single sign on security processes.
|Describe your repository administration environment.||Syspedia’s administration environment is very simple. Syspedia has a web interface that generates the batch Syspedia Knowledge Discovery parser parameters. These parameters direct the Knowledge Discovery java parser to extract system components from what files, libraries or systems and several other criteria. Since Syspedia is 100% java it can be executed|
on any platform or operating system. The Syspedia Knowledge Discovery module then populate the meta data back to the repository for access through the web interface or other interfaces.
|Does your product support single sign-on or LDAP?||Syspedia leverages standard DBMS and application server facilities in your environment and can be configured for single sign-on or LDAP.|
|Do you provide “auditing” facilities that allow you to track changes made to individual objects or groups of objects over time? By person? (describe)||Syspedia is looking to add these additional auditing facilities or reports to its capabilities list. Since it has the|
capabilities to handle multiple versions the level of audit reports is being discussed with clients for their audit reporting requirements.
|Does your product provide reporting/auditing on repository object/field usage by users? (e.g. Number of times a metadata field is searched for, or accessed over the last week…etc)||Syspedia statistics and search criteria can be gathered if desired through the web log.|
|Describe your backup, Restore, Failure, and Recovery utilities.||Syspedia backup, restore failure and recovery facilities would leverage the same facilities as standard web based applications and standard DBMS facilities.|
|Describe your pricing model. How does it work? Server-based pricing? Seat pricing?||Pricing model is simple. One copy of Syspedia one license, multiple copies of Syspedia in one location or multiple copies of Syspedia in multiple locations.|
|What is the price range of a typical customer configuration or product package that you are currently selling to?||Depends on the client configuration.|
|What is the maximum price for your product?||Depends on the client configuration.|
|Describe your maintenance support program and pricing.||Syspedia uses the 20% standard maintenance model.|
|Describe your technical support program and pricing.||Extra ordinary support is given to all Syspedia customers through their purchase and on-going maintenance agreements.|
|Describe your onsite consulting services. How much installation support does the typical customer require?||Syspedia has been used in several professional service engagements and has provided answers in only hours|
at a client location. Syspedia can be installed quickly since it leverages standard web application and DBMS facilities. Clients can install Syspedia in a matter of a couple of hours. Typical user training is minimal because of the straight forward Syspedia architecture and easy web interface with built in screen specific Help
|What is the typical timeframe for implementation of your product? Please provide a brief outline of the steps for implementation and how long each one takes. Feel free to make a few assumptions if needed.||Since Syspedia was developed through professional services engagements the installation process is accomplished very quickly. Install the web interface application on an existing server, define the Syspedia|
repository tables and begin extracting from your environment with a security cleared id. Installation has been completed in hours.
|Describe your metadata training programs||The purchase of Syspedia usually includes training for a classrooms of students. Our client’s understanding of Syspedia leads to a successful metadata program integrated into your standard practices and procedures.|
|How much training does the typical product Administrator require? What training classes do you offer to support the Administrator?||The Syspedia administrator usually sets up the Knowledge Discovery java module to work with the Change Management system to provide real time meta data. This is straight forward and quickly accomplished by adding a step that executes this java process. This typically takes minutes for the Administrator to understand and do.|
|How much training does the typical User require? What training classes do you offer to support the typical User?||Syspedia is very easy to use and a end-user can quickly find the information they need. Its Google like intuitive web interface allows users to quickly drill up or down through application object information or JCL dependencies. Users can typically become productive in a matter of minutes.|
|Do you offer a metadata User Conference, or User Groups?||Not at this time.|
|Describe your product documentation.||Each Syspedia screen has built in comprehensive Help facilities and documentation. Help is a click away with details about the screen data and navigational possibilities.|
|How do you handle product enhancement requests?||Product enhancement requests are encouraged. We want to make Syspedia the best solution in|
Syspedia can be used as a service offering to help you identify programs, files, and database elements along with business rules critical to your legacy system. Syspedia has been used as a research tool to identify the VSAM, IMS or IDMS key processing elements. Since a Syspedia comprehensive repository of your legacy application can be setup sometimes overnight, answers can quickly help business analysts and application developers understand the legacy processing and migrate it to another environment.
Syspedia’s provides immediate value and return on investment and has been vital tool for the user community understanding dependencies even after the migration.
Syspedia can be setup very quickly because it uses standard components and is so easy to use. The install process comes with a free pre-configured application web server, Apache Tomcat that can be working in minutes. The Syspedia business repository can be built on a existing or new database platform your company is most comfortable with such as DB2, Oracle, or SQL Server. Verify standard Java and JDBC connectivity and the extract and web application are ready to go. Configurations have been built and functioning in literally minutes getting the answers you need immediately.
Business analysts, data administrators and database administrators like Syspedia’s web interface for self service of data questions. This feature alone lightens their workload of questions and lets everyone get their own data answers.
Many companies with legacy repositories are interested in the many additional functions and features that Syspedia provides at a fraction of the cost. Syspedia exposes many additional systems, applications, jobs, files, data elements and relationships then these older products. Additionally Syspedia is designed and built to be an active
web accessible repository for all departments and platforms with its Java extract capabilities to get data from anywhere. Syspedia is active because it helps you set up and improve your systems with its Standards Administration and active flexible extract processes.
Also unlike other legacy repositories, Syspedia was developed by Pragmatic Solutions and not acquired in a merger. Pragmatic Solutions looks to continue to extend and enhance the capabilities of Syspedia with every new version and release.
Syspedia pays immediate dividends by reducing costs. Syspedia quickly automates the process of examining all of your data elements and programs, on any platform in any file type in any programming language. Know everything about your data everywhere in your enterprise.
- Who’s applications use the file thatThese capabilities help leverage existing systems instead of writing new code, spending less money on development, testing and problems.
- This capability provides immediate time/cost savings on impact analysis, speeds integration time and benefits all enterprise platforms.
Business Rules are buried in the application processes, policies and application code that runs your business. Syspedia automatically parses your applications and captures all your processes, decisions, logic and element dependencies in the Syspedia Analytical repository. By capturing all these component details Syspedia provides a web interface to quickly research any of the processes, policies, “IF” statements, logic statements, elements, or the business rule types used across your various platforms.
This harvesting and investigation of business rules is a by product of the Syspedia extraction process. The analysis can be done quickly and easily by simply entering the business rule type, element or module name in the Syspedia web browser interface.
For example if you wanted to understand all the business rules that the CUST_CODE element was involved in you could quickly enter the name and find its relationships. Syspedia would display all the business rules related to the element and the module line number of the source code. Syspedia would also display other elements related to CUST_CODE in move statements or other application statements such as outside calls.
Business rules can also be research by the rule type or comparison type. Applications using “IF”, “CASE”, or “88 level” code values can be researched and discovered quickly by asking for that particular rule type in the web interface. Syspedia quickly retrieves all the business rules matching your desired comparison type across applications or
across multiple platforms. The end-user can then quickly get the business rule answers they need for debugging, impact analysis or researching Sarbanes-Oxley controls. Syspedia also helps you standardize your values across platforms and modules through its Standards Administration process.
Sarbanes-Oxley Section 302 and Section 404 require companies to identify key business processes and any vulnerabilities in their controls. Syspedia quickly identifies the key elements in your application systems and the related controls that test them. This helps the CFO and the compliance team quickly extract and document particular controls, their parameters and the different module application practice.
Syspedia’s easy query capability and documentation can be vital for understanding all the existing controls and their dependencies. Since Syspedia is 100% java it can identify controls across applications and across platforms. It is difficult to extract the actual business rules or controls that exist in current computer software programs and
defining new rules or controls may not incorporate existing governance, duplicates efforts and wastes precious resources.
Syspedia finds existing controls embedded in application code and helps the compliance team understand their parameters and usage. The compliance team and the auditors can quickly realize and leverage the standard reporting and existing control documentation eliminating the effort needed to create new or duplicate controls and documentation.
Syspedia has several different features that help legacy application migration or software modernization projects. First the Syspedia Business Rules Scanner automatically harvests various data elements and their business rules in all the legacy databases, files, and objects. While extracting all this rich meta data it captures business rules captures the relationships of all the data elements. All of the data element meta data, dependencies, and relationships are then available for quick and easy research through the Syspedia web interface.
Next Syspedia is able to scan and parse through your job information and build the complete meta data relationships between data elements through to the various jobs and processing modules that reference them. Syspedia helps migration analysts and application developers quickly discover all the business rules, interfaces, data movement, outside module calls of a particular data element.
Next Syspedia provides a comprehensive data dictionary and central reference point that remote business or development groups can reference. Syspedia helps everyone realize the same definition, type and overall semantic meaning of the element. Syspedia captures all the related data elements and quickly identifies data range, domain, and type mismatches for resolution.
Next Syspedia provides a Standards Administration process where business analysts and application developers can resolve naming conventions and build enterprise data standards. This process allows data elements to be associated and resolved through an automated process where complete dependencies, relationships and interfaces are realized.
Syspedia’s complete data dictionary helps legacy application migration in many more ways. The best way to discovery its advantages is through a demonstration. Go to the Contact page and ask a question or request an on-site demonstration.