IEP Application Portfolio Attributes-RFI.xlsx
XLSX spreadsheet 49 KB Posted
- Solicitation number
- Not on record
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Draft IRS IEP 2.0 PWS.pdf | ||
| IEP Current State Draft.pdf | ||
| IEP 2.0 Service Initiation O-M TO PWS DRAFT.pdf | ||
| IEP_2.0_Initial TO RFI.docx | DOCX document | |
| IEP2_0 Initial TO DRAFT QASP.pdf | ||
| IEP 2.0 RFI Overview and Questions.pdf | ||
| IRS_IEP_2.0_PWS_Draft.pdf | ||
| IEP 2.0 Requirements Extract for RFI Responses.xlsx | XLSX spreadsheet | |
| IEP 2.0 SLOs Extract for RFI Responses.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attribute Description
| IEP Application Portfolio Attributes | ||
| DRAFT | ||
| General Application Information | Descriptions | |
| Application Name | The name of the IRS application, program, or group of programs, that is designed for the end user. | |
| Application Portfolio | Application group by supporting business unit or program. | |
| Application Description | Application description provides a summary of the scope and objective of the application. It can include the database programs, processors, Web browsers and spreadsheets. | |
| Application Status | Application status - 'Active', 'Retired', 'Planned to be Retired' with timeline, 'Planned' with timeline | |
| User Type | Defines the type of user such as business-to-business (b-to-b), employee, registered user, etc | |
| MSP Managed (Y/N) | Identify the application is managed by Managed Services Provider | |
| Dependencies | Dependency on other applications and business process | |
| User Traffic | Identify user traffic volume associated with application (Highest/Lowest) | |
| Application Development Technology | Technologies used to develop the application. (e.g. Java, Spring Framework, Open JDK, HTML, Python, etc.) | |
| User Auth Critera | App Embedded | |
| ID Provider External to App | ||
| No Authentication | ||
| Certificate Based | ||
| Other | ||
| IRS User Interface Type | Direct User Interactions | |
| App to App/API Based Interactions | ||
| Content Cachability and Type | Dynamic | |
| Static | ||
| Processing and Data Type Criteria | Publicly Available Data | |
| Transient Through the IRS Integrated Enterprise Portal (IEP) | ||
| Persistent/System of Record in IEP | ||
| Hosting and Application Management | Descriptions | |
| Hosting Service Type | Hosting service type could be one of Infrastructure as a Service (IaaS), Platform as a Service + (PaaS+), Platform as a Service + 3rd Party (PaaS+3rd), and Software as a Service (SaaS). If there is any additional hosting service type, please enter them in the field. | |
| Portal Type | Logical group of the hosting environment where IEP application reside - Employee User Portal (EUP), Public User Portal (PUP), Registered User Portal (RUP), Transactional Portal Environment (TPE), and Web Content Management System (WCMS). | |
| Physical Environment | ||
| (MSP Private Cloud, AWS Gov, Drupal SaaS) | Identify which hosting company/data center provides the service. (MSP Private Cloud, AWS Gov Cloud, Drupal SaaS) | |
| Deployment Model | Identify the deployment model for the application, e.g. IEP-Control Document (IEP-CD): covers automated deployments, IEP - DD/IEP - CD Manual: covers manual deployments. | |
| IEP DevOps | Is the application using DevOps process? | |
| Containerized (Y/N) | Containerization and virtualization are similar in that they both allow for full isolation of applications so that they can be operational in multiple environments. Where the main differences lie are in size and portability. Containers are much smaller, typically measured by the megabyte and not packaging anything bigger than an app and its running environment. Containers were made to be compatible with newer and emerging technology like clouds, CI/CD, and DevOps. | |
| Containerization Time Frame (Fiscal Year or N/A) | If the application is not containerized, identify time frame to containerize in the format of fiscal year. If there is no plan to containerize, enter 'N/A'. | |
| Container Orchestration Tool | Container orchestration is the automation of the deployment, management, scaling, and networking of containers. | |
| Server Operating Systems | Descriptions | |
| Application Server | An application server OS is a component-based product that resides in the middle-tier of a server centric architecture. It provides middleware services for security and maintenance, along with data access and persistence. | |
| Database Server(s) | A database server is the portal server which houses a database application that provides database services to other computer programs.It provides other computers with services related to accessing and retrieving data from a database. | |
| Web Platform Server(s) | Web Server handles HTTP requests. Application server will execute business logic on any number of protocols. Example: the portal uses Apache as a web server and Tomcat as an application server. | |
| Middleware Server(s) | Middleware is the software that lies between the operating system and the applications running on it. This can include security authentication, transaction management, message queues, applications servers, web servers, and directories. Common middleware include database middleware, application server middleware, message-oriented middleware, web middleware, and transaction-processing monitors. Each program typically provides messaging services so that different applications can communicate using messaging like SOAP, REST, and JSON. | |
| Middleware Integration Tools | Descriptions | |
| API Gateway | An API gateway is a programming tool that sits in front of an application programming interface (API) and acts as a single point of entry for a defined group of microservices. The API Gateway takes all the requests from the client, determines which services are needed, and combines them into a synchronous experience for the portal user. | |
| Messaging Tools | Programs communicate by sending each other data in messages. The tools support communications layer for visibility and control of the flow of messages and data. Portal messaging tools transport messaging integration from mainframe to portal apps. The portal uses MQ as a messaging and queuing middleware so that programs can run independently of each other, at different speeds and times, in different locations, and without having a direct connection between them. | |
| Database(s) | Database software tools are used for storing, modifying, extracting, and searching for information within a database. The portal uses Oracle MySQL and Microsoft SQL database SW | |
| File Transfer Tools | Programs communicate by sending each other data in messages. The tools support communications layer for visibility and control of the flow of messages and data. Portal messaging tools transport messaging integration from mainframe to portal apps. The portal uses MQ as a messaging and queuing middleware so that programs can run independently of each other, at different speeds and times, in different locations, and without having a direct connection between them. | |
| Middleware Runtime Tools | Descriptions | |
| Web Platform(s) Software | The Web platform is a collection of technologies developed as open standards to include technologies— computer languages and APIs. | |
| Application Server Software | An application server is a software framework that provides both facilities to create web applications and a server environment to run them. the application server acts as a set of components accessible to the software developer through a standard API defined for the platform itself. | |
| Data Encryption | Personally identifiable information, or PII, is any data that could potentially be used to identify a particular person such as SSN. | |
| Script Management Tool | A tool to manage and orchestrate script jobs and scheduled tasks scheduled ( e.g., Kron, Control-M) | |
| Identity and Access Management | An acronym for Identity and Access Management, IAM refers to a framework of policies and technologies for ensuring that the proper people in an enterprise have the appropriate access to technology resources. IAM identify, authenticate and authorize individuals who will be utilizing IT resources, the hardware and for accessing the applications. | |
| Middleware Protocols | Descriptions | |
| Front End Protocols Used | Frontend integration protocols is a web service that allows communication between frontend and backend technologies. The portal uses Simple Object Access Protocol (SOAP) and/or Representational State Transfer (REST) | |
| ECC Protocols Used (Back End) | A "back-end" integration protocol serves indirectly in support of the front-end services, and has the capability to communicate with the required resource. The back-end application may interact directly with the front-end or, is from an intermediate program that mediates front-end and back-end activities. | |
| IEP to Back End Messaging Tool | Secure File Transfer | |
| SiteMinder | ||
| Web Services | ||
| Message Queues | ||
| Other |
&P
Recommended Process Flow
Specification Temp source map
| AATS A2A | |||||
| Description | |||||
| Column E, Lookup column 4 | |||||
| Application Owner | |||||
| System Owner | Column I, Lookup column 8 | Business Owner | Column J, Lookup column 9 | ||
| Application User | |||||
| Public Users | Column G, Lookup column 6 | Registered Users | Column G, Lookup column 6 | ||
| Employees | Column G, Lookup column 6 | Business to Business | Column G, Lookup column 6 |
Supporting Services (Future Enhancement)
Operating Systems
| Application Server O/S | Column L, Lookup col 11 | Web Server O/S | Column Q, lookup col Q |
| Database Server O/S | Column O, lookup col 14 | Middleware Server O/S | Column S, lookup col S |
| Hosting Service Type - Column K, lookup col 10 |
| IF(VLOOKUP($A$2,'IEP App Portfolio Database'!$B:$CE,5,0)="PUP/WCMS Drupal","WCMS uses DRUPAL for content management","") |
| Middleware Classifications | |||||
| Middleware Integration Tools | Middleware Runtime Tools | ||||
| API Gateway | column X, lookup 23 | Web Platform(s) Software | Column AH, lookup 33 | ||
| Messaging | Column AC, lookup 28 | Application Server Software | Column AK, lookup 36 | ||
| Database(s) Software | Column AD, lookup 29 | PII Data -Encryption Tools | Column AL, lookup 37 | ||
| Script Management | Column AM, lookup 38 | ||||
| File Transfer Tools: | Identity Access Management Tools: | ||||
| Tectia | Column AF, lookup 31 | Siteminder | Column AN, lookup 39 | ||
| EFTU | Column AG, lookup 32 | eAuth | Column AO, lookup 40 | ||
| Active Directory | Column AP, lookup 41 | ||||
| Common Services | Column AQ, lookup 42 |
| Note: Proxy and Mail Server Tools can be required based on application needs | |
| Interface Protocols |
| Front End | Back End | |||
| HTTPS | Column AS, lookup 44 | HTTPS | Column AY, lookup 50 | |
| HTTPS w/SOAP | Column AT, lookup 45 | HTTPS w/SOAP | Column AZ,lookup 51 | |
| HTTPS SOAP w/MTOM | Column AU, lookup 46 | HTTPS SOAP w/MTOM | Column BA, lookup 52 | |
| HTTPS SOAP w/MTOM MA | Column AV, lookup 47 | HTTPS SOAP w/MTOM MA | Column BC, lookup 54 | |
| REST Request | Column AW, lookup 48 | REST Request | Column BF, lookup 57 | |
| JDBC | Column BE, lookup 56 | |||
| SQL Query | Column BH, lookup59 | |||
| NFS w/SFTP | Column BG, lookup58 | |||
| AMDAS | Column BB, lookup 53 |
Total Front End Interface Protocols Used Column AR,lookup 43 Total Back End Interface Protocols Used Column AX, lookup 49
Sizing (Future Enhancement) image1.emf
File details come from the government source that posted it. Updated .