273FCC20R0002 - App Dev - Technical Exhibit 2 - FCC Platform-Cloud Platform.doc

Technical Exhibit 2 FCC Platforms and Cloud Platform Architecture The FCC has acquired a set of commercial enterprise cloud platforms and software products that can be orchestrated in a modular fashion to efficiently develop, deploy, and maintain mission applications for FCC Bureau and Office stakeholders. For each system included under this contract, the contractor shall leverage the suite of FCC commercial enterprise cloud platforms and software products to the maximum extent possible. A graphical depiction of the FCC Cloud Platform Architecture is shown in Figure 1.

Figure 1: FCC Cloud Platform Architecture A short description of each of the primary cloud services in use by the FCC as well as their main contributions to the FCC service architecture is included below:

ServiceNow – This is the FCC’s primary enterprise application platform. Solutions requiring forms, workflows, business rules, and basic application-centric reporting shall leverage the ServiceNow platform and its configuration capabilities to rapidly prototype, iterate, and deliver basic capabilities required by FCC components. While custom development is possible (via UI and system scripting), it is preferable to leverage the out-of-the-box configuration capabilities of the service to the maximum extent possible before attempting development for application service delivery.

· ServiceNow Management, Integration, and Discovery (MID) Server – This on-premises component is primarily used to support data transmission and ingest from FCC legacy systems and databases. While it can also be leveraged to support API-level interactions, this use of the MID server component is not encouraged by the FCC architecture.

· ServiceNow User Interface / User Experience (AngularJS) – Public-facing applications delivered on the ServiceNow platform normally require some amount of interface customization. AngularJS is a JavaScript dialect that allows for interface development and customization.

MuleSoft AnyPoint Platform – This portion of the FCC’s to-be enterprise architecture is the primary integration platform that will enable the contractor to orchestrate services among the FCC’s cloud platforms as well as expose APIs to be leveraged both internally to the FCC and externally to the public as large.

Amazon Web Services (AWS) – AWS is the FCC’s preferred location for implementing and hosting custom applications and micro-services that cannot effectively (from a functional and cost perspective) be delivered and supported on the FCC’s other PaaS and SaaS cloud services. Services such as geo-spatial calculations, PDF conversion, and other functions not ideally suited for the Form and Workflow processing capabilities of the FCC’s ServiceNow solution that do not exist as enterprise services should be implemented on AWS as micro-services and exposed through the FCC’s MuleSoft AnyPoint Platform.

Box.com – While the FCC has many file storage solutions available to it (SharePoint, Amazon S3, Amazon Elastic File System, on-premises network drives, etc.), externally facing application solutions requiring content management, document publication, and accessible document visualization may leverage the Box.com platform used by the FCC.

Socrata – Many Bureaus and Offices at the FCC have data collected or generated in or by their mission applications where publishing it as Open Data is in the public interest. The FCC uses the Socrata Open Data Platform (ODP) to support this mission, and the contractor will be required to leverage the ODP to fill that mission. The ODP also API-enables published datasets, so usage of the platform to host data consumed by other mission applications on multiple platforms (where the data interfaces are exposed via MuleSoft) is supported as well.

Microstrategy – While ServiceNow can natively support some types of application-centric reporting, more sophisticated reporting that leverages data sources from multiple platforms, multiple mission areas, or analysis that requires basic statistical modeling necessitates a different toolset, and the FCC has selected Microstrategy (hosted on the FCC’s AWS Virtual Private Cloud) as the mechanism to provide that capability for its mission applications.

Okta – The FCC is consolidating its identity environment onto a single Identity and Access Management (IdAM) cloud platform for both internal and external use and has selected Okta as the tool of choice to enable that transformation. The FCC leverages multiple instances of the Okta platform to support its internal and external use cases, as consolidating the commissions’ external identity provisioning, authentication, and authorization capabilities into the same technology profile used for internal employee and contractor access, it greatly simplifies the cost of the IdAM program at the agency and makes significantly easier to develop a common codebase and identity profiles for new citizen-facing systems.