693KA8-24-DRAFTSIR-INVERSE_Attachment J-3 DIDs.pdf

DRAFT

Invoice Validation and Expense Reconciliation Services

(INVERSE)

Attachment J-3

Data Item Descriptions

June 20, 2024

Federal Aviation Administration

800 Independence Avenue

Washington, D.C. 20591

INVERSE DRAFT SIR 693KA8-24-R-XXXXX

Attachment J3-2

DATA ITEM DESCRIPTION

1. CDRL Title

Program Management Plan

2. CDRL Number

F001

3. Description

The Program Management Plan (PMP) must describe the Contractor’s management approach to ensure successful technical, schedule and cost execution of the tasks identified in the

INVERSE Statement of Work (SOW) and ensure successful operation and performance of the services and capabilities required by the INVERSE Functional and Performance Specification

(IFPS), Attachment J-1.

1) Data Requirements

Reference: SOW Paragraph C.4.1.2

Format: Microsoft Word in contractor format.

Content: The PMP must contain the following information at a minimum:

1) Introduction: This section must contain an overview of the Contractor's management approach to ensure successful performance of the contract.

2) Management Approach: This section must describe the Contractor's detailed management approach, including methodologies, corporate best practices, processes, and procedures to be used to ensure successful program and contract performance to include the Contractors approach to:

• Meeting the technical requirements;

• Meeting the Contractor’s schedule;

• Monthly invoice processing;

• Security Management (reference Attachment J-5)

3) Management Organization: This section must include company organization chart(s) with a narrative to fully describe all organizational levels, to include:

• The program management organization to be used in performance of the contract;

• Key personnel assigned to the project; and

• Major subcontractors, along with their specific role and responsibility.

• This section must describe executive and senior management oversight and visibility into contract performance.

• This section must also describe internal policies and procedures to be used in managing the contract.

4) Roles, Responsibilities, and Organizational Relationships. This section must discuss the authority of all responsible management positions identified by the management organization description. The description must include the role of the project manager to

Attachment J3-3

Program Management Plan

2. CDRL Number

F001 direct, control, and commit resources to successfully manage the performance of the contract. This section must describe working relationships the Contractor will establish with the FAA.

5) Configuration Management. This section must discuss the Contractor’s configuration management approach to comply with FAA Order 1800.66. This section must discuss how configuration management will be implemented and maintained, as well as the methods, procedures, and controls used to ensure effective configuration identification, configuration control, status accounting, and audits of hardware, software, firmware, and documentation. This section must discuss the responsibilities of the Contractor’s CM organization with respect to internal system interfaces like engineering, implementation, security, quality assurance, test and evaluation, and operations.

6) Program Control and Status Reporting. This section must describe the Contractor’s approach for continuous monitoring of program performance:

7) Program Schedule. This section must describe the Contractor’s approach for development and monitoring of the development schedule of the System and the INVERSE User Portal.

8) Performance Management. This section must describe the organization, resources, policies, processes, methods, systems, and tools for:

• Collecting and validating invoice data

• Monitoring and tracking performance

• Reporting and communicating performance

• Identifying, developing, and implementing preventative, corrective, and remedial actions

9) Risk Management. This section must discuss the Contractor’s approach for the identification, assessment, and mitigation of risks to support FAA's Risks, Issues, and

Opportunities (RIO) management process.

10) Insider Threat Prevention. This section must describe Contractor’s Insider Threat

Prevention Program to mitigate the risk of insider threats to the INVERSE system.

Attachment J3-4

Program Master Schedule

2. CDRL Number

F002

3. Description

The INVERSE Program Schedule must identify program activities and milestones leading to:

• An initial operating capability for the INVERSE contractor’s invoice review, expensing, and reconciliation process

• The availability of the INVERSE User Portal and data repository

• Delivery of all CDRLS identified in Attachment J-2

4. Data Requirements

Reference: SOW C.4.1.2

Format: Microsoft Project Schedule format.

Content: The INVERSE program schedule must contain the following information at a minimum:

1) The INVERSE Program Schedule shall identify and depict the following, at a minimum:

• Task descriptions

• Task identification numbers

• Planned and actual start dates for tasks

• Planned and actual completion dates for tasks

• Number of calendar days planned and required to complete a task

• Milestone descriptions for all

• Milestone identification numbers

• Planned and actual dates of accomplishment for milestones

• Tasks on the critical path

• Task progress

2) The INVERSE Program Schedule must be presented in Gantt/milestone chart format. The

INVERSE Program Schedule shall identify milestone dates for government-furnished items required by the INVERSE contractor.

Attachment J3-5

Monthly Status Report (MSR)

2. CDRL Number

F003

3. Description

The INVERSE Monthly Status Report must provide the Contractor’s assessment of overall contractual progress, risk identification and mitigation strategies, progress against schedule baseline and identification of variances, performance data, and cost reporting during the MSR reporting period.

4. Data Requirements

Reference: SOW C.4.1.2

Format: Microsoft Word contractor format.

Content: The Monthly Status Report must contain the following information at a minimum:

1) Executive Summary. This section must discuss the overall program status, including a summary of Contractor and subcontractor (if applicable) performance in meeting the cost, schedule, and technical baseline plans, including significant problem areas, corrective actions taken, and any required Government action(s).

2) Accomplishments. This section must discuss the accomplishments during the last reporting period, including the current status of major events and milestones. This section must compare the status of the current month with the prior month’s projections. This section must discuss any problems associated with each milestone as well as their resolutions.

Include a 60-day outlook on projected activities.

3) Schedule and Technical Performance. This section must include all INVERSE key milestone dates identified in the program schedule and their status. If there are schedule delays, discuss the impacts, risks, and risk mitigation actions planned or taken. This section must include information that shows the relationship between schedules and technical performance.

4) Test and Evaluation. This section must discuss the status of test and evaluation activities associated with achieving the full operational capability of the INVERSE System and

INVERSE User Portal.

5) Risk, Issues, and Opportunities Management. This section must include a top-level statistical summary of Risks, Issues, and Opportunities (RIO) status. The section must report on medium and high RIO items, including the status of the associated mitigation plans. Each RIO item must be identified and discussed separately. For each RIO item, provide a description, an assessment of the criticality and time sensitivity, and mitigation plans. All medium and high RIO items must be tracked until closure by the FAA.

6) Action Items. This section must include the status (e.g., open, closed) of all formally assigned action items. If open, provide the actions necessary to close the action item and the planned date. If closed, provide the date closed and the resolution. Action items remaining open between reporting periods will be reported.

Attachment J3-6

Program Management Review (PMR)

2. CDRL Number

F004

3. Description

This deliverable provides the materials presented by the Contractor during the conduct of a

Program Management Review (PMR).

4. Data Requirements

Reference: SOW C.4.1.2

Format: Microsoft PowerPoint in contractor format.

Content: The PMR Presentation Materials must provide the status of contract activities performed and services delivered during the period of performance covered by the review. The topics must include, but are not limited to:

1) Program status and accomplishments since the last PMR;

2) Quarterly and year-to-date metrics summarizing the support services provided;

3) Cost, schedule, and performance status, including problem areas and known or anticipated differences between contract milestones, schedules, or performance parameters;

4) Contractual issues and proposed resolutions;

5) Status of Risks, Issues, and Opportunities (RIO) items tracked by the Contractor, including items opened and closed since the last PMR;

6) Status of open action items including any actions closed since the last PMR; and

7) Major activities and events planned for the next 90 days.

Attachment J3-7

System Level Design Review Data Package

2. CDRL Number

F005

3. Description

The System Level Design Review Data Package demonstrates that the system is capable of meeting the INVERSE requirements and capabilities within the time and allocated budget.

4. Data Requirements

Reference: SOW C.4.2.2

Format: Microsoft Word and/or PowerPoint in contractor format.

Content: Must contain the following information at a minimum:

1) The technical architecture of the proposed solution;

2) Illustrations of what the user interface will look like;

3) Any Government-furnished items (GFI) that the proposed solution is dependent upon;

4) A qualitative description and quantitative substantiation of how the solution will meet all applicable requirements in the Statement of Work and INVERSE Functional and

Performance Specification (IFPS);

5) A description of how the solution will comply with all applicable information security standards, policies, and orders;

6) Details for testing of the proposed solution including a listing of all formal Development

Tests (DT) that will be performed to ensure system meets all requirements.

7) The transition and implementation approach and schedule;

8) The life cycle support approach including any training required for Contractor personnel;

9) Program risk analysis, including assumptions, trade-offs, and alternative approaches if applicable.

Attachment J3-8

System Test and Acceptance Report

2. CDRL Number

F006

3. Description

The System Test and Acceptance Report documents the results of the Development Tests (DT) conducted by the contractor.

4. Data Requirements

Reference: SOW C.4.2.2

Format: Microsoft Word in Contractor format.

1) Title Page. The title page must contain the following at a minimum:

• DT Report;

• Signatures from INVERSE Program Manager, the person managing the test, and the responsible Quality Assurance person; and

• A statement certifying that the test results are authentic, accurate, and conducted in accordance with the procedures and adheres to the contractor’s quality assurance procedures.

The title page must indicate whether the DT Test Report contained within the specific version of the deliverable applies to DT conducted at Contractor facilities or DT conducted at

Government facilities.

2) Executive Summary. This section must contain an executive summary of the test results including a summary of all requirements validated and any failures/discrepancies identified during test conduct. This section must also contain any testing deferred and the associated rationale.

3) Introduction.

• System Overview. This section must contain brief overview of the portion of the system under test.

• Document Overview. This section must contain the purpose and contents of this document.

• Reference Documents. This section must contain any reference documents applicable to the generation of this report.

4) Test Overview. This section must contain:

• an overview that includes a description of how test data was collected and the method of analysis used to obtain results.

• a summary of test procedure, test set-up and/or system configuration changes that occurred during the test conduct, and their associated rationale

• roles and responsibilities of Contractor and Government personnel who participated during DT.

Attachment J3-9

System Test and Acceptance Report

2. CDRL Number

F006

5) Test Results. This section must contain detailed test results including the following information at a minimum:

• The baseline system configuration under test.

• Test logistics including location, and start and completion dates.

• Test results for each test case/procedure (the test log may be used as reference);

• Any changes to approved test procedures, test set-up, or baseline system configuration under test and associated rationale.

• When there are test failures/discrepancies, identify:

i) Date, location, and time

ii) System configuration

iii) Test case/procedure

iv) Expected result

v) Specific failure/discrepancies

vi) Resulting Program Trouble Report (PTR) including PTR number, associated requirement number and description of the problem

• Detailed data analysis results and a complete description of post-test data analysis activities.

• Identify any open items after completion of testing and analysis.

6) Appendix A - Test Procedures. Appendix A must contain a copy of the approved test procedures used during testing including any changes approved by the Government Test

Director.

7) Appendix B - Test Log. Appendix B must contain a copy of the actual test log developed during testing including any discrepancy reports and supporting data.

Attachment J3-10

Certification and Expense Recommendation

Report

2. CDRL Number

F007

3. Description

The purpose of the Certification and Expense Recommendation Report is to identify the net amount to pay for Telecommunications Services Delivery Orders on a particular monthly invoice by Funding Account Number (FAN) in addition to accounting for administrative errors, service credits, and billing adjustments. This CDRL also provides the INVERSE contractors certification of the results to the FAA.

4. Data Requirements

Reference: SOW C.4.3.5

Format: Microsoft Excel one tab per program plus supporting tabs if required.

Content: The Certification and Expense Recommendation Report must contain the following information at a minimum. There must be one report for each program (FENS/EIS).

1) Bill Date

2) Funding Account Number (FAN)

3) Net Charges

4) Shipment (Delivery Order Line Number)

5) Release (Delivery Order Number)

6) Distribution (Breakout of funding under a Delivery Order Line Number)

7) Project

8) Project Task

9) Charge Account

Attachment J3-11

Discrepancies Recommendation Report

2. CDRL Number

F008

3. Description

The purpose of the Discrepancies Recommendation Report is to provide a record of all discrepancies identified by the IFMS contractor in the current FENS/EIS Invoice for FAA consideration for short pay in addition to tracking any open discrepancies not yet resolved.

4. Data Requirements

Reference: SOW C.4.3.6

Format: Microsoft Excel, single tab data file for each program for the current invoice. Single tab for each program with all open discrepancies from past invoices plus supporting tabs if required.

Content: Must contain the following information at a minimum. There must be one report for each program (FENS/EIS).

1) Invoice reference number of when discrepancy occurred

2) Unique Discrepancy ID number

3) Delivery Order Number

4) Service Order Identifier

5) Unique Service Identifier Number

6) CLIN Code

7) Discrepancy Description

8) Charges

9) Comments

10) Discrepancy status (i.e. Open, Closed, with CO/COR, etc.)

11) Any additional fields required to track and resolve discrepancies.

All discrepancies must remain on the report until they are closed and must only be removed from the report after the month it is shown to be closed on the report.

Attachment J3-12

FAN Status and Expensing Summary Report

2. CDRL Number

F009

3. Description

The purpose of the FAN Status and Expensing Summary report is to track and report the financial status of all FANS by program (FENS/EIS) for the life of the program.

4. Data Requirements

Reference: SOW C.4.5

Format: Microsoft Excel, single tab data file for each program

Content: Must contain the following information at a minimum. There must be one report for each program (FENS/EIS).

1) Delivery Order

2) Funding Category

3) Program Name

4) Funding Account Number (FAN)

5) FAN Status

6) FAN Start Date

7) FAN End Date

8) Amount Funded Less Total Cost

9) Amount Funded Less Cost Incurred to Date

10) Cost Incurred to Date

11) Estimated Costs to be Incurred

12) Total Estimated Cost at Complete

13) Funded Amount

14) Expensed Amount

15) Balance (Funded Less Expensed)

16) Funded Credit: Amount Funded Less Total Cost if Positive Number

17) Funded Debit: Amount Funded Less Total Cost if Negative Number

18) Number of Services within FAN

19) Earliest Service Need Date for Services not yet Installed

20) Latest Service Need Date for Services not yet Installed

Attachment J3-13

OPS Funding and Budget Projection

Summary

2. CDRL Number

F010

3. Description

The purpose of the OPS Funding and Budget Projection is to show 36 months of summary charges. Four of the 36 months must be the most recent invoice months, one of the 36 months must be the current invoice month, and the remaining 31 months must show the projected invoice amounts. The projection must be based on the following assumptions: 1) Existing

CLINs continue through the projection period, and 2) Any changes in CLIN prices associated with existing CLINs are incorporated into the projection.

4. Data Requirements

Reference: SOW C.4.5

Format: Microsoft Excel, single tab data file for each program. The FAA may request further breakdown within the program as needed.

Content: Must contain the following information at a minimum by program or subprogram breakdown as specified by the FAA:

1) Invoice Reference number showing 36 months of invoices (Four past invoices, One current

Invoice, Thirty One future invoice numbers)

2) New Invoice Charges (Excluding Taxes)

3) Prior Period Adjustments (Only required for Past Invoices)

4) Total Invoice Charges (New Invoice Charges + Prior Period Adjustments)

5) Taxes and Surcharges Invoiced

6) Outage and Security Credits

7) Special Credits and Charges

8) Additional breakout of remaining Total Invoice Charges based on FAA’s reporting needs.

Attachment J3-14

FAA Invoice to Organizations with

Reimbursable Agreements

2. CDRL Number

F011

3. Description

The FAA has reimbursable agreements with other organizations (e.g., DISA, NAV Canada, Bermuda). This document provides the respective organization with an invoice from the FAA based on the reimbursable agreement in place. Each organization will receive a separate

CDRL, and contractor must place a sequential Alpha character for each Organization (e.g., F011a, FO11b, etc.).

4. Data Requirements

Reference: SOW C.4.5

Format: Microsoft Excel in contractor format

1) Summary Page on First Tab of Excel Spreadsheet

• Invoice Sender: Name and Contact Information

• Invoice Recipient: Name and Contact Information

• Invoice Number

• Invoice Date

• Invoice Due Date

• Period of Performance covered on invoice

• Current Invoice Charges

• Prior Customer Balance

• Payments made since Prior Invoice

• Current Customer Balance

2) Details of Current Charges on Second Tab of Excel Spreadsheet

• FAA Service Identifier

• Start Date for current charges

• End Date for current charges

• MRC/NRC

• Description of charges

• Quantity

• Unit Price

• Extended Price (Quantity * Unit Price)

Attachment J3-15

Data Tracking and Analysis Reports

2. CDRL Number

F012

3. Description

Data Tracking and Analysis Reports provide the FAA with additional tracking of invoice and expensing information.

4) Data Requirements

Reference: SOW C.4.6

Format: Microsoft Excel in contractor format.

1) Delphi Status Report contains cumulative information by program the current invoice month (FENS and EIS) and must include all data elements listed below.

• Delivery Order Number

• Delivery Order Line Number

• Type of Funding (i.e., F&E, OPS)

• Net Funded Amount

• Cumulative Paid to Date

• Remaining Balance

• Invoice Sequence number information is based on

• Project code breakout

• Accounting Code

• Funding Account Number (FAN)

• Sub Program/Cost Centers as defined by the Government

Attachment J3-16

Data Tracking and Analysis Reports

2. CDRL Number

F012

2) Contract Expenditures Report contains FAA User defined information by program

(FENS and EIS) and must include all data elements listed below for the last 12 months of invoicing.

• Delivery Order Number

• Delivery Order Line Number

• Type of Funding (i.e., F&E, OPS)

• Expenditures to date

• Funded Amount

• Invoice Number (This is to show multiple months of invoices broken out by Invoice

Number)

• Project code breakout

• Accounting Code

• FAN

• Sub Program/Cost Centers as defined by the Government

• Invoice Sequence Number

Attachment J3-17

System Authorization Briefing

2. CDRL Number

F013

3. Description

The purpose of the System Authorization Briefing is to provide a high-level description of the system, its mission, functions, and users to support the security authorization of the system.

The System Authorization Briefing is required for the initial authorization for the system and when there are substantial changes to the system’s operational, support, development, monitoring, or test environment.

1) Data Requirements

Reference: SOW C.4.7

Format: Microsoft Word FAA Format.

1) The System Characterization Document completed in accordance with the instructions contained in the United States (U.S.) Department of Transportation (DOT), FAA current fiscal year Security Authorization Handbook and the Air Traffic Organization (ATO)

Information System Security Program Office System Authorization Briefing.

Attachment J3-18

System Security Plan (SSP)

2. CDRL Number

F014

3. Description

The SSP is used as the basis for the Security Control Assessment (SCA), verifying the correct operation and effectiveness of the control implementation. The SSP must provide a summary of the information system security requirements and identify applicable security controls as being System-Specific, Common, or Hybrid.

Reference: SOW C.4.7

Format: Microsoft Word FAA Format.

Information System Security Program Office System Security Plan Template.

Attachment J3-19

System Characterization Document (SCD)

2. CDRL Number

F015

3. Description

The SCD provides a description of the system, including the system overview and mission;

system architecture; hardware and software; internal and external connectivity; and system data/information types, sensitivity, and criticality.

Format: Microsoft Word FAA Format

Information System Security Program Office System Characterization Document Template

Attachment J3-20

System Privacy Documentation

2. CDRL Number

F016

3. Description

The FAA protects Personally Identifiable Information (PII) through the completion and management of the following privacy compliance documents: Privacy Threshold Assessment

(PTA), Privacy Impact Assessment (PIA), and System of Records Notice (SORN).

A PTA is required for all Information Technology (IT) systems, technologies, proposed rulemakings, and information collections at the Department of Transportation (DOT). The adjudicated PTA serves as the official determination by the DOT Privacy Office as to whether a program or system has privacy implications, and if additional privacy compliance documentation is required, such as a PIA and/or a Privacy Act SORN.

1) The System Privacy Documentation completed in accordance with the instructions contained in the United States (U.S.) DOT, FAA current fiscal year Security Authorization

Handbook

Attachment J3-21

Information System Contingency Plan (ISCP)

2. CDRL Number

F017

3. Description

The ISCP provides established procedures for the assessment and recovery of INVERSE following a system disruption. The ISCP is used to recover the system at the original or an alternate location. The ISCP describes the procedures necessary to ensure the continuing performance of INVERSE core business functions and services during an outage and the restoration of any failed service functionality after an event. The ISCP is not considered complete until it is tested and updated accordingly, based on the test results and lessons learned.

1) The ISCP completed in accordance with the instructions contained in the United States

(U.S.) Department of Transportation (DOT), FAA current fiscal year Security

Authorization Handbook and the Air Traffic Organization (ATO) Information System

Security Program Office Information System Contingency Plan Template.

Attachment J3-22

Information System Contingency Test Plan

2. CDRL Number

F018

3. Description

The Information System Contingency Test Plan describes the organization’s plan to verify the effectiveness of the organization’s controls and the means to be used to evaluate their effectiveness against anticipated outages. The Information System Contingency Test Plan identifies the system to be tested, the approach used for testing, and the testing team.

1) The Information System Contingency Test Plan completed in accordance with the instructions contained in the United States (U.S.) Department of Transportation (DOT), FAA current fiscal year Security Authorization Handbook and the Air Traffic Organization

(ATO) Information System Security Program Office Information System Contingency

Test Plan and Results Report Template.

Attachment J3-23

Information System Contingency Test Results

Report

2. CDRL Number

F019

3. Description

The Information System Contingency Test Results Report presents results of testing completed in accordance with the Information System Contingency Plan Test Plan to verify the effectiveness of the organization’s controls and evaluation of their effectiveness against anticipated outages.

1) The Information System Contingency Test Results Report completed in accordance with the instructions contained in the United States (U.S.) Department of Transportation (DOT), FAA current fiscal year Security Authorization Handbook and the Air Traffic Organization

(ATO) Information System Security Program Office Information System Contingency

Test Plan and Results Report Template.

Attachment J3-24

Information System Decommissioning and

Disposal Plan (ISDDP)

2. CDRL Number

F020

3. Description

The ISDDP describes the conditions requiring decommissioning and disposal, the types of media subject to the provisions of this plan, the approved processes for decommissioning and/or disposal for each media type, and test procedures for assuring the effectiveness of the decommissioning/disposal process. This plan also identifies data, software, firmware, storage media, documentation, and hardware that must be retained for legal or other purposes.

4. Data Requirements

Reference: SOW C.4.7

Format: Microsoft Word in Contractor format

1) System Identification.

• System Name/Title Identifier (ID) and Name of the System.

• Responsible Organization Identify organization(s) responsible for the application.

• Information Contacts Names of individuals knowledgeable about, or the owner of, the system and their alternate contact.

i) Name

ii) Title

iii) Telephone number; and

iv) Email address

• Assignment of Security Responsibility Name of person responsible for security of the system and their alternate contact.

i) Name

ii) Title

iii) Telephone number; and

iv) Email address

2) Determine Ownership of Data.

• Determine data ownership and obtain decommissioning permission in advance from the owner; and

• Notify and coordinate with all parties who may use data prior to decommissioning.

Attachment J3-25

Information System Decommissioning and

Disposal Plan (ISDDP)

2. CDRL Number

F020

3) Conditions Requiring Decommissioning and Disposal.

• State the conditions and timeframe that will require the decommissioning and/or disposal of electro-magnetic, optical, or other media. All sensitive but unclassified electro-magnetic, optical or other media, capable of holding a non-volatile image of the data, must be decommissioned and/or disposed of in such a manner as to prevent the disclosure of sensitive information. Examples of conditions are as follows:

i) Transfer of media (e.g., hard disks, computers, etc.) to another organization; and

ii) Decommissioning of information processing systems for disposal/sale to internal/external agencies.

4) Type of Media, Designation of Media and Data Types. Describe the types of media and data types/sensitivity that require decommissioning and/or disposal.

5) Legal and Forensic Data. Identify data, software, and hardware that must be retained for legal, forensic, or other purposes.

6) Type of Decommissioning and/or Disposal Process. Describe the decommissioning and/or disposal process that must be used upon the media defined in item #4 above. This information may be in text, table, or another format. The plan must include identification and disposal/recycling of components that contain toxic or hazardous materials. Examples of sanitization are as follows:

• Overwriting

• Degaussing

• Destruction

7) Test Procedures. Describe the procedures by which the sanitized media is to be tested for data remanence. This information may be in text, table, or another format. Examples of test procedures are as follows:

• Data restoral programs

• Disk sector-viewing programs

• Sampling of destroyed contents to assure the improbability of reconstruction of data

• Sampling of decommissioned or transferred systems/components for presence of designated data types

Attachment J3-26

Security Incident Report

2. CDRL Number

F021

3. Description

The Security Incident Report provides a description of a specific information system security incident, its impact, and how it was resolved.

4. Data Requirements

Reference: SOW C.4.7

Format: Microsoft Word in Contractor Format

1) Type of event

2) Date of event

3) Time of event

4) System source

5) User/subject identification

6) Event description

7) Operational impact of the event

8) Remedial actions

9) Session Identifier (ID), when the event has an associated Session ID

Attachment J3-27

User Instruction Manual

2. CDRL Number

F022

3. Description

The User Instruction Manual provides users instructions and reference material to utilize the functionality of the INVERSE user portal as specified in the SOW and accompanying documents.

4. Data Requirements

Reference: SOW C.4.8

Format: Microsoft Word contractor format.

1) Table of Contents

2) General Information

• System overview

• Help Desk support information

• Acronyms and Abbreviations

3) System Summary

• System configuration and Data Flows

• User Access Levels and definitions

4) Getting Started

• Logging On

• System Menu Tree

• Changing User ID and Password

• Exiting the System

5) CDRLs

• Opening up CDRLS for Review

• Approving and Rejecting with Comments

• Retrieving past CDRLs

6) Reporting

• Reporting Capabilities

• Running pre-made reports

• Modifying reports

• Creating Custom Reports

7) Data Repository

• Organization

Attachment J3-28

User Instruction Manual

2. CDRL Number

F022

• Posting information

• Accessing information