14
Clause Logic Service User Interface Integration Guide Version 1.0 2017 Prepared by: Northrop Grumman 12900 Federal Systems Park Drive Fairfax, VA 22033
Clause Logic ServiceUser Interface Integration Guide
Version 1.02017
Prepared by:Northrop Grumman
12900 Federal Systems Park DriveFairfax, VA 22033
Under Contract Number:SP4709-17-D-0022, TO 0001
Revision HistoryDate Revision
NumberAuthorization Revision/Change
DescriptionPage, Section
08/24/17 Original Bob Baughman New Document All08/25/17 Original Kathleen Lemming Verbiage, Grammar,
CenteringAll
Clause Logic Service User Interface Integration Guide
Table of Contents
1 Introduction...........................................................................................................................12 Contract Writing System Integration..................................................................................1Appendix A CLS ALTESS Login Screens.............................................................................4Appendix B Acronyms............................................................................................................8
Table of FiguresFigure 2-1. Validate Session.........................................................................................................1Figure 2-2. Export Clauses............................................................................................................2Figure 2-3. Save or Save As.........................................................................................................2Figure 2-4. Dropzone Location and Filename...............................................................................3Figure 2-5. CLS XML Response File.............................................................................................3Figure A-1. ALTESS SSO Page....................................................................................................4Figure A-2. CAC Login Page.........................................................................................................4Figure A-3. CAC PIN Window.......................................................................................................5Figure A-4. Acceptable Use Agreement Window..........................................................................5Figure A-5. Disclaimer Page..........................................................................................................6Figure A-6. CLS UI........................................................................................................................6Figure A-7. Invalid CLS User Window...........................................................................................7
i
Clause Logic Service User Interface Integration Guide
1 IntroductionThe operational enterprise Clause Logic Service (CLS) (using the Procurement Data Standard) is used by contracting personnel during the acquisition process to allow for consistent inclusion of the required provisions and clauses in every procurement action. CLS ensures the selection of provisions and clauses based on a standard set of system logic rules for the current Federal Acquisition Regulation Supplement (FARS), and Defense Federal Acquisition Regulation Supplement (DFARS).
The CLS User Interface (UI) application is a user Common Access Card (CAC) authenticated application that requires individual user accounts to be created in the CLS system prior to gaining access. Defense Procurement and Acquisition Policy (DPAP), Program Development and Implementation (PDI) is the approval authority for user accounts. CLS Champions must coordinate with the DPAP CLS points of contact for user account approval and creation at:
Kathleen Lemming - OSD Pentagon OUSD ATL Mailbox DPAP Clause Logic Service ([email protected])
2 Contract Writing System IntegrationA Contract Writing System (CWS) can access the CLS UI via the following Uniform Resource Locator (url): https://clauselogic-ui.altess.army.mil/ClauseLogicServiceUI/SSO
The CWS determines the best method to launch the CLS UI via the url from within their CWS application as part of their business application implementation. Once the CLS UI is launched from the CWS, the individual users are prompted to authenticate to CLS UI using their individual CAC and CAC Personal Identification Numbers (PIN). See Appendix A for expected screens for user login. Once authenticated and logged into the CLS UI, the user completes the question and answer (Q&A) session to provide the appropriate answers for the applicable contract document (see CLS User Manual v1.1).
At the end of the Q&A session, the user validates the session via the Validate Session button to receive clauses from the CLS rules engine (shown in Figure 2-1). The clauses are displayed in the CLS UI clause cart on both the “Session” and “Clauses” tabs.
Figure 2-1. Validate Session
1
Clause Logic Service User Interface Integration Guide
The CLS UI “Clauses” tab provides the capability to export the CLS clause results. The user navigates to the “Clauses” tab to be able to export (shown in Figure 2-2) the clause results in a CLS XML v3.0 schema structured file.
Figure 2-2. Export Clauses
When “Export Clauses” is selected, the normal windows “Save or Save As” functionality is available. The CWS can either set the CWS users default save files location to a common drop zone for clause results or they can allow the user to browse to a specific location. The user selects “Save or Save As” as directed by and implemented in the CWS (as shown in Figure 2-3).
Figure 2-3. Save or Save As
2
Clause Logic Service User Interface Integration Guide
If the “Save As,” function is chosen, the user browses to the common drop zone for the CWS and saves the file as shown in Figure 2-4. If using “Save,” the CWS will have set up the default save location for the user. The user also has the opportunity to change the file name before saving, but the default file name contains the document number (CWS PIID) that was entered in CLS at the start of the session.
Figure 2-4. Dropzone Location and Filename
The CLS XML file exported and saved from CLS has numerous <Clause Details> tags. The CWS will have to parse the CLS response XML file to gather the clauses applicable to the solicitation or award document and use them accordingly within the CWS to complete the clause preparation of the document. The CLS XML Response format is described by the CLS XML v3.0 schema, as shown in Figure 2-5.
Figure 2-5. CLS XML Response File
3
Clause Logic Service User Interface Integration Guide
Appendix A CLS ALTESS Login Screens
The Production CLS User Interface (UI) hosted at the Acquisition Logistics and Technology Enterprise System and Services (ALTESS) Army data center is a Common Access Card (CAC) authenticated web service.
The following screen shots show what the user receives as they progress through the CAC authentication and CLS login process:
In the first web page, the user is presented with the ALTESS Single Sign-On (SSO) web page (shown in Figure A-1). The user selects “I Agree” to progress to the next web page.
Figure A-1. ALTESS SSO Page
The user selects “CAC Login” to proceed (shown in Figure A-2).
Figure A-2. CAC Login Page
4
Clause Logic Service User Interface Integration Guide
The service takes a few seconds to display the CAC Personal Identification Number (PIN) window, shown in Figure A-3. The user enters their CAC PIN and selects “OK.”
Figure A-3. CAC PIN Window
On the page shown in Figure A-4, the user selects “I Agree” to accept the Use Agreement.
Figure A-4. Acceptable Use Agreement Window
5
Clause Logic Service User Interface Integration Guide
If successfully authenticated, the user sees the web page shown in Figure A-5. The user selects “Acknowledge” to the disclaimer and it opens the next web page.
Figure A-5. Disclaimer Page
The next web page, shown in Figure A-6, is the default first page of the CLS UI. Refer to the CSL UI User Manual to review user capabilities and the functionality of the CLS UI tabs and windows.
Figure A-6. CLS UI
6
Clause Logic Service User Interface Integration Guide
If the user is validated as a CAC user but are not in the CLS UI user database, the user will be denied access to the CLS UI application and sees the web page shown in Figure A-7. The user should contact their Agency/Serviced CLS Champion to request access.
Figure A-7. Invalid CLS User Window
7
Clause Logic Service User Interface Integration Guide
Appendix B Acronyms
The acronyms used in this document are defined below:
ALTESS Acquisition Logistics and Technology Enterprise System and Services
API Application Program Interface
CAC Common Access Card
CLS Clause Logic Service
CWS Contract Writing System
DFARS Defense Federal Acquisition Regulation Supplement
DPAP Defense Procurement and Acquisition Policy
FARS Federal Acquisition Regulation Supplement
PGI Procedures, Guidance, and Information
PIN Personal Identification Number
SSO Single Sign-On
UI User Interface
URL Uniform Resource Locator
8
