Thursday, December 4, 2014

FACTSHEET: Improving Systems Compliance and Integrity (REG SCI)

FACT SHEET



Improving Systems Compliance and Integrity

SEC Open Meeting
March 7, 2013

Background

Today’s securities markets rely extensively on technology more than ever before. As with any industry, the consequences can be significant when technology goes awry.
The high-speed automated trading that occurs both on national securities exchanges and alternative trading systems has heightened the potential for a technological problem to broadly impact the market.
Following the Flash Crash in May 2010, the SEC approved a series of measures to help limit the impact of such technological errors. For instance, the SEC approved rules to halt trading when a stock price falls too far, too fast as well as rules to provide certainty in advance of when an erroneous trade would be broken and rules to eliminate stub quotes.
Additionally, the SEC approved a rule known as the market access rule, which requires brokers and dealers with market access to put in place risk management controls and supervisory procedures designed to manage the financial, regulatory, and other risks posed to the markets by a malfunctioning of their technological systems.

Automation Review Policy

There are no mandatory rules governing the automated systems of self-regulatory organizations, such as national securities exchanges, clearing agencies, FINRA, and the MSRB. Instead, for the past two decades, they have followed a voluntary set of principles articulated in the SEC’s Automation Review Policy and participated in what is known as the ARP Inspection Program.
Recent technological issues in the securities markets including those that arose during the initial public offerings of Facebook and BATS Global Markets as well as the Knight Capital trading incident have shown that investors can be put at risk when technology fails, and confidence in the markets can falter.
The SEC convened a roundtable in October 2012 to discuss how market participants could prevent or at least mitigate systems issues, and how the response to such issues could be improved. The market closures following Superstorm Sandy also highlight the importance of having a robust market technology infrastructure. These events and discussions have helped shape the development of the rulemaking being proposed today.

Proposed Rule — Regulation SCI

The set of rules proposed by the Commission — called Regulation Systems Compliance and Integrity (Regulation SCI) — would formalize and make mandatory many of the provisions of the SEC’s Automation Review Policy that have developed during the last two decades. The proposed rule applies the policy and proposes additional measures to entities at the heart of U.S. securities market infrastructure in order to protect that infrastructure.
Regulation SCI would seek to ensure:
  • Core technology of national securities exchanges, significant alternative trading systems, clearing agencies, and plan processors meet certain standards.
     
  • These entities conduct business continuity testing with their members or participants.
     
  • These entities provide certain notifications regarding systems disruptions and other types of systems issues.
Regulation SCI is intended to reduce the chance of technology problems occurring in the first place and ensure that key entities are well-positioned to take appropriate corrective action if problems do occur.

Proposed Scope

The proposed rule would apply to “SCI entities,” a term that would include:
  • Self-regulatory organizations (the registered national securities exchanges, registered clearing agencies, FINRA, and MSRB).
     
  • Alternative trading systems that exceed specified volume thresholds (SCI ATSs).
     
  • Disseminators of market data under certain National Market Systems plans (“plan processors”).
     
  • Certain clearing agencies exempt from SEC registration.
It would apply primarily to the systems of SCI entities that are core to the functioning of the securities markets, such as those that directly support trading, clearance and settlement, order routing, market data, regulation, or surveillance.

Proposed Provisions

Under the proposed rule, each SCI entity would be required among other things to:
  • Establish policies and procedures relating to the capacity, integrity, resiliency and security of its technology systems.
     
  • Establish policies and procedures to ensure its systems operate in the manner intended, including in compliance with relevant federal securities laws and rules.
     
  • Take timely corrective action in response to systems disruptions, systems compliance issues and systems intrusions.
     
  • Notify and provide the SEC with detailed information when such systems issues occur as well as when there are material changes in its systems. Written notices would be filed electronically on new Form SCI.
     
  • Inform its members or participants about certain systems problems and provide information about the systems and market participants affected by the problem and the progress of corrective action.
     
  • Conduct an annual review of its compliance with Regulation SCI, and submit a report of the annual review to its senior management and the SEC.
     
  • Designate certain individuals or firms to participate in the testing of its business continuity and disaster recovery plans at least once annually, and coordinate such testing with other entities on an industry- or sector-wide basis.
     
  • Provide SEC staff with access to its systems to assess compliance with Regulation SCI.

What’s Next

A 60-day public comment period will follow Reg SCI’s publication in the Federal Register.

SEC rule takes aim at trading system glitches

The Securities and Exchange Commission approved new rules Wednesday to make sure that the systems that Wall Street trades run on are robust and vigilant enough to stand up to cyberattacks and technological glitches.

Regulation Systems, Compliance, and Integrity (or Regulation SCI) will create a framework for overseeing the complex systems that operate on Wall Street — and, increasingly, clash with each other, get hacked or fail.

"In today's markets, a single rogue algorithm can trigger a cascading series of errant trades, destroying billions of dollars of market value in the blink of an eye," says SEC Commissioner Luis Aguilar.

The most dramatic example was the Flash Crash on May 6, 2010, when the Dow Jones industrial average plunged 1,000 points, or nearly 9%, in minutes — only to recover nearly as quickly.
The new rules require periodic stress tests of system capacity, as well as requirements that companies report and address problems and malfunctions to the SEC immediately.

Previous systems rules on Wall Street were largely voluntary, and the original version was simply conceived as a codification of voluntary review. SEC staff worked with public comments to streamline the regulations and reduce the burden on the companies involved. "These companies have an enlightened self-interest in getting things right," said Commissioner Daniel Gallagher.

"As I have emphasized time and again, the critical infrastructure of the American securities markets must be built on the best, most robust technology feasible," SEC Chair Mary Jo White said in her opening statement. "Failures must be minimized and, when they occur, they must be remediated as quickly as possible and promptly reported to the commission."

"Much more can and needs to be done," Commissioner Kara Stein noted, objecting that some smaller trading platforms were exempted from the new rules, as well as to broker-dealers who operate proprietary platforms.

The commission passed the regulation, 5-0.

USA Today
11/19/2014
Link

Tuesday, November 25, 2014

AITS Enterprise Batch Scheduling

Link


Service Description

The Enterprise Batch Scheduling Service offered by AITS utilizes AppWorx Enterprise Scheduler software. AppWorx enables the automatic and manual execution of all administrative batch processes including:
  • Java applications
  • SQL scripts
  • System scripts
  • All Banner batch processing
  • Informatica
  • Business Objects
  • SAS reports

The AppWorx Enterprise Scheduler provides the following functionality:
  • Event-driven process scheduling (defined workflows and/or job dependencies)
  • Automatic submission of executions
  • Interface for monitoring executions and process flow analysis
  • Priorities and/or queues to control management of execution for processes
  • E-mail notification of process commencement, completion, and/or error messages
  • A testing environment is available

Hours of Availability

This service is available to customers 24/7, excluding planned outages, maintenance windows and unavoidable events. Maintenance windows are used only when needed for planned changes that have gone through the AITS Change Control Process. In addition to the standard AITS maintenance windows, site-specific and service-specific changes may be coordinated with customers at non-standard times.

Standard maintenance windows are defined as:
  • 6 a.m. to 12 p.m. each Sunday when application usage is at its lowest
  • After 5 p.m. every Tuesday and Thursday, unless business needs to make a change during business hours
  • The second Wednesday of the month from 5 p.m. to 8 p.m. for patching Microsoft servers
  • 6 a.m. to 6 p.m. three Sundays a year for routine Windows and Linux maintenance

Customer Responsibilities

Contact the appropriate AITS TAM (Technical Applications Management) team, part of the AITS ADSD group, to discuss new batch processing needs. A work request will need to be submitted to initiate new batch processes.

For scheduling your user developed reports (SAS reports), contact the Production Scheduling group in the COE group for standards and guidelines (before developing).

For access problems, questions or comments, contact the AITS Service Desk at 217-333-3102 (Urbana/Springfield) or 312-996-4806 (Chicago). You can also e-mail the AITS Service Desk at servicedeskaits@uillinois.edu.

How Do We Charge?

Currently, AITS does not charge for this service.

AppWorx User Manual

Online

AppWorx
Version 5.1 (2002)
User Guide
AppWorx Corporation

A Modular Approach to Operations

AppWorx replaces scripts with an object-oriented approach to operations.

AppWorx provides a complete background-processing management system. With
AppWorx, you can do all the traditional batch management tasks, as well as submit jobs
and view output.

However, instead of writing scripts to perform tasks, you create AppWorx modules that
run programs. You combine modules to create chains. You create a schedule for each chain
(or for each module if you wish) using a full complement of scheduling tools including
custom calendars and execution conditions.
As with all modular systems, you create individual objects once, then use them in different
combinations to accomplish a variety of tasks. In the context of batch management, this
can save you hours of time compared to writing, debugging, and maintaining scripts. A
diagram of the AppWorx modular approach to operations is shown in Figure A.

A Different Way of Thinking

In a traditional operations environment, scripts drive operations. Scripts incorporate the
information required to run one or more programs on a set schedule, direct output, and
handle exceptions. The problem with scripts is the required time maintaining them when
the system changes. For example, if a printer definition changes, you must change it in
every script.

AppWorx takes the individual components of a script such as programs, schedules,
printers, and variables, and lets you define them as discrete objects. You can then combine
the objects in an unlimited number of combinations to handle your operations. The
advantage is being able to change an object in one place, and have the changes roll over to
every use of the object.

Automic: KEY REQUIREMENTS FOR A JOB SCHEDULING AND WORKLOAD AUTOMATION SOLUTION

Overcoming Today’s Job Scheduling Challenges
While traditional batch job scheduling still has a place in many enterprises, the task is
far more complex than it used to be due to the use of various computing platforms,
multiple computing environments, and business processes that run 24x7. Add to that
the complex interdependencies that often exist between different processes and the
frequent need to trigger jobs dynamically, based on changing circumstances. It’s clear
that the requirements for a traditional job scheduler has evolved into a broader workload
automation capability to meet today’s complex requirements.

But what are the key capabilities you actually need to address a modern day demands
of an enterprise job scheduling or workload automation solution? We’ve collated the
top requirements from global enterprises during the past 15 years. All of which have
successfully automated their core data center processes supporting their core business
applications and services. As such, they were able to reduce processing time by 70% and
eliminate 90% of IT process errors whilst reducing manual effort by 90%.


If you are looking for a job scheduling or workload automation solution that is built to meet
the demanding enterprise requirements of a modern day business, then it’s important to
consider the following key capabilities:

1. It must be able to schedule jobs.
2. It should have built in managed file transfers.
3. Central, scalable and multi-tenant architecture.
4. Support object orientation to enable fast, flexible implementations.
5. Provide native application support.
6. Support dynamic, event-driven automation.
7. The ability to embed conditional business rules.
8. Support advanced workload balancing.
9. Provide a self-service capability to enable end-user involvement.
10. Enable security and compliance across the enterprise.

Whilst (??) there are many other factors that are also important to consider, only by ensuring
that your solution encompasses the above key capabilities as a foundation can you be
certain that you will be able to meet the ever increasing demands of the business.

Problem & Solution

AppWorx at a glance


AT A GLANCE: This infrastructure software solution now features a 100-percent Java* environment, enhanced Web services with XML support, a SOAP API, multidatabase support through JDBC and expanded multiplatform support, including the mainframe.

DETAILS: AppWorx is enterprise software that manages a company's application landscape from above. As a development tool, it can automate application batch processing routines without scripting. As an integration tool, it can integrate batch-processing requirements across multiple applications, speeding implementation. As an operations tool, it can perform data center "lights-out" processing, reducing headcount and lowering production and maintenance costs. As a business tool, it can ease the burden on functional end-users and accelerate the delivery of important business information.

http://www.ibmsystemsmag.com/mainframe/productnews/AppWorx-7/

Monday, November 24, 2014

What is Kuali Coeus?

What is Kuali: “Kuali is a growing community of universities, colleges, businesses, and other organizations that have partnered to build and sustain open-source software for higher education, by higher education. “ – kuali.org/about

What is Kuali Coeus: An open-source Electronic Research Administration system Originated in MIT as “Coeus,” it has been redeveloped using modern technologies by the Kuali Foundation.

Kuali Coeus meets many of the objectives and requirements identified by Boston University for an Enterprise Research Administration System. Kuali Coeus provides a comprehensive research proposal development and management system that integrates well with BU’s future financial system (SAP) and fits within the overall vision for a “cradle-to-grave” solution for research administration

Learn more about Boston University's implementation of a Kuali Coeus system here.