Login is required to start a virtual session on the web server. This is necessary in order to provide some continuity to the user without each web request (URL) having to contain a complete username and password and header. The virtual session is maintained on the server side by user, session, and company information stored in an online database. On the client side, the session is maintained by a persistent client state object called a "cookie". Use of cookie filters, browsers or client-side fetch programs which disable or do not support HTTP cookies is not supported.

Effective April 1, 2011 the PJM OASIS has been updated to be compliant with v1.5 of the OASIS Standards and Communication Protocols (S&CP) found in the NAESB WEQ Business Practice Standards Booklet, Version 002.1, located here: http://www.naesb.org/weq/weq_standards.asp  PJM will continue to support v1.4 for backward compatibility.

As a convenience, PJM has modified the fetch_http program (initially provided to the OASIS community by PacifiCorp) to handle the use of the Siemens-format cookies. To download a tar file containing the modified source click here.

A PJM OASIS Account is required to begin a session on any Siemen's OASIS node. The session is maintained via the OASIS database on the server end and a HTTP cookie on the client side.

A login is required to begin a Transmission Customer session on a Siemens OASIS node. The session is maintained on the server side by information stored in the OASIS database. The session is maintained on the client side through the use of an HTTP cookie.

The format for the login template is:
http://pjmoasis.pjm.com/OASIS/PJM/data/login?user={user_name}&passwd={user_password}&pprov={provider_alias}

Where
{user_name} is your PJM OASIS username
{user_password} is the password corresponding to your PJM OASIS username
{provider_alias} is the alias for your service's primary provider (i.e. PJM, MISO, etc.)

The response to a successful login request will be the ASCII text: "You are logged in."

After a successful login a HTTP cookie will be returned via the server HTTP response header. The HTTP cookie will have the following form:
Set-Cookie: Siemens_Oasis={value}.

This cookie must accompany each subsequent request as part of the header and in the following form:
Cookie: Siemens_Oasis={value}.

Template requests have the following general format:
http://pjmoasis.pjm.com/OASIS/PJM/data/{template}?{template_parameters}

Where
{template} is a valid template as defined by S&CP version 1.4.
{template_parameters} are the arguments accepted by {template} as defined by S&CP version 1.4.
Note that the HTTP header must contain the cookie text returned to the client during the login process.

When following the S&CP document for submitting the Transrequest template, please keep these PJM header additions in mind:

PAY_CONGESTION
FTR_REQUESTED

These fields should be entered in this order at the end of the template string.
Note: FTR_REQUESTED field need only contain a value for FIRM products.

Login
http://pjmoasis.pjm.com/OASIS/PJM/data/login?user=my_username&passwd=my_password&pprov=PJM

Logout
http://pjmoasis.pjm.com/OASIS/PJM/data/logout

Transrequest Template - Firm Request
Template Code (TXT)

Transrequest Template - Non Firm Request for multi hour multi-megawatt requests
Template Code (TXT)

Transrequest Template - Non Firm Request 
Template Code (TXT)

Transoffering Template
Template Code (TXT)

List Template
Template Code (TXT)