Petrosoft participates in setting c-store and petroleum industry technical standards by attending Conexxus committee meetings and events throughout the year. These meetings and events bring industry leading technology companies together to discuss present and future challenges to ultimately create and implement technical standards for the c-store and petroleum industries. The goal of the standards is to improve the c-store owner’s profitability by reducing the cost of IT ownership and improving the competitiveness of industry technology companies.
By participating in the development of these standards and working with industry-leading technology partners, Petrosoft helps to ensure that customers can make the most of their data and legacy systems while taking advantage of the advances in POS, foodservice, back-office, fuel management, and integration solutions.
What is a standard?
“Standards are the distilled wisdom of people with expertise in their subject matter and who know the needs of the organizations they represent – people such as manufacturers, sellers, buyers, customers, trade associations, users or regulators.
It makes it easier for different companies’ solutions to work with each other. It also reduces the time to implement the system within an existing an agreed way . It could be about making a product, managing a process, delivering a service or supplying materials—standards can cover a huge range of activities undertaken by organizations and used by their customers.” Conexxus
|DOCUMENT||WHAT IT IS||AUDIENCE|
|Business Requirements Document||This document should attempt to completely describe all requirements and do so in a technology independent way.||Business owners and standards developers|
|Use Cases||Use cases are commonly classified as system use cases or business use cases. System use cases describe an interaction with a system (software). Business use cases describe how a business reacts to a customer or event. Brainstorming through each use case, asking the questions “How could this go differently?” and “What could go wrong?” will identify additional scenarios.||Business owners, standards developers, and implementers of standards|
|Process Documents:Business Process Flow Diagram||A business process flow diagram provides a graphical overview of a business process.||Business stakeholders and standards developer|
|Process Documents:State Diagram||This graphical representation is intended to provide a finite number of modes of operation and show all factors that affect changes from one mode to another during system operation.||Standards implementers|
|Process Documents:Sequence Diagram||A sequence diagram is a technical document that graphically describes how objects or processes interact with each other.||Standard implementers|
|Annotated Schema||Schemas are technical documents that capture in XML format the data that is passed back and forth between systems, processes or objects. Typically, the schemas are the most critical piece of the Conexxus standard.||Standards implementers|
|Sample XML||A sample XML document provides standards implementers with a reference on how to use the published schemas and provides a data set against which to test.||Standards implementers|
|Example Stylesheet||This stylesheet is used to transform an xml document into a more human friendly form, providing a visual way to represent the data.||Standards implementers|
|Validation Stylesheet||This stylesheet is used to validate expectations that cannot be enforced via the schema itself. Using xpath statements, it provides consistency checks that validate totals, verify data integrity, and check elements against other related elements.||Standards implementers|
|Implementation Guide||An implementation guide provides information not captured in any of the other documents. It provides an overview of the standard and captures any observations, rationale, and theory behind the standard. It may include:· Architecture· Protocol· Data Model· Entity Relationship Diagram· Data Specification (including use of +/- signs, credits, adjustments and discounts)|
· Implementation details including reporting and operating recommendations.
· Explanations that would help a developer implement the specification
· Glossary of Terms